AUIDP-1 NATO guidance on unique identification of items

What it is

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.

UID does not replace NATO Codification

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.

Who it addresses, and how it binds

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."

Deciding what to mark

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, and when it is cheapest

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."

Registration and the data behind it

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.

What an assessor actually checks

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.

What it does not cover

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.

Standards it references

• STANAG 2290Binds
• AAP-48Background
• ALCCP-01Background
• STANAG 4457Background
• AEDP-01Background
• STANAG 4427Background
• AAP-51Background
• ISO 9001Background