UIDs are great for the Government, but really complicate the compliance process for contractors. They are long and complicated, easy to mistype, and each one may be used many times per shipment:
•Item Part Mark
•Unit Container Label (SN and in 2D symbol)
•Intermediate Container Label (SN and 2D)
•Exterior Container Label (SN and 2D)
•WAWF Receiving Report (UII and SN)
•WAWF RFID Pack Data
Unique Identifiers (UIIs) are long, complicated, easy to enter incorrectly. MIL-Comply requires that each UII be entered only once, saving time and errors. And if they already exist on one of your business systems, they can be imported to eliminate data-entry altogether.
Support for UIDs is integrated at multiple points in Labeling and Shipper, and other places in MIL-Comply. This manual section describes the features of UID support, which may vary a little depending on context.
UID Entry Point in CLIN Editors
The most frequently used UID capability is adding and editing UIDs that are attached to a shipment for labels or WAWF Receiving Reports (DD250s). The Line Item (CLIN) editors in Shipper and Labeling have some version of the UID Entry Point pictured at right, which shows the number of UIDs currently attached to the shipment, along with a button to edit them. Use the Edit [ UIDs ] button for adding and editing shipment UIDs. Note that when GFP characteristic is set the Edit button will indicate that GFP items are being selected rather UIDs. Serial Numbers may added to shipments when those are used instead of UIDs (never both).
MIL-Comply eliminates the redundant manual entry of UID data is used throughout the shipment process: ▪Receiving Report ▪RFID Pack Data (separately, or as part of the WAWF RR) ▪Unit Container Label ▪Exterior Container Label or Barcoded Serial Number List
MIL-Comply makes it simple to input, import, export and share UID data. |
Serial Numbers
Serial numbers receive special handling in MIL-Comply, managed by its Serial Number Editor. Even though every UID has an assigned serial number, those serial numbers should not be entered into MIL-Comply separately. Shipments may have serial numbers or UIDs, but not both. WAWF and Mil-Std-129 handle serial numbers somewhat differently, adding to the confusion. Serial Numbers vs UIDs in WAWFUIDs are included in Wide Area Workflow transactions in special data segments that include their assigned serial numbers. WAWF Receiving Reports (DD250s) printed by MIL-Comply list the UIIs attached to a shipment in their entirety. Non-UID serial numbers are also printed on DD250s, but are not submitted to WAWF in any rigorous fashion, simply listed in the item's extended description, space permitting. RFID data submitted to WAWF includes UIDs, while ignoring serial numbers. So it seems that serial numbers do not really matter to DoD. Items considered important enough by the DoD to be serially-managed are required by contract to be marked with UIDs. That said, serial numbers should definitely be included in shipment data if they are contractually required in lieu of UIDs. Serial Numbers in Mil-Std-129 LabelsMil-Std-129 considers serial numbers on equal footing with UIDs, requiring them to be be listed on container labels and included in the 2D PDF417 symbol. However, when UIDs are used only their serial numbers are shown due to space limitations on labels. But the caption of the PDF417 makes it (somewhat) clear that the serial numbers are those of UIDs rather than just serial numbers. |
Government-Furnished Property (GFP)
MIL-Comply also supports Government-Furnished Property (GFP) that is being processed for maintenance, overhaul and repair, that is items which were previously sold to the government that are temporarily in the custody of contractors for service. While these GFP items are generally UID-marked, their records are maintained separately from UIDs because not all GFP were necessarily marked with UIDs by the contractor, nor even sold by it. See GFP Support for more details. |