<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><StrategicPlan><Name>The Cloud Imperative: Better Collaboration, Better Service, Better Cost</Name><Description>This paper is a distillation of the SLG Cloud Commission’s efforts. It addresses cloud access and deployment challenges that are unique to states and localities — including procurement practices — and provides recommendations for surmounting barriers. In producing its recommendations, the Commission considered delivery of critical services to the public, such as healthcare, human services, and education, and discussed ways that large, complex programs can best leverage the cloud.</Description><OtherInformation>While the paper addresses technical subjects, it also covers business and policy issues for a broad audience. A document targeting only technologists would do little to move the adoption of cloud computing forward or speed the delivery of enhanced government services to constituents. Building on its knowledge of technology innovation and business process re-engineering, the Commission seeks to establish a widely shared communication process that draws all state and local stakeholders into a common cloud computing vision: better collaboration within and between government agencies; better service to government employees, to the public and to citizens; and all delivered at a better cost to taxpayers.</OtherInformation><StrategicPlanCore><Organization><Name>State &amp; Local Government Cloud Commission (SLG-CC)</Name><Acronym>SLG-CC</Acronym><Identifier>_0b6b50c0-641d-11e1-8d3e-5a117a64ea2a</Identifier><Description>... in September 2011 the TechAmerica Foundationformed a group of experts to develop guidance for helpingstate and local governments evaluate, adopt and implementcloud computing. This State and Local Government CloudCommission (SLG-CC) initiative follows the Foundation’searlier release of a blueprint for the U.S. federal government’sadoption of cloud computing, which supported the ObamaAdministration’s cloud-first strategy for government technologyand for driving U.S. commercial leadership and innovation.</Description><Stakeholder><Name>TechAmerica Foundation</Name><Description/></Stakeholder><Stakeholder><Name>Tarkan Maner</Name><Description>SLG-CC Chair. Wyse Technology, Inc.</Description></Stakeholder><Stakeholder><Name>Daniel Kent</Name><Description>SLG-CC  Vice-Chair, Cisco Systems, Inc.</Description></Stakeholder><Stakeholder><Name>David L. Cohn</Name><Description>SLG-CC Vice-Chair, IBM</Description></Stakeholder><Stakeholder><Name>Jennifer Kerber</Name><Description>President, TechAmerica Foundation</Description></Stakeholder><Stakeholder><Name>State Governments</Name><Description/></Stakeholder><Stakeholder><Name>Local Governments</Name><Description/></Stakeholder></Organization><Vision><Description>Better Collaboration, Better Service, Better Cost</Description><Identifier>_0b6b5322-641d-11e1-8d3e-5a117a64ea2a</Identifier></Vision><Mission><Description>To develop guidance for helping state and local governments evaluate, adopt and implement cloud computing.</Description><Identifier>_0b6b5408-641d-11e1-8d3e-5a117a64ea2a</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Understanding</Name><Description>Understanding Cloud Technology</Description><Identifier>_0b6b54c6-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/><Objective><Name>Selection</Name><Description>Picking the Right Cloud Solution</Description><Identifier>_0b6b557a-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Physical Layer</Name><Description>Physical Layer Considerations</Description><Identifier>_0b6b5624-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Abstraction Layer</Name><Description>Abstraction Layer Considerations</Description><Identifier>_0b6b56e2-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Service Models</Name><Description>Service Models</Description><Identifier>_0b6b5796-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.1.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Service Layer</Name><Description>Service Layer</Description><Identifier>_0b6b585e-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.1.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Technology</Name><Description>Key Technology Issues</Description><Identifier>_0b6b5926-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Portability</Name><Description>Portability</Description><Identifier>_0b6b5a02-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Security and Privacy</Name><Description>Security and Privacy</Description><Identifier>_0b6b5ad4-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Data Protection</Name><Description>Data Protection</Description><Identifier>_0b6b5bb0-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2.2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Identity Management</Name><Description>Identity Management</Description><Identifier>_0b6b5c8c-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2.2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Incident Response</Name><Description>Security Incident Response Vulnerability and Risk Management</Description><Identifier>_0b6b5d68-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2.2.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Vulnerability and Risk</Name><Description>Vulnerability and Risk Management</Description><Identifier>_0b6b5e4e-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>1.2.2.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Implementation</Name><Description>Implementing the Cloud</Description><Identifier>_0b6b5f3e-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/><Objective><Name>Readiness Assessment</Name><Description>Cloud Readiness Assessment</Description><Identifier>_0b6b602e-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Risk Management and Governance</Name><Description>Risk Management and Governance</Description><Identifier>_0b6b61fa-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Best Practices</Name><Description>Implementation Best Practices</Description><Identifier>_0b6b62fe-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Preparation and Planning</Name><Description>Preparing and Planning</Description><Identifier>_0b6b6470-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Implementation and Deployment</Name><Description>Implementation and Deployment</Description><Identifier>_0b6b657e-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Program and Project Management</Name><Description>Program and Project Management</Description><Identifier>_0b6b66fa-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Culture Change</Name><Description>Managing Culture Change</Description><Identifier>_0b6b6812-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Process Transformation</Name><Description>Managing Process Transformation</Description><Identifier>_0b6b6934-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Operations</Name><Description>Operations</Description><Identifier>_0b6b6a60-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>2.3.6</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Acquisition</Name><Description>Acquiring the Cloud</Description><Identifier>_0b6b6b96-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/><Objective><Name>Procurement Vehicles</Name><Description>Selecting Procurement Vehicles</Description><Identifier>_0b6b6cc2-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Deployment</Name><Description>Deployment Model Considerations</Description><Identifier>_0b6b6df8-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Architecture Design</Name><Description>Architecture Design Considerations</Description><Identifier>_0b6b6f38-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Contracts</Name><Description>Key Contractual Terms</Description><Identifier>_0b6b7082-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>3.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Funding</Name><Description>Funding Streams</Description><Identifier>_0b6b71cc-641d-11e1-8d3e-5a117a64ea2a</Identifier><SequenceIndicator>3.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2012-03-01</PublicationDate><Source>http://www.techamerica.org/Docs/fileManager.cfm?f=taf_slg_cc.pdf</Source><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>
