Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AUIDP-1
NATO bodies, agencies, nations and industry acting as an item acquirer, supplier, custodian, sustainment provider or operator across a defence programme's life cycle
AUIDP-1 is NATO's guidance for marking and registering defence items with a Unique Item Identifier so their history can be tracked and shared, reaching a supplier only once a specific contract requires it.
AUIDP-1, "NATO Guidance on Unique Identification of Items", explains how to give an individual defence item a Unique Item Identifier (UII): a globally unique, machine-readable data matrix mark that lets that item's configuration, usage and maintenance history be captured once and shared across information systems for the rest of its life. It is guidance, not a specification in its own right - the actual technical rules for building a UII and marking an item with one live in STANAG 2290, which AUIDP-1 says "any implementing organization can incorporate UID marking on items by complying with." What AUIDP-1 adds is the surrounding decision-making: which items are worth marking, when in a programme's life to do it, how to register the resulting data, and what a contract should actually ask a supplier to do.
The document is careful to separate two systems that get confused. The NATO Codification System assigns a NATO Stock Number to a class of interchangeable items - one Item of Supply, one NSN, shared by every manufacturer's equivalent part. UID works at a different level: the UII distinguishes one physical item from every other item carrying that same NSN, tracking its own custodian, configuration, usage and repair history. AUIDP-1 states plainly that "UID will not replace NSN, or any other element of the NCS," and expects the two data keys to be cross- referenced rather than compete.
AUIDP-1 "is applicable to NATO bodies and agencies, nations and industry, in their roles as system or item acquirer, supplier, through life manager, custodian, sustainment provider, or operator" (clause 1.2). It creates no obligation by itself. Our catalogue records it as covered by STANREC 4782, the NATO recommendation by which nations record their intent to use it - an invitation, not a ratified commitment. A supplier meets AUIDP-1 in practice only once a specific tender or contract requires UID marking, ordinarily by invoking STANAG 2290 directly; Annex 4 collects sample contract clauses from the Netherlands, Canada and the United States for exactly that purpose, all built around the same requirement: mark the specified items, and report a defined data set - the UII, the enterprise identifier, part number and serial number - "at the time of delivery."
Nations, or NATO programme managers for commonly funded items, decide which items actually get a UII. AUIDP-1 does not mandate a universal list; it offers a baseline of candidate categories: configuration items, repairable items, currently serially managed items, controlled items, items requiring certification, calibration or confirmation of disposal, items required by statute or policy, items of significant value, and items subject to through-life measurement. Its own framing of a starting point is concrete: "a logical starting point for the adoption of UID is serial number tracked items, small arms, and other controlled inventory items" (clause 2.5).
Marking method - dot-peen, laser-etch, a metal plate, or a label - is the design authority's decision, chosen so that "lifetime sustainability of the mark can be guaranteed" for the item's expected life (clause 3.1.7). Where a supplier already runs a compliant serialisation scheme, AUIDP-1 says to keep using it rather than impose a NATO-specific one: it gives a Vehicle Identification Number as the example of a commercial scheme that already meets STANAG 2290 and "should be the scheme of choice for UID identification" (clause 3.1.1). Timing matters: marking is "simplest during the development stage of the life cycle," when it can be designed into engineering documentation at negligible cost (clause 3.1.3). Marking a fielded fleet is a different, harder exercise - AUIDP-1 sets out two legacy strategies, using existing maintenance events or a dedicated "seek and apply" campaign - and warns plainly that retrofitting "will take years to both implement process improvements using UID, infrastructure improvements and incorporate marks on items" (clause 2.5.4.2). Marks also need upkeep once applied: clause 3.1.5 expects maintenance procedures to check mark integrity and renew it "when the original mark is missing, but known, or when the quality of the mark is compromised."
Every marked item needs a record in the appropriate registry - the owning nation's, or NATO's for commonly funded items - carrying, at minimum, the data elements Annex 6 lists: the UII, an item-type and population-type flag, enterprise identifier, part and serial numbers, a description, and a "Compliant Mark Flag" that states whether the item is actually marked to UID policy. A registry itself has to "ensure a single global instance of a UII" and be able to answer queries about an item's existence and pedigree data (clause 6.2.1), and since custody of an item moves between NATO, nations and industry over its life, registries have to agree which one is currently authoritative for a given UII (clause 6.2.2). One rule that is easy to miss: "once the UII is derived, it must not be deconstructed to determine the original elements" (clause 6.4) - systems are expected to treat it as an opaque key, never parsed back apart.
There is no accreditation body and no certification scheme for AUIDP-1 or for UID marking in general. What checking exists happens at the contract, not through an external audit: the sample DFARS-style clause in Annex 4 requires the contractor's delivery-time data "in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract" - the acquiring organisation's own goods-receipt inspection, a customer check against the contract rather than third-party certification. The registry's Compliant Mark Flag carries the same idea forward operationally, as a record rather than a credential.
AUIDP-1 sets no retention period for registry or pedigree data, and clause 2.5.5's cost and benefit categories are things to weigh, not a formula that decides whether marking an item pays for itself. It does not decide, for any given programme, which items must be marked - that stays with the nation or programme manager - and it does not itself define the UII's construction: for that, it points to STANAG 2290 throughout rather than duplicating it.
AUIDP-1 is published by the NATO Standardization Office and listed free of charge in the NATO Standardization Document Database. NATO's documents are not sold by ComplyTrain and we host no copies of them.
AUIDP-1 describes operational and technical work - marking physical items, registering them, and reporting defined data at delivery - not a management system a company builds and gets certified against. ComplyTrain does not do that physical work, and claiming otherwise would be exactly the kind of overclaim a reader who has actually implemented UID would catch immediately.
What ComplyTrain supports is the evidence trail around it: a controlled place to hold and version a UID implementation plan and marking procedure, training records for the staff who apply marks or operate a registry, and a logged record of the corrective action taken when a degraded mark is found and renewed rather than left unrecorded. A supplier working to a contract clause that requires UID reporting can use ComplyTrain to hold the delivery-time reporting procedure itself as a controlled, repeatable process rather than a one-off spreadsheet someone has to reconstruct each time.
What ComplyTrain does not do: it does not choose or apply a physical marking method, does not host or operate a UID registry, and does not generate or validate a UII. That work stays with the design authority, the marking organisation and the registry operator.
In defence, whether UID marking applies to a given programme, and to which items, is set by the contract and the customer's quality clause, not by AUIDP-1 alone. See the standards explorer for what sits alongside AUIDP-1 in NATO's life cycle and logistics document library, and talk to us about the evidence trail your contract actually requires.
Tell us how you need to work with AUIDP-1 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.
AUIDP-1, "NATO Guidance on Unique Identification of Items", is NATO's guidance for marking defence items with a Unique Item Identifier (UII) so their configuration, usage and maintenance history can be tracked and shared across information systems. It explains which items to mark, when to do it, and how to register the resulting data; the actual marking specification it points to is STANAG 2290.
Not on its own. Nations record their recommendation to use it through STANREC 4782, which is an invitation rather than a ratified commitment. A supplier is bound only once a specific tender or contract requires UID marking, typically by invoking STANAG 2290 directly.
No. AUIDP-1 is explicit that "UID will not replace NSN, or any other element of the NCS." The NATO Stock Number still identifies a class of interchangeable items; the UII distinguishes one physical item from every other item sharing that stock number.
No. AUIDP-1 describes no accreditation or certification scheme. Compliance is checked contractually: a contractor reports UID data at the time of delivery, verified by the acquiring organisation as part of its own receiving inspection, which is a customer check against the contract rather than third-party certification.
STANAG 2290 is the technical specification for constructing a UII and marking an item with it. AUIDP-1 is the guidance layered on top: which items to mark, when to mark them, how to register the data, and sample contract language, all built around applying STANAG 2290 rather than replacing it.
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.