Presentation, Spring 2000 SIW

1
SISOStudy Groupfor C4I-to-Simulation
Interoperability(SG-C4I)Interim Report27
March 2000
2
Outline

• Background
• SG-C4I Charter
• SG-C4I Membership
• SG-C4I Schedule
• SG-C4I Products
• Why are we here?
• The Road Ahead
• An Interoperability Technical Reference Model
• Summary

3
Background

• A key issue for the C4ISR MS community is the
  interoperability of live or real C4I systems and
  simulations
• Standards for C4ISR interfaces are being
  developed separately by both the C4I and MS
  communities
• Model and Simulation (MS) systems have
  standardized on certain protocols and
  architectures for interoperability, such as the
  High Level Architecture (HLA).
• The DoD C4I community is moving to standardize on
  the Joint Technical Architecture (JTA) and the
  Defense Information Infrastructure Common
  Operating Environment (DII COE)
• The international community is working to
  standardize message formats and develop common
  MS and C4I data models.

4
SG-C4I Charter

• The Study Group for C4I-to-Simulations
  Interoperability was chartered by SISO to
• Assess and recommend approaches that will support
  an appropriate and necessary level of
  interoperability between C4I systems and
  HLA-based simulations
• Deliver a report on the current "state of the
  art" of MS-to-C4I interoperability
• TOR presented to CC and SAC prior to Spring 99
  SIW
• First approved by CC on 14 March 1999
• SAC requested fleshing out of TOR
• Approved by EXCOM August 1999

5
SG-C4I Membership

• Officers
• SG-C4I Chair Joe Lacetera
• SG-C4I Vice Chair Don Timian
• CC POC Rick Severinghaus
• SAC POC Tom Mullins
• Forum POCs/Liaisons
• RPR-FOM Group Keith Briggs
• C4I Forum John Roberts
• SLT Chris Wertman
• General membership
• SG-C4I membership is open to all who wish to
  contribute
• there are currently over 100 members
• membership is attained by subscription to the
  SIW-ISG-C4I reflector

6
SG-C4I Schedule

• Preliminary meeting, Aug 99 _at_ CECOM (Ft Monmouth,
  NJ)
• Kickoff meeting Fall 1999 SIW
• Winter interim meeting, January 2000 _at_ SPAWAR
  (San Diego, CA)
• Working session 29 March, Spring 2000 SIW
• Summer interim meeting, mid to late July _at_ Air
  Force site in North East
• Final Meeting Fall 2000 SIW

7
SG-C4I Products

• Interim Report on process/progress
• Intermediate Products as developed (e.g., FOMs)
• SIW papers by subgroups
• Final Product Report
• Recommend approaches that will support an
  appropriate and necessary level of
  interoperability between MS and C4I
• A categorical bibliography and a partial
  MS-to-C4I interoperability lexicon
• Identify areas for further study and discussion
• Products/papers and other references available
  on C4I Document Library web

8
Why are we here?

• The motivation for improving the interoperability
  between simulations and live C4I systems include
• Simulation Based Acquisition
• Development of Doctrine and Tactics Techniques,
  and Procedures (DTTP)
• Train as you fight
• Embedded Training (both individual and
  collective)
• Course of Action Development and Analysis
• Mission Preview and Rehearsal
• Execution Monitoring

9
The Road Ahead Where we are now and where we
need to go.

• FAR TERM
• Common Databases
• Implicit Interoperability
• Full 2-Way Exchange
• Internal Black Box
• Plug and Play L/V/C C4I

• MID TERM
• Common Components
• Consolidated Interfaces
• 2-Way Feed
• Sims or C4I Initialize
• Sims Update C4I

• NEAR TERM
• Message Based
• Black Box Link
• Custom Point to Point
• Limited 2-Way Feed
• Sims Initialize C4I

2001
2004
Strategic
Constructive
Constructive
Strategic
Strategic
Legacy Constructive
H L A
Common Components
Virtual
Tactical
Tactical
Tactical

Legacy Virtual
Live
HLA Data Replication
Virtual
Platform
Platform
Platform
Database
Messages
Both
10
An MS-to-C4I Interoperability Technical
Reference Model
Simulation
C
Exercise Control Module
4
Non-Persistent Data
Orders
I
Reports
Behavior Models Module
Imagery
S
Tracks
Physical Models Module
y
Communications Effects
Communication Model
s
Environmental Models Module
t
e
Run Time Framework
m
Scenario DB
11
Interoperability of legacy and future Systems
MS
C4I
Shared Solutions
Processes For Alignment
Reusable Component Interfaces
Common Standards
Common Data/Object Models
Alignment of Architectures
12
Summary

• A key task for the MS community is to link with
  live or real C4I systems
• Within the C4I community there is a similar
  pressing need to link C4I equipment with
  simulations
• Up to this time C4I-to-simulation
  interoperability has been pursued separately by
  both the C4I and MS communities
• The primary task for the SISO SG-C4I is to
  articulate what MS-to-C4I interoperability is
  and to identify possible areas for joint
  investigation, by both the C4I and MS
  communities, that may result in standards
  applicable to both domains