AMSP-06 next-generation NATO mobility model guidance

What it is

AMSP-06 is a NATO Allied Modelling and Simulation Publication that defines an open-architecture standard for a Next-Generation NATO Reference Mobility Model, NG-NRMM: the terrain and soil data a mobility simulation consumes, the vehicle physics it has to represent, and the trafficability outputs, GO/NOGO, Speed-Made-Good and Motive Efficiency, it has to produce. It does not replace anything outright; it builds on the legacy NATO Reference Mobility Model, developed by the US Army in the 1960s and 1970s, which the document itself describes as "understood to be fundamentally limited and difficult to adapt".

Its cover is STANREC 4813, a NATO Standardization Recommendation rather than a ratified agreement, so no nation is obliged to build to it. It reaches a company only once a contract or an acquisition programme names NG-NRMM conformance, or a modelling-and-simulation vendor chooses to align its own tooling to the data model it publishes. AMSP-06's own development "follows the NATO standards development process provided in AAP-03(K)", and any future revision follows AAP-03's own revision procedure, routed through a Technical Activity Proposal to the NATO Science and Technology Organization's Applied Vehicle Technology panel.

Two audiences, not one

The document speaks to two distinct groups. It addresses geospatial-data and modelling-and-simulation developers directly: "Geospatial data developers should use the following data model when developing input terrain data sets for NG-NRMM applications." And it addresses NATO nations' vehicle acquisition and operational-planning communities, describing itself as needed "to support vehicle acquisition and design using common mobility metrics", and reporting that a survey and questionnaire was put to more than 60 NATO operational planners to gauge their readiness to use it. It never names a supplier or contractor directly; that role only appears once a contract invokes the standard.

The terrain and vehicle data model

The architectural core sets a minimum terrain-data model of at least 24 characterising attributes per terrain unit, covering surface and sub-surface soil type, bulk density, moisture, temperature, land use and roughness, each tagged by data-source type, measured, inferred, legacy or notional, so where a value came from stays traceable. That data moves between systems as a legacy ASCII "Code 11 MAPTBL" file, GeoTIFF rasters, or XML/GML built on a UML data model NATO derived from the legacy format, itself resting on the ISO 19100-series geographic-information standards, OGC's GML, WFS and WCS, and kept harmonised with AGeoP-11, NATO's own geospatial information framework. Every NG-NRMM implementation has to produce three summary mobility metrics, GO/NOGO, Speed-Made-Good and Motive Efficiency, each as a probabilistic value rather than a single point, with the algorithms that combine contributing factors documented rather than left as a black box.

Vehicle physics and terrain interaction

NG-NRMM builds on an existing 3D multibody-dynamics simulation capability rather than defining one from scratch, and adds terrain interaction through two tiers. "Simple Terramechanics" is a bearing-and-traction response calibrated by bevameter measurement, with specific plate-size, normal-pressure and repeat-measurement protocols. "Complex Terramechanics" is full three-dimensional soil deformation, using finite element or discrete element methods, for work that needs that level of resolution. Autonomous-vehicle mobility has to be modelled with common sensor types, GPS, IMU, radar, cameras and LIDAR, plus object, agent and material representations of the environment. Uncertainty quantification runs full stochastic terrain and vehicle data through at least 10,000 Monte Carlo samples per pixel to produce a reliability-based mobility map, not a single deterministic answer.

A maturity scale, not a pass/fail test

Verification and validation runs on a seven-level Capability Maturity Scale, rising from a basic "Demonstration" of a theoretically consistent model, through independent-user and cross-code verification, to "Calibration" and "Validation" against a real vehicle test data set, and finally to a level that repeats validation with a changed system parameter. Three benchmark vehicles, a tracked armoured personnel carrier, a 4x4 wheeled platform, and the Fuel Efficiency Demonstrator-Alpha, come with vehicle, terrain and measured performance data for ten defined mobility events. The document is candid where its own benchmarks fall short: the amphibious-vehicle and autonomous-vehicle events are listed as "Test Data N/A", and it reports that current verification and validation for tracked-vehicle performance "remains below the requirement" for the level of confidence operational planners actually need.

What an assessor of this kind of document actually checks

Nobody is certified against AMSP-06. It says so directly: "Accreditation and/or acceptance criteria are not addressed by this standard. These shall be defined by each M&S intended end use". What substitutes for certification is the maturity scale above, which a model's own developer or sponsoring programme demonstrates by calibrating and validating against the benchmark data, not by submitting to an external certification body, a notified body, or government quality assurance. Whoever commissions the model, a programme office or an acquiring nation, checks the evidence against whatever maturity level their own contract or use case requires.

What it does not cover

The standard is candid about its own gaps. A survey of more than 60 NATO operational planners found none using the bevameter measurement technique the standard specifies for terrain characterisation in the field; terrain and vehicle analysis is instead always completed well in advance of an operation, never in real time. Amphibious and autonomous-vehicle benchmark events are named but carry no test data yet. And AMSP-06 sets no acceptance or accreditation criteria of its own: those are left to each modelling and simulation end use.

Standards it references

• AAP-03Binds
• AGeoP-11Background