Posted on 10/24/2013 8:36:11 AM PDT by SeekAndFind
Yesterday, the contractors who contributed to the Healthcare.gov fiasco testified before the House Energy and Commerce Committee, which has begun a probe into how $400 million and a 42-month lead time produced an embarrassing failure for Health and Human Services. They made it clear where the blame lies for the failure, claiming that their pieces of the project won approval and worked when they turned them over to CMS. Either the problems are the other contractors in the room, or more likely CMS and HHS:
Principal contractors hired to build the ObamaCare website HealthCare.gov are hitting back at the Obama administration for the site’s overwhelming technical problems.
Executives from CGI Federal and QSSI—the site’s main contractors—are among four companies testifying before the House Energy and Commerce Committee Thursday on the glitches.
The Department of Health and Human Services (HHS) “serves the important role of systems integrator or `quarterback’ on this project and is the ultimate responsible party for the end-to-end performance,” CGI’s Senior Vice President Cheryl Campbell said in prepared testimony, according to the Associated Press.
“No amount of testing within reasonable time limits can adequately replicate a live environment of this nature,” she added.
Campbell went on to blame “another contractor” for the issues of account creation, the New York Times reports:
She blamed “another contractor” for problems that consumers have had creating secure password-protected accounts. She did not name the company, but government records show it is Quality Software Services Inc., a unit of the UnitedHealth Group, one of the nation’s largest insurers.
These problems “created a bottleneck that prevented the vast majority of users” from gaining access to the federal exchange, Ms. Campbell said.
Quality Software Services executive Andrew Slavitt told the House committee that they did the proper testing, identified a number of problems — and gave the information back to CMS:
Andrew M. Slavitt, the UnitedHealth executive responsible for Quality Software Services, said its identity verification tool was just one part of “the federal marketplace’s registration and access management system, which involves multiple vendors and pieces of technology.”
These were overwhelmed by people trying to use the site, Mr. Slavitt said. One reason for the logjam, he suggested, is that the administration made “a late decision requiring consumers to register for an account before they could browse for insurance products.”
Mr. Slavitt said that Quality Software Services was one of several companies that tested the federal marketplace before it opened.
“In our role as tester,” he said, “we were tasked with identifying errors in code that was provided to us by others.” The results were reported back to the Centers for Medicare and Medicaid Services and the relevant contractor, “who in turn was responsible for fixing coding errors or making any necessary changes,” he said.
The front-end problems are masking the back-end problems, too. Thanks to the logjam in account creation, the contractor responsible for dealing with paper applications has seen an unexpected boost in demand. The problem is that the contractor, Serco, has to use the same back-end system as Healthcare.gov to register those applicants — and that doesn’t work, either.
Energy and Commerce will start calling Obama administration officials to testify next week, Bloomberg notes in their preview of today’s continuing testimony. Republicans want to get enough on the record now for that interrogation, hoping to force HHS and CMS officials into providing real answers to account for the disaster:
Maybe they should keep this point from the NYT in mind, though:
The same contractors, testifying before the same committee on Sept. 10, assured lawmakers that they were ready to handle a surge of users when the federal exchange opened on Oct. 1.
Perhaps the ECC will remind them of that today.
This could get interesting, if our quisling Congress would do something about it.
Will they do anything....no. they are all cowards!
Full blown Cluster-F***
The head honcho at CMS testifying today is an affirmative action hire. This could possibly be a recurrent thread in the tangled debris of ObamaCare. Were any of these people qualified to be in charge of 19% of the U.S. economy? They certainly can’t answer any questions pertaining to this monstrous project.
“Thanks to the logjam in account creation, the contractor responsible for dealing with paper applications has seen an unexpected boost in demand. The problem is that the contractor, Serco, has to use the same back-end system as Healthcare.gov to register those applicants — and that doesn’t work, either.”
He said he has two states that are not operational yet.
Why not???
Having spent years in the Air Force dealing with contracts and contractors (on both sides)....I can say that the minute you split up a contractor and have more than one company providing the work for the tasks....it’s 99-percent or better that things will be screwed up unless the gov’t guy stands there and jerks everyone’s chains on a hourly basis. That’s the only way it works. I’d strongly suggest that one contract is for one company only, it lessens the pain involved.
ooooohhhh.... that’s one thing, as a government contractor, you DON’T do.
No, you’re not expected to succeed, but you’re definitely not allowed to blame the gov’t for it.
LOVE THIS!!! loving this. Extra large slice of Schadenfreude cream pie!!
The IRS is going to be occupied auditing the tax records of about 40 contractors, and their management.
MacAfee says it is unfixable. Throw it out and start over. Obama and friends should go to prison.
Were these no-bid contracts?
yes - a 22k campaign donation netted a $200 million no-bid contract.
Sweet ROI, don’t ya think?
There are concepts like "PRIME contractor" and
Project Management with deliverable "Milestones"
From the Book : The MYTHICAL MAN-MONTH
“adding manpower to a late software project makes it later”.
This idea is known as Brooks’ law, and is presented along with the second-system effect and advocacy of prototyping.
Brooks’ observations are based on his experiences at IBM while managing the development of OS/360. He had added more programmers to a project falling behind schedule, a decision that he would later conclude had, counter-intuitively, delayed the project even further. He also made the mistake of asserting that one project — writing an ALGOL compiler — would require six months, regardless of the number of workers involved (it required longer). The tendency for managers to repeat such errors in project development led Brooks to quip that his book is called “The Bible of Software Engineering”, because “everybody quotes it, some people read it, and a few people go by it.”
The book is widely regarded as a classic on the human elements of software engineering. People clearly have not learned from history.
The corollary of Brooks’s Law is that there is an incremental person who, when added to a project, makes it take more, not less time. Brooks adds that “Nine women can’t make a baby in one month”.
Absolute "Affirmative Action" Idiot speak !
geez, I thought only the evil Halliburton got those.
“One reason for the logjam, he suggested, is that the administration made “a late decision requiring consumers to register for an account before they could browse for insurance products.””
Now.... why would they do that ?
How about SIGNING UP ONE TEST USER TO SEE IF IT WILL WORK?
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.