Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AOP-63
The engineers and programme managers who plan a national in-service surveillance programme, and the government responsible for a munitions stockpile
AOP-63 is NATO's guidance on choosing which munitions to sample and how to select tests for in-service surveillance, feeding a nation's decisions on stockpile safety and service life.
AOP-63 is the NATO Allied Ordnance Publication that guides how a nation chooses which munitions to examine, and what kind of test to run, when it carries out in-service surveillance (ISS) of its own stockpile. In Service Surveillance itself "involves the selection and examination of items from the service inventory," and the evidence it produces is what lets a nation judge whether a stockpile remains safe to store and use, and whether a munition's predicted service life should be revised. AOP-63 sits underneath AOP-62, which sets out the process, documentation and roles a surveillance programme needs, and beside AOP-64, which covers the condition-monitoring and destructive-testing side of the same activity. This is Edition A, Version 1, promulgated February 2017, and nothing in the document points to an earlier edition it supersedes.
NATO nations agree to use AOP-63, together with its companion publications, through the Standardization Agreement recorded as STANAG 4675: "the agreement of nations to use this publication is recorded in STANAG 4675." AOP-63 does not bind a company on its own account, because it is written for the government running the surveillance programme rather than for a supplier meeting a contract. Where a company is involved, it is because a national defence customer's own in-service surveillance programme calls for sampling, testing or reporting work under contract, and AOP-63 is the framework that shapes how that work is scoped and read, not a document that reaches a supplier directly. Once a munition has entered service, "the owning government becomes responsible for the safety and suitability of the system from that date," and stays responsible, with surveillance expected to continue, until "the entire inventory has been disposed of."
AOP-63 frames in-service surveillance as a way to catch degradation in a munition's energetic materials before it becomes a safety problem, against a permanent pressure the document names plainly: "there is however a continual need for economy and operational efficiency which leads to a pressure to minimize the amount of testing, amount of inspections." It draws a line between what it calls Basic Objectives, the mandatory check that a system "remains safe and suitable throughout its service life," and Extended Objectives, where the same surveillance data is also used to argue for extending a munition's predicted service life. The second is the harder claim: "many degradation processes are non-linear, accelerating over time," so a handful of measurements taken periodically may not predict the end of life reliably.
The planning chapter assumes a System Programme Plan already exists under AOP-62, and works through how a Coordinator scopes it: clarifying which components and sub-components of a wider weapon or launch system count as critical items for surveillance, deciding whether the nature of a test means an item has to be examined as a complete round rather than in isolated sub-components, and judging when it is acceptable to draw on material procured and stored specifically for surveillance rather than pulled from operational stock.
AOP-63 explains how munitions sharing a manufacturer, model, age and environmental history can be treated as one surveillance group, so that "munitions can be grouped to form a specific population from which a statistical sample can be examined in detail" on the group's behalf. Grouping rests on an assumption of homogeneity: unless there is evidence otherwise, batches meeting the grouping criteria are assumed to function and age uniformly. The AOP then sets out two different logics for drawing a sample from that population. Probabilistic sampling lets a nation calculate a numerical confidence in the result, and suits reliability and performance questions. Non-probabilistic sampling, including expert-judgement "fleet leader" selection, is used where a genuinely random sample cannot practically be recovered; it is aimed at safety rather than at a statistical figure, and the AOP is explicit that "reliability cannot be estimated in this way and confidence in results cannot be estimated numerically."
AOP-63 names the factors that drive how large a sample needs to be, margin of error, confidence level, population variability and population size, without fixing a number: the final figure is agreed between the System Support Engineer and the Coordinator for each programme. It treats timing the same way, describing three patterns a programme can choose between rather than prescribing one: an interval that stays constant through the system's life, one that shortens as the system ages to track accelerating degradation, and one set case by case in response to an emerging issue.
AOP-63 distinguishes basic testing, which measures a parameter at a single point in time, from predictive testing, which also estimates the rate at which that parameter is changing. It explains why the distinction matters for a safety judgement: given the non-linear, exponential nature of degradation, a basic reading taken too early can look benign right up until it stops being benign. A table in the document groups the broad categories of testing a surveillance programme can draw on, from non-destructive examination through to destructive testing and system-level ageing trials, so a programme can match the depth of examination to the decision it needs to support, without the AOP fixing which category applies to which munition.
Three annexes (A to C) show how the same documentation structure, a System Programme Plan, Item Test Plans and Item Implementation Plans, scales differently for a complex guided weapon system, a medium-calibre gun system, and a simple small-arms system, without repeating the figures the annexes themselves give.
NATO's Standardization Document Database is the authoritative source for AOP-63. NATO's documents are free of charge; we credit NATO for the catalogue and neither sell nor host a copy ourselves.
The work AOP-63 describes, choosing a surveillance sample, agreeing which tests to run and how often, and turning the results into a judgement about stockpile safety and service life, happens in engineering and technical assessment, not in software. Evidencing it means holding a current Item Test Plan and Item Implementation Plan, records of every surveillance sample drawn and every test result, and a documented rationale for how those results feed the safety and service-life decisions a nation makes.
ComplyTrain gives a programme team a controlled place to hold that evidence trail: the surveillance plans and their revisions, the test records and results as they come in, the training records for the people running the programme, and the audit trail behind any change to a sampling group, a test interval or a life-extension decision. That is the same document-control and evidence discipline ComplyTrain supports across any technical standard's paperwork, not a mapping to AOP-63's own sampling logic.
What ComplyTrain does not do: it does not select a surveillance sample, choose or run a test, or decide whether a stockpile remains safe or how long it will last. Those judgements belong to the System Support Engineer, the Coordinator and the national authority responsible for the stockpile.
Which tier of surveillance a programme needs, and what a contract requires a company to deliver, is set by the contract and the customer's quality clause, not by us. See what else sits alongside AOP-63 in the standards explorer, and talk to us about the documentation trail behind an in-service surveillance programme.
Tell us how you need to work with AOP-63 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 directly. AOP-63 does not bind on its own account: NATO's Letter of Promulgation records that nations' agreement to use it "is recorded in STANAG 4675," and it is written for the government running an in-service surveillance programme, not for a supplier. A company meets it only where a national defence customer's own surveillance contract calls for the sampling or test work AOP-63 describes.
No. It names the factors that shape those decisions, margin of error, confidence level, population size and variability for sample size, and the pace of degradation for timing, but it leaves the actual numbers to the System Support Engineer and Coordinator running each programme, agreed for each stockpile rather than fixed by the AOP itself.
AOP-62 sets out the process, documentation and roles a surveillance programme needs, and AOP-63 explicitly assumes that process is already in place before it offers guidance on sample and test selection. AOP-64 covers the condition-monitoring and destructive-testing side of the same in-service surveillance activity, and AOP-63's own overview of testing categories points a reader toward it.
No. AOP-63 names no certification or assessment scheme. What it produces is surveillance evidence that feeds a nation's own safety and suitability review, the kind of assessment AOP-15 sets out, and any decision to revise a munition's service life. Where a company runs part of the surveillance work under contract, the government customer checks it against the agreed test plan, not an accredited certification body.
A basic test measures a parameter at a single point in time; a predictive test also estimates the rate at which that parameter is changing. AOP-63 explains that predictive testing matters more for a safety judgement because degradation in energetic materials is rarely linear, so a basic reading taken too early can look fine right up until it stops being fine.
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.