*DLM 4000.25, Volume 6, December 27, 2022*

*Change 15*

**C4. CHAPTER 4**

**PIPELINE MEASUREMENT**

## C4.1.  GENERAL

	C4.1.1.  Purpose of Chapter.  This chapter identifies the roles, authorities, business rules, governance and configuration management process that comprise the Logistics Metrics Analysis Reporting System (LMARS), located at Defense Automatic Addressing System (DAAS).  It establishes the information requirements for LMARS which tracks materiel as it moves through the logistics pipeline and reports the associated response times.  Within the authority granted it in paragraph C4.3.1. the Pipeline Measurement  Process Review Committee (PM PRC) is responsible for developing and maintaining LMARS to include the maintenance of this chapter.

	C4.1.2.  Purpose of LMARS.  LMARS is a reporting tool for the collection of logistics business events to allow measurement of actual logistics pipeline performance.  The information enables users and management to track trends, identify areas requiring improvement, and compare actual performance against pre-established goals.  LMARS consists of:

		C4.1.2.1.  Set of definitions identifying the beginning and ending of each of the twelve measurable logistics pipeline segments.

		C4.1.2.2.  Set of business event/transactions used as the authoritative source for recording a business event beginning or ending point.

		C4.1.2.3.  Set of business rules, decision tables, and algorithms applied to the standard events/transactions to populate database pipeline segment performance data.

		C4.1.2.4.  Data that is available for download and analysis.

		C4.1.2.5.  Set of monthly reports that capture the performance for a month in the life of the logistics pipeline identified as Report Control Symbol  DD-AT&L(AR)1419.  

## C4.2.  POLICY.  DoD policy states that:  DoD materiel management shall operate as a high-performing and agile supply chain responsive to customer requirements during peacetime and war while balancing risk and total cost.  The DoD supply chain shall provide best-value materiel and services in support of rapid power projection and operational sustainment of U.S. forces as required by the National Military Strategy.  Potential disruptions within and outside the DoD supply chain shall be identified, monitored, and assessed in order to mitigate risk to supply chain operations.  Life-cycle management controls shall be applied to guard against counterfeit materiel in DoD supply chain.  Energy efficient products or services shall have preference in all procurements, except those products or services procured for combat or combat-related missions.[footnoteRef:1]  DoDM 4140.01Volumes 4, 8, and 10 are the principal supply chain policy documents that lay the foundation for the following paragraphs  [1:  DoDI 4140.01 DoD Supply Chain Materiel Management Policy:  March 6, 2019] 

	C4.2.1.  Logistics Response Time (LRT).  LRT is a supply chain metric that measures “the time between the date a requisition is established and the date the requisitioned materiel is received and posted by the requisitioner”, [footnoteRef:2]  LRT measures that elapsed time in days.  The Department of Defense has established LMARS as the single, authoritative, enterprise-wide source for performance reporting and analysis of LRT.   [2:  DoDM 4140.01 Volume 8 Materiel Data Management and Exchange, October 21, 2019] 

	C4.2.2.  Order Processing & Delivery Standards.  The DoD supply chain stakeholders and customers have order processing and delivery standards for the wholesale supply and distribution system.  These standards apply to the delivery of materiel to requisitioning customers within the Department of Defense and are established and presented in two formats:  Uniform Materiel Movement Issue Priority System (UMMIPS) Operational Need Goals (ONG) and time definite delivery (TDD) standards.  

		C4.2.2.1.  UMMIPS Operational Need Goals (ONG).  The first format describes ONGs agreed upon between USTRANSCOM, Military Services, and Combatant Commands and translated by the ODASD(Logistics) to be used in accordance with the (UMMIPS).  ONG is customer focused and seeks to meet customer delivery requirements based on the military importance of the customer and the urgency of the customer’s need.  Military importance is reflected in the Force/Activity Designator (F/AD) assigned to each unit.  The unit's F/AD and urgency of need designators (UND) are combined and reflected in requisitions as Issue Priority Designators (IPDs).  Customer should expect the use of IPD and required delivery dates to assign accurate methods of transportation for the delivery of the requisitioned materiel, while ONGs are used to measure the reliability of the DoD supply chain from the customer's viewpoint.  This version of the standards is translated to address the warfighter's or customer's expectations.  ONGs help assess how quickly shipments move depending upon the transportation priority that the Services assigned. 

		C.4.2.2.2.  Time Definite Delivery (TDD) Standards.  The second format presents standards as coordinated by USTRANSCOM with distribution stakeholders from the service providers’ perspective and approved by the Distribution Steering Group.  These standards are coordinated between distribution providers, suppliers, and Combatant Commands and used to measure the performance of the distribution network in shipping materiel from storage sites to customer locations based on supplier location, transportation mode, and consignee location (country).

		C.4.2.2.3.  Complimentary Formats.  ONGs and TDD standards work together to measure the responsiveness and reliability of the distribution processes to deliver required materiel to the customer within a given period of time.  By assessing actual performance against the TDD standards assigned to distribution providers, as well as actual performance against the ONGs that the customers specify, DOD monitors the effectiveness of distribution and reliability of materiel in terms the distribution provider requires and customers understand.

## C4.3.  ROLES AND AUTHORITIES

	C4.3.1.  Pipeline Measurement Process Review Committee  (PM PRC).  The PRCs provide a joint forum for each of the Defense Logistics Management Standards (DLMS) functional areas (finance and supply to include, but not limited to, requisitioning and issue procedures, physical inventory, disposition services, and supply discrepancy reporting) responsible for the development, expansion, improvement, maintenance, and administration of the DLMS.  The PM PRC reviews issues as requested by the ODASD(Logistics) relating to LRT and LMARS pipeline measurements of performance across currently measurable segments of the DoD supply chain.  It reviews and resolves comments on approved DLMS changes, deviations and waivers, and provides recommendations for implementation or disapproval.  Any unresolved action from the PRC will be referred to the appropriate Office of the Secretary of Defense (OSD) Principal Staff Assistant (PSA).[footnoteRef:3]  The PM PRC operates under the authority and within the framework documented below. [3:  Ibid.] 

	C4.3.2.  Office of the Deputy Assistant Secretary of Defense for Logistics (ODASD(Logistics)).  The ODASD(Logistics) will:

		C4.3.2.1.  Serve as the Office of the Secretary of Defense (OSD) sponsor of the Pipeline Measurement program, issuing policy, procedural guidance and instructions to develop, expand, improve, and maintain LMARS as developed and maintained in the PM PRC.

		C4.3.2.2.  Review and approve Pipeline Measurement program plans, priorities, schedules, and goals, and resolve policy and procedural issues where agreement cannot be obtained within the PM PRC.

		C4.3.2.3.  Champion efforts to identify funding sources to support and further the Pipeline Measurement program objectives.

		C4.3.2.4.  Ensure applicable coordination within OSD staff elements that are responsible for Pipeline Measurement performance measurement policy guidance or one-time instructional memoranda affecting functions assigned to this PRC.

		C4.3.2.5.  Support the implementation and use of standard data elements in accordance with policy guidance.

		C4.3.2.6.  Maintain contact with the PRC through the OSD Principal Staff Assistant (PSA) and the ODASD(Logistics) representative, and accept updates after each meeting or as appropriate.

		C4.3.2.7.  Ensure DoD senior leaders are advised of initiatives and plans as they are developed with respect to Pipeline Measurement performance data integrity and management.

		C4.3.2.8.  Monitor PRC activity to ensure compliance with policy, instructions, and standards.

	C4.3.3.  Defense Enterprise Data Standards Office (DEDSO).  DEDSO will appoint the chair of the PM PRC, who will: 

		C4.3.3.1.  Develop PM PRC meeting agendas and convene meetings as required.  

		C4.3.3.2.  Submit proposed recommendations for LMARS improvement to the committee members and the OSD PSA.  

		C4.3.3.3.  Document the PM PRC program objectives and business rules in DLM 4000.25, “Defense Logistics Management Standards (DLMS)”.

		C4.3.3.4.  In support of the Supply Chain Metrics Group, develop and document (maintain) program functional requirements for data collection, uniform business rules, computational algorithms, and management reporting and queries for DAAS to develop and execute the tool set for measuring LRT, and supporting the Components’ calculation and reporting of CWT, and TDD actual performance.

		C4.3.3.5.  Coordinate LMARS training with DAAS.  

		C4.3.3.6.  Report findings and recommendations of evaluations and reviews, with comments from the DoD Components and participating external organizations, to the OSD PSA through the use of standard DLMS configuration management procedures (e.g., proposed and approved DLMS changes).

		C4.3.3.7.  When possible, announce the meeting and identify the agenda items 30 calendar days in advance of the meeting.  

		C4.3.3.8.  Submit minutes of each PM PRC meeting within 14 calendar days of meeting completion to the PM PRC membership and the OSD PSA for review.

		C4.3.3.9.  Publish fully documented minutes of these proceedings to the ODASD(Logistics) and each participating DoD Component or external organization within 30 calendar days after the meeting.

		C4.3.3.10.  Maintain a current list of representatives to the PM PRC.  

		C4.3.3.11.  Present issues to the PM PRC for review and resolution.  

		C4.3.3.12.  Where PM PRC consensus cannot be obtained, document and present the issues to the OSD PSA for resolution.

	C4.3.4.  Defense Automatic Addressing System (DAAS).  DAAS will:

		C4.3.4.1.  Develop and maintain the databases, applications, training aids, and tools required to support LMARS.

		C4.3.4.2.  Attend all PM PRC meetings.

		C4.3.4.3.  Implement enhancements and modifications to LMARS documented via Approved DLMS Change (ADC) by DEDSO and approved by the PM PRC.

		C4.3.4.4.  Provide LMARS subject matter expertise to members of the PM PRC for dissemination to their respective Components.

		C4.3.4.5.  Provide LMARS measurement summaries using formats prescribed by policy.

		C4.3.4.6.  Ensure testing and validation of proposed changes to standard data elements for Pipeline Measurement performance measurement.

	C4.3.5.  DoD Components.  DoD Components will support the PM PRC by providing qualified, experienced representatives who will:

		C4.3.5.1.  Attend all Pipeline Measurement meetings.

		C4.3.5.2.  Submit agenda items to the Chair, PM PRC.

		C4.3.5.3.  Respond to tasking emanating from PM PRC meetings.

		C4.3.5.4.  Identify inter-DoD Component LRT requirements to the PM PRC for discussion and formulation of a solution.

		C4.3.5.5.  Develop and submit recommended DLMS change proposals to the PM PRC Chair for processing under DLMS configuration management procedures.

		C4.3.5.6.  Present the Component position and be authorized to negotiate and seek agreement with PM PRC members to achieve the objectives and standardization of LMARS.  Provide Component responses to proposed DLMS changes within specified timeframes.

		C4.3.5.7.  Promote and support LMARS within the respective Components and serve as the Components’ LMARS subject matter expert.

		C4.3.5.8.  Use metrics to assess the DoD Supply Chain pipeline performance and use as a basis for process improvements.  .

		C.4.3.5.9.  Conduct analyses and take appropriate actions within the Component to improve pipeline performance.  

		C4.3.5.10.  Review Monthly LMARS Outputs and Data

			C4.3.5.10.1.  Review monthly reports analyzing and researching unusual trends.  Significant changes need to be researched using the drill down capability to determine the root cause of anomalies.  Researchers should look for conditions such as one or more activities performing mass close outs of open aged records in a non-timely manner resulting in unusually long LRT.  The Anomaly Code list and report is also a tool to aid in determination of suspect data and performance reporting.  

			C4.3.5.10.2.  Component representatives to the PRC will identify data corrections required as a result of the above research and analyses to the PM PRC Chair and DAAS.  When warranted, the PM PRC chair will ensure prior coordination with the ODASD(Logistics) PM PRC representative before performing data corrections.  The data correction method will be determined by DAAS and coordinated with the PM PRC Chair.

			C4.3.5.10.3.  Table updates, business rule changes, and fill rule changes will be identified by the Components to the PM PRC Chair where changes have occurred in critical decision tables such as Routing Identifier Codes (RICs), DoD Activity Address Codes (DoDAACs), Combatant Commander (COCOM) designations, etc.

		C4.3.5.11.  Retain records of LRT for audit and oversight.  After those business rules are satisfied, defer to the Component’s applicable National Archives and Records Administration (NARA)-approved Component Records Disposition Schedule or NARAs General Records Schedule (GRS)  in accordance with DoDI 5015.02, DoD Records Management Program as the authoritative source for disposition *authority.[footnoteRef:4]* [4:  Refer to ADC 1151] 

C4.4  Reserved

C4.5.  LMARS  ARCHITECTURE

	C.4.5.1  Functional Architecture

		C4.5.1.1.  Data in LMARS is based on the capture by DAAS of the business events at the individual transaction level for each individual customer order/document number.  Excluded from this capture are transactions from Foreign Military Sales (FMS), extended required delivery dates (RDD)[footnoteRef:5], initial outfitting and cancelled and rejected orders.   [5:  RDDs beginning with S or X] 

		C4.5.1.2.  LMARS reports and measures the pipeline segment(s) completed for a document number in that report month.  The total document numbers that complete a segment and the time to complete each document are the key data LMARS captures and uses to calculate average segment time performance.  

		C4.5.1.3.  LMARS is a point in time reporting system.  When an item identified by a document number has shipped, the first four segments are reported in the monthly report corresponding to the month DAAS receives the shipment transaction.  Later actions within the pipeline are reported in the month during which that segment is completed.  With the exception of the ICP segment (ISPT), no segment is reported again for that document number in any succeeding months.  A materiel release order (MRO) denial will cause the ISPT segment to be re-reported with additional time for the denial and new MRO processing added.

			C4.5.1.3.1.  With the exception of segments one through three (which are dependent on the date DAAS receives the shipment transaction), the first date that DAAS receives a transaction, defined as a segment ending event, determines when that segment’s count and time is included in a month’s report.

			C4.5.1.3.2.  The last in-document date is used to compute the segment time.

			C4.5.1.3.3.  Segments one through four are all reported in the month that the shipment transaction is received.  Segments five through twelve and the total for segments one through twelve are reported in the month that the transaction for the segments end event is received by DAAS.

	C.4.5.2  Technical Transaction Architecture.  LMARS is based on information provided from Logistics On-Line Tracking System (LOTS).  LOTS is a database that stores logistical data received from DAAS.  

C4.6.  LMARS CONTENT

	C4.6.1.  Inputs.  The data sources LMARS uses to prepare the monthly reports are as follows:

		C4.6.1.1.  DAAS Routed DLMS/DLSS Transactions.  DAAS uses the legacy(DLSS)/DLMS transactions it processes to measure the logistic response time for wholesale-managed items.  

		C4.6.1.2.  DAAS  Non-routed Transactions.  There are two types of non-routed transactions.

			C4.6.1.2.1.  These are Component unique DICs (DLSS-like) 80 record position transactions used to report offline actions by the Services, DLA, and GSA.  These transaction DLMS/DICs are B99, BE9, 867I/D7,and 511R/CHA/CH1/ CO_ /CQ.  

			C4.6.1.2.2.  Integrated Data Environment (IDE) and Global Transportation Network (GTN) Convergence (IGC) User Defined Format (UDF) data feeds provide information to open and close the transportation pipeline segments.

		C4.6.1.3.  DLA Special Prime Vendor Data Feeds.  Special data feeds are via SFTP for Fresh Fruits and Vegetables (FFV), Semi Perishables, Maintenance Repair Operations (MRO), and Prime Vendor Medical (PVM).

		C4.6.1.4.  For DLA orders from RIC SMS, LMARS utilizes the procurement instrument identifier (PIID) from the EDI 850 Purchase Order as the source to determine if a direct vendor delivery is planned or unplanned.  DAAS converts the EDI 850 to a flat file to facilitate LMARS processing and sends the flat file to LMARS once a month.  At the beginning of each month, LMARS sorts the new EDI 850-based flat files by document number/suffix (since there may be multiples) and determines the earliest transaction received for each.  LMARS uses the earliest date received by DAAS to end Pipeline Segment 3 (ICP Processing Time) for each document number/suffix and start Segment 4 (Storage Activity Processing Time).  Segment 4 is used for every transaction, and identifies the MRO sending time to the depot/vendor to the date the item was released to the carrier in shipment transaction.  This identifies the time the depot or vendor took to do processing.  The MROs for vendors are the transactions identified by status codes BV or AB, however, DLA only uses the EDI 850.  DAAS will use the PIID from the EDI 850 flat file to determine the type of DVD.  Those including the type of procurement instrument D (in the 9th position of the PIID) will identify planned deliveries and LMARS will construe all other values as unplanned.

		C4.6.1.5.  Other External Data Feeds used to support weekly and monthly LMARS processing are the DoD Activity Address Directory (DoDAAD) and the national item identification number (NIIN) file provided by the Logistics Information Service.  Additionally the following data sources are used and require validation and update by the Components.

			C4.6.1.5.1.  Guard or Reserve DoDAACs.  A table of DoDAACs identifying guard and reserve units provided to DAAS by the Marine Corps and Army.

			C4.6.1.5.2.   Reparable/Non Reparable Indicator.  A table designating reparable items and non-reparable items provided by all Services

	C4.6.2.  Segment Definitions

		C4.6.2.1.  Logistics Pipeline Segment 1, “Requisition Submission Time” is the elapsed time from the date in the requisition number to the date that DAAS received the requisition.

		C4.6.2.2.  Logistics Pipeline Segment 2, “Internal Service Processing Time” is the elapsed time beginning when DAAS releases a requisition for internal service or non-Wholesale action and ending when the requisition is returned and released to a Wholesale ICP.

		C4.6.2.3.  Logistics Pipeline Segment 3, “Inventory Control Point Processing Time” measures the time from DAAS release of a requisition to an ICP, until DAAS receipt of an MRO transaction directing shipment.

		C4.6.2.4.  Logistics Pipeline Segment 4, “Storage Activity Processing Time” is measured from the date DAAS received the MRO to the date shipped/released in an AS/AR/AU/856S (Shipment Status) transaction.

		C4.6.2.5.  Logistics Pipeline Segment 5, “Storage Activity to Consolidation Containerization Point Processing Time” is measured from the date shipped/released (856S/AS/AR/AU) to the  Consolidation and Containerization Point (CCP), to the date received (856A/TAV/TAW) by the CCP.

		C4.6.2.6.  Logistics Pipeline Segment 6, “Consolidation Containerization Point Processing Time” is measured from the CCP’s date of receipt until the date of release (856A/TAV/TAW).

		C4.6.2.7.  Logistics Pipeline Segment 7, “CONUS In-Transit Time” is measured from the date shipped (856S/AS/AR/AU) by the shipper (may be contractor, storage depot, or CCP) and ends on the date received (527R/DRA/DRB) by a CONUS customer or port of embarkation (POE) for overseas movements.

		C4.6.2.8.  Logistics Pipeline Segment 8, “Port of Embarkation Processing” is measured from the date of POE receipt to the date of POE release.

		C4.6.2.9.  Logistics Pipeline Segment 9, “Port of Embarkation to Port of Debarkation In-Transit Time” is measured from POE date of release to port of debarkation (POD) date of receipt.

		C4.6.2.10.  Logistics Pipeline Segment 10, “Port of Debarkation Processing” is measured from the date of POD receipt to date of POD materiel release.

		C4.6.2.11.  Logistics Pipeline Segment 11, “In-Theater In-transit Time” is measured from the POD release date to the consignee receipt or “tailgate” date, for all OCONUS areas.

		C4.6.2.12.  Logistics Pipeline Segment 12, “Receipt Take-Up Time” is the time between consignee receipt or “tailgate” date and the record posting date in the MRA transactions 527R/DRA/DRB.  ***A receipt or the image of receipt may also be used to calculate this segment when the MRA is not available.***

		C4.6.2.13.  Total Pipeline Time is measured from the date in the requisition number (start of segment 1) to the date the customer posts it to the property record (end of segment 12).

	C4.6.3.  Business Rules.  The paragraphs in this section describe the key tables that the LMARS uses to determine the appropriate reporting of a requisition’s life cycle events, DAAS procedures, and the output report-specific data population rules and display.

		C4.6.3.1.  Key Tables

			C4.6.3.1.1.  LMARS Type of Fill Table.  

				C4.6.3.1.1.1.  LMARS uses this table to determine in which applicable report(s) each document number, completing a pipeline segment within the report month, is included.  Paragraph C4.6.5 discusses each report in detail.  

				C4.6.3.1.1.2.  Examination of the data in the transaction against the values in Columns “A” through “H” of the  LMARS Type of Fill Table yields one of the Type of Fills below (which equate to Column “I”).  The derived Type of Fill is inserted into the LMARS database date element “CORP-FILL-TYPE” for that transaction document number.  The Type of Fill and their applicable Reports are identified below.

**LMARS Records Type of Fill Tables**

				A = Immediate shipment from depot

				B = Planned DVD Shipments

				C = Backordered

				D = Unplanned DVD Shipments

				O = Other

**LMARS Reports****Applicable Type of Fill Table Codes**

				Total				Type of Fill = A, B, C, D, O 

				Immediate		Type of Fill = A

				Planned DVD	Type of Fill = B

				Backorder		Type of Fill = C

				Unplanned DVD	Type of Fill = D

				Other			Type of Fill = O

			C4.6.3.1.2.  Output Report Specific Tables.  The LMARS application makes use of additional tables to populate the data in the specific monthly output reports.  

			C4.6.3.1.3.  DLA Special Report Type of Fill Table.  LMARS provides a series of reports that are tailored for DLA management usage.  

	C4.6.4  DAAS Procedures

		C4.6.4.1.  Daily Continuous Processing.  With the exception of special data feeds, transactions are received at DAAS continually, -then copied and parsed to the LOTS database.

		C4.6.4.2.  Weekly Processing.  Every Friday at midnight DAAS performs the following processing procedure in preparation for the monthly processing:

			C4.6.4.2.1.  LOTS database is copied and integrated with the temporary LMARS Master file.

			C4.6.4.2.2.  A temporary LMARS Master file is created for that week’s  reporting.

			C4.6.4.2.3.  LMARS business rules are applied to the temporary LMARS Master file.

			C4.6.4.2.4.  An LMARS flat file is produced and put on a guest server for Secure File Transfer Protocol (SFTP).

			C4.6.4.2.5.  Flat files tailored to each Service/Agency are created.

			C4.6.4.2.6.  Output.  Weekly activity file generated.

		C4.6.4.3.  Monthly Processing.  On the first of each month the following processes are performed:

			C4.6.4.3.1.  LOTS database is copied. 

			C4.6.4.3.2.  Special Feed data integrated with LMARS Master file.

			C4.6.4.3.3.  LMARS business rules applied to the new LMARS Master file.

			C4.6.4.3.4.  Test reports for the month are produced.

			C4.6.4.3.5.  Top 300 drilldown reports produced.

			C4.6.4.3.6.  Anomaly file produced.

			C4.6.4.3.7.  The test reports, anomaly file, and the Top 300 drill down reports are used to identify and correct any DAAS processing errors and to identify anomalies and unusual trends that the Services need to research and verify.  The DAAS processing errors, if any, are corrected and the reports are rerun.  The applicable LMARS Service Contact Points are provided Top 300 drill down reports when necessary and requested to determine whether the data is valid.  The Services with anomalies and/or unusual trends have five days to respond.  Based on their response and the PM PRC chair authorization, data identified as invalid are removed, the rationale is documented, and the LMARS reports are rerun and become final for that month.

		C4.6.4.4.  Retention requirements.  The monthly LMARS reports are maintained in accordance with DoDI 5015.02, DoD Records Management Program. [footnoteRef:6]  DAAS must verify with the DLA Records Officer that retention requirements are incorporated into any APPLICABLE NARA GRS or NARA approved DLA Records Disposition Schedule. [6:  Refer to ADC 1151] 

		C4.6.4.5. LMARS User Accounts.  The instructions for obtaining a user account are found on the DAAS Website.  Click on “Request Login ID and Password” and follow the screens for completing the On-Line Systems Access Request.  It is important to note that once a user has obtained access approval for LMARS, the user must keep the account active by logging into LMARS at least once every 30 days.  If not, the account will be placed in REVOKED status, and another 15 days from that point the account will be deleted if the user has not logged in for 45 days.  

			C4.6.4.5.1.  The Logistics Metrics Analysis Reporting System at DAAS maintains logistics pipeline information for all Wholesale items.  LMARS is populated with information from the DLMS and legacy MILSTRIP and MILSTRAP transactions that flow through DAAS.  LMARS reports response time within the 12 logistics pipeline segments:  All reporting time frames are expressed in terms of days.  Current standard reports are available via the Web on a monthly basis.

			C4.6.4.5.2.  Data download capabilities.  DAAS can provide data downloads in a variety of forms.  Monthly reports provide a link at the top that allows the user to directly download reports to a Microsoft Excel Spreadsheet.  For other database transfers/downloads of LMARS data and/or tables the requester should contact the Service/Agency PM PRC point of contact, or if not known, DAAS.  Database transfers/downloads of LMARS data for a specific Service or Agency, are performed by that Service or Agency.

		C4.6.4.6.  Handling of Corrections.  The Components and DAAS review the initial runs of each month’s reports prior to publication to identify any unusual trends.  Data corrections required as a result of that research and analysis will be identified to the PM PRC Chair and DAAS.  When warranted, the PM PRC chair will ensure prior coordination with the ODASD(Logistics) PM  PRC representative before correcting data. DAAS will determine the data correction method in coordination with the PM PRC Chair and  the Component that identified the problem.

	C4.6.5.  Output Reports.  There are six types of Output Reports:  

· Guard

· Reserve 

· Wholesale ICP 

· Contractor Wholesale ICP 

· Wholesale ICP Reparable NSNs

· ICP GSA  

Each of these reports follows a standard format and is reported by geographic area and priority.  The reports are further defined by Component and type of fill.  

		C4.6.5.1.  Major Report Categories.  The user selects the desired Major Report Category from the main LMARS Web Page.  The report categories are identified below:

			C4.6.5.1.1.  Guard Report.  To be included in the Guard Report, the document number’s Ship-To address or Consignee must be a Guard DoDAAC, as identified by the Components.  Note that the transactions included in the Guard Report are not included in the Wholesale ICP Report.  DAAS maintains an internal table supplied by the Components that identifies Guard unit DoDAACs. 

			C4.6.5.1.2.  Reserve Report.  To be included in the Reserve Report the transaction’s Ship-To address or Consignee must be a Reserve DoDAAC as identified by the Components.  Note that the transactions included in the Reserve Report are not included in the Wholesale ICP Report.  DAAS maintains an internal table of reserve DoDAACs. 

				C4.6.5.1.3.  Wholesale ICP Reparable NSNs Report.  The Wholesale ICP Reparable NSNs Report includes a subset of the document numbers in the Wholesale ICP Report.  To be included in the Wholesale ICP Reparable Report at least one Service must identify the NSN being ordered on a given transaction as a Reparable NSN.  

			C4.6.5.1.4.  Contractor Wholesale ICP.  To be included in the Contractor Wholesale ICP Report transaction’s Ship-To or Consignee address must contain a Contractor DoDAAC.  Note that the transactions included in the Contractor Wholesale ICP Report are not included in the Wholesale ICP.  Contractor DoDAACs are in Table H.

			C4.6.5.1.5.  Wholesale ICP Reparable NSNs.  The Wholesale ICP Reparable NSNs Report includes a subset of the document numbers in the Wholesale ICP.  To be included in the Wholesale ICP Reparable Report, at least one Service must identify the NSN being ordered on a given transaction as a Reparable NSN.

			C4.6.5.1.6.  ICP GSA.  Only GSA-filled transactions are included in the GSA Report.  To be included in the GSA Report, the transactions eligible for LMARS reporting in a given month, with the exception of those for Guard, Reserve, or Contractor DoDAACs, must identify GSA as the ICP.  The exception to this is any transaction with Guard, Reserve, or Contractor DoDAACs. 

		C4.6.5.2.  Major Report Category Sections.  Each Major Report Category is composed of tabs which are at the top or bottom of the report.  The titles of the tabs and section headings are (1) “Composite”, (2) “Army”, (3) “Air Force”, (4) “Navy”, (5) “Marine Corps”, (6) “Coast Guard”,  (7) “DLA” and (8) “Others”. 

			C4.6.5.2.1  Type of fill Table Sub-Sections.  Each Major Report Category tab is further sub-divided into six Type of Fill Table Sub-Sections:  Total, Immediate Fill (identified as type of fill A in the type of fill table).  Planned DVD (type of fill B).  Backordered (type of fill C), Unplanned DVD (type of fill D), and Other (type of fill O).  Each Sub-Section has a total line.  The LMARS Type of Fill Table discussed in paragraph C4.6.3.1 describes the Type of Fill Table composition, usage, mapping Type of Fill to the LMARS Type of Fill Report Sub-Sections, and Web link to the current LMARS Type of Fill Table.  Each Service and Agency must ensure its servicing ICPs RICs are listed in the LMARS output specific Table D in order for LMARS to include their transactions in the monthly reporting.  The Type of Fill Table Sub-Sections titles and descriptions are below:

			C4.6.5.2.2.  “TOTAL” Type of Fill Sub-Section.  The “TOTAL” Type of Fill Sub-Section reflects Wholesale requisition pipeline activity of the cumulative document numbers of each of the Report Sections identified in paragraph C4.6.5.2.1.  Reporting starts when DAAS receives a shipment transaction.  In the event there is not a shipment transaction, the reporting will start with the receipt of the MRA receipt transaction.  This Sub-section contains all Type of Fill = A, B, C, D, O.

			C4.6.5.2.3.  “IMMEDIATE” Type of Fill Sub-Section.  The “IMMEDIATE” Type of Fill Sub-Section reflects Wholesale requisition pipeline activity of immediate issues for each of the Report Sections identified in paragraph C4.6.5.2.1 above.  One of the following conditions must be met to qualify as an immediate issue: (1) The first or only Supply Status is BA. (2) The last Supply Status must be BA and received within five days of first status, and no Backorder Status ever received.  Direct Vendor Deliveries, whether planned or unplanned, are not considered immediate issues.  Reporting starts when DAAS receives a shipment transaction.  In the event there is not a shipment transaction, the reporting will start with the receipt of the MRA receipt transaction.  This Sub-section contains all the document numbers with Type of Fill = A.

			C4.6.5.2.4.  “PLANNED” Type of Fill Sub-Section.  The “PLANNED” Type of Fill Sub-Section reflects Wholesale requisition pipeline activity of Planned Direct Vendor Delivery (DVD) issues for each of the Report Sections identified in paragraph C4.6.5.2.1  For a transaction to qualify as a Planned DVD it must meet the criteria specified in the LMARS type of file table.  Reporting starts when DAAS receives a shipment transaction.  In the event there is not a shipment transaction, the reporting will start with the receipt of the MRA receipt transaction.  This Sub-section contains all the document numbers with Type of Fill= B.  For DLA orders, LMARS utilizes the PIIN from the EDI 850 Purchase Order as the source to determine if a Direct Vendor Delivery is planned or unplanned.  

			C4.6.5.2.5.  “BACKORDERED” Type of Fill Sub-Section.  The “BACKORDERED” Type of Fill Sub-Section reflects Wholesale requisition pipeline activity of document numbers that were at some time backordered within each of the Report Sections identified in paragraph C4.6.5.2.1 .  The following criteria must be met to qualify as a backorder:  (1) DLMS 870S/AE received, prior to shipment, must have a BB, BC, or Service specified (Table A) backorder code.  (2) Direct Vendor Delivery, whether planned or unplanned, was not received prior to shipment.  To be included in the “BACKORDERED” Sub-section the transaction must meet the criteria for backordered materiel in the LMARS Type of Fill Table = C.

			C4.6.5.2.6.  “UNPLANNED” Type of Fill Sub-Section.  The “UNPLANNED” Type of Fill Sub-Section reflects Wholesale requisition pipeline activity of unplanned direct vendor delivery (DVD) issues for each of the Report Sections identified in paragraph C4.6.5.2.1.  Reporting starts when DAAS receives a shipment transaction.  In the event there is not a shipment transaction, the reporting will start with the receipt of the MRA receipt transaction.  This Sub-section contains all the transactions within the Major Report Category and Section that contain Type of Fill= D.  

			C4.6.5.2.7.  “OTHER” Type of Fill Sub-Section.  The “OTHER” Type of Fill Sub-Section reflects Wholesale requisition pipeline activity of transactions that did not meet the criteria for Immediate Issue, Backorder, Planned or Unplanned DVD for each of the Report Sections identified i paragraph C4.6.5.2.1.  Reporting starts when DAAS receives a shipment transaction.  In the event there is not a shipment transaction, the reporting will start with the receipt of the MRA receipt transaction.  This Sub-section contains all the transactions within the Major Report Category and Section that contain Type of Fill=O.

		C4.6.5.3. Delivery Area and Issue Processing Group Row Headings.  These headings are repeated within each Major Report Category Section and its Sub-Sections.  Column A of the spreadsheet output identifies the breakout within the Sub-Section for each of the five delivery areas (CONUS, OCONUS1, OCONUS2, OCONUS3, OCONUS4).  Each Delivery Area is further broken out into the three Issue Processing Groups (IPGs).  The IPG headings are IPG 1, IPG 2, and IPG 3, and the TOTAL/AVERAGE line applicable to each pipeline segment and a grand “TOTAL” line appear at the bottom.

			C4.6.5.3.1.  Delivery Area Row Headings.  The five delivery areas utilized for LMARS are the COCOMS.  The  headings are CONUS, OCONUS1, OCONUS2, OCONUS3, and OCONUS4.  The authoritative source for COCOM locations is USTRANSCOM.  USTRANSCOM will update the DoDAAD, and the DoDAAD feeds data into LMARS.  LMARS will utilize the DoDAAD updates with the exception of Navy Mobile Units.  In order for LMARS to calculate LRT accurately for Navy Mobile Units afloat, the Navy will provide to DAAS an updated NAVY AFLOAT FILE via Secure File Transfer Protocol (SFTP) at the end of the third week of each month.  LMARS will access this file from DAAS for reporting LRT. 

The LMARS Delivery Areas are consistent with the USTRANSCOM Time Definite Delivery (TDD) areas, 

**LMARS Area****TDD Areas**

				CONUS 				USNORTHCOM

				OCONUS1			USEUCOM/USAFRICOM

				OCONUS2			USCENTCOM

				OCONUS3			USINDOPACOM

				OCONUS4			USSOUTHCOM/USNORTHCOM

LMARS makes no distinctions between Airlift and Sealift delivery areas.

			C4.6.5.3.2.  Issue Processing Group Row Labels.  Each Delivery area is further broken out into the three Issue Processing Groups (IPG 1, IPG 2, and IPG 3) and the Total/Average line applicable to each pipeline segment within and a grand “TOTAL” line appear at the bottom.  Standard Uniform Materiel Movement and Issue Priority System (UMMIPS) Priority Designator and IPG groupings apply.  The IPG  is determined by the priority designator in the document.  The priority designator of the document can be modified up until the item is shipped; after that point, it will never change for that document.  IPGs are groupings of Issue Priority Designators (IPDs) as shown below:

· IPDs 01, 02, and 03 form IPG I

· IPDs 04, 05, 06, 07, and 08 form IPG II

· IPDs 09, 10, 11, 12, 13, 14, and 15 form IPG III.

		C4.6.5.4.  Column/Pipeline Segment Heading and Data Descriptions.  The following paragraphs define the pipeline segment headings and data content that appears under each heading for a particular row heading.  Where applicable, DLMS /DLSS (e.g., 940R/A5_), 856S/AS_  and 527/DRA/DRB, or receipt image are indicated to denote which transactions are used to measure the beginning and ending of the pipeline segments.  Note that in all cases data values displayed in blue are active.  If the reviewer places the curser over the data value and clicks the value, the document numbers and their associated data will be presented. 

			C4.6.5.4.1.  Spreadsheet Report Columns B and C

· Logistics Pipeline Segment 1 – “Requisition Submission Time” (See C4.6.2.1.)

· Report Spreadsheet Heading 1 – “REQN SUBMIT”

· LMARS database name “RST – NODE”.

Columns B and C reflect the month’s data reported for Segment 1, Requisition Submission Time.  Spreadsheet column B shows the number of Wholesale requisitions submitted for each area’s Processing Group.  Service unique processing rules have identified additional transactions (Table B) included in this column.  Requisitions for National Guards, Reserve Units, and Contractors are excluded from these reports.  Requisitions for Foreign Military Sales (FMS), Initial Outfitting (Table C), or with RDDs beginning with “S” or “X” are excluded from all LMARS reports.  Column C reflects this segment’s time, calculated by subtracting the document date from the DAAS receipt date.  RST for images of requisitions submitted to DAAS (511R/CH1, 527R/CHA BE9, and 867I/D7_ is limited to 30 days or less.  The spreadsheet column C shows the average requisition submission time for each Processing Group.  At the bottom of each area is the total number and weighted average of requisitions DAAS received.  The last row in the report provides the TOTAL requisitions and weighted time in columns B and C for this segment.  Transactions that failed DAAS edits are not included until or unless they are resubmitted.

			C4.6.5.4.2.  Spreadsheet Report Columns D & E

· Logistics Pipeline Segment 2, “Internal Service Processing Time” (See C4.6.2.2.)

· Report Spreadsheet Heading 2 – “SERVICE PROCESS”

· LMARS database name “SPT – NODE”.

An example of Internal Service Processing is the processing by Naval Supply Systems Command (NAVSUP) Fleet Logistics Centers (FLCs).  This segment time begins when DAAS releases a requisition for internal Service (non-Wholesale (to a RIC other than that on Table D)) action and ends when it is returned and released to a Wholesale ICP (Table D).  The number of requisitions and average times are shown for each area’s Processing Group.  Total requisitions DAAS released and their weighted average are shown at the bottom of each area and on the last data line of the report.  DAAS processing time is not shown but is reflected in the Total Order-Receipt computations.

			C4.6.5.4.3.  Spreadsheet Report Columns F and G

· Logistics Pipeline Segment 3, “Inventory Control Point (ICP) Processing Time” (See C4.6.2.3.)

· Report Spreadsheet Heading 3 – “ICP PROCESS”

· LMARS database name “ISPT – NODE”.

This segment measures the time from DAAS’ release of a requisition to a Wholesale ICP, until DAAS’ receipt of an issue transaction.  Issue transactions can be an MRO, 940R/A5_ transaction, a Table E listed equivalent, an 870S/AB_ (Direct Delivery Notice) transaction, or an 870S/AE_ (Supply Status) transaction with BV status, indicating direct vendor delivery.  There may be multiple ICP actions taken on a requisition, but passing, referral, backorder, or delayed actions are not used to close this segment.  Supply status of BQ, BR, B4, C_, D1-D8, except D7, DB, DN, DQ, DR, or specified intra-service codes (Table F), indicating rejection or cancellation will drop a requisition from being reported unless shipment and/or receipt is indicated.  The number of “issues” transactions is shown in column F and average times are in column G. 

			C4.6.5.4.4.  Spreadsheet Report Columns H and I

· Logistics Pipeline Segment 4, “Storage Activity Processing Time” (See C4.6.2.4.)

· Report Spreadsheet Heading 4 – “STORAGE ACTIVITY”

· LMARS database name ”SAPT – NODE”.

The time is measured from when DAAS receives the defined MRO to the date shipped/released in DLMS/DIC 856S/AS_ /856S/945A/AU_ (Shipment Status) transaction.  When Shipment Status is not available, the date in a materiel release confirmation (MRC) DLMS/DIC 940R/945A/AR_ transaction is used to close the segment.  In the case of DVDs, time is measured from DAAS’ receipt of a DLMS/DIC 870S/AB_ transaction, or a DLMS/DIC 870S/AE_ transaction with BV status, to the date shipped/released in a DLMS/DIC 856S/AS_ ,856S/945A/AU_ or DLMS/DIC 940R/945A/AR_  transaction.  The number of shipments and average processing times are shown in Columns H and I.

			C4.6.5.4.5.  Spreadsheet Report Columns J and K

· Logistics Pipeline Segment 5, “Storage Activity to Consolidation Containerization Point (CCP) Processing Time” (See C4.6.2.5.)

· Report Spreadsheet Heading 5 – “STORAGE TO CCP”

· LMARS database name “DCPT – NODE”.

The time is measured from the date shipped/released by the storage activity to the CCP’s receipt date reported in the TAV, TAW, or the IGC provided transaction. DLMS transactions from commercial carriers may also be used in this segment.  The count of the number of shipments to a CCP and average processing times are displayed in columns J and K respectively.  **NOTE**:  When both the source of materiel and the Customer delivery point are in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs.

			C4.6.5.4.6.  Spreadsheet Report Columns L and M

· Logistics Pipeline Segment 6, “CCP Processing Time” (See C4.6.2.6.)

· Report Spreadsheet Heading 6 – “CCP ACTIVITY”

· LMARS database name “CPT – NODE”

For OCONUS, and only when a CCP is used, time is measured from the CCP’s receipt and release dates in the TAV, TAW, or a GTN provided transaction. The count of the number of shipments processed by a CCP and average processing times are shown in columns L and M respectively.  **NOTE:**When both the source of materiel and the Customer delivery point are in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs.

			C4.6.5.4.7.  Spreadsheet Report Columns N and O

· Logistics Pipeline Segment 7, “CONUS In-Transit Time” (See C4.6.2.7.)

· Report Spreadsheet Heading 7 - “CONUS IN-TRANSIT”

· LMARS database name “CIT – NODE”

There are two differing movement possibilities for this segment; however, they are mutually exclusive at the document level.  The start and stop times will depend upon whether a CCP is in the pipeline for the document number.  The following are the two mutually exclusive methods for the computation of time for a specific document number.

·  Segment 7A – For OCONUS shipments moving through a CCP, time is measured from the CCP’s release to the POE’s receipt.  Dates/times for calculating this segment come from the TAV/TAW or IGC-provided transaction.  Average times and the number of shipments from a CCP are shown.  

· Segment 7B – For CONUS shipments, it’s the time from the storage or vendor date shipped/released, in the AS_/AU_ or AR_ transaction, to the consignee’s receipt or “tailgate” date.  Unless transactions with “tailgate” dates are provided, this segment will not be populated.  (NOTE:  A 527R/DRA/DRB may have two date fields; one for a record posting date, used in Segment 12, and one for a “tailgate” date.  Each Service/Agency is to identify any transactions and/or record positions used for “tailgate” dates.)  For OCONUS shipments, when a CCP is not used, time is measured from the shipped/released date to the POE’s receipt date in a GTN provided transaction.  DLMS transactions from commercial carriers may be used in this segment (for CONUS and OCONUS).  The times and the number of shipments to a CONUS consignee or POE are shown. 

			C4.6.5.4.8.  Spreadsheet Report Columns P and Q

· Logistics Pipeline Segment 8, “POE Processing”(See C4.5.2.8.) 

· Report Spreadsheet Heading 8 – “POE ACTIVITY”

· LMARS database name “POET – NODE”

POE receipt and release dates, provided by GTN or other In-Transit data transactions, are used to calculate OCONUS times.  The average times and number of shipments processed by a POE will be shown.  NOTE:  When both the source of materiel and the Customer delivery point are in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs.

			C4.6.5.4.9.  Spreadsheet Report Columns R and S

· Logistics Pipeline Segment 9, “Port of Embarkation to Port of Debarkation In-Transit Time” (See C4.6.2.9.)

· Report Spreadsheet Heading 9 – “POE to Port of Debarkation (POD)”

· LMARS database name “ITTT – NODE”

Measurement is from POE release to POD receipt.  IGC provides the transactions needed to calculate this segment’s times.  DLMS or other In-Transit data transactions, if available, may also be used.  Times and numbers for these columns are shown similar to the previous segments.  NOTE:  When both the source of materiel and the Customer delivery point are in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs.

			C4.6.5.4.10.  Spreadsheet Report Columns T and U

· Logistics Pipeline Segment 10, “POD Processing” (See C4.6.2.10.)

· Report Spreadsheet Heading 10 – “POD Activity”

· LMARS database name “PODT – NODE”

IGC provides transactions with the POD receipt and release dates/times needed to calculate the OCONUS entries shown for this segment.  **NOTE:**When both the source of materiel and the Customer delivery point are in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs.

			C4.6.5.4.11.  Spreadsheet Report Columns V and W

· Logistics Pipeline Segment 11, “In-Theater In-transit Time” (See C4.6.2.11.)

· Report Spreadsheet Heading 11 – “IN-THTR IN-TRANS”

· LMARS database name “ITIT – NODE”

Measurement is from the POD release date to the consignee receipt or “tailgate” date, for all OCONUS areas.  Unless transactions with “tailgate” dates are identified, this segment will not be populated.  (NOTE: Transactions 527R/DRA/DRB), may have two date fields; one for a record posting date, used in Segment 12, and one for a “tailgate” date.  Each Service/Agency is to identify any transactions and/or record positions used for “tailgate” dates.)  DLMS transactions that measure commercial express service time from storage or vendor to consignee receipt will be included in this segment.  Average times and the number of In-Theater shipments are shown. **NOTE:**When both  the source of materiel and the Customer delivery point are in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs.

			C4.6.5.4.12.  Spreadsheet Report Columns X and Y

· Logistics Pipeline Segment 12, “Receipt Take-Up Time” (See C4.6.2.12.)

· Spreadsheet Report Heading 12 – “RCPT TAKE UP”

· LMARS database name “RTT – NODE”

For CONUS and OCONUS (see NOTE in Segments 7B and 11), it is the time between consignee receipt or “tailgate” date and the record posting date in the 527R/DRA/DRB,.  Quantity and discrepancy Code fields in the 527R/DRA/DRB are not checked to verify total receipt.  IGC or DLMS transactions, if applicable, may be used.  If only a record posting date is available, this segment will not be populated.  Times and number of receipted shipments are shown.

			C4.6.5.4.13.  Spreadsheet Report Columns Z and AA

· Logistics Pipeline Segment 13, “Total Order-Receipt Time”

· Spreadsheet Report Heading “TOTAL ORDER RECEIPT”

· LMARS database name “TPT – NODE”

This is the time between the requisition date and the receipt record posting date.  These columns are only populated when the order to receipt cycle has been completed.  A defined requisition (or a defined MRO) and a materiel receipt acknowledgment are the minimum transactions needed before a cycle’s time is reported.  To calculate the average time for each area’s IPG, the aggregate time of the completed cycles is divided by the number of completions.  At the bottom of each area is the number and weighted average of document numbers that were completed during the reporting month.  Included in these two columns are numbers and averages for DLA’s Prime Medical Vendor (PMV), Maintenance Repair Operations (MRO), and Perishable and Semi-Perishable orders.  See Table G for their computation logic.

			C4.6.5.4.14.  Spreadsheet Report Columns Z and AA.  The last two columns also show Total Order-Receipt, but with the document numbers with the highest five percent in terms of longest times in each area’s IPG eliminated.  The objective of these columns is to present counts and average times with the extremes removed.  Note:  These columnar calculations are not performed for the GUARD, RESERVE, and CONTRACTOR Major Reports.

C4-1	CHAPTER 4