|
<< Click to Display Table of Contents >> Navigation: UID Expeditor > UID Data Collection > Adding Composite UIIs > UID-CSV-v2: End/Embedded UID Import |
MIL-Comply uses this simplified format to import end-items and embedded-items for shipment definition purposes, for submission Wide Area Workflow (WAWF) and ultimately, the UID Registry. The resulting shipment data can also drive labeling compliant with Mil-Std-129.
The underlying requirements for end-items and embedded items differ somewhat, as indicated by the two rightmost columns below. The first line of the CSV file may optionally contain the field names when used in Comply/Shipper or Comply/Labeling. When present the column header line is used to confirmation of field mapping. It must be:
"UII,PN,SN,Noun,NSN,ParentUII,Contract,Order,CLIN,UOM,AcqCost"
When used in UID Expeditor, files of this format must include the column header line above as the first non-blank or non-comment line. This allows Expeditor to differentiate between supported formats.
The file may include:
•Blank lines (including all comma lines produced by exporting Excel spreadsheets)
•Comment lines that start with a semicolon (';')
Field Name |
Size/Format |
Description |
End Item |
Embedded |
|---|---|---|---|---|
UII |
A50 |
Unique Item Identifier of this end-item or embedded-item. |
M |
M |
PN |
A32 |
Part Number. The Part Number under which the item is identified. When it corresponds to the UII, the latter will be assumed to be Construct 2. Otherwise, the UII will be determined to be Construct 1. |
M |
M |
SN |
A30 |
Serial Number. The Serial Number assigned to the item by the Entity. It is a component of Construct 2 UIIs. It is required for Construct 1 UID items, but not included in the UII. |
C |
C |
Noun |
A35 |
Nomenclature - Mil-Std-129-compliant description of the item. |
M |
M |
NSN |
A23 |
National Stock Number. May include dashes, prefix and/or suffix. |
O |
- |
ParentUII |
A50 |
UII of the Parent Item should this item be embedded. |
- |
M |
Contract |
A25 |
Contract Number under which item was acquired. Mandatory if CLIN is present. |
C |
- |
Order |
A18 |
Order Number within Contract, if applicable |
C |
- |
CLIN |
A6 |
Line Item within Contract/Order Number |
O |
- |
UOM |
A2 |
Unit of Measure associated with the Acquisition Cost of the item. |
O |
- |
AcqCost |
R18.2 |
Unit Price as defined by the contract or as defined at delivery by the contractor. |
O |
- |
Key: M – Mandatory C – Conditional An – Alphanumeric , up to n chars O – Optional '-' – Not Applicable R18.2 – Dollar.Cents up to 18 digits |
||||
The v2 CSV import automatically determines the UID construct based on the fit of the item data to its UII:
•The Part Number is required for all constructs.
•A UII will be considered to be Construct 2 if the PN is found immediately following the UII's Entity ID, and additional characters follow, representing the SN.
•Construct 2 UIIs do not require a SN field, provided they meet the rule above. The characters following the part number component will be considered the item's serial number.
•UII's that do not meet the rules for Construct 2 will be considered to be Construct 1.
Version 5 of this import format features a UID Type field that allows for error detection. This allows for a more deliberative approach, eliminating the automatic designation of UIIs that fail the Construct 2 rules to be Construct 1.
NOTE: This specification pertains to UID Expeditor versions 1.5.049+ (MIL-Comply release 1.5.0226+).
See Also
UID-CSV-v5 - Simplified embedded UID import format