Presentation is loading. Please wait.

Presentation is loading. Please wait.

Defense Logistics Management Standards (DLMS) Introductory Training

Similar presentations

Presentation on theme: "Defense Logistics Management Standards (DLMS) Introductory Training"— Presentation transcript:

1 Defense Logistics Management Standards (DLMS) Introductory Training
Introduction to the DLMS This class will provide an introductory level instruction in EDI as applied under the Defense Logistics tManagement 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 Course Objectives Students will gain basic understanding of the:
DLMS purpose, definition, concepts, infrastructure, and policies Background and basics of electronic data interchange (EDI) The strategy and roadmap to implement the DLMS Accredited Standards Committee (ASC) X12 EDI definitions and basic structure ASC X12 applied in DOD: the Federal implementation conventions (ICs) & DLMS Implementation Conventions DLMS XML and emerging technologies/initiatives How to prepare and submit proposed DLMS changes

4 Module Structure Module 1 – Introduction to the DLMS Background
Corporate Infrastructure Enterprise Support Services Where to Get Help Policy and Guidance Ten Steps to Successful Implementation

5 Module 1 Objectives Students will gain basic understanding of:
What are the DLMS Why they are important How they are developed and maintained How EDI fits into the DLMS What enterprise services support the DLMS DLMS concepts & implementation strategy The policies governing the DLMS Ten Steps to a successful DLMS implementation

6 Defense Logistics Management Standards (DLMS)

Strategic Network Optimization Process Reengineering Service Oriented Architecture Business Enterprise Architecture Net-Centric Operations Standard Financial Information Structure SUPPLY CHAIN INTEROPERABILITY As you can see from the red program bumper stickers the logistics community is constantly striving to improve business processes to deliver the best possible service and value to the warfighter. Very simply the DLMSO mission is to facilitate the implementation of logistics business process improvements while maintaining interoperability among the systems in the logistics chain. FIAR Best Business Practices BRAC Performance Based Logistics NWRM RFID Information Superiority IUID

8 Interoperability of What?
Enterprise Services Providers Life Cycle Supply Chains Commodities DLMS delivers the business rules, transactions & data standards DLA-DLIS delivers master data reference repository services DAAS delivers the routing, translation, archiving Finance DFAS Weapon Systems Acquisition International Logistics DSCA Transport USTRANSCOM Disposal DLA - DRMS Distribution DLA -DDC Others Slide seconds This chart graphically depicts our supply chain support systems by the horizontal bars. A given horizon bar has many systems supporting that supply chain; among them are acquisition; retail, intermediate, and wholesale material management; maintenance; finance; etc. The vertical bars represent the common enterprise business function providers that DOD has established through the years and the multiple systems each provider uses in the delivery of their services. The connective tissue allowing business to be conducted along and among the supply chains and with common business function support systems is represented by the diagonal yellow semi-transparent line on which you see: DLMSO who provides the common business rules, and information exchange standards (except for Transportation standards established by DTEB). DAASC who provides connectivity and translation services DLIS who provide access to master data reference repositories Collectively, these three organizations perform enterprise services needed by every supply chain and every common business function provider. Without these three organizations the capabilities they deliver would have to be replicated hundreds of times making interoperability far more difficult and costly. DCMA 24 x 7 Challenge: To Connect Life Cycle Supply Chains & Enterprise Services Providers DoD-wide

9 Interoperability Framework
Business Policy: A required outcome – Property stewardship Business Process: An assemblage of business rules that collectively form a process. -- Physical Inventory Management Business Rule: States what must or must not be done. Storage Activities must report the ending on-hand inventory balance to the item owner for all items having any balance effecting business activity that day. Business Object: A collection of data in a specified format that launches a process or reports process results. An order, inventory adjustment, request for payment, etc. DLMS Business Metadata: Characteristics of a data element. Inventory Balance Date = 8 numeric characters (yyyymmdd)

10 The DLMS Enable Achievement of DoD Goals and Acquisition and Logistics Functional Business Strategy
Component Organizational Execution Plans Goal #3: Prepare to defeat adversaries and succeed in a wide range of contingencies Goal #5: Reform the business and support functions of the Defense enterprise Business Goal #2: Strengthen DoD financial management to respond to warfighter needs and sustain public confidence through auditable financial statements Business Goal #4: Increase the buying power of the DoD acquisition system and processes spanning requirements determination, development, procurement, and support to ensure that the force structure is modernized, recapitalized, and sustained within available resources Business Goal #6: Re-engineer business processes to reduce transaction times, drive down costs, and improve service Business Goal #7: Create agile business operations that plan for and sustain contingency missions Drive Acquisition and Logistics Business Strategy Execute Acquisition and Logistics Business Strategy & Systems Logistics Strategic Plan Defense Business Council (DBC)/ Investment Review Board (IRB) Architecture Compliance and Requirements Traceability (ACART) tool Component certifies Business Enterprise Architecture Compliance Component Receives DBC/IRB Business System Funding Approval Full DLMS Implementation 2019

11 Period of Transition & Transformation
In 1962, the DOD established the Military Standard Systems (MILS) to realize the advantages of advancing computer technology and ensure interoperability (The MILS were renamed the Defense Logistics Standard Systems (DLSS)) The DLSS information exchange format is technically obsolete, unique to DOD and inhibits functional process improvements and process reengineering efforts DOD is modernizing business systems which includes replacing the DLSS (aka MILS) with the DLMS Approximately 3 billion DLSS transactions are exchanged annually CY ,102,700,337 CY ,885,101,637 39 years old - enabled 35,000 paper transactions per day to be expanded to 5.5 million electronic transactions per day requisition, inventory transportation, billing and other data among ADP systems of military services and defense agencies MILSTRIP defined procedures and transactions formats for inter-agency/service related transactions that were previously accomplished by MOUs Immensely successful and expand over the next 16 years

12 What are the DLMS? The Defense Logistics Management Standards (DLMS) are a broad base of process rules, data standards and electronic business objects (information exchange forms) designed to meet DoD’s requirements for total logistics support. Developed in collaboration with representatives from the Military Departments, Defense Agencies, and participating Federal Agencies Accommodates the new Enterprise Resource Planning (ERP) system processes and implementation, while supporting legacy system data exchange requirements. DLMS replaces the fixed length DoD proprietary DLSS with the variable length ASC X12 EDI standards within the DoD logistics. DLMSO has completed a great deal of work, transforming the functionality of more than 450 fixed length transaction formats that have been consolidated in 26 ASC X12 transaction sets.

13 More about the DLMS: Includes procedures, data standards, code lists, metrics, policies, and transaction formats Currently consist of two data transmission forms: DLMS EDI Implementation Conventions (IC) that use ASC X12 transaction sets to consolidate the functionality of 500+ DLSS transaction formats DLMS XML Schemas – one for each EDI IC Maintains capability to communicate legacy system information requirements while expanding to support new initiatives such as: Item Unique Identification (IUID) Base Realignment And Closure (BRAC) Passive Radio Frequency Identification (pRFID) Financial Improvement Audit Readiness (FIAR) On bullet #3 point out Directive 4.1, the last 2 sentences.

14 Types of DLMS Support Supports transitioning from the DLSS to the DLMS
Replaces all of the DLSS transaction formats/associated procedures Examples: MILSTRIP, MILSTRAP, MILSBILLS, MILSCAP Supports new processes/capabilities not previously associated with a DLSS transaction Publishes the transaction format, adds data elements to DLMS Dictionary, and prescribes the business rules/procedures Examples: Warehouse Service Advice/Response, Passive RFID Visibility, Catalog Data Exchange, IUID Provides transaction formats for logistics processes that are not administered by the DLMSO Publishes the transaction format/adds data elements to DLMS Dictionary Provides overview of process/references governing policy/process (no procedural detail) Examples: Stock Readiness (Storage Quality Control Report and Stock Screening), Product Quality Deficiency Report, Weapon Systems Data Change

15 Enterprise Service Enablers
Goal: Interoperable infrastructure processes and applications Focus: Common support services – translation, business rules, standards, reference repositories, testing, etc. DoD focal point to accelerate the integration of EB/EC techniques into DoD operations Provide a seamless eBusiness environment for DoD and its partners Interoperability of business operations is as critical to the revolution in business affairs as interoperability on the battlefield is to the revolution in military affairs Focused Logistics is dependent on this interoperability Enterprise enabling services and infrastructure available to all, providing maximum implementation flexibility

16 Defense Logistics Management Standards Office
DoD’s Executive Agent for Logistics Data Interchange Primary proponent of the DLMS Established: 1962 as the DoD Military Standards Office General Guidance: DLA eBusiness, Information Operations (J6) Deputy Under Secretary of Defense, Logistics (DUSD(L)) Taskings: Assistant Deputy Under Secretary of Defense, Supply Chain Integration Director, Logistics Systems Modernization

17 DLMSO Purpose/Mission
Business Process Transformation & Interoperability Facilitate enterprise integration and continuous process improvements to logistics management and operations while maintaining interoperability by: Developing business rules that implement DoD policy Developing and managing the DoD logistics information exchange infrastructure Publishing detailed procedures that identify who does what, when, and how along the DoD logistics chain Business Process Data Standards Transaction Formats Business Rules

18 DoD Consensus Builder The DLMSO administers DoD-wide:
Defense Logistics Management Standards (DLMS) DoD Physical Inventory Control Program DLMS Data Management Plan Defense Logistics Standard Systems (DLSS) The DLMSO chairs: DLMS Process Review Committees (PRCs) Pipeline Measurement Process Review Committee (PM PRC) DoD Supply Discrepancy Reporting Sub-Committee Joint Physical Inventory Working Group Joint Small Arms/Light Weapons Coordinating Group DoDAAD / MAPAD Committees Composed of representatives from: Military Services Defense Agencies Coast Guard Participating Federal Agencies (e.g., GSA, FAA)

19 DLMS Process Review Committees (PRC)
The DLMSO chairs the following: Supply PRC Finance PRC Pipeline Measurement PRC DoDAAD, MAPAD, SDR, JPIWG & others Composed of representatives from the DoD Components, the U.S. Coast Guard, and participating Federal Agencies Responsibilities include: Develop and recommend revised policy, procedures, or process improvements Develop, evaluate, and coordinate proposed DLMS changes Help resolve problems, violations, and deviations that arise during system operations Membership: Military Services; Defense Agencies, e.g. DLA, DFAS, DTRA (Defense Treat Reduction Agency), NSA, DSCA (Defense Security Cooperation Agency); Coast Guard; Federal Agencies (e.g. GSA, FAA) GAO of Logistics Response Time (LRT) / Customer Wait Time (CWT)

20 DLMS Governance Process
DLMS Configuration Management Process, DLM Series of Manuals Systems Development: Business Enterprise Architecture (BEA) Acquisition & Logistics Functional Strategy & Component Organization Execution Plans Systems Execution: DAAS applied syntax & semantic validations Directives Instructions Regulations & Manuals OSD Policy Direction Standards Syndication Compliance Oversight

21 DLMS Process Review Committees
MANAGED TRANSFORMATION PROCESS Structured Collaboration Model INPUTS OUTPUTS OSD Policy Guidance Trading Partner Requirements & SMEs DLMSO SMEs & Technical Expertise DLA Transaction Services Technical Expertise Business Rules Business Objects Meta Data Functional Requirements Components Implement Artful Negotiation & Consensus Building Proposed DLMS Changes (PDCs) Slide Seconds Shown here is how the magic is performed that transforms high level policy outcomes into execution and delivery across the enterprise. The key is the DLMS Process Review Committees depicted in the center are the key. DLMS manages the process but the representative that you send as you subject mater experts are what make the process work. The DLMSO Process Committee Chairs oversee and guide the process, they also bring subject matter and technical expertise; but they don’t vote and they don’t dictate. We in DLMSO don’t own any business process or systems; we simply facilitate and enable business process changes and interoperability among the process and systems owners. You see the inputs on the left of the chart. Sometimes proposed changes are initiated due to new or change OSD policies and initiative like IUID and RFID other time they are initiated by one or more of your representatives. Regardless of how they are initiated they are always fully vetted and staffed. Some never get approved, but most times an acceptable process is agreed upon and is issued as an approved DLMS change that forms a contract among the trading partners on how business will be conducted. The last thought I want to leave with you on this chart is that it is in your individual organizations best interests to send us your best and brightest subject matter experts and make sure your component is consistently always represented on our process review committees. On the next series of charts we’ll take a quick look at a sample of high impact ACD. Approved DLMS Changes (ADCs)

22 DLMSO Implementers Support
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 DLMSO 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.

23 DLMSO Support to Implementers
Director D.C. Pipp (703) Functional PRCs Supply MILSTRIP Ellen Hilert (703) MILSTRIP (Alternate)/Transportation Heidi Daverede (703) MILSTRAP Mary Jane Johnson (703) SDR Finance MILSBILLS Bob Hammond (703) DODM Chartered Working Groups JSA/LWCG Lou Madrigal (703) JPIWG Logistics Interoperability Support Services DoDAAD Tad Delaney (703) MAPAD Samantha Khuon (703) Pipeline Measurement Ken Deans (703) Technical Transaction Support ANSI ASC X12 Frank Napoli (703) Implementation Dale Yeakel (703) Implementation (Alternate) Larry Tanner (614) Webmaster Dominic Thomas (703) Technical MetaData Support Data Dictionary Paul Macias (703) DLMS Training Deputy Director Lt Col Richard Fillman (703) NOTE: DSN is 427-XXXX XXXX = last four of commercial phone number

24 Defense Transportation Electronic Business (DTEB) Committee

25 Defense Transportation Electronic Business (DTEB) Committee
Established under authority of DUSD (L&MR) Focal point for DOD transportation e-business standards and requirements Community of interest: DOD Federal Government Commercial industry Chair: USTRANSCOM J-6CDO Members: Military Services, Defense Logistics Agency, USTRANSCOM Components, DLMSO, GSA, DFAS, AAFES, NEXCOM, Defense Commissary Agency and Marine Corps Exchange

26 Defense Transportation Regulation (DTR 4500.9-R)
“Prescribes policies and procedures…” “Assigns responsibilities for performing traffic management functions…” “Prescribes standard data elements, codes, formats, documents, forms, rules, methods, and procedures … for movement of materiel within the Defense Transportation System (DTS).” Procedures apply to Military Services, DLA, DCMA, Coast Guard, GSA, USTRANSCOM and its Component Commands, and other activities/agencies using the DTS. Seven Parts: Part II - Cargo Movement relevant to Logistics

27 (formerly Defense Automatic Addressing System Center (DAASC))
DLA Transaction Services Administers the Defense Automatic Address System (DAAS) SYSTEMS LOGISTICS TELECOMM (formerly Defense Automatic Addressing System Center (DAASC))

28 DAAS Mission: DAAS Vision:
The Defense Automatic Addressing System (DAAS) mission is to perform as an interoperable gateway for the DoD Components, Government activities, and Foreign Military Sales countries to provide value added services and to deliver logistics data to the appropriate destination, efficiently, expeditiously and accurately. DAAS Vision: Support the DoD warfighter’s mission by: Providing logistics data to the appropriate destination in the proper format the first time and every time. Providing global network interoperability. Providing value-added services and a central logistics data repository. Being proactive in supporting DoD modernization efforts. The DAASC came on line in June The original mission was to edit, validate and route logistics data for the Department of Defense. Through the years our mission has continued to expand to where today we support other government activities, civil agencies and foreign military sales countries. DAASC serves as custodian for several DoD publications and reporting capabilities. As an example, DAASC maintains the Department of Defense Activity Address File. In addition, DAASC supports several DoD level capabilities, such as the Logistics On-line Tracking System, which supports requisition tracking throughout their life cycle and the Logistics Metrics Analysis Reporting System, to report Logistics Response Time and Customer Wait Time. DAASC has also fielded an eBusiness Gateway hub to facilitate government to commercial industry exchange of data. We also provide direct support to DLA, the Army and Navy in their Enterprise Resource Planning (ERP) fielding efforts. So, as we will discuss today, we at DAASC are continuing to reinvent ourselves to stay abreast of the needs of the logistics community.

29 DAAS infrastructure production and test environment daily functions:
Transaction receipt, edit, translation, archiving, and routing Maintenance of logistics information databases Recurring and special reports and data queries DAAS technical consultation and support for: Set-up of new accounts, telecom protocols, and data protection schemes Logical data mappings between DLSS, DLMS EDI, and DLMS XML Coordination of integration testing with System PMO and trading partners Evaluation of test results and assistance with problem resolution Transaction tracking, archiving, file recovery/resubmission. Help desk 365/24/7 Authoritative Source of customer related reference databases: Customer profiles & routing rules DoDAAD, MAPAD, Fund Code, Project Code, RICs, LMARS, etc.

30 Receive, Validate, Edit, Route, & Transmit
DAAS delivers the ability to receive and transmit logistics data across various networks, supporting numerous protocols and formats. This communications interoperability minimizes the number of interfaces that the DoD Components must maintain for the exchange of logistics data. DAAS maintains a history of all transactions processed/routed to support supply chain analysis. Customers DoD: Departments of: Army Navy Air Force Marine Corps USTRANSCOM Defense Agencies Intelligence DoD Education Activity NATO FMS Countries 221,574 Activities Worldwide Exchanging Billions of Transactions 98% of workload Suppliers Defense Logistics Agency Military Services General Services Admin. Commercial DAAS Mapping & Translation Services Routing and Transmission Services Civilian Departments of: Commerce State Justice Transportation The original DAASC mission was developed around the idea of receiving, editing, validating, routing and delivering data to the appropriate destination, and we have been doing that quite well over the past years. In today’s environment Network Interoperability and Data Interoperability is the key to our success. Today a user may submit data via a dedicated or dial-in connection, through the NIPRNET, or Internet and the World Wide Webb using numerous formats and protocols. DAASC supports numerous formats and protocols based upon our customer’s needs. As an example, a transaction may be received via a dedicated connection using ASYNC pushing ASC X12 formatted data and the destination may required the data as DLSS fixed length using JANAP 128 format, or even as an file. Our two operational sites, running in a 24 x 7 environment, with no single point of failure for our mission essential processes, ensures our customers that we will always be there to support the processing of their logistics data. Thus, DAASC, through our varied community services stands ready to serve our customers through many avenues. Receive, edit, validate and route logistic data Communication (network and data) interoperability Logistics information databases and archiving Logistic information reporting and distribution Functional logistic support and assistance Route data by X12 envelope, transaction, van, TP, Prime vendor, and Activity, Multiple Communications FTP/SMTP, MQ-Series, HTTPS, , and Dial-up Auditing and archiving with 30 day on line access and 2 year retention Mapping, translation, and consulting services for X12, UDF, MILS, IDOC, and XML Data recovery and retransmission Establishment of new TP agreements and interconnects with VANs Standard and Custom logistic, supply, and transportation reports Logistic response and customer wait time reporting Foreign military addresses, sales, assistance and aid 24x7 Support from two operating locations Official repository and distribution point for DoD directories DoD Transaction processing utility WEB enabled systems and products Design, develop and manage DAASC systems DAAS Transactions: DLSS (MILS) DLMS (X12) DLMS (XML) UDF 2% of workload NASA GSA FAA VA FEMA USPS GAO USCG

31 DLA Transaction Services Support
DLMS eBusiness Program Management POCs: Gary Wooddell (937) /DSN Clarissa Elmore (937) /DSN Performance Based Agreement/Memorandum of Agreement: Audrey Lavoie, (937) Logistics Functional Support POCs: Army/GSA Allen Coleman (937) /DSN Air Force Bernace Collier (937) /DSN Navy/Marines/Coast Guard Edward “Nolan” Davis (937) /DSN DLA George "Scott" Amburgey (937) /DSN Testing Support

32 DLA Transaction Services Support (cont.)
Mapping Support POCs: Doug Mummert (937) Bill Strickler (937) Testing POC: Julie Kampman (937) /DSN eBusiness Group (account set-up): Jennifer Taulbee (937) /DSN Jordan Henderson (937) /DSN Andy Rohrer (937) /DSN

33 DLA Logistics Information Service (Formerly DLIS)

34 DLA Logistics Information Service
Mission: Create, obtain, manage, and integrate logistics data from a variety of sources for dissemination as user-friendly information to meet or exceed the needs of DOD, Federal and international logisticians Provide cataloging services for 7.5 million active national stock numbered items. Implement cataloging policies, procedures and metrics to monitor performance Deliver State-of-the-art logistics support

35 DLA Logistics Information Service
Enterprise Reference Repositories Federal Logistics Information System (FLIS) IUID Registry (includes GFP Registry) Master Data Capability (FLIS IUID Indicator) Federal Registration Registry (FedReg) Commercial and Government Entity (CAGE) Registry

36 Policy and Guidance

37 DoD Policy and Guidance
DoD Directive DoD Instruction DoD Manual DLM series of manuals Business Enterprise Architecture (BEA) These are some of the key policy documents applicable to implementation of commercial standards and the DLMS

38 DoD Policy and Guidance
DoD Directive , DoD Logistics Use of Electronic Data Interchange (EDI) Standards May 5, 2000

39 DoD Directive 8190.1 … continued
ANSI ASC X12 is the baseline logistics data exchange standard upon which the DLMS shall be based. Develop and apply DoD corporate services and processes to minimize duplication and ensure interoperability Use DLMS as process improvement enabler The DOD Components shall use the DLMS in new, replacement and major modifications of logistics business systems Use as part of ongoing and planned modernization programs Supercedes and cancels: DRID #48 Signed by Dr. John Hamre, December 9, 1998 USD(AT&L) Memo Policy & Guidance (signed by Dr. Gansler, September 14, 1999) Use only FIPS PUB standards in new or planned processes

40 DoD Policy and Guidance
DoD Instruction DoD Supply Chain Materiel Management Policy (December 14, 2011) Materiel management functions shall be implemented with DoD standard systems Authorizes publication of: DoDM , “DoD Supply Chain Material Management Procedures” DLM series of manuals: DLM (Defense Logistics Management System) DLM (MILSTRIP) DLM (MILSTRAP) DLM (DAAS)

41 DoD Policy and Guidance
DoDM DoD Supply Chain Material Management Procedures (February 10, 2014) Policy on DLMS Remains Unchanged DoDM , better known as the “SuperManual,” provides the policies and procedural guidance for the DLSS…and now the DLMS. It is a far reaching publication that covers the requirements and procedures for DoD material managers and others who need to work within or with the DoD Supply system.

42 DoDM … continued DoD Components shall support and maintain DLMS for all covered functions DLMS shall be the primary system governing logistics functional business management standards and practices DLMS shall use ASC X12 EDI transactional interfaces DLMSO shall provide configuration management for DLMS DLSS shall be deactivated upon DoD-wide implementation of DLMS DLMS shall be the basis for new, replacement and major modifications to logistics business processes/systems DLMS covers the functional areas of supply, transportation, acquisition (contract administration), maintenance, and finance. It implements the necessary policies to support the Components incorporation within their respective systems of the procedures and business rules to implement those policies. DLMS provides the required ASC X12 transactions and equivalent XML Schemas to interface with all trading partners. As new technologies are approved and become DoD standards DLMS will incorporate those emerging standards, as required, allowing Component systems to keep pace with the within their logistics business processes/systems. DLMSO will configuration manage all changes to the DLMS no matter what technology methods are employed by the Components. Once all DoD Components have fully implemented DLMS the DLSS will be deactivated.

43 DoDM 4140.01 … continued DAAS shall be: DoD Components shall:
Designated as the corporate community service provider for DLMS The logistics community’s authoritative repository for end-to-end performance metrics Designated as the source for conversion services (DLSS-DLMS) DoD Components shall: Route all DLSS/DLMS transactions to DAAS Use DAAS DLSS/DLMS conversion services Uniformly implement DLMS DAASC has implemented the required maps to provide complete conversion services (DLMS to DLSS and DLSS to DLMS) until all Components have implemented DLMS and conversion services are no longer needed. As the DoD corporate community service provider for DLMS, DAASC is providing telecommunications support, archiving and storage, translation services ASC X12/DLSS conversion and other services to support DoD Component supply chain management Standardsand DLMS implementation. In this capacity DAASC is providing the authoritative repository for DoD end-to-end performance metrics. DoD Components shall take advantage of this community service by routing all DLMS/DLSS transactions to DAAS for edit, validation, and routing to correct recipients and to support Combatant Commands and DoD Component logistics performance metric analysis reporting requirements. By their uniform implementation of the DLMS, the DoD Components will ensure a transition strategy that will support all organization levels in their logistical needs.

44 DoD Policy and Guidance
DLM DEFENSE LOGISTICS MANAGEMENT SYSTEM MANUAL (June 2012) DLM will subsume DLM and (target December 2014) Documents the detailed business processes and rules, information exchange formats, data standards and codes Developed using the DLMS Process Review Committee (PRC) collaborative model DoDM , better known as the “SuperManual,” provides the policies and procedural guidance for the DLSS…and now the DLMS. It is a far reaching publication that covers the requirements and procedures for DoD material managers and others who need to work within or with the DoD Supply system.

45 DLMS is a Business Transformation Initiative
DLMS are mandated in the Business Enterprise Architecture (BEA)

46 DLMS Migration Metric Projection
Metric measuring progress is the Percentage of DLMS Transactions versus DLSS Transactions Percentages for 2015 through 2019 are estimates based on system implementation dates.

47 DLMS Implementation Strategy Guide (Appendix 3)
Ten Steps to Success DLMS Implementation Strategy Guide (Appendix 3) Assemble Team of functional and technical experts on the system Initiate early contact with DLA Transaction Services and other trading partners. POC is Joanne Norman, (937) DSN , Develop an applicable agreement (e.g., Memorandum of Agreement, Performance Based Agreement, Interservice/Interdepartmental/Agency Support Agreement, Interface Requirements Document) and Authority to Operate (ATO) or equivalent (e.g., Interim ATO, System Security Plan, DOD Information Assurance Certification and Accreditation Process). Submit the agreement, ATO, and System Access Request (SAR) to DLA Transaction Services. Acquire DLA Transaction Services MILS to DLMS X12 data maps for the transactions to be migrated Establish communications mechanisms with DLA Transaction Services and determine what transfer protocol will be used with DAAS Schedule DLMS training Training courses can be requested by contacting DLMSO POC: Heidi Daverede , DSN , 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) DSN , 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.

48 Ten Steps to Success (con’t)
Select, acquire or develop an EDI or XML translator/parser Develop phased migration plan/schedule Pick a simple transaction to work first and do one at a time, reusing as much as possible for the next transaction Use EDI or XML translation software and DLA Transaction Services logical data maps to map/parse data for incoming/outgoing DLMS transactions Establish table driven DLSS or DLMS on/off switching mechanism to establish control, allow for phasing and fail safe fall back Test, Test, Test Establish “loop back” testing arrangement with DLA Transaction Services where legacy system sends MILS to DLA Transaction Services and DLA Transaction Services returns equivalent DLMS X12 for validation/verification. Conduct unit code testing on each transaction (test all conditions) Schedule and conduct integration testing with DAAS & Trading Partners Schedule live cut over in increments, implementing few transactions at a time coordinating closely with DLA Transaction Services 3. Training courses can be requested by contacting DLMSO, Ellen Hilert, , DSN , . 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 –

49 Summary DoD Directives mandate moving from DoD-unique logistics data exchange standards to the DLMS The Defense Logistics Management Standards are a broad base of DoD-approved business rules, standards, objects and processes designed to ensure interoperability The strategy to implement DLMS makes use of a managed, phased transformation process with a structured collaboration model DAAS ensures global network interoperability during the transition from the DLSS to the DLMS The DLMS are the new standard for all new or replacement logistics systems, or in major modifications made to existing systems

50 Module 1 Quiz Question 1: Which document requires DOD Components to replace DOD-unique logistics data exchange standards with the DLMS? a) The DOD Directive c) The Constitution b) DODM d) Both a & b Question 2: Two part question: 1) Office responsible for standard business process and transactions standards supporting Supply? 2) Transportation? a) DLMSO c) OSD b) DTEB d) Secret Service Question 3: Why does DOD policy mandate the routing of all logistics transactions through DAAS and the use of DAAS conversion services when translations among message formats are required? a) Save money d) Single trading partner b) Ensure Interoperability e) All of the above c) Provide Pipeline metrics f) None of the above Question 4: Which of the following is also called the “DLMS Manual”? a) DOD Directive c) DLM b) DODM d) Declaration of Independence

51 End of Module 1

Download ppt "Defense Logistics Management Standards (DLMS) Introductory Training"

Similar presentations

Ads by Google