DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

October 11, 2019

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

1267A, Administrative Update DLMS 830D to Include IMM Data from FLIS 

During DAAS Processing for Gross Demand Plan (GDP) (Supply)

We are forwarding the attached approved administrative change to DLM 4000.25, 

Defense Logistics Management Standards, for implementation. This change is to be 

implemented no later than December 31, 2019. Request DOD Components provide projected 

implementation date.

Addressees may direct questions to Mr. Rafael Gonzalez, e-mail: 

Rafael.Gonzalez@dla.mil. Others may direct questions to their Service or Agency designated 

Supply PRC representative available at 

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

 DREXEL K. ROSS

 Acting Director

 Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD(Logistics)
Attachment, ADC 1267A

Page 1

Attachment to ADC 1267A

Administrative Update DLMS 830D to Include IMM Data from 

FLIS During DAAS Processing for Gross Demand Plan (GDP)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Rafael Gonzalez, 

EBSO

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Demand Data Exchange (DDE) Projected 

Gross Demand Plan (GDP), Army Supply Plan (ASP) 

c. Logistics and Transaction Changes (Check All That Apply): 

 Category  Category  Category

Billing Physical Inventory Contract Admin

Discrepancies / Deficiencies MILSTRAP DoDAAD

Serialization MILSTRIP MAPAD

Small Arms/Light Weapons MRA LMARS

X Demand Planning Disposition X DLM Publications

GFP DOD BRAC X DAAS Map

3. REFERENCES:

a. ADC 1267, Approved Defense Logistics Management Standards (DLMS) Change 

(ADC) 1267, Revise DLMS 830D to Accommodate Gross Demand Plan (GDP) for 

Implementation by All DOD Components, June 4, 2018

b. DLM 4000.25, Defense Logistics Management Standards, Volume 2, Supply 

Standards and Procedures, June 13, 2012

c. DOD Directive 8190.01E, Defense Logistics Management Standards (DLMS), 

January 9, 2015

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This administrative change provides additional details to 

the procedures documented under ADC 1267 (Reference 3.a.) and clarifies that DAAS will use 

the Integrated Materiel Manager (IMM) identified in the Federal Logistics Information System 

(FLIS) to determine and populate the source of supply when the generating service uses RIC-TO 

SGA as the source of the supply.
Attachment, ADC 1267A

Page 2

b. Background: ADC 1267 revised procedures to authorize the use of the DLMS 830D 

Demand Data Exchange (DDE) Implementation Convention (IC) as the primary exchange 

method for reporting GDP between DOD Components. This change specifies that the DAAS 

match of the DLMS 830D national item identification number (NIIN) is with the FLIS IMM data 

to determine and populate the 830D with the appropriate source of supply RIC (replacing RICTO SGA) before forwarding the DLMS 830D transaction to the appropriate source of supply.

c. APPROVED Change in Detail: This administrative change clarifies the use of the 

IMM as the source of supply under the GDP procedures documented under (reference 3.b.) 

Chapter 2 Special Program Requirements and Demand Data Exchange Projected Supply Plan. It 

revises DLM 4000.25, DLMS, Volume 2, Chapter 2 as shown in the Enclosure.

d. Approved Transaction Flow:

(1) Upon submission, DAAS evaluates the NIIN (830D 2/LIN02/0100 Code 

ZZ in the transaction and populates the IMM from FLIS as the source of supply when the 

originator cites RIC-TO SGA. DAAS will then create a DLMS 830D transaction based on the 

original request. The forecasted requirement may contain only one NIIN or local stock 

number (LSN) in the same transaction. DAAS will route all forecasted requirements with 

local stock numbers (LSNs) (i.e., alpha characters in the NIIN field) to DLA RIC-TO SMS. 

When the NIIN is not valid, DAAS will reply to the originator with a DLMS 824R Reject 

Advice transaction, using Reject Advice Code DB (Rejected. NIIN Missing/Invalid).

(2) The remaining process will follow the flow as approved in ADC 1267.

e. Alternative: None

5. REASON FOR CHANGE: Upon further review of the changes documented in ADC 1267, 

DAAS recommended further explanation of what source of supply to populate when the 

originator uses SGA as the RIC-TO. As a result, DLA submitted a request to clarify the 

narrative in the DLM 4000.25 Vol 2 Chapter 2. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: None identified.

b. Disadvantages: None identified.

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT:

a. DLMS implementation of the DDE Projected Supply Plan requires implementation of 

the DLMS 830D Implementation Convention.

b. ADC 1267 processes are implemented by the Components and the DLMS 830D will be 

mapped through DAAS.
Attachment, ADC 1267A

Page 3

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: NLT December 31, 2019.

Request DOD Components provide projected implementation date.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

10. IMPACT:

a. New/Change DLMS Data Elements: None 

b. Automated Information Systems (AIS): None identified. 

c. Defense Automatic Addressing System (DAAS): DAAS will need to adjust any 

system changes made as a result of ADC 1267 to indicate the IMM as the source of supply when 

applicable. 

d. Non-DLM 4000.25 Series Publications: DOD Components may need to update 

internal guidance to comply with this DLMS change.
Enclosure, ADC 1267A

Page 1

ENCLOSURE TO ADC 1267A

Revise DLM 4000.25, Volume 2 Supply Standards and Procedures Chapter 2, Special 

Program Requirements and Demand Data Exchange Projected Supply Plan as follows:

Administrative update throughout the chapter to replace “shall” with “will” or “must” as 

appropriate.

(Preceding text not shown) 

C2.3.2.5. Validation of NIIN. After successful submission, DAAS will evaluate the NIIN

(830D 2/LIN02-03/0100 Code ZZ) in the transaction with RIC-TO SGA and use FLIS data to 

determine and populate the appropriate IMM and source of supply. DAAS will route all transactions 

with LSN (alpha characters in the NIIN field) to RIC-TO SMS. If DAAS is unable to validate the

NIIN, DAAS will reject the transaction and report to the originator with appropriate reject advice code 

(MILSTRAP DLMS, Volume 2, Appendix 2.8 Reject Advice Codes) via DLMS 824R Reject. After 

the evaluation is complete, DAAS will create a DLMS 830D transaction by source of supply based on 

the original transaction and route it to the applicable source of supply RIC. DAAS will transmit an 

image of each DLMS 830D for which RIC SMS was not the source of supply to DLA RIC-TO SMS in 

order to maintain full visibility of the initial forecasted request.