DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

April 04, 2018

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

1279, Material Processing Center (MPC) Transshipment Status 

(MILSTRIP/Supply)

The attached change to DLM 4000.25, Defense Logistics Management Standards (DLMS), 

is approved Implementation is authorized 30 days from the approval date above. The Enterprise 

Business Standards Office will post the updated DLMS Implementation Convention (IC) to the 

Web at http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/,

within 10 days from the above date.

Addressees may direct questions to Mr. Eric Flanagan, MILSTRIP Administrator e-mail:

DLMS_MILSTRIP@dla.mil. Others must contact their designated Supply PRC representative 

available at http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/.

HEIDI M. DAVEREDE

Director

Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)
Attachment, ADC 1279

Page 1

Attachment to ADC 1279

Material Processing Center (MPC) Transshipment Status

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Commander, U.S. Pacific Fleet, N41: 

http://www.cpf.navy.mil/contact/

b. Functional POC: Mr. Tom Tichy, 808-474-8032 or e-mail: Tom.Tichy@navy.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Sustainment

3. REFERENCES:

a. Approved DLMS Change (ADC) 229, Material Processing Center (MPC) Material 

Receipt and Delivery Supply Status, March 6, 2007

b. ADC 242B, Inclusion of Additional Customers under MPC Shipment Status 

Distribution Rules, July 8, 2009

c. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP), 

Appendix 3.10.

d. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, 

Chapter 5

e. NAVSUP P-485, Naval Supply Systems Command Publication, Operational Forces 

Supply Procedures

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change establishes procedures for the DLA 

Distribution Standard System (DSS) to provide supply status transactions (DLMS 870S/legacy 

MILSTRIP Document Identifier Code (DIC) AE8 when Material Processing Centers (MPCs)

transship materiel to other MPCs. This supply status allows status recipients to track materiel 

and measure logistics pipeline performance. Furthermore, this change adopts a Navy-unique 

process for inter-Navy-DLA Distribution use under DLMS.

b. Background:

(1) ADC 229 (Reference 3.a.) approved MPC requirements and established 

procedures for DSS to provide supply status transactions upon MPC receipt or delivery of 
Attachment, ADC 1279

Page 2

materiel. ADC 229 established Status Codes NL (received) and NW (delivered) to support 

materiel tracking and performance metrics.

(2) ADC 242B (Reference 3.b.) expanded the MPC process to activities whose 

DoDAAC begins with M (Marines) or Z (Coast Guard).

(3) DLA Distribution-operated MPCs support the Navy by working with the 

ships to identify materiel sortation requirements. Once onboard, the materiel is delivered to the 

storerooms or other areas to be placed on the shelf. This takes the time-consuming sortation 

burden off the crewmembers.

(4) DLA Distribution uses DSS to scan or manually process documents to show

that materiel has arrived at the MPC. DSS also provides Status Code NL to the customer. This 

supply status provides systemic notification that the materiel has arrived at the MPC.

(5) The MPC delivers the materiel to the ship after performing the sortation and 

consolidation, based on pre-determined delivery schedules or a call from the ship to deliver the 

materiel. The MPC creates the manifest in DSS with a date and time and delivers it to the ship 

along with the materiel. After the ship crew signs the manifest, the MPC staff returns and closes 

out the manifest by entering the actual date and time, and proof of delivery name in DSS. DSS 

then provides a supply status with Status Code NW to the customer for each document number 

that was on the manifest(s). 

(6) The Navy uses supply status transactions with Status Codes NL and NW for 

performance measurement and materiel visibility.

(7) N-series status codes are assigned for intra-Navy transactions with the 

exception of those authorized for MPC procedures under MILSTRIP/DLMS.

c. Approved Change in Detail:

(1) This change requires the MPC to provide supply status when transshipping 

materiel to another MPC. An MPC initiates the transshipment process when a ship departs the 

operational area of the MPC before the materiel arrives. The MPC performs transshipments in 

accordance with the Cargo Routing Identifier File (CRIF). In support of this requirement, this 

ADC approves the following:

(a) Adds new Supply Status Code NY to provide notification that an 

MPC transshipped materiel to another MPC (see paragraph 4.d.).

(b) Revises the DLMS Supply Status transaction to identify the date that 

an MPC transships materiel to another MPC and updates the notes to clarify mapping for the 

second destination MPC (see Enclosure 1).

(c) Revises the legacy MILSTRIP Supply Status transaction mapping.

(2) This ADC updates the list of MPCs in Reference 3.d. (see Enclosure 2).
Attachment, ADC 1279

Page 3

(3) Distribution centers at co-located MPCs also provide a DLMS 856S 

Shipment Status for the transshipment under existing business rules. The shipment status 

identifies the ship-to DoDAAC of the co-located distribution center when applicable.

(4) Enclosure 3 contains examples of DLMS and legacy formatted supply status 

transactions.

d. Revisions to DLM 4000.25 Manuals:

(1) Revise MILSTRIP Appendix 2.16, Supply Status to include the following 

code in the Requisition Transaction Status Codes section:

Code Explanation

NY Item transshipped by the receiving MPC to another destination MPC

(2) Revise DLM 4000.25-1, Appendix 3.10, Supply Status (Issues from Stock) 

footnotes as follows:

2 When used by the material processing center (MPC) to notify the Navy customer that materiel has 

arrived (NL Status), or been delivered (NW or Navy-unique BA Status), or transshipped (NY Status), rp 

4-6 shall will identify the MPC that originated the transaction.

6 When used by the MPC to notify the Navy customer that materiel has arrived (NL Status) or been 

delivered (NW Status), rp 67-69 shall will repeat the identification of the MPC that originated the 

transaction in rp 4-6. When used for transshipment notification (NY Status), rp 67-69 will identify the 

MCP to which materiel is transshipped. 

7 When used by the MPC, this will be the date associated with the materiel arrival (NL Status), delivery 

(NW or Navy-unique BA Status), or transshipment (NY Status).

(3) Revise DLM 4000.25, Defense Logistics Management System, Volume 2, 

Chapter 5, Supply Status. Renumber paragraphs as appropriate due to identified revisions.

“C5.1.2.1.4. Material Processing Center (MPC) Supply Status

C5.1.2.1.4.1. The MPC will provide Status Code NL to notify the Navy 

ship/customer that materiel has arrived at the MPC for sortation and temporary storage pending 

delivery to the customer.

C5.1.2.1.4.2. The MPC will provide Status Code NW to provide 

systematic notification materiel has been delivered from the MPC to the Navy ship.

C5.1.2.1.4.3. The receiving MPC will provide Status Code NY to provide 

systematic notification materiel has been transshipped from the receiving MPC to another 

destination MPC.”

(Intervening text not shown)
Attachment, ADC 1279

Page 4

“C5.1.6.5.1.1. Material Processing Center (MPC) Shipment Status. 

DAAS will also provide a copy of shipment status for materiel to be delivered to any customer 

supported by a MPC operated by DLA Distribution at the co-located DLA Distribution Depot

Center receiving site. In order to accomplish this, DAAS will maintain a table of DoDAACs 

associated with a particular copy of DSS as identified by DLA Distribution that the copy of DSS 

MPC supports. DLA Distribution, in coordination with the Service, will provide updates to 

DAAS as needed. When DAAS processes the DLMS 856S/AS8 and the ship-to DoDAAC 

begins with N, R, V, Z, M, or as otherwise identified, DAAS will match the ship-to DoDAAC to 

the MPC table. When an appropriate DSS DoDAAC for MPC support is identified, shipment 

status will be forwarded to the DSS for establishment of pre-positioned materiel receipt (due-in) 

record at the applicable MPC.

C5.1.6.5.1.2. MPCs receiving shipment status are located at the 

distribution depot center locations identified in Table C5.T3.

(4) See Enclosure 2 for revisions to DLM 4000.25, Defense Logistics 

Management System, Volume 2, Chapter 5, Table C5.T3. 

e. Approved Transaction Flow:

(1) An MPC in receipt of materiel uses DSS to scan the Issue Release/Receipt 

Document (IRRD) (DD Form 1348-1A or DD Form 1348-2). This generates NL status (Materiel

Received at MPC).

(2) The MPC closes the manifest and provides Status Code NW (Materiel

Delivered) after delivering materiel to the customer.

(3) The MPC provides Status Code NY (Materiel Transshipped to Another MPC) 

when transshipping materiel to another MPC for ships that have departed the local area. The 

MPC also generates a DLMS 856S Shipment Status.

(4) The destination MPC scans the DD 1348-1 and provides Status Code NL 

(Materiel Received at MPC) upon receiving the transshipped materiel.

(5) The MPC closes the manifest and provides Status Code NW (Materiel 

Delivered) after delivering the materiel to the customer.

f. Alternatives: None identified.

5. REASON FOR CHANGE: DSS does not currently provide supply status transactions for 

materiel transshipped from one MPC to another. Therefore, the Navy cannot differentiate 

materiel that an MPC delivers locally versus materiel that it transships to another MPC. To 

resolve this issue, this change requires the transshipping MPC to provide Status Code NY.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The new status code will improve the ability to track MPC-delivered 

materiel and Logistics Response Time (LRT) performance. Status Code NY will allow the Navy 
Attachment, ADC 1279

Page 5

to differentiate between a transshipment and a local delivery. Furthermore, this enhancement 

improves the accuracy of materiel tracking and the accountability of shipboard receipt 

processing.

b. Disadvantages: None identified.

7. ADDITIONAL COMMENTS TO CONSIDER:

a. Materiel Accountability: The MPC function is outside of the DODM 4140.01, DOD 

Materiel Management procedures. Those business rules require the storage activity to maintain 

materiel accountability for assets in its custody. DLMS procedures require the storage activity to 

maintain the property accountability record for all materiel in storage. At a minimum, storage 

activities are responsible for materiel custody, care, receipt, storage, and issue. The MPC 

function bypasses these requirements, despite DLA Distribution being responsible for care of 

materiel in temporary storage.

b. Materiel Receipt Acknowledgement (MRA):

(1) The Enterprise Business Standards Office (EBSO) is concerned that delaying

the posting of the accountable receipt for MPC-held materiel also delays providing the MRA. 

The MRA is a DOD requirement for materiel shipped from wholesale supply sources and is

important for timely payment of vendors. 

(2) MRA procedures authorize Navy ships to respond to MRA follow-ups by 

indicating an extended in-transit time for materiel awaiting delivery at an MPC. Implementing

this proposal will enhance Navy visibility of the cause for long delays resulting from

transshipment subsequent to an MPC receiving materiel.

c. Acceptance Report under Invoicing, Receipt, Acceptance, and Property Transfer 

(iRAPT): EBSO notes that delaying receipt processing of the materiel held or transshipped by 

the MPC may also delay the customer’s submission of the acceptance report. The customer must 

submit an acceptance report when a vendor ships materiel free-on-board (FOB) destination. The 

source of supply uses the acceptance report to process the vendor’s invoice. Delaying vendor 

payment may cause interest penalties to accrue for the source of supply.

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: The Pipeline Measurement Process 

Review Committee should determine the potential to integrate the new MPC transshipment 

status for use in Logistics Response Time metrics.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Implementation is 

authorized 30 days from ADC approval.

a. DLA Distribution should provide an estimated implementation timeline for DSS in the 

DLA response to this ADC.

b. The Navy developed and tested logic to accept Status Code NY in anticipation of this 

change. Configuring Navy systems to accept the new status code will have minimal impact.
Attachment, ADC 1279

Page 6

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: This change will reduce the amount of materiel

lost in shipment due to lack of visibility. However, the Navy cannot provide an estimated 

savings at this time.

11. IMPACT:

a. New DLMS Data Elements: Add (2/DTM01/240 qualifier 514 –Transferred: The 

date an MPC transships materiel to another MPC.

b. Changes to DLMS Data Elements: Add new value Supply Status Code NY to 

2/LQ01/330 qualifier 81 – Status Code.

c. Automated Information Systems (AIS):

(1) This change requires changes to DSS to prepare transshipment supply status 

and identify the destination MPC when transshipping materiel.

(2) This change requires Navy systems to recognize the mapping variation used 

to identify the transshipping MPC and the new destination MPC identified in the supply status.

(3) Owners of asset visibility applications (e.g., Integrated Development 

Environment/Global Transportation Network Convergence (IGC)) must direct updates to 

recognize new status.

d. Defense Automatic Addressing System (DAAS): Update DAAS maps for Supply 

Status NY to properly map the transshipment date and the second MPC (2/N101/90 Code WD,

Storage Facility at Destination).

e. Non-DLM 4000.25 Series Publications:

(4) MPC procedures will require updates.

(5) The Navy must update NAVSUP P-485 and the MILSTRIP/MILSTRAP 

Desk Guide to reflect Supply Status NY.

(6) DLA must update the DLA Customer Handbook to reflect Supply Status NY.
Attachment, ADC 1279

Page 7 

12. PROPOSED DLMS CHANGE (PDC) 1279 RESPONSE/COMMENT RESOLUTION:

Originator Response/Comment Disposition

1. DLA Concur without Comment Noted.

2. Navy Concur without Comment Noted.

3. Air Force Concur without Comment Noted.

4. US Army

5. USMC Concur without Comment Noted.

6. DAAS Concur without Comment Noted.

7. USTRANSCOM Abstains Noted.

No Response
Enclosure 1, ADC 1279

Page 1

Enclosure 1, DLMS Implementation Convention (IC) Revisions

Item 

#

Location 870S Supply Status Revision Reason

1. DLMS 

Introductory 

Notes

Add ADC 1279 to Introductory DLMS Note 5:

- ADC 1279, Material Processing Center (MPC) 

Transshipment Status

To identify DLMS 

changes included in the

DLMS IC.

2. 2/N101/90 Add DLMS note to existing Code WD:

WD Storage Facility at Destination

DLMS Note:

1. Use to identify the Material Processing Center 

(MPC).

2. When used with Status Code NY, this will 

identify the MPC to which materiel is 

transshipped. Identify the shipping MPC as the 

transaction originator. Refer to ADC 1279.

Clarification for new 

requirement.

3. 2/DTM01/240 Add new Code and DLMS notes:

050 Received

DLMS Note: Use with Status Code NL to identify 

the date materiel is received at the Material

Processing Center (MPC) for temporary storage 

pending delivery to the Navy vessel.

035 Delivered

DLMS Note: Use with Status Code NW to 

identify the date materiel is delivered from the 

Material Processing Center (MPC) to the Navy 

vessel (signature date).

514 Transferred

DLMS Note: Use with Status Code NY to 

identify the date that a Material Processing 

Center (MPC) transships materiel to another

MPC.

Existing Codes 050 

(Received) and 035 

(Delivered) are included 

for reference.

Allows for identification 

of the dates provided on 

the MPC status 

transactions.
Enclosure 2, ADC 1279

Page 1

Enclosure 2, DDC MPC List

Revise the DLA Distribution Center and Co-Located MPC Table in DLM 4000.25, Defense 

Logistics Management System, Volume 2, Chapter 5:

Table C5.T3. DLA Distribution Depots Centers and Co-Located 

Material Processing Centers

DEPOT DISTRIBUTION 

CENTER WITH CO-LOCATED 

MPC

DEPOT

DISTRIBUTION 

CENTER DODAAC

MPC ROUTING 

IDENTIFIER CODE

Norfolk SW3117 PSJ

Jacksonville SW3122 PSU

San Diego SW3218 PSK

Puget SW3216 PSN

Yokosuka SW3142 PSL

Sasebo SW3143 PSM

Guam SW3147 SCN

Pearl Harbor SW3144 PSY

Sigonella SW3170 SNH

Bahrain SW3183 SNN

Everett, Washington State SW3237 SNY

Little Creek, Norfolk, VA SW3187 SEF

D&S Pier, Norfolk, VA SW3186 SEE

Subron 11, Point Loma, CA SW3236 SNX

Groton, Ct SW3188 SEX

Djibouti SW311M S5W

Rota, Spain SW310J SC1

Salalah, Oman SW3156 S1C
Enclosure 3, ADC 1279

Page 1

Enclosure 3, Sample Supply Status Transactions

Sample Supply Status Transactions as Converted by DAAS for Legacy Recipient:

AE1PSK 5962010752660 EA00002R205506276Y201 A 03284NLPSK62840000000

AE1PSK 5962010752660 EA00002R205506276Y201 A 03287NWPSK62870000000

AE1PSK 5962010752660 EA00002R205506276Y202 A 03290NYPSK62900000000

Sample DSS-originated DLMS 870S Supply Status Transactions:

ISA*00* *00* *10*W25G1U *10*S36121

*070306*1712*U*00401*000000001*0*P*.~

GS*RS*W31G1Z*S36121*20070306*1712*000000001*X*004010~

ST*870*0001~

BSR*4*CO*Z*20070306***1712****00~ N1*SB**M4*SDF**FR~

HL*1**W~

DTM*097*20070306~

REF*TN*W31G3H6103H047~

N1*WD**M4*PSJ~

LM*DF~ LQ*0*AE8~

LQ*COG*9L~

LQ*A9*N69262~

LQ*SMI*BL~

LQ*DF*S~

PO1**3*EA***FS*6920002234919~

ISR*UR~

DTM*050*20070306*1615~

LM*DF~ LQ*83*A~

LQ*81*NL~

SE*19*0001~

GE*1*000000001~

IEA*1*000000001~

ISA*00* *00* *10*W25G1U *10*S36121

*070306*1712*U*00401*000000002*0*P*.~

GS*RS*W31G1Z*S36121*20070306*1712*000000002*X*004010~

ST*870*0001~

BSR*4*CO*Z*20070306***1712****00~

N1*SB**M4*SDF**FR~

HL*1**W~ DTM*097*20070306~

REF*TN*W31G3H6103H047~

N1*WD**M4*PSJ~

LM*DF~ LQ*0*AE8~

LQ*COG*9L

LQ*A9*N69262~

LQ*SMI*BL~

LQ*DF*S~

PO1**3*EA***FS*6920002234919~

ISR*UR~

DTM*035*20070306*1616~

LM*DF~ LQ*83*A~

LQ*81*NW~

SE*19*0001~

GE*1*000000002~
Enclosure 3, ADC 1279

Page 2

IEA*1*000000002~

ISA*00* *00* *10*W25G1U *10*S36121

*070306*1712*U*00401*000000002*0*P*.~

GS*RS*W31G1Z*S36121*20070306*1712*000000002*X*004010~

ST*870*0001~

BSR*4*CO*Z*20070306***1712****00~

N1*SB**M4*SDF**FR~

HL*1**W~

DTM*097*20070306~

REF*TN*W31G3H6103H047~

N1*WD**M4*PSJ~

LM*DF~

LQ*0*AE8~

LQ*COG*9L

LQ*A9*N69262~

LQ*SMI*BL~

LQ*DF*S~

PO1**3*EA***FS*6920002234919~

ISR*UR~

DTM*514*20070306*1617~

LM*DF~ LQ*83*A~

LQ*81*NY~

SE*19*0001~

GE*1*000000003~

IEA*1*000000003~