Drag your eyes to the right and note that there is a separate product/service and award date. The nature of gov contracting means there is likely a base contract, and when a new job comes up (e.g. healthcare.gov) they mod the contract and issue a new award. These are 114 separate scopes of work, separate projects. ~113 of which have nothing to do with healthcare.gov.

I am a federal and state gov IT contractor. I am well versed in the idiosyncratic nature of implementing systems for bureaucratic applications designed by committee. I still don't doubt it could have been done for less, but I doubt it could have been done for the amounts many of the folks here think they could do it for.

That figure covers 114 separate contracts (see http://usaspending.gov/explore?tab=By+Prime+Awardee&fiscal_year=all&idvpiid=HHSM500200700015I&typeofview=transactions ) Not to suggest that it still wasn't overly expensive, but consider the fact that the system is a national transaction application that has to dip into numerous other federal data sources - and has a mission criticality above and beyond facebook. Still, many of us could have done it better and cheaper, but then again very few of us would actually enjoy working for the federal government and conducting our business the way any federal contractor is required to.

I miss PointCast.

Sorry to burst everyone's bubble, but I just simulated an attack of far greater proportions. First, I simulated having the resources to simulate an attack of far greater proportions, then I simulated executing my far greater attack. If anyone is interested, the results showed that while I was adequately prepared to defend against a simulation, I need to beef up some protocols and institute some new processes.