recommended reading

Cost of Obamacare Contract Has at Least Quintupled

Ricardo Reitmeyer/Shutterstock.com

The cost of the computer cloud that supports back-end data sharing for HealthCare.gov and state Obamacare marketplaces grew to $60 million, more than five times its original value, by the time the troubled site was declared fully functional on Nov. 30, 2013, contracting documents show.

While the site has performed generally well since that date, the massive cost increase is further evidence that officials were ill-prepared for HealthCare.gov’s launch and drastically underestimated the amount of technology and storage the site would require.

The government’s contract with Terremark, Verizon’s cloud division, had already quadrupled from $11 million when it was first awarded in 2011 to $46 million at the time of HealthCare.gov’s disastrous launch in October 2013. That included a $9 million adjustment just days before launch when testing revealed the cloud could only support 10,000 concurrent HealthCare.gov users rather than the expected 50,000.

CMS ordered an additional $15.2 worth of cloud services from Terramark between the launch date, when most users were unable to access key portions of the site, and Nov. 30, when officials declared the site was performing at an acceptable level, according to a justification for other than full and open competition document posted on Thursday.

That contract adjustment paid for added cloud storage plus firewall upgrades, additional software and various other services.

The actual contract value only increased by about $13.9 million between those dates because CMS also docked Terremark $1.3 million for a service outage on Oct. 13, the document stated. There have been no additional imodifications to the cloud contract since November, a CMS official told Nextgov.

It’s not clear precisely when the additional funds were paid.

“CMS learned through system performance after the Oct. 1 Go Live for Open Enrollment that the Terremark cloud would not be able to handle expected traffic to the website,” the document stated. “The modifications were needed to meet the need to improve the user experience by Nov. 30, 2013.”

For each of the 12 modifications to its original Terramark contract, CMS has ordered the services directly from the cloud provider, stating it would take too long to competitively bid for the services and that could hurt health insurance seekers.

“CMS believed if the additional services were not added urgently, the exchanges would not function as designed and citizens would continue to have issues using the marketplace,” the agency said.

CMS originally ordered the services from Terramark using the General Services Administration schedule for information technology services. A GSA schedule is a slate of companies that the government has already vetted and found capable of providing certain services. 

This story has been updated to include details from CMS. 

(Image via Ricardo Reitmeyer/Shutterstock.com)

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats

JOIN THE DISCUSSION

Close [ x ] More from Nextgov
 
 

Thank you for subscribing to newsletters from Nextgov.com.
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

    View
  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

    View
  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

    View
  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

    View
  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

    View
  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.

    View

When you download a report, your information may be shared with the underwriters of that document.