1

ADC 288 

Local Delivery Manifesting Shipment Status 

1. ORIGINATOR: 

a. Service/Agency: Defense Distribution Center (DDC), DLA J 3/J4-TPR, (717) 770-7208

b. Sponsor: Defense Logistics Management Standards Office (DLMSO), Supply Process Review 

Committee (PRC): Ms. Ellen Hilert, Chair, Supply PRC, 703-767-0676; DSN: 427-0676; e-mail: 

ellen.hilert@dla.mil

2. FUNCTIONAL AREA: Primary: Supply

3. REFERENCE: DLMSO memorandum dated November 15, 2007, subject: Approved Defense 

Logistics Management System (DLMS) Change (ADC) 257, DLMS Shipment Status Generated by the 

Consolidation and Containerization Point (CCP). This change documented the CCP preparation of the 

DLMS Shipment Status using the Distribution Standard System (DSS) to provide passive Radio 

Frequency Identification (RFID) tag information following reconfiguration of the original shipment, 

when the shipper did not provide passive RFID, or when the original passive RFID tag was damaged. 

The change authorized a revision of the transaction format to clearly define this usage and distinguish 

it from shipment status transactions generated by the distribution depots on behalf of the source of 

supply. It provided new business rules for the distribution and use of the CCP shipment status. 

4. REQUESTED CHANGE: 

a. Description of Change: This change updates the DLMS shipment status procedures and the 

DLMS Version 4030 856S, Shipment Status transaction. It authorizes expanded use of the CCP 

shipment status format (see reference above) to include other consolidation processes performed 

subsequent to creation of shipment status, such as local delivery manifesting, for the purpose of 

providing passive RFID and updated status. 

b. Procedures: The procedures below mirror those approved for CCP shipment status (additional 

requirements or revisions from published CCP procedures are identified in bold italics).

(1) CCP and Local Delivery Consolidation Shipment Status Preparation. The 

consolidating activity will generate a shipment status transaction using the 856S format to provide 

passive RFID information to the receiving activity and other automated information systems in 

accordance with Service-directed business rules. 

(a) The consolidation shipment status will be identified by a unique code in the beginning 

segment of the transaction (Code 061 in BSN07). 

(b) The ship-to activity will be explicitly identified in the transaction using the designated 

DLMS enhancement (the Ship-To Qualifier ST in the N1 segment). 
2

 (c) The consolidation shipment status will carry the lead TCN which may differ from that 

on the original shipment status and will contain multiple passive RFID tag values using a hierarchical 

structure. The original passive RFID will be repeated when it is available. 

(d) The transaction originator field will identify the Routing Identifier of the Inventory 

Control Point perpetuated from the original shipment status. 

 (e) A new data field will be added to identify the DoDAAC of the location where the 

consolidation occurred, e.g., CCP or depot. 

 (f) The shipment date identified will be the local delivery consolidation shipment date. 

 (g) The mode of shipment will be the mode shipped by the consolidating depot. 

 (h) The original shipment status data content may not be perpetuated; normal shipment 

status data fields will not be populated. 

(2) DAAS Distribution/Business Rules. DAAS will route the consolidation shipment status 

to the ship-to activity and other automated information systems in accordance with Service-directed 

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

recipients will not apply. In addition, DAASC will suppress sending the consolidation shipment status 

to Distribution Depots or the Material Processing Centers (MPC) supported by the Distribution 

Standard System for Navy ships. 

(a) DAAS will assign the Document Identifier (DI) Code (located in the LQ segment) as 

AS1 if the ship-to activity is the same as the Document Number DoDAAC; otherwise DAAS will 

assign as AS2. 

 (b) DAAS will not convert the DLMS transaction to a MILS format, as this will not 

provide meaningful data and may cause confusion. 

(c) DAAS will post the updated information to the DAAS Passive RFID (R) Table making 

this information available for passive RFID query. 

(d) DAAS will make the consolidation shipment status information available via 

WebVLIPS. (DAASC may establish a separate, later implementation date for this aspect of the 

requirement.) 

(e) The consolidation shipment status may not be employed in determining processing 

time within Logistics Metrics Analysis Reporting System (LMARS) /Customer Wait Time metrics. 

(3) Receiving Activity. 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 consolidation mode of shipment and shipment date. New 

content on the consolidation shipment status should not be viewed as replacement values for a 

previously received shipment status matching on document number/suffix. Since there may not be a 
3

match on the previously identified TCN, the consolidation shipment status information must be 

handled in a way that does not impact quantity due or visibility of partial shipments which may not 

have been consolidated within the reconfigured shipment. 

 (4) Revise DS 4030 856S, Shipment Status as follows:

# Location Revision to 

4030 856S, Shipment Status 

Reason for Change 

1 DLMS 

Introductory 

note _ 

Add ADC 288 to DLMS introductory note 3:

- ADC 288, DSS Local Delivery Manifesting Shipment Status 

To identify changes in the 

DS. 

2 1/BSN07/02

00 

Revise DLMS Note for the following code to read:

061 Consolidation, Extension, Modification (CEM) 

DLMS Note: 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 clarify expanded 

usage. 

3 2/N101/2200 Revise wording of DLMS Note:

SB Storage Area 

DLMS Note: 

1. Use to identify the initial shipping activity Distribution Depot 

DoDAAC. 

2. For Army Total Package Fielding (TPF), use to identify the 

Routing Identifier of the Unit Materiel Fielding Point (UMFP) or 

staging site originating the UMFP shipment document. 

Clarification. 

On routine shipment 

status, this data field is 

provided to identify the 

initial shipping activity 

when the shipment 

originates from a 

Distribution Depot. 

This data element was 

approved for 

implementation in 

standard shipment status 

transactions under ADC 

223 and is being 

implemented by DSS in 

conjunction with ADC 

288. 

4 2/N101/2200 Add new qualifier and DLMS Note:

CS Consolidator 

DLMS Note: 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).

Used to clearly identify 

the location where the 

consolidation occurred. 

When identifying the 

CCP this will be the 

DoDAAC of the physical 

CCP (not the DSS 

mission DoDAAC). 

5 2/N101/2200 Revise wording of DLMS Note: Clarification. 
4

Z4 Owning Inventory Control Point 

DLMS Note: 

1. Use to identify the Routing Identifier of the supply source or 

applicable ICP/IMM as the originator of the shipment status. This 

includes shipment status prepared by the Distribution Depot on 

behalf of the ICP/IMM for ICP/IMM-directed shipments, and 

CCP/Consolidation shipment status. 

2. This is Use to identify the recipient for LRO Shipment Status. 

3. and Use to identify the recipient Fielding Command for Army 

Total Package Fielding shipments. 

 (5) Revise DLMS manual, Vol 2, Chapter 5, as shown in Enclosure 1. 

(6) Example transactions are provided at Enclosure 2. 

5. REASON FOR CHANGE: Distribution Depot Pearl Harbor, Hawaii (DDPH) is currently 

performing local deliver manifesting. This means after DSS makes the shipment and sends the 856S 

with passive RFID tags; DDPH may perform subsequent consolidation to bundle up multiple Material 

Release Orders (MROs) to local customers. They then put a passive RFID tag on that consolidation 

container. Passive visibility transactions created by tag readers (e.g. Globeranger) are transmitted to 

DAAS, but they do not marry up with the shipments (identified by the 856S) because the DSS 856S 

went out before the local delivery manifesting tag was applied. This change will identify the local 

delivery manifesting shipment status so that the tag read upon receipt (or other locations) can be used 

to identify the shipment.

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Purpose of change is to create an efficient automated process when local delivery 

manifesting applies and supports integration of passive RFID within logistics processes.

b. Disadvantages: N/A.

7. IMPACT: 

 a. DLMS Supplement 4030 856S, Shipment Status 

 b. Programming to support the unique CCP has already been implemented. There is minimal 

impact identified with expanding its use to other consolidation locations. 

c. The original requirement for the CCP shipment status was to post the information at DAAS for 

passive RFID visibility and provide the DLMS transaction to where a DLMS capable ship-to location 

is involved. If additional shipment status distribution is required, it must be identified separately by 

establishing Service-unique business rules for DAAS shipment status distribution.
 

Enclosure 1 - DLMS Procedures 

 C5.2.3.1. Preparation of Shipment Status. Shipment status shall be provided by the 

shipping activity or the source of supply for direct vendor delivery (contractor direct) or in response to 

a requisition follow-up. The Consolidation and Containerization Point (CCP) and other location

performing consolidation subsequent to issuance of shipment status may also provide shipment 

status for the purpose of identifying passive RFID.1

 Under DLMS, the shipment status will include 

enhanced data content and support item unique identification (IUID) and intransit visibility 

requirements as directed under DoD policy/procedures (DoD 4140.1-R), when available and pending 

full DLMS implementation/modernization.2 Shipment status shall be provided by the DoD shipping 

activity, the CCP, or by the supply source3 using DS 856S. Maintenance activities (organic and 

commercial) shall provide shipment notification to the receiving activity and other interested parties 

when material is shipped to the distribution depot, DRMO, or other designated receiving activity per 

source of supply/inventory control point guidance. This may be accomplished using either the DLMS 

Shipment Status, DS 856S, or the DLMS Advance Shipment Notice (ASN), DS 856, provided via 

Wide Area Work Flow-Receipt and Acceptance (WAWF-RA).4

 The DLMS Shipment Status shall 

include asset visibility content, such as IUID, and intransit visibility requirements, such as passive 

RFID and the transportation control number as directed under DoD policy/procedures (DoD 4140.1-

R). DLMS enhancements include, but are not limited to the following: 

 C5.2.3.1.1. Passive RFID for the shipment unit/case/pallet associated at the 

requisition document number level. The shipment status transaction may identify a hierarchy to clarify 

the relationship of passive tags within different shipment levels. 

 C5.2.3.1.2. For Unique Item Tracking (UIT) purposes, the IUID and/or serial 

number. Serial number without applicable IUID may only be used during MILS/DLMS transition and 

pending implementation of IUID capability. Additional UID information as identified in the DS 856S 

is optional. Refer to Chapter 19 for UIT guidance. 

 C5.2.3.1.3. Both the TCN and a secondary transportation number, such as the small 

package carrier number, when this is applicable.5

 C5.2.3.1.4. Identification of the carrier when other than United States Postal Service 

(USPS) by name and Standard Carrier Alpha Code (SCAC).6

 

1 Refer to ADC 257, DLMS Shipment Status Generated by the Consolidation and Containerization Point (CCP) 2

 DoD 4140.1-R guidance for passive RFID and IUID requirements is pending publication as of the date of this change. 

Interim guidance is available at http://www.acq.osd.mil/log/rfid/index.htm (RFID) and 

http://www.acq.osd.mil/dpap/pdi/uid/index.html(IUID). 3

 Direct vendor delivery shipment status using the 856S includes shipment status prepared by the DLA-sponsored Defense 

Planning and Management System (DPMS) application. 

4

 Business rules for use of the 856 for GFM or Property Transfer, including internal DoD transfers, are evolving. Refer to 

the Defense Procurement and Acquisition policy for UID available at url; http://www.acq.osd.mil/dpap/pdi/uid/index.html. 

Specific applicability and interoperability issues to be resolved by the UID Program Office and DUSD(L&MR)SCI. 

5

 Refer to ADC 223, DLMS Shipment Status Enhancements: Secondary Transportation Number, Initial Shipping Activity, 

Carrier Identification, and POE, approved for phased and staggered implementation. 6

 Refer to Footnote 6. 
2

 C5.2.3.1.5. Identification of the initial DoD shipping activity (origin) by DoDAAC.7

 C5.2.3.1.6. For OCONUS shipments made via the DTS, GBL/CBL, parcel post, and 

small package carrier shipments, specific identification of the POE or CCP. The shipment status shall 

specify air terminal, water terminal, or CCP by applicable qualifier code in the DS. (During 

MILS/DLMS transition, DAAS may substitute a generic terminal qualifier for shipment status 

transactions converted from MILS where the type of facility is unknown.)8

 C5.2.3.1.7. Under DLMS, the shipment status shall perpetuate data content as 

applicable: project code, the special requirements code (MILS RDD coded entries, e.g. 999), and 

priority designator.9

 C5.2.3.1.8. The transportation priority shall be included in all shipment status 

transactions as derived under DoD 4140.1-R guidance or other pertinent criteria.10

 C5.2.3.1.9. The shipment status may include the unit price (required for Distribution 

Standard System (DSS)-generated shipment status; otherwise optional).11

 C5.2.3.2. Shipment Status from the CCP12 or Other Locations Performing 

Consolidation.13 Shipment status will be provided by the CCP or other locations performing 

consolidation subsequent to the original issuance of shipment status, for the primary purpose of 

providing updated RFID information. This in turn supports intransit asset visibility and receipt 

processing. Other locations include distribution depots performing consolidation of local deliveries

resulting in passive RFID updates.

 C5.2.3.2.1. Preparation of the CCP/Consolidation Shipment Status

 C5.2.3.2.1.1. The CCP/consolidation shipment status will be identified by a 

unique code in the transaction and will include the information as described below. 

 C5.2.3.2.1.1.1 The Ship-To-Activity. this activity will be explicitly 

identified in the transaction. 

 C5.2.3.2.1.1.2 The CCP/consolidation shipment status will carry The 

Lead TCN. which This TCN may differ from that on the original shipment status. 

 C5.2.3.2.1.1.3 RFID Tag Value. When applicable, the transaction will 

contain multiple passive RFID tag values using a hierarchical structure. The original passive RFID 

will be repeated when it is available. Any additional tag values available to the CCP will also be 

provided. 

 

7

 Refer to Footnote 6. 

8

 Refer to Footnote 6. 

9

 Refer to ADC 242, Shipment Status DS 856S: Priority Designator (PD), Transportation Priority, Project Code, Special 

Requirements Code, approved for phased and staggered implementation. 10 Refer to Footnote 6. 

11 Refer to proposed addendum to ADC 242A, Inclusion of Unit Price on DLMS Shipment Status (DS 856S). 

12 Refer to Footnote 2. 

13 Refer to PDC 313. 
3

 C5.2.3.2.1.1.4 Transaction Originator. This will identify the Routing 

Identifier of the Inventory Control Point perpetuated from the original shipment status. 

 C5.2.3.2.1.1.5. Consolidation Activity. This will identify the DoDAAC of 

the location where the consolidation occurred, e.g. CCP or depot performing local delivery 

manifesting. 

 C5.2.3.2.1.1.6. The Shipment Date. identified This will be the 

CCP/consolidation point shipment date. 

 C5.2.3.2.1.1.7 The Mode of Shipment. This will be the mode shipped by 

the CCP/consolidation point. 

 C5.2.3.2.1.2. Shipment status information content may be repeated from the 

original shipment status when this information is available to the CCP, e.g., when the original shipper 

was a co-located distribution depot. Where the CCP does not have access to the original shipment 

status information is not available, the original data content will not be perpetuated and applicable 

data fields will not be populated. 

 C5.2.3.2.2. DAAS Distribution of CCP/Consolidation Shipment Status. DAAS will 

route the CCP/consolidation shipment status to the ship-to activity. Standard DAAS business rules for 

distribution of the shipment status to status recipients will not apply. In addition, DAAS will not 

distribute the CCP shipment status to Distribution Depot ship-to locations or Material Processing 

Center (MPC) locations supported by DSS. 

 C5.2.3.2.3. Use of the CCP/Consolidation Shipment Status by the Receiving 

Activity. 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 CCP mode of shipment and the CCP shipment date. New content on the 

CCP/consolidation shipment status should not be viewed as replacement values for a previously 

received shipment status matching on document number/suffix. Since there may not be a match on the 

previously identified TCN, the CCP/consolidation shipment status information must be handled in a 

way that does not impact quantity due or visibility of partial shipments which may not have been 

consolidated within the reconfigured shipment. 

 

Enclosure 2, Local Delivery Consolidation Example Transactions 

ISA*00* *00* *10*W62G2T *10*S36121 *080616*1432* *00403*000005566*0*P*¬~ 

GS*SH*W62G2T*S36121*20080616*1432*000005566*X*004030~ 

ST*856*0001~ 

BSN*00*ZZ*20080616*1432**AS~ 

HL*1**V~ 

N1*Z4**M4*SMS**FR~ 

HL*2**W~ 

LIN**FS*1630010099429~ 

SN1**10*EA~ 

TD5****LD~ 

REF*TN*FB529481638800~ 

REF*TG*FB529481638800XXX~ 

DTM*011*20080611~ 

N1*GP**M4*SGA**TO~ 

N1*SB**10*W62G2T~ 

N1*ST**10*FB5294~ 

LM*DF~ 

LQ*0*AS8~ 

LQ*BD*3~ 

LQ*37*SUU~ 

LQ*79*15~ 

HL*3**P~ 

REF*JH*2F0573632473254002FAE8BC~ 

HL*4*3*P~ 

REF*JH*2F1573632473254002FAE8BB~ 

SE*24*0001~ 

GE*1*000005566~ 

IEA*1*000005566~ 

 

ISA*00* *00* *10*W62G2T *10*S36121 *080616*1433* *00403*000005567*0*P*¬~ 

GS*SH*W62G2T*S36121*20080616*1433*000005567*X*004030~ 

ST*856*0001~ 

BSN*00*ZZ*20080616*1433**AS*061~ 

HL*1**V~ 

N1*Z4**M4*SMS**FR~ 

HL*2**W~ 

LIN**FS*1630010099429~ 

SN1**10*EA~ 

TD5****LD~ 

REF*TN*FB529481638800~ 

REF*TG*FB529481638800XXX~ 

DTM*011*20080611~ 

N1*GP**M4*SGA**TO~ 

N1*CS**10*W62G2T~ 

N1*ST**10*FB5294~ 

LM*DF~ 

LQ*0*AS8~ 

LQ*BD*3~ 

LQ*37*SUU~ 

LQ*79*15~ 

HL*3**P~ 

REF*JH*2F0573632473254002FAE8BD~ 

HL*4*3*P~ 

Shipper is DD Sharp 

Standard Shipment Status 

Consolidation Shipment Status 

Consolidator is DD Sharp 
2

REF*JH*2F0573632473254002FAE8BC~ 

HL*5*4*P~ 

REF*JH*2F1573632473254002FAE8BB~ 

SE*26*0001~ 

GE*1*000005567~ 

IEA*1*000005567~ 

 

ISA*00* *00* *10*W62G2T *10*S36121 *080616*1433* *00403*000005568*0*P*¬~ 

GS*SH*W62G2T*S36121*20080616*1433*000005568*X*004030~ 

ST*856*0001~ 

BSN*00*ZZ*20080616*1433**AS*061~ 

HL*1**V~ 

N1*Z4**M4*SMS**FR~ 

HL*2**W~ 

LIN**FS*1010123123123~ 

SN1**1*EA~ 

TD5****ED~ 

REF*TN*WT4J8S81634001~ 

REF*TG*WT4J8S81634001XXX~ 

DTM*011*20080611~ 

N1*GP**M4*SGA**TO~ 

N1*CS**10*W62N2A~ 

N1*ST**10*WT4J8S~ 

LM*DF~ 

LQ*0*AS8~ 

LQ*BD*1~ 

LQ*DF*S~ 

LQ*36*SUU~ 

LQ*79*02~ 

HL*3**P~ 

REF*JH*2F1573632473254001974428~ 

SE*23*0001~ 

GE*1*000005568~ 

IEA*1*000005568~ 

 

ISA*00* *00* *10*SW3144 *10*S36121 *080616*1434* *00403*000000204*0*P*¬~ 

GS*SH*SW3144*S36121*20080616*1434*000000204*X*004030~ 

ST*856*0001~ 

BSN*00*ZZ*20080616*1434**AS*061~ 

HL*1**V~ 

N1*Z4**M4*SMS**FR~ 

HL*2**W~ 

LIN**FS*8465000016482~ 

SN1**1*EA~ 

TD5****LD~ 

REF*TN*N221548163CME5~ 

REF*TG*N221548163CME5XXX~ 

REF*PA*7.85~ 

DTM*011*20080611~ 

N1*GP**M4*SGA**TO~ 

N1*CS**10*SW3144~ 

N1*ST**10*N22154~ 

LM*DF~ 

LQ*0*AS8~ 

LQ*BD*3~ 

LQ*79*09~ 

Consolidator is San Joaquin CCP 

Consolidator is DD Pearl Harbor 
3

HL*3**P~ 

REF*JH*2F0535733313434000000007~ 

HL*4*3*P~ 

REF*JH*2F0535733313434903DC5136~ 

HL*5*4*P~ 

REF*JH*2F1535733313434000000041~ 

SE*26*0001~ 

GE*1*000000204~ 

IEA*1*000000204~