1. Defense Logistics Management Standards (DLMS) Introductory Training
DLMS Functionality &
Transaction Life-Cycle
This class will provide an introductory level instruction in EDI as applied under the Defense Logistics Management Standards (DLMS). The DLMS is a broad base of business rules supported by American National Standards institute (ANSI) Accredited Standards Committee (ASC) X12 commercial standards and is designed to meet DoD’s requirements for total logistics support.
The target audience for this class is function experts and system analysts requiring knowledge of the DLMS application of ASC X12.).
“The right item at the right place at the right time.”

2. DLMS Training Catalog Module 1 - Introduction to the DLMS
Module 2 - Electronic Data Interchange (EDI) Basics and ASC X12 EDI Definitions and Concepts
Module 3 - DLMS Functionality & Transaction Life-Cycle
Module 4 - DLMS Implementation Convention Content
Module 4F - DLMS Functional Financial Transaction Life-Cycle
Module 5 - IUID & RFID - Emerging Technologies
Module 6 - Creating/Reengineering DOD Logistics Business Processes
Module 6A - DLMS Configuration Management (stand alone Module)
Module Enterprise Interoperability Tools
Module DoD Activity Address Directory (DoDAAD)
Module 9 - Supply Discrepancy Reporting (SDR)

3. Module 3 Structure DLMS Functionality & Transaction Life-Cycle
Relationship Between the DLMS EDI & DLSS
DLMS Functionality by Transaction
DLMSO Web Site Navigation

4. Module 3 Objectives Students will gain a basic understanding of:
Relationship of the DLMS and DLSS data formats
High level functionality of the DLMS
Relationship among DLMS business transactions
Breadth of functionality covered by the DLMS
Functional and data enhancements afforded by DLMS
How to navigate the DLMSO web site as a DLMS resource

5. Data Relationship Between the DLMS EDI and the DLSS 80 Record Position Fixed Length Data Field formats
What we are about to undertake now is an overview of the DLMS processes and transaction flow. Time wont permit a detailed look at all the functional areas and individual transactions, but I’ll highlight many of the high volume transactions and touch on some of the enhancements supported by the DLMS

6. EDI Document Structure
RPs Field Legend Sample Data
Document Identifier A01
Routing Identifier SMS
07 Media and Status B
Stock Number
Unit of Issue EA
Quantity 1
Document No FB
Demand R
Supplementary Address
Signal A
Fund KZ
Distribution
Project 9GF
Priority
Reqd. Delivery Date
Advice 2A
Blank (Date of Rcpt on Referral/Passing Order)
Blank (Intra-Service use)
The DLSS Fixed Format Requisition
MILS Format
ST*511* ^
BR*00*A0* ******131708^
N1*OB**10*FB2300**FR^
LX*1^
N9*TN*FB ^
PO1**1*EA***FS* ^
DD*R*74^
LM*DF^
LQ*0*A01^
LQ*78*9GF^
LQ*79*08^
LQ*80*2A^
LQ*DE*A^
LQ*DF*B^
LQ*AL*777^
N1*Z4**M4*SMS**TO^
FA1*DY*D340^
FA2*B5*KZ^
SE*14* ^
DLMS EDI Format
EDI document structure is an electronic version of a paper document
Paper-based system
Business document is created and printed on a standard form
Header area contains information pertaining to the entire document
Detail area contains information pertaining to the document items
EDI or electronic-based system
An electronic version is created
Instead of printing on standard form, information is in standard ANSI X12 or EDIFACT format
EDI version is functionally identical to the paper document

7. DLMS transaction/DLSS Transaction Relationship
DLSS Document Identifier Code (DIC)
DLMS 527R – Receipt
D4M/D4S/D4U/D4V/D4X/D4Z/
D6A/D6B/D6C/D6D/D6E/D6G/D6H/D6J/
D6K/D6L/D6M/D6N/D6Q/D6R/D6T/D6U/
D6V/D6X/D6Z/
DRA/DRB/DRF/
DXA/DXB/DXC/DXD/
DZK
1 DLMS Transaction
33 DLSS Transactions Families
Transactions within a DLSS family:
Same first 2 characters of the Document Identifier Code
Data content nearly identical -- lots of reusability

8. DLMS Functional Transaction Life-Cycle Overview
What we are about to undertake now is an overview of the DLMS processes and transaction flow. Time wont permit a detailed look at all the functional areas and individual transactions, but I’ll highlight many of the high volume transactions and touch on some of the enhancements supported by the DLMS

9. DLMS Requisition Cycle
Retail Base
Defense Finance and Accounting Service
Distribution Depot
or Vendor
We take a look at how each of these organizations fits into the big picture for various DLMS process. First we’ll look at the requisition cycle.
Source of Supply (SOS)
ICP/IMM
USTRANSCOM

10. DLMS Requisition Cycle
Retail Base
DLSS/DICs A0_, A3_, A4_ &
C0_, CH_, CQ_, YRZ
SOS

11. DLMS 511R, Requisition Basic Functionality
Standard and non-standard materiel
Government-furnished materiel (GFM)
Security Assistance
Passing orders
Referral orders
The 511R (Requisition) transaction is used to order items of supply, to refer transactions to another supply source for processing, and to transmit misrouted transactions between supply sources. Single or multiple requisitions made be sent to one or more supply sources.
A single transaction set may contain a combination of requisitions for standard and nonstandard material. Requisitions for material to be provided as Government Furnished Material (GFM) to commercial contractors, requisitions for excess government owned plant property, and requisitions from foreign governments for material to be provided in support of Security Assistance (SA) contain distinguishing requirements which do not apply to non-GFM or non-SA requisitions.
Supply sources receiving MILSTRIP requisitions, modifiers, passing orders, referral orders, follow-ups, and cancellations, regardless of the method of transmission, will process such transactions using the procedures contained in this transaction set. Supply sources will validate the data elements and codes in these transactions and accomplish changes, continue the processing action, or reject the documents.
When supply sources and storage activities utilize the sequential (or batch) method of processing and do not possess real time processing capability, such processing is to be performed as frequently as necessary in order to meet time standards, or specific required delivery date (RDD) for subsistence requisitions, as applicable. In every such cycle, cancellation requests DI AC_, including automatic cancellation initiated by the supply source) and MOV reconciliation requests (DI AP_) will be processed prior to backorder releases and new requisitions (DI A0_).
Rejection of transactions will be accomplished only after an attempt has been made to correct the questionable data element or code. If rejection actions are applicable to more than one data element or code and no other reject status code applies, reject using Status Code CA.

12. DLMS Enhancements Transaction set preparation date/time
Supply condition code
Unit Price/Total Dollar Value
Utilization code
Special requirements code
Shipment Status
Points of contact
Remarks
Detailed line of accounting components
Associated special program requirement transaction number
Touched on some of these during earlier discussions

13. DLMS Enhancements (con’t)
Expanded item identification
Weapon system designator code
Quantity stratified by weapon system and demand code
Reason for requisitioning code
Party(ies) to receive status DoDAAC
Mark-for-Party
Unique item identification information
Clear text exception ship-to location
Unique item identification information – (See notes on slide 12)
Clear text exception ship-to location – This enhancement provide the capability for processing of automated exception requisitions that include in-the-clear ship-to addresses. The authorized system (e.g. Navy One-Touch) that prepares the requisition establishes a constant in the customer identification field that would allow the supply source to know what organization to contact to find out who the actual user is. DAAS generates the customer identification based upon the communications routing information from the originators transaction when forwarding the DLA-supported DI Code YRZ requisition trailer for exception ship-to data.

14. DLMS Enhancements Applicable to Non-Standard Material
Supporting Document No.
Color
Drawing Revision No.
Catalog Number
Series Identifier
Model Number
Figure Number
General Specification No.
Manufacturer’s Name
Process Number
Publication Number
Dimension/Measurement
Material Description
Potential Source of Supply
End Item Manufacturer
We mentioned that the 511 allows for discrete expanded information pertaining to non-standard material. Here we see a list of some of the data elements.

15. DLMS 511R, Requisition After initial submission . . . . .
Once the requisition itself has processed, there are several related transactions which may be needed to modify, cancel, or follow-up.

16. DLMS Requisition Cycle
2a. Supply Status
DLMS 940R
Retail Base
DICs A5_
2b. Material Release
Order
SOS
DLMS 870S
DICs AE_
Distribution Depot
or Vendor

17. DLMS Requisition Cycle
Retail Base
2b. MRO
SOS
3a. Material Release Confirmation
2a. Supply Status
DLMS 945A
3b. Shipment Status
DICs AR_
DLMS 856S
Distribution Depot
or Vendor
DICs AS_

18. DLMS Requisition Cycle
2a. Supply Status
Retail Base
2b. MRO
SOS
3a. MRC
3b. Shipment Status
Distribution Depot
or Vendor
Materiel Shipment
4. Movement Document Transaction

19. Transportation
USTRANSCOM leading transportation reengineering efforts DoD goal is a paperless business environment using e-Business Wide range of transportation specific ICs ANSI ASC X12 is Procedures governed by DTR

20. DLMS Requisition Cycle
5. Material
Receipt
Acknowledgement
Retail Base
DLMS 527R
DIC DRA
2b. MRO
SOS
3a. MRC
2a. Supply Status
3b. Shipment Status
Distribution Depot
or Vendor
Materiel Shipment
4. Movement Document Transaction

21. DLMS Requisition Cycle
6. Logistics Bill
DLMS 810L
DICs GS_
Retail Base
DFAS
(Acting as
Customer’s Agent) $
MRA
2b. MRO
SOS
3a. MRC
2a. Supply Status
3b. Shipment Status
Distribution Depot
or Vendor
Material Shipment
4. Movement Document Transaction

22. Receipt Processing (New Procurements)
SOS
Electronic
Order
1a. Establish
Due In
Vendor
3a. Receipt
DLMS 527D / DICs DD_
2a. Materiel
Shipment
WAWF 856 ASN
DLMS 527R / DICs D4_
1b. Pre-positioned
Materiel Receipt
3b. Materiel
Acceptance
iRAPT
DLMS 527D / DICs DU_
DLMS 861
2b. Materiel
Shipment
Distribution Depot
DLMS 856 ASN

23. Physical Inventory Control ProgramII
1. Physical
Inventory Request
DLMS 846P / DIC DJA, DZJ
SOS
4. Location Reconciliation
Transaction Count
DLMS 846R /
DIC DZP
4. End of Day (EOD)
Transaction Count
DLMS 846P / DIC DZM
3. Transaction History
DLMS 527R, 940R,
945A & 947I /
DIC DZK
3. End of Day Process
DLMS 846R / DIC DZH
2. Location Reconciliation
DLMS 846R / DICs DZJ & DZK
2. Inventory Gain/
Inventory Loss
DLMS 947I / DIC D8_ & D9_
1. Location Reconciliation
Notification
DLMS 846R /
DIC DZN
I = ICP-initiated Physical Inventory Request
II = Location Reconciliation
III = Depot-initiated Physical Inventory Request
III
1. Physical
Inventory Request
Supply Depot
DLMS 846P / DIC DJA or
Internally System Generated

24. Sample of DLMS Enhancements
Automation of previously manual processes such as Supply Discrepancy Reporting (SDR) DLMS 842A/R
Mass transaction modification and cancelation capability– previously addressed by single line item or requested off-line
Separately identify supply & transportation priorities
Transmission to recipients of Radio Frequency Tag Identifier (RFID) at multiple tagging indenture levels
Transmission of Unique Item Identifier (UII) of items
Capability to transmit clear text exception data
Capability to transmit detailed Contract, Storage data, etc.
Inclusion of Component unique data
Current data enhancements by DLMS Implementation Convention published on DLMS Web site.
The 861 Acceptance Report transaction is a Federal IC that provides additional functionality to include the ability to capture UID information consistent with UID policy and establishes a DS for DLMS use in reporting acceptance. The DS captures the UID for those items accepted allowing the WAWF-RA to transmit required UID register information to the Defense Logistics Information Service.
The 861 also identifies a new Shipment/Acceptance Discrepancy Explanation Code for the purpose of identifying a discrepancy condition related to the UID information.

25. DLMS GFP Accountability Enhancements
New transaction data & business rules required by ADC 390, and 1014A:
Full DFARS contract number data in GFP requisitions DLMS 511R.
Include contract data in the DLMS 527R Receipt and MRA transactions.
MCA or DAAS when acting on behalf of the MCA perpetuate contract number data in requisition 511R and MCA Validation DLMS 517G.
Source of supply (SOS) perpetuate the GFP contract data in the Materiel Release Order (DLMS 940R) sent to supply depot for stock issues.
Shipping activity or SOS, as applicable, to perpetuate the GFP contract number data to the shipment status (DLMS 856S).
Contractors using DLMS transactions & shipping GFP into DoD inventory identify GFP contract data in shipment status transaction (DLMS 856S or 856R) and shipping documentation.
Include contract data in the DLMS 940R when used to direct reparables for induction to commercial maintenance & perpetuate contract data in status trans.
Contract number on the DLMS 856S, Shipment Status, when used for DD requirements and shipping to a contractor as GFP.
Stock issues require the shipping activity to identify the GFP contract number on the Issue transaction DLMS 867I.
The 861 Acceptance Report transaction is a Federal IC that provides additional functionality to include the ability to capture UID information consistent with UID policy and establishes a DS for DLMS use in reporting acceptance. The DS captures the UID for those items accepted allowing the WAWF-RA to transmit required UID register information to the Defense Logistics Information Service.
The 861 also identifies a new Shipment/Acceptance Discrepancy Explanation Code for the purpose of identifying a discrepancy condition related to the UID information.

26. DLMS Functionality MILSBILLS MILSTRAP MILSTRIP Contract Administration
810L, 812L, 812R, FV1 (XML), FV2 (XML)
MILSTRAP
527D, 527R, 536L, 830R, 830W, 846D, 846F, 846I, 846M, 846P, 846R, 846S, 867D, 867I, 870L, 888I, 947I
MILSTRIP
180M, 511M, 511R, 517G, 517M, 856N, 856R, 856S, 869A, 869C, 869F, 870M, 870N, 870S, 940R, 945A
Contract Administration
567C, 856, 861
Discrepancy/
Deficiency Programs
842A/R, 842A/W, 842C/I, 842C/R, 842P, 842S/Q, 842S/R
Disposition Services
832N, 846C, 996H, standard MILSTRIP, MILSTRAP, MILSBILLS
BRAC IMSP
832N, 940S, 943A, standard MILSTRIP, MILSTRAP, MILSBILLS
Medical
Unit Assembly Program
650A, 650C
Small Arms/
Light Weapons
140A, 888A
Material Returns Program
180M, Material Returns Reporting
870M, Material Returns Supply Status
856R, Shipment Status Material Returns
Material Obligation Validation Program
517M, MOV
517G, Government Furnished Material MOV
Foreign Military Sales Notice of Availability
856N, NOA
870N, NOA Reply
Logistics Reassignment
536L, LR Management Data
846D, LR Transfer/Decapitalization
846S, LR Storage Transfer/Order/Reply
War Material Requirements - 830W, WMR
Special Program Requirements - 830R, SPR
Demand Data Exchange (DDE) is a new process recently approved (ADC 139 was released Jan 6, 2005) for optional use between DLA BSM and the Services. DDE information from the change proposal DLA BSM submitted follows: DDE revised DS 830R, to include DLA Business Systems Modernization (BSM) planning functionality.   DLA indicated that the capabilities and data content of the Demand Data Exchange use of DS 830R 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.    
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 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.
Asset Reclassification
846A
Demand
Data Exchange
830D
Weapon System
888W
Demand - 867D, Demand
Inventory Related Transactions
846P, Physical Inventory/Transaction History
888I, Storage Item Correction
947I, Inventory Adjustment
Small Arms/Ammunition
846F Ammunition Freeze/Unfreeze
140A, Small Arms Reporting
888A, Small Arms Data Change
Issue - 867I, Issue
Logistics Asset Support - 846L, Logistics Asset Support Estimate
Asset Status Reporting - 846I, Asset Status Inquiry/Report
General
824R, 997
Transportation/pRFID
Visibility (XML), Visibility Response (XML), Reader Registration (XML)
*Reference Tab N for details

27. The DLMSO Web Site A Valuable Resource
Navigation of the DLMSO web site

28. Easy Access To: Latest published DLSS & DLMS manuals
DLMS Implementation Conventions
DLMS XML Schemas
Process change documentation
Committee information
DLMS Dictionary
Link to Logistics Data Resources Management System (LOGDRMS) website:
Link to DLMS training
And more – worth exploring!!!
Mention .gov/.mil change

29. Quick link to the DLMS Implementation Conventions

30. Jump to a specific Transaction

31. First link is always the Implementation Convention

33. DLMS
Enhancements

34. DLMS
Enhancements for 511R

35. DLMS Enhancement Report (page 1)

36. DLMS Enhancement Report (page 2)

37. Quick link to DLSS/DLMS Cross Reference

38. DLSS/DLMS Cross Reference

39. MILS to DLMS Cross Reference Report

40. Essential ANSI ASC X12 Code/DoD Code Conversions
ANSI ASC X12 mandates use of ANSI code list values in X12 transaction transmissions where they exist
There are three ANSI Code lists that must be used in DLMS transactions
Mode of Shipment
Type of Pack
Unit of measure
DLMS Conversion guides map DoD definitions to desired X12 definitions
DoD applications must convert outbound transactions from DoD code values to ANSI code values based on DLMS Conversion Guide definitions
DoD applications must convert inbound transactions from ANSI code values to DoD code values based on DLMS Conversion Guide definitions
Once the requisition itself has processed, there are several related transactions which may be needed to modify, cancel, or follow-up.

41. DLMS Conversion Guides

42. Link to Transportation Guide

44. Listing of PDCs

46. Listing of ADCs

47. DLMS
Change
Status
Review

48. Instructions Tab of the DLMS Change Status Report

49. Sample of the DLMS Change Status Report

50. Summary DLMS provides a new logistics data exchange format
Commercial vs. DoD proprietary standard
Variable length vs. 80-record position records with fixed data lengths
W3C compliant XML schema formats
Supports new data content to meet DoD needs
Provides opportunity to reengineer logistics business processes
Supports all current and future business/electronic commerce data transmission requirements

51. Module 3 Quiz
Question 1: Which of the following are DLMS enhanced capabilities?
Automation of previously manual processes e.g. Supply Discrepancy Reporting
Mass transaction modification and cancelation capability
Separately identify supply & transportation priorities
Transmission of Radio Frequency Tag Identifier (RFID)
All the above
Question 2: Which is not a basic functionality of the 511R?
Ordering Standard and non-standard materiel
Security Assistance Program materiel ordering (FMS)
Receipt and Acceptance of materiel
Passing and Referral orders
Question 3: If the DoD code (e.g., “AD”) is not the same as an ASC X12 code, where do you find the cross reference conversion tables?
Federally approved implementation convention
DLMSO Web site at DLMS/ANSI conversion guides
Appendix 13 of DLM

52. End of Module 3