Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AOP-62
Programme managers, coordinators and technical staff running a NATO munitions in-service surveillance programme, and the contractors named in its supporting contract clauses
NATO's guidance on planning and running an in-service surveillance programme that checks a munition stays safe, reliable and fit for use throughout its service life, up to disposal.
AOP-62 is NATO's general guidance on in-service surveillance (ISS) of munitions: the ongoing programme of monitoring, testing and reporting that confirms a munition stays safe, reliable and fit for its intended use throughout its service life, not only at the point it first enters service. Munitions degrade in store and in use however carefully they are handled, and the service life given to a system at qualification is a prediction rather than a guarantee. ISS is the mechanism that confirms, extends or cuts short that prediction using real evidence from the field rather than the original assumptions alone.
The guidance frames ISS as several information streams working together: routine in-service reporting; in-service proof testing carried out during normal service or training use; condition monitoring, which is usually destructive examination of a small number of items broken down for inspection; in-service monitoring, which is non-destructive and leaves the item available for further use; environmental monitoring, which records the real temperature, humidity, shock and vibration a system experiences rather than the environment originally assumed; and predictive testing, which investigates likely degradation ahead of when it would otherwise be found. AOP-62 explains why each stream exists and how they combine. It does not itself set the test methods, sample sizes or acceptance limits that any one of them uses.
The guidance is written for the people who plan and run a surveillance programme on behalf of a NATO nation: an Acquisition Programme Manager and a Through Life Programme Manager who fund and set policy for it, a Coordinator who runs the programme day to day, System Support Engineers who provide technical judgement, and Programme Managers, Test Engineers and Field Support Engineers who carry out the work for each item under surveillance. AOP-62 is explicit that Test Engineers can come from the procuring government, a vendor government, the design authority, or an independent commercial organisation.
A company does not sign up to AOP-62 directly. It reaches a supplier because a customer nation has ratified STANAG 4675, the agreement recorded as nations' commitment to use this AOP, and has then written the resulting obligations into a specific contract: the guidance tells the Acquisition Programme Manager to include data-requirement clauses and an ISS support clause in the prime contract, so that the design authority or manufacturer attends meetings, resolves action items, and comments on test plans and reports. What a company is actually asked to do, and when, is set by that contract clause rather than by the AOP itself.
AOP-62 places the start of the process earlier than most readers expect: the guidance says the process of ensuring safety and suitability for service ideally begins during the munitions development phase, when a failure-modes analysis is first carried out, well before the system enters service. Once a System Programme Plan exists and the system is fielded, surveillance becomes continuous: reviewed periodically, after operational deployment, during training, and whenever monitoring data gives cause for concern. AOP-62 is direct about when it ends: only on disposal. An item withdrawn from service for safety or any other reason still has to be monitored until it is finally disposed of, because it cannot simply sit in storage unwatched.
The substance of AOP-62 is the set of documents a programme is expected to produce and keep current. A System Programme Plan is the top-level, system-wide document: objectives, scope, roles and the list of items that need surveillance. Each item then gets its own Item Test Plan, covering that item's objectives, sampling concept and critical characteristics, and an Item Implementation Plan, which is the working agreement between the programme office and the test agency for how a particular test or sequence of tests will be carried out, alongside an Environmental Monitoring Plan and regular progress reports. AOP-62 allows a smaller or less sensitive programme to produce shorter versions of all of these, but says plainly that each element of the documentation is still needed.
There is no certification anyone can hold under AOP-62. Instead, after each reporting period, a review panel built around the Coordinator, the relevant Programme Manager and the primary System Support Engineer decides whether the system remains reliable, safe and suitable for service. What follows is one of a small set of outcomes: continue as planned, revise the Item Test Plan or Item Implementation Plan, suspend testing that has turned out not to be appropriate, or recommend withdrawal from service, after which the item still has to be monitored through disposal. The evidence the panel works from is documentary: progress reports at agreed intervals, a final report at the end of each surveillance cycle that compares results against criteria and earlier findings, and immediate notice of any safety failure.
AOP-62 deliberately stays at the level of programme and documentation. The sampling approach and detailed test procedures it points to are set out in AOP-63; the condition-monitoring detail is set out in AOP-64; the earlier Safety and Suitability for Service assessment and Whole Life Assessment basis that ISS builds on sit in AOP-15 and AOP-46; and the environmental conditions and test methods a programme extends into come from the AECTP-100, AECTP-300, AECTP-400 and AECTP-600 series. A further set of NATO STANAGs on explosive and munitions test methods sits behind condition monitoring and predictive testing whenever a programme needs to re-examine an explosive's properties against its original qualification data.
AOP-62 is an operational standard: the surveillance itself, condition monitoring, environmental data logging, predictive testing and the review panels that decide whether a system stays in service, happens in laboratories, depots and review meetings, not in software. What a programme still needs, and what ComplyTrain supports, is the documentation and evidence discipline the guidance insists on: a controlled, version-tracked home for the System Programme Plan, Item Test Plans and Item Implementation Plans; training records for the people who carry out the surveillance; a record of each reporting cycle, each review-panel decision and any resulting change to a test or implementation plan; and a place to hold the progress reports and final reports the guidance calls for, so a programme can show what it did and when.
ComplyTrain does not run the surveillance itself. It does not perform condition monitoring, environmental data logging, predictive testing or any physical inspection of a munition, and it makes no safety, reliability or suitability-for-service determination: those stay with the System Support Engineers, Test Engineers and the customer's own review panel.
In defence, which clauses of a contract actually pull a supplier into an ISS programme is set by the contract and the customer's quality clause, not by AOP-62 alone. See the standards explorer for what sits alongside AOP-62 in the NATO munitions surveillance library, and talk to us about how ComplyTrain can support the evidence trail your contract actually requires.
Tell us how you need to work with AOP-62 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.
AOP-62, "In-Service Surveillance of Munitions General Guidance," is NATO's guidance on planning and running a programme that checks a munition stays safe, reliable and fit for use throughout its service life. It covers why surveillance is needed, when it should start, the roles involved, and the documentation a programme should produce, rather than the detailed test methods themselves.
It binds through STANAG 4675: nations that ratify that agreement commit to using this AOP as the basis for their own surveillance programmes. For a company, it reaches a contract only where the customer writes a data-requirement or ISS support clause into it, so whether it applies to a given programme is a contractual question rather than a general one.
AOP-62 is the general guidance: why surveillance happens, who runs it, and what documentation it needs. AOP-63 covers the sampling and test procedures in detail, and AOP-64 covers condition monitoring in detail. AOP-62 points to both rather than repeating their content.
No. AOP-62 describes no certification or accreditation scheme for a company. The closest mechanism is a government-run review panel that periodically judges whether the munitions system itself remains safe, reliable and suitable for service, which is a judgement about the inventory item, not about the organisation supporting the programme.
Only on disposal. AOP-62 is direct that even an item withdrawn from service for safety or other reasons still needs monitoring until it is finally disposed of.
From the NATO Standardization Document Database, which lists it free of charge. NATO's documents are not sold by ComplyTrain and we do not host copies of them.
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.