DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

January 22, 2019

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1215,

Wide Area Workflow (WAWF) Revisions to Include Multiple Serial Numbers for 

Serially Managed Items Without Registered Unique Item Identifiers (UII) and Supply 

Condition Codes for Property Transfer and Repairable Receiving Reports for Government 

Furnished Property (GFP) (Supply/Contract Administration)

We are forwarding the approved change to DLM 4000.25 Defense Logistics Management 

Standards, for immediate implementation.

Addressees may direct questions to Ms. Tonja Daniels-Carter, Contract Administration Lead, 

(269) 961-5227, DSN 661-5227, or e-mail Tonja.Daniels-Carter@dla.mil. Others must contact their 

Component designated representative available at

www.dla.mil/HQ/InformationOperations/DLMS/allpoc/.

HEIDI M. DAVEREDE

Director

Enterprise Business Standards Office

Attachment

cc:

ODASD(Logistics)

OUSD(AT&L)PDI

PIEE PM
Attachment, ADC 1215

Page 1

Attachment to ADC 1215

Wide Area Workflow (WAWF) Revisions to Include Multiple Serial 

Numbers for Serially Managed Items Without Registered Unique Item 

Identifiers (UII) and Supply Condition Codes for Property Transfer and 

Repairable Receiving Reports for Government Furnished Property 

(GFP)

1. ORIGINATORS:

a. Functional POC: Carol Vigna, Defense Procurement and Acquisition Policy (DPC),

e-mail: carol.a.vigna.civ@mail.mil

b. Technical POC: Tonja Daniels-Carter, Enterprise Business Standards Office, (269) 961-

5227, DSN 661-5227, or e-mail Tonja.Daniels-Carter@dla.mil.

2. FUNCTIONAL AREA:

a. Functional Area: Supply/Logistics

b. Functional Process: Government Furnished Property (GFP)/Reparables

3. REFERENCE:

a. PIEE Release 5.10, Post Critical Design Review, ECP 0796, Multiple Serial Numbers for 

Non-UII Items and ECP 0915, Add Condition Code to WAWF (formerly Invoice, Receipt Acceptance 

and Property Transfer (iRAPT)

b. MIL-STD-130, Department of Defense Standard Practice Identification Marking of U. S. 

Military Property 

c. DFARS 252.211-7007, Reporting of Government-Furnished Property

d. DoDM 4140.01, Supply Chain Materiel Management Procedures, Volume 2, Demand and 

Supply Planning, February 10, 2014.

4. APPROVED CHANGE(S): Green highlighting identifies significant revisions subsequent to 

staffing of Proposed DLMS Change (PDC) 1215. Subsequent to PDC 1215, the name Wide Area 

Workflow (WAWF) e-Business Suite was changed to the new enterprise solution name Procurement 

Integrated Enterprise Environment (PIEE). The name for the module Invoicing, Receipt, Acceptance, 

and Property Transfer (iRAPT) was changed back its original name of Wide Area Workflow 

(WAWF). This change is reflected throughout this change but is not specifically marked with green 

highlight. Additionally, the property transfer functions are moving to the GFP Module.

a. Brief Overview of Change: This change modifies the DLMS 856 Advance Shipment 

Notice (ASN), the associated Federal 856 and the Federal 857 Shipment and Billing Notice 

implementation conventions (IC) to permit tracking of serially-managed GFP. It modifies the WAWF

856 and DLMS 856 ASN transactions to include the capability to identify multiple serial numbers for 

serially managed items that are not marked with the unique item identifier (UII). It also adds the 

supply condition code to identify the condition of reparables. These changes support the PIEE 5.10 
Attachment, ADC 1215

Page 2

Release (Reference 3.a.), which adds functionality to capture and transmit multiple serial numbers and 

supply condition codes in the WAWF Property Transfer Document (PTD) and Reparable Receiving 

Report (RRR).

b. Background:

(1) MIL-STD-130, Identification Marking of U.S. Military Property (Reference 3.b.),

identifies marking requirements for item unique identification (IUID) however, there are some serially 

managed items that have not yet been marked with a unique item identifier (UII). WAWF does not 

currently have the functionality to capture and transmit multiple serial numbers for property transfers 

involving non-UII serially-managed GFP. MIL-STD-130 is silent on GFP; and does not specifically 

require IUID for GFP.

(2) Per DFARS 252.211-7007, contractors must report and update supply condition 

codes for reparables (Reference 3.c.). WAWF does not include a supply condition code data element 

for the property transfer or RRR and is being updated to accommodate the condition at time of 

shipment and receipt. Currently, contractors must update supply condition code manually in the IUID 

Registry. Contractors using DLMS logistics transactions report supply condition code to the owner at 

time of shipment, receipt, and as changes occur during maintenance.

(3) Current DOD procedures require generating separate standard logistics transactions 

for shipping like items that are known to be in different conditions. For DOD shipments controlled by 

a document number, a different document number, or potentially a document number suffix code, is 

assigned for each outgoing shipment; mixed condition materiel would not normally be shipped to the 

same location on the same document number. If a shipment contains like items with different 

conditions codes upon receipt, then the receiver will prepare separate receipt transactions for each 

item/condition and the receiving system will assign a document number suffix code to distinguish the 

shipments (regardless of whether the controlling number is a document number or a contract number). 

For example, certain existing supply systems (such as Distribution Standard System (DSS)) can only 

accommodate one supply condition code (for multiple items) per shipment.

(4) The PIEE 5.10 requirements and design review meetings identified several gaps for 

serial number field length and characteristics. The ODASD(Logistics) led IUID Working Group in 

harmonized these gaps and issued policy with specific guidance on serial number format and length. 

The following gaps were resolved:

(a) Per MIL-STD 130 (Reference 3.b.), the serial number used to construct UII 

is 30 characters with hyphen, forward slash, and no spaces; and the IUID Registry requires a 

maximum 30-character serial number for creation of UII, allowing hyphen and slash.

(b) The “Item Serial Number1” format in WAWF for the PTD and RRR is 30 

characters, allowing no special characters (except hyphen and forward slash) and no spaces.

(c) The serial number in DLMS transactions supporting IUID and Unique Item 

Tracking (UIT) (exclusive of small arms/light weapons (SA/LW)) was designed to be consistent with 

the IUID Registry, allowing 30 positions with no special characters other than hyphen and forward 

slash. The intent of the DLMS requirement is to capture the human readable serial number used for 

tracking (especially if different from the value used for creation of the UII). However, DLMS 

transactions originating from WAWF are perpetuating the pedigree UII serial number to the receiving 

 1 Per ECP 796 (Reference 3.a.), the “Item Serial Number is only provided for non-UII items. 
Attachment, ADC 1215

Page 3

activity. Although normally this will be consistent with the serial number used for tracking, it can 

differ and, therefore, will not satisfy DLMS requirements and will provide no meaningful information 

to the receiving activity. Expanding the serial number field length to 50 characters (as originally 

proposed for WAWF tracking of non-UII serially-managed GFP and for consistency with the human 

readable mark in the IUID registry) would require DLMS transactions to either remap the existing 

X12 data elements for serial number or upgrade the DLMS transactions to a higher X12 version.

(5) During development of this change, multiple inconsistencies between the WAWF

and DLMS logistics procedures were identified. 

(a) Currently, WAWF does not allow contractors to add or delete serial 

numbers at the time of receipt as might occur in a mis-shipment. If WAWF processes a shipment that 

contains either UIIs or serial numbers or a mix of both, WAWF expects to receive a transaction with a 

positive action for every UII/serial number, received or noted as rejected. However, this is not 

consistent with the DLMS requirement for receipt processing, which requires the receiving activity to 

receipt items using the actual serial number received when different from the shipment notice. A 

supply discrepancy report (SDR) must be submitted to the shipper identifying the mismatch scenario. 

There is no methodology to “reject” an item received using a DLMS 527R.

(b) Additionally, there are no WAWF allowances to ship serially-managed

items without either a UII or serial number within the same transaction as the marked items. The 

quantity shipped validation in WAWF requires the quantity shipped to equal the number of UIIs 

and/or serial numbers. Logistics rules do not have the same validation requirements and allow 

generation of DLMS 856S Shipment Status containing UII or serial numbers for selected items 

without requiring that the quantity shipped match the number of uniquely identified items. This is 

because the logistics requirement calls for inclusion of this data when readily available and does not 

require capture of the data when not barcoded on exterior packaging or resident in the supply system

(unless the materiel shipped falls under a UIT program). 

(c) DOD logistics systems perform receipt based on what physically arrives

and do not perform any rejections. As described above, WAWF requires a one-for-one match 

between the shipment and receipt, otherwise the receiver must establish a rejection of the item not 

received and a separate receipt transaction for an overage. Consequently, there are two areas of 

concern:

1. The edit on shipped quantity and UII/serial number may cause the 

DLMS 856S to fail at GEX when it converts a DLMS 856S for WAWF use.

2. The edit on receipt content validation against shipment content may

cause the 856 resulting from GEX conversion of a DLMS 527R Receipt to fail at WAWF. WAWF

recognized these issues and will evaluate the feasibility to bypass the edit noted above in the future.

(d) WAWF does not currently support use of a condition code in the 527R that 

differs from the condition code on the shipment. DLMS logistics transactions require this 

functionality. WAWF needs to be able to update the condition code on the receipt to reflect the actual 

quantity by condition code as received when different from the shipment information. 

(e) The DLMS 527R Receipt identifies UIIs and serial numbers applicable to 

serially managed items for the purpose of tracking. This intent is stated in the DLMS IC notes. If the 

pedigree UII serial number differs from the human readable serial number used for tracking, there will
Attachment, ADC 1215

Page 4

be a significant disconnect if the pedigree UII serial number is perpetuated from the WAWF ASN to 

the DLMS 527R Receipt. At this time, further coordination is needed to determine a way ahead.

(6) 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). Contractors may use this transaction 

to communicate with WAWF, but it is not applicable for transmission to other DOD systems.

c. Requested Change in Detail: WAWF will add functionality to submit serial numbers or 

UIIs coupled with the applicable supply condition code in the WAWF Property Transfer Document 

and Reparables Receiving Report. This includes the capability to submit multiple serial numbers for 

non-UII GFP. Revise the DLMS transaction formats and business rules to accommodate the WAWF

changes as follows:

(1) Revise DLMS 856 Advance Shipment Notice (ASN) transaction (resulting from

WAWF Property Transfer Document or Reparables Receiving Report):

(a) Add a new hierarchical loop to provide the capability to submit individual

serial numbers or UIIs coupled with supply condition codes, when applicable; do not provide both

serial number and UII for the same item coupled with its condition code. The Quality Characteristics

loop (HL03 – G) will be a child of the line item loop (HL03 = I) if it contains a single supply 

condition code applicable to all line items or UID loop (HL03 = D) if it contains UII or serial number, 

and supply condition code for each item.

1. Authorize the use of serial number in the Quality Characteristics loop 

to identify individual human readable serial numbers (when a UII is not available) and the associated 

supply condition code.

2. Provide DLMS notes and a new data field to identify the supply 

condition code associated with a specific serial number or UII.

(b) Authorize the use of a data field in the Pack loop to include the use of a 

multi-box pack indicator that must be provided once for each UII or item serial number that is part of 

a multi-box pack. Revise existing usage notes to indicate that UIIs and/or item serial numbers 

associated with a line item are packed across multiple boxes and note the use of “Yes” as a mark 

indicator for an item serial number that is packed across multiple boxes; there must be only one mark 

indicator per item.

(c) WAWF EDI receivers have the ability to perform receipt/reject via the 

WAWF 856 receipt transaction. This practice is not consistent with the DLMS 856 ASN and 

therefore, is excluded from this change.

(2) Federal 857, Shipment and Billing Notice transaction. This change adds

comparable changes to the 857 Federal transaction as identified for the DLMS 856 ASN to add a new 

Quality Characteristics loop to submit serial numbers or UIIs coupled with supply condition codes. 

Changes to the Federal 857 have no impact on internal DOD transactions.

d. Revisions to DLM 4000.25 Manuals: Revise DLMS 856 ASN and Federal 857 Shipment 

and Billing notice ICs as shown in Enclosure 1.

e. Transaction Flow: There are no revisions to existing transaction flow.
Attachment, ADC 1215

Page 5

f. Alternatives: None identified.

5. REASON FOR CHANGE: For WAWF: This will allow for multiple quantities per line item and 

the ability to process each item with a unique serial number. It provides the capability to provide the 

serial number for an item without a UII (item serial number). Additionally, these changes will allow 

supply condition code recording at the line item level and the individual item level.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) Enable WAWF to comply with DFARS requirements. There are instances where 

GFP items are serially managed, but do not have a UII. WAWF does not currently have the 

functionality to capture and transmit multiple serial numbers or supply condition codes. This change 

will enable contractors to report supply condition code during receipt or shipment.

(2) Enable WAWF to be single point of data submission for distribution to IUID 

Registry; reduce manual data entry of supply condition code in the IUID Registry

b. Disadvantages: None.

7. ADDITIONAL FUNCTIONAL REQUIREMENTS: WAWF ECP 915 does not address the 

required communication of supply condition code changes subsequent to receipt by the contractor and 

prior to return shipment to a DOD Activity. Commercial maintenance contractors are required to 

report condition changes to the owner during the repair cycle. For example, changes from Supply 

Condition Code F (unserviceable) to Supply Condition Code M (suspended, undergoing maintenance); 

and changes to Supply Condition Code G (unserviceable/awaiting parts). These updates to the owner 

must be reported via a DLMS 947I Inventory Adjustment (Supply Condition) transaction.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: WAWF Release 5.10 was 

implemented in 2017.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH IMPLEMENTATION 

OF THIS CHANGE: Not identified.

10. IMPACT:

a. DLMS Data Elements:

(1) Changes to 856 and 857 DLMS and DOD ICs in Enclosure 1.

(2) Add new DLMS Data Element: Multi Box Pack Indicator (ID, Min 1, Max 1). The 

multi-box pack indicator “A” indicates that an item identified by UII or serial number associated with a 

line item are packed across multiple boxes. (Uses SLN08 = A). 

b. WAWF: Implement DLMS changes to the 856 ASN and Federal 857. WAWF EDI format 

changes are in Enclosure 2.

c. Component Automated Information Systems (AIS): None
Attachment, ADC 1215

Page 6

d. Defense Automatic Addressing System (DAAS): Vendor will continue to route

transactions through GEX and WAWF3-RA channels for translation and transfer to the PIEE.

e. Non-DLM 4000.25 Series Publications: The WAWF Program Management Office will 

update the relevant WAWF Guides to reflect the changes identified by this DLMS change.

11. PROPOSED DLMS CHANGE (PDC) 1215 STAFFING RESPONSE/COMMENT 

RESOLUTION:

Originator Response/Comment Disposition

1 Air Force Concurs Noted

2 Army No Response

3 Marine Corps Concurs Noted

4 Navy Concurs Noted

5 DLA Concurs Noted

7 USTRANSCOM Concurs: No impact to USTRANSCOM systems based on 

this change.

Noted

8 DPC Concurs Noted
Enclosure 1, ADC 1215

Page 1

Enclosure 1, Changes to the Federal and DLMS Implementation Conventions 

Subsequent to PDC 1215, the name Wide Area Workflow (WAWF) e-Business Suite change to 

the new enterprise solution name Procurement Integrated Enterprise Environment (PIEE). The 

name for the module Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) was 

changed back its original name of Wide Area Workflow (WAWF). This change will be reflected 

in the updated DLMS 856 ASN and the Federal 857 Shipment and Billing Notice, however the 

individual changes will not be identified in the change tables other than where specific notes are 

modified by this change. The name change will not be reflected in the existing published ADC 

titles shown in the introductory note (856 ASN).

Item 

#

Location DLMS 856 Advance Shipment Notice (ASN) Reason

1. DLMS Introductory 

Notes

Change “Wide Area Work Flow (WAWF)” 

reference to the new enterprise solution name 

Procurement Integrated Enterprise Environment 

(PIEE) .

1. This DLMS Implementation Convention IC is 

based upon the Federal Implementation Convention 

(IC) 856, Ship Notice/Manifest and is provided for 

clarification of internal DoD use of the 856 as it 

pertains to Procurement Integrated Enterprise 

Environment (PIEE), Wide Area Work Flow. eBusiness Suite, Invoicing, Receipt, Acceptance and 

Property Transfer (iRAPT), formerly Wide Area 

Workflow – Receipt and Acceptance (WAWF-RA).

2. This document describes the advance shipment 

notice as extracted from iRAPT WAWF and 

forwarded to Defense Contract Management 

Agency (DCMA), payment offices, and receiving 

points. For submission of the 856 to iRAPT WAWF

please refer to the iRAPT WAWF Implementation 

Guide located on the Wide Area Work Flow PIEE

e-Business Suite Website at: https://wawf.eb.mil

Program name change
Enclosure 1, ADC 1215

Page 2

Item 

#

Location DLMS 856 Advance Shipment Notice (ASN) Reason

2. DLMS Introductory 

Note

Add ADC 1215 to DLMS Introductory Note 9 and 

add DLMS Introductory Note 10:

- ADC 1215, Wide Area Workflow (WAWF) 

Revisions to Include Multiple Serial Numbers for 

Serially Managed Items Without Registered

Unique Item Identifiers (UII) and Supply 

Condition Codes for Property Transfer and 

Repairable Receiving Reports for Government 

Furnished Property (GFP) (Supply/ Contract 

Administration).

12. The name Wide Area Workflow (WAWF) eBusiness Suite change to Procurement Integrated 

Enterprise Environment (PIEE). The name for the 

module Invoicing, Receipt, Acceptance, and 

Property Transfer (iRAPT) was changed to Wide 

Area Workflow (WAWF). This change is reflected 

in the IC notes.

Identifies a new functional 

requirement.

3. Throughout entire 

856 DLMS IC

1. Change all existing “Invoicing, Receipt, 

Acceptance, and Property Transfer (iRAPT)” 

references to Wide Area Workflow (WAWF). 

2. Change all existing Wide Area Workflow 

(WAWF) references to Procurement Integrated 

Enterprise Environment (PIEE)

Program name change

4. 2/HL03/010 Add Code G and DLMS Notes to HL03:

G Quality Characteristics

DLMS Note: 

1. For WAWF, use to identify the supply condition 

code associated with the human readable serial 

number or UII. This loop can be a child loop to 

the I Item loop (individual line item), or the D UID 

Loop. 

2. The following detail segments and elements are 

applicable to the G loop, 2/REF/150 and 

2/LM/340, 2/LQ/350.

Identifies a new functional 

requirement.
Enclosure 1, ADC 1215

Page 3

Item 

#

Location DLMS 856 Advance Shipment Notice (ASN) Reason

5. 2/HL03/010 Change Federal Note to DLMS Note for Pack loop

and add a second note:

Federal DLMS Note: 

1. When providing RFID information pertaining to a 

shipment, use to identify individual pack loops 

associated with RFID. Only the 2/REF/150 and 

2/SDQ/290 are used in this loop when reporting 

pack/RFID information. 

2. For Multi-Box Pack Indicator, only 2/SLN08/40 

and 2/REF04/150 are applicable.

Updates note and identifies a 

new functional requirement.

6. 2/SLN06/40 Open SLN06 and add DLMS Note

DLMS Note: For WAWF, use with SLN08, enter ) 

(zero) to comply with mandatory X12 syntax 

requirement.

Required for X12 Syntax 

when using SLN08 to identify 

a multi-box pack indicator

7. 2/SLN08/40 Open SLN08 ata element 662, Relationship Code 

(SLN08) and DLMS note:

DLMS Note: For WAWF, use in the Pack loop 

(HL03=P), to identify a Multi-Box Pack Indicator. 

Provide Code A to indicate that items identified by

UIIs and/or item serial numbers associated with 

this line item are packed across multiple boxes. 

2/REF04/150 is applicable to the P loop.

Identifies a new functional 

requirement.

8. 2/REF01/150 Add code SE and DLMS note: 

SE Serial Number

DLMS Note:

1. For WAWF, use to identify the human readable 

serial number in the Quality Characteristics loop 

(HL03=G) and the HL03=P). Enter the actual 

serial number in REF02. 

2. For the Pack loop, use the Mark Indicator “W9” 

in REF04-01 and enter “Yes” in REF04-02 for 

item serial number that is packed across multiple 

boxes; there must be one, and only one, mark 

indicator per item.

Identifies a new functional 

requirement.

9. 2/REF04/150 Open REF04 Identifies a new functional 

requirement.
Enclosure 1, ADC 1215

Page 4

Item 

#

Location DLMS 856 Advance Shipment Notice (ASN) Reason

10. 2/REF04-01/150 Open REF04-01, add code W9 and note:

W9 Special Packaging Instruction Number

DLMS Note: 

For WAWF, use to provide the Multi Box Pack 

Indicator. Enter ”Yes” in REF04-02 for a serially 

identified item that is packed across multiple 

boxes; there must be one, and only one, mark 

indicator per item.

Identifies a new functional 

requirement.

11. 2/REF04-02/150 Open REF04-02 Identifies a new functional 

requirement.

12. 2/LQ01/350 Add code 83 and DLMS note:

83 Supply Condition Code

DLMS Note: 

1. For WAWF, use in the IUID Loop (2/HL/010, 

HL03 = D) to identify the supply condition code

(SCC) associated with serial number or UII in 

2/REF/150. Provide the SCC value in 2/LQ02/350. 

Only provide one SCC per serial number or UII.

2. For WAWF, use in the Item loop (2/HL/010, 

HL03 = I) to identify the SCC associated with all 

items. 

3. The Distribution Standard System (DSS) does 

not use SCC in the DLMS 856 ASN; therefore, 

DSS may drop the SCC upon processing. 

Identifies a new functional 

requirement.
Enclosure 1, ADC 1215

Page 5

# Location Federal 857 Shipment and Billing Notice (Version 4010) Reason

1. 857 Notes Revise transaction note 4 and add new note 5. 

4. The hierarchical sequence of this transaction set is 

Shipment level information, Order level information, Item 

level information and Unique Identification (UID) level 

information. WAWF transactions may also include the

Quality Characteristic loop to identify the human 

readable serial number or UII coupled with the supply 

condition code.

5. The name Wide Area Workflow (WAWF) e-Business 

Suite was changed to Procurement Integrated Enterprise 

Environment (PIEE). The name for the module 

Invoicing, Receipt, Acceptance, and Property Transfer 

(iRAPT) was changed to Wide Area Workflow (WAWF). 

This change is reflected in the IC notes.

Identifies a new 

functional requirement.

2. 1/HL03/010 Add new code G and DLMS note:

G Quality Characteristics 

Federal Note: For WAWF, use to identify the supply 

condition code loop associated with the human readable

serial number or UII. This loop will be a child loop to the 

I Item Loop (individual line item), or the D UID Loop. 

The following detail segments and specific elements are 

applicable to the G Loop, 2/SLN/470 and 2/LM/505, 

2/LQ/506.

Identifies a new 

functional requirement.

3. 1/SLN09/470 Add new note 2 to code SN:

SN Serial Number

Federal Note:

1. Use to identify the item serial number.

2. For WAWF, use to identify human readable serial 

number in the Quality Characteristics Loop (HL03=G) 

and the HL03=P Pack Loop. Enter the actual serial 

number in SLN10.

Identifies a new 

functional requirement.

4. 1/LQ01/506 Add Code 83 and note:

83 Supply Condition Code

Federal Note: 

1. For WAWF, use in the IUID loop (1/HL/010, HL03 = 

D) to identify the Supply Condition Code (SCC) 

associated with serial number or UII in 1/SLN09/470.

Provide the SCC value in 1/LQ02/506. Only provide one 

SCC per serial number or UII. Do not provide one SCC 

for both serial number and UII.

2. For WAWF, use in the Item loop (1/HL/010, HL03 = I) 

to identify the SCC associated with all items.

Identifies a new 

functional requirement.
Enclosure 2, ADC 1215

Page 1

Enclosure 2: Sample WAWF EDI Formats:

Serial number with supply condition code:
Enclosure 2, ADC 1215

Page 2

UII with condition code:
Enclosure 2, ADC 1215

Page 3

Multi-Box Packing by Item Serial Number:

Note: WAWF uses a colon as the delimiter for Mark Indicator in composite data element REF04 (i.e., 

REF04-01 = W9 and REF04-01 = Yes)
Enclosure 2, ADC 1215

Page 4

Receipt with DLMS 527R:

EBSO Comment: The 527R Receipt was updated to include mandatory serial 

number and UII when available for capital equipment and UIT Items