OOS C4I Adapter vs' the SISO C4ISR TRM: A Comparative Analysis

1
OOS C4I Adapter vs. the SISO C4ISR TRM A
Comparative Analysis

• Presented by
• Sept. 21, 2004
• Paper Authors
• Dr. Robert Wittman
• Stephen Lopez-Couto

2
OneSAF C4I Adapter
Training Audience
Train As We Fight Seamless Sim to C4I Interface
OneSAF Objective System
Brigade
Email
Battalion
USMTF
VMF Pkg 11
Company
FDL
Simulation
JVMF
Platoon
Forward Area Air Defense Data Link (FDL) Joint
Variable Message Formatting (JVMF) Global Command
and Control System Army United States Message
Text Formatting (USMTF) Variable Message
Formatting Package 11 (VMF Pkg 11)
3
SISO C4I/Sim TRM House Diagram
Interoperability of Legacy
MS
and Future Systems
C4ISR
Shared Solutions
Reusable Component Interfaces
Processes
for
Common
Common
Alignment
Standards
Data/Objects
and
and Tools
Models
Migration
Alignment of Architectures
4
OOS Alignment

• File Based
• ABCS LDIF
• Service Based
• CMP
• GTCS
• RTI
• DIS

Interoperability of Legacy
MS
and Future Systems
C4ISR
Shared Solutions
Reusable Component Interfaces
Processes
for
Common
Common
Alignment
Standards
Data/Objects
and
and Tools
Models
Migration
Alignment of Architectures
5
OOS Alignment
Interoperability of Legacy
MS
and Future Systems
C4ISR

• Standards
• JVMF
• USMTF
• HLA/DIS
• Tools Based
• CMP
• GTCS

Shared Solutions
Reusable Component Interfaces
Processes
for
Common
Common
Alignment
Standards
Data/Objects
and
and Tools
Models
Migration
Alignment of Architectures
6
OOS Alignment
Interoperability of Legacy
MS
and Future Systems
C4ISR

• Simulation
• Runtime Data Model (RDM)
• C2DM
• Organizational Objects Interactions
• Physical Objects Interactions
• Military Scenario Definition Language (MSDL)
• C4ISR
• C2 Information Exchange Data Model (C2IEDM)
• BML

Shared Solutions
Reusable Component Interfaces
Processes
for
Common
Common
Alignment
Standards
Data/Objects
and
and Tools
Models
Migration
Alignment of Architectures
7
OOS Alignment
Interoperability of Legacy
MS
and Future Systems
C4ISR

• OOS Development
• Battle Command and Control Operational
• Architecture (BCCOA)
• C4I Support Plan (C4ISP) Development
• Software Blocking

Shared Solutions
Reusable Component Interfaces
Processes
for
Common
Common
Alignment
Standards
Data/Objects
and
and Tools
Models
Migration
Alignment of Architectures
8
OOS Alignment
Interoperability of Legacy
MS
and Future Systems

• C4ISP
• Simulation and C4ISR Product
• Process Alignment

C4ISR
Shared Solutions
Reusable Component Interfaces
Processes
for
Common
Common
Alignment
Standards
Data/Objects
and
and Tools
Models
Migration
Alignment of Architectures
9
Functional Interfaces
10
What Needs To Be Interfaced?

• C4ISR Systems
• In FIG the box is empty
• This lack of detail is interpreted to mean that
  the internal C4ISR system details are unimportant
  to interoperable simulation systems when shown at
  this level
• OneSAF interoperates with the Armys ABCS
• These systems have a generally common message
  creation and transmission scheme, but
• They all have stovepipes that must be dealt with
  

11
What Needs To Be Interfaced?

• Simulation Systems
• FIG shows six subsystems that most simulations
  contain.
• OneSAF includes composable components that align
  to each of these
• One element left off of the diagram is the C4I
  Interoperability subsystem.
• OneSAFs is the C4I Adapter

12
The Interfaces

• The primary reason for a simulation to evaluate
  the C4ISR TRM is to assist in the discovery and
  definition of the data exchanges that need to
  occur between the C4ISR systems and the
  simulation.
• The TRM contains four categories of data exchange
• Simulation Service Interactions
• Persistent Data
• Non-Persistent Data
• C4ISR System Service Interactions
• OneSAF interacts with the Armys ABCS using all
  four of these information exchange categories.

13
The Interfaces

• Simulation Service Interactions
• Simulation Metadata
• Time Synchronization
• Execution Control
• The TRM describes as data which would allow a
  simulation to start, stop, pause, checkpoint,
  accelerate, etc. a scenario while it is in
  execution mode.
• Simulations can do this
• Current C4ISR Systems Cannot
• Visualization
• Bi-directional Overlay transmission
• Data Collection
• OneSAF performs its data collection functions in
  unison with its task of transmitting messages.
• Simulation Effects
• When in Simulation Comms mode OneSAF can inject
  communication effects onto all inter-TOC messages
  traffic

14
The Interactions

• Non-Persistent Data
• Orders
• OneSAF supports two way messaging generated and
  reacted to internally by models
• OneSAF can receive simple overlays from ABCS and
  display them on the PVD
• Reports
• OneSAF has the capability to create and transmit
  a number of report type messages
• Imagery
• OneSAF does not exchange any imagery data with
  C4ISR systems.
• Tracks
• The capability to create tracks of both ground
  and air units on the appropriate ABCS systems
  will be included in OneSAFs FOC functionality.
• Unit Data
• In the most recent TRM update this category was
  moved from Persistent to Non-Persistent
• From the OneSAF perspective this is still viewed
  as persistent
• Task Organizations are aligned during the pre-ex
  phase and remain static during runtime (when
  executing with live C4I)
• In the future the ability to update live C4I TOs
  on the fly may be implemented.

15
The Interactions

• Persistent Data
• Mission and Plan Information
• Sent to live C4I in the same manner they would
  receive it for a real event
• UTO was moved to Non-Persistent, why not Mission
  and Plan Information
• Fargo's
• Communications Plan
• OneSAF does not create a specific communications
  plan.
• We do create internal communication networks
• These must align to the C4ISR networks
• The C4ISR networks are configured via the task
  organizations.
• Weather Data
• OneSAF has the capability to represent dynamic
  weather conditions.
• In a thin slice of time weather may be
  persistent, but it can rapidly change.
• There are presently no avenues with which to
  dynamically affect weather on any of the C4ISR
  systems that OneSAF interoperates with,
• It is a stretch to consider weather data
  persistent.
• Terrain Specification
• Terrains must be aligned
• The persistent portion of terrain is ensuring
  that the piece of earth represented is equivalent
  between the systems.
• Once execution begins terrain can become a very
  non-persistent thing

16
The Interactions

• C4I System Service Interactions
• System Health/Heartbeat Status
• FBCB2 requires periodic heartbeats
• Depending on the configuration of the simulation
  exercise the heartbeat will not always have to be
  created by OneSAF
• Component Service Protocols
• OneSAF currently uses the GTCS to handle most
  acknowledgement and handshaking requirements.
• We are working on a Simulation Commserver that
  will better support simulations while performing
  many of the same tasks as the GTCS

17
Questions

• Thanks