Home Catalog of Products Technical Support Downloadable Software Price List Company Information Contact Us Our Partners Useful Resources
WAWF, RFID, UID, ASN
RFID, UID, WAWF
UID, WAWF, RFID
Mil-Std 129, RFID, UID
DD250, WAWF, RFID, UID
DD250, WAWF, RFID, UID
POPS, DVD, PBL
DD250, WAWF, RFID, UID


 

Submittal of UIDs to the DoD Registry 

Prime contractors that are required to mark parts with UIDs are also responsible for submitting those UIDs to the DOD UID Registry. This can be done in a number of different ways, including:

  • WAWF Web Interface
  • UID Registry Web Interface
  • EDI/FTP WAWF DD250 / Receiving Report
  • Direct UID Registry Transaction
  • AIA Partners To Primes (subcontract and embedded UID items)

The Mil-Pac WAWF Support Library (WASup) supports the later two electronic methods of UID submission using a DD250 created for submission as a WAWF Receiving Report. Direct submission to the UID Registry is also supported, and is used in circumstances where it is not possible to submit UIDs with a Receiving Report.

The submission of UIDs requires several pieces of data for each marked item in addition to contract and shipment numbers, the item number (CLIN), product identifier (NSN/PN) and unit cost:

  1. UID Type (Construct 1 or 2)
  2. Entity Identifier (such as CAGE) of company assigning the UID
  3. IAC (Issuing Agency Code) which controls the Entity ID
  4. Part Number (Construct 2 only)
  5. Serial Number
  6. Fully constructed UID

Automatic Generation of Construct 2 UIDs

The Mil-Pac WASup software tries to simplify the specification of UID data by recognizing that most companies will use UID Construct 2, combining their CAGE code, part number and serial number to create each UID. The WASup software will automatically generate these UIDs when it encounters the operator UID: Type2, which can appear anywhere between the nomenclature (second line) the first Serial Number.

Example 1:   Automatic Construct 2 UID
0001

1112-01-434-0001
LN-200 IMU HOUSING
P/N: 31-142
MILSTRIP: N005354281X001XXX
UID: TYPE2
S/N: 2044492, 2044498, 2044499,
2044501, 2044507

In this example five UIDs would be constructed, using the Prime CAGE code "1HLD9" (DD250 Block 9), part number "31-142" and each of the five serial numbers listed:

  • D1HLD931-1422044492
  • D1HLD931-1422044498
  • D1HLD931-1422044499
  • D1HLD931-1422044501
  • D1HLD931-1422044507

Note: You may view the encoding of these examples for both the UID Registry Direct Submittal (XML) transaction and the WAWF Receiving Report (EDI-856) transaction. The source DD250 Receiving Report can be viewed as well. Note also that example CLIN 0002 is intended as a non-UID test item.

Automatic Construct 1 UIDs

The same method can be employed for Construct 1 UIDs, automatically building UIDs from the Prime CAGE and each serial number listed. Keep in mind that the prime contractor is responsible for ensuring that each such serial number is unique.

Example 2:   Automatic Construct 1 UID
0003

CONNECTOR ASSEMBLY
P/N: RSEE11-4S
MILSTRIP: N005354281X002XXX
UID: TYPE1
S/N: 777002, 777005, 777006, 777009

This example would build four UIDs, using CAGE code 1HLD9 (DD250 Block 9) and each of the serial numbers.:

  • D1HLD9777002
  • D1HLD9777005
  • D1HLD9777006
  • D1HLD9777009

Using a Different Part Number and/or Entity

It is still possible to utilitize automatic UID construction in cases where the prime wishes to use the UID Part Number and Serial Numbers assigned by a sub-contractor or other vendor. The placement of UID-ENTITY and/or UID-PN operators before the first Serial Number overrides the prime contractor CAGE (DD250 Block 9) and/or part number (X22-5525 in the example below).

Example 3:    Alternative Part Number and Entity
0004

1224-01-122-0044
CIRUIT HOUSING
P/N: X22-5525
UID-ENTITY: 07700
UID-PN: 311875-1N42
S/N: 5525-0001, 5525-0003, 5525-0004,
5525-0006, 5525-0007, 5525-0009,
5525-0012

This example will override the prime's Part Number for UID construction and submittal only. On the WAWF Receiving Report this item would still be listed as P/N X22-5525, and the prime contractor 1HLD9 (DD250 Block 9). The following UIDs would be constructed:

  • D07700311875-1N425525-0001
  • D07700311875-1N425525-0003 . . .
  • D07700311875-1N425525-0012

In the examples above we have been assuming that the reponsible Entity was identified by a CAGE Code. In some cases the prime may wish to utilitize part numbers and serial numbers assigned using one of the other internationally recognized Issuing Agency Codes (IAC). This is done by following the Entity ID with its IAC, using one of the officially recognized codes

Example 4:    Non-CAGE Entity Identifier
0005

1224-01-788-9917
POWER REGULATOR
P/N: X22-7566
UID-ENTITY: 6445227111 [IAC: UN]
UID-PN: PNG911-032-5525
S/N: 7566-0008, 7566-0012, 7566-0017

This example is similar to the one above it, except that the Entity Identifier is a DUNS number instead of a CAGE Code. The following UIDs would be constructed:

  • UN6445227111PNG911-032-55257566-0012
  • UN6445227111PNG911-032-55257566-0008
  • UN6445227111PNG911-032-55257566-0017

Explicitly Named UID Components

It may be desirable to explicitly name each UID component. This is possible by providing a UID-ENTITY/IAC, UID-PN and UID-SN for (after) every serial number included for an item.

Example 5:    Explicit UID Components
0006

1112-01-434-0005
LN-200 INERTIAL MEASUREMENT UNIT
P/N: 31-142
MILSTRIP: N005354281X001XXX
S/N: 407090
UID-ENTITY: 06481 [IAC: D]
UID-PN: 06481-311875-1N42
UID-SN: 407090
S/N: 407091
UID-ENTITY: 06481 [IAC: D]
UID-PN: 06481-311875-1N42
UID-SN: 407091

The example above demonstrates arbitrary UID assignments, in which each UID component is explicitly stated. This example would produce the following UIDs:

  • D0648106481-311875-1N42407090
  • D0648106481-311875-1N42407091

 

See also: Overview of Mil-Pac UID Support.