Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4855
National authorities and NATO bodies implementing SISO-REF-010, and defence suppliers working to a contract or task order that invokes it
STANAG 4855 is NATO's agreement committing member nations to implement SISO-REF-010, the reference for enumerations for simulation interoperability; it binds nations, not suppliers, directly.
STANAG 4855 is a NATO Standardization Agreement, currently Edition 1, dated 15 March 2023. It is not a technical specification. It is the agreement by which NATO nations commit to implement SISO-REF-010, Reference for Enumerations for Simulation Interoperability, the SISO reference document that defines the schema and repository this STANAG covers. The schema and repository content itself lives inside SISO-REF-010, not inside this four-page cover. Read on its own, STANAG 4855 requires almost nothing of a supplier directly. Its obligations run to nations, and it reaches a contractor only indirectly, once a nation has implemented it and a contract or task order names SISO-REF-010.
STANAG 4855 is explicit that it binds nations rather than organisations. It "is effective upon receipt for use by the participating nations and NATO bodies." Its letter of promulgation describes the enclosed agreement as one "which has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith." Ratification and implementation are separate steps: nations that have not already done so are invited to "advise the NSO of their intention regarding its ratification and implementation." So "is STANAG 4855 mandatory" has no single answer. It depends on whether a given nation has ratified and implemented it, and, for a supplier, on whether a specific contract invokes SISO-REF-010 as a result.
The stated aim "is to respond to the following interoperability requirements," and that requirement is a single sentence: "To define a consistent schema and repository for enumerations for distributed simulation." Under "Agreement," "Participating nations agree to implement the following standard" - SISO-REF-010, named in the text as "SISO-REF-010 - REFERENCE FOR ENUMERATIONS FOR SIMULATION INTEROPERABILITY." None of this is written as a duty on a supplier; it is a duty on the nation, and on the NATO bodies that implement it.
A reader who only has STANAG 4855 in hand does not yet have the enumeration schema or repository itself. SISO-REF-010 holds that content. This STANAG names no other related document - "OTHER RELATED DOCUMENTS" is answered "None" in the text - and it does not say where to obtain SISO-REF-010.
STANAG 4855 "is implemented by a nation or by a NATO body when it has issued instructions that all relevant future systems, which interface to NATO and other national systems when engaged in NATO operations, will conform to the specifications detailed in SISO-REF-010 Reference for Enumerations for Simulation Interoperability (most recent edition)." Allies and NATO bodies "shall provide implementation details through the electronic reporting tool (e-Reporting)," and "Partner nations are invited to provide their implementation details through the electronic reporting tool (e-Reporting)." The NATO Effective Date is stated as "Not applicable," and the document states plainly that "This STANAG does not supersede any document." The STANAG "is to be reviewed in accordance with AAP-03. The result of the review is to be recorded within the NSDD," and the agreement is supervised under NATO's modelling and simulation standardization committee chain.
STANAG 4855 names no supplier obligation directly: every duty in the text runs to "nations," "NATO bodies" or "Allies," never to a contractor or manufacturer. It also names no assessment or certification scheme of any kind. The only stated check is that the agreement itself is reviewed periodically against AAP-03, not that an organisation, a system or a piece of software is certified.
STANAG 4855 itself gives a supplier nothing to implement in software: it is an agreement between nations, and the enumeration schema sits in SISO-REF-010. Where ComplyTrain fits is the paperwork trail behind whichever interoperability requirement a contract actually assigns: documented procedures for tracking which edition of SISO-REF-010 a system is built to, training records for the engineers who configure or maintain interoperable simulation systems, and a clear corrective-action trail an auditor or customer quality representative can follow when conformance is questioned. That work is done in engineering and evidence-keeping, not by a compliance tool building the schema itself, and ComplyTrain's role is to hold the evidence that it happened.
ComplyTrain does not define or verify an enumeration schema against SISO-REF-010, build or test simulation software, or substitute for the reference document itself - that is work carried out by the engineers and standards bodies that maintain it. The applicable tier and which interoperability requirements a supplier actually faces are set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 4855 - if you are weighing up what a tender actually requires, we're glad to talk it through.
Tell us how you need to work with STANAG 4855 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.
Not on its own. A STANAG binds a nation once that nation has ratified and implemented it, and it reaches a supplier only when a contract or task order names SISO-REF-010. Whether it applies to a given programme is a question for the contract, not for this page.
STANAG 4855 is the cover agreement: it commits nations to implement SISO-REF-010 but contains no schema or repository content itself. SISO-REF-010, Reference for Enumerations for Simulation Interoperability, is the SISO document that actually defines the schema and repository for enumerations used in distributed simulation.
No. STANAG 4855 describes no certification or accreditation scheme. Its only stated check is a periodic review of the agreement's own currency, carried out in accordance with AAP-03. NATO does not certify organisations or systems against a STANAG.
Edition 1, dated 15 March 2023. The document states that it does not supersede any earlier document.
The document names nations, NATO bodies, Allies and partner nations as the parties that ratify, implement and report on it. It does not name a supplier or contractor directly; a contractor's obligations come from whatever contract or task order invokes SISO-REF-010, not from this STANAG.
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.