1Defense Logistics Management Standards (DLMS) Introductory Training Introduction to the DLMSThis 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.”
2DLMS Training Catalog Module 1 - Introduction to the DLMS Module 2 - Electronic Data Interchange (EDI) Basics and ASC X12 EDI Definitions and ConceptsModule 3 - DLMS Functionality & Transaction Life-CycleModule 4 - DLMS Implementation Convention ContentModule 4F - DLMS Functional Financial Transaction Life-CycleModule 5 - IUID & RFID - Emerging TechnologiesModule 6 - Creating/Reengineering DOD Logistics Business ProcessesModule 6A - DLMS Configuration Management (stand alone Module)Module Enterprise Interoperability ToolsModule DoD Activity Address Directory (DoDAAD)Module 9 - Supply Discrepancy Reporting (SDR)
3Course Objectives Students will gain basic understanding of the: DLMS purpose, definition, concepts, infrastructure, and policiesBackground and basics of electronic data interchange (EDI)The strategy and roadmap to implement the DLMSAccredited Standards Committee (ASC) X12 EDI definitions and basic structureASC X12 applied in DOD: the Federal implementation conventions (ICs) & DLMS Implementation ConventionsDLMS XML and emerging technologies/initiativesHow to prepare and submit proposed DLMS changes
4Module Structure Module 1 – Introduction to the DLMS Background Corporate InfrastructureEnterprise Support ServicesWhere to Get HelpPolicy and GuidanceTen Steps to Successful Implementation
5Module 1 Objectives Students will gain basic understanding of: What are the DLMSWhy they are importantHow they are developed and maintainedHow EDI fits into the DLMSWhat enterprise services support the DLMSDLMS concepts & implementation strategyThe policies governing the DLMSTen Steps to a successful DLMS implementation
7DLMS Mission & Purpose SUPPLY CHAIN INTEROPERABILITY FIAR BRAC NWRM Strategic Network OptimizationProcess ReengineeringService Oriented ArchitectureBusiness Enterprise ArchitectureNet-Centric OperationsStandard Financial Information StructureSUPPLY CHAIN INTEROPERABILITYAs 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.FIARBest Business PracticesBRACPerformance Based LogisticsNWRMRFIDInformation SuperiorityIUID
8Interoperability of What? Enterprise ServicesProvidersLife CycleSupply ChainsCommoditiesDLMS delivers the business rules, transactions & data standardsDLA-DLIS delivers master data reference repository servicesDAAS delivers the routing, translation, archivingFinance DFASWeapon SystemsAcquisitionInternational Logistics DSCATransport USTRANSCOMDisposal DLA - DRMSDistribution DLA -DDCOthersSlide secondsThis 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 servicesDLIS who provide access to master data reference repositoriesCollectively, 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.DCMA24 x 7Challenge: To Connect Life Cycle Supply Chains & Enterprise Services Providers DoD-wide
9Interoperability Framework Business Policy: A required outcome – Property stewardshipBusiness Process: An assemblage of business rules that collectively form a process. -- Physical Inventory ManagementBusiness 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.DLMSBusiness Metadata: Characteristics of a data element. Inventory Balance Date = 8 numeric characters (yyyymmdd)
10The DLMS Enable Achievement of DoD Goals and Acquisition and Logistics Functional Business Strategy ComponentOrganizational Execution PlansGoal #3: Prepare to defeat adversaries and succeed in a wide range of contingenciesGoal #5: Reform the business and support functions of the Defense enterpriseBusiness Goal #2: Strengthen DoD financial management to respond to warfighter needs and sustain public confidence through auditable financial statementsBusiness 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 resourcesBusiness Goal #6: Re-engineer business processes to reduce transaction times, drive down costs, and improve serviceBusiness Goal #7: Create agile business operations that plan for and sustain contingency missionsDrive Acquisition and Logistics Business StrategyExecute Acquisition and Logistics Business Strategy & SystemsLogistics Strategic PlanDefense Business Council (DBC)/ Investment Review Board (IRB)Architecture Compliance and Requirements Traceability (ACART) toolComponent certifies Business Enterprise Architecture ComplianceComponent Receives DBC/IRB Business System Funding ApprovalFull DLMSImplementation 2019
11Period 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 effortsDOD is modernizing business systems which includes replacing the DLSS (aka MILS) with the DLMSApproximately 3 billion DLSS transactions are exchanged annuallyCY ,102,700,337CY ,885,101,63739 years old - enabled 35,000 paper transactions per day to be expanded to 5.5 million electronic transactions per dayrequisition, inventory transportation, billing and other data among ADP systems of military services and defense agenciesMILSTRIP defined procedures and transactions formats for inter-agency/service related transactions that were previously accomplished by MOUsImmensely successful and expand over the next 16 years
12What 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 AgenciesAccommodates 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.
13More about the DLMS:Includes procedures, data standards, code lists, metrics, policies, and transaction formatsCurrently 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 formatsDLMS XML Schemas – one for each EDI ICMaintains 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.
14Types of DLMS Support Supports transitioning from the DLSS to the DLMS Replaces all of the DLSS transaction formats/associated proceduresExamples: MILSTRIP, MILSTRAP, MILSBILLS, MILSCAPSupports new processes/capabilities not previously associated with a DLSS transactionPublishes the transaction format, adds data elements to DLMS Dictionary, and prescribes the business rules/proceduresExamples: Warehouse Service Advice/Response, Passive RFID Visibility, Catalog Data Exchange, IUIDProvides transaction formats for logistics processes that are not administered by the DLMSOPublishes the transaction format/adds data elements to DLMS DictionaryProvides 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
15Enterprise Service Enablers Goal: Interoperable infrastructure processes and applicationsFocus: Common support services – translation, business rules, standards, reference repositories, testing, etc.DoD focal point to accelerate the integration of EB/EC techniques into DoD operationsProvide a seamless eBusiness environment for DoD and its partnersInteroperability of business operations is as critical to the revolution in business affairs as interoperability on the battlefield is to the revolution in military affairsFocused Logistics is dependent on this interoperabilityEnterprise enabling services and infrastructureavailable to all, providing maximumimplementation flexibility
16Defense Logistics Management Standards Office DoD’s Executive Agent for Logistics Data InterchangePrimary proponent of the DLMSEstablished:1962 as the DoD Military Standards OfficeGeneral Guidance:DLA eBusiness, Information Operations (J6)Deputy Under Secretary of Defense, Logistics (DUSD(L))Taskings:Assistant Deputy Under Secretary of Defense, Supply Chain IntegrationDirector, Logistics Systems Modernization
17DLMSO Purpose/Mission Business Process Transformation & InteroperabilityFacilitate enterprise integration and continuous process improvements to logistics management and operations while maintaining interoperability by:Developing business rules that implement DoD policyDeveloping and managing the DoD logistics information exchange infrastructurePublishing detailed procedures that identify whodoes what, when, and how along the DoDlogistics chainBusinessProcessData StandardsTransaction FormatsBusiness Rules
18DoD Consensus Builder The DLMSO administers DoD-wide: Defense Logistics Management Standards (DLMS)DoD Physical Inventory Control ProgramDLMS Data Management PlanDefense Logistics Standard Systems (DLSS)The DLMSO chairs:DLMS Process Review Committees (PRCs)Pipeline Measurement Process Review Committee (PM PRC)DoD Supply Discrepancy Reporting Sub-CommitteeJoint Physical Inventory Working GroupJoint Small Arms/Light Weapons Coordinating GroupDoDAAD / MAPAD CommitteesComposed of representatives from:Military ServicesDefense AgenciesCoast GuardParticipating Federal Agencies (e.g., GSA, FAA)
19DLMS Process Review Committees (PRC) The DLMSO chairs the following:Supply PRCFinance PRCPipeline Measurement PRCDoDAAD, MAPAD, SDR, JPIWG & othersComposed of representatives from the DoD Components, the U.S. Coast Guard, and participating Federal AgenciesResponsibilities include:Develop and recommend revised policy, procedures, or process improvementsDevelop, evaluate, and coordinate proposed DLMS changesHelp resolve problems, violations, and deviations that arise during system operationsMembership: 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)
21DLMS Process Review Committees MANAGEDTRANSFORMATIONPROCESSStructuredCollaborationModelINPUTSOUTPUTSOSD Policy GuidanceTrading Partner Requirements & SMEsDLMSO SMEs & Technical ExpertiseDLA Transaction Services Technical ExpertiseBusiness RulesBusiness ObjectsMeta DataFunctional RequirementsComponents ImplementArtfulNegotiation& ConsensusBuildingProposed DLMSChanges (PDCs)Slide SecondsShown 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 DLMSChanges (ADCs)
22DLMSO Implementers Support Functional and technical consultationProviding X12 implementation conventions and XML schemasArranging trading partner meetings/teleconferencesTesting assistance as requiredFacilitate coordination with DAAS & trading partnersModification & configuration management of DLMSBusiness RulesTransaction formatsMetadataDLMSO Web site supportProviding DLMS Training materials and classesMuch of the DLMS training is generic enough that transportation program managers should consider sending appropriate folks to the appropriate DLMS courses.
23DLMSO Support to Implementers DirectorD.C. Pipp(703)Functional PRCsSupplyMILSTRIPEllen Hilert(703)MILSTRIP (Alternate)/TransportationHeidi Daverede(703)MILSTRAPMary Jane Johnson(703)SDRFinanceMILSBILLSBob Hammond(703)DODM CharteredWorking GroupsJSA/LWCGLou Madrigal(703)JPIWGLogistics InteroperabilitySupport ServicesDoDAADTad Delaney(703)MAPADSamantha Khuon(703)Pipeline MeasurementKen Deans(703)Technical Transaction SupportANSI ASC X12Frank Napoli(703)ImplementationDale Yeakel(703)Implementation (Alternate)Larry Tanner(614)WebmasterDominic Thomas(703)Technical MetaData SupportData DictionaryPaul Macias(703)DLMS TrainingDeputy DirectorLt Col Richard Fillman(703)NOTE: DSN is 427-XXXXXXXX = last four of commercial phone number
24Defense Transportation Electronic Business (DTEB) Committee
25Defense Transportation Electronic Business (DTEB) Committee Established under authority of DUSD (L&MR)Focal point for DOD transportation e-business standards and requirementsCommunity of interest:DODFederal GovernmentCommercial industryChair: USTRANSCOM J-6CDOMembers: Military Services, Defense Logistics Agency, USTRANSCOM Components, DLMSO, GSA, DFAS, AAFES, NEXCOM, Defense Commissary Agency and Marine Corps Exchange
26Defense 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)SYSTEMSLOGISTICSTELECOMM(formerly Defense Automatic Addressing System Center (DAASC))
28DAAS 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 destinationin the proper format the first time and every time.Providing global network interoperability.Providing value-added services anda central logistics data repository.Being proactive in supporting DoDmodernization 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.
29DAAS infrastructure production and test environment daily functions: Transaction receipt, edit, translation, archiving, and routingMaintenance of logistics information databasesRecurring and special reports and data queriesDAAS technical consultation and support for:Set-up of new accounts, telecom protocols, and data protection schemesLogical data mappings between DLSS, DLMS EDI, and DLMS XMLCoordination of integration testing with System PMO and trading partnersEvaluation of test results and assistance with problem resolutionTransaction tracking, archiving, file recovery/resubmission.Help desk 365/24/7Authoritative Source of customer related reference databases:Customer profiles & routing rulesDoDAAD, MAPAD, Fund Code, Project Code, RICs, LMARS, etc.
30Receive, 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:ArmyNavyAir ForceMarine CorpsUSTRANSCOMDefense AgenciesIntelligenceDoD Education ActivityNATOFMS Countries221,574 ActivitiesWorldwideExchanging Billions of Transactions98% of workloadSuppliersDefense LogisticsAgencyMilitary ServicesGeneral ServicesAdmin.CommercialDAASMapping & Translation ServicesRouting and Transmission ServicesCivilianDepartments of:CommerceStateJusticeTransportationThe 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 dataCommunication (network and data) interoperabilityLogistics information databases and archivingLogistic information reporting and distributionFunctional logistic support and assistanceRoute data by X12 envelope, transaction, van, TP, Prime vendor, and Activity,Multiple Communications FTP/SMTP, MQ-Series, HTTPS, , and Dial-upAuditing and archiving with 30 day on line access and 2 year retentionMapping, translation, and consulting services for X12, UDF, MILS, IDOC, and XMLData recovery and retransmissionEstablishment of new TP agreements and interconnects with VANsStandard and Custom logistic, supply, and transportation reportsLogistic response and customer wait time reportingForeign military addresses, sales, assistance and aid24x7 Support from two operating locationsOfficial repository and distribution point for DoD directoriesDoD Transaction processing utilityWEB enabled systems and productsDesign, develop and manage DAASC systemsDAAS Transactions:DLSS (MILS)DLMS (X12)DLMS (XML)UDF2% of workloadNASAGSAFAAVAFEMAUSPSGAOUSCG
31DLA Transaction Services Support DLMS eBusiness Program Management POCs:Gary Wooddell (937) /DSNClarissa Elmore (937) /DSNPerformance Based Agreement/Memorandum of Agreement:Audrey Lavoie, (937)Logistics Functional Support POCs:Army/GSAAllen Coleman (937) /DSNAir ForceBernace Collier (937) /DSNNavy/Marines/Coast GuardEdward “Nolan” Davis (937) /DSNDLAGeorge "Scott" Amburgey (937) /DSNTesting Support
32DLA Transaction Services Support (cont.) Mapping Support POCs:Doug Mummert (937)Bill Strickler (937)Testing POC:Julie Kampman (937) /DSNeBusiness Group (account set-up):Jennifer Taulbee (937) /DSNJordan Henderson (937) /DSNAndy Rohrer (937) /DSN
33DLA Logistics Information Service (Formerly DLIS)
34DLA 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 logisticiansProvide cataloging services for 7.5 million active national stock numbered items.Implement cataloging policies, procedures and metrics to monitor performanceDeliver State-of-the-art logistics support
35DLA Logistics Information Service Enterprise Reference RepositoriesFederal 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
37DoD Policy and Guidance DoD DirectiveDoD InstructionDoD ManualDLM series of manualsBusiness Enterprise Architecture (BEA)These are some of the key policy documents applicable to implementation of commercial standards and the DLMS
38DoD Policy and Guidance DoD Directive ,DoD Logistics Use of Electronic Data Interchange (EDI) StandardsMay 5, 2000
39DoD 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 interoperabilityUse DLMS as process improvement enablerThe DOD Components shall use the DLMS in new, replacement and major modifications of logistics business systemsUse as part of ongoing and planned modernization programsSupercedes and cancels:DRID #48 Signed by Dr. John Hamre, December 9, 1998USD(AT&L) Memo Policy & Guidance (signed by Dr. Gansler, September 14, 1999)Use only FIPS PUB standards in new or planned processes
40DoD Policy and Guidance DoD InstructionDoD Supply Chain Materiel Management Policy (December 14, 2011)Materiel management functions shall be implemented with DoD standard systemsAuthorizes publication of:DoDM , “DoD Supply Chain Material Management Procedures”DLM series of manuals:DLM (Defense Logistics Management System)DLM (MILSTRIP)DLM (MILSTRAP)DLM (DAAS)
41DoD Policy and Guidance DoDMDoD Supply Chain Material Management Procedures(February 10, 2014)Policy on DLMS Remains UnchangedDoDM , 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.
42DoDM … continuedDoD Components shall support and maintain DLMS for all covered functionsDLMS shall be the primary system governing logistics functional business management standards and practicesDLMS shall use ASC X12 EDI transactional interfacesDLMSO shall provide configuration management for DLMSDLSS shall be deactivated upon DoD-wide implementation of DLMSDLMS shall be the basis for new, replacement and major modifications to logistics business processes/systemsDLMS 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.
43DoDM 4140.01 … continued DAAS shall be: DoD Components shall: Designated as the corporate community service provider for DLMSThe logistics community’s authoritative repository for end-to-end performance metricsDesignated as the source for conversion services (DLSS-DLMS)DoD Components shall:Route all DLSS/DLMS transactions to DAASUse DAAS DLSS/DLMS conversion servicesUniformly implement DLMSDAASC 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.
44DoD Policy and Guidance DLMDEFENSE 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 codesDeveloped using the DLMS Process Review Committee (PRC) collaborative modelDoDM , 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.
45DLMS is a Business Transformation Initiative DLMS are mandated in the Business Enterprise Architecture (BEA)
46DLMS Migration Metric Projection Metric measuring progress is the Percentage of DLMS Transactions versus DLSS TransactionsPercentages for 2015 through 2019 are estimates based on system implementation dates.
47DLMS Implementation Strategy Guide (Appendix 3) Ten Steps to SuccessDLMS Implementation Strategy Guide (Appendix 3)Assemble Team of functional and technical experts on the systemInitiate 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 migratedEstablish communications mechanisms with DLA Transaction Services and determine what transfer protocol will be used with DAASSchedule DLMS trainingTraining courses can be requested by contacting DLMSOPOC: Heidi Daverede , DSN ,1. Assemble Team of functional and technical experts on the system to be migrated2. 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 DAASCb) Acquire DAASC DLSS to DLMS X12 data maps for the transactions to be migratedc) Establish communications mechanisms with DAASC and determine what addressing will be used with DAASJohn -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.
48Ten Steps to Success (con’t) Select, acquire or develop an EDI or XML translator/parserDevelop phased migration plan/schedulePick a simple transaction to work first and do one at a time, reusing as much as possible for the next transactionUse EDI or XML translation software and DLA Transaction Services logical data maps to map/parse data for incoming/outgoing DLMS transactionsEstablish table driven DLSS or DLMS on/off switching mechanism to establish control, allow for phasing and fail safe fall backTest, Test, TestEstablish “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 PartnersSchedule live cut over in increments, implementing few transactions at a time coordinating closely with DLA Transaction Services3. 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; SeeBeyondc) 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 anyPhase 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 processingFOR 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 help7. Self explanatory –
49SummaryDoD Directives mandate moving from DoD-unique logistics data exchange standards to the DLMSThe Defense Logistics Management Standards are a broad base of DoD-approved business rules, standards, objects and processes designed to ensure interoperabilityThe strategy to implement DLMS makes use of a managed, phased transformation process with a structured collaboration modelDAAS ensures global network interoperability during the transition from the DLSS to the DLMSThe DLMS are the new standard for all new or replacement logistics systems, or in major modifications made to existing systems
50Module 1 QuizQuestion 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 & bQuestion 2: Two part question: 1) Office responsible for standard business process and transactions standards supporting Supply? 2) Transportation?a) DLMSO c) OSDb) DTEB d) Secret ServiceQuestion 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 partnerb) Ensure Interoperability e) All of the abovec) Provide Pipeline metrics f) None of the aboveQuestion 4: Which of the following is also called the “DLMS Manual”?a) DOD Directive c) DLMb) DODM d) Declaration of Independence