1 of 12 

ADC 278 

Attachment 

ATTACHMENT TO ADC 278 

Establish New DLMS Supplement (DS) 830D, Version 4030, for Demand Data 

Exchange (DDE) Projected Supply Plan in Place of DS 830R, Version 4030, Special 

Program Requirements (SPR)/DDE Forecast (Supply) (Staffed as PDC 297) 

1. Originator: 

 a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

 b. Originator: Mary Jane Johnson, DLMSO, DOD MILSTRAP Administrator, (703) 767-0677, 

DSN, 427-0677, e-mail: Mary.Jane.Johnson@dla.mil

2. FUNCTIONAL AREA: Supply (ERP Planning and Collaboration Subsystem). 

3. REFERENCES: 

a. DLMSO Memorandum, June 24, 2008, subject: Approved DLMS Change (ADC) 287, 

Revision to DLMS 870L, SPR/LASE Status and Corresponding DLMS Manual Procedures; 

Administrative Update to DLMS 830R, SPR (Supply/MILSTRAP) (available at: 

http://www.dla.mil/j-6/dlmso/eLibrary/Changes/approved3.asp) 

b. DLMSO Memorandum, January 6, 2005, subject: Approved DLMS Change (ADC) 139, 

Revision to DS 830R to Accommodate Demand Data Exchange (Transmitting Forecasts of 

Recurring and Non-Recurring Demand Data) (Supply/DLMS) (available at: 

http://www.dla.mil/j-6/dlmso/eLibrary/Changes/approved.asp) 

c. Enterprise Business Systems (EBS) Demand Data Exchange Customer Collaboration 

(DDE/CC) via Digital Data Network (DDN) Job Aid, November 29, 2007. 

4. REQUESTED CHANGE: 

 a. Title: Establish New DLMS Supplement (DS) 830D, Version 4030, for Demand Data 

Exchange (DDE) Projected Supply Plan, in Place of DS 830R, Version 4030, Special Program 

Requirements (SPR)/ DDE Forecast.

b. Description of Change: 

(1) This change proposes establishment of a distinct DS for DDE, rather than 

combining the DDE transaction with the DLMS 830R SPR transaction. 

(2) A change incorporated into this ADC based on DLA comment to PDC 297, is 

that the use of the term “DDE Forecast” has been revised to “DDE Projected Supply Plan”. 

DLA noted that there has been a lot of discussion amongst DLA and the Services about the 

differences between a 'forecast' and a 'Supply Plan', and in response to that discussion a shift has 

been made to refer to the DDE as a ‘projected supply plan' vs. a forecast. 
2 of 12 

ADC 278 

Attachment 

c. Publications/Procedures: 

(1) DELETE existing DS 830R, VERSION 4030, combined SPR/DDE, from DLMS. 

(2) RETAIN existing DS 830R, VERSON 4010, SPR only, for use with SPRs. 

(3) ESTABLISH new DS 830D (version 4030), for Demand Data Exchange (DDE) Projected 

Supply Plan, as shown in Enclosure 1. The “DDE projected supply plan” is also referred to as “DDE” 

throughout this ADC. Data content for the DDE function in DS 830D (version 4030) is the same as that 

provided in DS 830R (version 4030) with the exception of select data such as that in the ST segment 

(Transaction Set Header), BFR Beginning Segment, optional use of a PER segment as a DLMS 

enhancement, and other changes as shown in the table below. Data which was specific to SPR in DS 

830R was eliminated from DS 830D. DDE data differences between 830R, version 4030, and DS 830D 

are shown below. This table does not reflect the exclusion of SPR data from the transaction. The 

exclusion of SPR data unrelated to DDE is understood for DS 830D. DS 830D revisions which differ 

from PDC 297 are identified by highlighted text in the Change Table below:

Item # Location CHANGE TABLE 

DS 830D CHANGE from DDE data portrayed 

in DS 830R (version 4030) 

Reason 

1. DS Title Change DS 830D title from “Demand Data 

Exchange Forecast” to “Demand Data Exchange 

(DDE) Projected Supply Plan” 

To eliminate use of “forecast” 

with DDE as noted in DLA PDC 

297 comment at paragraph 7 

below (comment # 6). 

2. Federal 

Introductory 

Note 

Revise Federal note 1 to read:

Organizations use this transaction set to transmit 

forecasts Demand Data Exchange (DDE) Projected 

Supply Plan for recurring and non-recurring 

demand data. 

To eliminate use of “forecast” 

with DDE as noted in DLA PDC 

297 comment at paragraph 7 

below (comment # 6). 

3. DLMS

Introductory 

notes 1, 2, and 

3.a 

Revise DLMS introductory notes 1 and 2 as follows: 

DLMS Note: 

1. Use a single occurrence of this transaction set to 

transmit Demand Data Exchange DDE Projected 

Supply Plan transactions to one or more Inventory 

Control Points (ICPs)/Integrated Material 

Managers (IMMs). At this time, DDE Projected 

Supply Plans are only submitted to the Defense 

Logistics Agency (DLA) ICP/IMM.”

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 Document Identifier (DI) code CDD. See 

introductory DLMS note 3.a. DLMS Supplement 

(DS) 830D replaces DS 830R, version 4030 only, 

combined SPR/DDE, in its entirety.” 

To note that only the DLA 

ICP/IMM has programmed to 

accept DDE at this time. See 

DLMSO PDC 297 comment at 

paragraph 7 (comment # 7). 

To note that DS 830D replaces the 

DS 830R-version 4030 SPR/DDE 

transaction. 

To eliminate use of “forecast” 

with DDE and replace it with 

‘projected supply plan’ as noted in 

DLA PDC 297 comment at 

paragraph 7 below (comment # 6). 
3 of 12 

ADC 278 

Attachment 

Item # Location CHANGE TABLE 

DS 830D CHANGE from DDE data portrayed 

in DS 830R (version 4030) 

Reason 

DLMS Intro 

notes con’t... 

3.a. Data associated with a DLMS enhancement 

which may not be received or understood by the 

recipient's automated processing system. 

Components must coordinate requirements and 

business rules with DLMSO prior to use. 

Administrative update to 

complete DLMS enhancement note 

consistent with other DS. 

4. DLMS 

Introductory 

Note 4 

Added ADC 278.

- ADC 278, Establish New DS 830D, Version 

4030, for Demand Data Exchange (DDE)

Projected Supply Plan, in Place of DS 830R, 

Version 4030, Special Program Requirements 

(SPR)/DDE Forecast (Supply) 

To identify DLMS changes 

included in the DS 

5. 1/ST03/0100 Revise DLMS note: 

DLMS Note: Use to indicate this transmission uses 

the 830D Federal Implementation Convention (IC) 

and 830D DLMS Supplement (DS). Enter the 

DLMS Supplement: 004030F830D0DA00 

To reflect DS 830D vice 830R. 

6. 1/BFR/0200 Delete segment level DLMS note:

DLMS enhancement; see DLMS supplement

note3a.

Administrative update. DLMS 

enhancement note unnecessary at 

BFR segment. 

7 1/BFR04/0200 Replace qualifier ZZ with qualifier PR as follows: 

ZZ Mutually Defined

DLMS Note: Use to indicate requirements data 

reflecting Demand Data Exchange for forecasts of 

recurring and nonrecurring demands.

A data maintenance action was approved in version 

5030. The approved code/name is "RD -Recurring 

Demand".

PR Planned Requirement Based 

DLMS Note: Use to indicate that data reflect DDE 

Projected Supply Plan requirements. 

Use of ‘PR’ is more appropriate for 

DDE than either ‘ZZ- Mutually 

Defined’ or ‘RD-Recurring 

Demand’ (approved in version 

5030), and is consistent with DS 

830R and DS 830W use of BFR04 

qualifier ‘PR’. 

See DMSO PDC 297 comment at 

paragraph 7 below (comment # 11). 

8 1/BFR06/0200 Revise the Federal note:

Federal Note: Must use to identify the projected 

supply plan period start date for which all identified 

material support should be available. This date 

represents the outside start date for all table 2 

iterations. 

To replace use of the word 

“forecast” with projected supply 

plan as noted in DLA PDC 297 

comment at paragraph 7 below 

(comment # 6). 

9 1/BFR07/0200 Revise the Federal note:

Federal Note: Must use to identify the projected 

supply plan period end date for which all identified 

material support should be available. This date 

represents the outside end date for all table 2 

iterations. 

To replace use of the word 

“forecast” with projected supply 

plan as noted in DLA PDC 297 

comment at paragraph 7 below 

(comment # 6). 
4 of 12 

ADC 278 

Attachment 

# Location CHANGE TABLE 

DS 830D CHANGE from DDE data portrayed 

in 830R (version 4030) 

Reason 

10 1/BFR12/0200 Add NEW Planning Schedule Type Code AACustomized Ordering Forecast with DLMS note:

AA Customized Ordering Forecast 

DLMS Note: Must use to indicate the transaction 

is a Demand Data Exchange Forecast Projected 

Supply Plan.

To reflect a new Planning Schedule 

Type Code for DDE Projected 

Supply Plan. 

As background: 

830D (4030) DDE is BFR12 

Planning Schedule Type Code AACustomized Ordering Forecast 

830R (4010) SPR is BFR12 

Planning Schedule Type Code XARequirement Forecast. 

830W (4010) WMR (War Materiel 

Requirements) is BFR12 Planning 

Schedule Type Code XF- War 

Reserve Forecast 

11 1/BFR13/0200 Add Federal and DLMS Note to beginning segment 

BFR13 Action Code:

Federal Note: Use any code. 

DLMS Note: For DLMS use there is no 

requirement for an action code at this time. 

Reserved for future DLMS use.

DS 830R, BFR13 used Action Code 

‘OT-Other Unlisted Action’ to 

identify when exception data (PWK 

segment) was being provided to 

associate SPR exception data with 

MILSTRAP SPR DI Code 

functionality. 

For 830D DDE, DLMSO 

recommends against using an action 

code to say that free text is 

provided. When free text is 

provided, the optional PWK 

segment will simply be used. 

Action code left open should it be 

needed in the future. 

12 2/LIN01/0100 Revise DLMS note for ‘C-Cancellation’ and ‘HDDE forecast submission’:

DLMS Note: C - Cancellation of previously 

submitted DDE Forecast 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 CDD format with an ‘R’ in rp 952.

H - DDE Forecast Projected Supply Plan 

transaction submission for the NIIN cited in 

LIN02/03.

To clarify that the DDE cancellation 

or submission is for a specific NIIN 

cited in the LIN segment at 

LIN02/03. 

Also shows that use of ‘CCancellation” is the DLMS 

equivalent of the DLA DI Code CDD 

use of ‘R’ in record position 952. 

Revised ‘Forecast’ to Projected 

Supply Plan’ per DLA PDC 297 

comment at paragraph 7 below.
5 of 12 

ADC 278 

Attachment 

# Location CHANGE TABLE 

DS 830D CHANGE from DDE data portrayed 

in 830R (version 4030) 

Reason 

13 2/PWK/1000 Revised DLMS segment level notes for PWK:

DLMS Notes: 

1. This segment contains free form text which the 

DDE submitter may use to provide information of 

value to the collaboration participants. This field 

may also be used by the submitter to provide 

information deemed useful to their planners during 

collaboration as it will be available for their 

viewing in the Collaborate tool. This segment is 

optional and informational in nature; the 

information in this segment shall be perpetuated 

into the Collaborate tool and can be viewed by all 

participants in the collaboration process. DLA will 

perpetuate the information in this segment and it 

will be visible in the online Collaborate tool as a 

drill down field. 

2. On an interim basis, to accommodate DLA’s DI 

Code CDD format in a mixed DLMS/non-DLMS 

CDD environment, the free form text in the PWK 

segment is limited to a total of 110 characters which 

maps to DI Code CDD Optional fields 1 through 4 

in record positions 953-1062. To accommodate 

DLA DI Code CDD fixed format, this requires 

restricting use of PWK segment to a maximum 4 

iterations, with maximum 20 characters each in 3 

iterations and maximum of 50 characters in one 

iteration. This supports DLA DI Code CDD which 

has 3 optional fields of 20 characters and 1 optional 

field of 50 characters. Use of PWK segment, other 

than as described by this note, is a DLMS 

enhancement. See introductory DLMS note 3a. 

To explain how free text is used 

with DDE. 

Added segment level note 3 to 

correlate the PWK segment to DLA 

DI Code CDD in a mixed DLMSDI Code CDD environment, and to 

identify that use beyond what is 

accommodated by the DLA DI 

Code CDD format is a DLMS 

enhancement.

See DMSO PDC 297 comment at 

paragraph 7 below (comment # 8).

14 2/REF/1400 Change the segment level Federal note to a DLMS 

Note and revise the note to change “SPR forecast” to 

“DDE Projected Supply Plan”.

DLMS Note: Must use to identify the transaction 

number associated with the DDE Projected Supply Plan

Administrative update. 

See DLA PDC 297 comment at 

paragraph 7 below (comment # 5).

15 2/REF01/1400 Add DLMS note to qualifier TN:

TN Transaction Number 

DLMS Note: Use to identify the Transaction 

Number (also known as the document number). 

Administrative update. 
6 of 12 

ADC 278 

Attachment 

# Location CHANGE TABLE 

DS 830D CHANGE from DDE data portrayed 

in 830R (version 4030) 

Reason 

16 2/PER/1500 Open the ‘PER’ segment for optional use when 

needed.

Adds an optional PER segment 

which is a standard DLMS segment 

for providing contact information. 

17 2/PER/1500 Add new segment level DLMS note 2:

DLMS Note 2: DLMS enhancement. See 

introductory DLMS note 3.a.

Administrative update to identify 

that use of PER segment is a DLMS 

enhancement over DLA DI Code 

CDD capability. Enhanced data 

will not convert to DI Code CDD in 

a mixed DLMS/non-DLMS CDD 

environment. 

18 2/N101/3200 Revise DLMS note for qualifier LW:

LW Customer 

DLMS Note: Use to identify the customer for DDE 

Projected Supply Plan transactions.

Administrative update to change 

“Demand Data Exchange 

transactions” to “DDE Projected 

Supply Plan transactions”. 

19 2/LQ01/4000 Revise DLMS Note 1 for qualifier ZZ:

ZZ Mutually Defined 

DLMS Note: Use with DDE Projected Supply Plan 

transactions to identify the planning code. 

Administrative update to change 

“Demand Data Exchange 

transactions” to “DDE Projected 

Supply Plan transactions”.

20 2/FST/4100 Revise segment level DLMS note:

DLMS Note: Use one or multiple repetitions of the 

2/FST/4100 segment for DDE Projected Supply 

Plan transactions. 

Administrative update to change 

“Demand Data Exchange 

transactions” to “DDE Projected 

Supply Plan transactions”. 

21 2/FST02/4100 Remove “forecast” from DLMS note for qualifier D 

and revise note for consistency with DLMS note for 

qualifier W:

D Planning 

DLMS Note: Use for DDE transactions when 

forecast removal (cancellation) does not apply. 

Use in conjunction with DDE Submission 

transactions (2/LIN01/0100 Code H- Submission)

For qualifier W, replace “Demand Data Exchange” 

with “DDE”:

W Cancellation 

DLMS Note: Use in conjunction with DDE 

Cancellation transactions (2/LIN01/0100 Code C - 

Cancelled) 

Administrative update to remove 

word “forecast” and to more closely 

align DLMS notes for qualifiers D 

and W for clarification. 
7 of 12 

ADC 278 

Attachment 

# Location CHANGE TABLE 

DS 830D CHANGE from DDE data portrayed 

in 830R (version 4030) 

Reason 

22 2/FST03/4100 Remove “forecast” from DLMS Note for Qualifiers 

A, M, Q, and S and replace with “projected supply 

plan”. Add note that qualifier for other than 

“monthly” are DLMS enhancements.

A Annually (Calendar Year) 

DLMS Note: Use to submit up to 5 annual periods 

of forecast projected supply plan data. Use of 

“Annual” is a DLMS enhancement. See 

introductory DLMS note 3a. [PDC 297 STAFFING

NOTE: Currently DLA only uses M-monthly] 

M Monthly Bucket (Calendar Months) 

DLMS Note: Use to submit up to 60 months of 

forecast projected supply plan data. [PDC 297 

STAFFING NOTE: Currently DLA only uses Mmonthly] 

Q Quarterly (Calendar Quarters) 

DLMS Note: Use to submit up to 20 quarters of 

forecast projected supply plan data. Use of 

“Quarterly” is a DLMS enhancement. See 

introductory DLMS note 3a. [PDC 297 STAFFING

NOTE: Currently DLA only uses M-monthly] 

S Semi-Annually (Calendar Year) 

DLMS Note: Use to submit up to 10 semi-annual 

periods of forecast projected supply plan data. Use 

of “Semi-Annually” is a DLMS enhancement. See 

introductory DLMS note 3a. [PDC 297 STAFFING

NOTE: Currently DLA only uses M-monthly] 

Replaced the word “forecast” with 

“projected supply plan” as noted in 

DLA PDC 297 comment at 

paragraph 7 below (comment # 6). 

 

2/FST03/4100 allows use of 

qualifiers for annual, semi-annual, 

quarterly and monthly submission 

of data, however at this time, DLA 

uses only monthly. Further, the 

DLMS procedures stipulate use of 

monthly. Accordingly, use of 

qualifiers A (annual), Q (quarterly) 

and S (semi-annually) are being 

identified as DLMS enhancements 

over current capability. See 

DLMSO PDC 297 comment at 

paragraph 7 (comment # 9). 

Excerpt from DLMS Vol 2, chapter 

2 (at enclosure 2): 

“C2.3.1. DDE supply planning 

activities may submit to DLA their 

projected supply plan/collaboration 

data for future requirements expected 

to be obtained from DLA using the 

DLMS 830D DDE Projected Supply 

Plan Transaction. Separate DDE 

projected supply plans into monthly

periods based on the projected dates 

that the materiel will be ordered from 

DLA.” 

23 2/FST04/4100 Open FST04 with DLMS notes: 

Date 

Description: Date expressed as CCYYMMDD 

DLMS Notes: 

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. 

Use for other than a date that corresponds to the 

BFR06 date is a DLMS enhancement. See 

introductory DLMS note 3a. 

Use of FST04 is mandatory IAW 

Accredited Standards Committee 

(ASC) X12. 

At this time, the FST04 start date 

would be the same as the BFR06 

start date. Both BFR06 and FST04 

are mandatory. Use of FST04 for a 

different date than BFR06 would be 

a DLMS enhancement over DLA 

DI Code CDD capability and would 

require a PDC. 

See DLMSO PDC 297 comment at 

paragraph 7 (comment # 10). 
8 of 12 

ADC 278 

Attachment 

(4) Revise DOD 4000.25-M, DLMS as follows (http://www.dla.mil/j6/dlmso/elibrary/Manuals/DLMS/default.asp): 

(a) Update DLMS Volume 2, Chapter 2, SPR and DDE Forecasts, as revised by 

ADC 287 (reference 3.a) as shown in Enclosure 2 (changes are identified by red, bold, 

italicized text). Changes to Chapter 2 SPR section, are identified in ADC 287. There is DDE 

introductory information in chapter 2 at paragraphs C2.1.1 and C2.1.2.1 of Enclosure 2. The 

DDE section of chapter 2 begins at section C2.3. 

(b) Revise the DDE definition in DLMS TERMS and DEFINITIONS (change is 

identified by red, bold, italicized text): 

DEMAND DATA EXCHANGE (DDE). A systemic method used for submitting 

collaborative customer projected supply plan materiel requirements to the Defense 

Logistics Agency (DLA). Used to communicate forecasts for both recurring and nonrecurring demands, as well as optional text data for consideration by Defense Logistics 

Agency Business System Modernization demand planners.

(c) Add the following two new definitions to DLMS TERMS and DEFINITIONS: 

CUSTOMER COLLABORATION. A confluence of strategic, tactical, and operational 

time based quantitative and qualitative sharing of information between the Defense 

Logistics Agency (DLA) and its customer activities including, but not limited to, 

formalized collaboration partnerships, exception handling by detection and notification, 

and DLA/customer collaborative demand planning 

JOINT COLLABORATION AGREEMENT. A collaborative and coordinated consensus 

between the Defense Logistics Agency (DLA) and customer activities that cites mutual 

responsibilities and expectations of both parties in the processes of demand data exchange 

(DDE). 

(5) Revise the DLMS Correlation of MILSTRAP DI Code Functionality to DS table

as shown below to add DS 830D. Changes are in red., bold, italicized text. Although DDE 

does not relate to a MILSTRAP or other Defense Logistics Standard System (DLSS, aka 

‘MILS’) transaction, the DLMS/MILSTRAP correlation table in DLMS sequence also 

addresses select DLMS transactions not associated with the DLSS. The cross reference table 

is available at: http://www.dla.mil/j6/dlmso/eApplications/LogDataAdmin/dlssdlmscrossreftable.asp. 

DS # DLMS Supplement Title DI Code(s) DS Accredited Standards Committee (ASC) X12

Functional Equivalent to MILSTRAP DI Code 

 Beginning Segment Additional Information 

needed 
9 of 12 

ADC 278 

Attachment 

DS # DLMS Supplement Title DI Code(s) DS Accredited Standards Committee (ASC) X12

Functional Equivalent to MILSTRAP DI Code 

 Beginning Segment Additional Information 

needed 

Demand Data Exchange 

(DDE) Projected Supply 

Plan (Submission) 

Non-DLSS 

DI Code 

CDD 

1/BFR12/0200 

Planning Schedule 

Type Code AA – 

Customized Ordering 

Forecast 

830D 2/LIN01/0100 Code H 1

Demand Data Exchange 

(DDE) Projected Supply 

Plan (Cancellation) 

Non-DLSS 

DI Code 

CDD with 

an ‘R’ in 

pr 952 

1/BFR12/0200 

Planning Schedule 

Type Code AA – 

Customized Ordering 

Forecast 

2/LIN01/0100 Code C 

(for cancellation of 

DDE for a given NIIN) 

1

 No DLSS (aka MILS) equivalent transaction exists for DS 830D, but it does equate to non-DLSS 

DLA DI Code CDD. 

5. REASON FOR CHANGE: 

a. To provide a distinct DLMS transaction for the DDE process. By ADC 139 (reference 

3.b), DLMSO added the DDE function to DS 830R which was used for Special Program 

Requirements (SPR). DLMSO migrated DS 830R to version 4030 to add the DDE 

requirements. DS 830R Version 4010 is still in use for SPR only. Upon further consideration, 

DLMSO finds that SPR and DDE are two distinct processes, and would be better served as two 

distinct DLMS transactions. Since there has been very limited implementation of DS 830R 

version 4030 to date (only DLA EBS has implemented), this is an opportune time for 

establishing a distinct DLMS DDE transaction before widespread implementation of the 

DLMS SPR/DDE transaction has taken place. The DLMS combined SPR/DDE transaction 

would be phased out entirely as DLA transitions to the DS 830D DDE transaction. SPR would 

continue as the existing DLMS 830R version 4010. Any Service implementation of the DLMS 

DDE transaction would take place with DS 830D version 4030. 

b. DLMSO understanding is that to date, no Service has implemented DS 830R version 

4030 for DDE as early DDE collaborators used a non DLMS fixed length DLA transaction 

(DLA DI Code CDD). Army LMP is in process of implementing DLMS, and implementation 

for SPR will use DLMS 830R version 4010. This is consistent with DLA’s implementation for 

SPR. DLA continues to use DS 830R, version 4010, for SPR, and uses DS 830R, version 

4030, only for DDE. 

6. ADVANTAGES and DISADVANTAGES: 

 a. ADVANTAGES: Supports DLA’s Customer Collaboration processes by identifying a 

distinct DLMS DDE interface transaction to communicate collaboration customers’ projected
10 of 12 

ADC 278 

Attachment 

supply plan data to DLA. Given that no Service has yet implemented the DLMS 830R version 

4030 DDE transaction, and DLA continues to use DS 830R version 4010 for SPR, DLA is the 

only Component affected by this change and DLA is only affected for the DDE process.

 b. DISADVANTAGES: Will require change by DLA EBS to transition from DS 830R 

Version 4030 to DS 830D version 4030 for DDE. 

7. PDC 297 COMMENT DISPOSITION: 

ORGANIZATION # COMMENT TO PDC 297 DISPOSITION 

ARMY 1 Concur. 

NAVY 2 No comments. 

USTRANSCOM 3 Abstains. 

4 Concur (with comments below) 

5 DS 830D, 2/REF/1400 segment level note 

states: "Must use to identify the transaction 

number associated with the SPR forecast". 

“SPR forecast” should be changed to “DDE 

Projected Supply Plan” 

Changed “SPR Forecast” to “DDE 

Projected Supply Plan” as noted in 

DS 830D Change Table (row 14), at 

paragraph 4.c(3) above. 

DLA 

 

 DLA, Ms. Kathy 

 Martinez 

 

 

 DLA, Ms. Kathy 

 Martinez 

6 There has been a lot of discussion amongst 

DLA and the Services about the differences 

between a 'forecast' and a 'Supply Plan', based 

on that, DDE forecast is changed to DDE 

projected supply plan. 

Deleted the word “forecast” or changed 

“forecast” to “projected supply plan” 

throughout ADC, DS 830D, and the 

DLMS chapter at enclosure 2. 

7 Currently DDE is only received by DLA 

ICP/IMMS. DLMSO revised the DLMS 

introductory notes to address that fact. 

Revised DS830D DLMS introductory no

1 as noted in the DS 830D Change 

Table (row 3), at paragraph 4.c(3) 

above. 

8 In a mixed DLMS and non-DLMS DLA DI 

Code CDD environment, the 2/PWK/1000 

segment relates to DI Code CDD as follows: 

Optional Field 1 (rp 953-972, 20 spaces) 

Optional Field 2 (rp 973-992, 20 spaces) 

Optional Field 3 (rp 993-1012, 20 spaces) 

Optional Field 4 (rp 1013-1062, 50 spaces) 

Currently use of the PWK segment should align 

with the CDD format. Expanded use of PWK 

segment is a DLMS enhancement. 

DS 830D revised as noted in DS 830D 

Change Table at row 13 to address use 

of PWK correlation to DI Code CDD 

format. 

See Enclosure 3 for DI Code CDD 

format excerpted from the DLA 

EBS DDE/CC Job Aid (see 

reference 3.c). 

DLMSO 

Ms. Mary Jane 

Johnson 

MILSTRAP 

Administrator 

9 2/FST03/4100 allows for submission of 

annual, semi-annual, quarterly and monthly 

buckets of data, however at this time, DLA 

uses only monthly buckets. Remaining 

buckets will be identified as DLMS 

enhancements.

DS 830D revised to add DLMS 

enhancement note to qualifiers for 

annual, semi-annual and quarterly, as 

shown in DS 830D Change Table at 

row 21. 
11 of 12 

ADC 278 

Attachment 

ORGANIZATION # COMMENT TO PDC 297 DISPOSITION 

10 2/FST04/4100 was not identified as used for 

DDE in the 830R Combined SPR/DDE, and 

was not open in PDC 297; however FST04 is 

mandatory and must be used. 

Opened FST04 and added DLMS notes 

noted in DS 830D Change Table 

above at row 23.

DLMSO 

comments 

continued...

11 For BFR04 Schedule Type Qualifier use 

qualifier ‘PR-Planned Requirement Based’ in 

Place of ‘ZZ-Mutually Defined’. 

Use of ‘PR’ is appropriate for DDE and 

consistent with DS 830R and DS 830W, 

whereas qualifier ZZ and new qualifier ‘RDRecurring Demand’ (approved in version 

5030), are not as appropriate. 

BFR04 is used in DLMS 830 transactions 

as follows: 

830W War Materiel Requirements (WMR) 

BFR04:

PR Planned Requirement Based 

DLMS Note: 

Use to indicate that requirements data reflect 

forecasted requirements. 

830R (v4010) Special Program 

Requirements (SPR) BFR04:

PR Planned Requirement Based 

DLMS Note: Use to indicate requirements 

data reflecting planned program requirement 

projections not based on historical demand. 

PROPOSED CHANGE FOR ADC 278 

830D DDE BFR04:

PR Planned Requirement Based 

DLMS Note: Use to indicate that 

requirements reflect DDE Projected Supply 

Plan data. 

REPLACES PDC 297 830D DDE BFR04:

ZZ Mutually Defined 

DLMS Note: Use to indicate requirements 

data reflecting Demand Data Exchange for 

forecasts of recurring and nonrecurring 

demands. 

A data maintenance action was approved in 

version 5030. The approved code/name is "RD 

-Recurring Demand". 

DS 830D revised to replace qualifier 

ZZ with qualifier PR as shown in DS 

830D Change Table above at row 7. 
12 of 12 

ADC 278 

Attachment 

8. IMPACT: 

a. Automated Information Systems (AIS): 

(1) Service AIS: No impact to Service systems as a result of this proposal as none 

have implemented DS 830R, version 4030, combined SPR/DDE. Services implementing DLMS 

for DDE Projected Supply Plan must do so using DS 830D. 

(2) DLA and DAASC AIS: DLA implementation of DS 830D version 4030 for 

DDE, in place of the existing DS 830R Version 4030, SPR/DDE will require EBS system change. 

STAFFING NOTE FOR DLA: DLA must identify to DLMSO when this change can be 

implemented so that an implementation date for DAASC to begin converting DI Code CDD 

to DLMS 830D can be established. 

b. DAASC Maps: 

(1) DAASC mapping update will be required to map DLA-unique DI Code CDD 

fixed length format to new DS 830D. 

(2) If a Service begins to process DS 830D under modernization before DLA 

EBS has transitioned from 830R version 4030 to DS 830D, DAASC may need to provide a map 

between the Service DS 830D (version 4030), to DS 830R (version 4030) for DLA, until such 

time as EBS transitions and DS 830R version 4030 is completely phased out. 

c. DLMSO strongly recommends that the Services using DI Code CDD transactions with 

DLA identify and review the information they are including in the DI Code CDD free-form text 

fields (record positions 953 through 1062) to determine if any data conveyed in these record 

positions should be added to an appropriate DS 830D transaction segment by a DLMS change 

proposal. 

Enclosures: 

1) DLMS Supplement 830D 

2) DOD 4000.25-M, Volume 2, Chapter 2 

3) DLA DI Code CDD Data Format
ADC 278 

Enclosure 1 

ENCLOSURE 1 TO PDC 297 

DLMS Supplement 830D (version 4030) 

This page intentionally left blank. 

Enclosure 1, DS 830D, is provided as a separate rtf file 
DoD 4000.25-M, Volume 2 

C2-1

ADC 278, Enclosure 2

DLMS, Vol 2, Chapter 2 (DDE section only) 

ENCLOSURE 2 TO PDC 297 

[CHANGES FROM DOD 4000.25-M, DLMS, VOL 2, CHAPTER 2 DDE PROCEDURES 

ARE IDENTIFIED BY RED, BOLD, ITALICS. CHANGES FROM PDC 297 ARE ALSO

HIGHLIGHTED.]

C2. CHAPTER 2

SPECIAL PROGRAM REQUIREMENTS

AND DEMAND DATA EXCHANGE FORECASTS

PROJECTED SUPPLY PLAN

C2.1. GENERAL. 

 C2.1.1. Purpose. This chapter provides procedures for Special Program Requirements 

(SPR) and for Demand Data Exchange (DDE) forecasts Projected Supply Plan. 

 C2.1.2. Transactions. This chapter addresses the procedures to the following ASC 

X12 transaction functions identified by their beginning segment and report type code. Other 

DLMS formats, such as XML, are also available. See the DLMSO website for available 

DLMS formats: http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp. The 

corresponding Defense Logistics Standard System (DLSS) MILSTRAP transaction 

functionality is identified for information purposes in a mixed DLSS/DLMS environment. 

 C2.1.2.1. DDE Projected Supply Plan is DS to Federal IC 830D (version 

4030) identified by beginning segment (1/BFR12/0200) Planning Schedule Type Code 

AA – Customized Ordering Forecast. DDE function is further broken down in 

2/LIN01/0100 to identify a DDE Projected Supply Plan submission (LIN01 Code H) 

and a DDE Projected Supply Plan cancellation (LIN01 Code C) for a given NIIN. 

This transaction is a DLMS enhancement and has no corresponding DLSS 

transaction, but does provide functionality of the Defense Logistics Agency (DLA) 

Document Identifier (DI) Code CDD transaction. 

 C2.1.2.2. SPR is DS to Federal IC 830R (version 4010) identified by beginning

segment (1/BFR12/020) Planning Schedule Type Code XA – Requirement Forecast. 

[Section C2.1.2.2. for SPR was approved by ADC 287. The SPR procedures are not 

impacted by the DDE process or ADC 278. See ADC 287 for section C2.1.2.2. for SPRs: 

http://www.dla.mil/j-6/dlmso/eLibrary/Changes/approved3.asp.] 

C2.2. SPECIAL PROGRAM REQUIREMENTS (SPR), DS 830R. [Changes to section 

C2.2, SPR were staffed separately and were approved by ADC 287. The SPR 

procedures are not impacted by the DDE process or ADC 278. See ADC 287 for the 

revised section C2.2 for SPRs: http://www.dla.mil/j6/dlmso/eLibrary/Changes/approved3.asp.] 
DoD 4000.25-M, Volume 2 

C2-2

ADC 278, Enclosure 2

DLMS, Vol 2, Chapter 2 (DDE section only) 

C2.3. DDE PROJECTED SUPPLY PLAN FORECASTS. This section provides 

procedures for the exchange of demand forecast DDE projected supply plan data between 

the Defense Logistics Agency (DLA) and DoD customers. The two components of this 

business process are the transmission of customer requirements via DDE and Customer 

Collaboration. Business rules for the submission and processing of DDE shall be 

documented in a DLA customer support agreement, (i.e. Joint Collaboration Agreement). 

This agreement must be in place prior to the initial submission of DDE. DLA shall use the 

DDE/Customer Collaboration process to improve the accuracy of DLA’s demand planning 

to support customer’s requirements. 

 C2.3.1. Forecasting DDE supply planning activities may submit to DLA their 

forecasts projected supply plan/collaboration data for future requirements expected to be 

obtained from DLA using the DLMS 830D DDE Projected Supply Plan Transaction. 

Separate DDE projected supply plans into monthly periods based on the projected dates 

that the material will be ordered from DLA. Types of demands for which collaboration 

data may be submitted include, but are not limited to: 

 C2.3.1.1. Requirements for which the DoD Component has a recurring demand. 

 C2.3.1.2. Subsistence, all categories. 

 C2.3.1.3. One-time training exercises or maneuvers. 

 C2.3.1.4. Repair or rebuild programs which are either nonrecurring or which 

are seldom or irregularly programmed. 

 C2.3.1.5. New constructions (ships, buildings, etc.). 

 C2.3.1.6. One-time alterations, modifications, or conversion programs. 

 C2.3.1.7. Initial issue of existing items (i.e., outfittings, activations, and 

changes in authorized allowances). 

 C2.3.1.8. Initial requirements for special operational projects. 

 C2.3.1.9. Requirements for initial testing. 

 C2.3.1.10. Requirements for infrequently planned support operations such as 

Arctic and Antarctic resupply missions. 

 C2.3.1.11. Special situations of a nonrepetitive nature when required in support 

of authorized Security Assistance Program requirements (e.g., initial pipeline stockage 

requirements in support of approved Cooperative Logistics Supply Support Arrangement 

(CLSSA), etc.) 

 C2.3.1.12. Zero or reduced requirements, which are different than past 

demand history patterns. 
DoD 4000.25-M, Volume 2 

C2-3

ADC 278, Enclosure 2

DLMS, Vol 2, Chapter 2 (DDE section only) 

 C2.3.2. DDE Projected Supply Plan Submission and Routing

 C2.3.2.1. Submission Timeframe. DDE Transactions must be submitted each 

month. Demand data should be submitted by the 1st of the month and may be submitted up 

to 5 business days prior to the 1st of the month, with a buffer until the 6

th 3rd of the month 

to accommodate transmission errors or failures. 

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

prepare the DDE projected supply plan for each item = Demand Forecast Unit (i.e., 

National Item Identification Number (NIIN), Ship To DoDAAC, and 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 spanned can be as little as 12 months or as 

much as 60 months. 

 C2.3.3. DAASC Processing. DAASC shall route all DDE transactions to DLA’s 

Enterprise Processing Center, SOS “SMS.” 

 C2.3.4. DLA Validation of NIIN. DLA shall screen transaction sets and will only 

accept for processing valid NIINs. 

 C2.3.5. DLA Processing of DDE Data. DLA shall compare the collaboration 

customer’s projected supply plan to the projected customer supply plan calculated by the 

Planning and Collaboration Subsystem or the previous collaborative projected supply plan

if the NIIN is a recurring Demand Forecast Unit. 

 C2.3.5.1. Those items that Collaborative items (which may or may not exceed 

system tolerance parameters) shall be flagged for available for collaboration interaction 

with the customer and DLA via the Planning and Collaboration Subsystem. 

 C2.3.5.2. Items previously identified for inclusion in DDE that are not in the 

current DDE submission shall be flagged for review remain flagged as Collaborate with 

the most recent DDE projected supply plan quantities received from the customer. If the 

customer would like to remove an item from the DDE effort, the customer shall submit a 

DS 830D, DDE Cancellation Transaction for the NIIN and the item will be removed from 

the DDE/Customer Collaboration effort. 

 C2.3.5.3. The setting of system tolerance parameters used in this review 

requires consideration of the following: size of the DDE projected supply plan quantity in 

relation to the Planning and Collaboration Subsystem forecasted demand for the item; 

value (cost) of the projected supply plan quantity; supply status of the item being 

forecasted; funding capabilities; accuracy of customer’s past DDE projected supply 

plans; and degree of assurance that requisitions will follow. 

 C2.3.6. Collaboration Interaction. All Collaborative items (which may or may not

exceed system tolerance parameters) shall be available for monthly collaboration 

interaction with the customer and DLA. The point of contact for the customer shall be 

alerted, via e-mail by the Collaboration lead at their Center (Defense Supply Center 
DoD 4000.25-M, Volume 2 

C2-4

ADC 278, Enclosure 2

DLMS, Vol 2, Chapter 2 (DDE section only) 

Richmond (DSCR), Defense Supply Center Columbus (DSCC), Defense Supply Center 

Philadelphia (DSCP)), by the 7th business day of every month to notify their customer of 

the open and close dates of the monthly collaboration window. The customer shall

normally have until the 16th day 4th Thursday of the month to complete the review 

(specific open and close dates will be cited in the e-mail). The DLA demand planner will 

then have until the 25th 4th Friday of the month (also known as ‘Demand Month End’) to 

complete the review and publish the demand plan for inclusion in the projected supply 

plan.
ADC 278 

Enclosure 3 

DLA DI Code CDD Format 

ENCLOSURE 3 to ADC 278 

CDD Format 

EXCERPT FROM EBS DDE Customer Collaboration via Digital Data Network, 

Job Aid, November 29, 2007:

Each DDE data record is categorized by a field legend, and provides details on the following: 

field position, whether the field data is required or optional, and field contents. 

NOTE: Where the field is identified as OPTIONAL below, please refer to this as a 

‘mandatory / optional’ field. The field should still be programmed in the formatting; 

however, the data inside the field is OPTIONAL

Field Legend: Transaction Type Field Position: 01-03 REQUIRED 

This field will contain a constant of ‘CDD’ which is the DIC for the DDE transaction. All 

collaboration forecast submittals will reflect CDD in positions 1-3. 

Field Legend: Source of Supply Field Position: 04-06 REQUIRED 

This is the RIC of the destination Source of Supply. The only allowable entry in this field is 

‘SMS’ indicating that the NIIN is managed by the DLA. DDE transactions for NIINs that do not 

have a SMS source of supply will be rejected. 

Field Legend: Submitter DoDAAC Field Position: 07-12 REQUIRED 

This field will contain the six-position Department of Defense Activity Address Code 

(DoDAAC) of the submitting organization. Identified as Location 3 within Manugistics Collab. 

Field Legend: Sold To DoDAAC Field Position: 13-18 REQUIRED 

This field will contain the six-position DoDAAC of the customer’s user’s organization that will 

be requisitioning the item. This DoDAAC is found in the first six positions of a requisition 

document number. Identified as Location 2within Manugistics Collab. 

Field Legend: Ship To DoDAAC Field Position: 19-24 REQUIRED 

This field will contain the six-position DoDAAC of the “Ship to” organization. In many cases 

the submitter and ship-to DoDAAC will be the same on the transaction. Identified as Ship To 

Location within Manugistics Collab. 

Field Legend: NIIN Field Position: 25-33 REQUIRED 

Nine-position National Item Identification Number (NIIN) of the item the submitter wishes to 

collaborate on. 

Field Legend: Unit of Issue Field Position: 34-35 REQUIRED 

Two-position unit of issue for the nine-position NIIN identified in positions 25-33 above. 

Field Legend: Planning Code Field Position: 36-40 OPTIONAL

Five-position planning code to be used by the DDE transaction Submitter to identify any unique planning 

code. The planning code will be reflected in the submitter’s collaboration forecast as input by the 

submitter. The intent of this field is to provide the user with a field that may be useful for either internal 

service analysis or the collaboration process. DLA will perpetuate the data in this field and it will be 

visible in the online Manugistics Collaborate tool as a drill down field. This field can be blank or contain 

maximum of five alpha/numeric characters. NOTE: If field is blank file must still contain 5 spaces. 
ADC 278 

Enclosure 3 

DLA DI Code CDD Format 

Field Legend: Supply Plan Start Date Field Position: 41-45 REQUIRED

Five-position Julian date that the supply plan will begin. The supply plan start date indicates the 

beginning of the collaboration (forecast) time period and is the 1st day of the month in which 

collaboration transactions are submitted. This date field must reflect the 1st day of the month in 

which the DDE transactions are submitted to DLA. Example: If DDE is submitted on May 1, 2007, 

the supply start date must be 07121. NOTE: This date must always be the 1st day of the month, even 

if the actual date of transmission is later a later date in the month. 

NOTE: The DDE/CC transactions will be submitted no later than the 1st day of every month but 

should be submitted up to 5 business days prior to the 1st business day of the month. The 2nd and 

the 3rd business day will be reserved fro error correction to the submitted files. 

Field Legend: Supply Plan End Date Field Position: 46-50 REQUIRED

Five-position Julian date that the supply plan will end. The supply plan end date indicates the end of 

the collaboration (forecast) time period and is the last day of the final forecast period (or month). 

Time periods beyond the final forecast period are not considered in the collaboration process. When 

submitting monthly requirement quantities, the supply plan end date must reflect the last day of the 

last month in the forecast period/ quantities are expected to end. Example: If DDE is submitted on 

May 1, 2007 for two years of forecast quantities, the supply end date must be 09120 (April 30, 2009). 

Field Legend: Supply Plan Type Field Position: 51 REQUIRED 

This field is a one-position Supply Plan (forecast) Type and is a required field. NOTE: This field 

will ALWAYS contain M (Monthly). At a later release, the transaction may allow input of one of the 

following codes: Q = Quarterly, S = Semi-Annually, and A = Annually. This field reflects the period 

in which the supply plan quantity fields will be expressed. If the Submitter puts an “M” in this field 

the quantity fields in transaction position 52-951 (60 individual quantity fields of 15 positions each) 

of this transaction are forecast periods of monthly quantities required. If the user puts a Q in this 

field, forecast periods of quarterly quantities are required. If the user puts an S in this field, forecast 

periods of semi-annual quantities are required. If the user puts a Y in this field, forecast periods of 

yearly quantities are required. 

Field Legend: Supply Plan Period Quantities Field Position: 52-951 REQUIRED This field will contain up to 60 separate supply plan quantities in fifteen-position fields per quantity and 

should correspond to the periods covered between the Supply Plan Start Date and the Supply Plan End 

Date, in terms of the Supply Plan Type. Positions 52-951 of the DDE transaction are designed as an array 

to hold the 60 separate supply plan quantities (forecast quantities) required by the Submitter based upon 

the supply plan start date, the supply plan end date, and the supply plan type. Quantities are to be whole 

numbers; no decimal numbers are allowed. Each of the Quantity fields must be filled either with a 

numeric quantity or zeros (each field must be left padded with zeros to fill out the entire field space 

allocated) and should correspond to the periods covered between the Supply Plan Start Date and the 

Supply Plan End Date and in terms of the Supply Plan Type. Quantities must be entered starting with the 

first field in the Array and continuing with quantity entries that correspond with to the Start Plan End 

Date and the Supply Plan Type. All sixty fields must be populated with either a numeric quantity or zero; 

a Null (no data) in a supply plan quantity field will cause the transaction to fail validation. The forecast 

period is defined by the Supply Plan Start and End dates. All fields beyond the Supply Plan End Date 

should be filled with zeros. A numeric quantity in a month beyond the Supply Plan End Date will trigger 

a validation request to the submitter. Quantities of zero in a field representing a month within the Supply 

Plan Start Date and Supply Plan End Date will indicate that the submitter does not have a requirement in 

that month. Zero quantities in months beyond the Supply Plan End Date indicate that the user has not 

submitted a forecast for these months. 

NOTE: If quantity is entered outside of the Supply Plan End Date specified in Field Position: 46-50, this 

quantity will default to null. 
ADC 278 

Enclosure 3 

DLA DI Code CDD Format 

Field Legend: Supply Plan Removal Code Field Position: 952 OPTIONAL 

This field should contain an ‘R’ to indicate that this Supply Plan DFU should be deleted when the 

submitter wants to remove the item from the collaboration efforts. When this field is used, ALL 

other required fields must be valid data. If a NIIN is submitted to DLA for collaboration, DLA 

“marks” it as a collaborative item and “looks” for it in each subsequent submission from the user. If 

the item is missing, the DLA edit will trigger an inquiry to the submitter and all previous forecast 

quantities remain in the system (the item is not removed unless the ‘R’ is included). The ‘R’ supply 

plan removal code advises DLA that the submitter intentionally deleted the item. NOTE: If field is 

blank, file must still contain 1 space. 

Field Legend: Optional Field 1 Field Position: 953-972 OPTIONAL

This field contains free form text which may be used as a field for the submitter to provide information of 

value to the collaboration participants. This field may also be used by the submitter to provide 

information deemed useful to their planners during collaboration as it will be available for their viewing 

in the Manugistics Collaborate tool. This field is optional and informational in nature; the data in this 

field will be perpetuated into the Manugistics Collaborate tool and can be viewed by all participants in the 

collaboration process. The intent of this field is to provide the user with a field that may be useful for 

either internal service analysis or the collaboration process. DLA will perpetuate the data in this field and 

it will be visible in the online Manugistics Collaborate tool as a drill down field. 

NOTE: If field is blank file must still contain 20 spaces. 

Field Legend: Optional Field 2 Field Position: 973-992 OPTIONAL

Same as Optional Field 1 

NOTE: If field is blank file must still contain 20 spaces.

Field Legend: Optional Field 3 Field Position: 993-1012 OPTIONAL

Same as Optional Field 1 

NOTE: If field is blank file must still contain 20 spaces.

Field Legend: Optional Field 4 Field Position: 1013-1062 OPTIONAL 

Same as Optional Field 1 

NOTE: If field is blank file must still contain 50 spaces.