Attachment, ADC 1112 

Page 1 

ADC 1112 

Administrative Approved Defense Logistics Management Standards 

(DLMS) Change (ADC) 1112, Revise Federal Implementation Convention 

(IC) 856 Ship Notice/Manifest to Identify Item Unique Identification (IUID) 

and Embedded IUID Marks Data to the Receiving Report for Wide Area 

Workflow (WAWF) 

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Agency (DLA) 

b. Originator(s): DLA, DCMA, DSCA, Navy, and Army 

2. FUNCTIONAL AREAS: 

a. Primary: Contract Administration and WAWF Receiving Report (RR)

b. Secondary: IUID and embedded IUID Mark data 

3. REFERENCE: 

a. Defense Logistics Agency (DLA) WAWF Engineering Change Proposal (ECP) 0761 

IUID Registry Incorporation into WAWF Portal

b. DLM 4000.25, Volume 7, Contract Administration, Chapter 2, Shipment Notification

4. APPROVED CHANGE(S): 

a. Brief Overview of Change: Add IUID and embedded IUID “Mark” information and 

all associated fields to the WAWF Receiving Report (RR). The WAWF RR is mapped to the 

commercial standard (American Standards Committee (ASC) X12) 856 Ship Notice/Manifest to 

provide functionality as an electronic data source for shipment information. 

b. Background: 

(1) The Wide Area Workflow (WAWF) is a DoD mandated system that allows 

the vendor to electronically submit invoices and receiving reports, and the Government to inspect, 

receive, accept information and pay electronically. 

(2) ECP 0761 (See Reference a) combines the business rules for both the IUID 

Registry and WAWF “up front” to one location. The functionality of the IUID Registry is 

migrating from its current location into the WAWF architecture. The scope of this migration 

includes procedures for data migration, user registration processes, data entry and updates into the 

IUID Registry using the IUID Registry XML Schema 5.1, while supporting existing XML and flat 

file formats, and direct web entry. The benefits of the new capabilities are increased efficiencies, 

reduced long term costs, and better access to acquisition data. 
Attachment, ADC 1112 

Page 2 

(3) All changes identified for the Federal IC 856 will also be applied to the 

Federal IC 857, Shipment and Billing Notice (also known as the COMBO). 

c. Describe Requested Change in Detail: 

(1) WAWF will add the "Mark" information and all associated fields based upon 

the current IUID Registry data entries, validations, and edits for new items. The new capability 

will allow for the capture of “Mark” information for the new UII (Parent UII and Embedded UII) 

items. This new capability applies to the Ship Notice / Manifest Receiving report (856). 

(2) For each “Mark” to be reported to the IUID Registry, vendors will submit a 

record comprised of at least a bagged or tagged code, contents, marker code and identifier, marker 

medium, value (except for UII marks), and the effective date of the event. The “Mark” 

information will be reported in a separate loop (HL03 Code X). It is mandatory that at least one of 

the “Marks” reported in the Mark loop be the UII.

(3) Upon receipt of “Mark” information, WAWF will perform a direct update of 

the DOD IUID Registry records, vice the current use of transaction extracts. WAWF will read the 

UII received in the Mark loop (HL03 Code X) of the transaction and attempt to find the same UII 

in either the parent loop (HL03 Code D) or Embedded UII Loop (HL03 Code F). If the UII is not 

found in either the parent or embedded UII loop, WAWF will reject the transaction with an error 

because it was unable to assign the Mark to a parent UII or embedded UII. 

(4) The “Mark” information will not be extracted to downstream systems, so there 

is no impact to the DLMS 856 ASN.

d. Revisions to DLM 4000.25 Manuals: There are no changes to DLMS procedures and 

transactions, since this information will NOT be extracted from WAWF to downstream DOD 

Component systems. 

e. Proposed Transaction Flow: Vendors will send “Mark” information in the 856 to 

WAWF through the Global Exchange (GEX). GEX will translate the 856 into a WAWF User 

Defined File (UDF). Once the translated UDF is received in WAWF, WAWF will update the 

WAWF IUID module to ensure the IUID Registry is updated.

f. Alternatives: If the 856 Federal IC is not updated, it would require the vendors to add 

the “Mark” information manually via the web interface. 

5. REASON FOR CHANGE: The WAWF Joint Requirements Board approved ECP 0761 for 

development and deployment as part of WAWF Version 5.6. Deployment is scheduled for August 

2014. Changes are necessary to combine the UID Registry and WAWF into one platform and 

helps gain that efficiency. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Increased efficiencies, reduced long term costs, and better access to 

acquisition data. 
Attachment, ADC 1112 

Page 3 

b. Disadvantages: Requires systems development to process enhanced IUID data 

content. 

7. ADDITIONAL FUNCTIONAL REQUIREMENTS: 

a. Modify the Federal IC 856 ASN per Enclosure 1.

b. Comparable changes must be made to the Federal IC 857 Shipment and Billing Notice 

transaction. This transaction is used by vendors reporting to WAWF as a combination of shipping 

and billing information in a single transaction; it is not used with DOD trading partners (WAWF 

separates content into 856 Ship Notice/Manifest and 810 Invoice for DOD processing).

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This update will be 

deployed in WAWF Release 5.6, targeted for August 1, 2014. 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Increased efficiencies and reduced long term costs. 

This update enables greater use of automated processes that require less manual intervention and 

increase data accuracy.

10. IMPACT: 

a. DLMS Data Elements: There are no new DLMS data elements or changes to 

existing data elements, since changes are only being made to the Federal IC. The changes will not 

be extracted to the DLMS 856.

b. Wide Area Workflow (WAWF): Implement Federal IC changes to WAWF 856 and 

857. 

c. Component Automated Information Systems (AIS): No impact to Component 

Systems. WAWF will not extract “Mark” information to downstream systems. 

d. DLA Transaction Services: Vendor transactions will continue to be routed through 

GEX and WAWF3-RA channels for translation and transfer to WAWF.

e. Non-DLA Logistics Management Standards Publications: The WAWF Program 

Management Office will update the WAWF Guides for 856 and 857 to reflect the changes 

identified by this DLMS Change.

 
Enclosure 1, ADC 1112 

Page 1 

Enclosure 1 

Item # Location 856 Ship Notice/Manifest 

Federal IC Revision 

Reason 

1. 2/HL/010 Add segment level Note 6: 

6. For inclusion of Mark information associated with 

IUID data content, the Mark Loop (HL03 code X) will be 

a child loop to either the UID loop (HL03 code D) or 

Embedded UID loop (HL03 code F) depending on its 

association. 

Clarify business rule for 

Mark loop relationship 

to Parent and Embedded 

UID loops. 

2. 2/HL03/010 Add the following code and note to Data Element HL03: 

X Serial Number 

Use to provide Mark information associated with Parent 

UII (identified by a Parent UID loop) or an embedded UII 

(identified by an Embedded UID loop) for new or updated 

items in the IUID Registry. 

For each mark reported 

to the Registry, a record 

comprised of at least 

bagged or tagged code, 

contents, marker code 

and identifier, medium, 

value (except for UII 

marks), and the effective 

date of the event shall be 

recorded. 

3. 2/REF/150 Add segment level note 10: 

10. Use in 2/HL/010 Mark loops to provide Mark 

information related to parent or embedded UIIs. Repeat 

the REF segment as needed. For values exceeding the 

REF02 maximum field length limit of 30 characters, use 

the REF03 for the overflow. For values exceeding the 

REF02 and REF03 maximum field length limit 

(combined 110 characters), use the REF04 C04002, 

C04004, and C04006 as needed with appropriate qualifier 

cited in the C04001, C04003, and C04005. 

Clarify business rules for 

values exceeding REF02 

and REF03 maximum 

field lengths authorized 

by X12 through use of 

the composite REF04. 
Enclosure 1, ADC 1112 

Page 2 

4. 2/REF01/150 

(Used in 

HL03=”X”, 

Mark Loop) 

Add the following codes and associated notes: 

7M Frame 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Hull Number. 

CT Contract Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Contract Number. 

DX Department/Agency Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type USN Number. 

GU Internal Purchase Order Item Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Internal Asset Number. The Internal Asset 

Number may be carried in a combination of REF02 (30 

characters), REF03 (80 characters), C04002 (30 

characters), C04004 (30 characters), and C04006 (30 

characters) for a maximum of 200 characters. When 

extending the Internal Asset Number into the composite 

data elements, the C04001, C04003, and C04005 must cite 

code GU. 

JL Packet 

Use in Mark loop (HL03 code X) as the Bagged/Tagged 

Indicator. Enter Y (Yes) or N (No) in the REF02. 

K6 Purchase Description 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Item Nomenclature. The description may be 

carried in a combination of REF02 (30 characters), 

REF03 (80 characters), C04002 (30 characters), C04004 

(30 characters), and C04006 (30 characters) for a 

maximum of 200 characters. When extending the 

description into the composite data elements, the C04001, 

C04003, and C04005 must cite code K6. 

LT Lot Number 

1. Use in Product Characteristics loop (HL03 code PH) to 

identify the batch/lot number. 

2. Use in Mark loop (HL03 code X) to identify the Mark 

content type Lot Number. 

NS National Stock Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type National Stock Number. 

Use to identify bagged or 

tagged code, contents, 

marker code and 

identifier, medium, value 

(except for UII marks), 

and added data. 
Enclosure 1, ADC 1112 

Page 3 

5. 2/REF01/150 

(Used in 

HL03=”X”, 

Mark Loop) 

Add the following codes and associated notes: (continued) 

PM Part Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Part Number. Cite the Part Number in the 

REF03. 

Q5 Property Control Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Property Control Number. 

Q8 Registration Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Registration Number. 

SE Serial Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Serial Number. 

SJ Set Number 

Use in Mark loop (HL03 code X). 

U3 Unique Supplier Identification Number (USIN) 

1. Use in UID loop to identify the UII value. Cite the UII in 

REF03. Cite the serial number, when applicable, in 

REF02. When a batch, lot, or other type of production run 

number is included in the UII for uniqueness, this number 

may be cited in REF04 or in 2/SLN/040. 

2. Use in RFID Content/Quantity loop to identify the UII 

value. Cite the UII in REF03. 

3. Use in the Embedded loop to identify the UII of the item 

for which embedded information is being provided. Cite 

the UII in REF03. 

4. Use as applicable in the Current Part Number loop to 

identify the UII of the item for which a new part number is 

being provided. Cite the UII in REF03. 

5. Use in the Mark loop (HL03 code X) to identify the 

Mark content type UII. Cite the UII in REF03. 

Y9 Current Certificate Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type FAA Certification. The FAA Certification 

may be carried in a combination of REF02 (30 

characters), REF03 (80 characters), C04002 (30 

characters), C04004 (30 characters), and C04006 (30 

characters) for a maximum of 200 characters. When 

extending the FAA Certification into the composite data 

elements, the C04001, C04003, and C04005 must cite 

code Y9. 

Use to identify bagged or 

tagged code, contents, 

marker code and 

identifier, medium, value 

(except for UII marks), 

and added data. 
Enclosure 1, ADC 1112 

Page 4 

6. 2/REF01/150 

(Used in 

HL03=”X”, 

Mark Loop) 

Add the following codes and associated notes: (continued) 

ZA Supplier 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Supplier Name. The Supplier Name may be 

carried in a combination of REF02 (30 charactes ) and 

REF03 (80 characters). 

AAG Military ID 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Service/Agency/Command. Authorized 

values for REF02 are: 

CHEMBIO 

MDA 

TRANSCOM 

SOCOM 

USARMY 

USAF 

USCG 

USMC 

USN 

AAL Agent Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type USMC Number. 

AAU General Agency Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type USA Number. 

AAW Agency Assigned Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type USAF Number. 

ABS Vessel Name 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Vessel Class. 

PRT Product Type 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Type Designation. Type Designation is a 

series of letters and numbers based on a standard (usually 

military) that identifies the type/model/series of a piece of 

equipment. Examples: F/A-18C means Fighter/Attack 

Aircraft model 18 Series C. CVN-75 means Nuclear 

Aircraft Carrier Hull Number 75. The Type Designation 

may be carried in a combination of REF02 (30 

characters) and REF03 (80 characters). 

Use to identify bagged or 

tagged code, contents, 

marker code and 

identifier, medium, value 

(except for UII marks), 

and added data. 
Enclosure 1, ADC 1112 

Page 5 

7. 2/REF01/150 

(Used in 

HL03=”X”, 

Mark Loop) 

Add the following codes and associated notes: (continued) 

TIP - Technical Information Package 

Use in Mark loop (HL03 code X) to identify the Medium 

for the mark data. Authorized values for REF02 are: 

2D COMPLIANT 

NONCOMPLIANT DATA MATRIX 

HUMAN READABLE 

CMB 

PDF417 

BARCODE 

RFID 

DEFINED 

PROFILE

Use to identify bagged or 

tagged code, contents, 

marker code and 

identifier, medium, value 

(except for UII marks), 

and added data. 

8. 2/REF04-

C04001/150 

(Used in 

HL03=”X”, 

Mark Loop) 

Add the following codes and associated notes: 

GU Internal Purchase Order Item Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Internal Asset Number. 

K6 Purchase Description 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Item Nomenclature. 

Y9 Current Certificate Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type FAA Certification. 

ZA Supplier 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Supplier Name. 

PRT Product Type 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Type Designation. 

Establish qualifier to 

enable the overflow of 

the Mark content type 

descriptions to the 

Composite data elements 

in the event there is 

insufficient space in the 

REF02/REF03. 

9. 2/REF04-

C04003/ 

C04005/150 

(Used in 

HL03=”X”, 

Mark Loop) 

Add the following codes and associated notes: 

GU Internal Purchase Order Item Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Internal Asset Number. 

K6 Purchase Description 

Use in Mark loop (HL03 code X) to identify the Mark 

content type Item Nomenclature. 

Y9 Current Certificate Number 

Use in Mark loop (HL03 code X) to identify the Mark 

content type FAA Certification. 

Establish qualifier to 

enable the overflow of 

the Mark content type 

descriptions to the 

Composite data elements 

in the event there is 

insufficient space in the 

REF02/REF03. 
Enclosure 1, ADC 1112 

Page 6 

10. 2/DTM/200 Add segment level note 4: 

4. Used in the Mark loop to identify the date of 

manufacturer and the date a “Mark” is placed on the 

item. 

Clarify business rule 

usage for Mark loop. 

11. 2/DTM01/200 

(Used in 

HL03=”X”, 

Mark Loop) 

Add Code 094 and note: 

094 Manufacture 

Use in Mark loop (HL03 code X) to identify Date of 

Manufacture 

The Date of 

Manufacturer is an IUID 

Mark data item. 

12. 2/DTM01/200 

(Used in 

HL03=”X”, 

Mark Loop 

Revise note to code 007: 

007 Effective 

1. Use in Part Characteristics loop (HL03 code J) to 

report the Current Part Number Effective Date. 

2. Use in Mark loop (HL03 code X) to identify the Date 

the Mark is placed on the item.

The Effective date is an 

IUID Mark data item. 

13. 2/N101/220 

(Used in 

HL03=”X”, 

Mark Loop) 

Add codes 42, AAU and associated notes: 

AAU Marker Owner 

Use in Mark loop (HL03 code X) to identify the Mark 

Owner, who represents the entity/activity that added the 

Mark to an item. 

 

42 Component Manufacturer 

Use in Mark loop (HL03 code X). 

Identify the Mark Owner 

and Manufacturer for the 

Mark information 

14. 2/N103/220 

(Used in 

HL03=”X”, 

Mark Loop) 

Add codes 14, 21, and 41 and notes: 

14 UCC/EAN Location Code Prefix 

Use to identify the UCC/EAN Company Prefix. Enter the 

prefix value (0-9) in the N104. 

 

21 Health Industry Number (HIN) 

When used in the Mark loop (HL03 code X), use to 

identify the European Health Industry Business 

Communications Council (EHIBCC) Number. 

41 Telecommunications Carrier Identification Code 

When used in the Mark loop (HL03 code X), use to 

identify the American National Standard for 

Telecommunications Information Interchange - Coded 

Representation of the North American 

Telecommunication Industry Manufacturers, Suppliers, 

and Related Service Companies (ANSI T1.220) value.