MIL-STD-130 and IUID marking: a practical advisory guideIUID marks that fail verification hold up deliveries.

MIL-STD-130 and IUID in brief

A contract may require a particular mark, data structure, reporting step or flowdown to subcontractors. So check the contract and the current clause as well as the standard: the contract wording and the applicable clause govern what you must do, not the standard on its own.

TRACIO’s role is to define the decision, test the proposed marking and data flow, and help you select marking methods and verification equipment without steering you to one supplier. We are an independent advisory: we do not sell printers, markers, scanners, verifiers, RFID platforms or ERP software. See TRACIO’s independent RFID and RTLS advisory.

Source note: official status checked 30 September 2026. DLA ASSIST-QuickSearch lists MIL-STD-130 as active and shows Revision N Notice 1, Validation dated 26 August 2019. Acquisition.gov displays DFARS 252.211-7003 as ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023) under DFARS Change 5/7/2026, effective 7 May 2026. This guide is a plain-language summary, not legal advice. Check the official records before release or implementation.

What MIL-STD-130 and IUID are

MIL-STD-130, Identification Marking of U.S. Military Property, gives the marking criteria used to develop specific marking requirements and methods for items produced, stocked, stored and issued by or for the DoD. It covers what information goes on an item and how machine-readable information is structured. The current revision is MIL-STD-130N.

Four things are often treated as one, and they are not the same:

• The standard. MIL-STD-130 describes how items are marked and how the marked data is structured.
• IUID policy. DoD instructions set out which items need unique identification and how the identifiers are built and managed.
• Contract requirements. A clause such as DFARS 252.211-7003, with its filled-in tables and attachments, decides which of your delivered items are in scope and what you must report.
• The DoD IUID Registry. The DoD record that receives UII data and the related reporting.

A UII is the unique data set marked on an item. It is not simply a stock code, a part number or the ID of an RFID tag. A part number tells you what kind of item it is; a UII tells you which single item it is.

Short glossary

• IUID (item unique identification): the DoD system of giving each discrete item a machine-readable identifier that distinguishes it from all other like and unlike items.
• UII (unique item identifier): the globally unique and unambiguous identifier for one item, derived from a data set of one or more data elements.
• Enterprise identifier: a code uniquely assigned to an enterprise by an issuing agency, such as a CAGE code.
• Issuing agency code: the code for the agency that issued the enterprise identifier. Under the clause it is not placed on the item; it is derived from the data qualifier for the enterprise identifier.
• Serial number: the number that, combined with the other data elements, makes the item unique within its scope.
• Original part number: the part number first assigned to the item by the enterprise that identified it.
• Lot or batch number: the number that identifies a group of items made under the same conditions.
• Machine-readable information (MRI): information encoded so that a device, rather than a person, reads it.
• AIT (automatic identification technology): the devices and software, such as Data Matrix readers and RFID readers, that capture identification data automatically.

The two common UII constructs

A UII is built by joining (concatenating) data elements in a defined order. Two constructs are common:

1. Serialisation within the enterprise identifier (the clause’s “serialization within the enterprise identifier”): the enterprise identifier plus a serial number that is unique across the whole enterprise.
2. Serialisation within the original part, lot or batch number: the enterprise identifier, the original part, lot or batch number, and a serial number that is unique within that part, lot or batch assignment.

The DoD also recognises some existing unique identification equivalents. A vehicle identification number is one example. Treat these only as examples: use one only where the contract and the current rules permit it.

We do not recommend a construct without first reviewing the item, your enterprise identifiers, the contract and who owns the numbering data. A construct that suits one item family can create duplicates in another.

The DoD IUID Registry

The DoD IUID Registry is the DoD record and reporting destination for item unique identification. Your physical marks and your internal records have to agree with what is reported there.

• End items and embedded items. Reporting may cover delivered end items and, where the contract requires it, items embedded in them, with the parent-child relationship between the two.
• Records that must agree. The physical mark, the receiving report, and your ERP and MRO records must hold the same UII data for the same item.
• Problems to resolve before submission. Duplicate identifiers, missing parent-child relationships and incomplete reports all need resolving, because they break the link between the item and its record.
• Check the process first. Read the contract, the current Wide Area WorkFlow (WAWF) instructions and the current DoD process before you submit.

The DFARS clause names the DoD’s official unique identification reference: DoD item unique identification (IUID) reference.

What DFARS 252.211-7003 asks for

This is a neutral summary, not legal advice. The current Acquisition.gov page for DFARS 252.211-7003 identifies the clause as ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023). Its prescription, the conditions for using it, is in DFARS 211.274-5.

The clause can require unique identification for specified delivered items, lower-value items listed in the schedule, embedded items, designated special tooling or test equipment, and items the contractor elects to identify for traceability. Exactly which items are in scope depends on the contract and its filled-in tables or attachments. Not every DoD item, and not every supplier, is automatically in scope.

The parts most useful to a delivery team:

• No duplicates. The unique item identifier must not be duplicated.
• 2D Data Matrix. The clause specifies two-dimensional Data Matrix marking for the UII component data elements.
• A permitted UII approach. The contractor selects a permitted UII approach and places the required data elements on the item based on the current MIL-STD-130.
• Reporting and flowdown. Reporting can be required, and so can flowdown of the requirements to subcontractors.
• Machine-readability verification. The clause calls for verification with an AIT device programmed to the requirements of Appendix A of the latest MIL-STD-130.

2D Data Matrix versus RFID

Both can make sense together: a permanent 2D mark for the contractual item identity, plus RFID for a separate operational workflow such as stores issue and return. That depends on the contract, a security review and your data architecture. RFID is neither always required nor always unsuitable.

For background, see how RFID works, RFID tag types and RFID versus barcode. These are operational explainers, not sources for DoD compliance.

Choosing a marking method: a checklist

There is no single right method. Work through these questions for each item family:

• The surface: substrate, coating, curvature, surface preparation and the marking area available.
• Permanence: abrasion, fluids, heat, corrosion, cleaning, and what happens to the mark during repair or rework.
• Symbol quality: contrast, cell size, quiet zone, human-readable text and placement.
• The method: direct part mark, laser mark, dot peen, chemical etch, label, plate or another controlled method.
• Production: production rate, batch control, operator training and maintenance of the marking equipment.
• The part itself: inspection access, and the effect of the mark on the part, its certification or its warranty.
• Supplementary marks: whether a secondary label or RFID tag is supplementary, rather than the contractual UII mark.

Test a sample part with the intended process before a fleet or depot rollout. For tool and item-control context in maintenance, see tool control and aerospace FOD prevention.

Verification and grading

Reading the data and assessing symbol quality are different tasks. A successful scan alone does not prove that the mark will stay readable or that it meets the applicable specification.

• Check the data: content, data qualifiers, syntax, and the link to the intended item.
• Check machine readability with the applicable AIT device and software.
• Assess the symbol against the quality and grading method required by the contract or the applicable standard.
• Record the evidence: verifier settings, grade or result, sample identity, operator, date, location and any corrective action.
• Repeat the checks after coating, cleaning, repair, packaging or a process change, where relevant.

We do not quote a pass grade: the contract and the applicable quality specification supply it. The clause’s reference to Appendix A of MIL-STD-130 is a verification requirement. It is not a promise that one reader works for every application.

Common audit findings to check for

These are checks we often recommend, not measured industry statistics:

• the wrong UII construct, or a serial number reused in another item family;
• a duplicate UII, or a UII that does not match the enterprise’s source record;
• missing, extra or incorrectly ordered data qualifiers;
• a Data Matrix that scans in a clean demonstration but fails after handling, coating or cleaning;
• poor contrast, cell growth, damage, quiet-zone encroachment or a mark in the wrong location;
• human-readable text that disagrees with the encoded data;
• an ERP, WMS or MRO record that uses a part number where a UII is required;
• a missing parent-child relationship for an embedded item;
• an incomplete Registry or receiving report submission;
• an RFID tag treated as the contractual UII mark without checking the clause;
• subcontractors receiving unclear marking, verification or data-reporting instructions.

How TRACIO helps

Our advisory work falls into three workstreams. See consulting services for how an engagement runs.

1. Marking method and verification selection: map the contract requirements and item conditions, compare marking methods, define sample tests, and specify the verification and grading evidence needed before approval.
2. Data and process control: map enterprise identifiers, UII constructs, data qualifiers, ownership, parent-child relationships, change control and the hand-off to reporting teams.
3. ERP and MRO integration: trace the UII from design or procurement through manufacture, receipt, stores, maintenance, repair, overhaul, transfer and retirement, and define interfaces and reconciliation checks for ERP, WMS, MRO, MES, quality and Registry reporting. See ERP and platform build advisory and asset tracking for lifecycle visibility.

TRACIO advises on requirements, tests and selection. We do not replace the prime contractor, the contracting officer, the quality authority or legal review. We keep TRACIO’s work unclassified, and we work within your export-control process. For the sector context, see our defence industry advisory and aerospace industry advisory for MRO.

Frequently asked questions

Official sources

Official status checked 30 September 2026. Each source is linked where it is used above.

• DLA ASSIST-QuickSearch, MIL-STD-130 document details: title, active status and the Revision N Notice 1, Validation record dated 26 August 2019.
• Acquisition.gov, DFARS 252.211-7003 Item Unique Identification and Valuation: clause date, Data Matrix requirement, UII constructs, verification, reporting and subcontract flowdown.
• Acquisition.gov, DFARS Part 211 (211.274-5): prescription of 252.211-7003 and the conditions for using it.
• DoD item unique identification (IUID) reference: the official DoD unique identification reference named by the clause.

Last updated: 4 October 2026