Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4603
National authorities and the defence M&S programmes that build to the standards they commit to
STANAG 4603 is NATO's agreement by which member nations commit to the IEEE 1516 High Level Architecture standards for simulation interoperability.
STANAG 4603 is not itself a technical specification. It is the agreement by which NATO nations commit to a technical specification that lives elsewhere: the IEEE 1516 series, better known as the High Level Architecture (HLA), the framework that lets modelling and simulation (M&S) systems built by different organisations, in different countries, interoperate. Edition 3 was promulgated on 16 March 2023 and supersedes Edition 2 of 17 February 2015; the document states the only substantive change is adding SISO-STD-012 to its list of other related documents and moving to the current STANAG template, so the underlying commitment to IEEE 1516, 1516.1 and 1516.2 carries over unchanged.
The agreement exists to answer one interoperability requirement: connecting Level 3 (command and staff), Level 2 (tactical) and Level 1 (individual and crew) M&S systems that are used for operations, training and analysis, where those systems are developed by, and located in, different NATO nations.
STANAG 4603 is addressed to participating nations and NATO bodies, not to a supplier or manufacturer directly. It binds a nation once ratified, as recorded in the NATO Standardization Document Database (NSDD); nations are invited to advise the NATO Standardization Office of their ratification and implementation intentions, and to report implementation details through NATO's electronic reporting tool afterwards. The document's own NATO Effective Date field reads "Not applicable", so there is no calendar date at which this reaches a company. A supplier meets STANAG 4603 the same way it meets any NATO architecture agreement: indirectly, when a national programme or a contract specifies HLA (IEEE 1516) compliance. That contract clause, not the STANAG itself, is where the obligation actually lands on a company building or maintaining a simulation federate.
The STANAG's own standards section names exactly three documents participating nations agree to implement: IEEE 1516 (the HLA framework and rules), IEEE 1516.1 (the federate interface specification) and IEEE 1516.2 (the object model template specification). Those three IEEE documents, not the two pages of the STANAG, carry the actual technical interoperability requirements.
Clause 1 of the implementation section covers new development: when procuring or developing new M&S systems, a nation ensures those systems are compliant with the latest IEEE series of standards cited, based on its own national requirements. The STANAG does not itself specify how compliance is demonstrated; it leaves that to the nation.
Existing systems are not stranded by a new edition. Clause 2 lets federations built to an earlier HLA edition continue operating without being brought into conformance with the current version, so a working system is not obliged to chase every revision. The only point where nations have to actively reconcile editions is clause 3's case: an older system that has to interoperate fully with, or be conformant with, a federation on a later edition. There, the STANAG puts the decision in the hands of the two simulation managers involved, who determine the least costly or best technical approach between them. It does not prescribe which approach to take.
Clause 4 has participating nations agree to use the HLA Compliance Certification Process established by the NATO Modelling and Simulation Group (NMSG), though the STANAG names the process without describing how it works. Clause 5 is a separate, more concrete obligation: submitting details of national M&S federates and federations proposed for NATO use, and submitting equivalent details to withdraw one, both in the format set out in SRD 4603.1. Clause 6 keeps the references current: whatever edition of a cited document is currently in effect is the applicable one for developing simulation federations, and a revision to one of those documents does not require the STANAG itself to be resubmitted for ratification. An administrative note reinforces the same point for the IEEE references specifically: they should always be checked for newer versions before being applied.
Two different mechanisms sit side by side in this STANAG, and they are easy to conflate. The HLA Compliance Certification Process (clause 4) is a NATO-administered process for certifying federates and federations for NATO use; the document gives no detail on how it is run, who conducts it, or what evidence it examines, so nothing more than its name should be assumed. Separate from that, clause 5's reporting obligation is not an audit at all: nations submit details of the federates and federations they propose for NATO use, and NATO records the ratification and implementation status nations report through the NSDD and the electronic reporting tool. Neither mechanism is a certification of a company or its management system, and neither is something a vendor can hold on a customer's behalf.
All three IEEE documents are published and sold by IEEE, not by NATO or by us. Copies are available from the IEEE Digital Library at www.ieee.org.
STANAG 4603 is an operational and technical agreement, not a management-system standard, and the work of meeting it is engineering work: building a federate or federation to the IEEE 1516 series, running it through NATO's HLA Compliance Certification Process, and reporting it through the SRD 4603.1 format. ComplyTrain does not do that engineering and does not perform HLA compliance testing.
What a programme or supplier needs alongside the engineering is the evidence trail: a documented procedure for how federate compliance decisions get made and recorded, a controlled record of which IEEE 1516 edition a given federate or federation was built against, and a held copy of what was submitted to NATO under SRD 4603.1 and when. That is the kind of documentation, version control and audit-trail work ComplyTrain supports for any process a defence supplier has to prove it followed - it does not map to specific HLA requirements, because at the informational support level none exist to map to.
What ComplyTrain does not do: it does not build, test or certify a simulation federate or federation, it does not run or replace NATO's HLA Compliance Certification Process, and it is not a source for the IEEE 1516 documents themselves, which are obtained from IEEE. The applicable tier for a given programme, and which of IEEE 1516, 1730 or SISO-STD-012 actually apply, is set by the contract and the customer's own interoperability requirement. If you want to see what else sits alongside STANAG 4603 in the catalogue, the standards explorer is the place to look, or talk to us about the documentation and evidence side of a defence M&S programme.
Tell us how you need to work with STANAG 4603 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.
It binds a nation once that nation has ratified it, as recorded in NATO's Standardization Document Database. For a supplier, it is mandatory only in the sense that any contract clause is: if a tender or contract calls up HLA (IEEE 1516) compliance, you have to meet it; the STANAG itself does not reach a company directly.
STANAG 4603 is NATO's two-page agreement to use HLA; IEEE 1516 (and 1516.1, 1516.2) is the actual technical specification, published and sold by IEEE, that defines what HLA compliance means. The STANAG names the documents; it does not restate their content.
No. The document names an HLA Compliance Certification Process run by NATO's own Modelling and Simulation Group for federates and federations proposed for NATO use. That process, and any HLA compliance testing, is outside what ComplyTrain does.
The STANAG does not require it. Federations built to an earlier HLA edition may continue operating without being brought into conformance with the current version. The exception is when that older system needs to interoperate fully with a federation running a newer edition, at which point the two simulation managers involved agree the technical approach between them.
From IEEE. STANAG 4603 names them and the editions NATO expects, but the documents themselves are published and sold by IEEE through the IEEE Digital Library, not distributed by NATO or by us.
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.