DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060..6221 

April I7, 20I4 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

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

Revise DLMS 830D Demand Data Exchange (DDE) Projected Supply Plan 

Requirements to Clarify Data and Associated Procedures (Supply) 

The attached change to DLM 4000.25, Defense Logistics Management System, is 

approved for implementation. This change impacts Army and the Defense Logistics Agency 

(DLA), and is approved for staggered implementation. Army can implement this change in 

June 2014; DLA can implement immediately. The updated DLMS Implementation 

Convention will be posted to the Defense Logistics Management Standards Office Website 

www.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp within 10 days from the above date. 

Supply PRC members may direct questions to Ms. Mary Jane Johnson, (703) 767-0677; 

DSN 427-0677 or email: Mary.Jane.Johnson@dla.mil. Others must contact their Service or 

Agency designated Supply PRC representative available at 

www. dla.mil/j -6/ dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: ODASD(SCI) 

Director 

Defense Logistics Management 

Standards Office 
Attachment ADC 1105

Page 1 of 4

ATTACHMENT TO ADC 1105

Revise DLMS 830D Demand Data Exchange (DDE) Projected Supply Plan 

Requirements to Clarify Data and Associated Procedures (Supply)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Defense Logistics Management Standards Office (DLMSO), Mary Jane Johnson, 

DOD MILSTRAP Administrator, 703-767-0677, DN 427, email: mary.jane.johnson@dla.mil 

b. DLA:

(1) Technical POC: HQ DLA J343, 804-357-8727

(2) Functional POC: HQ DLA J343, 703-767-0138

2. FUNCTIONAL AREA: Primary Functional Area: Supply, DDE Projected Supply Plan

3. REFERENCE: DLM 4000.25, Defense Logistics Management System, Volume 2, linked at 

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp

4. APPROVED CHANGE(S): (Significant changes from Proposed DLMS Change (PDC) 1105

are highlighted in yellow throughout ADC)

a. Brief Overview of Change: Revise Defense Logistics Management Standards 

(DLMS) 830D implementation convention (IC) to clarify use of organization DOD activity 

address codes (DoDAAC), the FST segment forecast timing qualifiers, and the SDQ segment. 

DLA is also revising the procedures to recommend that DDE projected supply plans have 60 

month plan periods, with zero filling those months with no plan data.

b. Background: During Army implementation of DLMS 830D with DLA, it was 

determined that the explanation for the DoDAAC fields and the FST segment, FST03 

forecast timing qualifiers were subject to interpretation and additional clarification was 

needed.

c. Describe Approved Change to DLMS 830D in Detail: 

(1) DLA J3 revisions:

(a) revised DLMS 830D to more clearly identify which organization 

DoDAACs are used in the transaction, to include that the requisitioner (Sold-to) DoDAAC is 

the DoDAAC of the requisitioning (customer) organization. The requisitioner (Sold-to) 

DoDAAC is found in the first six positions of a requisition document number. The requisitioner

(Sold-to) DoDAAC could be the same as the Ship-to DoDAAC.

(b) revised DLM 4000.25 procedures to recommend that DDE projected 

supply plans have 60 month plan periods, with zero filling those months with no plan.
Attachment, ADC 1105

Page 2 of 4

(2) DLMSO revisions:

(a) revised DLMS 830D Loop ID FST, to clarify the requirements 

associated with providing the projected supply plan quantities. Data must be provided for every 

data bucket (e.g., monthly buckets) within the projected supply plan, including those buckets with 

zero quantity forecast/projection. This is necessary under the existing DLMS 830D requirements,

where the FST04 date is the same as the beginning segment BFR06 date (i.e., the projected supply 

plan period start date). In the absence of providing dates in chronological sequence with zero 

quantity projections included, there is no way to determine the start dates for the individual 

quantity buckets provided by the FST Loop.

(b) revised DLMS 830D SDQ segment to provide specific guidance to satisfy 

mandatory X12 syntax requirements for clarification and consistency with other DLMS ICs, and to

reaffirm that unit of issue is a valid requirement not being streamlined.

d. Revisions to DLM 4000.25 Manuals:

(1) Revise DLM 4000.25, Volume 2, Chapter 2, paragraph C2.3.2.2. as follows:

C2.3.2.2. DDE Projected Supply Plan. DDE supply planning activities shall shall prepare 

the DDE projected supply plan for each item = Demand Forecast Unit (e.g., NIIN, Ship to DoD 

activity address code (DoDAAC), and requisitioner (Sold To) DoDAAC) for which the customer 

wishes to collaborate with DLA. Each transaction set must include the projected supply plan period 

beginning date and the projected supply plan period ending date. The projected supply plan period 

span can be as little short as 12 months or as much long as 60 months; however, DLA recommends 

that DDE projected supply plans provide for 60 months in the plan period, zero filling those 

months with no plan data.

(2) Revise DLMS 830D IC as shown at the enclosure. 

e. Alternatives: None identified.

5. REASON FOR CHANGE: During a recent Army DLMS 830D implementation effort with 

DLA, the DLMS 830D organization DoDAACs and the FST03 forecast timing qualifiers were 

subject to interpretation. This change clarifies those requirements for all DOD Components using 

DLMS 830D DDE Projected Supply Plan. This change also further emphasizes the existing

requirement for the FST04 date and clarifies the SDQ segment, as was documented in PDC 1105 at

the DLMS 830D Change Table (shown at the enclosure).

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Clarifies intent of transaction data.

b. Disadvantages: None identified.

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

DEVELOPMENT: DLMS implementation of the DDE Projected Supply Plan requires 

implementation of the DLMS 830D IC.
Attachment, ADC 1105

Page 3 of 4

8. ESTIMATED IMPLEMENTATION TARGET: This change is effective immediately for 

Air Force, Navy, and Marine Corps, which have not yet implemented DLMS 830D. In response 

to PDC 1105, DOD Components that have implemented DLMS 830D were to provide impact of 

this change, and projected implementation date, in accordance with Impact paragraph 10.c. This 

change is approved for staggered implementation for DLA and Army as follows:

a. DLA: DLA and DLA Transaction Services have advised that they can implement 

this change immediately.

b. Army: The next Army Supply Plan (ASP) submission will include these changes; 

Army anticipates this to be during the June 2014 timeframe. 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

10. IMPACT:

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: Revises DLMS notes in the 830D IC to clarify 

organization DoDAACs, the intent of the forecast timing qualifiers, and use of the SDQ segment.

c. Automated Information Systems (AIS): 

(1) Army and DLA: May require revision to Army and DLA AIS to implement 

DoDAACs and FST03 Forecast qualifiers as clarified. Refer to paragraph 8 for implementation 

date.

(2) Air Force, Navy and Marine Corps: No impact. In response to PDC 1105, 

Air Force, Navy, and Marine Corps noted they had not yet implemented DLMS 830D.

d. DLA Transaction Services: Minor mapping changes required.

e. Non-DLM 4000.25 Series Publications: None identified

11. PDC 1105 Response Table:

Component Response to PDC 1105 Disposition

Army Army concurs with Comment:

RE: "In many cases the submitter, requisitioner (Sold-to), 

and Ship-to DoDAAC will be the same in the transaction". 

Comment: For Army, submitter would never be the same 

as the other two. Should read as: "In many cases the 

requisitioner (Sold-to), and Ship-to DoDAAC will be the 

same in the transaction."

Concur. Change made 

as requested. See the 

enclosure, 830D 

Change Table, row 6.

DLA also concurred 

with this change by 

DLA email 3/14/2014.
Attachment, ADC 1105

Page 4 of 4

Component Response to PDC 1105 Disposition

Air Force Concur.

AFMC satisfies this requirement with a DDE flat file, 

however, we are not in DLMS compliance

Noted.

Marine Corps Marine Corps concurs with PDC as written.

Marine Corps has not implemented DLMS 830D. 

Revisions have no impact on Marine Corps plans for 

future implementation of DLMS 830D, DDE Projected 

Supply plan.

Noted. 

Navy Navy concurs with PDC as written.

Navy has not implemented DLMS 830D/DDE.

Noted. 

DLA Concur without comment. Noted. 

USTRANSCOM Abstains Noted. 
Enclosure, ADC 1105

Page 1 of 3

ENCLOSURE TO ADC 1105

# Location DLMS 830D Change Table 

(Change identified by bold red text or double strikethrough)

Reason

1 DLMS 

Introductory 

notes

Revise DLMS introductory note 2:

2. The Demand Data Exchange Projected Supply Plan transaction is a 

DLMS enhancement. There is no corresponding DLSS transaction; 

however this transaction encompasses functionality of non-DLSS DLA 

legacy Document Identifier Code (DIC) CDD. See introductory DLMS 

note 3a. DLMS IC 830D replaces IC 830R, version 4030 only, combined 

SPR/DDE, in its entirety.”

Administrative updates to identify 

DIC CDD is a DLA legacy format 

and to delete reference to IC which 

was eliminated over 5 years ago.

2 DLMS 

Introductory 

notes

Revise DLMS introductory note 4 to add change:

- ADC 1105, Revise DLMS 830D Demand Data Exchange (DDE) 

Projected Supply Plan Requirements to Clarify Data and Associated 

Procedures

To show changes for the IC

3 2/LIN01/

0100

Revise DLMS Note for ‘C’:

DLMS Note: C - Cancellation of previously submitted DDE Projected 

Supply Plan transaction. Use indicates cancellation of the entire open 

DDE transaction for the NIIN cited in LIN02/03. This equates to DLA’s 

Document Identifier Code legacy DIC CDD format with an ‘R’ in rp 952.

Administrative update.

4 2/REF/1400

2/REF01/

1400

Revise segment level DLMS Note:

Must use to identify the transaction document number associated with the 

DDE Projected Supply Plan.

Revise DLMS Note for qualifier TN:

TN Transaction Number

DLMS Note: Use to identify the transaction Number (also known as the

document number).

Administrative update for 

consistency with wording in other 

DLMS ICs.

5 2/N101/

3200

Revise DLMS note for code LW:

LW Customer

DLMS Note: 

Use to identify the customer requisitioner (Sold-to) DoDAAC for DDE 

Projected Supply Plan transactions. This is the DoDAAC of the 

requisitioning (customer) organization. The requisitioner (Sold-to) 

DoDAAC is found in the first six positions of a requisition document 

number. In many cases the requisitioner (Sold-to) DoDAAC and the 

Ship-to DoDAAC will be the same in the transaction.

To clarify requirement.

6 2/N101/

3200

Revise DLMS note for code ST:

ST Ship To

DLMS Note:

Must use to identify the Ship-to DoDAAC. when different from the 

customer. In many cases the submitter, requisitioner (Sold-to) DoDAAC

and Ship-to DoDAAC will be the same in the transaction.

Removing the restriction which 

only allowed entry of the Ship-to 

DoDAAC when different from the 

N101 qualifier LW DoDAAC and 

assumed no entry meant the Ship-to 

was the same as the requisitioner 

DoDAAC. Provides clarity.

Revised to delete submitter from 

note at left, per Army comment that 

Army submitter DoDAAC would 

never be the same as requisitioner 

DoDAAC or Ship–to DoDAAC.
Enclosure, ADC 1105

Page 2 of 3

# Location DLMS 830D Change Table 

(Change identified by bold red text or double strikethrough)

Reason

7 2/FST03/

4100

Revise DLMS notes for codes A, M, Q, and S as follows:

A Annually (Calendar Year)

DLMS Note: Use to submit up to 5 years (5 annual periods) of projected supply

plan data. (e.g., for a 5 year projection, 5 annual periods will be submitted, to 

include zero entries for plan years with no data; for a 4 year projection, 4

annual periods will be submitted, etc.). The beginning segment defines the 

projected supply plan period start and end dates (BFR06 and BFR07 

respectively). The annual buckets must be provided in chronological sequence 

in the transaction and zero quantity projections must be included. Use of 

“Annually” is a DLMS enhancement. See introductory DLMS note 3a. 

M Monthly

DLMS Note:

1. Use to submit up to 5 years (60 months) of projected supply plan data. (e.g., 

for a 5 year projection, 60 monthly buckets will be submitted, to include zero 

entries for plan months with no data; for a 3 year projection, 36 monthly 

buckets will be submitted, to include zero entries, etc.). The beginning segment 

defines the projected supply plan period start and end dates (BFR06 and 

BFR07 respectively). The monthly buckets must be provided in chronological 

sequence in the transaction and zero quantity projections must be included. 

2. While DDE projected supply plans can be as short as 12 months, DLA 

recommends that DDE projected supply plans have 60 month plan periods, 

zero filling months with no plan. 

Q Quarterly (Calendar Quarters)

DLMS Note: Use to submit up to 5 years (20 quarters) of projected supply plan

data. (e.g., for a 5 year projection, 20 quarters will be submitted, to include zero 

entries for plan quarters with no data; for a 4 year projection, 16 quarters will 

be submitted, etc.). The beginning segment defines the projected supply plan 

period start and end dates (BFR06 and BFR07 respectively). The quarterly 

buckets must be provided in chronological sequence in the transaction and zero 

quantity projections must be included. Use of “Quarterly” is a DLMS 

enhancement. See introductory DLMS note 3a.

S Semi-Annually (Calendar Year) 

DLMS Note: Use to submit up to 5 years (10 semi-annual periods) of projected 

supply plan data (e.g., for a 5 year projection, 10 semi-annual periods will be 

submitted, to include zero entries for semi-annual plan periods with no plan 

data; for a 3 year projection, 6 semi-annual periods will be submitted, etc.). 

The beginning segment defines the projected supply plan period start and end 

dates (BFR06 and BFR07 respectively). The semi-annual buckets must be 

provided in chronological sequence in the transaction and zero quantity 

projections must be included. Use of “Semi-Annually” is a DLMS 

enhancement. See introductory DLMS note 3a.

To clarify current 

requirement.

Data must be provided in 

chronological sequence for 

every data bucket within the 

projected supply plan, 

including those buckets with 

zero quantity 

forecast/projection. 

Under the DLMS 830D 

current requirements, FST04 

is the same as the beginning 

segment BFR06 date, which 

is the projected supply plan 

period start date. In the 

absence of providing 

monthly buckets in 

chronological sequence, with 

zero quantity projections 

included, there is no way to 

determine the start dates for 

the individual quantity 

buckets provided by FST 

Loop.
Enclosure, ADC 1105

Page 3 of 3

# Location DLMS 830D Change Table 

(Change identified by bold red text or double strikethrough)

Reason

8 2/FST04/

4100

Revise DLMS note 2:

DLMS Note: 

1. Must use to identify the start date for which material support should be 

available for the NIIN cited in LIN02/03 for the bucket (weekly, monthly, 

etc) identified in FST03. This date corresponds to the 1/BFR06/0200 start 

date.

2. Use for other than a date that corresponds to the BFR06 date is a DLMS 

enhancement and therefore requires a proposed DLMS change (PDC)

before use. See introductory DLMS note 3a, which requires that 

Components must coordinate requirements and business rules for DLMS 

enhancements with the Defense Logistics Management Standards Office 

prior to use.

Further emphasis of the stated need 

for Components to coordinate 

proposed business rules with 

DLMSO if they are interested in 

using FST04 for other than 

mirroring the BFR06 date, as 

currently required by the IC.

9 2/SDQ01/

4200

Add new DLMS note 1, renumber current DLMS note 1 as note 2, and 

delete current DLMS note 2:

Unit or Basis for Measurement Code

DLMS Note: 

1. Use to identify the unit of issue for the materiel.

1. 2. DLMS users see the Unit of Issue and Purchase Unit Conversion 

Table for applicable codes.

2. Future Streamlined data; see introductory DLMS note 3c.

The DOD MILSTRAP 

Administrator is not aware of any 

plans to streamline the unit of 

measure out of the DLMS 830D, 

and believes the streamline note 

was included in error.

10 2/SDQ03/

4200

Revise DLMS Note:

Identification Code

Description: Code identifying a party or other code

DLMS Note: Use any acceptable value "ZZ" for this data element to 

satisfy mandatory X12 syntax requirements.

Providing specific guidance to 

satisfy mandatory X12 syntax 

requirements for clarification and 

consistency with other DLMS ICs. 

11 2/SDQ04/

4200

Revise DLMS Note:

Quantity

Description: Numeric value of quantity

DLMS Note: Use any acceptable value “0” (zero) for this data element

to satisfy mandatory X12 syntax requirements.

Providing specific guidance to 

satisfy mandatory X12 syntax 

requirements for clarification and 

consistency with other DLMS ICs.