DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J . KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

April 14, 2015 

:MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) :MEMBERS 

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

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

provide an FST04 Date Representing the Start Date of Forecast Bucket (Supply) 

The attached change to Defense Logistics Manual (DLM) 4000.25, Defense Logistics 

Management Standards is approved for immediate implementation. The updated DLMS 

implementation convention (IC) will be posted to DLMSO Web site at 

www.dla.mil/j-6/dlmso/elibraryffransFormats/fonnats.asp within I 0 days from the above date. 

At this time, the Defense Logistics Agency (DLA) has not yet implemented DLMS for DDE 

Projected Supply Plan. DLA must advise DLMSO of their implementation timeframe for 

DLMS 830D. DLA implementation of DLMS 830D requires coordination with DLA 

Transaction Services. 

Addressees may direct questions to Mary Jane Johnson, (703) 767-0677; DSN 427-0677 or 

email: Mary.Jane.Johnson@dla.mil. Others must contact their Component designated Supply PRC 

representative available at https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp 

Attachment 

As stated 

cc: ODASD (SCI) 

~M~ 

~~~far ~LJ~.fw~ Defense Logistics Management 

Standards Office 
Attachment to ADC 1138

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

to Provide an FST04 Date Representing the Start Date of Forecast Bucket

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Program Management Office, Logistics Modernization Program 

(PMO LMP), 862-259-0186 

b. Functional POC: PMO LMP, 973-724-9335

2. FUNCTIONAL AREA: Primary: Supply

3. REFERENCES:

a. Approved DLMS Change (ADC) 1105, Revise DLMS 830D Demand Data 

Exchange (DDE) Projected Supply Plan Requirements to Clarify Data and Associated 

Procedures, April 17, 2014, www.dla.mil/j-6/dlmso/eLibrary/changes/approved1100.asp

b. DLMSO Director email, February 19, 2014, subject: Demand Forecasting Recap 

of Telecon 19 Feb 14

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

Standards and Procedures, www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp

4. REQUESTED CHANGE(S):

a. Overview of Change: This change incorporates the use of the actual forecast date,

aligned to the forecast quantity for that date, in the Demand Data Exchange DDE Projected 

Supply Plan (DLMS 830D) transaction. Army will continue populating the forecast date 

associated with the monthly bucket, with the understanding that DLA will implement the same 

when DLA implements DLMS 830D. Until DLA implements DLMS 830D, DLA Transaction 

Services will continue to ignore that date populated by Army in the translation to DLA’s legacy

format, and only read the currently populated date of the beginning of the entire forecast.1

b. Background: 

(1) Under the current DLMS 830D Implementation Convention (IC), the 

FST04 (Date) element is required to be the same as the projected supply plan period start date 

(beginning segment BFR06 date). The FST04 DLMS Note in the 830D IC states that use of 

FST04 as other than BFR06 date functionality is a DLMS enhancement and Components must 

coordinate requirements and business rules with the Defense Logistics Management Standards 

Office prior to use.

1 DLA’s legacy format is a DLA-unique Document Identifier Code (DIC) CDD fixed format transaction.

Attachment, ADC 1138 

Page 1

 
(2) During the initial Army implementation of DLMS 830D with DLA, Army 

populated the FST04 date as corresponding to the forecast quantity (i.e., the start date for each 

forecast bucket), rather than the start date for the entire forecast (as reflected in BFR06). This 

was a misinterpretation of the IC requirement and DLA Transaction Services did not recognize 

intelligent forecast dates that Army populated in the FST04. The current DLMS 830D IC 

requirement does not use FST04 as a date representing the start of each forecast bucket, 

therefore, the IC requires an iteration of the 2/FST/4100 segment for each of the sixty months of 

the forecast period, regardless of any periods that may have zero quantity. Army believes that 

populating the forecast date corresponding to each forecast quantity is a true DLMS 

enhancement that should be implemented. Army proposed such use be authorized by an ADC

for those DOD Components that are DLMS compliant and use DLMS 830D, with the 

understanding that DLA and DLA Transaction Services will not use the FST04 date in this 

manner immediately, since DLA has not yet implemented DLMS for this process. Army’s 

proposed use of FST04 is consistent with the 830D Accredited Standards Committee (ASC) X12 

FST Segment comment, which states that, when used with forecast buckets (e.g., weekly, 

monthly, quarterly, etc.), FST04 represents the first date of a forecasted bucket. As a result of 

the initial Army implementation of the 830D DDE Projected Supply Plan, DLMSO published 

ADC 1105 (Reference 3.a.) to further clarify the current intended purpose of each of the data 

elements in question.

(3) The implemented procedures in use today are:

(a) The DDE Projected Supply Plan transactions are sent by Army 

Logistics Modernization Program (LMP) to DLA Enterprise Business System (EBS) via DLA 

Transaction Services in DLMS 830D format. The 1/BFR06/0200 data element indicates the 

starting date for the forecast. For a five year monthly forecast, there is an iteration of the 

2/FST/4100 loop for each of the sixty (60) months of the forecast, in consecutive order. All 

FST04 elements prepared by Army LMP currently contain the forecast date corresponding to the 

quantity bucket, even if it is zero quantity. It is understood that DLA Transaction Services uses 

the BFR06 date, so there would be limited value in LMP changing its functionality. 

(b) DLA EBS is not yet DLMS compliant for DDE Projected Supply Plan. 

Therefore, DLA requires that DLA Transaction Services translate DLMS 830D into the legacy 

DLA-unique DIC CDD fixed format transaction, using the date in BFR06 to populate the starting 

date of the forecast in the legacy CDD record positions 41-45. DLA has not yet implemented the 

DLMS 830D, but has committed to doing so per Reference 3.b.

(c) DLA Transaction Services sends formatted legacy DLA DIC CDD 

transactions to DLA EBS.

c. Approved Change in Detail:

(1) Modify the DLMS 830D FST04 data element to identify the forecast date of 

the quantity in FST01 (i.e., the start date of a forecasted monthly bucket). Forecast horizon start 

date will continue to be identified in the beginning segment at BFR06. 

Attachment, ADC 1138

Page 2
(2) There will continue to be sixty (60) FST loops for the five-year monthly 

buckets to align with the current requirement to include zero quantity segments in FST01.

(3) Army considers this change is an interim step. To achieve true utilization of 

the DLMS format, only having required quantities (i.e., non-zero) and dates populated in the 

DLMS 830D transaction is the next logical step; this would require a new PDC to propose 

updated business rules and notify systems to make the changes.

d. Revisions to DLM 4000.25 Manuals: Revise DLMS 830D as shown below:

# Location DLMS 830D Change Table 

(Change identified by bold text or double strikethrough)

Reason

1. DLMS 

Introductory 

Note

Revise DLMS Introductory note 4 to add change:

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

Projected Supply Plan to provide an FST04 Date Representing the 

Start Date of Forecast Bucket (Supply)

To identify DLMS 

changes included in 

the implementation 

convention.

2. 2/FST04/4100 Revise FST04 DLMS Notes:

DLMS Note: 1. Must use to identify the start date for which materiel 

support should be available for the NIIN cited in LIN02/03 for the

forecast bucket (e.g., weekly, monthly) identified in FST03 for the 

associated quantity in FST01. This date corresponds to the 

1/BFR06/0200 start date. Authorized DLMS migration 

enhancement. Refer to ADC 1138.

2. Until such time as DLA implements DLMS 830D, the DLA legacy 

fixed format DIC CDD cannot use this date and the forecast bucket 

dates will not be mapped to the legacy transaction. However, all 

DLMS implementations must use the start date for the bucket to 

position the input for DLA’s planned implementation of DLMS 

830D.

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

To allow 

Components that 

have implemented, 

or plan to 

implement, DLMS 

830D to use FST04 

consistent with FST 

segment ASC X12 

comment that as 

qualified by FST02 

and FST03, FST04 

represents the first 

date of a forecasted 

bucket (weekly, 

monthly, quarterly, 

etc.).

c. Alternatives: Require Army to populate all FST04 data elements with the BFR06

date. This could cause Army to lose sight of the requirement when it is required on the horizon, 

and additional coding will be required by Army in the future.

5. REASON FOR CHANGE: Aligns DLMS use of FST04 with the intended Accredited Standards 

Committee (ASC) X12 use. Prepares Army for the full DLMS mapping in the future and allows 

Army to always have visibility of when the forecast requirement quantities are required.

Attachment, ADC 1138

Page 3
6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) Army advises that currently DLA Transaction Services does not read the 

FST04 data element, so no negative impacts should be seen on the conversion.

(2) Supports the ASC X12 intent for FST04. The 830D FST Segment Comments 

state: “As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the 

first date of a forecasted bucket (weekly, monthly, quarterly, etc.), or the start date of a 

flexible interval.”

b. Disadvantages: DLA EBS and DLA Transaction Services programming changes 

will be required when DLA implements DLMS 830D for this function (implementation date 

unknown at this time), however, DLA is required to implement DLMS for this process, 

independent of this proposal.

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

DEVELOPMENT:

a. The current DLMS 830D Implementation Convention FST segment strategy is based 

on DLA legacy system and CDD format requirements and limitations. As other systems become 

DLMS compliant, additional changes to the mapping and conventions for the DLMS 830D may 

need to be implemented. Possible future changes include proposing the inclusion of only nonzero quantity forecasts over the 60 month period (i.e., fewer than 60 FST iterations for a 5 year 

forecast), as well as removing the requirement for the FST segments to be in chronological order, 

as the actual date is already provided.

b. Per the telecon referenced in reference 3.b., DLA J33 agreed to initiate a system 

change request to use the DLMS 830D transaction for DDE Projected Supply Plan, in lieu of 

DLA’s legacy DIC CDD 1,062 character transaction. This effort will ensure DLA becomes 

DLMS compliant with respect to this process.

8. ADDITIONAL COMMENTS TO CONSIDER:

a. This change formally approves the current Army use of the FST04 data element to 

be the date associated with the quantity in the corresponding FST01 data element, and provide 

for future implementation of same by DLA and DLA Transactions Services, when DLA 

implements DLMS 830D.

b. DLMS 830D and DLM 4000.25-2, Volume 2, do not currently authorize the use of 

fewer than 60 consecutive months (for a 60 month forecast period) of forecast data, to exclude 

months with zero plan data. Army may submit a future PDC to propose this capability.

c. No immediate AIS impact for DLA EBS and DLA Transaction Services; impact will 

coincide with DLA’s implementation of DLMS 830D. Immediate impact is Army continues to 

populate FST04 with the monthly bucket date, consistent with the ASC X12 intent for FST04, 

and DLA Transaction Services continues to ignore initially as they use BFR06 date. However,

Attachment, ADC 1138

Page 4
if approved, a future implementation date will need to be established for DLA. Otherwise, 

there will be two disparate requirements for FST04 with no plan to move forward to a standard 

solution. Accordingly staggered implementation is appropriate. The standard solution is 

addressed in this ADC, and DLA must provide an implementation target for becoming DLMS 

compliant with implementation of DLMS 830D. Essentially this change has 2 parts:

(1) Army LMP continued use of the FST04 monthly bucket date as they have 

been doing, with no negative impact to DLA EBS and DLA Transaction Services, which 

continue to use BFR06 date for FST04, and 

(2) DLA implementation of DLMS 830D at a date to be determined, with use 

of the FST04 bucket date consistent with Army approach and the ASC X12 intent for FST04. 

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET (the DoD Components 

provided the yellow highlighted text in response to the PDC):

a. DLA: DLA must advise DLMSO of target implementation date to become DLMS 

compliant and implement DLMS 830D, with ability to recognize the intelligent FST04 date. 

DLA implementation of DLMS 830D will require coordination with DLA Transaction Services.

In addition, DLA must address the EMALL impact as noted in paragrapgh 10.b.(2). 

DLA will be setting up a meeting with DLA J6 to look into implementing DLMS 830D. DLA 

will provide DLMSO with an implementation update as soon as it is available

b. Army: Army is currently populating the FST04 date as described in this change;

accordingly Army implementation would be immediate and coincide with the ADC date. 

c. Air Force, Navy, and Marine Corps: This change is effective immediately for 

Air Force, Navy, and Marine Corps, since they have not yet implemented DLMS 830D. 

Those Services would include the intelligent FST04 date in their implementations, even if 

DLA has not yet implemented DLMS 830D to accept/process the date. DLMSO requested

Air Force, Navy, and Marine Corps advise if DLMS 830D implementation is already 

underway at this time, and impacted by this change; responses follow:

(1) Marine Corps has not yet begun implementation of DLMS 830D and there is 

no impact from this change.

(2) Navy has no development currently underway to send the 830D.

(3) Air Force concurred without comment.

10. IMPACT:

a. New DLMS Data Elements: New usage of the ‘Date - Forecast Bucket Start’

(FST04) data element. Represents the first date of a forecasted bucket

b. Automated Information Systems (AIS): Army LMP will continue to process 

DLMS 830D transactions as it currently does and DLA EBS will continue to receive and process 

them as it does currently.

Attachment, ADC 1138

Page 5
(1) DLA: DLA is required to implement DLMS 830D to become DLMS

compliant. Coinciding with DLA’s implementation of DLMS for DDE Projected Supply Plan, 

DLA will implement the intelligent FST04 date consistent with this change and the ASC X12 

intent that FST04 represents the first date of a forecasted bucket (weekly, monthly, quarterly, 

etc.). DLA must coordinate its implementation of DLMS 830D with DLA Transaction Services 

due to the impact.

(2) EMALL: DLA provides an EMALL screen for customers to upload legacy 

DDE Projected Supply Plan transactions using the DLA unique fixed format transaction. When 

DLA implements DLMS 830D for DDE Projected Supply Plan, DLA must address impact on 

the EMALL input, to include the change addressed by this ADC. This EMALL impact was not 

noted in the PDC.

(3) Army: No impact. Army LMP will continue to process DLMS 830D 

transactions as it currently does. Army currently populates the intelligent FST04 date described in 

this change, but that date is not read by DLA Transaction Services since the date cannot be 

translated to the non-DLMS compliant, DLA-unique DIC CDD transaction currently used by DLA.

c. DLA Transaction Services: No immediate changes to DLA Transaction Services maps 

are required, as they do not currently read the FST04 data elements. However, as DLA implements 

DLMS 830D, DLA Transaction Services will be required to read the FST04 dates as described in 

this change. Accordingly, impact will coincide with DLA implementation of DLMS 830D.

d. Non-DLM 4000.25 Series Publications: None identified.

11. PDC 1138 Staffing Response/Comment Resolution:

Originator Response/Comment Disposition

1. Air Force Concurs without comment. Noted.

2. Army Concurs without comment to PDC as written. Noted.

3. DLA Concurs without comment. 

Regarding the 830D implementation target, DLA will be setting 

up a meeting with DLA J6 to look into implementing 830D.

Noted.

4. Marine Corps Concurs with PDC as written.

Marine Corps has not yet begun implementation of DLMS 830D 

and there is no impact from this change.

Noted.

5. Navy Concur.

No Navy development currently underway to send the 830D.

Noted.

6. USTRANSCOM Abstains. No impact to USTRANSCOM systems based on this 

change.

Noted.

Attachment, ADC 1138

Page 6