C4IM

1
C4I/MS Technical Reference Model Interim
Report Briefing for theFall 2001 SIW 11
September 2001

• Presented by
• Maj. Lynda Myers
• Study Group Chair

2
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

3
Introduction

• TRM Requirements
• 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
• Study Group Formation

4
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

5
MS Reference Models

• The House Diagram
• C4I/MS Interoperability TRM
• C4I/MS Interoperability Conceptual Reference
  Model
• The General Unified Model (GUM)

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
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
8
C4I/MS Interoperability Conceptual Reference
Model
Simulation
C4I
Transmit/Receive
Format
Information
Exercise Control/AAR/DC
Ressler, Hieb Sudnikovich, 1999
9
C4I/MS Interoperability Conceptual Reference
Model
Simulation
C4I
Information
C2
Communications
Environment
Exercise Control/AAR/DC
Ressler, Hieb Sudnikovich, 1999
10
C4I/MS Interoperability Conceptual Reference
Model
C2 Information
Simulation
C4I
11
C4I/MS Interoperability Conceptual Reference
Model

Simulation
C4I
Information
Communications
- Physical network description - Logical network
description - Effects SNE EW IW - Network
management info
12
C4I/MS Interoperability Conceptual Reference
Model
Simulation
C4I
Information
Environment
- terrain - air - ocean - space - weather -
multi-spectral emissions
13
C4I/MS Interoperability 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
14
General Unified Model (GUM)
Simulation
C4I System


User Interface
User Interface

• Provides GUI displays for user.
• Menus, command line interfaces

• Provides GUI displays for user.
• Menus, command line interfaces

Mgmt/Execution
Mgmt/Execution

• Mgt functions for execution
• Examples
• Event scheduler, or sim engine
• Infrastructure SW( e.g. DIS, HLA)

• Mgt functions for execution
• Operating System, Communications, etc

Data
Data
Persistent data (such as terrain
files) Non-persistent data (e.g. unit location,
heading, msgs) Simulated ground truth Simulated
perceived data
Persistent data (such as terrain
files) Non-persistent data (e.g. unit location,
heading, msgs) Only perceived data. NOT ground
truth


Algorithms
Algorithms
Formulas, rule-based algorithms, and other
mathematical constructs. These algorithms tend
to be strictly associated with representation of
some physical phenomenon
Few exist within a C4I system.
15
GUM Use Case Modeling
Simulation
C4I System


User Interface
User Interface
Map Displays
Command Interface
Msg Displays


Mgmt/Execution
Mgmt/Execution
Sim Engine


Data
Ground truth data
Perceived truth data
Data
C4I DB
Tactical Msgs Proc
Msg Gen


Algorithms
Algorithms
Sensor, Comm Algorithms
Attrition Algorithms
Movement Algorithms
Use Case Simulation generation of C4I messages
(Training)
16
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

17
Other Related Reference Models

• NATO C3 Technical Architecture
• NC3TA TRM
• NCOE Component Model
• NC3TA Interoperability Reference Model
• Levels of Information Systems Interoperability
• DoD and US Federal TRM

18
NC3TA TRM
19
NCOE Component Model
NATO Common Operating Environment Component Model
20
The NC3TA Interoperability Reference Model

• Objective Measure the Degree of
  Interoperability of Systems
• Degree 0 Not connected
• Degree 1 Unstructured Data Exchange
• Network, Document Exchange, Messages
• Degree 2 Structured Data Exchange
• Network Management, Data Object
  Exchange/Replication, Web
• Degree 3 Seamless Sharing of Information
• Common Data Exchange, System and Security
  Management
• Degree 4 Seamless Sharing of Information
• Common Information, Knowledge Bases, Distributed
  Applications

21
Incremental Levels of System Interaction
Level 4 Universal
Shared Systems
Level 3 Integrated
Shared Applications, Data
Level 2 Distributed
Heterogeneous Product Exchange
Level 1 Connected
Homogeneous Product Exchange
Level 0 Isolated
No Electronic Connection (Manual)
22
Linking MS and C2 Domains Levels of
Information Systems Interoperability(LISI)
Procedures Applications Infrastructure Data
23
DoD TRM
Interfaces View
Services View
24
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

25
Guiding Principles for the TRM

• Comprehensive
• Spectrum of interoperability
• Range of technologies
• Data exchange methodologies
• Describing human aspects
• Easy to Interpret
• Build on existing models
• Use well defined terms
• Traceable
• Well documented
• Allows users to check TRM covers critical areas
  of interest

• Usable
• Allow end users/sys developers communicate with
  each other across domain and technology
  boundaries
• Help end users trace between problem space and
  solution space
• Independent
• Not tied to specific application architectures,
  designs, or implementations
• Must be flexible/adaptable enough to endure over
  time

26
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

27
Domain Challenges

• Level of Resolution or Abstraction
• Both C4ISR and MS represent abstraction of
  reality
• Time Synchronization
• C4ISR interested in near real-time
• MS interested in faster/slower than or in
  real-time
• Varied Perceptions
• C4ISR sees only one reality
• MS sees absolute ground truth and several
  perspectives of virtual reality
• Cognitive Discontinuities
• Different systems will look for different levels
  of information
• Configuration Management
• A CM process will be developed provide oversight
  of TRM development activities that creat design
  products/artifacts

28
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

29
Initial Review of Use Cases

• Use Cases are a construct for analysis of TRM
  against guiding principles
• Need communities of interest to champion
  development of Use Cases and assess results of SG
  effort against those cases
• Use Case examples review in paper
• Air Traffic Management (ATM)
• DoD Test Range Operations
• Track Data Management

30
TRM SG Interim Report Briefing Agenda

• Introduction
• Overview of MS Reference Models
• Overview of Related Reference Models
• Guiding Principles for the TRM
• Excursion into Domain Challenges
• Initial Review of Use Cases
• Conclusion

31
Conclusion

• Road Ahead
• Expand SG participation from international
  community and inter-disciplinary interests
• Develop generalized TRM following guiding
  principles
• Continue development of use cases
• Develop consensus recommendation to SISO on
  adoption of SGs TRM
• If recommended, take steps to move TRM toward a
  formal product

32
Thank you

• Questions?

33

• Backup Slides

34
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
35
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
36
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
37
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
38
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