Atlantic Consulting Services, Inc'

1
Simulation Interoperability Workshop (SIW) Fall
2001 Simulation to C4I Interoperability For
Planning and Decision Support Paper Number
01F-SIW-004 10 14 September 2001 John D.
Roberts Atlantic Consulting Services (ACS),
Inc. Shrewsbury, NJ, 732-460-9416 jroberts_at_acsinc-
nj.com
2
Introduction

• Problem The Army has identified a need for
  interfacing real C4I Systems with MS to create a
  realistic simulation/stimulation environment that
  will allow warfighters to train as they fight
• Objective - Investigate approaches for defining
  interoperability standards between MS
  applications and Army C2 Systems in the area of
  Planning and Decision Support.
• Contract - CECOM sponsored Small Business
  Innovation Research (SBIR)
• Phase I 6 month effort from Dec 2000 through
  June 2001
• Phase I Option 4 month effort started in August
  2001
• Phase II Anticipated award November 2001 (2 yr
  effort)

3
Approach

• Phase I Tasks
• Review the Armys Decision Making Process
• Army Command and Control (C2) Systems Survey
• Survey of Existing and Emerging Modeling
  Simulation (MS) Applications
• Identify Interoperability Requirements between C2
  Systems and MS Applications
• Develop Initial C2 Object Model for
  planning/decision support.

4
Army Doctrine Review
Military Decision Making Process (MDMP) FM 101-5
Additional Resources - FM 34-130 - FM
100-5 - FM 100-6 - FM 101-5-1 - ST 100-3
- ST 101-5
5
C2 Systems Survey
Initial Focus on MCS Information Exchange within
ABCS
USMTF
A423
AMD W/S
C400
ASAS-RWS
JVMF
S201
S302
S507L
A423
C400
S201
S302
S507L
MCS
FBCB2
A423
C400
C400
S201
S302
S302
S507L
S507R
S507L
A423
S201
A423
S302
C400
C523
AFATDS
CSSCS
S302
C400
G880
S201
S302
S302
S507L
S507L
S507R
IMETS
DTSS
S507S
S509
6
MS Applications Survey
Sources AMSO, MSRR, DMSO, MSIAC, etc.
Focus on Existing and Emerging Combat Simulations
Eagle
WARSIM
7
Analyze Interoperability Requirements

• C2 Systems
• Message Exchange (USMTF, JVMF)
• Relational Databases (i.e., JCDB)
• MS Applications
• Object-oriented data models
• Standard Simulation Protocols (DIS, ALSP, HLA)
• Comparison
• C2 Systems Convey Plan Data as Free Text
  (Messages JCDB)
• Simulations use highly structured Data
  Representations
• Conclusions
• Both sides need to compromise
• C2 Systems better structure content of
  Databases (Doctrine)
• Simulations Better align object models to
  Doctrine
• Develop mapping between databases and object
  models

8
Develop C2 Object Model

• Focus on Information Contained in the OPLAN/
  OPORD
• Identify Key high level objects
• Plan Object (5 Paragraphs Task Org Header)
• Activity Object (Who, What, When, Where, Why)
• Identify Attributes and Relationships
• Define Objects associated with Parts of the Plan
• Define Common Base objects (DTG, Location,
  Relationship, Control Type, etc)

9
Key High Level Objects
 
 
10
C2 Object Model High Level View
PlanObj
Header PlanHeaderObj referenceUnit
UnitObj taskOrganization TaskOrgObj situationPar
agraph SituationObj missionParagraph
MissionStatementObj executionParagraph
ExecutionObj serviceParagraph ServiceSupportObj
commandParagraph CommandAndSignalObj
11
SBIR Phase I - Option
Bridge the Gap Between Phase I and Phase II Work
C2 Object Model
Data Mapper
Plan
Plan
HLA
SQL/ODBC
HLA
SQL/ODBC
JCDB
C2 System BPV/DaVinci)
Simulation (OTB)
12
SBIR Phase II Proposed Effort

• Demonstrate C2 Object Model
• Apply to Mission Rehearsal
• Apply to Execution Monitoring
• Apply to COAA/War-gaming
• Evolve C2 Object Model
• Maintain/update C2 Object Model
• Incorporate structures/concepts from BML
• Align C2 Object Model with Tactical Data Models

13
Coordination with SIMCI OIPT

• Simulation C4I Interoperability (SIMCI)
  Overarching Integrated Product Team (OIPT)

Provide recommendations on Army-level policy to
the Army Modeling and Simulation Executive
Council (AMSEC) for improving interoperability
between the MS and C4I Domains.

• Membership on Council of Architectures
  (CECOM/ACS)
• Participated in Data Products meeting in December
  00 and February 01.
• Participated in BML Conference in April 01
• Coordinate with FY02 SIMCI sponsored BML effort
  (ref 01F-SIW-067)
• Provide testbed for evaluation of BML concepts as
  part of SBIR Phase II effort.

14
Summary

• There is a need to develop Interoperability
  Standards between C2 Systems and MS
• SBIR Phase I resulted in an initial C2 Object
  Model focused on planning and decision support.
• Phase I Option will show an initial capability to
  exchange planning information and serve to flesh
  out the C2 Object Model
• SBIR Phase II will provide an opportunity to
  incorporate BML concepts and structures within a
  testbed environment for evaluation.

15
--- BACKUPS ---
16
Interoperability Vision Where it fits
Interoperability
Interoperability
of legacy and
of legacy and
MS
MS
C4ISR
C4ISR
future Systems
future Systems
Shared
Shared
Solutions
Solutions
Reusable Component Interfaces
Reusable Component Interfaces
Common
Processes
Processes
Common
Data/Object
For
For
Standards
Models
Alignment
Alignment
Alignment of
Alignment of
Architectures
Architectures
17
C2 Object Model Plan Object
PlanObj
Header PlanHeaderObj referenceUnit
UnitObj taskOrganization TaskOrgObj situationPar
agraph SituationObj missionParagraph
MissionStatementObj executionParagraph
ExecutionObj serviceParagraph ServiceSupportObj
commandParagraph CommandAndSignalObj