Defense Logistics Management System DLMS Introductory Training

1. Defense Logistics Management System (DLMS)Introductory Training This class will provide an introductory level instruction in EDI as applied under the Defense Logistics Management System (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.”This class will provide an introductory level instruction in EDI as applied under the Defense Logistics Management System (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. Course Structure Module 1 - Introduction to the DLMS Module 2 - Electronic Data Interchange (EDI) Basics and ASC X12 EDI Definitions and Concepts Module 3 - DLMS Implementation Strategy Module 4 - DLMS EDI Module 4F - DLMS Financial Module 4M -DLSS/DLMS Mapping Module 5 - IUID & RFID - Emerging Technologies Module 6 - Creating / Changing DOD Logistics Business Processes Module 7 - DODAAD http://www.dla.mil/j-6/dlmso

3. Module Structure Module 3 –DLMS Implementation Strategy

4. Module 3 Objectives Students will gain basic understanding of: Successful strategies to implement the DLMS The DLSS/DLMS critical translation and conversion processes Successful steps to Implementation What corporate services are available to support implementation

5. DLMS Implementation Strategy

6. DLMS is Largely About – “Cutting the Elephant Into Manageable Pieces”

7. DLSS/DLMS Transition Concept To avoid the trauma and expense of "turn-key" implementations, an incremental migration to DLMS is in progress DoD will operate in a mixed DLSS / DLMS environment for an undetermined period During the transition period, logistics systems will undergo modernization and process reengineering changes DoD will operate in a mixed DLSS and DLMS environment for an undetermined period The DAAS and DEBX play a critical role in sustaining this mixed environment A significant level of conversion, between legacy DLSS 80-position formats and ASC X12 DLMS formats, will be required Logistics systems will undergo process reengineering changes From a business process perspective, the underlying functionality of DoD logistics data exchange will remain the same DLMS will support these critical logistics functions: requisitioning inventory management billing transportation contract administration discrepancy reporting DoD will operate in a mixed DLSS and DLMS environment for an undetermined period The DAAS and DEBX play a critical role in sustaining this mixed environment A significant level of conversion, between legacy DLSS 80-position formats and ASC X12 DLMS formats, will be required Logistics systems will undergo process reengineering changes From a business process perspective, the underlying functionality of DoD logistics data exchange will remain the same DLMS will support these critical logistics functions: requisitioning inventory management billing transportation contract administration discrepancy reporting

9. Transition to DLMS DLSS/DLMS conversion tables have been developed that allow conversion of data from DLSS to DLMS (ASC X12/XML) and vice-versa These conversion tables enable logistics business to be conducted in both environments DAAS will also translate between DLMS and: Multiple versions of ASC X12 standards Other emerging standards when adopted as DoD standards Component User Defined File (UDF) formats (by exception) conversion can be considered a subset or a specific type of translation.conversion can be considered a subset or a specific type of translation.

10. Conversion Policy DoD Supply Chain Material Management Regulation (DoD 4140.1-R) states DAAS will be used for conversion services (see guidance beginning on page 162, Paragraphs C8.6.1.1.7, 8, 9, and 10). The guidance to the Components to use DAAS is in Paragraphs C8.6.1.2.2.1 and C8.6.1.2.2.2. This guidance states all transactions are to be sent through DAAS and use the DAAS DLSS and DLMS standards conversion support capabilities. Customer profile = which version/release etc.Customer profile = which version/release etc.

11. Ten Steps to Success Jump Start Project Management Plan (PMP) (pg5) http://www.dla.mil/j-6/dlmso/Programs/DLMS/jumpstart.asp Assemble Team of functional and technical experts on the system to be migrated Initiate early contact with DAAS/other trading partners (e.g., DFAS, MOCAS, WAWF); DAAS POC is Clarissa Elmore, (937) 656-3770 DSN 986-3770, email Clarissa.Elmore@dla.mil Develop a Performance Based Agreement (PBA) with trading partners and Authority To Operate (ATO) Acquire DAAS DLSS to DLMS X12 data maps for the transactions to be migrated Establish communications mechanisms with DAAS and determine what addressing will be used with DAAS 1. Assemble Team of functional and technical experts on the system to be migrated 2. Initiate early contact with DAASC and other trading partners such as DFAS, MOCAS, WAWF. The DAASC point of contact is Clarissa Elmore, (937) 656-3770 DSN 986-3770, email Clarissa.Elmore@dla.mil. a) Develop a memorandum of agreement (MOA) with DAASC b) Acquire DAASC DLSS to DLMS X12 data maps for the transactions to be migrated c) Establish communications mechanisms with DAASC and determine what addressing will be used with DAAS John - For transportation, DAASC will perform translation for us also. However,you should come to me or Mr. Nappoli for DLSS to EDI maps you need. 1. Assemble Team of functional and technical experts on the system to be migrated 2. Initiate early contact with DAASC and other trading partners such as DFAS, MOCAS, WAWF. The DAASC point of contact is Clarissa Elmore, (937) 656-3770 DSN 986-3770, email Clarissa.Elmore@dla.mil. a) Develop a memorandum of agreement (MOA) with DAASC b) Acquire DAASC DLSS to DLMS X12 data maps for the transactions to be migrated c) Establish communications mechanisms with DAASC and determine what addressing will be used with DAAS John - For transportation, DAASC will perform translation for us also. However,you should come to me or Mr. Nappoli for DLSS to EDI maps you need.

12. Ten Steps to Success (con’t) Schedule training with DLMS office and acquire training Training courses can be requested by contacting DLMS office Heidi Daverede 703-767-5111, DSN 427-5111, Heidi.Daverede@dla.mil Select, acquire or develop an EDI or XML translator/parser Develop phased migration plan/schedule Pick a simple transaction first and do one at a time, reusing as much as possible for the next transaction Use EDI or XML translation software and DAAS logical data maps to map/parse data for incoming/outgoing DLMS transactions to or from legacy database or flat files 3. Training courses can be requested by contacting DLMSO, Ellen Hilert, 703-767-0676, DSN 427-0676, Ellen.Hilert@dla.mil . a) This software decodes the syntax associated with the inbound transactions, enabling the parsing of the individual data fields in the transaction and provides for the appropriate assemblage of data fields with correct syntax formatting for outbound transactions. b) Lots of COTS products available to support this process- Mercator; Sterling; SeeBeyond c) The DSS development team that successfully migrated DSS from the DLSS to the DLMS determined that the appropriate course of action for them was to develop their own decoding/parsing and formatting code and integrate it with the DSS application itself. John’s comments on parsers if any Phase I: Establish DLMS X12 EDI or XML baseline, determining the DLSS transactions that enter and exit the system (implement the data content of the DLSS using DLMS X12 EDI or XML) Phase II: Identify initial DLMS X12 EDI or XML enhanced data functionality to be implemented (minimum under “Jump Start” is RFID and IUID data content) Phase III: Determine, plan and schedule DLMS X12 EDI or XML enhanced data content for incorporation into system processing FOR Supply: Note the DLSS are composed of families of transactions, such as the DD_ series of DLSS Document Identifier Code transactions that migrate to a DLMS DS 527D. Once having developed the computer code to migrate a DLSS DDM to a DS 527, much of the code will be reusable for the other DLSS documents in the DD_ series. FOR TRANS Unfortunately all of the transportation transactions we have to imp are very complex, but we have succeeded before and are here to help 7. Self explanatory – 3. Training courses can be requested by contacting DLMSO, Ellen Hilert, 703-767-0676, DSN 427-0676, Ellen.Hilert@dla.mil . a) This software decodes the syntax associated with the inbound transactions, enabling the parsing of the individual data fields in the transaction and provides for the appropriate assemblage of data fields with correct syntax formatting for outbound transactions. b) Lots of COTS products available to support this process- Mercator; Sterling; SeeBeyond c) The DSS development team that successfully migrated DSS from the DLSS to the DLMS determined that the appropriate course of action for them was to develop their own decoding/parsing and formatting code and integrate it with the DSS application itself. John’s comments on parsers if any Phase I: Establish DLMS X12 EDI or XML baseline, determining the DLSS transactions that enter and exit the system (implement the data content of the DLSS using DLMS X12 EDI or XML) Phase II: Identify initial DLMS X12 EDI or XML enhanced data functionality to be implemented (minimum under “Jump Start” is RFID and IUID data content) Phase III: Determine, plan and schedule DLMS X12 EDI or XML enhanced data content for incorporation into system processing FOR Supply: Note the DLSS are composed of families of transactions, such as the DD_ series of DLSS Document Identifier Code transactions that migrate to a DLMS DS 527D. Once having developed the computer code to migrate a DLSS DDM to a DS 527, much of the code will be reusable for the other DLSS documents in the DD_ series. FOR TRANS Unfortunately all of the transportation transactions we have to imp are very complex, but we have succeeded before and are here to help 7. Self explanatory –

13. Ten Steps to Success (con’t) Establish table driven DLSS or DLMS on/off switching mechanism to establish positive control, allow for phasing and fail safe fall back Test, Test, Test Establish loop back testing arrangement with DAAS. System sends DLMS to DAAS & DAAS returns same document in DLSS format and/or vice versa for validation/verification. Conduct unit code testing on each transaction (test all conditions) Schedule and conduct integration testing with DAAS & Trading Partners as feasible Schedule live cut over in increments, implementing few transactions at a time coordinating closely with DAAS 8 .Establish table driven DLSS or DLMS on/off switching mechanism to establish control, allow for phasing and fail safe fall back For transportation, since translating from EDI back to DLSS will be very difficult if not impossible, you should plan on transmitting both EDI and DLSS until your trading partners have been converted. 9. Test, Test, Test Establish “loopback” testing arrangement with DAASC, where legacy system sends DLMS X12 to DAASC and DAASC returns equivalent DLSS and visa versa for validation/verification of correctness. Conduct unit code testing on each transaction (test all conditions) Conduct system testing Schedule and conduct integration testing with DAASC 10. Schedule live cut over in increments, implementing few transactions at a time coordinating closely with DAASC 8 .Establish table driven DLSS or DLMS on/off switching mechanism to establish control, allow for phasing and fail safe fall back For transportation, since translating from EDI back to DLSS will be very difficult if not impossible, you should plan on transmitting both EDI and DLSS until your trading partners have been converted. 9. Test, Test, Test Establish “loopback” testing arrangement with DAASC, where legacy system sends DLMS X12 to DAASC and DAASC returns equivalent DLSS and visa versa for validation/verification of correctness. Conduct unit code testing on each transaction (test all conditions) Conduct system testing Schedule and conduct integration testing with DAASC 10. Schedule live cut over in increments, implementing few transactions at a time coordinating closely with DAASC

14. DoD Corporate Services

15. DLMS office Support to Implementers Functional and technical consultation Providing X12 implementation conventions and XML schemas Arranging trading partner meetings/teleconferences Testing assistance as required Facilitate coordination with DAAS & trading partners Modification & configuration management of DLMS Business Rules Transaction formats Metadata DLMS office Web site support Providing DLMS Training materials and classes Much of the DLMS training is generic enough that transportation program managers should consider sending appropriate folks to the appropriate DLMS courses.Much of the DLMS training is generic enough that transportation program managers should consider sending appropriate folks to the appropriate DLMS courses.

19. Module 3 Quiz

20. End of Module 3