DEFENSE LOGISTICS AGENCY

HEADQUARTERS

8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

IN REPLY

REFER TODLMSO

November 15, 2007

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 257, DLMS

Shipment Status Generated by the Consolidation and Containerization Point (CCP)

(Supply) (Staffed as PDC 275)

The attached change to DOD 4000.25-M, DLMS, is approved for implementation. The

Distribution Standard System (DSS) implemented these new business rules, as of November 14,2007,

modifying the CCP Shipment Status previously provided. DAASC will block conversion of the CCP

shipment status to MILSTRIP customers; standard Distribution Depot-generated shipment status will

continue to be converted to MILS TRIP. DAASC will update new routing distribution rules per this

ADC no later than November 30, 2007. The updated DLMS Supplement will be posted to the

Defense Logistics Management Standards Office (DLMSO) Web site http://wvvw.dla.mil/i6/dlmso/elihrarv/TransFormats/formats.asp within 5 days from the above date for implementation

planning. DLMSO will submit concurrently any necessary revisions to the governing Federal

Implementation Convention.

Addressees may direct questions to the DLMSO points of contact, Ms. Ellen Hilert, Chair,

Supply Process Review Committee, 703-767-0676, DSN: 427-0676, or e-mail: ellen.hilert(a).dla.mil

and/or Mr. Robert Hammond, 703-767-2117, DSN: 427-2117 or e-mail: robert.hammond(a)dla.mil.

Others must contact their Component designated representative.

~~~P~PP ~-:[LA'?»~

Director ,

Defense Logistics Management

Standards Office

Attachment

cc:

DUSD(L&MR)SCI

Federal Recycling Program 0. Printed on Recycled Paper
2

ADC 257 

DLMS Shipment Status Generated by the CCP 

1. ORIGINATING SERVICE/AGENCY: 

 Technical: 

 Service, Agency or Committee: Defense Logistics Agency, J6N 

 Phone No: 717-770-6105/DSN: 771-6105 

 

 Functional: 

 Service, Agency or Committee: Defense Logistics Agency, J-37 

 Phone No: 703-767-1538/DSN: 427-1538 

2. FUNCTIONAL AREA: 

 a. Major Functional Area: Supply 

 b. Secondary Functional Process: CCP Consolidation/Passive RFID 

3. BACKGROUND: 

a. INTENT OF THE TRANSACTION: This change documents the preparation of the DLMS 

Shipment Status by the CCP using the Distribution Standard System (DSS) in order to provide passive 

RFID information to the customer. This will normally be triggered by the reconfiguration of the 

original shipment by the CCP. It may also occur when the shipper did not provide passive RFID or 

when the original passive RFID tag was damaged. This change provides for a revision of the 

transaction format to clearly define this usage and distinguish it from shipment status transactions 

generated by the DSS on behalf of the source of supply. It provides new business rules for the 

distribution and use the CCP shipment status. Yellow and green highlights represent significant 

changes from the original staffing (green for the most recent changes). 

b. SCENARIO FOR WHICH THE TRANSACTION IS USED: The material is assigned 

passive RFID by the CCP rather than by the shipping depot, when the depot tag is unreadable, or when 

reconfiguration of the shipment results in additional levels of passive RFID. Therefore, a new 

shipment status transaction is necessary to communicate the passive RFID value to support visibility 

and receiving activity processing. 

c. CURRENT DATA ELEMENTS IN USE TODAY: This is a new requirement and will be 

used to modify the currently transmitted CCP Shipment Status. There is no prior agreement that the 

CCP will provide shipment status. 

d. CURRENT DOCUMENT IDENTIFIER CODES and DLMS IC’s IN USE TODAY: This 

change is not applicable to the MILSTRIP Shipment Status (Document Identifier AS_). It applies only 

to the 4030 856S, Shipment Status. 

4. PROPOSED CHANGE(S): 

a. Description of Change: Include a unique code when the 856S is generated by CCP and 

ensure identification of the ship-to activity. Eliminate extra/unnecessary distribution of the CCP 

shipment status.
3

b. Procedures: 

(1) CCP Shipment Status Preparation. The CCP will generate a shipment status transaction 

using the 856S format to provide passive RFID information to the receiving activity. 

(a) The CCP 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). 

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

original shipment status. 

(d) 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. 

 (e) The shipment date identified will be the CCP shipment date. 

 (f) The mode of shipment will be the mode shipped by the CCP. 

 (g) Shipment status information content will 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, 

the original data content will not be perpetuated and applicable data fields will not be populated. 

(2) DAAS Distribution/Business Rules. DAAS will route the CCP 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, DAASC will suppress sending the CCP 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 CCP shipment status information available via WebVLIPS. 

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

(e) The CCP shipment status may not be employed in determining depot processing time 

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

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

content on the CCP 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 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) DLMS Supplement. Modify the DLMS transaction to allow a status reason code to 

identify the shipment status generated by a CCP. 

Location Revision to 

4030 856S, Shipment Status 

Reason 

DLMS 

Introductory 

Note: 

Add ADC 257 to DLMS Introductory note 3. 

- ADC 257, DLMS Shipment Status Generated by the CCP 

To identify DLMS 

changes included in the 

DS. 

1/BSN07/0200 Insert new Status Reason Code (qualifier 061) and the 

following DLMS note: 

061 Consolidation, Extension, Modification (CEM) 

DLMS Note: Use to identify that shipment status is 

provided by the Consolidation and Containerization Point 

(CCP) 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 purpose. 

 (2) Revise DLMS manual, Vol 2, Chapter 5, as shown in Enclosure 1 (text based upon 

PDC/ADCs applicable to this portion of the DLMS procedures): 

c. Alternatives: Alternative mapping may be available, but no alternative to this process is 

identified. 

5. REASON FOR CHANGE: Without the distinguishing code, the CCP shipment status may 

appear as a duplicate or as additional quantity shipped, when in fact it is conveying added information 

at a different point in the distribution process. The distinguishing code may be used by DAAS to 

prevent conversion to MILSTRIP AS_ formats which drops the RFID content, and could easily cause 

confusion in the MILS environment (since a new lead TCN may be assigned making the shipment 

status appear to be subsequent shipment of the same quantity). The new code allows DLMS receiving 

activities to properly identify and process the transaction.
5

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: This change provides clarification of source and purpose of the transaction. It is 

provided so that the receiver may have the passive RFID tag number pre-lodged in their receiving 

system. It supports passive RFID implementation. MILS recipients with DLMS “Bridge” capability 

may receive this information via DLMS shipment status. The information provided will populate the 

DAAS Passive RFID table for use in intransit visibility. As CCP passive RFID tagging is expanded 

beyond the current limited scope, this new capability will greatly enhance visibility and receipt 

processing.

b. Disadvantages: May require modification to DLMS receiving systems to recognize two 

sources of shipment status to ensure proper interpretation of the second updated shipment status.

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE: If the receiving system 

doesn't program to interpret the new code, the second transaction may overlay the first. If this occurs 

there is a potential for some loss of original content. If the second CCP shipment status transaction 

rejects as a duplicate, passive RFID content will be lost, but there will be no other negative 

consequence. This new process will be applied primarily to Distribution Depot shipments, but may 

also apply to contractor direct shipments received at the CCP for onward movement via DTS. 

8. ADDITIONAL COMMENTS TO CONSIDER: 

 a. MILSTRIP Shipment Status is not to be provided by DAAS resulting from conversion of CCP 

shipment status. DLMS-capable receiving applications which have not yet adopted this DLMS change 

should review impact of receiving a second updated shipment status and verify that receipt of the new 

CCP shipment status will not cause any unanticipated problems. 

 b. DAASC must block distribution of the CCP shipment status to ship-to locations which are 

Distribution Depots (DD) and DSS supported locations. DAASC maintains a table of DDs and may 

use this to identify ship-to locations to be blocked. There is also a table of Navy DoDAACs related to 

DSS sites that is used to send copies of shipment status for the MPC process. DAASC will need to 

exclude the CCP shipment status from going through this logic. 

9. NOTE ANY REGULATIONS OR GUIDANCE: A DLMS manual revision is provided as an 

enclosure. 

10. NOTE ADDITIONAL FUNCTIONAL REQUIREMENTS: The DoD Supply Process Review 

Committee (PRC) was advised (during the 07-2 meeting) that the generation of the CCP shipment 

status is already underway, but without the distinguishing code identified in this change. Rather than 

request that the CCP shipment status be terminated (risking decreased passive RFID processing 

capability at the receiving site), it was agreed that the business rules should be further clarified and 

coordinated for documentation in the DLMS manual. 

11. ALTERNATIVES: During the original concept development within the DDC/DSS, and again 

during the Supply PRC 07-2 meeting, alternatives for satisfying this requirement were discussed, to 

include using the 856A, Receipt/ Shipment-Consolidation/Due-In Notice. It was agreed that the 856S, 

which is designed to flow to the receiving activity, would be a suitable fit for the current requirement. 

However, consideration should be given to transitioning to the 856A which is currently designed to 

flow to/between the CCP and transportation nodes, but provides better mapping of hierarchical levels 

of shipment consolidation. USTRANSCOM will further investigate potentially better solutions for 

future use, while this process (which is already implemented for a specific target community using 
6

passive RFID, although lacking clear identification and procedures as recognized by this ADC) may be 

used to fill the existing void. 

12. ESTIMATED TIME LINE: This change is requested for immediate implementation.

13. IMPACT: This approved change is to be expedited to eliminate confusion for MILS applications 

due to the continued conversion of the already implemented CCP shipment status. 

a. This change impacts DLMS-capable receiving applications and those in the process of planning 

for DLMS migration. DLMS-capable receiving applications should be modified to recognize the new 

CCP identifier and properly append new date if desired; Pending system modification, Components 

must verify the impact on processing of shipment status when a CCP shipment status is received (e.g., 

will it reject or overlay existing status). 

 b. This change impacts the DAAS Passive RFID (R) Table, the Global Transportation Network 

(GTN), and other applications maintaining a historical database and query capability associated with 

RFID, so that additional data content may be saved and displayed appropriately. 
7

Enclosure 1 – DLMS Manual Procedures 

Note: Revisions directly associated with this PDC are highlighted in yellow. An administrative 

revision to this portion of the guidance is highlighted in green. The following paragraphs also contain 

administrative updates to clarify procedures which are not highlighted. 

C5.2.1.2. Shipment Status. Shipment status informs the receiving activity and designated status 

recipients of the basic shipment information to include the actual shipping dates (such as the date 

released to the carrier) and/or shipment delay notification. It serves as an interface with transportation 

for shipment tracing under DoD 4500.9-M. 

Intervening text not shown 

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 deliver (contractor direct) or in response to a requisition 

follow-up. The Consolidation and Containerization Point (CCP) 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 Item Unique Identification (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. 

 

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/UID

(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/UID/. Specific 

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

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

carrier number, when this is applicable5

. 

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

by Standard Carrier Alpha Code (SCAC)6

. 

 C5.2.3.1.5 Identification of the initial DOD shipping activity (origin) by DODAAC7

. 

 C5.2.3.1.6 For Outside Continental United States (OCONUS) shipments made via Defense 

Transportation System (DTS), GBL/CBL, parcel post, and small package carrier shipments, specific 

identification of the Port of Embarkation (POE) or Consolidation and Containerization Point (CCP). 

The shipment status will 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. 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 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 DSS-generated 

shipment status; otherwise optional).11 

C5.2.3.2. Shipment Status from the Consolidation and Containerization Point (CCP).

12 The CCP 

will generate a shipment status transaction using the 856S format to provide passive RFID 

information to the receiving activity. 

C5.2.3.2.1 Preparation of the CCP Shipment Status

 C5.2.3.2.1.1 The CCP shipment status will be identified by a unique code in the 

transaction. 

 C5.2.3.2.1.2 The ship-to activity will be explicitly identified in the transaction. 

 C5.2.3.2.1.3 The CCP shipment status will carry the lead TCN which may differ from 

that on the original shipment status. 

 C5.2.3.2.1.4 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. 

 

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 5. 

7

 Refer to Footnote 5. 

8

 Refer to Footnote 5. 

9

 Refer to ADC 242, Shipment Status DS 856S: Priority Designator (PD), Transportation Priority (TP), 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 1. 
9

 C5.2.3.2.1.5 The shipment date identified will be the CCP shipment date. 

 C5.2.3.2.1.6 The mode of shipment will be the mode shipped by the CCP. 

 C5.2.3.2.1.7 Shipment status information content will 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, 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 Shipment Status. DAAS will route the CCP 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 

the Distribution Standard System (DSS). 

C5.2.3.2.2. Use of the CCP 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 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 

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.