1. Cloud Computing Capability Patterns NCOIC Briefing to DISA 11 January 2010 Approved for Public Release Distribution Unlimited NCOIC-CC CapabPattsDISA – KJ20100111

2. The NCOIC

3. What is the problem we’re trying to solve?

4. Value for DISA

5. Pattern Categories

6. Capability Patterns

7. 7 NCOIC Cloud Computing Working Group Charter Collaboration & engagement with other Cloud groups to look at standards-based solutions Government, standard bodies, vendors, NCOIC member companies Peer-to-peer interoperability, improved usability/ trust of the cloud, and portability across clouds.  Document best practices, architectures and blue prints for commercially- available implementations, including examining security implications and how to implement an internal cloud. –“In-Field”, Edge, and Enterprise Clouds –Layered Quality of Service for Cloud Computing –“Infrastructure cloud" standards to develop consensus across vendors to reduce lock-in to a given vendor or platform. –Develop Net-Centric Patterns on well developed instances –Focused on solving business/operational needs  Interactions and effects with other NCOIC teams and Deliverables –NIF, Specialized Frameworks, SCOPE Model, NCAT, Building Blocks etc., –Updates to the NCOIC Lexicon to add our Cloud Computing taxonomy

8. The Way Forward rev date 9/5/2015 slide 8 Cloud Computing Value Document and Validate Key capabilities and standards Evangelize and Iterate Our Goal: Close collaboration with DISA on the development of Cloud Computing capability patterns !

9. 9 What is the SCOPE Model?  Systems, Capabilities, Operations, Programs, and Enterprises (SCOPE) Model  SCOPE gives customers and companies the means to characterize interoperability requirements for network centric systems –How isolated or connected are the systems to each other? –How isolated or connected are the systems to their environment? –What are the intended purposes of the connection between systems? –What portion of operational space do the systems address?

10. 10 The Role and Value of the SCOPE Model Enterprise Models Specific Node Architectures High Level Models On-time Cargo Delivery Models of Customer Objectives Domain General Architectures Architecture A Tailored QoS Capability Scope Security Net Awareness Service Orientation Autonomy Transfer Rate Cost The SCOPE Model measures RANGES of a domain’s needs and capabilities in many dimensions that relate to interoperability (Illustrative of a greatly simplified SCOPE analysis; the actual SCOPE Model and associated tools cover many dimensions in more depth)

11. 11 The Role and Value of the SCOPE Model Specific Node Architectures High Level Models On-time Cargo Delivery Domain General Architectures Architecture A Tailored QoS Capability Scope Security Net Awareness Service Orientation Autonomy Transfer Rate Cost The SCOPE Model measures needs of each domain in many dimensions… … and each domain often has different needs, characterized via the SCOPE Model Fuel Efficient Operations Architecture B Tailored Enterprise Models Models of Customer Objectives ? Interoperable?

12. Program X Capability Scope Dimension Example Overall Scope and Types of Enterprise Single Facility/NodeSingle Division or Agency Nation-WideWorld-Wide Capability Breadth Represented Single Functional Domain Multi-DomainMulti-Dept, NGO, Industry Coalition, Multi- Enterprise Types Capability Levels of Granularity Single Granularity Level Two Levels – eg, buildings & rooms Three LevelsFour or More Levels Organizational Model and Culture Rigid Hierarchy, Vertically Integrated Adaptive Hierarchy, Interact Horizontally Flat, Empowered, Open to Partnering Adaptive, Social, Interdependent Unity of Life Cycle Control/Alignment Single Acquisition Exec Multiple Acquisition Execs Government and Commercial Owners Multi-National System Owners Acquisition Congruence (SD) All Systems on Same Timeline Timeline within 2 years Timeline within 5 years Timelines >5 years apart Semantic Interoperability Single Domain Vocabulary Multi-Domain Vocabulary Single LanguageMultiple Languages Operational Context (SD) Single Ops ContextMultiple Ops Contexts Future/Past Integration Hypothetical Entities Value Dimension Narrower Scope Broader Scope

13. Possible Cloud Computing SCOPE Dimensions  Degree of coupling between operational responsibility and execution resource ownership for –Network resources –Computing platform resources (incl plant, power, etc.) –Data resources – including controlled/licensed data –Service resources – for proprietary IP or bundled platform/data  Business model types connecting consumer with cloud provider –Relationship management, consequence management  Dynamic range of cloud services (mainly scalability)  Network infrastructure capacity between cloud provider and consumer  Execution platform types provided by the cloud  Degree of domain-specificity of cloud-based services offered  Others?

14. Value Dimension Tighter Coupling / Less Net-Readiness Looser Coupling / More Net-Readiness Net Ready Dimensions and Levels Service Discovery Service specs pub at design Service specs pub run-time OWL spec for Services Comparative service select Information Discovery Static IndexesMetadata Navigation Relevance Measures Context-driven Search Info Model Pre- Agreement Complex data & doctrine Standard XML Schemas Business Object ASCII, URLs Information Assurance Link encrypt - SSL Single sign-on support Agency-Wide PKI support MSL, cross- domain spprt Autonomic Networking Design Time Configuration Run Time Re- Configuration Dynamic Net Management Adaptive Net Management Semantic Interoperability No Explicit Semantics Semantic Metadata for Interfaces Ontology- based interfaces Dynamic Ontology mapping

15. Technical Feasibility Dimensions Inter-System Time Binding to Achieve Capability StrategicTacticalTransactionalReal Time Run-Time Computing Resources Needed <1% of existing system resources 1-10%10-50%>50% of existing system resources Service Mgmt. Resources Needed NegligibleWithin Current Net Service Capacity Within Planned Net Service Capacity Beyond Planned Net Service Capacity Net Resources Needed (FD) NegligibleWithin Current Net Capacity Within Planned Net Capacity Beyond Planned Net Capacity Interface Development Complexity <1% of system size 1-10%10-50%>50% of system size Technology Readiness Level For Net Use TRL Levels 8-9TRL Levels 6-7TRL Levels 4-5TRL Levels 1-3 Value Dimension Smaller Risk Larger Risk

16. The use of cloud computing technology and techniques to support localized, short-lived information access and processing. Use cases could include: –“Cloudbursting” to support cyclic data processing requirements –Establishing a cloud-based collaboration environment in order to coordinate firefighting resources during a wildfire –Virtually binding shipboard IT infrastructures in order to create a battlegroup infrastructure-as-a-service platform –Virtually binding land vehicle based servers and storage resources into a battlefield data center –Dynamic provisioning of virtual cloud-based servers in order to automate exploitation and dissemination of unmanned air vehicle (UAV) streaming video feeds Focus Area: Tactical Cloud Computing rev date 9/5/2015

17. 17 Example: Hybrid Cloud Computing  Abstract: The Hybrid Cloud Computing (HCC) capability pattern provides a practical, pragmatic guide for development of cloud computing capability focused on interoperability and design for affordability. This capability pattern seeks to balance the cost, speed, and agility afforded cloud computing consumers with the required security, privacy and confidentiality.  Goal: Make Government more agile and adaptive with a focus on collaboration, openness and transparency Service Oriented Government Powered by Cloud Computing  NCOIC Hybrid Cloud Computing Pattern = Service Oriented Government Powered by Cloud Computing –Leverage net-centric thinking to power Government transformation

18. 18 Evolving Design Pattern  Maintain security and control of personal identifiable information on premise (I.e., from personal identity theft).  Obtain agility and cost benefits from public cloud  Develop cloud bursting capability to right sized private cloud  Extend to mobile devices Source: Lockheed Martin Cloud Computing Research Investigation Public Cloud On Premise Environment Data Browser Applications Mobile Devices Private Cloud

19. 19 Net-Enabled Future Stovepiped Systems, Point-to-Point Networks Questions???