150 likes | 347 Views
Designing for C2 Capability Across the GIG. CAPT Rob Zalaskus Naval Network Warfare Command (N6). Roles. Operationally Defining Network Enabled C2 Requirements. Functional Component Commander Operational Development. Data Sharing Communities of Interest. Activities. Functions.
E N D
Designing for C2 Capability Across the GIG CAPT Rob Zalaskus Naval Network Warfare Command (N6)
Roles Operationally Defining Network Enabled C2 Requirements Functional Component Commander Operational Development Data Sharing Communities of Interest Activities Functions SysNode OpNode OV SV Systems Information Exchanges Data Exchanges OrgStructure Governance Governance Strategy Doctrine
MOC 8 MOC 4 MOC 7 MOC MOC MOC 5 MOC MOC 9 MOC 6 CPOF w CPOF t AOC K ROC F ROC L AOC B ROC O CPOF v CPOF r CPOF x CPOF z CPOF s AOC A ROC E AOC I AOC J AOC M ROC D CPOF y ROC N AOC C CPOF u ROC H AOC G Globally-Netted Operations Centers Maritime Air Land
Multi-Domain Awareness • “Multi-Domain Awareness” • Maritime, Air, Space, Land, Cyber, … • MDA = GSA + GII • Awareness + Analysis + C2 = Operational Threat Response • JFC Support • Family of Systems approach • Family of Integrated Service Architectures • Federated Services approach • Federated data sharing strategies via NCES Global Awareness – Focused Execution
Multi-Domain Awareness • Information flow between netted operations centers (Joint and Intra-Service) • Supporting Phase 0 Operations • GWOT • Developing engineered inter-dependence • “Multi-Domain Awareness” • Not a mission/task – the result of capability integration • Supports decision-making for operational response
Layered SA Cyber Maritime Multi-Domain SA Air Land
Global Networking • Achieved by combining Information Assurance and Interoperability • Common core infrastructure - GIG • Minimize information boundaries • Operational architecture interface analysis • Shared operational processes • Shared understanding via metadata • Complementary NCES instantiations • Data and functional Services • Designing for the operational information environment • “Tiered” networking
Multi-Tiered Approach GWOT/BMD ROCs • MDA Policy • Legal Framework for information sharing • COI Steering • National/International data handling guidance MIO/CP HQ 1 Component 1 1 HQ 2 2 HA/DR 3 Component 2 NGO NGO NGO • International release of certification methodology • Data aggregation – data mining and sharing • Common Data Model • Data Pedigree • Standards/Protocols • Interoperability thru common doctrine and exercise frameworks NGO/OGA/Partners • Non-Classified Network Policy • Ability to hastily form networks
MCO Managing Network Complexity Tier 1 Tier 2 Tier 3 Ph 0
Tier 1 Information Exchange Operational architects identifying information elements, operational activities and nodes involved with information exchanges
Global Networking Information Interfaces • Coordinated, detailed review of functional component commander operational architectures • ~50 confirmed point-to-point information exchange requirements • ~25 items identified for resolution after additional analysis • ~150+ required significant abstraction in order to account for differences in language and context to facilitate meaningful analysis
Global Networking – SV Perspective AOC SV-1 MOC SV-1 Next steps should include analysis of systems interoperability between AOC, MOC and LOC (?)
Systems and Applications SOCRATES TMS JTT JFAST GCSS TCTF SOA Services JWARN WPC COLISEUM ADSI WEEMC JSS TMDS JOPES