Integration of Army

1
Integration of Army MS and C4I Systems
?
MS
C4I
http//134.11.235.51/ms-2-c4i
2
Why?
In order to accomplish full interoperability
between Army Models and Simulations (MS) and
Command, Control, Communications, Computers, and
Intelligence (C4I) systems, it is not sufficient
for MS developers to build in better messaging
capabilities into their systems. MS and C4I
systems must move towards integrating common C4I
components, as well as a common data model.
Hieb Timian, 1999 C2RT Symposium
3
ACII Components Army Common Information
Infrastructure
C4I Database
Data Distribution/ Replication Components
Applications
Comms Server
COE Message Processor
DII COE Component
DII COE Component
Timian, Hieb, Glass and Staver, 1999, Using
Standard Components to Interface to Simulations,
Paper 99S-SIW-035, 1999 Spring Simulation
Interoperability Workshop.
http//134.11.235.51/ms-2-c4i
4
Why Align Army MS and C4I Data Models?
Data
Dissemination
A
Specification
JCDB
B
C
1
D
HLA
Custom
4
Interface
Software
7
C4I System
FOM
Simulation
Hieb Blalock, 1999, Data Alignment Between Army
C4I Databases and Army Simulations, Paper
98F-SIW-34, 1999 Spring Simulation
Interoperability Workshop.
http//134.11.235.51/ms-2-c4i
5
Do we want to mandate the JCDB?

• Yes, but . . .
• JCDB only applies to MS-to-C4I Interfaces . . .
  .
• Harder problem is aligning C4I data models and
  MS object models. The JCDB is not sufficient.

DUSA(OR) 27 May 1999
6
Current C4I Data Models
Core Architecture Data Model (CADM)
Army Integrated Common Data Model (AICDM)
C2 Core Data Model
JTDM
JTDM JCDB Transitional Data Model
7
Two Track Approach

• Track One - Implement JCDB and CMP in MS-to-C4I
  Interfaces (we know how to do this . . . )
• Track Two - Evolution of MS and C4I data models
  into unified paradigm (more time required . . .
  )
• Army C4I data models evolving into object models
• Army C4I and MS data models communities do not
  share common vocabulary need to push x-talk
• Need to input Army MS requirements into Army C4I
  data models

8
Next Step - - DUSA(OR) DISC4 Warning Order

• Create an IPT and a Working Group
• IPT - - will be co-chaired by the Project
  Manager, C4I Simulation Systems and a Chief,
  Readiness and Engineering, Program Executive
  Office for Command, Control, and Communications
  Systems and will focus on improving
  Simulation-to-C4I Integration by folding common
  C4I components into the interfaces that link
  simulations and C4I systems, as well as how best
  to align the data models used by the MS and C4I
  communities.
• Working Group - - will be co-chaired by DISC4s
  Architecture Directorate and the Armys MS
  Standards Category Coordinator for Object
  Management and will focus on how best to align
  the data models used by the MS and C4I
  communities.

9
BACKUP SLIDES
10
What is the JointCommon Database?

• The JCDB conforms to the DoD C2CDM standards and
  focuses on data which is shared by two or more
  ABCS.
• The JCDB will be segmented throughout its
  iterative growth and each segment will be
  submitted for inclusion in the DII.
• The JCDB is comprised of several different
  components
• JCDB Transformation Data Model
• Joint Data Dictionary
• Joint Common Database
• Subscribe and Receive
• JCDB to COE Message Processor Interface
• JCDB Application Programmer Interfaces (APIs)

11
Potential to Leverage JCDB in MS-to-C4I
Interfaces
C4I System
Simulation System
AFATDS
ASAS
Data Replication
Comms Server
MCS
Translator
WARSIM ISP
FAADC2I
CSSCS
TOC
12
JCDB APIs

• APIs to the JCDB provided for puts, gets,
  deletes and utilities.
• SQL library routines included for all APIs.
• Use of puts is mandatory - gets, deletes
  and uitilities are optional.

13
The JCDB and MS-to-C4I Interfaces
MCS
JCDB API
JCDB Data Management Services (Intra-TOC)
MCS
Order Building Template Features
Eagle
JCDB
JCDB API
RTI Interface
RTI Interface
Eagle C4I Interface (DLRC Student Workstation)
Unit State Data
Unit Orders
RTI
14
Common Operating Environment Message Processor
(CMP)

• A multi-functional automated message processing
  system
• (both inbound and outbound) using a standard
• Graphical User Interface.
• Functional capabilities include
• Internal Routing
• Extraction of Data from Messages or Databases
• Standing Requests for Information
• Automatic and Interactive Message Generation
• Validation of Inbound and Outbound messages
• Autofill of Data from Systems Database to
• a Message or Application

15
Using the CMP
Short Term
C4I System
Simulation System
CMP
Comms Server
Comms Server
CMP
WARSIM ISP
MCS
16
Function Description of the CMP

Di s c r i m i n t o r
Parsing/ Validation
SIM
A
Journal Server
Comms Server
P
Application orDatabase
I
Au t o f i l l
Message Preparation
s
CMP User Interface
Note SIM is System Interface Module, NOT
Simulation
17
CMP APIs

• The CMP APIs provide the user with the ability to
  process a specific message into the structures
  used by the CMP and then access certain types of
  information about the message.
• The CMP APIs are for the Java CMP version and
  follow standard Java programming conventions.

18
CMP Implementation
Some Message Formats Supported
ARMY FBCB2
USMTFJVMFMARINE MTSOTH Gold STANAG
MARINETACTICALSYSTEMS
MCS
GCCS
CMP
CMP
FADC2I
AFATDS
ATCCS
USAFCTAPS
CMP
CMP
NAVYJIMCS
CMP
ASAS
CSSCS
CMP
CMP
Comms Server
19
Proposed TSIU Federation Diagram
JCDB
MCS Block IV
JCDB Data Management Service (Intra-TOC)
USMTF Message Exchanges
JCDB
FED- PROXIE
EADTB
EADSIM
CMP
RTI Interface
RTI Interface
RTI Interface
TSIU
Unit Orders, Unit Status Data, Sensor Data,
Intel Data
Battlefield Geometry Free Text
Unit Status Data
Unit Orders
RTI