Don Timian

1
Integrating Army MS-to-C4I Requirements into
the DII COE
Don Timian donald.timian_at_sterling-fsg.com Stephen
R. Whitson swhitson_at_mitre.org Richard J.
Hyde rich.hyde_at_hood-ctsfmail.army.mil
00F-SIW-008
2
Previous Papers

• 98F-SIW-259 - - Hieb, M.R., Glass, J., and
  Staver, M.J. The Armys
• Approach to Modeling and Simulation Standards
  for C4I Interfaces
• 99S-SIW-035 - - Timian, D.H., Hieb, M.R.,
  Glass, J., and Staver, M.J.
• Using Standard C4I Components to Interface
  to Simulations
• 99F-SIW-036 - - Newcomb, M., Gustafson, J., and
  Nguyen, P. The
• WARSIM C4I Interface
• 00F-SIW-011 - - Timian, D.H. Hicks, M.W., and
  Hieb, M.R. An
• Approach for Using DII COE Components to Link
  Simulations and
• C4I Systems A Case Study Using the CMP

3
10M a year . . .
TACSIM
Annually, the Army spends at least 10M to
maintain limited interoperability between it
suite of analytical and training simulations and
it division and below C2 systems.
RTM
BCIM
TSIU
STORM
DLRC
4
So where do we go from here?
Consider integrating Defense Information
Infrastructure Common Operating Environment (DII
COE) components into MS-to-C4I interfaces
But were not talking plug and play
5
What is the DII COE?
Think of it as an Operating Environment . . . a
collection of re-useable software that collate
common support applications . . . that can run on
either Windows or UNIX platforms.
6
The DII COE Architecture
7
DII COE Technical Working Groups
Mapping, Charting, Geodesy, Imagery
(JMTK) Modeling and Simulation Multimedia/Collabor
ative Services Message Processing (CMP) Network
Management Services Office Automation Real
Time Security Services Technical Working
Group Visualization
Administrative Services Alerts Configuration
Management Communication Services (Comms
Server) Common Operational Picture (COP) Data
Access Services Distributed Computing
Object Management Services Developers
Toolkit Human Computer Interface Style Guide
MS TWG http//www.dmso.mil/index.php?page181
8
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
• 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

9
Why use Common C4I Components?
MCS
GCCS
CMP
CMP
MARINETACTICALSYSTEMS
FADC2I
AFATDS
ATCCS
CMP
CMP
ASAS
CSSCS
NAVYGCCS-M
CMP
CMP
Some Message Formats Supported
USMTF, JVMF, VMF Package 11, Over-The-Horizon
Gold (OTH Gold)
Messages
Money makes the world go around
10
The Army CommonInformation Infrastructure
C4I Database
Data Distribution/ Replication Components
DII COE Infrastructure Service
Applications
Out
Army Foundation Software
Comms Server
In
CMP
DII COE Common Component
C2R
11
Some Background Information

• In November 1999 the Armys DISC4 and DUSA(OR)
• establish the Simulation-to-C4I
  Interoperability (SIMCI)
• OIPT to focus on better ways to make Army MS
  and C4I
• systems interoperable.
• One of the Working Groups within the SIMCI OIPT
  is a
• Consortium of Army MS-to-C4I Interfaces
  whose
• task last year was build off of the
  Warfighter
• Simulation 2000s CMP-based Interface work
  (which
• was initially funded in FY98 by the DISC4).

12
Conceptual SIMCIAPI to CMP
ABCS 6.x - Generalized
CMP API
ASAS
- Inbound/Outbound Processing - C APIs -
Documentation and Tools - Additional Message
Protocols
CMP
Warfighter Simulation 2000
MCS
TOC Server
AFATDS
Enhanced Tactical Simulation Interface Unit
AMDWS
Run Time Manager
Eagle
CSSCS
JCDB
http//simci.org
13
Some of the ConsortiumsRecommended Changes

• CMP improve their message inbound and outbound
  processing
• and performance requirements
• CMP to provide software upgrades to accommodate
  both
• Java and C
• Additional CMP documentation and tools to
  support building
• CMP message databases
• Request CMP support additional message
  protocols. Specifically,
• some of the unique ATCCS message protocols
  such as the CSSCS
• USMTF Like database updates and AFATDSRO.

14
Key Points andRecommendations for SISO

• Key points that impact on MS-to-C4I
  interoperability
• It is technically possible to use a DII COE
  component in a MS-to-C4I interface and the DII
  COE TWG are willing to make changes to their APIs
  to support MS
• While the DII COE has most of the technical and
  process components needed, it is still necessary
  to align or merge MS and C4I data models and
  resolve the time management issue
• Recommendations for the specific forum
• SISO needs to work with DII COE MS TWG to
  develop a roadmap and help coordinate Service
  efforts
• __ Highlights a need for further action as
  follows
• __ Points towards a need for further research to
  better scope need for future standards
• __ Raises issues that merit initiating new
  standards development activities

?
?
15
Acknowledgements

• For their feedback and assistance, the authors
  would like to thank
• Mr. John Diem (Chief, National Simulation
  Center's Digital Integration Office at Fort
  Hood, Texas)
• Mr. Gene Hardin (Coleman Research Corporation)
• Dr. Michael Hieb (AB Technologies/IITRI)
• Mr. Hank Rose (Computer Sciences Corporation)
• Mr. Ron Sprinkle (AEgis Technologies Group)
• Ms. Susan Wright (Institute for Defense Analysis)