MIL-STD-130 UID Marking Service for DoD Parts
Need a MIL-STD-130 UID marking service? We route your parts to suppliers that apply 2D Data Matrix UII marks by label, dot peen, laser or chemical etch, verify each mark to the grade MIL-STD-130 sets, and return the data you need to register the items. Send the drawing, the contract IUID clause and the item list.
Updated
What a MIL-STD-130 UID marking service should hand back
A MIL-STD-130 UID marking service should return three things with the parts: a readable Data Matrix mark in the location and method the drawing calls for, a verification report that shows the mark met the required grade, and a data file that lists every unique item identifier (UII) so it can go on the receiving report. If any of the three is missing, the job is not done.
We are a sourcing service. We do not own marking lasers or peen heads. We match the job to a supplier that marks and verifies to MIL-STD-130, flow the drawing and contract requirements down to it, check the verification reports and UII list against your item list, and ship with a certificate of conformance.
When DFARS 252.211-7003 requires a UID mark
The clause, DFARS 252.211-7003 Item Unique Identification and Valuation (JAN 2023), requires unique item identification on delivered items in five cases. If your contract carries it, start by sorting your line items into these buckets.
| Paragraph | Items covered | Buyer note |
|---|---|---|
| (c)(1)(i) | Delivered items with a Government unit acquisition cost of $5,000 or more, except line items the contract lists as exceptions | Check the exception table in your copy of the clause |
| (c)(1)(ii) | Items under $5,000 that the Schedule or the clause table identifies | Cheap items can still need a mark |
| (c)(1)(iii) | Embedded subassemblies, components and parts; items with warranty requirements; DoD serially managed reparables and nonreparables, as listed in an attachment | Embedded items are where buyers most often miss the requirement |
| (c)(1)(iv) | Special tooling or special test equipment designated for preservation and storage for a Major Defense Acquisition Program, per an attachment | Applies to tooling, not only flight parts |
| (c)(1)(v) | Any other item the contractor creates and marks a UII for, for traceability | A voluntary mark still has to follow the rules |
The clause says the data elements are marked with two dimensional Data Matrix symbology compliant with ISO/IEC 16022, encoded with Application Identifiers, Data Identifiers or Text Element Identifiers, and formatted to ISO/IEC 15434 Format Indicators 05, 06 or 12. It points to MIL-STD-130, Identification Marking of U.S. Military Property, latest version, for the marking criteria.
Paragraph (g) matters for buyers below the prime. When a contractor buys items by subcontract that need IUID under (c)(1), it must put the clause in the subcontract, including subcontracts for commercial products. So if you are a sub and your PO quotes 252.211-7003, the obligation is real for you and for your suppliers. See our defense contractor page for related clauses.
Have a part like this?Send it in under a minute. A person replies within 1 business day.Which MIL-STD-130 revision applies
The edition most buyers will find cited is MIL-STD-130N with Change 1, dated 16 November 2012, which superseded MIL-STD-130N of 17 December 2007. The DFARS clause invokes the latest version rather than a letter, so confirm the current revision on ASSIST before you release the order, and put the revision you expect on the PO.
The standard is blunt about one thing buyers often skip. Its foreword says product designers must put the specific marking content, size, location, application process and marking materials into the product definition data, and that simply writing "mark per MIL-STD-130" on a drawing is not sufficient. It says the same of contracts: the acquiring activity has to state what marking is required, including the IUID provisions. A drawing note that only names the standard leaves the marking supplier guessing at location and method, and that guess is what fails later at receiving.
If your drawing has only the bare note, get engineering to add a marking callout before the parts go out.
UII Construct 1 and Construct 2
The construct is decided by how your enterprise serializes, and the mark has to match it. Construct 1 uses a serial number unique across the enterprise; Construct 2 uses a serial number unique only within an original part number, lot or batch.
| Construct | Data elements in the UII | Fits when |
|---|---|---|
| UII Construct 1 | Enterprise identifier plus a serial number unique within the assigning enterprise | Your company runs one serial sequence across all part numbers |
| UII Construct 2 | Enterprise identifier, original part number (or lot or batch number), plus a serial number unique within that part, lot or batch | Serial numbers restart for each part number, which is common in machine shops |
MIL-STD-130 lists the accepted enterprise identifiers: CAGE Code, DoDAAC, DUNS, NCAGE and GS1 Company Prefix. Most suppliers to DoD use their CAGE Code. The enterprise that serializes the item normally assigns the UII, and that enterprise is responsible for making sure its serial scheme produces globally unique identifiers.
Decide early whose CAGE goes in the mark: the shop that serializes, or you if you assign serials and send them down. Mixing the two on one contract creates duplicate or orphan UIIs.
Data Matrix ECC 200 size and placement rules
The 2D symbol must be Data Matrix ECC 200 to ISO/IEC 16022, and MIL-STD-130 paragraph 5.2.3.2 bounds its size. Unless the contract says otherwise, the module size (one cell of the symbol) runs from 0.0075 inch (0.19 mm) to 0.025 inch (0.635 mm), and a square symbol may not exceed one inch.
- Syntax. Machine readable data is encoded to ISO/IEC 15434 (paragraph 5.2.4).
- Curved surfaces. Per 5.2.7.2.3, the symbol may not exceed 32 percent of the radius, 16 percent of the diameter or 5 percent of the circumference of the curved surface. On small shafts and tubes this rule, not the cell size, sets the limit.
- Location. Paragraph 4.2 asks for a location that stays readable in normal use.
Label, dot peen, laser or chemical etch: what fits flight hardware
The design activity picks the method, not the marking shop. Section 4.1 says the design activity shall specify the method to be used, Table II of the standard lists suggested methods, and section 4.5 says marking must not adversely affect the item's ability to meet its required performance. On flight hardware, read that last rule as a design question, and get the method on the drawing.
| Method | What it does | Typical use per MIL-STD-130 Table II | Flight hardware question to ask |
|---|---|---|---|
| Label or data plate | Symbol printed or marked on a separate plate or label fastened to the item | Any item with a flat area to bond or rivet to; plates conform to MIL-DTL-15024, MIL-DTL-19834 or GG-P-455 as the contract specifies | Will the adhesive or fastener survive the thermal, vacuum, fluid and cleaning exposure the part sees? |
| Dot peen | Stylus indents a pattern of dots into the surface | Metal or nonmetal parts that will not deform under the stamping pressure, where altering surface finish is not detrimental | Is the area outside fatigue critical zones, and thick enough not to distort? |
| Laser engraving or etching | Removes or alters material with a laser | Fine surface finishes without protective coating, and high hardness parts (HRC 50 or higher); laser etching is generally limited to 0.001 inch maximum depth | Has engineering accepted the depth and any heat affected surface on this alloy? |
| Electrochemical etch | Electrolytic process through a stencil | Sheet metal fabrications that would deform if stamped | Is residue fully neutralized and cleaned before finish? |
Paragraph 4.3 says marks must last the normal life of the item, survive its environmental tests and cleaning, and account for final paints, coatings and sealants. A symbol marked before anodize or paint has to be verified after finish.
For intrusive methods on flight parts, ask engineering for written acceptance of the method, depth and location, even if the drawing already allows it. Our special processes page covers how marking fits the finish sequence.
Verification grading to ISO/IEC 15415
A mark that scans on a phone is not a passing mark. MIL-STD-130 paragraph 5.2.7.2.1 gives the supplier three acceptance routes, and the verification report should state which one was used.
- ISO/IEC 15415: minimum quality grade 3.0/05/650, meaning grade 3.0, a 0.005 inch (0.127 mm) aperture and a 650 nm light source. Modulation, symbol contrast or both may read as low as 2.0 if the overall grade would be 3.0 with those parameters at 3.0, and the report must show that. The grade is based on a single scan, and the report must document the synthetic aperture used.
- AIM DPM-1-2006 or ISO/IEC TR 29158: minimum grade DPM 2.0 for an X dimension of 7.5 to 25 mils, at 650 nm, under one of the listed lighting conditions. This route suits direct part marks like dot peen, where printed label grading does not fit.
- SAE AS9132: acceptance against the AS9132 quality requirements and the design specification it calls out.
Paragraph 5.2.7 allows conformance to be based on a sampling plan such as ISO/IEC 2859-1, and says conformance includes validation of content as well as verification of quality. Validation catches a perfect symbol that encodes the wrong serial.
A failed direct mark that cannot be reworked without harming the part is crossed out per paragraph 5.2.8, using a method set by the design authority, and the item is re-marked elsewhere. Leave room for that on small parts.
Registering items in the IUID Registry through WAWF and PIEE
Marking is half the job; the UII also has to reach the DoD IUID Registry. Under paragraph (f) of the clause, end item data goes in through the receiving report in Wide Area WorkFlow (WAWF). Embedded items can be reported through the WAWF embedded items capability, by direct data submission to the IUID Registry, or as a WAWF deliverable attachment.
Both WAWF and the IUID Registry are modules of the Procurement Integrated Enterprise Environment (PIEE), DoD's procurement portal, as listed in DLA's PIEE module overview. PIEE training includes a web based module for the Registry.
Who submits depends on who delivers to the Government. Usually the prime or the contractor named on the contract files the receiving report, so a supplier below it delivers marked parts and a clean UII data file, and the prime enters it. Agree the data file format with the submitter, including parent UIIs for embedded items.
What goes wrong with UID marking, and how we check for it
- Duplicate UIIs when two shops serialize under the same CAGE, or when Construct 1 serials restart. We confirm the serialization owner and scheme before marking.
- Marks lost under finish. Paint, hard anodize or sealant drops contrast below grade. We ask for verification after final finish when the sequence puts marking first.
- Marks on the wrong surface, such as a sealing face, because the drawing named only the standard. We ask for a marking callout instead of letting the shop choose.
- Symbol too large for a small diameter under the 32 percent of radius rule. The supplier checks fit against the data string before marking.
- Reports missing the aperture, wavelength or acceptance route. We check each against paragraph 5.2.7.2.1.
- Data that does not match the parts. We compare the UII file line by line with the serials on the verification report before shipment.
Too small to mark at all? Section 4.1.b sends the mark to a supplemental container that is managed with the item, or to the unit pack alongside the MIL-STD-129 shipping marks. Our counterfeit parts avoidance page explains why traceability on small critical items still matters.
What drives lead time and cost on a marking job
Setup and data work usually outweigh the marking itself. No prices or promised lead times here, but these factors move both:
- Whether engineering still has to add a marking callout
- Number of unique UIIs, and whether serial data comes from you or the supplier
- Method: labels can be printed in batches, direct marks are part by part
- Finish sequence, when parts must be marked between processes or re-verified after finish
- Verification sampling level required by the contract
- Export control on the drawing, which limits who can handle it
What to send with your request
- Drawing at its released revision, with any marking detail or callout
- The contract or PO clauses: DFARS 252.211-7003 and any prime IUID requirements, including the exception table and attachments for embedded items
- Item list with part numbers, quantities and which items need a UII
- Serialization owner, enterprise identifier and construct (1 or 2), or a request for the supplier to serialize
- Preferred method if engineering has one, and any surfaces that must not be marked
- Finish and process sequence, so marking lands at the right step
- Verification route required (ISO/IEC 15415, AIM DPM or AS9132) and sampling plan
- Data file format your WAWF submitter needs
- Export classification of the drawing
Our aerospace RFQ checklist covers the rest of a complete request, and the certificate of conformance page shows what comes back with the parts.
How Aerospace Sourcing handles IUID marking
We do not hold any marking qualification ourselves and we do not submit data to the IUID Registry on your behalf. We route the work to suppliers whose marking and verification capability fits your method and grade, and manage it through delivery.
- One quote, one lead time, one point of contact and one purchase order, even when marking is combined with machining or finishing at other shops
- Your drawing, DFARS clause, construct and verification requirements flowed down to the marking supplier
- Verification reports and the UII data file checked against your item list before parts ship
- A certificate of conformance with every order
If the drawing is ITAR or CUI controlled, do not attach it to a web form. Read controlled programs and confidentiality first.
Request UID marking
Send the drawing, the IUID clause and the item list through the special process request form. Tell us the construct and who submits to WAWF, because those two answers decide what the marking supplier has to deliver besides the mark. A person replies within one business day, and rush requests are prioritized.
Send the job. A person replies within 1 business day.
Part, quantity and date are enough to start. Drawings and the mutual NDA follow by reply, and controlled programs never send technical data through this site.
We have it.
Reference . A person replies within 1 business day. Watch for our email from [email protected].
Questions
Does every part on a DoD contract need a UID mark?
No. DFARS 252.211-7003 requires it for delivered items with a Government unit acquisition cost of $5,000 or more unless excepted, items under that figure the contract identifies, listed embedded items, warranted items and serially managed items, certain MDAP special tooling and test equipment, and any item you choose to mark with a UII. Read the clause, its exception table and its attachments for your contract.
What is the difference between UII Construct 1 and Construct 2?
Construct 1 is your enterprise identifier plus a serial number unique across your whole enterprise. Construct 2 adds the original part number, lot or batch number, with a serial number unique only within it. Use the construct that matches how your company actually serializes. Construct 2 fits shops whose serial numbers restart for each part number.
What verification grade does MIL-STD-130 require for a Data Matrix mark?
Under ISO/IEC 15415 the minimum is 3.0/05/650, with modulation and symbol contrast allowed down to 2.0 if the overall grade would otherwise be 3.0. For direct part marks the supplier may instead use AIM DPM-1-2006 or ISO/IEC TR 29158 at DPM grade 2.0, or SAE AS9132. The verification report should say which route was used and show the settings.
Can dot peen or laser marking be used on flight hardware?
Often yes, but the design activity decides. MIL-STD-130 says the design activity specifies the marking method and that marking must not affect the item's performance. Dot peen alters surface finish and laser marking affects the surface, so engineering should accept the method, depth and location on fatigue sensitive or thin parts. Get it on the drawing before parts are marked.
Who registers the UII in the IUID Registry?
Whoever submits the receiving report to the Government, usually the prime or the contractor on the contract. End items are reported through the WAWF receiving report, and embedded items through the WAWF embedded items capability, direct submission or a WAWF attachment. A lower tier supplier delivers marked parts and a UII data file that the submitter enters.
What if the part is too small to mark?
MIL-STD-130 section 4.1.b allows the marking to go on a supplemental container managed with the item, or on the unit pack with the MIL-STD-129 markings. For very small critical items such as electronic components or critical safety items, the standard still asks that physical marking be considered for traceability, even if the mark cannot meet the normal size limits.
Is "mark per MIL-STD-130" enough on a drawing?
No. The standard's foreword says that stating marking per MIL-STD-130 is not sufficient, and that product definition data must give the marking content, size, location, process and materials. Without that, the marking supplier has to guess, and a mark in the wrong place or by the wrong method can fail at receiving or harm the part.
Related
Sources
- Acquisition.gov: DFARS 252.211-7003 Item Unique Identification and Valuation (JAN 2023)
- EverySpec: MIL-STD-130N with Change 1, 16 November 2012
- MIL-STD-130N with Change 1, full text (Camcode copy of the ASSIST document)
- DLA: PIEE module overview (September 2021)
- PIEE training: IUID Registry web based training
- Wikipedia: MIL-STD-130 revision history
Ready to
source it?
A person replies within 1 business day. NDA first.
Request a quote