Common Operating Environment (COE) and Global Information Grid (GIG) Enterprise (GES) Mr. Rob Walker 24 September 2003
Common Operating Environment COE is mission-application independent - A basis for a system architecture - An integration approach - A collection of reusable software - A software infrastructure - A set of guidelines and standards The COE is not a system; it is a platform focused foundation for building a shared system. 2003 COE/GES Technical Exchange 2
COE Components Mission Applications Mission Unique Functionality Developed by /Agencies Controlled/deployed by and agencies Common Support Applications Common Infrastructure Emphasizes interoperability via common view of data Functionality common within domains Developed by /Agencies Controlled & deployed by DISA Emphasizes movement of data through the network Functionality Common across DoD Developed by /Agencies & DISA controlled & deployed by DISA COE Kernel Present on every COE compliant workstation Functionality Common across DoD Developed by DISA Controlled & deployed by DISA 2003 COE/GES Technical Exchange 3
Formal Compliance Definitions No duplication of functions with COE components No more than 25% of data can be duplicate with COE or COEbased target system Uses at least 75% public APIs for COE service access All segmented applications share the same COE Kernel Segments can be installed and deinstalled thru COE tools Two applications can coexist on the same platform COE Kernel or equivalent resides on the platform System uses same standards for operating system, windowing, and database queries as COE 8 7 6 5 4 3 2 1 No duplication of functions with COE or co-hosted segments No duplication of data with COE or COE-based target system 100% I&RTS and User Interface Guide compliant Segment functions are at least 50% COE implemented Application is segmented Two applications can coexist on the same network 2003 COE/GES Technical Exchange 4
Net-Centric Operations Fundamental Shift in Data Environment Platform-Centric Net-Centric AF78 533 533 Traditional stove-pipe approach v. Fused Data available on the Net 2003 COE/GES Technical Exchange 5
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 2003 COE/GES Technical Exchange 6
GIG Enterprise Scope Domain & COI Enterprise include levels of services beyond the 9 Core, Net-Centric Enterprise Domains and their COI: - Business - Warfighter - Intel Plus: Cross-Domain COI Plus: Expedient COI Net-Centric Enterprise (NCES Program) FY04-09: $380M Milestone B, 2nd QTR FY04 Scope Includes: - 9 Core Enterprise - Application Program Interfaces (APIs) for CES GIG 2003 COE/GES Technical Exchange 7
GIG Enterprise Governance Structure GES Executive Board & Steering Group GES AoA (DISA) GES ICD/CDD (DISA) Transition Policy (DCIO) Arch & Sys Eng Review Board Program Synchronization Domain EA Program Governance Program Program Bd Synchronization Synchronization Program Synchronization Synchronization GIG ES Oversight Group (GOG) Data Net Ops & ESM Collaboration & Messaging IA/Security Engineering Support Groups Reporting Coordination 2003 COE/GES Technical Exchange 8
GIG Enterprise Support real-time & near-real-time warrior needs, and and business users users DoD (Title 10) IC (Title 50) Users Business Domains Acquisition/ Procurement Logistics Installations & Environment COI s Strategic Planning & Budget Finance, Accounting Operations Expedient COI s Human Resource Warfighter Domains Command & Control Focused Logistics COI s Protection Force Application Battlespace Awareness Cross Domain COI s (e.g. Situational Awareness, M&S) National Intel Domain ICSIS Org Space GIG Domain/ COI capabilities Levels of services above core level Application Enterprise Service Management Storage Discovery Storage Discovery IA/Security Messaging Collaboration Collaboration User User Assistant Assistant ICSIS Community Space Mediation Mediation Core Enterprise (CES)
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 2003 COE/GES Technical Exchange 10
IT Standards Management Legacy Standards Management Processes SMEs Developers /Agencies COIs Transformation Migrate Standards to NCES NCES Logistics Logistics Community-of- Interest (COI) Capability Comms Backbone Functionals ESM Discovery Mediation Security/IA Messaging Storage Collaboration App User Asst Core Enterprise (CES) Legacy Stds Stores Legacy Stds Stores Legacy Stds Stores Legacy Stds Stores Federated Standards Process Standards Registration Discovery & Mediation DoD Metadata Registry Standards Registry Web- Based Other Subscription Process 2003 COE/GES Technical Exchange 11
Summary Department of Defense is transitioning from COE to GES Focus moving from platform-centric to network-centric The need for standards-based COTS solutions will increase over time COE software engineering concepts will continue to be important, even for COTS: Minimize impact on other applications during installation and runtime Keep security in mind at all stages of development 2003 COE/GES Technical Exchange 12