Expanding the U'S' Transportation Commands Analysis of Mobility Platform AMP Federation to Model Aer

1
Expanding the U.S. Transportation Commands
Analysis of Mobility Platform (AMP) Federation to
Model Aerial Ports of Debarkation (APODs)

• Phil Collins
• Amy Fedyk
• Lora Goldston
• Gary Kratkiewicz
• Soraya Stevens, Ph.D.
• Jeffrey Tustin

2
Outline

• AMP Overview
• AMP Federation Infrastructure
• Transportation Models
• Extending the AMP Federation
• Functional
• Technical
• Integrated Solution
• Summary and Future Work

3
Analysis of Mobility Platform (AMP)
AMP provides modeling and simulation capabilities
for strategic deployment and distribution
processes

• Used by US Transportation Command since the early
  1990s for programmatic analysis
• Long term strategic planning
• Capability analysis for mobility
• Integrates multiple transportation models to
  enable end-to-end assessments
• Provides a common environment for editing,
  running, and data analysis of simulation studies

4
Integrated Desktop System

• Editors, planning factors
• Data critics, setup summaries
• Model selection

Setup
Analyze
Run

• Launch, control, and dynamic monitoring of
  simulation

• Reports and analysis tools

5
AMP Federation Infrastructure

• Prototype Federation (2000 2003)
• Implemented in HLA, impractical to deploy on the
  desktop
• Fielded Federation (2004 present)
• Java RMI component-based infrastructure
• Deterministic and configurable startup sequence
• Models run simultaneously, exchanging data in a
  round-robin time-stepped manner
• Domain independent component API
• Domain data are exchanged as Java objects
• See U.S. Transportation Command Analysis of
  Mobility Platform Federation, EuroSISO 2004

6
Transportation Models In AMP

• In 2004, the AMP Federation included two
  transportation models
• Model for Intertheater Deployment by Air and Sea
  (MIDAS)
• Strategic deployment of unit personnel and
  equipment by air and sea
• Enhanced Logistics Intratheater Support Tool
  (ELIST)
• Movement of personnel and equipment from theater
  origins to final destinations

7
AMP Modeling Capability
Fast Initial Answer High Fidelity airlift
sealift Low Fidelity port land movement
AMP
8
APOD Model

• APOD contains a suite of analysis and decision
  support tools for various airport operations

Setup Analysis Tools
Airport Simulation Tool (AST)
9
APOD Integration Requirements

• Maintain AMPs single common interface
• AMP must interface with the APOD GUI to set up
  the simulation
• Preserve the one button push run capability
• AMP federation models must dynamically interact
  with one or more airfield simulations (ASTs)

AMP
APOD
MIDAS
AST
AST
AST
10
APOD Integration Challenges

• Maintain a single common user interface
• AMP is written in Java.
• APOD is written in Microsoft Visual Basic .NET
• Preserve One Button Push Run Capability
• AST is normally run through APOD in a separate
  process.
• Expand AMP Federation Infrastructure to launch
  AST
• Grow the existing simulation framework to include
  the AST model
• AST is written in Squeak, an implementation of
  Smalltalk
• Transfer data between AST and the AMP Federation
  Domain Object Model

11
Integrated Solution

• AMP is built on a distributed component-based
  architecture
• AMP supports anytime components
• Applications are invoked as components that can
  be launched and used anytime in an AMP session
• Components may communicate with AMP via an
  application-specific API
• The Distributed Simulation Framework includes a
  Federate API for models running in the AMP
  federation

12
AMP to APOD
APOD (.dll)
Java VM
Java VM
APOD Component
RMI
COM
AMP
APOD API JACOB

• Defined a minimal APOD API to set up the
  modeling of an airfield
• userLogin(String user, String password)
• chooseScenario(String airportGeoloc)
• writeAstInitFile(List aircraftTypes, String
  astInitDir)
• Exposed the APOD API and relevant libraries
  (DLLs) via the Microsoft Component Object Model
  (COM)
• Implemented the APOD API using JACOB, a
  Java-To-COM bridge
• uses Java Native Interface (JNI) to make native
  calls to COM libraries

13
AMP to APOD Scenario Chooser
14
AST Federate
Platform OS
Java VM
Java VM
AMP
Ast Federate
Ast Wrapper
Squeak VM
Ast Wrapper
AST

• A single AST federate launches and communicates
  with multiple ASTs (multiple airfields)
• Lightweight AST wrappers monitor each AST
  instance
• The wrappers and AST communicate via the file
  system
• Leveraged the same XML data model that APOD uses
  to communicate with AST
• The wrappers handle the translation between the
  AMP Federation object model and the AST XML

15
AMP Federation Run with AST
16
Summary and Future Work

• Expanded the AMP Distributed Simulation Framework
  to support Microsoft Visual Basic and file-based
  components
• Rapid integration of new components
• Integrated a detailed airport simulation with
  detailed asset movement models
• Enabled multiple AST instances to run in the same
  simulation
• Events at one airport can affect another
• Future Work
• Package and document the domain-independent
  federation library and make available to the
  simulation community (if funding permits)
• Integrate a detailed warfight model
• Integrate the seaport analog to the AST