DoD Transformation and The Global Information Grid

Transcription

1 DoD Transformation and The Global Information Grid Implications for GIS of Emerging Net-Centric Warfare Operational Concepts Mr. Rob Walker 9 July 2003

2 Net-centric Challenge & Payoff Net-centric Operations Transformational t e n rt le m a te en 6l.eT heem e8 4 4TePl A BR 4 z M A M BT 8 GH.4 RP l 7 GHz 169 e / 2 0 Capability Data System 70 s Family of Systems Global Information Grid tenrt h emame e n t l. T le 6 1 e5 6 e e l ebr z M A 8 GH T PA 4 RP M BT l. 7 GHz 1 69 e / 2 0 System of Systems 90 s 80 s Scale Significant 2

3 The Key Components of Net-Centric GIG Infrastructure Foundation Communications Computing Applications Data Management Provides an approach to manage, operate, and change the culture Provides a comprehensive terrestrial and space network Provides services to exploit the network and support applications Provides tools needed for a capabilities based force Ensures all data is discoverable and understandable Information Assurance Protects the data and the network The Enterprise Infrastructure is Greater Than the Sum of the Components 3

4 Today s Operational Environment White House Pentagon CINC HQs Coalition JTF Headquarters Some Networks, point-to-point & peer-to-peer JTF Components Networks Systems & Data Too many stovepipes Limited interoperability JTF Environment Varying missions & locales Varying force sizes/types Varying JTFs & coalitions Varying comms & equipment Varying information needs 4

5 Tomorrow s Operational Environment The DISA Transformation Vision White House Pentagon Sensor-to-shooter CINC HQs JTF Headquarters Secure Interconnected Nodal Network JTF Components Coalition Common Enterprise Services Worknets Capabilities & Relationships Power to the Edge! Transforming Technologies & Concepts Ubiquitous, secure & robust network Deploy collaborative capabilities Populate network with all data Continuously refresh content Secure & assure the network & info Data as a global resource 5

6 What s In? What s Out? with Net-Centricity IN Situational awareness Self-synchronizing ops Information pull Collaboration Communities of Interest Task, post, process, use Only handle information once Shared data Persistent, continuous IA Bandwidth on demand IP-based Satcom Diverse routing Enterprise services COTS based, net-centric capabilities OUT Limited operational picture Autonomous ops Broadcast information push Individual Stovepipes Task, process, exploit, disseminate Multiple data calls, data duplication Private data Perimeter, one-time security Bandwidth limitations Circuit-based Satcom Single points of failure Separate infrastructures Customized, platform centric IT 6

7 Making Data Accessible Consumer Automated search of data based on core metadata standard. Pulls data of interest. Based on producer registered format and definitions, translates into needed structure. Searchesmetadata catalogs to find data Metadata (e.g., community and Catalogs enterprise-wide Enterprise & search services) Community Web Analyzes metadata to Sites determine context of data found Producer Streaming video available for use, tagged and stored in shared space. Metadata added to catalog based on registered format. Security Services (e.g., PKI, SAML) Shared Data Space Application Services (e.g., Web) Metadata Registries Describes content using metadata Posts metadata in catalogs and data in shared space Ubiquitous Global Network Pulls selected data based on understanding of metadata Posts to and uses metadata registries to structure data and document formats for reuse and interoperability Developer Understand the data format to build applications that post, process, exchange, and display target information. 7

8 On the Road to Network Centric Warfare Pre-Web... Stovepipe systems Little or no interoperability Some network connections...today Joint / Enterprise Enterprise Services More networks Some web services Various directory & security services Uncoordinated Service/Functional transformations Force Sustainment Providers Pervasive networks Mission-effective apps & applets Assured, interoperable enterprise services Dynamically composable architectures Robust & reliable edge computing Accurate, timely & relevant info Improved Quality of Service (QOS) 8 with centrally managed infrastructure

9 GIG Enterprise Services Scope Domain & COI Enterprise Services include levels of services beyond the 9 Core, Net-Centric Enterprise Services Domains and their COI: - Business - Warfighter - Intel Plus: Cross-Domain COI Plus: Expedient COI Net-Centric Enterprise Services (NCES Program) FY04-09: $380M GIG Services Milestone B, 2nd QTR FY04 Scope Includes: - 9 Core Enterprise Services - Application Program Interfaces (APIs) for CES 9

10 GIG Enterprise Services Support real-time & near-real-time warrior needs, and business users DoD (Title 10) Business Domains Expedient COI s Users IC (Title 50) Warfighter Domains National Intel Domain Command & Control Force Application Human Resource Installations & COI s Protection Environment COI s Acquisition/ Strategic Planning Procurement Battlespace Focused & Budget Awareness Logistics Logistics Finance, Accounting C ross Dom ain C O I s (e.g. Situ ation al Operations Aware n e ss, M&S ) Application Application Services Enterprise Service Management Messaging Storage Storage Services Collaboration Collaboration Services Discovery Discovery Services User User Assistant Assistant Services Services Mediation Mediation Services Core Enterprise Services (CES) ICSIS Community Space Security IA/Security ICSIS Org Space GIG Domain/ COI capabilities Levels of services above core level

11 Horizontal Fusion Horizontal Fusion is net-centric with (1) a focus on data - cross functional posting, Ad Hoc access to and fusion of data that is created by operations processes which are integrated and federated and (2) a focus on making sense of that data. Federated Integrated Federated Operations Enterprise Value mostly derives from loosely coupled functional processes, some operating in a just in time manner. Cross functional contributions or contributions from multiple Communities of Interest (COI) to enterprise value are substantial. Integrated Operations Enterprise Value derives from processes that must be executed against tight timelines with high assurance. Processes may be either functional or cross functional but generally execute within a well defined Community Of Interest (COI). Fusion The merging of different elements into a union 11

12 Horizontal Fusion Enterprise Services Security Services Discovery Services Application Services Mediation Services Storage services ESM services Messaging services Collaboration services User assistance Collateral Space: Enterprise Service Selective Demonstration, but not a focus of the pilot Provide operators on the edge with the applications and data 12 access to achieve a near real-time dynamic view of the battlespace

13 Security Services User Access Control Identification and authentication Authorization Single sign-on Cross-Domain Data Exchange messaging Structured situation and location data Documents Video Metadata 13

14 Discovery Services Intelligent Search Military vocabulary Google bar Cataloging Coordinated SIPRNet cataloging Cross-domain cataloging (SIPRNet-JWICS) Integrated Metadata Management Discovery People/expertise Applications/services Content 14

15 Making Data Accessible Create shared information spaces and data exposure services Provide Web-Services style access Deploy information resource subscription capabilities Associate security-related metadata Deal with single sign on issues Adopt metrics and incentives 15

16 Mediation Services GES Discovery Metadata Vocabulary Core Standard (Dublin Core) Security (CAPCO) High level DoD-IC taxonomy COI extensions CES Federation Intra-CES Metadata transformations COI-to-CES Transactions Multi-ontology support Semantic translations 16

17 Application Services Portal Infrastructures Operational hosting Development environment Integrated Visualization Portlet management, integrated geospatial display Application Integration Intel and C2 applications ACTD capabilities Publication Services Net-wide TPPU Advertise available products and services Post needs, task assets 17

18 COE Commercialization Source code for Posix/Linux COE turned over to industry Industry consortiums free to vary from Governmentprovided baseline as long as resulting software passes verification testing GOTS code will be phased out as Industry Best Practices emerge Government-funded enhancements in COE Kernel Platforms will be through industry processes (e.g., open source initiatives) Government may influence industry direction through participation in industry groups & standards bodies 18

19 Platform Desired End-state COE Certification Criteria defines the COE-Era platform, including information assurance configuration. Future Certification industry-based Posix/TCP-IP/X Platform certification available via The Open Group Linux certification available via Free Standards Group Any gaps in standards-based functionality is defined by GOTS Reference Implementation Cross-Platform User Accounts and Profiles Package Format and Installation Tools Common Data Store 19

20 Industry Process for COE Linux Kernel Free Standards Group has populated a Linux SourceForge repository accessible via web Content includes Linux kernel GOTS, that is: 1. RPM (RPM Package Manager) 2. GNOME Java Based Developers Toolkit (JBDT) & Runtime Libraries (COE APIs) 4. Account and Profile Management (APM) 5. Common Data Store (CDS) Develop processes for managing incorporation of source code updates 20

21 COE Windows Commercialization Strategy No major Government-funded enhancements in COE Kernel Platforms Monitor Microsoft s market direction and use native tools Maintain Application Platform Criteria. FSO Gold Disk strategy supported 21

22 Platform Definition: GES Approach Focus is J2EE-oriented software platform Less emphasis on hardware platform for application interoperability/portability Develop Application Platform Criteria maintained and made available for use in certification programs Adopt FSO Gold Disk and guidance when available. 22

23 Platform Information Assurance: GES Approach NIAP Medium Robustness Protection Profile (MRPP) replace appendix E of the Compliance Criteria MRPP is broader and moves away from government specific requirements to industry standards Security lockdown will be coordinated with the FSO gold disk strategy GOTS code will be phased out as Industry Best Practices emerge 23

24 GES Platform Supplemental To the minimum extent necessary, DISA will provide platform specific guidance as compliance criteria for: Level 5 compliance for transitioning legacy applications Posix/TCP-IP/X based platforms Linux platforms W indows platforms Leverage Industry testing/certification, and Apply FSO guidance and NIAP process, to the maximum extent appropriate. 24

25 Target Architecture Enterprise Architecture Services available via the net (not system dependent) Web-services based application platform (Backend) COTS products (Partnering with Industry) Open development environment (JCP and Open Source or Shared Source where it makes sense) 25

26 Build-Time Electronic Market DOD Data Emporium e One Stop Publish & Subscribe Data/metadata Registration Data Component Vending COI Creation & Management Current Version vending XML Reference Sets Transformations Data Tools DB Segments Purpose: visibility and re-use, not standardization through mandate! Upcoming Versions Robust Subscription Service Better Metrics and Search More Products (e.g., ontologies) Run-time interfaces 26

27 GES IT Standards Approach Minimize Enterprise Level Standards Key on standards required to enable Net-Centric Vision Focus on integration points as required Include: Enterprise implementation guidance Basic architectural precepts (e.g., GIGv2) Communities of Interest (COI s) provide detail Publish and manage COI Standards Profiles Include COI-specific implementation and architecture guidance Most MilStds are in COI Portfolio s Enterprise-wide Visibility Service All publish via NCES using XML Registry paradigm 27

28 IT Standards Management Transformation Legacy Standards Management Processes NCES Services/Agencies SMEs Migrate Standards to NCES Logistics Logistics Community-ofInterest (COI) Capability Developers Comms COIs Backbone ESM Functionals Mediation Discov ery Legacy Stds Stores Legacy Stds Stores Legacy Stds Stores Legacy Stds Stores Messaging Security/IA Federated Standards Process Collaboration Storage User Asst Core Enterprise Serv ices (CES) App Discovery & Mediation Services Standards Registration bwe e d s Ba DoD Metadata Registry Standards Registry Other Net-Centric: Post before Processing Subscription Process 28

29 JC2 Transformation Vision M C P s Today s Global Command & Control System (GCCS) will evolve from its current state of joint and Service variants to a single Joint C2 architecture and capabilities-based implementation Service-oriented architecture. comprised of mission capability packages and Services Applications Army Applications MarCorps Applications Navy Applications Air Force Applications Agency Applications Readiness Planning, Force Projection & Sustainment Intelligence Situation Awareness Force Protection Cross-functional services (JC2 COI core) NCES core enterprise services and GIG Force Employment: Air/Space operations Force Employment: Joint fires/ Maneuver M C P s Based on GIG / NCES infrastructure providing shared access to Service/Agency/joint data sources 29

30 JC2 Interaction with NCES C2 Centers & Reachback Producers Storage GIG ESM Security Authenticate NCES Services Messaging Mail M JC2/NCES local Services Joint Force Commander Example JC2 Services: JC2 Decision Support JC2 Training JC2 Apps Svcs Monitor Producers in e et Collab n COP Register Discover Mediate Register for sources & services gs Tracks pport u s O, AT video t e g r Ta JC2/NCES local Services JTF Component HQ Service Registry JC 2 w eb acce ss Alert Service WMD Alert JC2/NCES web-based Access JTF, Coalition, Interagency Forces NCES will provide a common set of interoperable information capabilities30in the GIG to access, collect, process, store, disseminate, and manage information on demand for warfighters, policy makers, and support organizations.

31 What is involved in C2 transformation? Modernization of C2 infrastructure to support transition to JC2 WebCOP (Web 1.0) Web Services transition (Web 2.0) Incorporation of data strategy XML Registry expansion (Run-time) Open development environment Process improvements Modeling of capabilities (Static/Dynamic) Concept pilots and demos 31

32 What needs to change for C2 to Transform? Client-Server transition to Services Context Better QoS capabilities in platform and network infrastructure Dynamic allocation of computing resources Graceful Degradation Grid Computing concepts Fusion architecture to provide: Information manager for data producers Association/Correlation/Fusion functions Access by edge users Web Services infrastructure Composable Implementation (Component/ Object Based) 32

33 JC2 in a Service Oriented Architecture An example: Joint Deployment The process Business logic WHAT Metrics: What is my business performance? Lift requirements Request for forces Deployment monitoring Enroute intell & port status Deployment Plan capabilities readiness capabilities readiness HOW Pipeline monitoring sustainment generation transportation feasibility, Strategic lift Force Providers In-theater lift, intelligence RSOI, resupply Supported Commander (ACOA, JOPES, DRRS) (GCCS) Force Sustainers (& GCSS) Force Transporters (& DTS/GTN 21) The implementation organization & IT components Legacy: No single data / process models usually across (or beyond) the enterprise 33

34 C2 Modernization Plan for Transition to JC2 Today FY03 FY04 FY05 Global C2 System GCCS 3.X GCCS Block IV GCCS Block V IOC FY06 FOC FY10-11 advanced concepts & technology C2 MODERNIZATION JC2 ORD Horizontal Fusion Pilot NCES CDD JC2 MCP prototypes + J2EE server JC2 pilot services NCES pilot services FOS Integration JC2 Block I NCES v.1 JC2 Block II NCES v.2 JC2 Block III NCES v.3 Joint C2 Capabilities Common Operating Environmt COE 3.X COE 4.X INCREASING CAPABILITY RISK REDUCTION, PRODUCTION & INTEGRATION Prototype the functionality of M ission Capability Packages Work out interfaces between M CPs Work out interfaces with NCES core services Develop C2&I-specific net-centric services Pilot M CPs with GCCS Block V in operational context Integrate final versions with production NCES v.1 34

35 Summary Change is in progress Cultural shift from Client-Server to Net-Centric capabilities Grid Computing is part of our future Application integration needs to evolve Need better way to get capabilities into the hand of the warfighter faster! Coordination with our Service and Agency partners should set into action a plan for C2 transformation 35