Simulation to C4I Support Plan Development: Experience Report 03SSIW135

1
Simulation to C4I Support Plan Development
Experience Report03S-SIW-135

• Robert Wittman
• MITRE CORPORATION
• 3504 Lake Lynda Drive
• Orlando, FL 32817
• 321-235-7601
• rwittman_at_mitre.org

Hugh Kelley MITRE CORPORATION 3504 Lake Lynda
Drive Orlando, FL 32817 407-208-1320 hkelley_at_mit
re.org
Sheila Cane MITRE CORPORATION 3504 Lake Lynda
Drive Orlando, FL 32817 407-208-1320 sheila_at_mitr
e.org
2
Agenda

• C4I Support Plan Introduction
• Program Participation
• Training Aids Devices, Simulators, and
  Simulations (TADSS) System of Systems (TSOSA)
• OneSAF Objective System (OOS)
• Common Training Instrumentation Architecture
  (CTIA)
• ABCS 7.0 System of System Engineering
  Integration
• Architecture Products Development Process
• Architecture Products
• C4I/Simulation Derived Requirements
  Dependencies
• Potential Uses for DoD Framework Architecture
  Products

3
Application of DOD Architecture Framework - DOD
5000.2-R

• Prior to Sept. 2002 DOD 5000.2-R required a C4ISP
  for all programs that
• Are ACAT 1x or ...
• Interoperate in any way with ACAT 1x systems or
  ...
• Interoperate with a DOD C4I system (regardless of
  their acquisition category)
• DOD 5000.2-R specified that a C4ISP will include,
  as a minimum, all the mandatory products of the
  DOD Architecture Framework
• AV-1 Overview and Summary Information
• AV-2 Integrated Dictionary
• OV-1 High Level operational Concept Description
• OV-2 Operational Node Connectivity Description
• OV-3 Operational Information Exchange Matrix
• OV-5 Activity Matrix
• OV-6 Event Trace (Not Required)
• SV-1 System Interface Description
• TV-1 Technical Architecture Profile

Note C4ISP focus is interoperability
requirements between external systems - not
internal system requirements!
4
Program Participation
PEO-STRI TADSS System of Systems Architecture
(TSOSA)
PEO-STRI One Semi-Automated Force Simulation
PEO-C3T ABCS 7.0 System of Systems Engineering
Integration Team
5
C4ISP Development Process
Overview Summary Information AV-1
Integrated Dictionary AV-2
High Level Operational Concept Description OV-1
Operational Node Connectivity Diagram OV-2
Activity Matrix OV-5
Operational Event Trace OV-6c
Operational Node Info Exchange Matrix OV-3
System Interface Exchange Matrix SV-6
System Interface Diagrams SV-1
Technical Architecture Profile TV-1
6
OOS-ABCS 7.0 Interoperability (OV-1)
Functions Product Line Development, Deployment,
Maintenance Phases KA/KE Product Line
Development Product Line Deployment Product
Line Maintenance Pre-Event Phases Event
Planning Database Development Software
Development Model Composition Scenario
Generation Event Phases Simulation
Configuration System Test and Verification
Simulation Execution Post Event Phases Post
Execution Analysis/AAR Archival Retrieval
Exercise Participants Exercise Control
Observer/Controller, Battlemaster/Senior
Controller, Technical Controller Role Player
OOS Simulation System
Analysis Review Tools
Exercise Execution Tools
Pre- Exercise Tools
Military Simulation (Fire Support Organizations,
Entities, Processes)
Data Services
C4I Interface
Simulation Interfaces Constructive, Live, Virtual
Data System Configuration Initialization Unit
Orders and Report Information Environment/Mapping
Information Tactical Overlays/Battlefield
Graphics Unit Organization Information
References OneSAF PLAS Volume 1
7
Operation View (OV)-5 Process Decomposition
(Draft)
8
OV-6c Process ChartPre Event - Event Planning
(Draft)
9
Pre-Event Phase Operational Node Connectivity
Diagram (OV-2) (Draft)
10
Operation Node Information Exchange Matrix (OV-3)
(Sample)
11
SV-1 System Interface DiagramsPre-Event (Draft)
12
Systems IER Matrix OV-3 SV-6 (Sample)
13
Technical Architecture Profile (TV-1) Sample

• Military messaging TADSS sends ABCS systems
  messages from simulated friendly units, and
  receives messages sent to simulated friendly
  units.
• ABCS internal standards TADSS emulates data
  distribution between simulated and live command
  posts and platforms.
• ABCS Operating Environment TADSS and ABCS must
  share a compatible operating environment.
• ABCS Security Environment Since ABCS operates as
  high as Secret System High, TADSS must have the
  capability to operate at the same level.

14
C4ISP Issue and Dependency Summary

• Pre-Event
• Need to Define Consistent Approach for
  Initialization of Simulation and ABCS 7.0 Devices
  for Unit, Equipment, and Environmental Data
• Exercise Execution
• Need to Plan for Coordinated Checkpoint/Restart
  and Time Synchronization between OOS and ABCS 7.0
• Need to Plan for Coordinated Handling and
  Separation of Simulation and Real-World Data
• Need to Identify and Coordinate Interface
  Technologies such as XML, SOAP, and Java
  Messaging Services that can be Utilized as Part
  of Interface Solution
• Need to Identify and Coordinate Specific Message
  Sets/Versions to be Communicated between OOS and
  ABCS 7.0
• Post-Event
• Need to Identify Specific Bandwidth and
  Distribution Process of AAR Products to ABCS 7.0
  Devices for In the Field Review

15
Potential Uses of the C4ISP Architecture Products

• Systematic Starting Point using standardized
  syntax and semantics for detailed analysis and
  definition of interfaces between OOS and ABCS 7.0
  Systems
• Systematic definition of common message types and
  specific IDs to support stimulation between TADSS
  and C4I systems
• Systematic definition of new or identification of
  existing API and services to support
  interoperability requirements
• Consistent and accurate system documentation to
  serve as reference for educational and management
  purposes as well as input to future
  specifications
• Collaborative development of solutions to
  interoperability problems at the architecture and
  design levels, rather than at the interface
  control level

16
Questions? Thank You