DoD Transformation and The Global Information Grid
Implications for GIS of Emerging Net-Centric Implications for GIS of Emerging Net-Centric Warfare Operational ConceptsWarfare Operational Concepts
Mr. Rob Walker9 July 2003
2
Net-centric Challenge & Payoff
SystemSystem of Systems
Family of Systems
Net-centricOperations
Capa
bilit
y
ScaleSignificant
Transformational
Global Information Grid
70’s
90’s
Data
6 1 e l . T h e a te r
8 GHz M BR
1 6 9 e l. 7 GHz M BT44/20
2 56 e le m e nt
TPA48 4 e l e m en t
RPA
80’s
6 1 e l . T h e a te r
8 GHz M BR
1 6 9 e l . 7 GHz M BT44/20
2 5 6 e le m e n t
TPA4 8 4 e l e m e n t
RPA
3
The Key Components of Net-Centric GIG Infrastructure
Foundation Provides an approach to manage, operate, and change the culture
Communications Provides a comprehensive terrestrial and space network
Computing Provides services to exploit the network and support applications
Applications Provides tools needed for a capabilities based force
Data Management Ensures all data is discoverable and understandable
Information Assurance Protects the data and the networkThe Enterprise Infrastructure is Greater Than the
Sum of the Components
4
Today’s Operational Environment
CINC HQsPentagonWhite House
CoalitionJTF
Headquarters
JTF Components
Some Networks,point-to-point& peer-to-peer
Varying missions & localesVarying missions & localesVarying force sizes/typesVarying force sizes/typesVarying JTFs & coalitionsVarying JTFs & coalitionsVarying comms & equipmentVarying comms & equipmentVarying information needsVarying information needs
JTF EnvironmentJTF EnvironmentNetworksSystems & Data
Too many stovepipes
Limited interoperability
5
Tomorrow’s Operational Environment
The DISA Transformation Vision
CINC HQsPentagonWhite House
Power to the Edge!
Ubiquitous, secure & robust networkUbiquitous, secure & robust networkDeploy collaborative capabilitiesDeploy collaborative capabilitiesPopulate network with all dataPopulate network with all dataContinuously refresh contentContinuously refresh contentSecure & assure the network & infoSecure & assure the network & infoData as a global resourceData as a global resource
Transforming TechnologiesTransforming Technologies& Concepts& ConceptsWorknetsWorknets
Capabilities & Capabilities & RelationshipsRelationships
Coalition
JTF Headquarters
JTF Components
CommonEnterpriseServices
SecureInterconnectedNodal Network
Sensor-to-shooter
Power to the Edge!
Power to the Edge!
Power to the Edge!
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
7
Making Data Accessible
UbiquitousGlobal Network
MetadataCatalogs
Enterprise &Community
Web Sites
Application Services(e.g., Web)
Shared DataSpace
Metadata Registries
Security Services(e.g., PKI,
SAML)
Automated search of data based on core metadata standard. Pulls data of interest. Based on producer registered format and definitions, translates into needed structure.
Consumer
Understand the data format to build applications that post, process, exchange, and display target information.
Developer
Describes content using metadata
Posts metadata in catalogs and datain shared space
Streaming video available for use, tagged and stored in shared space. Metadata added to catalog based on registered format.
Producer
Searchesmetadata catalogs to find data (e.g., community andenterprise-wide search services)
Analyzes metadata to determine context of data found
Pulls selected data based on understanding of metadata
UbiquitousGlobal Network
MetadataCatalogs
Enterprise &Community
Web Sites
Application Services(e.g., Web)
Shared DataSpace
Metadata Registries
Security Services(e.g., PKI,
SAML)
Automated search of data based on core metadata standard. Pulls data of interest. Based on producer registered format and definitions, translates into needed structure.
Consumer
Understand the data format to build applications that post, process, exchange, and display target information.
Developer
Describes content using metadata
Posts metadata in catalogs and datain shared space
Streaming video available for use, tagged and stored in shared space. Metadata added to catalog based on registered format.
Producer
Searchesmetadata catalogs to find data (e.g., community andenterprise-wide search services)
Analyzes metadata to determine context of data found
Pulls selected data based on understanding of metadata
Posts to and usesmetadata registries to structure data and document formats for reuse and interoperability
8
On the Road to Network Centric Warfare
• Stovepipe systems
• Little or no interoperability
• Some network connections
Pre-Web. . . . . . Joint / Enterprise
• Pervasive networksPervasive networks• Mission-effective apps & applets Mission-effective apps & applets • Assured, interoperable enterprise Assured, interoperable enterprise
services services • Dynamically composable Dynamically composable
architecturesarchitectures• Robust & reliable edge computing Robust & reliable edge computing • Accurate, timely & relevant infoAccurate, timely & relevant info• Improved Quality of Service (QOS) Improved Quality of Service (QOS)
with centrally managed infrastructurewith centrally managed infrastructure
. . .Today. . .
• More networks• Some web
services• Various directory
& security services
• Uncoordinated Service/Functional transformations
• Few authoritative data sources
EnterpriseServices
ForceSustainment
Providers
9
GIG Enterprise Services Scope
Domains and their COI: - Business - Warfighter - Intel Plus: Cross-Domain COI
Plus: Expedient COI
Domain & COI Enterprise Services include levels of services beyond the9 Core, Net-Centric Enterprise Services
Net-Centric Enterprise Services (NCES Program) FY04-09: $380M
Milestone B, 2nd QTR FY04
Scope Includes:- 9 Core Enterprise Services- Application Program Interfaces (APIs) for CES
GIGServices
GIG Enterprise ServicesSupport real-time & near-real-time warrior needs, and business users
Finance, Accounting Operations
Users
ApplicationServices
StorageServices
DiscoveryServices
SecurityServices
MediationServices
User AssistantServices
CollaborationServicesMessaging
Users
Application Enterprise Service
Management
Storage Discovery IA/Security
MediationUserAssistant
Collaboration
Acquisition/Procurement
Human Resource
Business Domains Warfighter Domains
COI’sCOI’s
Force Application
Protection
Focused Logistics
Command & Control
Strategic Planning & Budget
Logistics
Installations&
Environment
Expedient COI’s
Cross Domain C O I’s (e .g. Situational Awareness, M&S) GIG
Domain/ COI
capabilities
Levels of services
above core level
ICSISOrg Space
Battlespace Awareness
DoD (Title 10) IC (Title 50)
National Intel Domain
ICSIS Community SpaceCore Enterprise Services (CES)
11
Horizontal Fusion
Horizontal FusionHorizontal Fusion is netis net--centric with (1) a focus on data centric with (1) a focus on data -- cross functional posting, cross functional posting, Ad Hoc access to and fusion of data that is created by operations processeswhich are integrated and federated and (2) a focus on making sense of that data.
Federated OperationsEnterprise Value mostly derives from looselycoupled functional processes, some operating in a “just in time” manner. Cross functionalcontributions or contributions from multiple Communities of Interest (COI) to enterprisevalue are substantial.
Integrated OperationsEnterprise Value derives from processes that must be executed against tight timelines with high assurance. Processes may be eitherfunctional or cross functional but generallyexecute within a well defined Community Of Interest (COI).
The merging of different elements into a union
Fusion
IntegratedFederated
12
Collateral Space:Enterprise Service
• Horizontal Fusion Enterprise Services – Security Services– Discovery Services– Application Services– Mediation Services– Storage services– ESM services– Messaging services– Collaboration services– User assistance
Selective Demonstration, butnot a focus of the pilot
Provide operators on the edge with the applications and data 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– E-mail messaging– Structured situation and location data– Documents– Video – Metadata
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
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
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
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
18
COE Commercialization
• Source code for Posix/Linux COE turned over to industry
• Industry consortiums free to vary from Government-provided 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
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
20
• 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 2.03. 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
Industry Process for COE Linux Kernel
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
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.
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
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– Windows platforms
• Leverage Industry testing/certification, and• Apply FSO guidance and NIAP process,
… to the maximum extent appropriate.
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)
26
Build-Time Electronic Market DOD Data Emporium • “One Stop” Publish & Subscribe
– Data/metadata Registration– Data Component Vending– COI Creation & Management
• Current Version vending – XML – Reference Sets– Transformations– Data Tools– DB Segments
• Upcoming Versions– Robust Subscription Service– Better Metrics and Search– More Products (e.g., ontologies)– Run-time interfaces
http://diides.ncr.disa.mil/shadehttp://diides.ncr.disa.smil.mil
Purpose: visibility and re-use, not standardization through mandate!
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
28
IT Standards Management Transformation
Legacy Standards Management Processes
Other
Migrate Standards to NCES
DoD MetadataRegistry
StandardsRegistry
Federated Standards Process
StandardsRegistration
Functionals
COIs
Services/AgenciesSMEs
Developers
LegacyLegacyStdsStds
StoresStores
Subscription Process Net-Centric: “Post before Processing”
Web-
Based
CoreEnterpriseServ ices
(CES)
CommsBackbone
LogisticsCommunity-of-Interest (COI)
Capability
MediationESM
Discov ery
CollaborationMessaging
AppStorage
UserAsst
Logistics
Security/IA
NCES
Discovery & Mediation
Services
LegacyLegacyStdsStds
StoresStores
LegacyLegacyStdsStds
StoresStores
LegacyLegacyStdsStds
StoresStores
29
JC2 Transformation Vision
• “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
– Based on GIG / NCES infrastructure providing shared access to Service/Agency/joint data sources
ReadinessPlanning,
ForceProjection &Sustainment
Intelligence SituationAwareness
ForceProtection
ForceEmployment:
Air/Spaceoperations
ForceEmployment:
Joint fires/Maneuver
Cross-functional services (JC2 COI core)NCES core enterprise services and GIG
Army Applications MarCorps Applications Navy Applications Air Force Applications Agency Applications
MCPs
MCPs
30
JC2 Interaction with NCES
NCES will provide a common set of interoperable information capabilities in the GIG to access, collect, process, store, disseminate, and manage information on
demand for warfighters, policy makers, and support organizations.
ServiceRegistry
NCES Services AlertService
Producers Producers
ESM
Collab’n MediateMessagingSecurity
Storage
Joint ForceCommander JTF
ComponentHQ
JTF, Coalition,Interagency
Forces
COP
JC2/NCESlocal
Services JC2/NCESlocal
Services
JC2/NCESweb-based
Access
GIG
Discover
C2 Centers& Reachback
WMDAlert
Tracks
Target video, ATO support
MeetingsMailAuthen-
ticate Register for sources &
services
JC2 web access
Register
Example JC2 Services: JC2 Decision Support JC2 Training JC2 Apps Svcs Monitor
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
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)
33
JC2 in a Service Oriented ArchitectureAn example: Joint Deployment
WH
AT
HO
W
The process – Business logic
The implementation – organization & IT components
Metrics: What is my business performance?
DeploymentPlan
SupportedCommander
(GCCS)
ForceProviders
(ACOA, JOPES,DRRS)
ForceSustainers
(& GCSS)
ForceTransporters(& DTS/GTN 21)
Requestfor
forces
capabilitiesreadiness
sustainmentgeneration
transportationfeasibility,
Strategic lift
Liftrequirements
In-theater lift,intelligence
RSOI,resupply
Pipelinemonitoring
DeploymentmonitoringEnroute
intell &port status
Legacy: No single data / process models usually across (or beyond) the enterprise
capabilitiesreadiness
34
C2 Modernization Plan for Transition to JC2
JointC2
Capabilities
GCCSBlock IV GCCS
Block V
JC2Block I
JC2Block II
JC2Block III
GCCS3.X
COE3.X
COE4.X
NCESv.1
NCESv.2
NCESv.3
GlobalC2
System
CommonOperatingEnvironmt
+ J2EE server
NCESpilot
services
JC2pilot
servicesHorizontalFusionPilot
JC2 MCPprototypes
JC2ORD
NCESCDD
Today
IOCFY06 FOC
FY10-11
C2
MO
DER
NIZ
ATI
ON
adva
nced
con
cept
s&
tec
hnol
ogy
RISK REDUCTION,PRODUCTION & INTEGRATION
● Prototype the functionality of M ission Capability Packages● Work out interfaces between MCPs● Work out interfaces with NCES core services● Develop C2&I-specific net-centric services● Pilot MCPs with GCCS Block V in operational context● Integrate final versions with production NCES v.1
INCREASINGCAPABILITY
FOSIntegra-
tion
FY03 FY04 FY05
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