Source Code Dispute in Boston's Big Dig

JoshuaDFranklin writes "Boston's 'Big Dig' is famously long-running and over budget as noted before on Slashdot. But now Computerworld is reporting that a Software Ownership Battle Adds $10M to Cost of 'Big Dig'. The legal dispute was over whether Massachusetts had the right to share Transdyn source code with Honeywell, causing $2.72 million in damages and $7.2 million in costs of a four-month delay in the project."

Comments

Re:For those of us who don't live near Boston

[will_die]

The idea is to put in a 8-10 lane expressway under the city of Boston. They have a site at www.bigdig.com.
It has taken close to 20 year to do and has been extermly over run with greed, mismanagement, poor construction, and cost overruns.

Bad deal for Honeywell

[yakitori]

The segment of Honeywell that was involved with Big Dig was HTSI (Honeywell Technology Solutions Inc). HTSI is involved in alot of NASA or military related contracts (primarily ground stations or satellite control like HST, Landsat, etc). HTSI was formally Allied Signal which was formally Bendix (NASA followers should know the name). Lockheed became prime on a major NASA contract and began shrinking HTSI's role in it, so Big Dig was an attempt to branch out into Intelligent Traffic Systems to save jobs. Anyway, it was a disaster since day one. Folks here viewed Big Dig as the last stop to hell. Long mandatory hours with no vacations, constant deadline dates that were pushed back week after week, quarreling customers that literally threw chairs at each other. There were weekly 'farewell' lunches for employees as everyone started jumping ship. HTSI didn't receive the Transdyn software for years. What little that was received had to be completely rewritten (thousands upon thousands of lines of code) because it did not fulfill any of the necessary requirements. Boston refused to pay cost overruns to HTSI was the big kicker that made HTSI start to hemorrhage money. Big Dig was a losing cause.

HTSI eventually managed to recover. Lockheed royally screwed up their contract with NASA so it was ended early and HTSI managed to win on recompetes - by slitting their own throats but that is a story for another day... HTSI negotiated a way to end their involvement in Big Dig early (I guess HTSI learned a lesson and will only get involved in federal level contracts). Rumors are that Transdyn are negotiating to get back into writing the code for Big Dig. Hopefully they will have better luck the second time around. I'm sure there are lots of helpful comments in the current source revs in the ITS software for whoever develops it (particularly Transdyn :P)

Re:Typical

[phayes]

RTFA (yeah, I know this is /.). The code was never open in the first place.

Company A wins the contract to do phase 1 by modifying their existing software product.

Company B wins contract for phase 2. Company A refuses to deliver source code as it contains significant proprietary info. Segue into N month court battle ending up with a settlement in which company B sublicenses company A's info (for an undisclosed amount) & A gets .3M$ from BigDig.

Company B goes way overbudet & negotiates a premature end to it's contract. BigDig is now negotiating with Company A to finish what it started.

The 10M$ pricetag is from 3M$ BigDig wished they could have fined Company A for, + 7M$ in overruns from Company B.

Opensource could have been a solution to the problems they encountered, but only if BigDig was ready to finance the development of the software from scratch. Company A came to the table with a big head start as they were only modifying their own existing software.

Supplementary info: Company A is Californian & Company B is local. IMHO it sounds like somebody thought that the developers of the software was generic interchangable pork that could be used to buy votes locally & got burned when company A refused to play along...