1Defense Logistics Management Standards (DLMS) Introductory Training DLMS Functionality &Transaction Life-CycleThis 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.”
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)
3Module 3 Structure DLMS Functionality & Transaction Life-Cycle Relationship Between the DLMS EDI & DLSSDLMS Functionality by TransactionDLMSO Web Site Navigation
4Module 3 Objectives Students will gain a basic understanding of: Relationship of the DLMS and DLSS data formatsHigh level functionality of the DLMSRelationship among DLMS business transactionsBreadth of functionality covered by the DLMSFunctional and data enhancements afforded by DLMSHow to navigate the DLMSO web site as a DLMS resource
5Data Relationship Between the DLMS EDI and the DLSS 80 Record Position Fixed Length Data Field formatsWhat 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
6EDI Document Structure RPs Field Legend Sample DataDocument Identifier A01Routing Identifier SMS07 Media and Status BStock NumberUnit of Issue EAQuantity 1Document No FBDemand RSupplementary AddressSignal AFund KZDistributionProject 9GFPriorityReqd. Delivery DateAdvice 2ABlank (Date of Rcpt on Referral/Passing Order)Blank (Intra-Service use)The DLSS Fixed Format RequisitionMILS FormatST*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 FormatEDI document structure is an electronic version of a paper documentPaper-based systemBusiness document is created and printed on a standard formHeader area contains information pertaining to the entire documentDetail area contains information pertaining to the document itemsEDI or electronic-based systemAn electronic version is createdInstead of printing on standard form, information is in standard ANSI X12 or EDIFACT formatEDI version is functionally identical to the paper document
7DLMS transaction/DLSS Transaction Relationship DLSS Document Identifier Code (DIC)DLMS 527R – ReceiptD4M/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/DZK1 DLMS Transaction33 DLSS Transactions FamiliesTransactions within a DLSS family:Same first 2 characters of the Document Identifier CodeData content nearly identical -- lots of reusability
8DLMS 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
9DLMS Requisition Cycle Retail BaseDefense Finance and Accounting ServiceDistribution Depotor VendorWe 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/IMMUSTRANSCOM
11DLMS 511R, Requisition Basic Functionality Standard and non-standard materielGovernment-furnished materiel (GFM)Security AssistancePassing ordersReferral ordersThe 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.
12DLMS Enhancements Transaction set preparation date/time Supply condition codeUnit Price/Total Dollar ValueUtilization codeSpecial requirements codeShipment StatusPoints of contactRemarksDetailed line of accounting componentsAssociated special program requirement transaction numberTouched on some of these during earlier discussions
13DLMS Enhancements (con’t) Expanded item identificationWeapon system designator codeQuantity stratified by weapon system and demand codeReason for requisitioning codeParty(ies) to receive status DoDAACMark-for-PartyUnique item identification informationClear text exception ship-to locationUnique 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.
14DLMS Enhancements Applicable to Non-Standard Material Supporting Document No.ColorDrawing Revision No.Catalog NumberSeries IdentifierModel NumberFigure NumberGeneral Specification No.Manufacturer’s NameProcess NumberPublication NumberDimension/MeasurementMaterial DescriptionPotential Source of SupplyEnd Item ManufacturerWe 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.
15DLMS 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.
19TransportationUSTRANSCOM 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
23Physical Inventory Control Program II1. PhysicalInventory RequestDLMS 846P / DIC DJA, DZJSOS4. Location ReconciliationTransaction CountDLMS 846R /DIC DZP4. End of Day (EOD)Transaction CountDLMS 846P / DIC DZM3. Transaction HistoryDLMS 527R, 940R,945A & 947I /DIC DZK3. End of Day ProcessDLMS 846R / DIC DZH2. Location ReconciliationDLMS 846R / DICs DZJ & DZK2. Inventory Gain/Inventory LossDLMS 947I / DIC D8_ & D9_1. Location ReconciliationNotificationDLMS 846R /DIC DZNI = ICP-initiated Physical Inventory RequestII = Location ReconciliationIII = Depot-initiated Physical Inventory RequestIII1. PhysicalInventory RequestSupply DepotDLMS 846P / DIC DJA orInternally System Generated
24Sample of DLMS Enhancements Automation of previously manual processes such as Supply Discrepancy Reporting (SDR) DLMS 842A/RMass transaction modification and cancelation capability– previously addressed by single line item or requested off-lineSeparately identify supply & transportation prioritiesTransmission to recipients of Radio Frequency Tag Identifier (RFID) at multiple tagging indenture levelsTransmission of Unique Item Identifier (UII) of itemsCapability to transmit clear text exception dataCapability to transmit detailed Contract, Storage data, etc.Inclusion of Component unique dataCurrent 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.
25DLMS 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.
26DLMS Functionality MILSBILLS MILSTRAP MILSTRIP Contract Administration 810L, 812L, 812R, FV1 (XML), FV2 (XML)MILSTRAP527D, 527R, 536L, 830R, 830W, 846D, 846F, 846I, 846M, 846P, 846R, 846S, 867D, 867I, 870L, 888I, 947IMILSTRIP180M, 511M, 511R, 517G, 517M, 856N, 856R, 856S, 869A, 869C, 869F, 870M, 870N, 870S, 940R, 945AContract Administration567C, 856, 861Discrepancy/Deficiency Programs842A/R, 842A/W, 842C/I, 842C/R, 842P, 842S/Q, 842S/RDisposition Services832N, 846C, 996H, standard MILSTRIP, MILSTRAP, MILSBILLSBRAC IMSP832N, 940S, 943A, standard MILSTRIP, MILSTRAP, MILSBILLSMedicalUnit Assembly Program650A, 650CSmall Arms/Light Weapons140A, 888AMaterial Returns Program180M, Material Returns Reporting870M, Material Returns Supply Status856R, Shipment Status Material ReturnsMaterial Obligation Validation Program517M, MOV517G, Government Furnished Material MOVForeign Military Sales Notice of Availability856N, NOA870N, NOA ReplyLogistics Reassignment536L, LR Management Data846D, LR Transfer/Decapitalization846S, LR Storage Transfer/Order/ReplyWar Material Requirements - 830W, WMRSpecial Program Requirements - 830R, SPRDemand 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 Reclassification846ADemandData Exchange830DWeapon System888WDemand - 867D, DemandInventory Related Transactions846P, Physical Inventory/Transaction History888I, Storage Item Correction947I, Inventory AdjustmentSmall Arms/Ammunition846F Ammunition Freeze/Unfreeze140A, Small Arms Reporting888A, Small Arms Data ChangeIssue - 867I, IssueLogistics Asset Support - 846L, Logistics Asset Support EstimateAsset Status Reporting - 846I, Asset Status Inquiry/ReportGeneral824R, 997Transportation/pRFIDVisibility (XML), Visibility Response (XML), Reader Registration (XML)*Reference Tab N for details
27The DLMSO Web Site A Valuable Resource Navigation of the DLMSO web site
28Easy Access To: Latest published DLSS & DLMS manuals DLMS Implementation ConventionsDLMS XML SchemasProcess change documentationCommittee informationDLMS DictionaryLink to Logistics Data Resources Management System (LOGDRMS) website:Link to DLMS trainingAnd more – worth exploring!!!Mention .gov/.mil change
29Quick link to the DLMS Implementation Conventions
40Essential ANSI ASC X12 Code/DoD Code Conversions ANSI ASC X12 mandates use of ANSI code list values in X12 transaction transmissions where they existThere are three ANSI Code lists that must be used in DLMS transactionsMode of ShipmentType of PackUnit of measureDLMS Conversion guides map DoD definitions to desired X12 definitionsDoD applications must convert outbound transactions from DoD code values to ANSI code values based on DLMS Conversion Guide definitionsDoD applications must convert inbound transactions from ANSI code values to DoD code values based on DLMS Conversion Guide definitionsOnce the requisition itself has processed, there are several related transactions which may be needed to modify, cancel, or follow-up.
50Summary DLMS provides a new logistics data exchange format Commercial vs. DoD proprietary standardVariable length vs. 80-record position records with fixed data lengthsW3C compliant XML schema formatsSupports new data content to meet DoD needsProvides opportunity to reengineer logistics business processesSupports all current and future business/electronic commerce data transmission requirements
51Module 3 QuizQuestion 1: Which of the following are DLMS enhanced capabilities?Automation of previously manual processes e.g. Supply Discrepancy ReportingMass transaction modification and cancelation capabilitySeparately identify supply & transportation prioritiesTransmission of Radio Frequency Tag Identifier (RFID)All the aboveQuestion 2: Which is not a basic functionality of the 511R?Ordering Standard and non-standard materielSecurity Assistance Program materiel ordering (FMS)Receipt and Acceptance of materielPassing and Referral ordersQuestion 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 conventionDLMSO Web site at DLMS/ANSI conversion guidesAppendix 13 of DLM