Stimulating the Army Tactical Command

1
Stimulating the Army Tactical Command Control
System (ATCCS) Using the Run Time Manager (RTM)
Concepts and Implications

• 99S-SIW-162
• Antonio R. Paola [phone],
  paola_antonio_at_bah.com
• Richard L. Ressler [phone],
  ressler_richard_at_bah.com
• BOOZALLEN HAMILTON, INC.

2
Outline

• Background on ATCCS and RTM
• Stimulation Concepts
• Standards and Implications

3
The Army Battle Command System (ABCS)

• Enable Commanders at all levels to exploit
  digitization
• Simulations are an integral piece.
• Stimulation Focus on
• Army Tactical Command and Control System (ATCCS)
• Force XXI Battle Command Brigade and Below
  (FBCB2)
• Global Command and Control System -Army.

4
Acronym Valley

• MCS Maneuver Control System
• ASAS All Source Intelligence System
• AFATDS Advanced Field Artillery Tactical Data
  System
• FAAD Forward Area Air Defense System
• CSSCS Combat Service Support Control System

5
C2 Network Stimulation Links Live and Simulated
Networks

• System Stimulation
• Providing automated interactions with a given
  system by emulating the presence of other
  systems.
• C2 Network Stimulation
• Providing automated interactions between the live
  and the simulated portions of a C2 network.

6
The RTM Stimulates C2 Networks

• The RTM is a small suite of hardware and software
  that stimulates a live C2 network by managing the
  transformation and exchange of data between the
  live and the simulated portions of the network.

7
III (US) Corps Warfighter Exercise

• Each WFX is an intensive 7-10 day exercise.
• Provide Division and Corps commanders a Combat
  Training Center experience.
• III Corps WFX occurred in Dec 98
• Involved command posts at Corps, Division, and
  Brigade level with Battalions as simulation role
  players.
• Simulations included CBS, CSSTSS, and EADSIM.
• One of the largest ATCCS stimulation events.

8
Stimulation for the III Corps WFX

• MCS - S507L (Unit Location)
• ASAS - S303 (SALUTE Report)
• FAAD - F-3 (Air Tracks) F59-63 (TMD)
• Fire Support - Artillery Movement and Request for
  Fire Cycle
• AFATDS, IFSAS, FDS
• 10 CCSIL Messages with Fort Sill PIU
• CSSCS - Unit Supply Point Updates
• Unit Class III, V, VII, Battle Loss, and
  Personnel
• Supply Point Class IIIB, IIIP, V, and IX.

9
Goals for Successful C2 Stimulation

• The information exchange must be realistic
• Train under operational conditions
• Avoid negative or incorrect training
• The stimulation mechanism must be invisible to
  the participants
• No intrusion on live tactical units

10
Criteria for Realistic Stimulation

• The Information Exchange must be
• Accurate each time
• Consistent over time
• Correctly Routed
• Timely
• Correlate to goals for Digitization
• to acquire, exchange, and employ timely
  battlefield information. ...
• to share a common picture
• for optimizing the flow of information.

11
C4ISR Stimulation Concepts

• Meet Unit Specific Requirements
• Handle Asynchronous Input and Output
• Maintain a C2 Network Perspective of the
  Simulated World

12
Meet Unit Specific Requirements

• Standard Operating Procedures differ in the 5Ws
• Routing/Flow Who sends, Where do they send it?
• Real world task organization versus simulation
  task organization
• Answers vary by type of information
• Detailed information required to match the Who to
  the Where
• Why/When to stimulate? Time Based, Event based
• What Type of Exchange Update vs Synch
• What Data Command Filters (CCIR, CTIL,
  Commanders Attack Guidance)
• Answers will vary across units, exercises, and
  within exercises.

13
Handle Asynchronous Input and Output

• Commanders desire for info does not always match
  the simulations ability to provide it.
• CBS EADSIM could provide real-time info
• CSSTSS had two types of output
• Real-time
• Checkpoint files
• Simulation output may be more frequent than
  Commander desires
• Simulation Time may vary from the Commanders
  (Wall Clock) Time

14
Maintain a C2 Network Perspective of the
Simulated World

• Simulations and C2 network had different data
  models
• Designed for different purposes
• Different tradeoffs on computational resources
• Transform on input to C2 perspective
• Speed of response to output request
• Complexity and volume of data
• Multi-Source/Use Data e.g., Battle Loss location
• Asynchronous input and output
• Enables the output side to be unaware of the
  simulation sources.

15
Two Potential Cases for C2 Federations

• Case 1 replicates C2 network across the
  federation.
• FOM must include C2 standards.
• Case 2 insulates C2 network from federation.
• FOM may include C2 standards.
• Cases may use different standards

16
Potential Standards Areas

• Defining the 5 Ws of information exchange
• Who is sending information
• To where is it sent
• Classifying Why/ When is it sent
• What gets sent
• C2 Community defining their standards.
• Data Definitions
• Information Exchange structures
• Communications

17
Potential Information Exchange Standards

• DII COE Components
• Joint Common Data Base
• Common Operating Environment Message Processor
• Communications Processor
• See
• 99S-SIW-034 Data Alignment between Army C4I
  Databases and Army Simulations
• 99S-SIW-035 Designing Army Simulation
  Interfaces to the Army Common Interoperability
  Infrastructure
• Emphasis is on Common
• Significant stimulation of stovepiped information

18
Requirement for a Flexible FOM

• Ownership Management permits federates to enter
  and leave federation.
• Two scenarios for transferring ownership of a
  location attribute.
• Single Federate Pull Intrusive
• Multiple Federates Last Requestor Wins
• Federation must contain the logic to maintain
  accuracy and consistency for C2 network.

19
Summary

• The Army has a growing need for C2 network
  stimulation for testing and training.
• Requirements change with the unit and event.
• Stimulation standards must enable dynamic events.
• DII COE a starting point but not enough.

20
The End
21
III Corps SOP for Message Flows To Ensure
Consistent Picture Across Unit (CSS Example)

• Goal is to ensure consistency up and down chain
  of command with minimal transmissions.
• RTM sends update messages for a reporting echelon
  to an inject point, usually for Brigade to a
  brigade S-3 or S-4, which then retransmits to
  peers and one node at Div/Corps.
• Higher HQs node retransmits Bde message,
  beginning flow throughout Corps.

Example Update Message Flow
RTM to generate CSSCS messages and inject them
here.
22
III Corps WFX Message Release Criteria

• Event based messages in real time (Fire Support,
  F-3, F59-63)
• RTM used elapsed wall clock time as the trigger
  for Update messages
• S507L (location) and S303 (SALUTE) every 15
  minutes
• Unit Class VII Battle Losses - real time (PM set
  to 1 hour)
• Unit Class VII/Maintenance updates - every 2
  hours
• Other Unit and Supply Point logistics updates -
  every 4 hours
• Personnel updates - every 12 hours
• Logistics Updates were constrained by the
  simulation check point schedule (usually 60-120
  minutes)