Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AOP-68
NATO nations' ordnance and ammunition design and procurement authorities, and the manufacturers building to their requirements
NATO's Allied Ordnance Publication standardising nose fuze contours and matching projectile cavities so a fuze from one nation's stock fits a projectile from another's.
AOP-68, NATO's Allied Ordnance Publication on nose fuze contours and matching projectile cavities, standardises the physical and ballistic interface between a nose fuze and the artillery or mortar projectile it seats in. The point of it is interchangeability: a fuze made by one NATO nation is meant to fit, and perform correctly in, a projectile made by another. That interchangeability is not only mechanical. A fuze fitted to a given projectile type is required to follow the same ballistic trajectory to the same burst point as the fuze the projectile was designed around, and firings, not geometry alone, are used to confirm that. The current edition, Edition A Version 1, was promulgated in August 2019. AOP-68 is covered by STANAG 2916: AOP-68 carries the technical content, and a nation's ratification of the STANAG is what commits it to the interface AOP-68 defines.
AOP-68 speaks throughout to "participating nations" rather than to a company. It reaches a fuze or projectile manufacturer indirectly, through whichever national design authority, requirement or contract specifies conformance with its contours and cavities. Because it governs the interface itself, the point to work to it is at design, when the fuze contour or cavity geometry is fixed; changing either afterward, once tooling or qualification is done, is a redesign rather than an adjustment.
AOP-68 does not carry its requirements mainly as prose. Its annexes hold the actual interface: a preferred set of fuze contour and projectile cavity combinations, a second, wider set of combinations that remain permissible even though not preferred, one permissible fuze adapter, and preferred and permissible setter-slot arrangements for mechanical time fuzes. All of that lives in dimensioned figures rather than in the clauses, which is why this page describes what the standard is for rather than reproducing any of it.
The permissible set is a standing category, not a deprecated one: a combination does not stop being valid just because a preferred alternative exists. What does narrow it over time is a specific mechanism in Chapter 1: nations using deep-intrusion fuzes or fuze cavities are asked to provide forecast dates for when they expect to stop using them, and NATO uses those dates in periodic review to decide when to delete a combination.
A handful of clauses show that AOP-68 is not a purely mechanical rulebook. Certain fuze/projectile combinations may need close control of fuze weight, centre of gravity and contour, purely for ballistic reasons, and the document illustrates this with one worked naval example rather than stating it as a general rule. Most fuze/cavity mating threads use standard sizes, but some applications deliberately use a non-standard thread specifically so that a fuze and cavity that should not mate cannot be forced together, a safety measure rather than an oversight. Where a mortar projectile is pre-fuzed at the point of manufacture with no intention of re-fuzing it in the field, the intrusion dimensions that would otherwise apply become optional. And any deviation from the maximum material condition specified for the fuze intrusion and projectile cavity has to take operational and safety considerations into account.
Introducing a genuinely new fuze-setting technique that needs its own setter slot is the one place the document requires an external sign-off: NATO AC/326 approval, before the resulting design can be type classified. AOP-68 is explicit that the need for special setters for future hand-set fuzes "should be eliminated," which is the document steering designers toward the existing slot arrangements rather than new ones.
AOP-68 names no accreditation, audit or certification scheme, and nobody is "AOP-68 certified." The two checks it does describe both examine a design or a test result rather than an organisation: firings, used to confirm that a fuze/projectile combination reproduces the required ballistic trajectory and burst point, and NATO AC/326 approval of a genuinely new fuze-setting technique before it can be type classified.
AOP-68 assumes drawing practice and symbology consistent with the international conventions of "American National Standard Engineering Drawings and Related Documentation Practices," ANSI Y14.5M-1982, which sits outside NATO's own catalogue and is obtained from ANSI/ASME directly. Its figures are dimensioned in SI metric units throughout, except thread designations, which stay in English unit notation. Beyond ordinary ordnance design and drawing capability, it does not assume any prior quality-management system or certification.
NATO publishes AOP-68 through the NATO Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for AOP-68 is the source.
AOP-68 is an operational/technical interface standard, not a management-system standard: the work of meeting it happens in ordnance design and manufacturing engineering, drawing control and firing-test programmes, not in software. What an organisation working to AOP-68 needs to evidence is disciplined document control over the design records showing which contour/cavity combination a fuze or projectile was built to, records of the firings used to confirm ballistic interchangeability, records of any NATO AC/326 approval sought for a new fuze-setting technique, and training records for the people who apply the interface controls. ComplyTrain supports that kind of work in general, as a quality management and evidence system: controlled documents, revision history, training records and audit trails that a customer or national authority can inspect.
ComplyTrain does not design, draw, mate-test or dimensionally inspect a fuze against a projectile cavity, and it does not replace the firing programme AOP-68 requires to confirm ballistic interchangeability; that engineering and test work happens outside any compliance software. The applicable tier for a given programme, and the standards that come with it, are set by the contract and the customer's quality clause. See the standards explorer for what sits alongside AOP-68, and talk to us about the documentation and training side of that work.
Tell us how you need to work with AOP-68 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 the agreement that covers it. Nations commit to AOP-68's interface by ratifying STANAG 2916, and a manufacturer meets it only when a national design requirement or a contract specifies conformance with it, not because the document exists on its own.
The preferred combinations in Annex A are AOP-68's recommended fuze contour and projectile cavity pairings. The permissible combinations in Annex B are a wider set already in national service that remain valid even though not preferred. Deep-intrusion configurations within that permissible set are the ones nations report forecast phase-out dates for, under periodic review.
NATO publishes it free of charge through the NATO Standardization Document Database. ComplyTrain does not sell or host copies of NATO documents.
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.