WARSIM 2000 and C4I Device Initialization

1
WARSIM 2000 and C4I Device Initialization
Jude Anthony
Science Applications International
Corporation 12479 Research Pkwy Orlando, FL
32826 [phone]
2
Overview

• Why WARSIM needs to initialize C4I devices
• What data WARSIM needs to initialize
• How WARSIM interfaces with the Training Audience
• Initializing ABCS 4.x devices
• Initializing ABCS 6.x devices
• Initialization in the future

3
Why WARSIM Initializes C4I Devices

• WARSIM has a requirement to reduce exercise
  preparation time
• Customized scenario generation tools will be
  faster than preparation via organic devices
• Need some way synchronize the simulation state
  with the state perceived by the Training Audience
  through their C4I devices
• WARSIM calls this state transfer download

4
WARSIM Initialization Data

• What WARSIM needs an accurate presentation of
  the current state
• Friendly and enemy unit locations
• Orders
• Supplies
• UTO
• Collectively WARSIM refers to these as the TAs
  Perceived Truth

5
Representing Perceived Truth

• Option 1 Use the JCDB

Simulated Unit
JCDB
Perceived Truth
Simulated Unit
JCDB
Perceived Truth
Simulated Unit
JCDB
Perceived Truth
6
Representing Perceived Truth

• Option 2 Design a WARSIM Data Store

Simulated Unit
Perceived Truths
World Model
Fact
Fact
Simulated Unit
Fact
Fact
Simulated Unit
Fact
7
WARSIM Interfaces
All TOC communications are routed through WARSIM.
The CPIM and CPI constitute the necessary
physical and logical connections.
CPIM
WARSIM
TOC
CPI
8
The CPIM and the CPI

• The CPIM is a physical interface, routing
  messages and communications.
• Includes hardware for voice communications
• The CPI is a physical and logical interface,
  handling both simulation and C4I data
• Physical configuration is highly flexible

9
The CPIM and its Contents

• A router
• Allows WARSIM to appear as a C4I device on the
  TOC network
• No role for simulations as yet
• Still necessary to modify address data so
  messages get sent to WARSIM
• Disconnects the TOC from the MPE net
• Sound cards for each radio net
• Wireless LAN equipment, including crypto

10
CPI Design

• Simulation and C4I Interface (C4II) sides
• Simulation side C with Java interfaces to the
  C4I side
• C4II side Java with interfaces depending on the
  C4I software accessed
• Currently includes a JCDB and CMP interface
• Linked via Java RMI
• Could be more than one physical machine

11
C4I Device Configuration
C4I Device

• Every C4I Device has common elements
• JCDB
• CMP
• DCM

JCDB
DCM
CMP
Device-Specific Databases and Code
12
Downloading ABCS 4.x and 5.x

• Proof of Concept
• Only the JCDB was considered, and only a minor
  subset of the data available
• Created an executable using the JCDB API which
  used its command-line arguments to insert data in
  the JCDB
• Placed the executable on an MCS
• Connected to MCS with telnet, ran the executable,
  examined MCS display

13
Downloading ABCS 4.x and 5.x

• What We Found
• Data was inserted in the JCDB as expected
• A different interface than telnet and command
  line arguments would be necessary for faster,
  larger downloads
• No reason this approach couldnt be extended to
  device-specific databases by executing SQL in the
  application

14
Downloading ABCS 4.x and 5.x

• Some Problems
• Passwords were necessary to access databases and
  systems not always the same
• TCP/IP wrappers and other security features would
  need to be turned off
• Database schemas were not always available
• ABCS 6.x security regulations wouldnt allow an
  application to be inserted on the C4I devices

15
Downloading ABCS 6.x

• How could we use the JCDB API if we couldnt put
  an application on a C4I device?
• Add a JCDB to our own interface, look like a
  device in the TOC, and let the built-in data
  replication mechanism (SR) handle the data
  transfer.

CPI
Simulation Interface
JCDB
16
Using the JCDB for Download

• Advantages
• Satisfied ABCS 6.x security problems
• No special access necessary
• Data transfer software already written
• JCDB API available

• Disadvantages
• Must be part of the TOC network
• Need to modify addressing data for automatic data
  transfer
• No access to anything not in the JCDB API

17
More Than One Way

• If a single solution couldnt do everything, more
  than one solution would be necessary.
• Many C4I devices have the capability to
  initialize their databases via messages received
  from similar devices.
• WARSIM C4II already used CMP to format and send
  messages, so adding this capability wouldnt be
  too onerous.

18
Downloading with Messages

• Advantages
• Accesses data outside JCDB API
• Necessary hardware and software already available
  for message transfers
• Few changes when devices are upgraded

• Disadvantages
• Not always processed automatically, requiring
  operator intervention
• All messages formats not published
• STILL doesnt cover all the data

19
One Last Try

• Besides transferring information to C4I devices,
  WARSIM also has requirements to accept data from
  C4I devices. One of the solutions considered was
  Document Content Analysis and Retrieval System
  (DCARS).
• Although DCARS is designed to retrieve data from
  a C4I device, it has access to all the data a
  device produces. If it could be modified to
  populate data, WARSIM download we be completed.

20
A Quick DCARS Overview
DCP
The DCG gives the DCM SQL and system commands to
execute on an immediate or regular basis. All
data is collected at the DCP. The DCM is
capable of executing arbitrary SQL or system
commands.
21
Modifying DCARS

• WARSIM needs to insert data, not just query it.
  The DCM is capable of executing SQL and system
  commands that do this.
• The DCARS system is controlled by a user
  interface at the DCP. WARSIM must use its own
  interface.
• WARSIM needs to store data at each C4I Interface,
  not at a single DCP.
• The easiest solution would be some way to access
  the DCM directly.

22
Downloading With DCM

• If WARSIM can make a custom DCG to access the
  DCM, all data can be downloaded.

TOC
WARSIM
C4II
JCDB
Simulated Unit
DCG
CMP
23
Download in the Future

• The ASDSM is designed to provide simulations with
  direct access to the DCM.
• WARSIM and DCARS teams are expected to work on
  ASDSM concurrently.
• End product would be available for other
  simulations to use and modify.
• ASDSM would be a single way to retrieve and
  insert all the data in a C4I database!

24
Conclusions

• WARSIM uses the JCDB API and messaging to
  initialize C4I devices.
• It may be possible to gain more direct access to
  device databases through the DCM.
• Developing interfaces to C4I devices is a
  difficult task due to the rate of upgrade and
  lack of published, stable interfaces.
• When all DII COE devices access data through a
  common component, C4I device initialization will
  become easier.