Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 3104
NATO nations and the aircraft and missile manufacturers whose contracts invoke ISO 12 pipeline identification
STANAG 3104 is NATO's agreement committing member nations to implement ISO 12, the civil standard for identifying aircraft and missile pipelines and electrical conduits.
STANAG 3104 is the NATO standardization agreement that commits participating nations to implement ISO 12, "Aerospace - pipelines - identification," as the common method for identifying pipelines and electrical conduits in aircraft, missiles, launching equipment and installed equipment. A STANAG is not itself a technical specification: it is the agreement by which NATO nations commit to use one, and here the identification scheme lives entirely in the civil standard it covers rather than in an Allied Publication. The document states the requirement plainly: "participating nations agree to implement the following standard for identification of aircraft and missile pipelines and electrical conduits," and names no other related document. Read plainly, that means STANAG 3104 exists so that every participating nation marks pipelines and conduits in aircraft and missiles the same way, using ISO 12, rather than each nation running its own marking scheme.
This is Edition 7, promulgated 28 September 2015. It supersedes STANAG 3104, Edition 6.
The mechanism that matters here: a STANAG binds a nation, not a manufacturer. Nations "are invited to examine their ratification of the STANAG and, if they have not already done so, advise the NSO of their intention regarding its implementation," and the national response is recorded in the NATO Standardization Document Database (NSDD). Once ratified, "STANAG 3104 is considered implemented when the provisions specified therein have been included in the national documentation concerned with reference to STANAG 3104." A manufacturer or installer meets ISO 12's identification scheme only where a contract or a tender brings STANAG 3104 or ISO 12 in by name, not because the STANAG exists on its own.
Nations report their effective implementation "using the form in Annex H to AAP-03(J)"; partner nations report their adoption of the STANAG the same way, "using the form in Annex G to AAP-03(J)." The STANAG "is to be reviewed at least once every three years," with the result recorded within the NSDD, and nations or NATO bodies may propose changes at any time through a standardization proposal to the tasking authority.
No certification exists here, and the document names none. What it describes is a national ratification, implementation and review cycle run through NATO's own machinery, not an audit against this STANAG as such. How a manufacturer actually marks a pipeline or conduit is judged against ISO 12's own requirements, once a contract or a nation's own documentation calls for them.
STANAG 3104 and ISO 12 describe a physical identification scheme, not a management system: the work of marking a pipeline or conduit correctly, on the aircraft, missile or piece of equipment in front of you, sits in design and production practice, not in software. What that leaves to evidence is the paperwork around it: procedures that correctly reference ISO 12 and this STANAG, records showing which drawings or work instructions carry the identification scheme, training records for the people who apply it, and the trail an internal or customer audit asks for afterwards.
ComplyTrain holds that evidence as a modern, auditable system: version-controlled procedures, training records tied to named individuals and dates, and corrective actions when a gap turns up, all searchable when a customer's quality clause asks for it. It does not mark pipelines or conduits, does not decide how a nation implements the agreement, and does not replace the ratification and reporting nations carry out themselves through the NSDD and the AAP-03(J) forms.
The applicable tier here, and whatever else it comes with, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 3104, the standards explorer covers the related NATO publications, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 3104 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 in general. It binds a nation once that nation ratifies it, and it reaches a manufacturer through a contract or a tender that names ISO 12 or this STANAG, not by existing on its own. Whether it applies to a given programme is set by the tasking or contract in front of you.
STANAG 3104 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. ISO 12 is the civil standard itself, "Aerospace - pipelines - identification," which sets out the actual identification methods. The STANAG is the cover; ISO 12 is the content.
Edition 7, promulgated 28 September 2015. It supersedes STANAG 3104, Edition 6.
No. There is no accredited certification for STANAG 3104 or ISO 12 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around procedures and training for pipeline and conduit identification, at an informational level.
At least once every three years, with the result recorded in the NATO Standardization Document Database. Nations and NATO bodies can also propose changes at any time through a standardization proposal to the tasking authority.
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.