MIL-STD-130 and IUID marking requirements

MIL-STD-130 is the military standard for identification marks on U.S. military property. It covers human-readable text and machine-readable information. Item Unique Identification (IUID) adds a globally unique identity for the individual item. (MIL-STD-130N, scope and definitions)

The contract determines the required marking and reporting. A correct IUID delivery needs the right item selection, identifier, physical mark, and delivery data.

Is MIL-STD-130N still the current revision?

The official catalog lists Revision N with Change 1 and a later validation notice. Change 1 is dated November 16, 2012. Notice 1, dated August 26, 2019, validates the standard. (ASSIST MIL-STD-130 record)

The Acquisition Streamlining and Standardization Information System (ASSIST) identifies the document as active. A validation notice is listed separately from the incorporated technical change.

Use the complete Change 1 text when developing a marking specification. The standard says a bare instruction to mark an item per MIL-STD-130 is insufficient. Product definition data must identify details such as content, size, location, process, and marking materials. (MIL-STD-130N, Foreword)

Put those details into the applicable drawing or specification. For the documents that carry those requirements, see technical data packages.

Which items require IUID marking?

The published clause includes delivered items costing $5,000 or more and several categories below that threshold. The figure is the government's unit acquisition cost, not the total order value. (DFARS 252.211-7003(a) and (c))

DFARS means Defense Federal Acquisition Regulation Supplement. The acquisition.gov clause is dated January 2023 and displays a May 7, 2026 change banner.

For a fixed-price line item, use the contract's unit price at delivery. Cost-type and time-and-materials items use the contractor's estimated fully burdened unit cost to the government.

Do not assume a $4,000 item is exempt. Read the schedule and attachments, including embedded-item requirements. The clause also requires applicable subcontract flowdown.

Did the 2026 acquisition changes remove the $5,000 threshold?

The reproduced contractor clause still contains $5,000, but the acquisition-policy language is broader. Class Deviation 2026-O0013 took effect February 1, 2026. It implements the Revolutionary Federal Acquisition Regulation (FAR) Overhaul for Part 11 and DFARS Part 211. (Part 11 deviation)

The deviation's section 211.274-2(a) states that item unique identification, or a recognized equivalent, is required for all delivered items. That includes contractor-acquired property delivered on line items.

The same attachment reproduces DFARS 252.211-7003 with its January 2023 date and its $5,000 and below-threshold categories. These provisions must be read together.

For a solicitation using the deviation, ask the contracting officer to resolve any mismatch in the schedule or attachments. Identify the exact items requiring marks before choosing equipment or ordering labels. Price alone is insufficient to establish an exclusion.

What are UII Construct 1 and Construct 2?

The 2 constructs differ in where the serial number is unique. A Unique Item Identifier (UII) combines data that distinguishes the physical item globally. (MIL-STD-130N, Appendix A)

For Construct 1, the enterprise must not reuse the serial number on another item. Construct 2 permits serial numbers scoped to the original part, lot, or batch. The complete identifier combination must remain unique. (DFARS 252.211-7003(a))

Choose the construct that matches the actual serialization system. Record the original identifier fields separately from later configuration changes.

The Wide Area WorkFlow (WAWF) entry help separates enterprise, issuing agency, construct type, and original part information from individual serial numbers. It also states that the company creates the identifier. (WAWF identifier help)

What does Data Matrix ECC 200 require?

The clause requires a Data Matrix symbol using Error Checking and Correction 200 (ECC 200). The encoded information must also follow the prescribed data syntax and qualifiers. A successful scan alone does not establish that every requirement was met. (DFARS 252.211-7003(c)(3)-(5))

The clause references standards from the International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC):

The clause's component-data approach derives the issuing agency code from the enterprise identifier's data qualifier. Do not simply print the concatenated identifier as arbitrary barcode text.

Verify both symbol readability and the decoded data. Compare the result with the intended construct and the delivery record.

Can you use a label instead of a direct part mark?

Yes. MIL-STD-130 permits identification plates, bands, tags, labels, and direct marking. The selected method must meet the item's permanence and legibility requirements. (MIL-STD-130N, sections 4.1-4.3)

The mark must last for the item's normal life expectancy. It must withstand the specified environment, cleaning, and applicable rebuild processes.

Choose the process through the item's engineering requirements. A laser mark is not automatically required, and an adhesive label is not automatically acceptable.

How do you report items to the IUID Registry?

Report the required identifier and item data through the contract's delivery process. Marking the item does not complete the reporting requirement. (DFARS 252.211-7003(d)-(f))

1. Build the delivery record from the same identifier fields used for the mark.
2. Include the required acquisition cost, unit of measure, and other applicable item data.
3. Report end items through WAWF receiving reports when required.
4. For embedded items, include the parent and embedded identifiers.
5. Use the embedded-item reporting method specified by the clause and contract.
6. Resolve validation errors and compare the submitted record with the physical mark.

The clause allows specified alternatives for embedded-item reporting, including direct IUID Registry submission. Official registry training routes new-acquisition end items through the receiving report. (IUID Registry training) WAWF provides construct checks and error messages for identifier entry. (WAWF identifier help)

Connect the item identity to the relevant maintenance and support records. The surrounding data requirements are explained in logistics product data.

What to do next

• Read the clause, schedule, attachments, and applicable 2026 deviation together.
• List required end items and embedded items before marking production starts.
• Select the construct that matches your serialization system.
• Specify the mark's content, location, material, and application process.
• Verify the symbol and decoded data against the standard.
• Reconcile each physical mark with its delivery record.

Azcuna's TRACE is one offline viewer for S1000D, MIL-STD-3001 XML, and PDF technical manuals. It keeps the source location and the markings of everything it shows and never modifies the source. It was proposed to NAVAIR under Navy SBIR Phase I topic DON26BZ05-NV078, and the proposal was submitted on September 23, 2026.

Questions people ask

What is MIL-STD-130?

MIL-STD-130 is the Department of Defense standard for identification marking of military property. It covers readable text and machine-readable information. The standard supplies marking criteria, while the contract and product definition data must specify the actual item requirements, including content, placement, and application method.

Which items need IUID marking?

DFARS 252.211-7003 includes delivered items costing $5,000 or more, subject to listed exceptions, plus designated lower-cost items and specified attachment categories. The 2026 Part 11 deviation uses broader language for delivered items while retaining that clause text. Read the award's clause, schedule, and attachments together.

What is the difference between UII Construct 1 and Construct 2?

Under MIL-STD-130N, Construct 1 uses serialization unique within an enterprise. Construct 2 uses serialization unique within an original part, lot, or batch within the enterprise. Both derive a globally unique item identifier from the applicable identifying elements, including the issuing agency code.

Does MIL-STD-130 require a direct part mark?

No. MIL-STD-130N permits attached plates, bands, tags, and labels as well as direct marking. The selected method must meet permanence and readability requirements for the item's normal life, environment, cleaning, and applicable rebuild processes. The item's engineering requirements determine which method is suitable.

Is printing an IUID label enough?

No. DFARS 252.211-7003 requires appropriate item selection, unique identifier data, machine-readable marking, verification, and delivery reporting. A label that scans can still contain incorrect fields or syntax. Compare the decoded identifier with the physical item and the receiving-report data before delivery.

Sources

1. 1MIL-STD-130N with Change 1, Identification Marking of U.S. Military Property, November 16, 2012 · Department of Defense
2. 2ASSIST-QuickSearch MIL-STD-130 document record · Defense Logistics Agency
3. 3DFARS 252.211-7003, Item Unique Identification and Valuation · Department of Defense
4. 4Class Deviation 2026-O0013, Revolutionary FAR Overhaul Part 11 and DFARS Part 211 · Defense Pricing, Contracting, and Acquisition Policy
5. 5WAWF Help, Add UID · Department of Defense
6. 6IUID Registry training · Department of Defense

Where this shows up in our work

• TRACE, the offline S1000D and IETM viewer opens S1000D, MIL-STD-3001 and PDF technical manuals on a tablet with every marking intact.
• BABEL, offline multilingual translation and search translates and searches foreign-language documents on-device, every fact tied to its source passage.