C4IM

1
C4I/MS Technical Reference Model Background
Overview Briefing for theProposed TRM Study
Group 23 May 2001

• Presented by
• Dr. Michael Hieb
• Chief Architect
• US Army Simulation to C4I Interoperability OIPT

2
TRM Information BriefingPurpose

• The Purpose of this Briefing is...
• ...to review the Technical Reference Model
• and give an overview as to
• its views, components
• and potential uses

3
Simulation Interoperability Workshop
SISO C4I Study Group Recommended that the TRM be
made into a SISO Product Fall 2000 SIW
4
TRM Information Briefing Agenda

• Why a TRM?
• Influences
• C4I/MS Interoperability TRMs
• Examples of TRM Use
• Evolution of TRM

5
Why a TRM?

• C4ISR field is too broad to discuss
  Standardization Efforts meaningfully
• Provide Taxonomy for more specific
  Standardization Efforts in C4ISR/Simulation
  Interoperability
• Provide comprehensive framework for assessment of
  interoperability between two systems (an example
  is shown later...)
• Identify requirements for future systems

6
A Comprehensive Approach to Interoperability
Interoperability of Legacy and Future Systems
Shared Solutions
Processes For Alignment
Reusable Component Interfaces
Common Standards
Common Data/Object Models
Alignment of Architectures
7
Missing?

• A well-defined framework for use as a reference
  against which to compare interoperability,
  interfaces and specific standards
• We propose to develop the TRM as a Standard
• Not a specific interoperability solution
• A technical reference model framework within
  which alternative approaches and designs can be
• Dissected, described, compared, and contrasted
  in order to
• Progress towards the complex goal of C4I/MS
  interoperability
• One interface/reference FOM does not fit all
• A standard TRM is a necessary next step to future
  interoperability standards between C4ISR and MS

8
TRM Information Briefing Agenda

• Why a TRM?
• Influences
• C4I/MS Interoperability TRMs
• Examples of TRM Use
• Evolution of TRM

9
Synthetic Natural Environment (SNE) Conceptual
Reference Model
Dr. Paul A. Birkel The MITRE Corporation pbirkel_at_
mitre.org
98F-SIW-018
1998 Fall Simulation Interoperability Workshop
10
Conceptual Reference Model

• Environmental Ground Truth forms the gaming board
• Military System Models comprise the gaming pieces
• The rules of play are tightly coupled to the
  configuration of the gaming pieces
• The gaming board is constantly changing
  configuration as a result of gaming piece
  state/actions as well as on its own ...

From Birkel, 98F-SIW-018
11
AMSO Standard Categories (1)

• Acquire
• Architecture
• Attrition
• C4I Integration
• Communication Systems
• Command Decision Modeling
• Cost Representation
• Data
• Deployment / Redeployment
• Dynamic Atmospheric Environments

Key to Developing C4I Standards!
12
AMSO Standard Categories (2)

• Functional Description of the Battlespace (FDB)
• Logistics
• Mobilization/Demobilization
• Move
• Object Management
• Semi-Automated Forces (SAF)
• Terrain
• Verification, Validation, Accreditation (VVA)
• Visualization

Key to Developing C4I Standards!
13
DII COE Technical Working Groups (1)
ABBREV. TECHNICAL WORKING GROUP ADM
TWG Administrative Services Alerts TWG Alerts CM
TWG Configuration Management Services COM
TWG Communication Services COP TWG Common
Operational Picture DATA TWG Data Access
Services DC TWG Distributed Computing
Object Management Services DTK TWG Developers
Toolkit HCI TWG Human Computer Interface Style
Guide
14
DII COE Technical Working Groups (2)
ABBREV. TECHNICAL WORKING GROUP MCGI
TWG Mapping, Charting, Geodesy Imagery MM
TWG Multimedia/Collaborative Services MP
TWG Message Processing MS TWG Simulation NET
TWG Network Management Services NTAG Windows NT
Advisory Group OA TWG Office Automation SEC
TWG Security Services RT AG Real Time Advisory
Group Viz 3D TWG 3-D Visualization
15
TRM Information Briefing Agenda

• Why a TRM?
• Influences
• C4I/MS Interoperability TRMs
• Examples of TRM Use
• Evolution of TRM

16
Interoperability Technical Reference Model (TRM)
C
4
Non-Persistent Data
I
Orders
Reports
Behavior Models Module
Imagery
S y s t e m
Tracks
Physical Models Module
Communications Effects
Communication Model
Environmental Models Module
Persistent Data
Unit Data (OB, TOE, Symbology, etc) Mission
Plan Information Comms Plan (Radio/Network Setup,
etc) Weather Data Terrain Specification
Run-time Framework
Scenario DB
Hieb Carr, 1998 CGF Conference
17
MS/C4ISR Conceptual Reference Model
Simulation
C4I
Transmit/Receive
Format
Information
Exercise Control/AAR/DC
Ressler, Hieb Sudnikovich, 1999
18
MS/C4ISR Conceptual Reference Model
Simulation
C4I
Information
C2
Communications
Environment
Exercise Control/AAR/DC
Ressler, Hieb Sudnikovich, 1999
19
MS/C4ISR Conceptual Reference Model
C2 Information
Simulation
C4I
Ressler, Hieb Sudnikovich, 1999
20
MS/C4ISR Conceptual Reference Model

Simulation
C4I
Information
Communications
- Physical network description - Logical network
description - Effects SNE EW IW - Network
management info
Ressler, Hieb Sudnikovich, 1999
21
MS/C4ISR Conceptual Reference Model
Simulation
C4I
Information
Environment
- terrain - air - ocean - space - weather -
multi-spectral emissions
Ressler, Hieb Sudnikovich, 1999
22
MS/C4ISR Conceptual Reference Model
Event Control/ AAR/DC Information
Simulation
C4I

• Start/Stop/Pause/Resume
• Resynch
• Time management
• Identify exercise
• Sim/Live status
• Troubleshooting
• Data Collection

Ressler, Hieb Sudnikovich, 1999
23
TRM Information Briefing Agenda

• Why a TRM?
• Influences
• C4I/MS Interoperability TRMs
• Examples of TRM Use
• Evolution of TRM

24
Example of using TRM in An Investment Plan
SIMCI Investment Strategy Task Matrix
A
B
C
E
D
Processes
Architectures
Standards
Data
Components
1) Initialization/Execution 2) Data Collection 3)
Orders 4) Situation Awareness 5) Unit Data 6)
Mission/Plan Data 7) Communications 8) Terrain
25
Example of using TRM in An Investment Plan
Categories from The TRM
Three Year Action Plan (3 of 6)
3 Year Cost/ FY00 Cost (k)
FY00
FY01
FY02
Task
Actionee
NA 1200/600 150/0 700/0 500/400 100/0 400/300
200/100
DMSO DISC4 STRICOM STRICOM CTSF EPG NSC NSC
C.0.1 C.0.2 C.0.3 C.1.1 C.1.2 C.2.1
C.3.1 C.4.1
26
FY00 Simulation-to- C4I Integration Strategy
Example of using TRM in An Investment Plan
Technical Reference Model Categories
FTI
C4I Jammer
Comm Flow Mgr
U
Comms
CECOM RDEC
PM, C4ISS
EPG
ABCS AAR Module
DCARS JCDB
Event Control AAR/DC
TSIU WRAP Funding
JCDB CMP Interface Research
RTM CMP
EPIU CMP

OIRS / JCDB
STORM CMP
Orders/ Reports
U
C2DIF, C2 Data
JCDB Integration
TSIU CMP
NSC
DCST JCDB

OTC/EPG
BML /JCDB
SMDC Battle Lab
JCDB Legacy C4I dbs
TRAC
Database Initialization Alignment
Data Alignment
ABCS OA/SA SIM
JCDB Legacy dbs
U
TODS
NSC
NSC

Terrain
SEDRIS / DTSS JMTK
U
JMTK
Univ.XXI
DISC4
CECOM
DSA Battle Lab
ATEC
TRADOC
STRICOM
SMDC
Legend
FY99 Effort Continued
DOI
Army Studies Prgm
Sponsors
U
SIMTECH
University XXI
AMIP
27
Example of Using the TRM to Identify Areas for
Standardization
C2 Information
orders reports message status plans overlays UTO,
OrgID, relationships, UIC Order of Battle
(OPFOR) coordinate system status
(Unit/Org)/location 3D visualization symbology/ope
rational graphics Information Exchange Plan
triggers (when, why) equipment characteristics
C4I
Simulation
28
Example of Using the TRM to Analyzean Interface
Development of an Interface Between a C4I
Collection Management System and an Intelligence
Sensor Simulation
Matthew R. Maier U.S. Army STRICOM /
NAWCTSD 12350 Research Parkway Orlando, FL
32826 407-384-3667 Matt_Maier_at_stricom.army.mil
Frederick G. Smith Allyn W. Dunstan OptiMetrics,
Inc. 3115 Professional Drive Ann Arbor, MI
48104-5131 734-973-1177, ext. 201 ext.
213 smith_at_omi.com, dunstan_at_omi.com
00S-SIW-025
2000 Spring Simulation Interoperability Workshop
29
Comparison of Reference Model Categories with
JCMT-to-TACSIM Interface Solutions

Example of Using the TRM to Analyzean Interface
00S-SIW-025
2000 Spring Simulation Interoperability Workshop
30
TRM Information Briefing Agenda

• Why a TRM?
• Influences
• C4I/MS Interoperability TRMs
• Examples of TRM Use
• Evolution of TRM

31
Selected C4I/MS TRM Papers
Carr and Hieb, Issues and Requirements for Future
C4ISR and MS Interoperability, 7th Conference on
Computer Generated Forces and Behavioral
Representation, 1998. Hieb Staver, 1998, The
Armys Approach to Modeling and Simulation
Standard For C4I Interfaces, Paper 98F-SIW-259,
1998 Fall Simulation Interoperability
Workshop. Hieb Blalock, 1999, Data Alignment
Between Army C4I Databases and Army Simulations,
Paper 98F-SIW-34, 1999 Spring Simulation
Interoperability Workshop. Timian, Hieb, Glass
and Staver, 1999, Using Standard Components to
Interface to Simulations, Paper 99S-SIW-035, 1999
Spring Simulation Interoperability
Workshop. Ressler, Hieb Sudnikovich, 1999,
C4I and MS Interoperability Reference Model,
Paper 99S-SIW-060, 1999 Fall Simulation
Interoperability Workshop.
On SISOs Recommended Reading List
32
Where to go?

• Help to create definitions of the categories in
  the TRM
• Assist in Preparing Reference Document
• Need International Participation
• Review/validate existing models
• Assist in further development and definition

33
Backups