Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMSP-03
NATO and nations designing distributed synthetic training environments, and the system developers and integrators who build them
NATO's reference architecture for building distributed synthetic training environments, recommended rather than mandated, that nations and NATO M&S programmes consult when designing a collective training and exercise capability.
AMSP-03 is NATO's reference architecture (RA) for Distributed Synthetic Training (DST), published by the NATO Modelling and Simulation Group (NMSG) through the NATO Standardization Office. It provides "a common architectural approach for designing, developing and implementing Distributed Synthetic Training (DST) environments," built around nine architecture principles and a catalogue of Architecture Building Blocks (ABBs) and Architecture Patterns rather than a fixed technical specification with its own pass or fail criteria. Edition B, Version 1 (May 2022) is the current edition, replacing Edition A (2018).
AMSP-03 is covered by a NATO Standardization Recommendation, STANREC 4799, which recommends rather than binds: the document states plainly that "NATO and partner nations should use AMSP-03 when designing and implementing DST environments to support CTE." For the specific interoperability standards a project should build to, AMSP-03 does not set its own list; it uses AMSP-01, the NATO M&S Standards Profile (STANREC 4815), "as the source of NATO mandated and recommended M&S standards." The one standard it treats as mandated rather than recommended is the High Level Architecture, bound through STANAG 4603, not through AMSP-03 itself.
The document names its own audience directly (section 1.3): NATO and nations "implementing DST within their organizations and participating in NATO CTE events"; system developers, for whom the RA provides "requirements and standards with enough details to support the development and evaluation of compliance"; integrators, for whom it is "a reference to define specific constraints and directions for implementing a DST environment"; and the NMSG itself, which uses it to identify requirements for future standards work. A commercial supplier is not addressed by name; where the RA reaches one, it does so through a contract, tender or federation agreement that names AMSP-03 or one of the standards it recommends.
The RA rests on nine principles set out in Annex A: support training and mission rehearsal, enable Live, Virtual and Constructive (LVC) assets, enable flexibility and evolution across generations of technology, use open standards, comply with NATO M&S policies and standards, comply with security rules up to NATO Secret classification, provide cross-domain security for multiple security domains in one exercise, provide a representative "fair-fight" training environment, and provide cost-effective training solutions. The "comply with NATO policies and standards" principle is the one that names the baseline agreements a DST environment is expected to follow: AMSP-01 under STANREC 4815, the High Level Architecture under STANAG 4603, the NETN FOM under STANREC 4800, and AMSP-03 itself under STANREC 4799.
The RA organises a DST environment into five layers. Operational Capabilities cover the reference training process (Bi-SC 75-3 and AMSP-05) and the engineering processes that build the environment itself, including the Distributed Simulation Engineering and Execution Process (DSEEP) and its Multi-Architecture Overlay (DMAO). User-Facing Capabilities are the national Training Systems brought to an exercise and the M&S Applications staff use to prepare and control it: Scenario Preparation, Synthetic Environment Modelling, Simulation Control, and Analysis and Debrief Applications. Back-End Capabilities are the M&S Services, Synthetic Environment Services, C2 Mediation Services, Scenario and Model Repository Services, and Core Services such as geospatial, time synchronisation and communication services, that support them. CIS Security and Service Management and Control are cross-cutting layers: the former governs the release of simulation data across security domains, the latter the coherent start, stop, monitoring and logging of every other component.
Each building block's section states functional and non-functional requirements as direct obligations and names the standard that satisfies them. Distributed Simulation Services, for example, carry a functional requirement to let connected systems exchange simulation data using NATO standards for distributed simulation, naming the High Level Architecture under STANAG 4603 and the NETN FOM recommended under STANREC 4800. Scenario Preparation Applications "shall provide the functionality to import and export a scenario to a file" and to "automate the translation of scenario information to an executable scenario." An auditor or programme reviewer working from this document looks for a federation agreement naming the chosen standards and evidence that each ABB's stated requirements were actually built, not a certificate.
The RA is also candid about what it leaves out. Common cyber security measures, national and NATO security accreditation, and the physical connection of a nation's network to shared infrastructure are explicitly out of scope, left to national authorities and existing NATO policy. The construction of high-detail 3D terrain content is flagged as a known gap: there is "no standard to serve this content via web services."
AMSP-03 names no assessor or accreditation body for an organization, and there is no certification for being "AMSP-03 compliant." What it does describe is technical interoperability testing between individual participant systems ahead of an exercise: "Certification tools shall be provided to expedite test & integration of new participants," covering both protocol-level and application-level conformance, naming the NATO Integration, Verification and Certification Tool (IVCT) and a Test Federate. That checks one Training System's implementation against agreed protocols; it is not a scheme that certifies a company. Where a DST environment needs it, Verification, Validation and Accreditation (VV&A) of the simulation itself is a separate exercise, carried out under IEEE 1516.4 or the SISO GM-VV methodology and decided by a national or programme Technical Authority.
NATO publishes AMSP-03 through the NATO Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for AMSP-03 is the source.
AMSP-03 describes structure and patterns for a DST environment; the work of designing, federating and running one happens in engineering practice and in the exercise itself, not in a compliance tool. Once a programme has picked its architecture, for example a federation built to STANAG 4603's High Level Architecture with the NETN FOM, the evidence trail that follows is procedural: federation and data-release agreements to draft and version, VV&A plans and reports for the specific simulation, training records for the engineers and staff who build and run the environment, and a documented record of which building blocks and standards a given exercise actually used. ComplyTrain, as an auditable quality management system, supports exactly that kind of document control and evidence trail in general.
What ComplyTrain does not do: it does not design, build, integrate, test or accredit a distributed synthetic training environment, and it makes no claim that ComplyTrain or a customer is "AMSP-03 certified" or "NATO M&S qualified," because the RA describes no such certification for anyone to hold. Which building blocks and standards apply to a given programme is set by that programme's own contract and quality clause. The standards explorer shows what else sits alongside AMSP-03, and we are glad to talk through what a specific contract or federation agreement actually requires.
Tell us how you need to work with AMSP-03 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, not on its own. AMSP-03 is covered by STANREC 4799, a Standardization Recommendation, and the document states that "NATO and partner nations should use AMSP-03 when designing and implementing DST environments to support CTE," the language of an invitation rather than an obligation. It becomes a live requirement for a supplier or integrator only when a contract, tender or programme document names it.
AMSP-01 is NATO's standards profile: a survey that lists which M&S standards exist and which NATO currently recommends or mandates. AMSP-03 is the reference architecture: it defines the building blocks and patterns for a distributed synthetic training environment and, for the standards behind each block, points back to AMSP-01 rather than repeating that list itself.
AMSP-03 recommends the High Level Architecture for distributed simulation, and that recommendation is the one point where a stronger instrument applies: HLA is mandated through STANAG 4603, not through AMSP-03. Everything else in the RA, its scenario, geospatial, and communication building blocks among them, is a recommended pattern that a project architecture can tailor to its own requirements.
No. AMSP-03 names no certifying body, accreditation scheme or audit process for an organization. The certification it does describe, using the NATO IVCT and a Test Federate, tests one participant system's protocol and application-level interoperability ahead of an exercise, not a company's compliance with the standard.
Edition B, Version 1, published May 2022. It replaces Edition A, developed by MSG-106 and published in 2018 under the same STANREC 4799 cover.
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.