Government IT to the cloud: private-sector lessons
Business' shift to public clouds can offer a path for agencies to follow
- By Glenn Weinstein
- Jan 19, 2011
With his “25-Point Implementation Plan to Reform Federal Information Technology Management,” in December 2010, federal CIO Vivek Kundra sent shock waves through the IT world by announcing a “cloud-first” policy for the federal government.
Writing in clear, non-bureaucratic prose, Kundra showed that a new era is dawning in federal government IT.
Point No. 3 of the plan, the cloud-first policy, lays down the gauntlet immediately by comparing commercial and government IT in their ability to build applications that scale quickly. Demand for the 2009 “Cash for Clunkers” program quickly exceeded expectations, leading to unplanned outages and service disruptions within three days of the program’s launch. By contrast, Kundra describes how an unnamed “Web-based multimedia production company” was able to scale a video-sharing service from 50 to 4,000 virtual machines within the same period — three days — to meet demand that was tenfold what the company had anticipated.
Kundra’s implicit taunt — “the private sector can do it, so why can’t we?” — mirrors a typical sales approach used by commercial solutions providers, comparing consumer and enterprise services. The consumer Web, illustrated by the success of Amazon, Google, Facebook, Twitter and others, has raised users’ expectations, and those same users are now increasingly expecting a similar level of integration and performance in the computing services provided to them at work. In other words, “If our kids are enjoying such a great computing experience, why shouldn’t our customers and our constituents?"
Implementing the cloud-first policy? Start with e-mail.
GSA takes the plunge, as first to move e-mail to cloud agencywide
Private-sector IT shops face many of the same cloud adoption barriers that government agencies face. Large companies are entrusted to secure data for millions of customers and have invested years in integrating systems internally and with commercial partners. System availability and performance are paramount; even a few minutes of downtime could translate to significant lost revenues or worse. In the short term, the risks of a dramatic shift in IT architecture may not seem worth the long-term benefits.
However, in the four years that Appirio has provided products and consulting services to large organizations moving to the public cloud, we have witnessed a significant shift in priorities. We encounter far less resistance from the CIOs and IT rank-and-file to the notion of migrating to cloud-based systems. Individual IT practitioners have moved from seeing cloud technology as a threat to viewing it a necessity for career progression.
Public cloud services like Salesforce.com, NetSuite, Google Apps, and Amazon Web Services are becoming ubiquitous in the Fortune 1,000 landscape. They offer a proven security model, scalability, and a mature set of technologies that the corporate world has learned it can count on for performance and uptime. Kundra’s call for the National Institute of Standards and Technology to work in 2011 to develop standards for security, interoperability and portability will allow such companies to certify their readiness to serve a greater number of business and government scenarios.
Kundra’s mandate is aggressive. His requirement for each agency CIO to designate at least three “must-move” services to migrate to the cloud mirrors the approach we’ve seen successful corporate CIOs take.
The CIO often is among the first to recognize the long-term benefits of shifting to the public cloud around economics, flexibility and speed to market. But some departmental leaders can work within bureaucratic systems that, ironically, incentivize against optimizing for long-term benefits if they involve short-term risk. By establishing a bold mandate, a CIO can give his subordinates air cover in signing up for transition plans that require moving significant data and processes away from data centers that they implement, manage and maintain.
Moving to the cloud may make for some tough early conversations but will ultimately enable government IT organizations to address problems they have been itching to solve but that have laid dormant due to lack of resources.
Another encouraging aspect of the federal plan is its emphasis on “commercial cloud technologies,” relegating “private” and “regional” clouds only to situations where commercial cloud is not feasible. This aligns with a commonly held vision that so-called private cloud computing is an evolution of virtualization technology within a company’s physical or virtual data centers but should be viewed as a steppingstone toward deployment to public (commercial) clouds.
Ultimately, the IT consumer, whether a company or a government agency, gets the full benefit of pay-per-use pricing, nearly infinite up-and-down scalability and operational expenditures by relying on fewer and larger collections of computing power, shared with very large numbers of other companies or agencies.
Cities such as Washington, D.C., and Los Angeles are proving the viability of the public cloud computing model for essential IT services such as e-mail and collaboration tools, and helping the marketplace identify and prioritize must-have features that will allow such solutions to be deployed even more widely. Between marketplace pressure and forthcoming standards from NIST, vendors will have a clear road map for delivering cloud-based solutions that can apply to the broadest possible set of government agencies.
Some have criticized Kundra’s plan for its lack of specificity. Little distinction is provided to separately consider the types of cloud solutions, categorized broadly as software as a service, platform as a service and infrastructure as a service. Flexibility is needed in any plan that is meant to provide top-level direction and apply across a disparate set of usage scenarios. Kundra has properly allowed each agency to make choices appropriate to its unique set of factors but has left no room for misunderstanding the overall mandate toward adoption of public cloud computing.
2011 should be a watershed year for public cloud computing in the government sector and for the federal government, as agencies attempt to comply with the CIO’s plan. The plan will create significant new demands, in terms of both scalability and breadth of requirements, on the existing cloud vendors, and perhaps spawn creation of new vendors. Just as the Fortune 1,000 learned valuable lessons and found opportunities from the consumer market, government agencies should consider the experience of the commercial segment in crafting their plans.