Leveraging the HLA

1

• Leveraging the HLA
• and the DII COE
• To Build a Simulation-Based Framework for C2
  System Integration and Test
• R. Douglas Flournoy
• rflourno_at_mitre.org
• [phone]

2
This is a Background/Approach/Results Briefing
from an Ongoing Sim-to-C2 Research Effort...

• Project Objectives
• Background
• ESC, HLA, DII COE
• Approach
• Simulation-Based C2 Integration Framework
• Lightweight Interface Federates (LIFs)
• Current Status
• Lessons Learned/Remaining Challenges

3
Project Objectives Evolution
100
Apply HLA to ESC C2 Development Needs

50
Merge HLA and COE
0
FY99

• FY00/Future

• FY98

4
The Air Force Electronic Systems Center (ESC)
Develops C2 Systems

• Integrated C2 System (IC2S)
• Theater Battle Management Core Systems (TBMCS)
• Airborne Warning and Control System (AWACS)
• Joint Surveillance Target Attack Radar System
  (JSTARS)
• ...

5
Simulation Technologies at Work for ESC
6
The MST PAD Provides Simulation Support to ESC

• Modeling, Simulation and Training (MST) Product
  Area Directorate (PAD)
• National Air Space Warfare Model (NASM)
  Program Office
• JSIMS
• Modeling Analysis Simulation Center (MASC)
• provides simulated battle for C2 integration
  activities at ESCs C2 Unified Battlespace
  Environment (CUBE)
• Critical piece of new IC2S effort

7
Applying Simulation Technologies to C2 System
Integration Testing

• Increasing C2 system interoperability requires
  leap in testing, training capabilities
• Simple test jigs used for traditional stovepipe
  systems insufficient for system of systems
  testing
• Synthetic battlespace needed to test
  interoperable sets of systems in realistic
  operational context
• The HLA facilitates the composition of synthetic
  battlespace from existing/emerging DoD
  simulations
• To take advantage of a synthetic battlespace, C2
  systems must connect to HLA environment

Key cost-effective HLA connection solutions
for C2 systems
8
The High Level Architecture

• Architecture calls for a federation of simulations

• Architecture specifies
• Ten rules
• define relationships among federation components
• Object Model Template
• specifies the form in which simulation elements
  are described
• Runtime Interface Specification
• describes the ways simulations interact during an
  operation

Live Participants
The HLA is a standard and does not mandate a
specific software implementation
9
The DII COE
Combat Support, Tactical Strategic Mission
Applications
Standard Application Program Interfaces
Data
Office
MCGI
Alerts
Correlation
Developers
Automation
Access
Kit
COMMON SUPPORT APPLICATIONS
Presentation
On-Line Help
S HADE
Presentation
Distributed
Communications
Management
Data Object
C O E
Computing
Web
Management
INFRASTRUCTURE SERVICES
KERNEL
Operating System
Databases
10
The DII COE and the HLA Complementary or
Contradictory?

• In spite of contrasting themes...
• COE/JTA product standardization
• HLA dynamic data exchange framework
• ...there is high potential for synergy...
• Technically, nothing preventing HLA software from
  inclusion in COE
• that could facilitate certain sim-to-C2 use cases

11
ESCs Simulation to C2 System Infrastructure
Research Project Vision

• Robust, realistic, SPO-friendly integration
  framework to support C2 testing experimentation
  as sims, C2 systems migrate toward HLA, COE.

AWACS
Other C2 or Intel S/W Components
...
Operational System S/W
...
C2 Inf. S/W
DSI
ORBs, DAIMIs, etc.
AWACS mission slice
DIS
CORBA
...
Sim-to-C2 S/W
Ground LIF
Air LIF
LIFs TBD
HLA
HLA
GMTI mission slice
AWACS Sensor Models
GMTI Testbed
Other Role-Specific Simulations
Role-specific Simulations
JSTE
...
JSS
UAV
Other slices (Intel, Space Ops, Logistics, etc.)
HLA Runtime Infrastructure
Battlespace Infrastructure
Other Tools Simulations
...
12
The Lightweight Interface Federate (LIF) Concept

• LIFs are streamlined translation applications
• Each LIF handles one FOM, one C2 data protocol
• Balanced sim-to-C2 approach that fits ESCs needs
• Less complex than single universal sim-to-C2
  solution
• More reusable than custom point-to-point
  interfaces

13
Current State of Simulation-Based C2 Integration
Framework Prototype

GMTI Testbed
AWACS FET
UAV Model
JSS
Sensor Models
Process Control
JSTE
Tracker
Display
DIS Entity State PDUs
CORBA
AWACS DSI
Ground Tgt Truth LIF
Truth LIF
aircraft data
ground tgt data
HLA RTI
FMT
EADSIM
14
Example Scenario
15
AWACS Dots chart
16
Dots!
17
Lessons Learned

• HLA and COE can be complementary
• Broader community now examining whether HLA-based
  s/w should be included in the COE
• DISA HLA-COE Advisory Group
• spurred by ESC MST PAD efforts
• LIF approach appears viable for ESC sim-to-C2
  framework
• Streamlined translators proving economical to
  build and revise
• Reusable, layered HLA interface s/w key
• Performance solid so far (need more data)

18
Remaining Technology Challenges

• 2-way data exchange between C2 applications and
  synthetic battlespace
• simulated battle should be influenced by command
  messages, track data, etc. generated at C2
  stations
• Maximize benefits, minimize cost-to-connect for
  ESC C2 programs
• define streamline steps necessary for SPOs to
  plug components into framework
• capture runtime events for later review
• minimize software rework to adapt HLA interfaces
  to evolving data exchange

19
The HLA-COE White Paper Series

• The DII COE and the HLA Complementary or
  Contradictory?
• Merging the DII COE and the HLA Overview of
  Options and Tradeoffs
• Presentation tomorrow, 200 PM, Captiva
• The HLA Mandate for DoD Simulations
  Considerations for the C2 Community
• Presentation tomorrow, 130 PM, Captiva