When the “Federal Agency” has successfully migrated to the cloud, differences may exist in the relationship between the “Federal Agency” and the CSP, which will require adopting new governance processes. The “Federal Agency” will need to ensure it can effectively manage SLAs based on the metrics defined previously as part of cloud service selection activity. “SLAs should clearly define how performance is guaranteed (such as response time resolution/mitigation time, availability, etc.) and require CSPs to monitor their service levels, provide timely notification of a failure to meet the SLAs, and evidence that problems have been resolved or mitigated” [21].
SLA monitoring will also require the “Federal Agency” to actively evaluate the met-rics to ensure they are enforced and usage charges are accurate. Since portability, interoperability, and security are key requirements for cloud service selection, the
“Federal Agency” can periodically re-evaluate the market to identify opportunities that maximize capabilities offered by changes in technologies, new cloud services, and private-sector innovations.
SUMMARY
In this chapter a brief overview of the Cloud Strategy was presented to highlight the key drivers for the federal government’s adoption of cloud computing. In addi-tion, the introduction provides CSPs with a basic understanding of how the strat-egy may be used by federal agencies considering cloud services as an extension of their IT portfolio. We briefly reviewed the history of federal IT with the purpose of understanding the potential challenges that may be a force behind the cloud adoption. We also discussed the key drivers for federal IT transformation and the expected benefits received through cloud computing. Lastly, a brief examination of the three-step decision framework offered insight into its application for cloud migration.
References
[1] Kundra V. Federal cloud computing strategy. Washington, DC: Executive Office of the President, Office of Management and Budget; 2011.
[2] US Congress, Office of Technology Assessment (OTA). Federal government information technology: management, security, and congressional oversight. Washington: US Government Printing Office; 1986.
29 References
[3] Paperwork Reduction Act [Internet]. Washington: US National Archives and Records Administration [cited July 7, 2012]. <http://www.archives.gov/federal-register/laws/
paperwork-reduction/3504.html>.
[4] Melvin V. Federal chief information officers: opportunities exist to improve role in information technology management. Washington: US Government Accountability Office; 2011.
[5] Comptroller General of the United States. Acquisition and use of software products for automated data processing systems in the federal government. Washington: US General Accounting Office; 1971.
[6] Staats EB. Uses of minicomputers in the federal government: trends, benefits, and problems. Washington: US General Accounting Office; 1976.
[7] Finch JC. Use of Minicomputers for Internal Revenue Service Tax Return Preparation.
Washington: US General Accounting Office; 1978.
[8] Comptroller General of the United States. Problems found with government acquisition and use of computers from November 1965 to December 1976. Washington: US General Accounting Office; 1977.
[9] Seifert J. Government information technology management: past and future issues (The Clinger-Cohen Act). Washington, DC: The Library of Congress, Congressional Research Service (CRS) Office; 2002.
[10] McClure D. Statement of Dr. David McClure, Associate Administrator, Office of Citizen Services and Innovative Technologies, US General Services Administration, Before the House Science, Space and Technology Committee, Subcommittee on Technology and Innovation. Washington: US House of Representatives; 2011.
[11] Office of Management and Budget (OMB). White House forum on modernizing government: overview and next steps. Washington, DC: Executive Office of the President, Office of Management and Budget; 2010.
[12] Daniels ME. Office of Management and Budget (OMB) Memorandum 02-08, Redundant Information Systems Relating to On-Line Rulemaking Initiative. Washington, DC:
Executive Office of the President, Office of Management and Budget; 2002.
[13] Katz GD, Rhodes KA. DOD business systems modernization: billions continue to be invested with inadequate management oversight and accountability. Washington: US General Accounting Office; 2004.
[14] Dodaro GL. Opportunities to Reduce Potential Duplication in Government programs, Save Tax Dollars, and Enhance Revenue. Washington: US Government Accountability Office; 2011.
[15] Federal Data Center Consolidation Initiative (FDCCI). Workshop III: Final data center consolidation plan [Internet]. Washington: US General Services Administration [cited July 18, 2011]. <http://www.cio.gov/documents/FDCCI%20Workshop%20III%20%20 Aug%2010th%20010.pdf13>.
[16] White House. White House forum on modernizing government: overview and next steps.
Washington, DC: Executive Office of the President, Office of Management and Budget;
2010.
[17] Brock JL. Information Technology: A Statistical Study of Acquisition Time. Washington:
US General Accounting Office; 1995.
[18] McClure DL. Leadership Needed to Confront Serious Challenges and Emerging Issues.
Washington: US General Accounting Office; 2000.
30 CHAPTER 1 Introduction to the Federal Cloud Computing Strategy
[19] Kundra V. 25 Point implementation plan to reform federal information technology management. Washington, DC: Executive Office of the President, Office of Management and Budget; 2010.
[20] Jansen W, Grance T. NIST Special Publication (SP) 800-144, guidelines on security and privacy in public cloud computing. Maryland: National Institute of Standards and Technology; 2011.
[21] Federal CIO Council and Chief Acquisition Officers Council. Creating effective cloud computing contracts for the federal government. Washington, DC: Executive Office of the President, Office of Management and Budget; 2012.
Federal Cloud Computing.
© 2013 Elsevier, Inc. All rights reserved.
http://dx.doi.org/10.1016/B978-1-59-749737-4.00002-2 31
INFORMATION IN THIS CHAPTER:
• Introduction
• Standards Development Primer
• Cloud Computing Standardization Drivers
• Identifying Standards for Federal Cloud Computing Adoption
INTRODUCTION
Standardization can be characterized as the process by which new standards are developed or new products are brought to market implementing standards. A stan-dard (or technical stanstan-dard) can be classified differently and published by many dif-ferent organizations. In Table 2.1 the generally accepted definitions are provided for what constitutes a standard for use by the US government.
Standards play a critical role for cloud adoption, both by the federal government1 and the private sector. As we will discuss later in this chapter, the federal government has a unique responsibility to ensure voluntary consensus standards are adopted in lieu of government-unique standards.
The Federal Cloud Computing Strategy identified the importance of standards development to ensure the federal government’s adoption and effective use of cloud computing and related technologies is supported by broad standardization. For fed-eral agencies to leverage the capabilities and achieve the benefits offered by cloud computing, as described Chapter 1, the development of standards will need to focus
1From Kundra, V. Federal Cloud Computing Strategy. Washington: Executive Office of the President, Office of Management and Budget; 2011. “Standards encourage competition by making applications portable across providers, allowing Federal agencies to shift services between providers to take advan-tage of cost efficiency improvements or innovative new product functionality.”