Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 5527
NATO nations and NATO bodies implementing ADatP-36 for friendly force tracking system interoperability
STANAG 5527 is NATO's agreement committing member nations to implement ADatP-36 Edition B, the standard for friendly force tracking system interoperability. It binds nations, not suppliers directly.
STANAG 5527 is a NATO Standardization Agreement, not a technical specification in its own right. Its whole content is the commitment it creates: participating nations "agree to implement the following standard," which is ADatP-36, Edition B, the Allied Data Publication that actually defines Friendly Force Tracking Systems (FFTS) interoperability. Everything a reader usually wants from a standard - the data format, the message structure, the interface detail - lives in ADatP-36, not in this two-page cover.
That distinction matters because a STANAG binds a nation, not a supplier. Ratification and implementation are the nation's steps, recorded in the NATO Standardization Documents Database (NSDD); a supplier meets ADatP-36's requirements only when a contract or tender names them, never because the STANAG number appears in a catalogue.
The stated aim is "to respond to the following interoperability requirements": "to provide friendly ground force information throughout the NATO Command Structure, within the respective chain of command, and to increase situational awareness of the land battle space." The document names the payoff directly: "improved overall situational awareness, improved command and control, force multiplication, improved synchronization of forces, and reduced risk of fratricide." This is Edition 2, dated 24 April 2025, and it "supersedes the following document: STANAG 5527, Edition 1, dated 20 March 2017."
The document addresses NATO nations and NATO bodies directly - it "is effective upon receipt for use by the participating nations and NATO bodies." Partner nations are separately "invited to provide their implementation details through the electronic reporting tool (e-Reporting)." No supplier, manufacturer or contractor is named anywhere in the text. Nations that have not yet examined their ratification are invited to "advise the NSO of their intention regarding its ratification and implementation" - ratification and implementation are treated as two distinct steps, and a nation can do one without the other being complete.
The "Implementation of the Agreement" section is where the actual content sits. Nations "should add to the current and future national ground forces tracking systems, interfaces to produce/consume FFT data in compliance with the ADatP-36 standard," and "should augment the current and future Command and Control systems with interfaces to consume the track position information provided in compliance with the ADatP-36 standard." Nations "should also plan for the development and deployment of the FFT services required to enable seamless ADatP-36 information exchange," including security devices that let FFT data cross "between different security domains." The NATO Effective Date is stated as "Not applicable" - there is no fixed date by which this must happen; it proceeds through national ratification and implementation instead.
STANAG 5527 sets out no data format, message structure or interface detail itself - all of that is in ADatP-36. It also names no supplier obligation: every duty in the text runs to "nations," "NATO bodies" or "Allies," never to a contractor. A reader looking for the technical FFT specification needs ADatP-36, not this cover.
STANAG 5527 "is to be reviewed in accordance with AAP-03," and the result is recorded in the NSDD. That is a periodic check on whether the agreement itself is still current, not an assessment of any organisation, system or supplier. NATO does not certify a tracking system or a Command and Control interface against this STANAG, and the document makes no such claim.
The agreement is supervised under the authority of NATO's Digital Policy Committee (DPC), within its Navigation and Identification remit (CaP2).
The STANAG names two other agreements under "other related documents": STANAG 7149, which covers APP-11, the NATO message catalogue, and STANAG 2019, which covers APP-06, NATO joint military symbology. Both inform where ADatP-36 sits among NATO's other communications and information standards rather than binding anything themselves. AAP-03 governs how STANAG 5527 itself is reviewed. The specification it commits nations to is ADatP-36, Edition B.
STANAG 5527 itself is a cover agreement between nations, so there is nothing in this document for a supplier to implement directly. The work sits one level down, in ADatP-36, and in whatever a specific contract or task order actually asks a supplier to build or prove.
In practice that work looks like documented procedures for interface development and testing tasks a contract assigns, training records showing the people responsible understand the FFT data requirements, and a clear evidence trail an auditor or customer quality representative can follow when interoperability is questioned. ComplyTrain gives an organisation a place to hold those procedures as controlled documents, keep training current, and maintain the corrective-action trail that an interoperability review asks for.
ComplyTrain does not design or build tracking-system or Command and Control interfaces, decide what FFT capability a mission or contract requires, or substitute for ADatP-36's own technical content. That engineering work stays with the nations and NATO commands implementing ADatP-36. The applicable tier and which interoperability requirements a supplier actually faces are set by the contract and the customer's quality clause - see the standards explorer for what sits alongside this agreement, and talk to us about the evidence trail behind it.
Tell us how you need to work with STANAG 5527 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 it, recorded in the NATO Standardization Documents Database. For a supplier, ADatP-36's friendly force tracking requirements apply only when a specific contract or tender invokes them.
STANAG 5527 is the agreement by which nations commit to implement a standard; ADatP-36, Edition B, is that standard. The STANAG's text states plainly that "participating nations agree to implement the following standard" - ADatP-36. All the technical detail on friendly force tracking data and interfaces lives in ADatP-36, not in the STANAG.
No. STANAG 5527 names no accreditation, notified-body or audit scheme. Its only stated check is a periodic review of the agreement itself, carried out in accordance with AAP-03 and recorded in the NSDD - that is a review of whether the STANAG is current, not a certification of any organisation or system.
The document states that this edition, dated 24 April 2025, "supersedes the following document: STANAG 5527, Edition 1, dated 20 March 2017." The text does not itemise what changed between the two editions.
The document's obligations run to "nations," "NATO bodies" and "Allies," who report ratification and implementation details through NATO's electronic reporting tool. It names no supplier, manufacturer or contractor directly; a supplier's role is set by whatever contract or tender invokes ADatP-36.
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.