DEFENSE LOGISTICS AGENCY

HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

June 04, 2018 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

1161B, Modify DLMS 536L Logistics Reassignment Management Data to Identify 

the Procurement Instrument Identifier (PIID) Associated with a Base Contract 

Number in Logistics Reassignment Contract History Data Transactions 

(Supply/Contract Administration) 

We are forwarding the attached approved change to DLM 4000.25, Defense Logistics 

Management Standards, for implementation. Implementation must be completed by December 

2019 for DLMS compliance; refer to the attachment for specific target dates. The Enterprise 

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

Defense Logistics Management Standards Program Office Web at 

www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/, within 10 days 

from the above date. 

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

Administration, e-mail: tonja.daniels-carter@dla.mil. All others must contact their Component 

designated Supply PRC representative at

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

HEIDI M. DAVEREDE

Director 

Enterprise Business Standards Office

Attachment

As stated

cc:

ODASD (SCI) 

ODASD DPAP (PDI)
Attachment, ADC 1161B

Page 1

Attachment to ADC 1161B

Modify DLMS 536L Logistics Reassignment Management Data to Identify the 

Procurement Instrument Identifier (PIID)Associated with a Base Contract 

Number in Logistics Reassignment Contract History Data Transactions 

(Supply/Contract Administration)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Functional POC: Shawn Meads, HQ DLA J341, Order Fulfillment Order 

Management, e-mail: Shawn.Meads@dla.mil

b. Technical POC: Tonja Daniels-Carter, Enterprise Business Standards Office 

(EBSO/DLMS Program Office), e-mail: Tonja.Daniels-Carter@dla.mil.

2. FUNCTIONAL AREA: 

a. Primary Functional Area: Logistics Reassignment Contract History Data

b. Secondary Functional Process: Contract Administration

3. REFERENCES:

a. Defense Logistics Manual (DLM) 4000.25, Defense Logistics Management Standards 

(DLMS), Volume 2, Chapter 9, Logistics Reassignment

b. Approved DLMS Change 1161A, Update Uniform Procurement Instrument Identifier 

(PIID) Numbering System in the Federal/DLMS Implementation Conventions and DLMS 

Manuals, February 23, 2017 

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change updates the DLMS 536L Logistics 

Reassignment Management Data to enable identification of the PIID associated with the base 

contract number on Logistics Reassignment – Contract History Data transactions (Reference 

3.a.). This will enable a capability removed during the transition to PIID numbering under ADC 

1161A (Reference 3.b.). Inclusion of the base contract number and the PIID call/order 

number(s) will help associate both data elements for a complete contract history for an item 

being logistically reassigned.

b. Background:

(1) ADC 1161A (Reference 3.b.) updates DLMS procedures to accommodate the 

PIID numbering system. This was a mandated change required by recent changes to the FAR 

and DFARS. Under that change, the DOD PIID and PIID call/order are structured as unique 13-

position identification numbers distinguished by the type of instrument identified in the ninth

position. The letter F or M in the 9th position designates a PIID call/order. As initially 
Attachment, ADC 1161B

Page 2

established in ADC 1161A, either the PIID or the PIID for the call/order are provided in the 

536L transaction, but not both.

(2) To provide a complete history of the contracts on the 536L Logistics 

Reassignment – Contract History Data (2/HL03/10. Code IB – Contract loop) (legacy Document 

Identifier Code (DIC) DLW functionality) transaction, the losing item manager (LIM) needs to 

provide the gaining item manager (GIM) with both the base contract (Agreement) which was 

formerly the procurement instrument identification number (PIIN) and the call/order number 

(Order).

(3) Part of the new PIID process established a Reference PIID to represent the 

base contract between the purchasing organization and the vendor, and established a call/order 

PIID to be used when a specific order pursuant to the base contract is required. While either the 

Reference PIID or the call/order PIID can be used to look up item and order information, the 

logistics reassignment process seeks to provide the GIM with a comprehensive history of an 

item's prior procurement actions. 

c. Approved Change in Detail: Update the DLMS 536L Implementation Convention 

(IC) to permit identifying both the PIID for the call/order associated with a base contract, and the 

PIID for the base contract for logistics reassignment transaction history transactions for PIID 

compliant contracts.

d. Updates to DLM 4000.25: Revise DLMS 536L IC as shown in the enclosure. 

e. Approved Transaction Flow: Standard Logistics Reassignment transaction flows 

apply. 

f. Alternatives: None identified.

5. REASON FOR CHANGES: 

a. The call/order PIID and the Reference PIID share a similar contract format. Putting 

both pieces of data into the same X12 element will cause confusion among the Component 

systems, especially during the PIIN-PIID transition period. To facilitate a smoother data 

exchange, separate X12 elements in the Logistics Reassignment – Transaction History 

transaction will allow clear identification of the base contract (Reference) PIID and call/order 

PIID. This will reduce the possibility of errors in the data exchanges between the LIM and the 

GIM.

b. Associating the call/order PIID with the PIID for a base contract will allow the LIM to 

provide the complete contract history for an item being logistically reassigned.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Aligns the functionality in DLMS with the legacy Military Standard 

Transaction Reporting and Accountability Procedures (MILSTRAP) DIC DLW transaction 

content.
Attachment, ADC 1161B

Page 3

b. Disadvantages: None 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: 

a. DLA implemented this change in October 2017.

b. Components must implement by December 2019.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available. 

9. IMPACT:

a. New DLMS Data Elements: None identified.

b. Changes to DLMS Data Elements: None identified. 

c. Automated Information Systems (AIS): Revise DLA Enterprise Business Systems 

(EBS) and Component systems to accommodate this change. DLA and Component systems 

must accept (or generate, as applicable) the PIID for the call/order associated with the PIID for a 

base contract when using the logistics reassignment, contract history transaction.

d. DAAS: Update DAAS maps for revised DLMS 536L content.

e. Non-DLM 4000.25 Series Publications: Process revisions may require updates to 

internal operating procedures and other published guidance.

10. PROPOSED DLMS CHANGE (PDC) 1161B STAFFING RESPONSE/COMMENT 

RESOLUTION

Originator Response/Comment Disposition

1. Army No Response Received

2. Navy Concur Noted

3. Air Force No Response Received

4. Marine Corps Concur Noted.

5. DLA Concur Noted. Implemented October 2017

6. DSCA Concur Noted

7. USTRANSCOM Concur Noted.
Enclosure ADC 1161B

Page 1

Enclosure DLMS Implementation Convention (IC) Revisions

# Location Change Table for 

536L Logistics Reassignment Management Data

Reason

1. DLMS 

Introductory 

Note

Add ADC 1161B to DLMS Introductory notes: 

- ADC 1161B, Modify DLMS 536L Logistics Reassignment 

Management Data to Identify the Procurement Instrument 

Identifier (PIID)Associated with a Base Contract Number in 

Logistics Reassignment Contract History Data Transactions

(Supply/Contract Administration)

To identify DLMS 

changes included in 

the implementation 

convention.

2. Throughout 

this DLMS IC

Change ADC 1161 to ADC 1161A in all IC Notes unless noted as 

relevant to ADC 1161B. 

Administrative update

3. 2/CS01/030 Add new note 2 and renumber existing note:

Contract Number

DLMS Note: 1. Must use with the 2/HL/010 contract loop to 

identify the procurement instrument identifier (PIID). When 

procurement is authorized under a PIID call/order number (F in 9th 

position), provide the value in the PIID field. Refer to ADC 1161A.

2. Use only with Logistics Reassignment Contract History Data 

Transaction to provide the PIID of the base contract number. In 

CS06, provide the PIID of the call/order associated with the base 

contract. Refer to ADC 1161B.

23. CS01 is optional to accommodate DLSS to DLMS conversion. 

The 536L is intended to accommodate all MILSTRAP DI Codes 

DLS through DLX transaction data for a given NSN and review 

period, in a single 536L transaction. CS01 would be a “must use” in 

this situation. However during DLSS to DLMS conversion some 

systems may be converting each individual MILSTRAP transaction 

to individual 536L transactions, in which case CS01 may not 

always be required.

To provide a complete 

history of the contracts 

on the (Logistics 

Reassignment -

Contract History 

Data), legacy DLW 

transaction 

information, the 

Losing Item Manager 

(LIM) needs to 

provide the Gaining 

Item Manager (GIM) 

with both the 

Agreement (formerly 

the PIIN) and the 

Order (formerly the 

CALL

4. 2/CS03/030 Release Number

DLMS Note: Use in the 2/HL/010 contract loop to identify the sixposition Supplementary PIID when applicable. Refer to ADC 

1161A.

No Change;

Provided for context

only. 

5. 2/CS06/030 Open CS06 and add DLMS Note. 

Purchase Order Number

DLMS Note: Use in the 2/HL/010 contract loop, only with 

Logistics Reassignment Contract History Data Transaction to 

provide the PIID of the call order associated with the base 

contract identified in CS01. Refer to ADC 1161B.

Same Reason as 

CS01