Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMSP-06
Geospatial-data and modelling-and-simulation developers who build NG-NRMM tooling, and NATO nations' vehicle acquisition and operational-planning communities
NATO guidance defining the terrain data, vehicle physics and validation approach a next-generation mobility-prediction tool needs, reaching a company only once a contract or acquisition programme names it.
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.
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 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.
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.
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.
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.
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.
AMSP-06 is an operational and technical Allied Publication, not a management-system standard: the requirement it sets is a data model and a modelling capability, and the work of meeting it happens in GIS and vehicle-dynamics engineering tooling and in physical terramechanics testing, not in a compliance platform.
Where ComplyTrain fits is once a contract or programme names AMSP-06 or NG-NRMM conformance: holding the documented procedures for how terrain and vehicle data are sourced and tagged, measured, inferred, legacy or notional, the calibration and validation records that support a claimed Capability Maturity level, and the training records for staff running the benchmark test events, kept current and ready for whoever asks to see them, a programme office or an acquiring nation. That evidence trail is what an assessor for this kind of document actually wants.
ComplyTrain does not run the mobility simulation itself, generate the GIS terrain data, or perform the physical soil and vehicle testing the standard describes. Those stay day-to-day engineering and field work. Which tier of NG-NRMM conformance applies to a given programme, and which of the standards in the explorer sit alongside AMSP-06, is set by the contract and the customer's quality clause, not by us. If your organisation needs to evidence this kind of work, talk to us.
Tell us how you need to work with AMSP-06 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
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 data, vehicle physics and validation approach a mobility-prediction tool needs to produce GO/NOGO, Speed-Made-Good and Motive Efficiency outputs for ground and amphibious military vehicles.
Next-Generation NATO Reference Mobility Model. It updates the legacy NATO Reference Mobility Model, developed by the US Army in the 1960s and 1970s, which AMSP-06 itself describes as "understood to be fundamentally limited and difficult to adapt".
No. Its cover is STANREC 4813, a NATO Standardization Recommendation, so nations are invited to use it rather than obliged to. It reaches a company only once a specific contract or acquisition programme names NG-NRMM conformance.
No. The document states plainly that accreditation and acceptance criteria are not addressed by this standard, and that each modelling and simulation end use sets its own. What it offers instead is a seven-level Capability Maturity Scale, demonstrated against benchmark vehicle and terrain data rather than assessed by an external certification body.
Edition A, Version 1, published in July 2021 by the NATO Standardization Office. It presents itself as the first release of this open-architecture approach, and its own text names nothing that it supersedes.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.