UNITED STATES TRANSPORTATION COMMAND DIRECTORATE OF PLANS AND POLICY

1

MIDAS -ELIST HLA FEDERATION
Chuck Van Groningen ANL
Bill Ferguson BBN Technologies
Carroll Keyfauver GRCI
2
OVERVIEW

• The players and the objective
• MIDAS
• ELIST
• AMP Shell
• MIDAS-ELIST HLA Integration
• FUTURE

3
THE PLAYERS

• BBN TECHNOLOGIES (BBN)
• GRC International (GRCI)
• ARGONNE NATIONAL LAB (ANL)
• Major Contributors
• Doug Barbour MTMC-TEA
• Emmet Beeker, GRCI
• Mary Duffy Braun-ANL
• Chuck Replogle, GRCI
• Nathan Rinsema-ANL
• Jeff Tustin, BBN

4
END TO END MOBILITY MODELING
HLA
MIDAS
ELIST
TPFDD
RTI
Dynamic Parallel
5
THE FEDERATES

• MIDAS (Model for Intertheater Deployment by Air
  and Sea)
• Strategic Movement and Asset Handoff
• ELIST (Enhanced Logistics Intra-theater Support
  Tool)
• Asset Unloading, Hand-back and Onward Movement
• AMP (Analysis of Mobility Platform)
• Initialization, Data-gathering and Display

6
MIDAS

• An End-to-end Planning and Simulation Model That
  Schedules the Deployment of Units and Their
  Sustainment in Multiple Theaters.
• Uses Simulation to Execute a Deployment Schedule
  That Is Updated Daily.
• Simulates Individual Aircraft and Ship Routing
  and Movements.
• Forecasts Fuel Dry Sustainment Requirements for
  the Forces Based on Expected Arrival Schedules,
  Expected Theater Combat Intensity, and Stockage
  Buildup.

7
MIDAS OVERVIEW
.
INTER THEATER
.
AIR ENROUTE
.
.
.
.
.
THEATER
INTRA CONUS
.
ILOC
.
.
APOD
.
.
APOE
.
HOME STATIONS
.
APOE
.
AIR ENROUTE
.
.
.
APOD
TAAs
.
.
SPOE
SPOE
SPOD
ASHORE PREPO
AFLOAT PREPO
MARRY UP
8
MIDAS MODIFICATIONS TO SUPPORT THE FEDERATION

• Simulate Individual Aircraft Activities (en
  route, arrival, and departures)
• Incorporate HLA Interaction Cycle for the Theater
  Version of ELIST
• Support Daily HLA Interaction Cycle
• Start new day
• Update asset and ports from ELIST
• Schedule the deployment transmit to ELIST
• Plan future deployments while ELIST executes

9
MIDAS HLA MODIFICATIONS (Cont.)

• Add HLA Federation Join, Time Management and
  Resign Capability.
• Ability to Send Aircraft and Ship Arrivals and
  Expected Departures to the Federation
• Ability to Send Ship and Aircraft Manifests to
  the Federation
• Register Ships, Aircraft, Seaports and Airports
  in the Federation
• Receive Departure Updates From Federation

10
MESSAGES SENT BY MIDAS
.
INTER THEATER
1.Aircraft arrival time expected departure
time 2. Aircraft manifest
.
AIR ENROUTE
.
.
.
.
.
THEATER
.
ILOC
.
Updated Closure Time For Unit
.
APOD
.
.
APOE
.
HOME STATIONS
.
APOE
.
AIR ENROUTE
.
.
.
APOD
TAAs
.
Updated port to destination travel time for unit
.
SPOE
SPOE
SPOD
ASHORE PREPO
AFLOAT PREPO
1. Ship arrival time expected departure
time 2. Loading manifest
1. Ship arrival time expected departure
time 2. Ship manifest (Level IV)
MARRY UP
Updated Marry-Up Completion for Unit
11
MESSAGES RECEIVED BY MIDAS
.
INTER THEATER
Updated APOD departure time for aircraft.
.
AIR ENROUTE
.
.
.
.
.
THEATER
.
ILOC
.
Updated Closure Time For Unit
.
APOD
.
.
APOE
.
HOME STATIONS
.
APOE
.
AIR ENROUTE
.
.
.
APOD
TAAs
.
Updated port to destination travel time for unit
.
SPOE
SPOE
SPOD
ASHORE PREPO
AFLOAT PREPO
Updated SPOD departure time for ships.
MARRY UP
Updated Marry-Up Completion for Unit
12
ELIST

• Discrete Event Simulation of Military Deployments
  Through the RSOI Process in the Theater of
  Operations.
• Answers Questions Like
• Will the theater infrastructure support the plan
• Are theater assets sufficient to support the
  given delivery dates.
• Where are the bottlenecks?
• What are the effects of exogenous events?

13
ELIST OVERVIEW
Personnel are Offloaded and Marshalled
Airport
Units Marry and Personnel Train on Equipment
Cargo/Pax
Cargo Pax
Theater Staging Base
Advanced Party
Destination
Cargo
Seaport
Cargo
Staging Area
Cargo is Set Up or Transferred to Alternate Mode
Cargo is Offloaded and Marshalled
14
ELIST MODIFICATIONS TO SUPPORT THE FEDERATION

• Incorporate JAVA HLA Runtime Libraries
• Build In Synchronization Methods
• Incorporate Clock Infrastructure to Allow ELIST
  to Coordinate With Other Models
• Ability to Create Simulation Events in the Model
  Dynamically Based on Arriving Strategic Assets
  Received From the HLA Federation
• Generate Statistics on Port Usage Each Day
• Provide Travel Time Averages for MIDAS Planning

15
MESSAGES RECEIVED BY ELIST

• Objects Created by ELIST
• Airports
• Seaports
• Interactions Received by ELIST
• Ready to proceed
• Resign federation
• Air POD arrival
• Air arrival manifest item

16
MESSAGES SENT BY ELIST

• Interactions Sent by ELIST
• Plane on ramp
• Air Strategic Release
• Ship In Berth
• Sea Strategic Release
• RLN Marry Complete
• Destination Arrival
• POD-Destination Travel Time (Average travel time
  of units performing RSOI for each POD/Dest. pair)

17
AMP

• An environment for managing and combining
  transportation models, data and other tools.
• The AMP project provided the control and
  visualization federate and coordinated the
  integration effort.

18
AMP CONTROL GUI
Initialization Data Display
19
AMP DATA DISPLAY
Displays Plan VS Actual Visualization
20
TIME IN THE FEDERATION

• Getting the federates in sync
• ELIST is an event-based simulator
• MIDAS is a step-based simulator with a one day
  time step
• We wanted to achieve as much parallel processing
  as possible

21
TIME SOLUTION

• Fortunately, we were able to divide the
  interactions and attribute changes that MIDAS
  produces into two groups
• A set (the asset arrivals) that were known at the
  beginning of the step and which would not change
  regardless of what happened during the step.
• A set which needed to be computed but which could
  not affect ELIST during that step.
• Our solution was to send all interactions and
  attribute changes in receive order and to process
  each step in two phases
• MIDAS would produce all of the arrival events
  with minimal computation.
• Both federates would process the whole time step.

22
AMP INTEGRATION ISSUES

• Event Flow and Ontology
• Agreement on the objects and interactions
  (events) that needed to be shared
• RTI (High Level Architecture Run Time Interface)
  Intricacies
• Data Consistency
• Ship names, ship type names, plane types, etc.

23
ISSUE RESOLUTION

• Event Flow and Ontology
• Leverage previous successful efforts to combine
  these models sequentially
• RTI Intricacies
• Sweat them out, get assistance from DMSO
• Data Inconsistencies
• Solve them one at a time, but be should have been
  more rigorous up front.
• Eventually, implement centralized data set-up

24
LESSONS LEARNED(MIDAS)

• Minimize amount of information exchanged between
  models in order not to overload the RTI
• Having a HLA SOM/FOM only establishes a common
  data format therefore create a common data
  dictionary
• Keep models up to date with current language
  standards

25
LESSONS LEARNED(ELIST)

• Data Consistency Between Federates is Critical
• Needs to be solved outside of federation, not
  inside
• HLA Java Interface Works Well
• HLA Has Matured Greatly
• Still some problems with starting/stopping/restart
  ing federation

26
STATUS OF THE EFFORT

• THIS SUMMER
• Hardened the federation to support UFL 01
• FUTURE
• Dynamic mode and port selection
• True pause of the federation
• Dynamic events injected into the federation
• Dynamic sustainment requirement generation
• Port congestion feedback to other federates
• Linkage to JSIMS federation

27
SUMMARY

• A federation has been created out of existing
  models which can simulate both strategic and
  theater movement with high efficiency using the
  HLA.
• AMP is the modeling and simulation vision of USTC
• HLA RTI is a key feature
• The prototype exists and has been used
• FY 02 work will produce additional functionality