1 

Attachment 1

ATTACHMENT TO ADC 417 

Shipment Status for Local Delivery Manifested, Outbound MILS Shipments on Behalf of 

On-Base Customers, Re-Warehousing Actions between Distribution Depots, 

 and non-MILS Shipments to Off-Base Customers, with Passive RFID 

1. ORIGINATOR: 

a. Service/Agency: DLA Distribution 

b. Originator: DLA Distribution J4

2. FUNCTIONAL AREA: 

a. Primary: Supply 

b. Secondary: Transportation/AIT/SDR 

3. REFERENCES: 

a. DOD 4000.25-M, Defense Logistics Management System (DLMS), Volume 3, 

Chapter 3, Passive Radio Frequency Identification (pRFID) Transactions

b. DOD 4000.25-M, Defense Logistics Management System (DLMS), Volume 2, 

Chapter 5, Status Reporting 

c. DOD Automatic Identification Technology (AIT) Implementation Plan For Supply 

and Distribution Operations, Spiral I, dated March 2008 

d. DOD Automatic Identification Technology (AIT) Implementation Plan For Supply 

and Distribution Operations, Spiral II, dated October 21, 2009 

4. BACKGROUND: 

a. Intent of the revision: To establish procedures for use of the DS 856S, Shipment 

Status, to document the application of pRFID tagging for shipments that are either local delivery 

manifesting to base customers, outbound MILS shipments on behalf of on-base customers, rewarehousing actions/transshipments between Distribution Depots in support of ‘Home’ 

Industrial Activity site and ‘Forward Support’ Industrial Activity site material requirements, or 

outbound non-MILS shipments (e.g., DD1149) to off-base customers. Implementing pRFID 

tagging on these shipments will provide enhanced intransit visibility and enable use of pRFID 

tag reads to trigger the automated receiving business processes/transactions at the customer 

location. Based on the staffing of the PDC, any significant changes to this document are 

highlighted in YELLOW. 

b. Scenario for which transaction is used: To implement pRFID tagging for these 

four scenarios, a DS 856S, Shipment Status, message is required to associate any pRFID tag(s) 
2 

Attachment 1

applied by the transportation activity to the document number of the item(s) being transshipped/cross-docked. Note that this change to the use of the DS 856S should not be interpreted 

to mean that it can be used in lieu of the Defense Transportation Electronic Business (DTEB) 

Committee 856A transactions; normal DTEB business rules for the 856A shall be followed. 

1) Local Delivery Manifesting: Examples of this scenario include Direct 

Vendor Delivery (DVD), Military Service/Agency, and non-DOD (e.g., GSA) shipments for 

local delivery to a base customer or delivery to a Material Processing Center (MPC). These 

shipments may already have had a shipment status message sent to the customer by either the 

Inventory Control Point (ICP) or the origin distribution activity. So, any subsequent DS 856S 

sent by the receiving transportation officer will need to be coded such that subsequent DS 856S 

generated for that document number carrying the pRFID tag information and updated shipment 

status are appended to the original shipment status, not overlaid. 

2) Outbound MILS Shipments on Behalf of On-Base Customers: Examples 

of this scenario occur when a supply activity processing a MILSTRIP requirement uses a base 

transportation office, with which they lack a direct interface, to deliver the material to the 

customer. If the supply and transportation activity lack a direct interface under the procedures 

stipulated by DOD 4000.25-M, Volume 3, Chapter 2, Retail Transportation and Supply 

Interchange, the supply activity generating the shipment status message may not have all the 

transportation data for dissemination to the customer. Additionally, if the transportation activity 

applies pRFID tags to the shipment, that information will not be available in the initial shipment 

status message. So, any subsequent DS 856S sent by the origin transportation officer will need 

to be coded such that subsequent DS 856S generated for that document number carrying the 

pRFID tag information and updated shipment status are appended to the original shipment status, 

not overlaid. If the outbound shipment in this scenario is in response to the material returns 

program (MRP), retrograde, or directed discrepant/deficient materiel returns1

, a DS 856R 

Materiel Returns Shipment Status message shall be used in lieu of the DS 856S. 

3) Re-warehousing Actions/Transshipments between Distribution Depots in 

support of ‘Home’ Industrial Activity site and ‘Forward Support’ Industrial Activity site 

material requirements2: Under this scenario, material that is physically located at the colocated DSS depot of the Industrial Activity ‘home site’ managing the maintenance action is 

required to support an off-station ‘forward site’ physically performing the maintenance. In 

support of this requirement, when directed by the material owner, DSS will re-warehouse the 

material from the ‘home site’ co-located DSS depot to the ‘forward site’ co-located DSS depot 

using their transshipment process and subsequently report the put away/stow completion back to 

the ‘home site’ depot. To enable application of a pRFID tag by the supplying depot and facilitate 

receipt take-up at the forward site support depot using the pRFID tag, a DS 856S Shipment 

                                                           

1 Approved DLMS Change 353A, Revised Procedures for Pre-positioned Materiel Receipt (PMR) and Shipment 

Status for Retrograde and Directed Discrepant/Deficient Materiel Returns Including Corrected Time Standard for 

Security Assistance/Foreign Military Sales (SA/FMS), dated August 25, 2010. 

2

 Proposed DLMS Change 384, Warehouse Service Request (for Materiel Protection/Re-Warehousing, Staging, and 

Picklist/Callout), New DS 943A, Warehouse Service Advice, and Associated Procedures under Navy BRAC 

SS&D/IMSP, dated April 20, 2010. 
3 

Attachment 1

Status message is required to associate the pRFID tag to the document number of the rewarehousing order. 

4) Outbound Non-MILS Shipments: A typical example of this scenario is a 

base customer documenting a shipment request on a DD1149, Requisition and Invoice/Shipping 

Document, and requesting the base transportation officer ship the material on their behalf. Since 

these are not requisitions/orders processed under normal MILSTRIP procedures, there is no 

provision for a supply shipment status message. So, a DS 856S is required to associate the 

pRFID tag number to the document number on the DD1149. The DS 856S in this scenario may 

not include all the traditional supply shipment status data elements; see Table 1 in paragraph 5 

below for listing of required data elements to support this scenario. 

c. Procedures, transactions, data elements, processing details in use today: 

1) DAAS “L” Table. All pRFID readers are required to be registered in DAAS. 

This is accomplished through use of the standard XML Reader Registration transaction, in which 

a unique Location Control Number (LCN) is assigned to the reader and its information is stored 

in the DAAS “L” table. 

 

2) DAAS “R” Table. When a shipment of DOD stocked material has pRFID 

tags applied to it, the association of the pRFID tag to a particular document number is identified 

in the DS 856S. For MRP, retrograde and directed returns with pRFID, the association of the 

pRFID tag to a particular document number is identified in the DS 856R. In addition to these 

transactions being routed under normal MILSTRIP business rules, a copy is stored in the DAAS 

“R” table as extended shipment data. 

3) DAAS “V” Table. When the pRFID tag is subsequently read by a registered 

reader, the standard XML visibility transaction is transmitted to DAAS to identify the LCN and 

the pRFID tag number that were read; this data is subsequently stored in the “V” table. 

4) The fusion of the data in the “L”, “R”, and “V” tables enables enterprise 

visibility systems (e.g., Asset Visibility and WebVLIPS) to provide intransit visibility in 

response to queries by associating the pRFID tag read to an LCN and a particular document 

number and/or transportation control number. 

5) Customer supply receiving business processes can be triggered by the pRFID 

tag read, by fusing the pRFID tag number with the matching 856S or 856R. 

6) This process works well for stocked shipments, as well as those moving 

through a DLA Containerization and Consolidation Point (CCP). However, the process 

delineated above has a gap when transportation offices are trans-shipping/cross-docking 

shipments for local delivery manifesting to on-base customers, outbound MILS shipments on 

behalf of on-base customers, re-warehousing actions between distribution depots, and outbound 

non-MILS shipments to off-base customers. For local delivery manifested shipments and 

outbound MILS shipments on behalf of on-base customers, the ICP may already have sent a 

shipment status message; however, the pRFID tag information and updated transportation data 
4 

Attachment 1

may be absent from the message. For re-warehousing actions and outbound non-MILS 

shipments, normally there is no supply shipment status message; therefore, the pRFID tag and 

transportation data are not transmitted to the receiving activity to facilitate use of pRFID tagging 

to trigger the receipt take-up process. 

5. APPROVED CHANGE: 

a. Description of Change in Detail: 

1) For local delivery manifested shipments, deliveries to the MPC, and outbound 

MILS shipments for On-Base Customers, the DS 856S will need to use the transaction status 

reason code (BSN07 = “091” Trans-ship/Cross-dock Shipment Status (non-CCP)) to denote that 

the shipment status is being provided by a location performing trans-shipping/cross-docking 

subsequent to the original shipment. The RIC From will be the RIC of the activity executing the 

local delivery manifest. The remaining data elements for a shipment status message will be 

ascertained from the pack list/shipping documentation accompanying the shipment. If the 

shipment already has a pRFID tag on it, no additional DS 856S is required; the existing pRFID 

tag will just need to be read and an XML Visibility transaction sent to DAAS recording the tag 

read event. If there is no document number either on the inbound data or on the pack 

list/shipping documentation, then do not generate the DS 856S for conveying the pRFID tag. 

This is to preclude a mismatch of data with the original DS 856S transmitted by the ICP, which 

will have a document number. DLA Transaction Services shall route the shipment status to the 

ship-to activity; standard DAAS business rules for distribution of the shipment status to status 

recipients shall not apply. 

2) Industrial Activity (IA) Support. For re-warehousing actions/ 

transshipments between Distribution Depots in support of ‘Home’ Industrial Activity site and 

‘Forward Support’ Industrial Activity site material requirements, a normal DS 856S (DIC AS8) 

should be generated and transmitted to DAAS (LQ02=AS8). NOTE: No status reason code is 

required for this scenario. This transaction should carry the normal shipment status message 

data, along with the pRFID tag identification numbers and any extended transportation data (e.g., 

bill of lading number, commercial carrier tracking numbers). Since there will never be a 

Material Receipt Acknowledgement (MRA) for these re-warehousing actions/transshipments 

between the Home and Forward Industrial Activities, a status reason code (BSN07=048 

Industrial Activity Re-Warehousing/Trans-ship Shipment Status) shall be included so that DLA 

Transaction Services can flag these DS 856S instances and prevent them from triggering the 

MRA Report. 

3) For outbound non-MILS shipments documented on a DD1149, a DS 856S 

will be created. Table 1 lists the minimum data elements that should be included in the shipment 

status message; sources of the data are the DD1149 and pRFID tag information. 

 
5 

Attachment 1

Table 1 (Non-MILS Shipment Status Message) 

Item 

# 

Data Element X12 Reference Value 

1. Transaction Set Purpose Code BSN01 “00” 

2. Shipment Identification BSN02 “ZZ” 

3. Transaction Date BSN03 [CCYYMMDD] 

4. Transaction Time BSN04 [HHMM] 

5. Transaction Type Code BSN06 “AS” 

6. Status Reason Code BSN07 “014” 

7. Hierarchical Level 

(Transaction Originator) 

HL01 “1” 

HL03 “V” 

8. Routing Identifier Code 

(From) 

N101 “CS” 

N103 “M4” 

N104 [RIC of Activity Generating Status]

N106 “FR” 

9. Hierarchical Level (Shipment 

Status Information) 

HL01 “2” 

HL03 “W” 

10. Materiel Identification LIN02 “FS” (for single line item NSN) 

“MG” (for single line item part 

number) 

“ZZ” (for multi-line items) 

LIN03 [NSN] (if LIN02 = “FS”) 

[Part Number] (if LIN02 = “MG”) 

 “MIXED” (if LIN02 = “ZZ”) 

11. Unit of Issue SN103 [Unit of Issue] (for single line 

items) 

“MX” (for multi-line items) 

12. Quantity SN102 [Quantity] (for single line items) 

“1” (for multi-line items) 

13. Document Number REF01 “TN” 

REF02 [Document Number from DD1149] 

14. Consignor N101 “CN” 

N103 “10” 

N104 [DODAAC] 

15. Ship To N101 “ST” 

N103 “10” 

N104 [DODAAC] 

N106 “TO” 

16. Release Date DTM01 “011” 

DTM02 [CCYYMMDD] 

17. Transportation Control 

Number 

REF01 “TG” 

REF02 [TCN] 
6 

Attachment 1

Item 

# 

Data Element X12 Reference Value 

18. Mode of Shipment TD504 [X12 Code from DLMS 

Conversion Guide] 

19. Hierarchical Level (Passive 

RFID Information) 

HL01 “3” 

HL02 [Parent Loop Number] (if multiple 

levels of pRFID used between 

interior and exterior packaging) 

HL03 “P” 

20. pRFID Tag Number REF01 “JH” 

REF02 [Tag Number] 

b. Additional Change: See attachment 1 for changes to the DS 856S and 856R to 

support the data requirements for this interchange. 

   

6. REASON FOR CHANGE: 

a. The DOD AIT Implementation Plans Spiral 1 and 2 direct the implementation of pRFID 

by DOD shippers. These plans require pRFID tagging to be enabled on Layer 1 (package), 

Layer 2 (Transport Unit), and Layer 3 (Unit Load). Spiral 1 introduced pRFID into the DOD 

wholesale and retail operations at DLA Distribution depots, service installations, and 

USTRANSCOM aerial ports. Spiral II builds on the foundation established in Spiral I to enable 

efficiencies in supply activities. The DOD vision is to enable a consistent, coordinated use of 

AIT media throughout DOD’s supply and distribution processes, to achieve seamless AIT and 

asset visibility. 

b. This change will also facilitate the implementation of Item Unique Identification, by 

providing visibility to enterprise systems, such as IGC and AV. By associating the IUID to the 

document number and transportation control number in the DS 856S, IGC and AV will be able 

to fuse the supply transactions associated with that IUID to the transportation transactions, 

without requiring all transportation systems to carry and validate IUID information while the 

material is in-transit. 

7. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Supports implementation of pRFID guidance stipulated by the DOD AIT 

Implementation Plan and expands the availability of tagging information to local delivery 

manifested shipments and non-MILS (DD1149) shipments. 

 b. Disadvantages: This will require retail transportation systems (e.g., Cargo Movement 

Operations System) to implement the DS 856S for these types of situations. For the outbound 

non-MILS shipments, there is a potential for redundancy in shipment status reporting with the 

Wide Area Workflow 856 Property Transfer Notice. 
7 

Attachment 1

8. NOTE ANY REGULATIONS OR GUIDANCE: See Attachment 2 for changes to the 

DLMS Manual supporting these new shipment status reporting requirements. 

9. ESTIMATED IMPLEMENTATION DATE: DLA target is May 2012. 

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: 

a. Cost Savings Estimate: The DLA Distribution projection is $2.36 million annually. 

This estimate is based on the DLA Distribution pRFID Enabled Receipt findings of a 5.5% (0.42 

hours) reduction in receipt time. Extrapolating this result in conjunction with an average cost of 

$26.44 per hour for warehouse personnel, the cost savings per receipt is up to $11.10. The DLA 

Distribution generates an average of 850,000 Transshipments per year, of which a potential of 

25% of these may be pRFID-enabled. Thus, the cost savings estimate is $2.36 million per year. 

b. Intangible Cost Avoidances: Enhanced visibility to the DOD supply chain.

11. IMPACT: 

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

changes to existing DLMS data elements resulting from this proposed change. There are three 

new codes authorized for use in the 856S and 856R BSN07 segment: 

1) 091 – Trans-ship/Cross-dock Shipment Status (non-CCP) 

2) 048 – Industrial Activity Re-Warehousing/Trans-ship Shipment Status 

3) 014 – Non-MILS Shipment Status (e.g., DD1149) 

b. DLA Transaction Services: 

1) Verify that WEBVLIPS, the “R” table, “L” table, and “V” table will function 

appropriately with the introduction of these additional DS 856S messages. 

2) Ensure that the data required to build the XML Visibility Response messages 

can be compiled in these four new pRFID tagging scenarios. 

3) Verify that the MRA Report will not react to the DS 856S messages for 

outbound non-MILS shipment transactions. There will never be an MRA reported for these 

shipments. 

4) Verify that the MRA Report will not react to the DS 856S messages for rewarehousing actions between distribution depots in support of IMSP Industrial Activities. There 

will never be an MRA reported for the re-warehousing actions in support of BRAC IMSP. 

5) Verify that the shipment status report is routed to the ship-to activity for local 

delivery manifested shipments, deliveries to the MPC, outbound MILS shipments for On-Base 
8 

Attachment 1

Customers, and non-MILS shipments (e.g., DD1149) to Off-Base Customers. Standard business 

rules for distribution of the shipment status shall not apply. 

c. DoD WebSDR Interface Requirement: The shipment status contents shall be made 

available for prepopulation of the shipment history on Supply Discrepancy Reports using DoD 

WebSDR. 

 

d. IGC: This is a new business process that will generate additional DS 856S, for 

which there may already be previously transmitted shipment status messages in support of local 

delivery manifested and outbound MILS shipments supporting on-base customers. For DS 856S 

in response to non-MILS shipments, there will likely be no document number information, since 

these shipment requirements are processed outside the normal MILSTRIP procedures. 

 
1 

Enclosure 1 

Enclosure 1 to ADC 417 

Item 

# 

Location Revision to 4030 DS 856S Shipment Status Reason 

1. DLMS 

Introductory 

Note 

Add ADC 417 to Introductory note for PDCs/ADCs:

- ADC 417, Shipment Status for Local Delivery 

Manifested, Outbound MILS Shipments on Behalf 

of On-Base Customers, Re-Warehousing Actions 

between Distribution Depots, and non-MILS 

Shipments to Off-Base Customers, with Passive 

RFID

To identify DLMS 

changes included 

in the DS 

2. 1/BSN06/0200 Modify existing DLMS note to existing code AS:

AS Shipment Advice 

DLMS Note: 

1. Use to indicate this transaction provides shipment 

status information related to requisitions. 

2. Also applies to Army Total Package Fielding. 

3. Use with BSN07=WTP to identify CAV Shipment 

Status. 

4. Use with BSN07=014 for outbound non-MILS 

shipments (e.g., a DD1149). Refer to ADC 417

To identify 

outbound intraArmy non-MILS 

shipment via DD 

1149 

3. 1/BSN07/0200 Modify existing DLMS note to existing code 061:

061 Consolidation, Extension, Modification (CEM) 

Use to identify that shipment status is provided by the 

Consolidation and Containerization Point (CCP) or 

other location performing consolidation subsequent 

to original shipment, e.g., local delivery manifesting,

in support of passive RFID data exchange. The CCP 

Shipment Status may reflect multiple levels of pack 

associated with the lead Transportation Control 

Number (TCN). It may update the shipment date or 

mode of shipment while providing visibility of 

additional or replacement passive RFID tag values 

associated with the original shipment as a result of 

CCP processing/ reconfiguration. The CCP Shipment 

Status should not be used to overlay the original 

shipment status in the receiving application, as this 

may result in some loss of data content. 

To limit use of this 

qualifier to CCP 

use only. 
2 

Enclosure 1 

Item 

# 

Location Revision to 4030 DS 856S Shipment Status Reason 

4. 1/BSN07/0200 Add new qualifiers and DLMS notes:

091 Reprocessed 

Trans-ship/Cross-dock Shipment Status (non-CCP). 

Use to identify that shipment status is provided by a 

location performing consolidation subsequent to 

original shipment (e.g., local delivery manifesting, 

deliveries to MPC) in support of passive RFID data 

exchange. The status may reflect multiple levels of 

pack associated with the lead Transportation Control 

Number (TCN). It may update the shipment date or 

mode of shipment while providing visibility of 

additional or replacement passive RFID tag values 

associated with the original shipment as a result of 

processing/ reconfiguration. The Shipment Status 

should not be used to overlay the original shipment 

status in the receiving application, as this may result 

in some loss of data content. Refer to ADC 417. 

 

014 Military Service 

Use to identify that the shipment status is provided in 

response to a non-MILS shipment (e.g., DD1149) in 

support of passive RFID data exchange. The status 

may reflect multiple levels of pack associated with 

the shipment unit Transportation Control Number 

(TCN) and may provide the secondary transportation 

data (e.g., bill of lading, tracking number, carrier 

identification). Refer to ADC 417. 

048 Location Changed 

Industrial Activity Re-Warehousing/Trans-ship 

Shipment Status. Use to identify that the shipment 

status is provided in response to rewarehousing/transshipments between Home and 

Forward Industrial Activities in support of IMSP. 

Since no Material Receipt Acknowledgement (MRA) 

is required for these types of shipments, the shipment 

status will not trigger the MRA Reports. 

To identify unique 

reason codes for 

processing 856S in 

support of local 

delivery 

manifesting and 

non-MILS 

DD1149 

shipments. 

No separate reason 

code is required 

for the Industrial 

Activity Rewarehousing 

support shipments.
3 

Enclosure 1 

Item 

# 

Location Revision to 4030 DS 856S Shipment Status Reason 

5. 2/SN102/0300 Modify Existing DLMS note: 

Number of Units Shipped 

DLMS Note: 

1. For shipment status and lateral redistribution 

shipment status, use to identify the shipped quantity. 

2. For pseudo shipment status (BSN06 code NC), use 

to identify the Material Release Order (MRO) 

quantity. 

3. A field size exceeding 5 positions may not be 

received or understood by the recipient's automated 

processing system. See introductory DLMS note 2d. 

4. For CAV shipment status (BSN06=WTP), use to 

indicate quantity shipped or quantity reversed. 

Always enter a quantity of one (1). A separate CAV 

shipment status is prepared for each individual item 

shipped. To reverse, enter a quantity of minus one 

(-1). 

5. For non-MILS shipment (e.g., DD1149) status 

(BSN07=014) in support of pRFID exchange, when 

2/LIN02/0200=ZZ and 2/LIN03/0200=MIXED, enter 

a quantity of one (1) to indicate multi-line items. 

Refer to ADC 417. 

Identifies that 

multi-line items 

comprising mixed 

NSNs are being 

conveyed. 

6. 2/SN103/0300 Modify existing DLMS note

Unit or Basis for Measurement Code 

DLMS Notes: 

1.DLMS users see the Unit of Issue 

Conversion Table for available codes. 

2. For non-MILS shipment (e.g., DD1149) status, 

(BSN07=014) in support of pRFID exchange, when 

2/LIN02/0200=ZZ and 2/LIN03/0200=MIXED, enter 

a unit of issue of “MX”. Refer to ADC 417. 

Identifies that 

multi-line items 

comprising mixed 

NSNs are being 

conveyed. 
4 

Enclosure 1 

Item 

# 

Location Revision to 4030 DS 856S Shipment Status Reason 

7. 2/N101/2200 Modify existing DLMS note to existing code CS:

CS Consolidator 

DLMS Note: 

1. Use to identify the consolidation point DoDAAC 

when shipment status is provided by the CCP or other

activity performing consolidation, e.g. local delivery 

manifesting (BSN07=061). 

2. For non-MILS shipment (e.g., DD1149) status, 

(BSN07=014) in support of pRFID exchange, use to 

identify the origin activity generating the shipment 

status. Refer to ADC 417. 

To identify the 

consolidator for 

non-MILS 

DD1149 

shipments. 
1 

Enclosure 2 

Enclosure 2 to ADC 417 

Item 

# 

Location Revision to 4030 DS 856R Shipment Status 

Material Returns 

Reason 

1. DLMS 

Introductory 

Note 

Add ADC 417 to Introductory note for PDCs/ADCs:

- ADC 417, Shipment Status for Local Delivery 

Manifested, Outbound MILS Shipments on Behalf 

of On-Base Customers, Re-Warehousing Actions 

between Distribution Depots, and non-MILS 

Shipments to Off-Base Customers, with Passive 

RFID

To identify DLMS 

changes included 

in the DS 

2. 1/BSN07/0200 Add new qualifier and DLMS note:

091 Reprocessed 

Trans-ship/Cross-dock Shipment Status (non-CCP). 

Use to identify that shipment status is provided by a 

location performing consolidation subsequent to 

original shipment (e.g., local delivery manifesting) in 

support of passive RFID data exchange. The status 

may reflect multiple levels of pack associated with 

the lead Transportation Control Number (TCN). It 

may update the shipment date or mode of shipment 

while providing visibility of additional or 

replacement passive RFID tag values associated with 

the original shipment as a result of processing/ 

reconfiguration. The Shipment Status should not be 

used to overlay the original shipment status in the 

receiving application, as this may result in some loss 

of data content. Refer to ADC 417. 

 

014 Military Service

Use to identify that the shipment status is provided in 

response to a non-MILS shipment (e.g., DD1149) in 

support of passive RFID data exchange. The status 

may reflect multiple levels of pack associated with 

the shipment unit Transportation Control Number 

(TCN) and may provide the secondary transportation 

data (e.g., bill of lading, tracking number, carrier 

identification). Refer to ADC 417.

To identify a 

unique reason code 

for processing 

856R in support of 

outbound MILS 

shipments on 

behalf of on-base 

customers 

supporting the 

material returns 

program (MRP), 

retrograde, or 

directed 

discrepant/ 

deficient materiel 

returns, where 

there is no direct 

interface between 

the base supply 

and transportation 

systems. 
1 

Enclosure 3 

Enclosure 3 – DLMS Manual Changes 

1. Insert the following new paragraph in DoD 4000.25-M Volume 2, Chapter 5, Status 

Reporting at C5.2.3.3, and renumber subsequent paragraphs. 

C5.2.3.3. Shipment Status for Local Delivery Manifested, Outbound MILS Shipments on 

Behalf of On-Base Customers, Re-warehousing actions/transshipments between 

Distribution Depots in support of ‘Home’ Industrial Activity and ‘Forward Support’ 

Industrial Activity site material requirements, and non-MILS Shipments (e.g., DD1149) to 

Off-Base Customers, with Passive RFID. For shipments prepared by the Transportation Office 

that are local delivery manifested, Materiel Processing Center (MPC) deliveries, outbound MILS 

shipments on behalf of on-base customers, re-warehousing actions between distribution depots, 

and outbound non-MILS shipments (e.g., DD1149) to off-base customers, the shipment status 

shall be prepared IAW paragraph C5.2.3.1 using DS 856S, Shipment Status, to include 

identifying the passive RFID information and associating the tag data to the document number of 

the item(s) to be trans-shipped or cross-docked. 

 C5.2.3.3.1. For local delivery manifested shipments, MPC deliveries, and 

outbound MILS shipments for On-Base Customers, the DS 856S will need to use the transaction 

status reason code (BSN07 = “091” Trans-ship/Cross-dock Shipment Status (non-CCP)) to 

denote that the shipment status is being provided by a location performing trans-shipping/crossdocking subsequent to the original shipment. The RIC From will be the RIC of the activity 

executing the local delivery manifest. The remaining data elements for a shipment status 

message will be ascertained from the pack list/shipping documentation accompanying the 

shipment. If the shipment already has a pRFID tag on it, no additional DS 856S is required; the 

existing pRFID tag will just need to be read and an XML Visibility transaction sent to DLA 

Transaction Services recording the tag read event. If there is no document number either on the 

inbound data or on the pack list/shipping documentation, then do not generate the DS 856S for 

conveying the pRFID tag. This is to preclude a mismatch of data with the original DS 856S 

transmitted by the ICP, which will have a document number. 

 C5.2.3.3.2. For re-warehousing actions/transshipments between Distribution 

Depots in support of ‘Home’ Industrial Activity site and ‘Forward Support’ Industrial Activity 

site material requirements, a normal DS 856S should be generated and transmitted to DAAS. 

This transaction should carry the normal shipment status message data, along with the pRFID tag 

identification numbers and any extended transportation data (e.g., bill of lading number, 

commercial carrier tracking numbers). Since there will never be a Material Receipt 

Acknowledgement (MRA) for these re-warehousing actions/transshipments between the Home 

and Forward Industrial Activities, a status reason code (BSN07=”048” Industrial Activity ReWarehousing/Trans-ship Shipment Status) shall be included so that DLA Transaction Services 

can flag these DS 856S instances and prevent them from triggering the MRA Report. 

 C5.2.3.3.3. For outbound non-MILS shipments documented on a DD1149, a 

DS 856S will be created. Table C5.T1 lists the minimum data elements that should be included 

in the shipment status message; sources of the data are the DD1149 and pRFID tag information. 
2 

Enclosure 3 

Table C5.T1. Non-MILS Shipment Status Message

Item 

# 

Data Element X12 Reference Value 

1. Transaction Set Purpose Code BSN01 “00” 

2. Shipment Identification BSN02 “ZZ” 

3. Transaction Date BSN03 [CCYYMMDD] 

4. Transaction Time BSN04 [HHMM] 

5. Transaction Type Code BSN06 “AS” 

6. Status Reason Code BSN07 “014” 

7. Hierarchical Level 

(Transaction Originator) 

HL01 “1” 

HL03 “V” 

8. Routing Identifier Code 

(From) 

N101 “CS” 

N103 “M4” 

N104 [RIC of Activity Generating Status]

N106 “FR” 

9. Hierarchical Level (Shipment 

Status Information) 

HL01 “2” 

HL03 “W” 

10. Materiel Identification LIN02 “FS” (for single line item NSN) 

“MG” (for single line item part 

number) 

“ZZ” (for multi-line items) 

LIN03 [NSN] (if LIN02 = “FS”) 

[Part Number] (if LIN02 = “MG”) 

 “MIXED” (if LIN02 = “ZZ”) 

11. Unit of Issue SN103 [Unit of Issue] (for single line 

items) 

“MX” (for multi-line items) 

12. Quantity SN102 [Quantity] (for single line items) 

“1” (for multi-line items) 

13. Document Number REF01 “TN” 

REF02 [Document Number from DD1149] 

14. Consignor N101 “CN” 

N103 “10” 

N104 [DODAAC] 

15. Ship To N101 “ST” 

N103 “10” 

N104 [DODAAC] 

N106 “TO” 

16. Release Date DTM01 “011” 

DTM02 [CCYYMMDD] 

17. Transportation Control 

Number 

REF01 “TG” 

REF02 [TCN] 
3 

Enclosure 3 

Item 

# 

Data Element X12 Reference Value 

18. Mode of Shipment TD504 [X12 Code from DLMS 

Conversion Guide] 

19. Hierarchical Level (Passive 

RFID Information) 

HL01 “3” 

HL02 [Parent Loop Number] (if multiple 

levels of pRFID used between 

interior and exterior packaging) 

HL03 “P” 

20. pRFID Tag Number REF01 “JH” 

REF02 [Tag Number] 

C5.2.3.3.4. DAAS Distribution of Shipment Status for Local Delivery 

Manifested, Deliveries to MPC, Outbound MILS Shipments on Behalf of On-Base Customers,

and non-MILS Shipments (e.g., DD1149) to Off-Base Customers. DAAS will route the 

shipment status to the ship-to activity. Standard DAAS business rules for distribution of the 

shipment status to status recipients will not apply. 

 C5.2.3.3.5. DAAS Distribution of Shipment Status for Re-warehousing 

actions/transshipments between Distribution Depots in support of ‘Home’ Industrial Activity and 

‘Forward Support’ Industrial Activity site material requirements. DAAS will route the shipment 

status according to standard DAAS business rules for distribution of the shipment status to status 

recipients. 

 C5.2.3.3.6. Receiving Activity Use of Shipment Status for Local Delivery 

Manifested, Deliveries to MPC, Outbound MILS Shipments on Behalf of On-Base Customers, 

Re-warehousing actions/transshipments between Distribution Depots in support of ‘Home’ 

Industrial Activity and ‘Forward Support’ Industrial Activity site material requirements, and 

non-MILS Shipments (e.g., DD1149) to Off-Base Customers. The value of this transaction to 

the receiving activity is to support passive RFID-enabled receipt processing. DLMS applications 

not supporting passive RFID may disregard this status or choose to append the mode of shipment 

and the shipment date. New content on the shipment status should not be viewed as replacement 

values for a previously received shipment status matching on document number/suffix.

 
4 

Enclosure 3 

2. Insert the following new paragraph in DoD 4000.25-M Volume 3, Chapter 3, Passive 

Radio Frequency Identification (RFID) Transactions C3.11, and renumber subsequent 

paragraphs. 

C3.11. PASSIVE RFID AND SHIPMENT STATUS.

 C3.11.1. DAAS “L” Table. All pRFID readers are required to be registered in DAAS. 

This is accomplished through use of the standard XML Reader Registration transaction, in which 

a unique Location Control Number is assigned to the reader and its information is stored in the 

DAAS “L” table. 

 C3.11.2. DAAS “R” Table. When a shipment of DOD stocked material has pRFID tags 

applied to it, the association of the pRFID tag to a particular document number is identified in 

the DS 856S. For Materiel Returns Program, retrograde and directed returns with pRFID, the 

association of the pRFID tag to a particular document number is identified in the DS 856R. In 

addition to these transactions being routed under normal MILSTRIP business rules, a copy is 

stored in the DAAS “R” table as extended shipment data. 

 C3.11.3. DAAS “V” Table. When the pRFID tag is subsequently read by a registered 

reader, the standard XML visibility transaction is transmitted to DAAS to identify the LCN and 

the pRFID tag number that were read; this data is subsequently stored in the “V” table. 

C3.11.4. The fusion of the data in the “L”, “R”, and “V” tables enables enterprise 

visibility systems (e.g., Asset Visibility and WebVLIPS) to provide intransit visibility in 

response to queries by associating the pRFID tag read to an LCN and a particular document 

number and/or transportation control number. 

C3.11.5. Customer supply receiving business processes can be triggered by the pRFID 

tag read, by fusing the pRFID tag number with the matching 856S or 856R. 

C3.11.6. This process works well for stocked shipments, as well as those moving through 

a DLA Containerization and Consolidation Point (CCP). However, the process delineated above 

has a gap when transportation offices are trans-shipping/cross-docking shipments for local 

delivery manifesting to on-base customers, deliveries to Materiel Processing Centers (MPC), 

outbound MILS shipments on behalf of on-base customers, re-warehousing actions between 

distribution depots, and outbound non-MILS shipments to off-base customers. For local delivery 

manifested shipments, deliveries to MPC, and outbound MILS shipments on behalf of on-base 

customers, the ICP may already have sent a shipment status message; however, the pRFID tag 

information and updated transportation data may be absent from the message. For rewarehousing actions and outbound non-MILS shipments, normally there is no supply shipment 

status message; therefore, the pRFID tag and transportation data are not transmitted to the 

receiving activity to facilitate use of pRFID tagging to trigger the receipt take-up process. For 

those requirements when transportation offices are trans-shipping/cross-docking shipments, other 

shipment status reporting procedures are followed. These scenarios include local delivery 

manifesting to on-base customers, deliveries to MPC, outbound MILS shipments on behalf of 
5 

Enclosure 3 

on-base customers, re-warehousing actions between distribution depots, and outbound non-MILS 

shipments to off-base customers. 

 C3.11.6.1. For local delivery manifested shipments, deliveries to MPC, and 

outbound MILS shipments for On-Base Customers, the DS 856S will need to use the transaction 

status reason code (BSN07 = “091” Trans-ship/Cross-dock Shipment Status (non-CCP)) to 

denote that the shipment status is being provided by a location performing trans-shipping/crossdocking subsequent to the original shipment. The RIC From will be the RIC of the activity 

executing the local delivery manifest. The remaining data elements for a shipment status 

message will be ascertained from the pack list/shipping documentation accompanying the 

shipment. If the shipment already has a pRFID tag on it, no additional DS 856S is required; the 

existing pRFID tag will just need to be read and an XML Visibility transaction sent to DAAS 

recording the tag read event. If there is no document number either on the inbound data or on the 

pack list/shipping documentation, then do not generate the DS 856S for conveying the pRFID 

tag. This is to preclude a mismatch of data with the original DS 856S transmitted by the ICP, 

which will have a document number. 

 C3.11.6.2. For re-warehousing actions/transshipments between Distribution 

Depots in support of ‘Home’ Industrial Activity site and ‘Forward Support’ Industrial Activity 

site material requirements, a normal DS 856S should be generated and transmitted to DAAS. 

This transaction should carry the normal shipment status message data, along with the pRFID tag 

identification numbers and any extended transportation data (e.g., bill of lading number, 

commercial carrier tracking numbers). Since there will never be a Material Receipt 

Acknowledgement (MRA) for these re-warehousing actions/transshipments between the Home 

and Forward Industrial Activities, a status reason code (BSN07=”048” Industrial Activity ReWarehousing/Trans-ship Shipment Status) shall be included so that DLA Transaction Services 

can flag these DS 856S instances and prevent them from triggering the MRA Report. 

 C3.11.6.3. For Outbound Non-MILS shipments documented on a DD1149, a 

DS 856S will be created. See the DLMS Manual, Volume 2, Chapter 5, Status Reporting, Table 

C.5.T.1. for the minimum data elements that should be included in the shipment status message; 

sources of the data are the DD1149 and pRFID tag information.
1 

Enclosure 4 

Enclosure 4, PDC 424 RESPONSE/COMMENTS: 

Organization Response/Comment Disposition 

DLA Transaction Services No impact from SDR group. 

From logistics group, need to 

identify a means to identify 

the 856S from 

“Rewarehousing 

actions/transshipments 

between distribution depots 

in support of Home IA site 

and Forward IA site material 

requirements, so as to 

exclude from MRA 

Reporting. 

Added BSN07=048 for this 

IMSP rewarehousing/ 

transship scenario. 

USTRANSCOM Concur.

DFAS No comment. 

DLA Concur. 

Navy Concur. 

Air Force Concur with comment: Need 

to add statement that the 

856S in these scenarios is not 

to be considered a 

replacement for the 856A 

transaction to retail 

transportation systems. 

Inserted at paragraph 4.b. 

“Note that this change to the 

use of the DS 856S should 

not be interpreted to mean 

that it can be used in lieu of 

the Defense Transportation 

Electronic Business (DTEB) 

Committee 856A 

transactions; normal DTEB 

business rules for the 856A 

shall be followed.” 

Marine Corps Concur. 

Army Concur. 

DLA Logistics Management 

Standards 

Add DLMS definitions for 

BSN07=091 and BSN07=48. 

Add statement for the 

BSN07=91 scenarios that 

routing of transactions shall 

be determined by the Ship 

To, which supersedes the 

current routing procedures at 

DLA Transaction Services. 

Inserted at paragraphs 5.a.1), 

5.a.2) and 11.a. 

Inserted at paragraph 5.a.1). 
2 

Enclosure 4 

Add requirement for DLA 

Transaction Services to use 

this shipment status content 

to prepopulate the shipment 

history for Supply 

Discrepancy Reports using 

DoD WebSDR. 

Added new paragraph 11.c.