John Engates went to the White House Monday to get a better examine what went wrong with HealthCare.gov. Unlike actor Jimmy Stewart’s Mr. Smith, Engates came far from Washington saying this problem may be fixed.
Rackspace CTO John Engates went to the White House Monday to get a more in-depth look into what went wrong with HealthCare.gov. What he saw convinced him that giant Government doesn’t operate the way in which enterprises do — and perhaps it’s going to.
Engates was among the few technology industry spokespersons to leap forward when the talk over HealthCare.gov broke out. He was quoted, among other places, on front page of USA Today, commenting that the location appeared to not have government repositories that may stay alongside of its needs.
Engates doesn’t fit the stereotype of a business-oriented government critic. “i used to be very proud and excited to be invited,” he said in an interview after returning to his home base in San Antonio, Texas. Concurrently, he hasn’t hesitated to explain the launch of the administration’s public enrollment website as “one of the vital spectacular public failures ever.”
While Engates has a lot of criticism for HealthCare.gov’s troubled start, the visit to Washington bolstered his confidence that the positioning is now on the right track. Indeed, the brand new Healthcare.gov project lead Jeffrey Zients to inform the clicking six days after Engate’s visit that the site’s error rate in loading pages is down from 6% to only 1%. It’s also now ready to serve 50,000 people at a time and takes one second (in comparison to eight) to load most pages.
With coverage under Obamacare scheduled to start in 30 days, however, these fixes is probably not enough. In keeping with Engates, a more persistent problem than response time involves connecting new healthcare signees to their policies at specific providers. A fix remains to be within the works.
Only a handful of executives joined Engates on his visit, including representatives from Salesforce.com, Exact Target (a contemporary Salesforce.com acquisition), and IBM. The gang included a minimum of one friend of the administration; when President Obama visited San Francisco on a fundraising tour, one in every of his stops was on the residence of Salesforce.com CEO Marc Benioff.
[Desire to learn more about how the govt. buys IT? Read Will HealthCare.gov Mess Spur Procurement Reform?]
In addition to meeting with Zients, the crowd met with federal government CTO Todd Park, federal government CIO Steven VanRoekel, and White House chief of staff Denis McDonough. After an hour-long briefing within the White House situation room, the crowd was taken to the Maryland offices of QSSI, the contractor that was hired to tug together the site’s disparate elements. There, Engates said, he saw “an exchange operations center where all reactions to the crisis could be orchestrated.”
For something, he explained, there is a “quarterback” liable who could make decisions over the subcontractors considering the location, each of whom has a representative within the operations center 24 hours an afternoon. “Before, you had people working nine to 5, five days every week — in the event you were lucky,” Engates noted. “Now they’re working 16 to 17 hours an afternoon, with the heart fully staffed seven days every week.”
“They’ve standup meetings twice an afternoon,” Engates continued, through which participants report on anything that goes wrong. “Within the government contracting system, people weren’t in one room [just like the operations center]. Nobody was willing to ring the alarm bell.”
Engates discussed with VanRoekel how private business keeps contractors honest. “The bidders with your entire right characters get the contracts, but they don’t seem to be the easiest ones for the job… He was inquisitive about reforming that,” said Engates.
Government officials were straightforward about what had gone wrong with the positioning, and Engates even made a tenet or two of his own on the way to improve it. “Don’t log in and update servers one after the other,” he advised. Rather, he recommended pushing updates into production using a blueprint updating large groups of servers, the best way Rackspace Cloud and other large scale vendors do. Likewise, he also suggested monitoring more things relating to the application’s performance and taking action earlier when monitoring shows completed actions heading south.
Unlike Jimmy Stewart’s Mr. Smith, Engates believes not just that the issues is also corrected, but that the govt is already halfway down that path. “Additionally it is fixable. The accountability and intensity have changed from what they were before the launch,” he said. Previously, contractors didn’t appear to see how their work might appear within the public eye. Now they know they’re under scrutiny and every piece of labor is necessary.
The crucible of cloud, big data, and distributed computing is hell on systems. Will application performance management settle down complexity — or simply add fuel to the fireplace? Also within the new, all-digital APM Under Fire special issue of InformationWeek:Cloud industry heavyweights discuss the professionals and cons of OpenStack support for Amazon APIs. (Free registration required.)
More Insights