Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4607
Defence suppliers and system integrators whose NATO ISR contracts invoke STANAG 4607 or the AEDP-4607 GMTI format it covers
STANAG 4607 is NATO's agreement for member nations to implement AEDP-4607, the format for exchanging ground moving target indicator radar data between NATO ISR systems.
STANAG 4607 is the NATO Standardization Agreement covering the NATO Ground Moving Target Indicator Format (GMTIF). It is not itself a technical specification. It is the agreement by which NATO nations commit to implement AEDP-4607, Edition A, the publication that actually defines the binary, message-oriented format used "for the prompt dissemination of MTI data" among NATO Intelligence, Surveillance and Reconnaissance (ISR) systems. Implementation guidance sits in a further document, AEDP 4607.1.
This distinction matters more than it looks. A STANAG does not bind a supplier. It binds the nations that ratify it, and those nations implement it domestically; a supplier meets STANAG 4607, or more precisely the AEDP-4607 format it covers, only when a contract or tender names it, not because the agreement exists. Ratification and implementation are recorded separately in the NATO Standardization Document Database (NSDD), through NATO's electronic reporting tool.
This is Edition 4, promulgated 16 February 2024. It supersedes STANAG 4607, Edition 3, dated 14 September 2010. Worth knowing if you are reading an older copy: earlier editions of STANAG 4607 carried the GMTIF specification directly inside the STANAG. Current editions do not; they describe only the agreement to use AEDP-4607, whose own implementation guide, previously published as AEDP-7, Edition 2, is now AEDP 4607.1.
The stated aim is interoperability: to let NATO ISR systems exchange ground moving target indicator radar data in a common structure, and to give a system a standard way to request surveillance from a sensor and receive acknowledgement of whether that surveillance will happen. GMTIF is a binary, message-oriented format. It can stand alone, or it can travel embedded inside a frame-oriented format such as the NATO Primary Imagery Format, STANAG 7023, for the dissemination of primary imagery.
The STANAG's own agreement text sets out three things national authorities must do to implement STANAG 4607/AEDP-4607(A)(1):
A nation is considered to have implemented the STANAG once it has issued instructions that all equipment procured for its forces will be manufactured to the specifications the agreement details. Allies and NATO bodies then report implementation details through the same electronic reporting tool used for ratification.
There is no certification scheme described here, and no third party audits a supplier's or nation's conformance with STANAG 4607 itself. What exists is self-reporting: nations report their ratification, and later their implementation, through NATO's e-Reporting tool, with both recorded in the NSDD. The STANAG as a whole is separately reviewed in accordance with AAP-03, with the result of that review also recorded in the NSDD.
STANAG 4607 is an operational agreement, not a management-system standard: what it points to is a data format and a set of national reporting steps, not a quality system to certify. Where it reaches an organisation, because a contract names STANAG 4607 or the AEDP-4607 format it covers, the compliance work is procedural: the instruction that procured equipment will meet the specified format, records of the AEDP 4607.1 guidance followed, and the internal sign-off that shows the GMTI data and surveillance-request formats were built and tested as specified.
ComplyTrain gives a team a place to hold that documentation, train people against the procedure, and keep the audit trail an assessor or customer would ask to see. It does not implement the GMTIF binary format, generate or validate GMTI data, or connect to a radar sensor; building and testing the format itself is engineering work, and ComplyTrain supports the process and paperwork around it rather than the format itself.
In defence, the applicable tier and the standards that come with it are set by the contract and the customer's quality clause, not by this page. Use the standards explorer to see what sits alongside STANAG 4607 and AEDP-4607, and talk to us about the documentation and training trail your contract requires.
Tell us how you need to work with STANAG 4607 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.
Only through ratification and a contract. STANAG 4607 binds the NATO nations that ratify it, and a nation implements it once it instructs that equipment procured for its forces will meet the specification. It reaches a supplier when a tender or contract names STANAG 4607 or AEDP-4607, not automatically.
STANAG 4607 is the agreement: NATO nations' commitment to use a common format. AEDP-4607, Edition A is the specification of that format, the NATO Ground Moving Target Indicator Format (GMTIF), with its own implementation guide in AEDP 4607.1.
Yes. Earlier editions carried the GMTIF specification directly inside the STANAG document itself. Current editions only record the agreement to use AEDP-4607, which now carries the specification separately.
No certification scheme is described. Nations self-report their ratification and implementation status through NATO's electronic reporting tool, and the results are recorded in the NATO Standardization Document Database.
Yes. The document allows it to be sent as a stand-alone format or embedded in a frame-oriented format such as STANAG 7023, the NATO Primary Imagery Format, for dissemination alongside primary imagery.
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.