Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AOP-4157
National Safety Approving Authorities and the design authorities developing fuzes, fuzing systems and ignition systems for NATO munitions
AOP-4157 is NATO's test programme for the safety and suitability for service of Safety, Arming and Functioning Systems, run and approved by each nation's own safety authority.
AOP-4157, Edition A, is the NATO Allied Ordnance Publication that sets out the test requirements for assessing the safety and suitability for service of Safety, Arming and Functioning Systems, called SAF Systems throughout the document, a category that covers fuzes, fuzing systems and ignition systems. Its own aim is "to standardize the test requirements for the safety and suitability for service assessment of Safety, Arming and Functioning Systems (SAF Systems), to which the design requirements of STANAGs 4187, 4368, or 4497 are applicable" (clause 1.1). AOP-4157 picks up once that design work is done: it standardizes how a SAF system already built to those requirements gets tested, not how it is designed. The agreement of NATO nations to use it is recorded in STANAG 4157, and it governs "the development and acquisition of SAF systems commenced after promulgation of this Standard" (clause 1.2.b) - this is Edition A, Version 1, promulgated February 2017, created to bring the old STANAG 4157 test requirements into a standalone publication in line with AAP-03(J), NATO's own directive for producing standardization documents.
Every SAF system a nation develops or procures gets a formal assessment: "Formal S3 assessments by NSAA of all SAF systems developed or procured by nations shall be performed, documented and maintained" (clause 2.2.1.a). The NSAA, the National Safety Approving Authority, is the constant thread through the whole standard: it approves the test plan before testing starts, including which tests are selected, the quantities, parameters, facilities and acceptance criteria (clause 2.2.1.c); it approves any tailoring of a standardised test procedure; and it approves the reappraisal a SAF system needs whenever it moves to a new application (clause 2.2.1.e). The assessment itself has to bundle four things: a design safety and hazard assessment done under STANAG 4187, 4368 or 4497; the results of the mandatory tests, or an equivalent analysis; a justification for any test that was not performed; and any additional national test results a developer chose to add (clause 2.2.1.b).
AOP-4157 draws a deliberate line between addressing a test and performing it. Annex B is mandatory to address: "The tests shall be performed or evidence shall be provided that compliance is met by analysis, analogy, or other means," and where one "is not applicable or was not carried out, justification shall be provided to the satisfaction of the NSAA" and becomes part of the assessment report (clause 2.1.5). Annex C adds further national test procedures offered for information, not as a requirement. Pyrotechnic Initiated Explosive projectiles are the exception to that flexibility: the additional tests in Annex D "shall be performed", with pass/fail criteria the NSAA establishes or approves rather than left to the standard tests' own criteria (clause 2.1.5).
Tailoring a standardised test procedure is "not encouraged" (clause 2.2.2.a), and where a programme tailors one anyway, three conditions apply: NSAA approval before testing, written into the test plan; a tailored test that is at least as demanding as the SAF system's expected life cycle conditions, never less; and a documented rationale kept as part of the assessment report. The same logic governs reuse: whenever a SAF system is proposed for a new application it "shall be reappraised, retested as appropriate, and approved by the NSAA" (clause 2.2.1.e), so a qualification decision travels with a specific application rather than covering every future use automatically. Where a test procedure sets no pass/fail criterion of its own, the standard's own default applies: no unsafe condition may be observed during or after the test, one such observation being a failure on its own, and any small, safety-neutral drop in performance needs the proper national authorities' or the NSAA's approval to be accepted (clause 2.2.2.d).
AOP-4157 keeps the technical content out of its own core text on purpose. Definitions of the munition-specific terms it uses come from the NATO terminology database and AOP-38, and the test procedures themselves, including the environmental test levels a SAF system is expected to withstand, are described in AOP-20 and the other documents this standard names (clause 2.1.6). The test procedures and their pass/fail thresholds belong to those referenced documents and to the test house and safety engineers running the programme, not to this standard.
AOP-4157 creates nothing a company can be certified in. It names no certification body and no certification scheme, and neither "certification" nor "certified" appears anywhere in the document. What happens instead is government assessment of the product: a National Safety Approving Authority runs, documents and keeps the formal assessment for every SAF system a nation develops or procures, and approves the test plan, any tailoring, and any reappraisal along the way. This is government surveillance of a specific SAF system's qualification, similar in shape to how the AQAPs work for a quality management system, and the approval it produces belongs to the SAF system, not to the company that built it.
agreement to use AOP-4157; the cover that gives it force.
documents, which AOP-4157 was created to bring the old STANAG 4157 requirements into line with.
safety and suitability for service framework this standard's tests support and contribute to.
safety requirements a SAF system, or a Pyrotechnic Initiated Explosive projectile, has to meet before this standard's testing regime applies.
this standard's Annex B points to.
test procedure this standard points certain SAF systems toward.
certain SAF systems toward.
environmental test methods Annex D points Pyrotechnic Initiated Explosive projectiles toward.
NATO publishes AOP-4157 through the Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for AOP-4157 is the source.
The work AOP-4157 describes - building and getting NSAA approval for a test plan, working through or justifying every item on the Annex B list, keeping the assessment report current through any tailoring or reappraisal - happens in engineering and safety-assessment work, not in software. What a developer needs to hold is a live record of what was approved, what was tested or justified instead, and what the NSAA signed off on.
ComplyTrain gives a programme team a controlled place to keep that evidence trail: the approved test plan and any revisions to it, the justification on file for every Annex B or D item not performed, the reappraisal record each time a SAF system moves to a new application, and the training records for the people managing that paperwork. That is the same document-control and audit-trail discipline ComplyTrain supports for any technical standard's evidence, not a mapping to AOP-4157's specific test categories.
What ComplyTrain does not do: it does not run a safety, arming or functioning test, design or tailor a test procedure, or decide whether a SAF system is safe and suitable for service. Those judgements sit with the test house, the SAF system's design authority, and the National Safety Approving Authority. Which tests apply to a given programme, and whether any tailoring is acceptable, is set by the contract and the customer's quality clause, not by us. See what else sits alongside AOP-4157 in the standards explorer, and talk to us about the documentation trail behind a SAF system test programme.
Tell us how you need to work with AOP-4157 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-4157 does not bind on its own account: the agreement of NATO nations to use it is recorded in STANAG 4157, and the standard itself names no contract mechanism. It governs "the development and acquisition of SAF systems commenced after promulgation of this Standard", so whether it applies to a given programme, and on what terms, is set by that programme's contract and the customer's quality clause.
No. The document names no accredited certification body and creates no certification scheme; the word "certification" does not appear in it. A National Safety Approving Authority formally assesses and approves a specific SAF system, which is government assessment of a product, not a certification of the company that developed it.
Every test in Annex B is mandatory to address, not necessarily mandatory to perform. Where a test "is not applicable or was not carried out, justification shall be provided to the satisfaction of the NSAA", and that justification becomes part of the formal assessment report the NSAA maintains. Pyrotechnic Initiated Explosive projectiles are the exception: the additional Annex D tests must be performed.
Tailoring is "not encouraged". Where it happens, the NSAA has to approve it before testing and see it documented in the test plan, the tailored test cannot be made less demanding than the SAF system's expected life cycle conditions, and the tailoring and its rationale both have to be kept as part of the assessment report.
STANAG 4157 is the Standardization Agreement: the record of NATO nations agreeing to use AOP-4157. AOP-4157 is the technical publication itself, moved into its own standalone document, in line with NATO's AAP-03(J) directive, from requirements that used to sit inside STANAG 4157.
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.