The December 2022 issue of IEEE Spectrum is here!

Close bar

Texas Tells IBM: Make Way For Others on Outsourcing Contract

Texas Outsourcing Contract to IBM Likely to End in Court?

2 min read
Texas Tells IBM: Make Way For Others on Outsourcing Contract

Well, I sure got that wrong.

I was pretty confident that IBM and the State of Texas would reach some sort of mutually unacceptable accommodation in their disagreements over the quality and level of performance involving the outsourcing contract Texas awarded to IBM in 2006 that would allow everyone to save face and move on.

While I got the mutually unacceptable bit right, more importantly, I was way off about the two sides reaching an accommodation.

As you may recall, the Texas Department of Information Resources (DIR) sent an 8-page "Notice to Cure" letter to IBM last month in essence stating that in the state's opinion, IBM has failed to live up to the IT outsourcing promises it has made to the state since the contract's start.

The DIR gave IBM 10-days to come up with an acceptable cure plan, and 30-days to cure the contract breaches noted in the cure notice.

The 30-day period ended this week, with IBM declining to submit an acceptable plan, as well as in DIR's opinion, declining to fix the contract breaches noted in its cure letter.

On the Tuesday, the DIR sent a new letter to IBM stating that:

"On August 13, 2010, IBM delivered a letter to DIR that mischaracterized the obligations of IBM and DIR under the MSA, was insufficient to cure the breaches identified in the Notice to Cure Letter, and was little more than a reiteration of inconsistent and incomplete ideas that IBM has previously expressed. During discussions over the past nine months, IBM suggested that DIR re-procure all or part of the services under the MSA. Given IBM's failure to cure the breaches set forth in the Notice to Cure Letter, IBM now leaves DIR no course but to pursue procurement."

"In accordance with the terms of the MSA, the Notice to Cure Letter specified that IBM had thirty (30) days to cure each such breach. IBM has failed to cure the identified breaches. Accordingly, DIR has full legal right and authority to terminate the MSA for cause. DIR has determined that it is not in the best interests of the State to exercise that right at this time. DIR will proceed with procurement for all services required of IBM under the MSA. DIR requires IBM’s full and compliant performance of its obligations under the MSA."

"DIR expressly retains all rights with respect to termination of the MSA, and no delay in termination of the MSA shall be deemed a waiver of those rights."

What this all means is that the DIR will take over control of the contract, and according to a story in the Dallas-Morning News, rebid much of the remaining work on the contract.

An article in the Austin-American Statesman states that the contract required the merger of the data centers of 28 Texas state agencies "into two streamlined and secure facilities. The consolidation was supposed to be completed by December 2009 but is still only 12 percent complete."

IBM disagrees with the DIR's stance, and is quoted in the Statesman as saying it is still "hoping to continue a constructive dialogue" with the DIR.

That doesn't look too likely.

I hesitate to make any predictions, given my previous track record, but I would guess an eventual trip to court looks better than a 50-50 chance.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less