SIW_123 Mobility

1
Getting One of the Basics Right for Distributed
Simulations A Mobility Service/Server for the
Present and Future
European Simulation Interoperability Workshop
2004 Edinburgh, Scotland
2
Outline

• Issue Goals
• Objectives Scope
• Background
• Description of Tactical/Entity Level API
• I/O for Levels 1 2
• Bins and Representative Vehicle Mappings
• Data and Software Standards
• Mobility Server
• Conclusion
• Summary
• Questions

3
Issue Goals

• Issue
• Mobility implementation in MS is largely
  tailored for specific simulations
• Goal
• To create an API to facilitate the implementation
  of NATO Reference Mobility Model (NRMM)-based
  mobility into modeling and simulation
  applications by providing a standard interface
• To promote consistent representations of ground
  vehicle mobility across the hierarchy of MS

4
Objectives Scope

• Objective
• Identify the types and variations of API levels
  needed to meet the needs of the MS community
• Design the architecture for these APIs
• Develop the associated algorithms using the US
  Army Model Simulation (AMSO) standard for
  mobility, the NRMM.
• Transition the products to the user community
• Scope Focus
• Ground vehicle mobility, or trafficability, in
  terms of achievable vehicle speed, and on MS
  applications.
• The accomplishments to date dealing with the
  design and development of the Level 1
  Entity/Tactical hierarchy category

5
Background (MS Taxonomy)
TYPOLOGY
6
Background (Model Versions)
7
Description of Tactical/Entity Level API

• Level 1 (look-up tables)
• Fidelity Degree 1 (limited to 12 representative
  vehicles)
• Fidelity Degree 2 (allows variation for specific
  vehicles)
• Level 2 (physics based)
• Fidelity Degree 3 (limited to 12 representative
  vehicles)
• Fidelity Degree 4 (not limited)

8
I/O for Fidelity 1 2

• Input

• Bin(R) or Specific Vehicle Data
• (High, Med, Low Mobility) Tracked
• (High, Med, Low Mobility) Wheeled
• (High, Med, Low Mobility) Wheeled w/Trailer
• (Amphib or similar design) Tracked
• (Amphib or similar design) Wheeled
• Small ATV

• Environmental Data
• Climate Zone
• STGJ Code (Soil Type, Vegetation, water, etc.)
• Surface Condition (Normal/Dry, Slippery/Wet,
  Snow/Ice)
• Visibility/Obstacle Spacing Pairs
• Slope

Output Level 1 SpeedR NRMM speed predictions
implemented in WARSIM Amphids ATV
Level 2 SpeedS SpeedR MaximumRoadSpeedS /
MaximumRoadSpeedR
9
Bins and Representative Vehicle Mappings

• No. Vehicle OOS,WARSIM,JWARS,CBTXXI
  Name CCTT-SAF Name
• M1A1 High Mobility Tracked High Mobility
  Tracked
• M270 MLRS Medium Mobility Tracked Good Mobility
  Tracked
• M60 AVLB Low Mobility Tracked Low Mobility
  Tracked
• M1084 MTB High Mobility Wheeled High Mobility
  Wheeled
• M985 HEMTT Medium Mobility Wheeled Low Mobility
  Wheeled
• M917 Dump Truck Low Mobility Wheeled Not
  Applicable
• M1084/M1095 High Mobility Wheeled w/Trailer Not
  Applicable
• M985/M989 Medium Mobility Wheeled w/Trailer Not
  Applicable
• M911/M747 HET Low Mobility Wheeled w/Trailer Not
  Applicable
• M113A2 Tracked Amphib Combat Vehicle Moderate
  Mobility Tracked
• LAV25 Wheeled Amphib Combat Vehicle Not
  Applicable
• Kawasaki ATV Light ATV Not Applicable

10
Example Mobility Implementation
Sand
Clay
Gravel
Dry
Wet
Dry
Wet
Dry
Wet
11
Example Mobility Implementation
Sand
Clay
Gravel
Dry
Wet
Dry
Wet
Dry
Wet
12
Design Interdependence
13
Data and Software Standards

• Extraction From NRMM
• Open Standards (XML/W3C)

14
Data and Software Standards

• Software Specs
• Java JRE 1.3, 1.4
• Junit
• HLA RTI 1.3ngr4
• Windows NT/2000
• Linux 7

15
Mobility Server

• Software c wrapper
• High Level Architecture / Run Time Interface
  (HLA/RTI)
• IEEE specification 1516

16
Conclusion

• STNDMob API
• A standard, platform-independent implementation
  based on the AMSO standard for ground vehicle
  movement representation, NRMM
• Software enhancements Java, XML, HLA
• Facilitates integration of the model into future
  simulations
• Allows for model upgrades with minimal
  reengineering of simulation links
• Helps reduce the proliferation of differing
  mobility models
• Provides access to standard speed prediction
  algorithms
• Promotes reuse/consistency
• Saves developers and analysts time and money
• Operates at about an order of magnitude faster
  than NRMM

17
Summary

• The NATO Reference Mobility Model (NRMM) is the
  AMSO standard for single vehicle ground movement
  representation. While representation of ground
  vehicle mobility in both entity- and
  aggregate-level MS has typically been
  simplified, many of the speed limiters
  incorporated in NRMM are ignored. The Standard
  Mobility Application Programming Interface,
  NRMM-based, is a means of readily achieving
  higher-fidelity movement representation by
  incorporating terrain-limited speeds into MS. By
  providing a standard interface for applications,
  this API helps reduce the proliferation of
  differing mobility models, provides access to
  standard speed prediction algorithms, and
  promotes reuse/consistency.
• STNDMob Mobility Server has been nominated in
  the AMSO standards process and will be managed by
  the US Ground Vehicle Mobility Modeling Technical
  Management Committee.

18
Questions?
19
Getting One of the Basics Right for Distributed
Simulations A Mobility Service/Server for the
Present and Future
European Simulation Interoperability Workshop
2004 Edinburgh, Scotland