Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMSP-04
Organisations that design, build or integrate simulation federates for NATO and Partner-nation training exercises
AMSP-04 defines the NETN-FOM, a shared HLA data model that lets national and NATO simulation systems exchange scenario, tasking and reporting data in joint training exercises.
AMSP-04 is the NATO Allied Modelling and Simulation Publication that defines the NATO Education and Training Network Federation Object Model, known as NETN-FOM: a shared data model for exchanging information between the simulation systems that take part in a joint distributed training exercise. It is not a management-system standard and it does not set out obligations for a quality function. It is a technical specification for the people who design, build or integrate simulation software, and Edition C, Version 1 (March 2025) is the current version, superseding Edition B, Version 1 (March 2021).
NETN-FOM works inside the IEEE High-Level Architecture (HLA), the simulation infrastructure NATO covers separately under STANAG 4603. HLA lets independent simulation applications, called federates, interoperate through standard services and interfaces; AMSP-04 defines the specific object and interaction classes federates publish so that other federates in the same federation can understand them. The document describes itself as a reference: it does not replace the need for detailed design work, but gives federation designers a common foundation to build against instead of each inventing their own.
AMSP-04 addresses those who design and develop simulation federates, not a procurement or compliance function. It reaches a company through a contract, not through NATO membership: the document itself is not mandatory. It is carried by STANREC 4800, a NATO recommendation rather than a ratified agreement, so nations are invited to use it rather than committed to it. For a supplier, the practical trigger is a training programme, exercise directive or contract that names NETN-FOM, or a specific edition of it, as the data model a federate must implement. Because it governs how a federate's data model is structured, it is far cheaper to design for from the outset than to retrofit once a federate is already built.
NETN-FOM is organised into modules, each covering one aspect of a simulated exercise and built on a shared base:
Every object a federate creates needs a published unique identifier, and a federate receiving a control action has to respond so the sender can tell whether it succeeded. The aggregation, disaggregation, division and merging patterns in NETN-MRM are defined step by step with explicit preconditions - which attribute has to be owned, which status an entity must be in, whether the referenced organisational unit has subunits - which is the kind of detail an implementer checks an integration against, not a paraphrase of intent.
Just as important is what the document leaves open. It says plainly that some choices, such as how logical time is synchronised between federates, belong to the federation's own agreement rather than to NETN-FOM: implementers are told to use their federation agreement to settle it. The same pattern applies to default symbol standards and non-standard equipment subcategories. An implementer's federation agreement, not AMSP-04, is where those gaps get closed.
There is no certification against AMSP-04. Where its history mentions certification at all, it is a related but different activity: a NATO technical group once worked on establishing an HLA certification process under STANAG 4603, which is a certification route for HLA itself, not one NATO operates for NETN-FOM. What the document does define is federate-level technical conformance: a federate is "NETN-SMC-compliant" when it correctly implements and responds to the interactions its modules specify, and that is proven through interoperability testing between federates during federation development and exercise events, not by an accredited body auditing an organisation.
STANREC 4800 is the NATO recommendation that carries AMSP-04, and the mechanism by which it acquires whatever force it has. STANAG 4603 covers HLA, the architecture AMSP-04's object model is built inside; AMSP-04 assumes an HLA federation already exists rather than replacing it. Outside our catalogue, AMSP-04 also normatively cites IEEE 1516 (the HLA standard), the SISO Real-time Platform Reference FOM, the SISO C2SIM standard, the Military Scenario Definition Language, ISO/IEC 9834-8:2014 for UUID generation, ITU-R M.1371-5 for AIS message formats, NMEA-0183, and IEEE 1730-2022 for the Distributed Simulation Engineering and Execution Process.
AMSP-04 is a technical data specification. Meeting it is systems engineering work - implementing the specified object and interaction classes in a federate's own software - and that is not something a compliance platform does for you. What an organisation can and should document around it is the evidence trail a contract-driven technical requirement needs: which edition and which modules of NETN-FOM a federation agreement specifies, the federation agreement itself wherever AMSP-04 leaves a choice open, records of the interoperability testing that proved a federate's implementation actually works with others, and training records for the engineers who built to it.
That is where ComplyTrain fits: controlled documents for the federation agreement and design decisions, training records for the people who need to show they worked to the specified edition, and an audit trail of what was tested and when. It does not implement NETN-FOM in software, run the interoperability tests, or decide which modules a given exercise requires - that is set by the contract and the programme's own technical requirements, not by us. If AMSP-04 or a related NATO simulation standard has landed in a tender or training programme you support, the standards explorer shows what else sits alongside it, and we are glad to talk through what evidencing it would look like in practice.
Tell us how you need to work with AMSP-04 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.
No. AMSP-04 is carried by STANREC 4800, a NATO recommendation, so nations are invited to use it rather than committed to it. It becomes relevant to a supplier only when a contract, tender or training programme specifically names NETN-FOM conformance.
STANAG 4603 covers HLA, the simulation infrastructure and services federates use to interoperate. AMSP-04 defines NETN-FOM, the specific data model of object and interaction classes built on top of HLA for NATO education and training exercises. One is the plumbing, the other is the data that flows through it.
No. AMSP-04 describes no certification scheme, and NATO does not operate one for it. The only certification its own history mentions is a separate HLA certification process under STANAG 4603. Interoperability with AMSP-04 is demonstrated through testing between federates, not through a certificate.
Edition C, Version 1 (March 2025) restructures the model using newer HLA modelling techniques, adds the NETN-SMC module for common service control actions and the NETN-DIM module for representing disasters, and renames the module formerly covering physical entities to NETN-ENTITY.
From NATO's Standardization Document Database, or through a national standardization authority. NATO does not charge for its standardization documents. The related FOM modules and full technical documentation are published separately, free of charge, on GitHub.
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.