NCOIC Geospatial Interoperability Task Team

1. NCOIC Geospatial Interoperability Task Team Kevin L. Jackson Chairman, NCOIC Cloud Computing Working Group April 12, 2011 Approved for Public Release Distribution Unlimited NCOIC GITT20110412

2. NCOIC, A Global Industry Consortium Industry working together with our customers to provide a network centric environment to facilitate the global realization of Network Centric Operations • Focused solely on network centric • A global perspective to facilitate NCO adoption • An industry neutral perspective to facilitate NCO adoption • An industry, government and academic cadre of expertise • US DoD Official

3. Net Enabled Emergency Response Aviation Network Sense & Respond Logistics One-to-Many NCOIC™ Network Centric Patterns (NCP): Analyze Missions A Global-Scale Ecosystem… • Engineering guidance for development of • a Network Centric Architecture and enabling • existing architectures and networked systems • Capability and Technical NCP describe how to enable • specific network centric capabilities and how to mitigate • interoperability problems. • Operational NCPs describes how organizations can enable • networked operational capabilities through descriptions of • collaborative scenarios and business processes Maritime C3 Cyber Security Specialized Frameworks Defining and Assessing Netcentric Capability Working Groups: Mobile Networks, Ground Systems, Semantic Interoperability Framework, Information Assurance, Services, Cloud Computing & Open StandardsAreas of Responsibility: Frameworks, patterns/PFCs, standards and design guidance Charter: To host and encourage the development, approval, and publication of specialized Frameworks and Patterns that contain guidelines and standards recommendations for the broad range of domains.

4. NCOIC Cloud Computing Working Group Charter • 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 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.

5. Operational Flow Cloud Computing Value Document and Validate Key capabilities and standards Evangelize and Iterate

6. NCOIC Lab Interoperability Project Group Chair: Karen Mowrey, Boeing NCOIC Plenary Meeting Falls Church, VA Sept. 27 – Oct.1, 2010 Approved for Public Release Distribution Unlimited NCOIC-Lab Interop Press 20100923

7. Purpose • Reduce expense, time, and risk associated with integrating labs • Modeling & simulation capabilities to be tested in a joint environment • An environment that supports more dynamic and broader scope testing • Commercial customers and NGOs require test before buy Industry Solution: An infrastructure approach will enable “Interoperability”

8. Interoperability Matrix Description Technology Level Processes 4 Applications Hosted in Environment 3 Core Middleware Support for LVC environment 2 Focus on Levels 1-3 Convergence of Visualization and Presentation Capability 1 Communication Interoperability and Information Assurance • Deliverables: • Three global demonstrations showing interoperability at the infrastructure level • A technical framework that documents the technical configuration, protocols and standards used • Next Steps: • Work with NCOIC Technical Council on developing patterns and best practices to be made available to all

9. Phase 1: Network and Presentation Layer Interoperability Demo: Rome, Italy -- March 2010 4 EUROPEAN SITES Finmeccanica: Genova, Italy(Lab Presenter, DIS, VTC) Thales: Colombes, France(Lab Presenter, DIS, VTC) EADS: Elancourt, France (Lab Presenter, DIS, VTC) Cisco Systems: Europe(Networking H/W back-up) Rome, Italy(NNEC – Audience Location) 6 U.S. SITES Lockheed Martin: Suffolk, VA (Lab Presenter, DIS, VTC) Raytheon: Suffolk, VA (Lab Presenter, VTC)  IBM: Bethesda, MD(Lab Presenter, VTC) Boeing: Seattle, WA (NOC – LabNet Ops) Boeing: Anaheim, CA(BIC – COP, DIS, DMS Recording, Lab Presenter) Boeing: Arlington, VA(Event Control, MCU)

10. Phase 2: Brussels NCOIC Middleware Interoperability Demo NCOIC Plenary Session Brussels, Belgium Networking hardware in Europe provided by CISCO

11. Cloud Computing Experiments NCOIC Plenary Session Brussels, Belgium Cloud Experiments • #1 Physical Servers running Data Interoperability Middleware were migrated to Virtual Servers in the Cloud • #2 Network Management capabilities delivered as a Cloud Service

12. Summary • Using the lab interoperability technical framework reduces expense, time, and risk • Saves companies approximately $200K per event • Reduces time-to-event execution by two thirds • Reduces risk of event failure • Cloud computing technology can help to further reduce lab integration time

13. NGA Request NCOIC was asked to submit a formal proposal to the National Geospatial-Intelligence Agency to design, build and present a demonstration on how cloud computing technologies and/or techniques could be used to enhance interoperability between geospatial information systems Leverage processes and lessons learned from lab interoperability experiment The demonstration must address the following: How does the geospatial community leverage industry best practices to globally provide access to electronic geospatial data and services How can digital geospatial data be protected from unauthorized use while maintaining the ability of each participating data provider to manage the data that they provide? How can the community maintain geospatial data consistency and interoperability while maintaining application backward compatibility through as many as three versions? How can electronic data mobility capable of supporting operational collaboration across the geospatial community be assured?

14. NCOIC Member Participation • Three areas of work under consideration • Development of the concepts • Demonstration of the concepts • Evaluation of the results. • Recommendations for detailed activities is being solicited from members • One submission per NCOIC member • Recommendation Format • Work Area(s) of interest • Recommended activities for each work area of interest • FTE Estimate for each recommended activity • Other cost (if any) for each recommended activity • Due November 10, 2010 • Consolidate recommendations into proposal draft • Distribute for comments (11/17/10 target) • Finalize and submit (12/1/10 target)

15. NCOIC Members who submitted input • Boeing • Cisco • Deloitte • EADS • Finmeccanica • GBL Systems • Harris • IBM • Lockheed Martin • Luciad • Microsoft • MilSoft ICT • Mosaic ATM • OGC • Raytheon • The Aerospace Corporation

16. GITT Proposal • Cycle 1: Basic cloud infrastructure and connectivity services. • Cycle 2 & 3: Additional Cloud Functionality and Analysis. • Each cycle will include three phases: • Development of the concepts to be employed and hypotheses to be tested • Demonstration of the capabilities and supporting • Reporting on the results. functionalities.

17. Cloud (Connected Member Company Nodes) Provisioning engine Core Node Environment Self Service Portal Cloud User Approver Cloud Administrator Server, Network, Storage, Middleware and Application Resources STANDARDIZATION Service Catalog VIRTUALIZATION AUTOMATION

18. Four User Roles Based on a “Team” concept. The OGC Node will support multiple teams. Teams have Users and an Administrator. The Cloud has Managers and Administrators. Team User • View projects available to the team • Check status of servers provisioned for their team • Log in and use provisioned servers and applications Team Administrator • Create/modify team user accounts • Request new servers for their team • Check status of existing requests and servers • Change server status and password • Log in and use provisioned servers and applications Cloud Manager • Check the status of projects and monitor the servers of any team Cloud Administrator • Define new teams, user accounts and roles • Register and unregister software images (templates) • Approve resource allocations and changes • Approve Team Administrator requests

19. Base Cloud Capabilities • Add and delete users and teams • Create projects and virtual machines with resources such as OS, CPU, memory, disk space • Show available, standardized, reusable images for rapid and reliable provisioning (via catalog) • Monitor requests status (requested, approved, being provisioned) • Monitor server status (use of resources) • Scale server resources to meet new workload requirements (such as CPU, memory,…, or duration time for which the server is needed) • De-provision unused capacity and compute power • Remote Control features (allowing power on, power off, restart, reset password, and backup of a virtual machine)

20. Current Status • Formal proposal submitted and accepted • Funding available, contracting vehicle in work • GITT Task Team 1 (Core Node) formed. Task proposal under development

21. Questions??? Net-EnabledFuture Stovepiped Systems, Point-to-Point Networks 21