iN REPLY 

REFER ' DLMSO 

DEFENSE STiCS AGENCY 

HEADQI ARTERS 

8725 JOHN J. -tINGMAN ROAD 

FORT BELVOIR, VI 'GINIA 22060-622 1 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE 

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

139, Revision to DS 830R to Accommodate Demand Data Exchange 

(Transmitting Forecasts of Recurring and Non-Recurring Demand Data) 

(SupplyIDLMS) (Staffed by PDC' 13 1) 

TL- ,++,,L,A -L,,,,- t, nnn nnnn ?<-nn n-\r nnc :, ,,,,,,,,A c, :,A:~+, ,+;,I I IIL aLLaLuLu LllalLgL LU YVU -~UUU.LJ LVI. UIIIVIO, 13 appluv~u LWL LILLIIILUIULL U~LIUIIUI 

1 .-... 1 _.-A ___L_L:___ I___ I._.._____x._L I__~.._-_._ Li__ ~1 : _._J n~ A TI__ ____A-~_A n~ n .KO IIII~ICIIICIIL~~LIVII uy ~~~ICCIIICIIL UCLWCCII LIIC XI VICCS mu ULA. I IIC upuil~cu ULIVICI 

Supplement will be posted to the Defense Logistics Management Standards Office 

(DLMSO) web site (http://www.dla.mil/j-6/dlmso/ICs/Default.htrn) within 30 days from 

the above date for implementation planning. DLMSO will submit concurrently any 

necessary revisions to the governing Federal Implementation Convention to the DOD 

Electronic Data Interchange Standards Management Committee, and the Federal Electronic 

Data Interchange Standards Management Coordinating Committee, and applicable working 

groups. 

Addressees may direct questions to the DLMSO point of contact, Ms. Mary Jane 

Johnson, 703-767-0677, DSN 427-0677, or e-mail: Mary.Jane.Johnson@dla.mil. Others 

must contact their Component designated Supply Process Review Committee 

representative. 

P X&GES A. JOHNSON 

Director 

Defense Logistics Management 

Standards Office 

Attachment 

cc: 

ADUSD(L)SCI 
1 of 11

ADC 139 

Attachment

ATTACHMENT TO ADC 139

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

of Recurring and Non-Recurring Demand Data) (Supply/DLMS) (Staffed by PDC 131)

1. Originator:

 a. Service/Agency: Defense Logistics Agency (DLA).

 b. Originator: Ms. Beth Altman or Ms. Brenda Meadows, HQ, DLA, Distribution 

and Reutilization Policy, Distribution Management Division, Material Accountability and 

Distribution Policy Branch (J-3731)

 c. Subject Matter Expert: Mr. Dave Dimmick, DSCR-OK, Focused Operations 

Group and BSM Planning Team Member

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

3. REQUESTED CHANGE:

 a. Title: Revision to DS 830R to Accommodate Demand Data Exchange 

(Transmitting Forecasts of Recurring and Non-Recurring Demand Data) (Supply/DLMS)

 b. Description of Change: This change revises DLMS Supplement to the Federal 

Implementation Convention DS 830R (Planning Schedule with Release Capability) to 

include DLA Business Systems Modernization (BSM) planning functionality. As an 

interim, until such time as the Services have implemented DLMS, DLA is also providing 

for Component use of a new Document Identifier (DI) Code developed by the BSM 

Planning Team (DI Code CDD, Demand Data Exchange). DLA indicates that the 

capabilities and data content of the Demand Data Exchange DS 830R (and its interim 

counterpart, DI code CDD), will enable collaboration customers to communicate 

periodic demand forecast data required by the BSM Planning and Collaboration 

subsystem (i.e., Manugistics) and should result in better and more accurate forecasts for 

items customers require. DLA indicates that initial implementation in BSM Release 

R2.1.2 (February, 2005) will include 12 collaboration customers among the DOD 

Components. BSM plans to use the Demand Data Exchange process for a wide range of 

commodities, including subsistence; therefore, forecast quantity fields are set at 15 record 

positions. The new use of DS 830R is expected to evolve as DLA and its collaboration 

customers gain experience and additional program data is added. 
2 of 11

ADC 139 

Attachment

 c. Procedures: 

 (1) Each collaboration customer will route to DLA BSM (Routing Identifier Code 

“SMS”) a DS 830R (or its interim counterpart DI Code CDD) for each item (i.e., 

National Item Identification Number/Material Number) for which the customer wishes to 

collaborate with DLA BSM. The Demand Data Exchange transaction also provides 

customers the capability to withdraw an item from collaboration efforts by notifying 

BSM to delete the demand forecast data. The Defense Automated Addressing System 

Center (DAASC) will provide corporate translation services -- converting the customers’ 

Demand Data Exchange transactions submitted in DI Code CDD format to DS 830R 

transaction sets for DLA BSM E-Gate. The Demand Data Exchange transaction set can 

be used to communicate forecasts for both recurring and non-recurring demands, as well 

as optional text data for consideration by DLA BSM Demand Planners. Data being 

furnished in text format will not be used for programmatic decisions. Although the 

Demand Data Exchange data structure is capable of accommodating different forecast 

periods, DLA BSM will initially request monthly forecasts. The Demand Data Exchange 

transaction set accommodates up to 60 separate (monthly) forecast quantities (15-position 

numeric), with the intent of allowing collaboration customers to forecast demands for up 

to 5 years. The 5-year forecast period applies regardless which interval is used (i.e., 

monthly, quarterly, semi-annually, or annual). DLA BSM will require maximum 

flexibility while the processes and data content evolve in a production environment. 

Accordingly, the Demand Data Exchange transaction set contains 4 unstructured optional 

fields to accommodate free-form text. Collaboration customers will use free-form text 

fields to communicate additional information regarding the demand forecast data. 

 (2) The format for the interim DLA DI Code CDD, demand data exchange user 

defined file is provided at Enclosure 1 for Component information and use if desired by 

agreement with DLA pending implementation of revised DS 830R. 

 (3) Revise DS 830R as follows (Changes from Proposed DLMS Change 131 are 

identified by red text with double underscore or, for deletions, double strike-thru):

Item 

#

Location DS 830R Revision Reason Federal 

IC

1 DS 830R title Revise DS 830R name to:

Special Program Requirements and 

Demand Data Exchange Forecast

Identifies Demand data 

exchange forecast 

functionality.

Revision 

required.

2 Federal 

Introductory 

Notes 

Revise Federal Introductory Note 1: 

Organizations use this transaction set to 

transmit Special Program Requirements 

(SPRs) and for forecasts of recurring 

and non-recurring demand data to 

Inventory Control Points 

(ICPs)/Integrated Material Managers 

(IMMs).

Identifies Demand data 

exchange forecast 

functionality.

Revision 

required.
3 of 11

ADC 139 

Attachment

Item 

#

Location DS 830R Revision Reason Federal 

IC

3 DLMS 

Introductory 

Notes

Revise DLMS Introductory Note 1: 

Use a single occurrence of this 

transaction set to transmit SPR and 

Demand Data Exchange forecast 

transactions to one or more ICPs/IMMs. 

Demand Data Exchange forecast is a 

DLMS enhancement. See 

introductory DLMS note 5.a”

Identifies Demand data 

exchange forecast 

functionality as an 

enhancement.

No 

impact.

4 DLMS 

Introductory 

Notes

Add new DLMS introductory note 5:

5. This revision to the DLMS 

Supplement incorporates Proposed 

DLMS Changes (PDC) and Approved 

DLMS Changes (ADC) listed. 

PDCs/ADCs are available from the 

DLMSO website at: 

http://www.dla.mi/lj-6/dlmso/Changes.

-ADC 139, Revision to DS 830R to 

Accommodate Demand Data Exchange 

(Transmitting Forecasts of Recurring 

and Non-Recurring Demand Data) 

(Supply/DLMS)

Administrative. 

Identifies proposed and/or 

approved changes included 

in the DS.

No 

impact.

5 1/BFR04/020 DE 675, add new qualifier “ZZ” , 

Mutually defined with DLMS note:

ZZ Mutually Defined

DLMS note: Use to indicate 

requirements data reflecting Demand 

Data Exchange for forecasts of 

recurring and nonrecurring demands. 

An ANSI data maintenance request will 

be submitted to obtain A DM will be 

developed to add a more appropriate 

qualifier.

Identifies Demand data 

exchange forecast 

functionality.

Revision 

required.

6 1/BFR12/020 DE 783 code value “XA” , revise DLMS 

note: to include Demand Data Exchange 

and Component-unique note:

XA Requirement Forecast

DLMS note: Must use to indicate the 

transaction is an SPR forecast or a 

Demand Data Exchange forecast.

Identifies Demand data 

exchange forecast 

functionality. 

No 

impact.
4 of 11

ADC 139 

Attachment

Item 

#

Location DS 830R Revision Reason Federal 

IC

7 1/BFR13/020 Revise DLMS note for DE 306 code 

value “OT” to include Demand Data 

Exchange:

OT Other Unlisted Action

DLMS Note: “Exception Date. Use 

only with 2/LIN01/010 codes “A,” “B,” 

“C,”, or “H” Use only when exception 

data is to be provided.”

Includes Demand Data 

Exchange removal 

transaction (i.e., 

2/LIN01/010=C).

No 

impact.

8 1/N101/230 DE 0098 code value “41”, revise DLMS 

note to include Demand Data Exchange 

and Component-unique note:

41 Submitter

Proposed DLMS Note 1. “Must use to 

identify the submitter of the SPR or 

Demand Data Exchange

requirement.”

Authorizes use of code 

value “41” for Demand 

Data Exchange submitters.

No 

impact.

9 2/LIN01/010 DE 350 Revise DLMS notes and add 

new code ‘H’ as follows: 

Assigned Identification

Description: Alphanumeric characters 

assigned for differentiation within a 

transaction set

DLMS Note: 

A – SPR submission

B - SPR Security Assistance (SPR SA) 

submission

C - Cancellation of previously submitted 

SPR or Demand Data Exchange. 

Use indicates cancellation of the entire 

open SPR or Demand Data Exchange

quantity. 

D - Modification of a previously submitted 

SPR

E - Inquiry on status of previously 

submitted SPR. or demand data 

exchange

F - Acceptance of offer to provide 

substitute material

G - Rejection of offer to provide 

substitute material

H – Demand Data Exchange Submission

Authorizes use of code 

‘H’ to identify Demand 

Data Exchange 

submission, and provides 

for use of cancellation 

with demand data 

exchange transactions.

Based on DLA response 

to PDC 131, Code E is 

withdrawn for use with 

Demand data Exchange. 

DLA stated that the BSM 

Planning Team has no 

planned ability to inquire 

against a previously 

submitted Demand Data 

Exchange transaction.

No 

impact.
5 of 11

ADC 139 

Attachment

Item 

#

Location DS 830R Revision Reason Federal 

IC

10 2/LIN02/010 Change Federal note to:

“Use any code.”

Administrative change.

DS identifies specific codes 

to be used for DLMS.

Revision 

required.

11 2/LIN02/010 Add DLMS note:

“Use only one of codes A1, A2, A4, FB, FS, 

MG, TP or YP to identify the material. Must 

use National Stock Number (NSN) when 

known, except for Demand Data Exchange 

which uses the National Item Identification 

Number (NIIN).

Identifies use of NIIN for 

demand data exchange 

transactions for DLA 

requirement. 

No 

impact.

12 2/LIN02/010 Change DLMS Note for DE 235 code 

value “FS”:

FS National Stock Number

Revise DLMS Note: “Must use the 

NSN when known, except for Demand 

Data Exchange transactions which 

require use of the NIIN.” 

Establishes use of NIIN as 

acceptable alternate for 

NSN.

No 

impact.

13 2/LIN02/010 Add new DE 235 code value to identify 

National Item Identification Number 

(NIIN):

ZZ Mutually Defined 

Proposed DLMS Note: 

“1. Use to identify the National Item 

Identification Number (NIIN) for 

Demand Data Exchange transactions.

 2. DLMS enhancement; see 

introductory DLMS note 4.a.

A ANSI code maintenance request will 

be submitted for code NN - National Item 

Identification Number (NIIN).

Authorizes use of NIIN for 

demand data exchange 

transactions per DLA 

requirement.

No 

impact.

14 2/PWK/100 Add Federal Note: “Use any code.” Administrative change.

DS identifies specific codes 

to be used for DLMS.

Revision 

required.

15 2/N101/320 Change Federal note to “Use any code.” Administrative change.

DS identifies specific codes 

to be used for DLMS.

Revision 

required.
6 of 11

ADC 139 

Attachment

Item 

#

Location DS 830R Revision Reason Federal 

IC

16 2/N101/320 Authorize use of DE 98 code value 

“LW” – Customer for Demand Data 

Exchange:

LW Customer

DLMS Notes: 

1. Use to identify the customer for 

Demand Data Exchange transactions.

2. DLMS enhancement; see introductory 

DLMS note 4a

Authorizes use of code 

value LW to identify the 

collaboration customer.

No 

impact.

17 2/N101/320 Revise DLMS Notes for DE 98 code 

value ST:

ST Ship To

Add new DLMS note 2 (and 

renumber current note 2 as 3): 

2. “Use in Demand Data Exchange 

transactions to identify the Ship To 

when different from the Customer.”

Authorizes use of code 

value “ST” for Demand 

Data Exchange Ship To 

entity.

No 

impact.

18 2/LQ01/400 Add ZZ Mutually defined with DLMS 

note:

ZZ Mutually Defined

DLMS Note: 

1. Use only with Demand Data 

Exchange transactions to identify the 

planning code. An ANSI code 

maintenance request will be prepared 

to request a new code.

1. Use only with Demand Data 

Exchange transactions to identify the 

planning code. An ANSI data 

maintenance request will be prepared 

to request a new qualifier for 

Planning Code.

2. Planning Code is optional data that 

the customer may use as they 

determine is needed. Planning Code is 

an intra-Component, five-position 

code, which is under development by 

the Services. Accordingly, although 

the data will be meaningful to the 

customer and will be visible to 

customers in the Collaborate web 

tool, it won’t necessarily be 

meaningful to DLA or the other 

Services.

Advance planning to obtain code list 

qualifier code value for new list of 

Demand Data Exchange Planning 

Codes.

DLMSO comment: DLA must 

provide code list and code source 

(publication) for DLMSO to obtain 

an ANSI qualifier. Request 

information be provided within the 

response timeframe for this PDC.

DLA response to DLMSO comment: 

DLA can provide neither a list of 

Planning Codes nor a source for 

those codes, since this is an 

optional field that the customers 

use as they see fit. There should 

be no problem if different 

submitters use the same code for 

different purposes, since the DDE 

comes in at submitter/customer/ 

ship-to level. Accordingly, 

although the data will be 

meaningful to the customer and 

will be visible to them in the 

Collaborate web tool; it won’t 

necessarily be meaningful to 

DLA.
7 of 11

ADC 139 

Attachment

Item 

#

Location DS 830R Revision Reason Federal 

IC

19 2/FST/410 Add new DLMS Note 3:

3. Use one or multiple repetitions of the 

2/FST/410 segment for demand data 

exchange. Demand data exchange 

transactions are a DLMS enhancement. 

See introductory DLMS note 4.a.

Identifies that FST segment 

is used for Demand Data 

Exchange.

No 

impact.

20 2/FST01/410 Add DLMS Note to authorize use of 

FST01 segment for Demand Data 

Exchange:

Add new DLMS Note 7: “Use up to 

60 repetitions in Demand Data 

Exchange transactions to identify the 

quantity for each interval/bucket. 

DLMS enhancement. See introductory 

DLMS note 4.a.

Adds note regarding 

applicability of FST01 to 

Demand Data Exchange.

No 

impact.

21 2/FST02/410 Add Federal note: Use any code. Administrative change.

DS identifies specific codes 

to be used for DLMS.

Revision 

required.

22 2/FST02/410 Add DLMS note: For DLMS, only the 

following codes are authorized.

Administrative. No 

impact.

23 2/FST02/410 Revise DLMS notes to DE 680 qualifier 

code values “D” and “W.”

D Planning

1. Use only for SPR, SPR SA, SPR 

substitute acceptance, SPR substitute 

rejection, and SPR inquiry transactions.

2. Use for Demand Data Exchange 

transactions when forecast removal code 

does not apply

W Cancellation

1. Use only for SPR cancellation 

transactions.

2. Use for Demand Data Exchange

transactions that include 2/LIN01/010 

code C

DLMS enhancement; see introductory 

DLMS note 4a.

Authorizes applicability to 

Demand Data Exchange 

process.

No 

impact.

24 2/FST03/410 Add Federal note: Use any code. Administrative change.

DS identifies specific codes 

to be used for DLMS.

Revision 

required.

25 2/FST03/410 Add DLMS note: For DLMS, only the 

following codes are authorized.

Administrative. No 

impact.
8 of 11

ADC 139 

Attachment

Item 

#

Location DS 830R Revision Reason Federal 

IC

Add qualifier M:

M Monthly Bucket (Calendar Months)

DLMS Note:

 Use in DLA-unique demand data 

exchange transactions to submit up to 60 

months of forecast data. DLMS 

enhancement; see introductory DLMS 

note 4a.

Add qualifier Q:

Q Quarterly (Calendar Quarters)

DLMS Note:

Use in demand data exchange transactions to 

submit up to 20 quarters of forecast data. 

DLMS enhancement see introductory DLMS 

note 4a.

Add qualifier S:

S Semi-Annual (Calendar Year)

DLMS Note:

Use in Demand Data Exchange transactions 

to submit up to 10 semi-annual periods of 

forecast data. DLMS enhancement; see 

introductory DLMS note 4a.

26 2/FST03/410

Add qualifier A:

Z Mutually Defined

A Annually (Calendar Year)

DLMS Note:

Use in Demand Data Exchange transactions 

to submit up to 5 annual periods of forecast 

data. DLMS enhancement; see introductory 

DLMS note 4a.

Adds time intervals required 

by Demand Data Exchange 

process.

DLMSO Comment: ANSI 

may suggest use of existing 

code A Annually 

(Calendar Year)

DLA response to PDC 131: 

qualifier for “Yearly” or 

“Annual:” Either qualifier 

is acceptable to the DLA 

BSM Collaboration Team.

No 

impact.

 (4) DoD 4000.25-M, DLMS: Procedures for demand data exchange will be added to 

DLMS, Volume 2, Chapter 2, and the chapter name revised to: Special Program Requirements 

and Demand Data Exchange Requirements.

4. REASON FOR CHANGE: This change is required to support BSM Customer 

Collaboration interface transactions. DLA considers the change DLA unique, however, 

DLMSO notes it requires Service interface and Service submission of demand data exchange 

information making it an inter-Component process.

5. ADVANTAGES and DISADVANTAGES:

 a. ADVANTAGES: This change:

(1) Supports DLA’s BSM Customer Collaboration processes, by providing an 

interface transaction to communicate collaboration customers’ forecast data to DLA.
9 of 11

ADC 139 

Attachment

(2) Ensures that DLA BSM supports the customer’s requirements in a timely manner.

(3) Aids DLA BSM Release R2.1.2 implementation.

(4) Ensures DAASC translator map for DS 830 accurately translates collaboration 

customers’ DI Code CDD transaction sets for BSM E-Gate.

 b. DISADVANTAGES: None specifically identified; however additional changes may be 

required as BSM Planning/Collaboration development moves forward, to modify or enhance 

the transactional exchange as outlined in this change.

6. IMPACT: 

a. New DLMS Demand Data Exchange procedures

b. New DLMS Supplement 830R requirements

c. DAASC mapping for DLA-unique DI Code CDD to new DS 830R

d. Automated information system impact for those Components implementing this 

process.

7. PDC 131 Comments and Disposition. The following comments were received to PDC 131:

Component Comment Disposition

1 USAF The AF has discussed this interim approach with the 

organizations involved and DLA and agree that 

demand forecasting will be handled by RFM using 

the new DIC CDD and there are no issues that 

cannot be worked out.

Noted.

2 DLA Attachment, paragraph 3c(3), item 7 (1/BFR13/020): 

Proposed DLMS Note: “Exception Date. Use only 

with 2/LIN01/010 codes “A,” “B,”,“C.”, or “H”. Use 

only when exception data is to be provided.”

Change made.

3 DLA Attachment, paragraph 3c(3), item 9 (2/LIN01/010/E): 

The DLA BSM Planning Team has no planned ability 

to inquire against a previously submitted Demand 

Data Exchange transaction.

Code E withdrawn for use 

with demand data 

exchange.
10 of 11

ADC 139 

Attachment

Component Comment Disposition

4 DLA Attachment, paragraph 3c(3), item 18 (2/LQ01/400), 

Planning Code: DLA can provide neither a list of 

Planning Codes nor a source for those codes, since 

this is an optional field that the customers may use 

as they see fit. There should be no problem if 

different submitters use the same code for different 

purposes, since the DDE comes in at 

submitter/customer/ship-to level. Accordingly, 

although the data will be meaningful to the customer 

and will be visible to them in the Collaborate web 

tool; it won’t necessarily be meaningful to DLA. 

DLMSO will pursue an 

ANSI qualifier, but may 

not be successful 

without a code source or 

code list.

DLMSO added a DLMS 

note to DS 830R 

(2/LQ01/400 ZZ) to 

include information from 

the DLA comment 

emphasizing the code is 

intra-Component for 

optional use as deemed 

necessary by the 

Component.

5 DLA Attachment, paragraph 3c(3), item 26 (2/FST03/410/Z), 

qualifier for “Yearly” or “Annual:” Either qualifier is 

acceptable to the DLA BSM Collaboration Team. Upon 

final determination, request DLMSO advise J-3731 so that 

the DI Code “CDD” format provided J-6^ may be modified.

DLMSO used existing ANSI 

qualifier for ‘annually’.

6 DLA Enclosure 1, RP 1013-1062: Description should state “50” 

positions instead of “20.”

Change made.

7 DLA Enclosure 2, paragraph CX.1.1: Recommend paragraph 

be replaced by the following: “Purpose. This chapter 

provides procedures for the exchange of demand forecast 

data between DLA and DOD customers. The two 

components of this business process are the transmission 

of customer requirements via Demand Data Exchange 

(DDE)/ and DLA/Customer Collaboration. Business rules 

for the submission and processing of DDE will be 

documented in a DLA Customer support agreement. This 

agreement must be in place prior to the initial submission 

of DDE. DDE/Collaboration will be used to improve the 

accuracy of DLA’s demand planning to support customer 

requirements.”

Change made, with the 

exception of creating a new 

acronym.

8 DLA Enclosure 2, paragraph CX.1.2, revise 1st sentence as 

follows: “Forecasting activities . . . future requirements 

expected to be obtained from DLA using DLMS . . ..”

Change made.

9 DLA Enclosure 2, paragraph CX.1.2, revise 2nd sentence 

as follows: “Separate . . . projected dates that the 

material will be ordered from DLA, following . . ..”

Change made.

10 DLA Enclosure 2, paragraph CX.1.2, delete 3rd sentence. Change made.
11 of 11

ADC 139 

Attachment

Component Comment Disposition

11 DLA Enclosure 2, paragraph CX.1.2, 4th sentence: 

change “should” to “may” and delete “Provisioning, 

recurring type” from the list.

Change made.

12 DLA Enclosure 2, paragraph CX.2.1, delete existing 2nd

sentence and replace with the following: “Demand 

forecasting date should be submitted by the 1st of the 

month with a buffer until the 6th day of the month to 

accommodate transmission errors or failures.”

Change made.

13 DLA Enclosure 2, paragraph CX.6, 3rd sentence, change 

“20”th” to “16 th.” 

Change made.

14 DLA Enclosure 2, paragraph CX.6, 4th sentence, change 

“29th” to “25th.”

Change made.

Enclosures:

1. CDD Format

2. DOD 4000.25-M, DLMS, procedures
1 of 2

ADC 139

Enclosure 1

CDD format

ENCLOSURE 1 TO ADC 139

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

and Non-Recurring Demand Data) (Supply/DLMS)

DLA-Unique Demand Data Exchange 

Record 

Position

Description Sample Contents

1-3 Transaction Type (REQUIRED). 

This field will contain a constant “CDD” to indicate a

 Collaboration Demand Data exchange transaction.

Constant “CDD.”

4-6 Source of Supply (SOS). (REQUIRED).

Self-explanatory.

Constant “SMS.”

7-12 Submitter DODAAC (REQUIRED).

This field will contain the DODAAC of the Submitting

 Organization.

E.g., “WK4123,” etc.

13-18 Customer DODAAC (REQUIRED).

This field will contain the DODAAC of the Customer 

 Organization.

E.g., “WK4456,” etc.

19-24 Ship to DODAAC (REQUIRED). 

This field will contain the DODAAC of the Ship to

 Organization

E.g., “WK4789,” etc.

25-33 Material Number (NIIN) (REQUIRED). E.g., “123456789,” etc. 

34-35 Unit of Measure (Unit of Issue) (REQUIRED). E.g., “EA,” etc.

36-40 Planning Code (OPTIONAL).

Still under development. 

E.g., “XXXXX,” etc.

41-45 Supply Plan Start Date (REQUIRED).

The Julian Date the Supply Plan will begin.

E.g., “05001,” etc.

46-50 Supply Plan End Date (REQUIRED).

The Julian Date the Supply Plan will end.

E.g., “06365,” etc.

51 Supply Plan Type (REQUIRED). Initial default will be

 monthly.

M=Monthly

Q=Quarterly

S=Semi-Annually

Y=Yearly

I.e., “M,” “Q,” “S,” or “A.”

52-951 Supply Plan Period Quantities (REQUIRED).

This field will contain up to 60 separate Supply Plan

quantities of 15 positions each, right-justified and zerofilled, to 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.

E.g., “000000000000100,” etc.

952 Supply Plan Removal Code (OPTIONAL).

When the submitter wants to remove the item from the

 collaboration efforts, this field should contain an 

“R” to indicate that this NIIN should be deleted.

I.e., “R.”

953-972 Optional Field 1 (20 Positions) (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 collaboration tool.

E.g., “A10 weapon system,” etc.
2 of 2

ADC 139

Enclosure 1

CDD format

Record 

Position

Description Sample Contents

973-992 Optional Field 2 (20 positions) (OPTIONAL). 

See Optional Field 1.

E.g., “Spt Spc: Anna Campbell,” 

etc. 

993-1012 Optional Field 3 (20 positions) (OPTIONAL). 

See Optional Field 1.

E.g., “Major System Overhaul,” 

etc.

1013-1062 Optional Field 4 (50 positions) (OPTIONAL). 

See Optional Field 1.

 
DoD 4000.25-M

1 of 3

ADC 139

Enclosure 2

DLMS Procedures

ENCLOSURE 2 TO ADC 139

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

Forecasts of Recurring and Non-Recurring Demand Data) (Supply/DLMS)

[DLMSO NOTE: These procedures will be added as a section to DLMS Volume 2, chapter 2

(Changes from Proposed DLMS Change 131 are identified by red text with double underscore

or, for deletions, double strike-thru)]

DEMAND DATA EXCHANGE

CX.1 GENERAL

 CX.1.1 Purpose. This chapter provides procedures for the exchange of 

demand forecast data between DLA and DOD customers. (i.e., customer 

collaboration). Data exchanged will be used to improve the accuracy of future 

demands. Customer collaboration using Demand Data Exchange will include 

items in support of both repetitive and nonrepetitive programs or projects. 

The two components of this business process are the transmission of customer 

requirements via Demand Data Exchange and DLA/Customer Collaboration. 

Business rules for the submission and processing of demand data exchange will 

be documented in a DLA customer support agreement. This agreement must be 

in place prior to the initial submission of demand data exchange. Demand data 

exchange/collaboration ill be used to improve the accuracy of DLA’s demand 

planning to support customer’s requirements.

 CX.1.2 Demand Data Exchange Transaction Sets. Forecasting activities 

may submit to DLA their forecasts/collaboration data for future expected 

requirements expected to be obtained from DLA using DS 830R. Separate 

forecasts into monthly periods based on the projected need dates that the 

materiel will be ordered from DLA, following the prescribed format. All future 

requirements should be included. Types of demands for which collaboration data 

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

Provisioning, recurring type

War Material Requirements

Requirements for which the DOD Component has a recurring demand

Subsistence, all categories

One-time training exercises or maneuvers
DoD 4000.25-M

2 of 3

ADC 139

Enclosure 2

DLMS Procedures

Repair or rebuild programs which are either nonrecurring or which are seldom 

or irregularly programmed

New constructions (ships, buildings, etc.)

One-time alterations, modifications, or conversion programs

Initial issue of existing items (i.e., outfittings, activations, and changes in 

authorized allowances)

Initial requirements for special operational projects

Requirements for initial testing

Requirements for Government-furnished property

Requirements for infrequently planned support operations such as Arctic and 

Antarctic resupply missions

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.)

CX.2 DEMAND DATA EXCHANGE SUBMISSION AND ROUTING

 CX.2.1 Submission Timeframe. DS 830R forecasts should be submitted 

each month. The window for submission of demand forecasting data is between 

3 calendar days prior to each month’s end and the first day of the next month. 

Demand forecasting date should be submitted by the 1st of the month with a 

buffer until the 6th day of the month to accommodate transmission errors or 

failures.

 CX.2.2 Forecasting. Forecasting activities will prepare a DS 830_ for each 

item (i.e., National Item Identification Number (NIIN)/Material Number) for which 

the customer wishes to collaborate with DLA. Each transaction set will include 

the forecast period beginning date and the forecast period ending date. The 

forecast period spanned can be as little as twelve (12) months or as much as 

sixty (60) months.

CX.3 DEFENSE AUTOMATIC ADDRESSING SYSTEM CENTER (DAASC) 

PROCESSING

 CX.3.1 Source of Supply (SOS). DAASC will route all DDE transactions to 

DLA’s Enterprise Processing Center, SOS “SMS.”

CX.4 DLA VALIDATION
DoD 4000.25-M

3 of 3

ADC 139

Enclosure 2

DLMS Procedures

 CX4.1 Validation of NIIN/Material Number. DLA will screen transaction sets 

and will only accept for processing valid NIIN/Material Numbers.

CX.5 DLA PROCESSING OF DEMAND DATA EXCHANGE DATA

 CX.5.1 Source of Supply Risk. DLA will compare the collaboration 

customer’s forecast to the projected customer forecast calculated by the 

Planning and Collaboration Subsystem (i.e., Manugistics).

• Those items that exceed system tolerance parameters will be flagged 

for collaboration interaction with the customer and the customer will be 

notified.

• Items previously identified for inclusion in DDE that are not in the 

current DDE submission will be flagged for review. If the customer has 

indicated he wishes the item removed from the DDE effort by 

annotation of a “C” in 2/LIN01/010 the review flag will not be set and 

the item will be removed from the DDE/Collaboration effort. 

• The setting of system tolerance parameters used in this review 

requires consideration of the following: size of the forecasted quantity 

in relation to the Planning and Collaboration Subsystem forecasted 

demand for the item; the value (cost) of the forecast quantity; the 

supply status of the item being forecasted; funding capabilities; 

accuracy of customer’s past forecasts; and the degree of assurance 

that requisitions will follow.

CX.6 COLLABORATION EFFORTS

 CX.6.1 Collaboration Interaction. Those items that exceed system tolerance 

parameters will be flagged for collaboration interaction with the customer. The 

point of contact for the customer will be alerted to the need for collaboration via 

e-mail. The customer will have until the 16th 20th of the month to complete his 

review and response to the collaboration request. The DLA Demand Planner will 

then have until the 25th 29th day of the month to complete his review and publish 

the demand plan for inclusion in the supply plan.