Shared Operational Context: A Needed Transformation

1. Shared Operational Context:A Needed Transformation Erik Chaum NUWC S&T Presentation July 2002

2. Team • Office of the Deputy Under Secretary of Defense (Advanced Systems and Concepts) • Mr. Dick Lee • Naval Undersea Warfare Center, Division Newport • Mr. Erik Chaum • Mr. Ernie Correia • Naval Postgraduate School, Monterey • Dr. Don Brutzman • Institute for Defense Analysis • Dr. Gene Simaitis • Dr. Francisco Loaiza

3. Outline • NCW Challenge • An essential trilogy • Opportunity: Generic Hub • ACTD 01: C4I Coalition Warfare • Future Opportunities

4. NCW Challenge • Information Age transformation of war fighting systems and processes. • More than connectivity. • Broad tactical and operational shared-awareness. This type of sophisticated shared understanding will leading to improved synchronization of effects, speed of command and effectiveness. • Ubiquitous Interoperability & Info Sharing • The ability to work together: Intra-service, Joint, Coalition • Are we progressing to the goal? Are all the pieces in place - just more time and funding required? Decision & Information Superiority resulting in more timely, relevant, and accurate effects.

5. An Analogy • Military decision maker • Intelligent part of today’s system • Scenario • Well trained • Perfect Tactical Picture • Decision makers Need Context to make decisions Operational Context is today maintained in the warfighter “part” of tactical and command and control systems.

6. Operational Context Shared Understanding Interoperability Automation Trilogy NCW Foundation Pillars

7. Operational Context • Situational Awareness includes shared understanding regarding: • the scope of operations • command relationships • task force order of battle • mission assignments/objectives • Commander's Intent • rules of engagement (ROE) • coordination guidelines • schedule of operations • communication schedules • battlespace management (e.g., waterspace management) • sensor employment and management plans/guidance • threat assessment • environmental guidance • Family of Interoperable Operational Pictures [FIOP] This information and knowledge is understood by people, and must be available and used by automated systems!

8. Data Fusion Sys #1: • 60% Sub • 30% Ship • 10% Helo • Data Fusion Sys #2: • Unk • Sub • Ship • Air = Goal: Shared Understanding • Independent, incompatible models create unsolvable interoperability problems. • Classification Uncertainty Models: There is no unambiguous mapping between these two models - information is lost, imprecise understanding.

9. Context Driven Operational Context Service FIOP Service Sensor Driven Future NCW Systems: Sensor and Context Driven Global Information Grid Applications Agents Autonomous Systems Sensing

10. Implementation Considerations • Hierarchical Process • Each echelon adds additional information • Top-down • Shared understanding across the range of battlespace information • New Interoperability Standards required • Workload • Country, Service, System, Application, Technology, Contractor Independent • Generic, Cross-Cutting and Unifying

11. N2 Top-down “Unified” N Capability Gaps Global Exchange Ontology GH4 Bottom-up “Negotiated” Capability Shortfall Today NCW Objective Capability

12. NATO Reference Model • NATO Battlespace Operational Context model: Land C2 Information Exchange Data Model (LC2IEDM), or GH5 (Generic Hub version 5) • Countries use it for C2 systems interface definition • Draft NATO STANAG (ADat-P32). • Work progressing on GH5 • Provides a rational mature framework for interoperability and exploring more sophisticated automation methods.

13. Battlefield objects and types: Facility Feature Materiel Organization Person etc. Entity-Relationship Model: [not a list of data] Key information entities, and relational meta-information GH4: Basic Entities

14. Basic Entities Situational Awareness Reporting Data Battlefield objects and types Facility Feature Materiel Organisation Person Capability Plans, Orders, Requests NATO Land Command and Control Information Exchange Data Model

15. C4I Coalition Warfare Task • This work explored, demonstrated, and evaluated GH4 applicability to maritime coalition interoperability and system automation • GH4, via XML Schema, distributed operation context and tactical data • CORBA data server interface • Submarine combat control system • X3D browser-based visualization

16. ESG CVN Auto-generation & Visualization of Structured Planning Information Dr. Don Brutzman, MOVES, NPS

17. Multiple Transformation Enabler • New Capabilities for the Warfighter - • Applications, Intelligent Agents, and Autonomous Systems with Operational and Tactical Awareness • Cost Reduction • System Engineering • Maintenance • Interoperable based on top-down design • Operational Context Information Architecture • Industry Best Practices Approach • Start with Coalition Success

18. Future Opportunities • Building on key ideas and successes • Sharing ideas, looking for synergy & partners: • Joint & Coalition Project formulation • Joint Experimentation • Scaling up and out • Appropriate to consider as a mission-oriented enterprise solution for all DoD • Working Coalition partnerships • Technology outreach to Allies

19. POC: • Mr. Erik Chaum Naval Undersea Warfare Center, Newport, RI 401.832.6915 Chaume@npt.nuwc.navy.mil