MIL-STD-130N
w/Change 1
TABLE IV. UII construct business rules and supplemental data.
UII Construct #1 If items are serialized within the enterprise |
UII Construct #2 If items are serialized within PIN, Lot or Batch Number |
||
UII is derived by linking together data elements in order (top to bottom) for Constructs #1 and #2 |
Issuing Agency Code1 Enterprise ID Serial Number |
Issuing Agency Code1 Enterprise ID |
|
|
Original PIN Serial Number |
Lot or Batch # Serial Number |
||
Data identified on assets not part of the UII (separate identifier) |
Current PIN2 |
Current PIN2 |
|
Other Traceability Number3 |
Other Traceability Number3 |
||
NOTES:
1. The issuing agency code (IAC) represents the registration authority that issued the enterprise identifier (e.g., Dun and Bradstreet, GS1). The IAC can be derived from
the data qualifier for the enterprise identifier and is not separately marked on the item. The IAC for the GS1 Company Prefix need not be derived because it is contained in each GS1 Company Prefix and should not be repeated when linking together the UII data set elements (see Appendix A).
2. In instances where the PIN changes with new configurations (also known as part number roll), the current PIN shall be included on the item for traceability purposes and should be encoded as a separate data element in the MRI.
3. The Data Identifier 30T has been designated for use as a traceability number that is not part of the UII data set. For example, applications may specify 30T for encoding a lot or batch number when the lot or batch number is not required or desired in the UII data set.
38
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business