ADC 462, Attachment, Page 1

ADC 462

Initial Publication of Logistics Metrics Analysis Reporting System (LMARS) 

Chapter as DOD 4000.25-M “Defense Logistics Management Standards (DLMS) 

Manual," Volume 6, Chapter 4

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Service/Agency: DLA Logistics Management Standards, DLA J627

b. Originator: DLA Logistics Management Standards 

2. FUNCTIONAL AREA: Logistics Metrics

3. REFERENCES: 

a. OSD (L&MR/SCI) Memorandum, dated September 24, 2010, subject; 

“Establishment of the Pipeline Measurement (PM) Process Review Committee”

b. DOD Instruction 4140.61, dated December 14, 2000, subject; “Customer Wait 

Time and Time Definite Delivery”

c. DOD Regulation 4140.1-R, dated May 23, 2003, subject; “Supply Chain Materiel 

Management Regulation”

d. DOD Manual 4000.25-M, Defense Logistics Management System

4. REQUESTED CHANGE:

a. Description of Change: This change is the initial publication of Chapter 4,

Logistics Metrics Analysis Reporting System (LMARS) of Volume 6, reference d. above.

b. Background: Reference a. above established the PM PRC to propose, manage, 

and implement enhancements to LMARS to support the goals and policies contained in 

references b. and c. The PM PRC is responsible via reference a. for the configuration 

management of the LMARS. The attachment to this ADC documents the “as is” state of 

LMARS and will serve as the initiation of the configuration management of the changes 

proposed and approved by the PM PRC. 

c. Procedures: 

1) Currently no formal LMARS process and procedures exist. The DLA 

Transaction Services developed and posted to its web site a number of independent 

documents related to LMARS. These documents were developed ten years ago and serve 

as the only existing documentation. This ADC compiles and organizes these existing 

documents into a single formally published “as-is” baseline for LMARS. The 

formalization of the existing documents will be published as Chapter 4 of Volume 6 to 
ADC 462, Attachment, Page 2

reference d. above.

2) The attached LMARS Chapter covers:

(a) The policies governing Customer Wait Time (CWT), Logistics Response 

Time (LRT) and Time Definite Delivery, all of which to varying degrees either depend 

on LMARS data or likely will in the future.

(b) The organizational roles and responsibilities of the participants PM PRC 

and LMARS users.

(c) The methodology for managing the configuration of LMARS and its 

functional and technical architecture.

(d) The key inputs to LMARS, business rules and computation applied to the 

inputs, logistics pipeline segment definitions, and the output reports and files.

3) This ADC does not propose or establish any new procedures. Subsequent 

ADCs staffed through the PM PRC will document changes and enhancements to the 

LMARS baseline document at enclosure 1.

5. REASON FOR CHANGE:

a. To provide a single compilation of baseline documentation of LMARS in its “asis” state. This baseline provides a reference point from which all future enhancements to 

LMARS will be documented.

 

b. The documentation will be posted to the DLA Logistics Management Standards

web site, providing LMARS users a readily available source for understanding the 

LMARS sources of information, the business rules applied, and output capabilities. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages:

1) Provides a single point of reference for all LMARS information formalizing it 

within DOD Manual 4000.25-M, Defense Logistics Management System (DLMS).

2) The formalization of LMARS within Volume 6, Chapter 4 of the DLMS 

manual and its publication/posting on the DLA Logistics Management Standards web site 

makes it accessible to users 24 hours a day, seven days a week.

b. Disadvantages: None

7. IMPACT: DLA Transaction Services should remove the documentation currently 

posted to their Web site and reference users to the DLA Logistics Management Standards 
ADC 462, Attachment, Page 3

Web site. Components should update any internal documentation to agree with or point 

to the new Chapter 4, “Pipeline Measurement” to ensure consistent documentation across 

the enterprise. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: The staffing and publication of Chapter 

4, Volume 6, of reference d. above will eliminate the need for separate and potentially 

conflicting Pipeline Measurement and LMARS information.
DOD 4000.25-M Volume VI, TBD

C4-1 Enclosure 1, CHAPTER 4.

CHAPTER 4

PIPELINE MEASUREMENT (PM)

Table of Contents

Subject Page

C4.1. GENERAL C4-1

C4.1.1. Purpose of Chapter C4-1

C4.1.2. Purpose of Logistics Management Analysis Reporting System (LMARS) C4-1

C4.2. POLICY: C4-2

 C4.2.1. Logistics Response Time C4-2

C4.2.2. Customer Wait Time (CWT) C4-2

 C4.2.3. Time Definite Delivery (TDD) C4-2

C4.3. ROLES AND AUTHORITIES: C4-3

C4.3.1. Pipeline Measurement Process Review Committee C4-3

C4.3.2. Office of the Assistant Secretary of Defense, Supply Chain Integration C4-3

C4.3.3. DLA Logistics Management Standards C4-4

C4.3.4. DLA Transaction Services C4-5

C4.3.5. DOD Components C4-5

C4.4. CONFIGURATION MANAGEMENT C4-6

C4.4.1. PM PRC Administration C4-6

C4.4.2. Proposed/Approved DLMS Change Process C4-7

C4.4.3. DLA Transaction Services Technical Documentation C4-7

C4.5. LMARS ARCHITECTURE C4-8

C.4.5.1 Functional Architecture C4-8

C.4.5.2 Technical Transaction Architecture C4-9

C4.6. LMARS CONTENT C4-8

C4.6.1. Inputs C4-8

C4.6.2. Segment Definitions C4-9 

C4.6.3. Business Rules C4-11

C4.6.4. DLA Transaction Services Procedures C4-12

C4.6.5. Output Reports C4-14
DOD 4000.25-M Volume VI, TBD

C4-2 Enclosure 1, CHAPTER 4.

CHAPTER 4 

PIPELINE MEASUREMENT (PM)

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 Metric Analysis 

Reporting System (LMARS). It establishes the information requirements for LMARS. The 

LMARS tool is a database and collection of reports located at the DLA Transaction Services. 

LMARS provides a single, authoritative, enterprise-wide source of logistics pipeline 

performance and customer wait time data. Within the authority granted to it, in paragraph 4.3.1. 

below, the Pipeline Measurement (PM) Process Review Committee (PRC) is responsible for 

developing and maintaining LMARS to include the maintenance of this chapter.

C4.1.2. Purpose of LMARS. LMARS is a tool/database for the collection of logistics 

business event information that allows actual logistics pipeline performance to be measured and 

reported uniformly. The information enables management to track trends, identify areas 

requiring improvement, and compare actual performance against pre-established goals. It 

provides information that allows policy, procedural, and/or technology infusions to be assessed 

for their effects on pipeline performance. LMARS supports the measurement of logistics 

pipeline segment performance, to include Logistics Response Time (LRT), and will in the future, 

based on individual business event transactions, provide the ability to measure Customer Wait 

Time (CWT), and to compare actual performance against Time Definite Delivery (TDD) 

standards. The common denominator among the LRT, CWT, and TDD performance 

measurements is that they all begin with the submission of a customer order document number

and end with the receipt of the ordered materiel. The LMARS is comprised of a standard:

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. Business rules, decision tables, and algorithms applied to the standard 

event/transactions to populate database pipeline segment performance data.

C4.1.2.4. Database consisting of 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.
DOD 4000.25-M Volume VI, TBD

C4-3 Enclosure 1, CHAPTER 4.

C4.2. POLICY: It is DOD policy that all organizations in the supply chain recognize and 

emphasize the importance of time in accomplishing their respective functions. DOD materiel 

management shall be structured to be responsive to customer requirement during peacetime and 

war. Timely receipt of items ordered by customers of the logistics system contributes to 

increased customer confidence in that system. All organizations in the supply chain must 

accomplish their respective functions in an efficient and cost-effective manner. The DOD 

4140.1-R, “DOD Supply Chain Materiel Management Regulation” is the principal supply chain 

policy document that lays the foundation for paragraphs C4.2.1, C4.2.2., and C.4.2.3.

C4.2.1. Logistics Response Time (LRT). To gauge logistic system timeliness, the 

performance data collection system, LMARS, is established as the single, authoritative, 

enterprise-wide source for performance reporting and analysis of LRT.

C4.2.2. Customer Wait Time (CWT)

C.4.2.2.1. Components shall develop methods of including retail transactions at 

the lowest level (e.g., immediate issues of materiel from installation or shipboard supply 

activities, Government purchase card acquisitions, etc.) with wholesale logistics response time 

measurement in order to produce a customer wait time performance measure.

C.4.2.2.2. Components shall use the CWT measurement to assess past 

performance and apply lessons learned to improve future performance of the DOD supply chain.

C.4.2.2.3. Components shall submit monthly reports to DLA Transaction Services 

covering completed orders originating from organizational maintenance activities. The reports 

shall be prepared in accordance with reporting requirement instructions specified in Enclosure 1 

of DOD Instruction 4140.61. DLA Transaction Services shall compile the Component data and 

fill out the DD Form 2829 for posting to the LMARS Web site.

C4.2.3. Time Definite Delivery (TDD)

C.4.2.3.1. The purpose of establishing time definite delivery (TDD) standards is 

based on the concept that, within a specified degree of probability (e.g., 95 percent), the logistics 

system is capable of delivering required materiel to the customer within a given period of time 

depending on the priority and geographic location of the customer.

C.4.2.3.2. United States Transportation Command (USTRANSCOM) negotiates 

and maintains the TDD standards. In the absence of specific customer time definite delivery 

(TDD) standards, the legacy aggregate standards in the DOD 4140.1-R, DOD Supply Chain 

Materiel Management Regulation, prevail. In developing organic or contractor performance 

agreements with their customers, materiel managers and distribution and transportation managers 

should develop specific customer TDD standards that are tailored to meet specific delivery 

requirements:
DOD 4000.25-M Volume VI, TBD

C4-4 Enclosure 1, CHAPTER 4.

C.4.2.3.2.1. TDD standards address the supply of materiel from the time 

of origination of the requirement (date of the requisition) to the time that the requisitioner 

acknowledges physical receipt. The major segments of the total logistics pipeline are requisition 

submission time, inventory control point (ICP) processing time, storage depot segment time, 

transportation segment time, and theater segment time.

C.4.2.3.2.2. Each logistics pipeline segment involved in the processing of 

a requisition has been assigned a portion of the total time available. Individual segment standards 

should not be considered inviolate if exceeding those standards results in savings in time and 

improved service for the total pipeline.

C.4.2.3.2.3. Timely receipt of items ordered by customers of the logistics 

system contributes to increased customer confidence in that system. All organizations in the 

supply chain must accomplish their respective functions in an efficient and cost-effective 

manner. 

C.4.2.3.2.4. The LMARS database is intended to be the primary source of 

logistics response time data for comparison against the TDD standards. 

C4.3. ROLES AND AUTHORITIES: 

C4.3.1 Pipeline Measurement (PM) Process Review Committee (PRC) The PM PRC is 

responsible for developing and maintaining the LMARS for the capture and recording of 

logistics pipeline business events from business transactions. LMARS provides a reliable and 

consistent database of information from which the measurement of logistics pipeline segment 

performance metrics such as Logistics Response Time (LRT) and Customer Wait Time (CWT)

may be generated. The LMARS data recording of actual performance times can be compared to 

the Time Definite Delivery (TDD) standards. The PM PRC operates under the authority and 

within the framework documented below. 

C4.3.2. Office of the Deputy Assistant Secretary of Defense Supply Chain Integration 

(DASD/SCI) shall:

C4.3.2.1. Serve as the Office of Secretary of Defense (OSD) sponsor of the PM 

program, issuing policy guidance and instructions for development, expansion, improvement and 

maintenance of the LMARS.

C4.3.2.2. Review and approve PM program plans, priorities, schedules and goals. 

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 

PM program objectives.
DOD 4000.25-M Volume VI, TBD

C4-5 Enclosure 1, CHAPTER 4.

C4.3.2.4. Ensure applicable coordination within OSD staff elements that are 

responsible for PM 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), the DASD/SCI representative, and accept updates after each meeting or as 

appropriate. 

C4.3.2.7. Ensure that DOD senior leaders are advised of initiatives and plans as 

they are developed with respect to PM performance data integrity and management.

C4.3.2.8. Monitor the activity of the PRC to ensure compliance with policy, 

instructions and standards.

C4.3.3. DLA Logistics Management Standards, as the Chair of the PM PRC, shall:

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

but at least semi-annually. Announce meetings 30 calendar days in advance. Submit minutes of 

each PM meeting within 7 to 14 calendar days of meeting completion to the PM PRC 

membership and the OSD PSA, for review. Publish final meeting minutes within 30 calendar 

days of meeting completion. Maintain a current list of representatives to the PM PRC.

C4.3.3.2. Submit proposed recommendations for LMARS improvement to the 

committee members and the OSD PSA. Present issues to the PM PRC for review and resolution. 

Document and present issues to the OSD PSA for resolution, on issues where PRC consensus 

cannot be obtained.

C4.3.3.3. Document the PM program objectives and business rules in DOD 

4000.25-M.

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 DLA Transaction Services 

to develop and execute the tool set for the measurement of LRT, CWT, and TDD actual 

performance.

C4.3.3.5. Develop and provide training on LMARS.

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).
DOD 4000.25-M Volume VI, TBD

C4-6 Enclosure 1, CHAPTER 4.

C4.3.3.7. Ensure that the PRC builds an extensible capability allowing for the

expansion of data to encompass PM performance measurement at both wholesale and retail 

logistics processes and functions.

C4.3.3.8. Ensure testing and validation of proposed changes to standard data 

elements for PM performance measurement.

C4.3.4. DLA Transaction Services shall:

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 by 

DLA Logistics Management Standards and approved by the PM PRC.

C4.3.4.4. Provide LMARS subject matter expertise to members of 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 PM performance measurement.

C4.3.5. DOD Components shall support the PM PRC providing qualified, experienced 

representatives who shall:

C4.3.5.1. Attend all PM meetings.

C4.3.5.2. Furnish 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, CWT, and TDD 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 timeframes specified.
DOD 4000.25-M Volume VI, TBD

C4-7 Enclosure 1, CHAPTER 4.

C4.3.5.7. Promote and support LMARS within their respective Components and 

serve as the Components subject matter expert for LMARS. 

C4.3.5.8. Use measurements to assess the pipeline performance of the DOD

Supply Chain and as a basis for process improvements. Conduct analysis and take appropriate 

actions within the Component to improve pipeline performance.

C4.3.5.9. Review Monthly LMARS outputs and data

C4.3.5.9.1. Review of monthly Reports analyzing and researching 

unusual trends. Significant changes need to be researched using the drill down capability to 

determine the anomaly causes. Researchers should look for conditions such as one or more 

activities doing mass close outs of open aged records not in a 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. The Anomaly Code list is available at the following 

link. http://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/Anomaly_Code_List.doc

 

C4.3.5.9.2. Data corrections that are required as a result of the above 

research and analysis will be identified to the PM PRC Chair and DLA Transaction Services. 

When warranted, the PM PRC chair will ensure prior coordination with the ODASD/SCI PM 

PRC representative before data corrections are made. The method for making the data 

corrections will be determined by DLA Transactions Services and coordinated with the PM PRC 

Chair.

C4.3.5.9.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) changes, Combatant Commander (COCOM) designations, etc.

C4.3.5.10. Submit required monthly CWT reports to the DLA Transaction 

Services in accordance with approved formats and instructions.

C4.3.5.11. Retain records of LRT, CWT, and TDD performance measurements 

for audit and oversight.

C4.4. CONFIGURATION MANAGEMENT

C4.4.1. PM PRC Administration. The PM PRC shall be responsible for:

C4.4.1.1. Coordinating actions essential to the maintenance and improvement of 

LMARS.

C4.4.1.2. Developing and maintaining uniform business rules for the 

measurement and reporting of LRT, CWT, and TDD in LMARS.
DOD 4000.25-M Volume VI, TBD

C4-8 Enclosure 1, CHAPTER 4.

C4.4.1.3. Serving as the primary group responsible for developing and executing 

LMARS and its associated products for the measurement of LRT, CWT, and TDD. 

C4.4.1.4. Ensuring senior leaders in the DOD Components are apprised of all 

initiatives and plans as they are developed with respect to LMARS.

C4.4.1.5. Documenting and maintaining DOD-level LRT, CWT and TDD 

calculation rules to support consistency of measurement across the Department of Defense 

within LMARS.

C4.4.1.6. Posting PM PRC Meeting minutes of each PM PRC meeting to DLA 

Logistics Management Standards website, along with a current list of representatives to the PM 

PRC.

C4.4.1.7. Providing feedback to the ODASD/SCI concerning Component 

requirements to fully implement LRT, CWT, and TDD measurement tools.

C4.4.2. Proposed DLMS Change (PDC)/Approved DLMS Change Process (ADC).

The requirements and guidelines for change management are documented in Volume 1, Chapter 

5 (DLMS Change Management) of DOD 4000.25-M. The change control process ensures the 

proper documentation of all proposed or approved changes and the tracing and reporting of these 

changes to the functional baseline using change control status accounting, and the validation of 

the changes using functional change control reviews, as required. Below is the link to Chapter 5 

DLMS Change Management:http://www.dla.mil/j6/dlmso/elibrary/manuals/dlms/msw/v1/v1c5_chg5.doc

A subset of the DLMS change process is the preparation of the Proposed DLMS Change (PDC). 

The PDC is an audit trail for PM. Changes to PM are required to be submitted using the process 

located in Volume 1, Appendix 1 of DOD 4000.25-M:

http://www.dla.mil/j-6/dlmso/elibrary/manuals/dlms/msw/v1/v1a1_ch3.doc

The process flow of how the PDC process works is defined in Appendix 2 of DOD 4000.25-M:

http://www.dla.mil/j-6/dlmso/elibrary/manuals/dlms/msw/v1/v1a2.doc

C4.4.3. DLA Transaction Services Technical Documentation.

C4.4.3.1. Develop and provide training on LMARS.

C4.4.3.2. 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).
DOD 4000.25-M Volume VI, TBD

C4-9 Enclosure 1, CHAPTER 4.

C4.4.3.3. Ensure that the PRC builds an extensible capability allowing for the 

expansion of data to encompass PM performance measurement at both wholesale and retail 

logistics processes and functions.

C4.4.3.4. Ensure testing and validation of proposed changes to standard data 

elements for PM performance measurement.

C4.5. LMARS ARCHITECTURE. 

C.4.5.1 Functional Architecture.

C4.5.1.1. LMARS is based on the capture by DLA Transaction Services of the 

business events at the individual transaction level for each individual customer order/Document 

Number.

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 recorded for the completion of each document are the key data captured and used 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. Later actions within 

the pipeline are reported in the month that segment is completed. No segment, with the 

exception of the ICP segment (ISPT), is reported again for that document number in any 

succeeding months. A Material 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, 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 DLA Transaction Services.

 

C.4.5.2 Technical Transaction Architecture. LMARS is based on legacy Military 

Standard Requisitioning and Issue Procedures (MILSTRIP) and Military Standard Transaction 

Reporting and Accountability Procedures (MILSTRAP) transactions formats with some data 

extensions of the base legacy documents. Incoming DLMS based transactions are converted to 

legacy transaction formats using the DLA Transaction Services standard DLMS to legacy 

MILSTRIP/MILSTRAP maps. 
DOD 4000.25-M Volume VI, TBD

C4-10 Enclosure 1, CHAPTER 4.

C4.6. LMARS CONTENT.

C4.6.1. Inputs. The Data sources used to fill the LMARS database and prepare the monthly 

reports are as follows:

C4.6.1.1. DLA Transaction Services Routed DLSS/DLMS Transactions. The 

DLMS X12 Electronic Data Interchange (EDI) and DLMS eXtensible Markup Language (XML)

transactions are first converted to DLSS transactions (legacy MILSTRIP/MILSTRAP) and 

merged with standard legacy DLSS transactions. The DLMS transactions, when converted to 

DLSS, include extended data not available in the equivalent DLSS transaction as originated by 

the source system. There are also some Service Unique DLSS-like transactions that are not 

DLSS standard transactions but are standard within a Component such as the Air Force 

document identifier code BF7.

C4.6.1.2. DLA Transaction Services Non-routed Transactions. These are 

Component unique document identifier codes (DLSS-like) transactions used to report offline 

actions by the Services, DLA, and GSA. These transaction document identifier codes are B99, 

BE9, D7, CHA, CH1 CO_, and CQ. Integrated Data Environment (IDE) and Global 

Transportation Network (GTN) Convergence (IGC) User Defined Format (UDF) data feeds 

provide information to both open and close the transportation pipelines segments. 

 

C4.6.1.3. DLA Troop Support Special Prime Vendor Data Feeds. Special data 

feeds are received for Fresh Fruits and Vegetable (FFV), Semi Perishables, Maintenance Repair 

Operations (MRO), and Prime Vendor Medical (PVM). 

C4.6.1.4. EDI 850 transaction is used in place of Other S9G material release orders 

(MROs) if the EDI 850 has an earlier date.

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 DLA Logistics Information Service. 

Additionally the following data sources are used and require validation and update by the 

Components.

C4.6.1.5.1. CoCOM DODAACs– Report not presently produced

C4.6.1.5.2. DLA Demand Chain DODAACs – DLA Operations 

Research 

C4.6.1.5.3. DLA Supply Chain – DLA Logistics Information Service 

(NIIN) and DLA Operations Research (Part Number)

C4.6.1.5.4. Guard or Reserve DODAACs– Marines and Army

C4.6.1.5.5. Reparable/Non Reparable indicator – all Services
DOD 4000.25-M Volume VI, TBD

C4-11 Enclosure 1, CHAPTER 4.

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 it was received by DLA 

Transaction Services. 

 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 ends when the requisition is returned and released to a Wholesale Inventory Control 

Point.

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

Time” measures the time from DAAS release of a requisition to an ICP, until DAAS receipt of a 

material release order (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 (CCP) Processing Time” is measured from the date shipped/released to 

the CCP, to the date received by the CCP.

C4.6.2.6. Logistics Pipeline Segment 6, “CCP Processing Time” is measured from 

the CCP’s date of receipt until the date of release.

 C4.6.2.7. Logistics Pipeline Segment 7, “CONUS In-Transit Time” measurement 

starts with date shipped by the shipper (may be contractor, storage depot, or CCP and ends on the 

date received by a CONUS customer or POE for overseas movements. 

C4.6.2.8. Logistics Pipeline Segment 8, “POE Processing” is measured from the 

date of POE receipt to the date of POE release.

C4.6.2.9. Logistics Pipeline Segment 9, “POE to Port of Debarkation (POD) 

Intransit Time” is measured from POE date of release to POD date of receipt.

C4.6.2.10. Logistics Pipeline Segment 10, “POD Processing” is measured from the 

date of POD receipt to date of 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 
DOD 4000.25-M Volume VI, TBD

C4-12 Enclosure 1, CHAPTER 4.

between consignee receipt or “tailgate” date and the record posting date in the DRA, DRB, or 

D6S.

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, the DLA 

Transaction Services’ procedures, and the output report specific data population rules and 

display.

C4.6.3.1 Key Tables.

C4.6.3.1.1. LMARS Fill Type Table. The LMARS Fill Type Table can 

be found at the following link. 

http://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/Type_of_Fill_Table.xlsx

This table is used to determine the applicable reports in which each document number, 

completing a pipeline segment within the report month, is included in. Each of the reports is 

discussed in detail in paragraph C4.6.5. below. The usage and detailed procedures for the 

LMARS Fill Type Table are available at the following link.

http://www.dla.mil/j6/dlmso/Archives/PMPRC/documents/LMARS_FILL_Rules_Procedures.docx

Examination of the data in the transaction against the values in Columns “A” through “H” of the 

LMARS Fill Table yields one of the Fill Types below (which equate to Column “I”) of the 

LMARS Fill Table. The derived Fill Type is inserted into the LMARS database date element 

“CORP-FILL-TYPE” for that transaction document number. The Fill Types and the Reports 

that a Fill Type is applicable to are identified below.

LMARS Records Fill Types

A = Immediate shipment from depot

B = Planned DVD Shipments

C = Backordered

D = Unplanned DVD Shipments

O = Other

LMARS Reports Applicable Fill Type Codes

Total Fill Types = A, B, C, D, O 

Immediate Fill Types = A

Planned DVD Fill Type = B

Backorder Fill Type = C

Unplanned DVD Fill Type D

 Other Fill Type O
DOD 4000.25-M Volume VI, TBD

C4-13 Enclosure 1, CHAPTER 4.

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. These 

tables are provided at the link below:

https://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/KeyLMARSTables.docx

C4.6.3.1.3. DLA Special Report Fill Type Table. LMARS provides a 

series of reports that are tailored for DLA management usage. While these DLA specific reports 

are not discussed in this chapter, the report fill rules are identified within the DLA Corporate Fill 

Table found at the link below: 

http://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/DLA_Corp_fill_rules.doc

C4.6.4 DLA Transaction Services’ Procedures.

C4.6.4.1. Daily Continuous Processing. Transactions, except special data feeds, 

are received at DLA Transaction Services continually, copied and parsed to the Logistics On-line 

Tracking System (LOTS) database.

C4.6.4.2. Weekly Processing. Every Friday at midnight DLA Transaction 

Services performs the following processing procedure in preparation for the monthly processing.

C.4.6.4.2.1. LOTS database is copied and integrated with the LMARS 

Master file.

C.4.6.4.2.2. A Temporary Master file is created for that month’s 

reporting.

C.4.6.4.2.3. LMARS business rules are applied to the temporary 

LMARS Master file.

C.4.6.4.2.4. LMARS flat file is produced and put on guest server for 

SFTP.

C.4.6.4.2.5. Flat files tailored to each Service/Agency are created.

C.4.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 and integrated with the LMARS 

Master file. 

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.
DOD 4000.25-M Volume VI, TBD

C4-14 Enclosure 1, CHAPTER 4.

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 DLA Transaction Services processing errors and to 

identify anomalies and unusual trends that the Services need to research and verify. The DLA 

Transaction Services 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 if the data is valid. The Services with anomalies and/or 

unusual tends have five days to respond. Based on their response and the PM PRC chair 

authorization, identified invalid data is 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 

for a minimum of 3 years. 

C4.6.4.5. User Accounts. User account must be obtained from DLA Transaction 

Services. The instructions for obtaining a user account are found on the DLA Transaction 

Services web site at https://www.transactionservices.dla.mil/daashome/homepage.asp. Click on 

“Request Login ID and Password” and follow the screens for completing the On-Line Systems 

Access Request.

C4.6.4.5.1. The Logistics Metrics Analysis Reporting 

System/Customer Wait Time (LMARS/CWT) at Transaction Services maintains logistics 

pipeline information for all wholesale items. LMARS/CWT is populated with information from 

the MILSTRIP and MILSTRAP transactions that flow through Transaction Services. 

LMARS/CWT reports response time within the 12 segments of the logistics pipeline. All 

reporting time frames are in terms of days. Current Standard reports are available via the web on

a monthly basis.

C4.6.4.5.2. To access LMARS and CWT Reports a user must acquire 

an access account from DLA Transaction Services. Users must submit a System Access Request 

(SAR). It is important to note that once a user has obtained access approval for LMARS, they 

must keep the account active by logging into LMARS at least once every 30 days or the account 

will be inactivated.

C4.6.4.5.3. Data download capabilities. DLA Transaction Services can 

provide data downloads in a variety of forms. The monthly reports themselves provide a link at 

the top that allow the report to be directly downloaded by the user to a Microsoft Excel 

Spreadsheet. For other database transfers/downloads of LMARS data and/or tables the requester 
DOD 4000.25-M Volume VI, TBD

C4-15 Enclosure 1, CHAPTER 4.

should contact the Service/Agency PM PRC point of contact, or if not known, DLA Transaction 

Services. Database transfers/downloads of LMARS data, for a specific Service or Agency, are 

done by that Service or Agency. 

C4.6.4.6. Handling of Corrections. Both the Components and DLA Transaction 

Services review the initial runs of each months reports reviewing, analyzing, and researching 

unusual trends. Significant changes need to be researched using the drill down capability to 

determine the cause. Researchers should look for conditions such as one or more activities doing 

mass close outs of open aged records, not in a 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. The Anomaly Code list is available at the following link. 

http://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/Anomaly_Code_List.doc

Data corrections that are required as a result of the above research and analysis will be identified 

to the PM PRC Chair and DLA Transaction Services. When warranted, the PM PRC chair will 

ensure prior coordination with the ODASD/SCI PM PRC representative before data corrections 

are made. The method for making the data corrections will be determined by DLA Transactions 

Services and coordinated with the PM PRC Chair by the Component that identified the problem.

C4.6.5. Output Reports. - All output reports are displayed in a standard format. The 

following sub-paragraphs of this section describe the format and content of standard monthly 

reports for the selected month; if no month is selected LMARS defaults to the most recent month 

available. Paragraphs C4.6.5.1, C4.6.5.2, and C4.6.5.3 below describe the Major Report 

Categories, the Sections and Sub-sections within them. The titles of the Major Report 

Categories, the Sections and Sub-sections are all centered on the report pages. Paragraph 

C4.6.5.4 below defines the meanings of the heading titles in the far left column of the reports and 

paragraph C4.6.5.5 defines the Column headings and data content across the top of the reports. 

A sample output report showing the format is available at the following link 

http://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/WhollesaleReguistionPipeline.xls

and the LMARS database data dictionary is available at the following link. http://www.dla.mil/j6/dlmso/Archives/PMPRC/documents/Record_Layout.doc . The data value names and location 

on the LMARS master data record is available at the following link

http://www.dla.mil/j-6/dlmso/Archives/PMPRC/documents/Data_values.doc This database is the 

authoritative source from which all LMARS output reports are produced. It is also the 

authoritative source of all files that are made available to the Components for their individual 

purposes. Foreign Military Sales documents and Initial Outfitting documents are excluded from 

all LMARS reporting.

 

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: 

C.4.6.5.1.1. “COMPOSITE” Report. The Composite Report includes all 

document numbers eligible for LMARS reporting in a given month with the exception of those 

for Guard, Reserve, or Contractor DODAACs. 
DOD 4000.25-M Volume VI, TBD

C4-16 Enclosure 1, CHAPTER 4.

C4.6.5.1.2 “MAJOR COMMAND” Report. The Major Command 

Report includes a subset of the document numbers in the Composite Report. To be included in 

the Major Command report the document number’s Ship-To address or Consignee must be 

identified as being in that specific Major Command. Note: Major Command Report is not 

presently produced pending Major Command Code table update; therefore the “Major 

Command” report category is not currently on the main LMARS page as a Major Report 

Category that can be selected.

C4.6.5.1.3. “REPAIRABLE NIIN” Report. The Reparable NIIN Report 

includes a subset of the document numbers in the Composite Report. To be included in the 

Reparable NIIN report the NIIN being ordered on a given document number must be identified 

as a Reparable NIIN by at least one service.

C4.6.5.1.4. “GUARD” Report. To be included in the Guard Reports, the 

document number’s Ship-To address or Consignee must be an identified Guard DODAAC. Note 

that the document numbers included in the Guard Report are not included in the Composite 

Report, paragraph C6.5.1.1 above. DLA Transaction Services maintains an internal table of 

DODAACs supplied by the Components that identifies Guard unit DODAACs.

C4.6.5.1.5. “RESERVE” Report. To be included in the Reserve Reports 

the document number’s Ship-To address or Consignee must be an identified Reserve DODAAC. 

Note that the document numbers included in the Reserve Report are not included in the 

Composite Report, paragraph C4.6.5.1.1 above. DLA Transaction Services maintains an internal 

table of DODAACs supplied by the Components that identifies Reserve unit DODAACs.

C4.6.5.1.6. “CONTRACTOR” Report. To be included in the Contractor 

Reports the document number’s Ship-To or Consignee address must be an identified Contractor 

DODAAC. Note that the document numbers included in the Contractor Report are not included 

in the Composite Report, paragraph C4.6.5.1.1 above. Contractor DODAACs are identified 

according to Table H.

 

C4.6.5.2. Major Report Category Sections. Each Major Report Category is 

composed of Sections and each Section has a total line totaling all the data for that section prior 

to beginning a new Section. The Sections are identified by Tabs at the bottom of the report. 

The titles of the Tabs and section headings are (1) “TOTAL”, (2) “ARMY”, (3) “AIR FORCE”, 

(4) “NAVY”, (5) “MARINE CORPS”, (6) “COAST GUARD” and (7) “OTHER”.

C4.6.5.3. Fill Type Sub-Sections. Each of the above Major Report Sections is 

further sub-divided into six Fill Type Sub-Sections. Each Sub-Section has a total line. The Fill 

Types Sub-Sections record document numbers according to how that document number is being 

satisfied. The LMARS Fill Type Table discussed in paragraph C4.6.3.1.1. is a key table used to 

produce the LMARS output reports. Paragraph C4.6.3.1.1. describes the Fill Type Table

composition, its usage, the mapping of the Fill Types to the LMARS Fill Type Report SubSections, and the web link to the current LMARS Fill Type Table. The Fill Types Sub-Sections 
DOD 4000.25-M Volume VI, TBD

C4-17 Enclosure 1, CHAPTER 4.

titles and descriptions are below:

C4.6.5.3.1. “TOTAL” Fill Type Sub-Section. The “TOTAL” Fill Type 

Sub-Sections reflect Wholesale requisition pipeline activity of the cumulative document 

numbers of each of the Report Sections identified in paragraph C4.6.5.2 above (TOTAL, 

ARMY, AIR FORCE, NAVY, MARINE CORPS, COAST GUARD, and OTHER (any 

document that is not identified to one of the foregoing, such as Federal and Civil Agencies)). 

The Reporting starts when a shipment is indicated by a shipment transaction or receipt 

transaction. This Sub-section contains all the document numbers within the Major Report 

Category and Section that contain Fill Types that = A, B, C, D, O. 

C4.6.5.3.2. “IMMEDIATE” Fill Type Sub-Section. The “IMMEDIATE” 

Fill Type Sub-Sections reflect Wholesale requisition pipeline activity of immediate issues for 

each of the Report Sections identified in paragraph C4.6.5.2 above (TOTAL, ARMY, AIR 

FORCE, NAVY, MARINE CORPS, COAST GUARD, and OTHER (any document that is not 

identified to one of the foregoing, such as Federal and Civil Agencies)). 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. The Reporting starts when a shipment is indicated by a 

shipment, transaction or receipt transaction. This Sub-section contains all the document 

numbers within the Major Report Category and Section that contain Fill Type that = A.

C4.6.5.3.3. “PLANNED” Fill Type Sub-Section. The “PLANNED” Fill 

Type Sub-Sections reflect Wholesale requisition pipeline activity of Planned Direct Vendor 

Deliveries (DVD) issues for each of the Report Sections identified in paragraph C4.6.5.2 above 

(TOTAL, ARMY, AIR FORCE, NAVY, MARINE CORPS, COAST GUARD, and OTHER 

(any document that is not identified to one of the foregoing, such as Federal and Civil 

Agencies)).The servicing Inventory Control Point’s (ICP) criteria (Table B) must be met to 

qualify as a planned DVD. The reporting starts when a shipment is indicated by a shipment, 

transportation or receipt transaction. To be included in the PLANNED Sub-Section (Planned 

Direct Vendor Deliver (DVD)), the document number must meet the criteria for Planned DVD 

in the LMARS Type of Fill Table. This Sub-section contains all the document numbers within 

the Major Report Category and Section that contain Fill Type that = B. 

C4.6.5.3.4. “BACKORDERED” Fill Type Sub-Section. The 

“BACKORDERED” Fill Type Sub-Sections reflect 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 above (TOTAL, ARMY, AIR FORCE, NAVY, MARINE 

CORPS, COAST GUARD, and OTHER (any document that is not identified to one of the 

foregoing, such as Federal and Civil Agencies)). The following criteria must be met to qualify 

as a backorder: (1) Any Supply Status (AE transaction) received, prior to shipment, must have a 

BB, BC or a Service specified (Table A) backorder code. (2) Direct Vendor Delivery, whether 

planned or unplanned, was not indicated prior to shipment. To be included in the 

“BACKORDERED” Sub-section the document number must meet the criteria for backordered 
DOD 4000.25-M Volume VI, TBD

C4-18 Enclosure 1, CHAPTER 4.

documents in the LMARS Type of Fill Table, having a Fill Type that = C.

C4.6.5.3.5. “UNPLANNED” Fill Type Sub-Section. The 

“UNPLANNED” Fill Type Sub-Sections reflect Wholesale requisition pipeline activity of 

unplanned Direct Vendor Deliveries (DVD) issues for each of the Report Sections identified in 

paragraph C4.6.5.2 above (TOTAL, ARMY, AIR FORCE, NAVY, MARINE CORPS, COAST 

GUARD, and OTHER (any document that is not identified to one of the foregoing, such as 

Federal and Civil Agencies)). The servicing Inventory Control Point’s (ICP) criteria (Table A) 

must be met to qualify as an unplanned DVD. The reporting starts when a shipment is indicated 

by a shipment, transportation, or receipt transaction. This Sub-section contains all the document 

numbers within the Major Report Category and Section that contain Fill Type that = D. 

C4.6.5.3.6. “OTHER” Fill Type Sub-Section. The “OTHER” Fill Type 

Sub-Sections reflect Wholesale requisition pipeline activity of document numbers and/or its 

related data that did not meet the criteria for Immediate Issue, Backorder, Planned or Unplanned 

Direct Vendor Delivery for each of the Report Sections identified in paragraph C4.6.5.2 above 

(TOTAL, ARMY, AIR FORCE, NAVY, MARINE CORPS, COAST GUARD, and OTHER 

(any document that is not identified to one of the foregoing, such as Federal and Civil 

Agencies)). All reporting starts when shipment is indicated by a shipment, transportation, or 

receipt transaction. This Sub-section contains all the document numbers within the Major 

Report Category and Section that contain Fill Types that = O. 

C4.6.5.4. 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 

PROC GP1, PROC GP2, and PROC GP3 and the TOTAL/AVERAGE line applicable to each 

pipeline segment and a grand “TOTAL” line at the bottom.

C4.6.5.4.1. Delivery Area row headings. The five delivery area 

headings are CONUS, OCONUS1, OCONUS2, OCONUS3, and OCONUS4. The delivery area 

a document number is reported within is based on an internal DLA Transaction Services table. 

DLA Transaction Services researches all new DODAACs as they are established and determines 

the appropriate delivery area. The LMARS Delivery Areas are consistent with the TDD Areas 

identified in DOD 4140.1-R, Appendix 8, paragraph AP8.2., found at link 

http://www.dtic.mil/whs/directives/corres/pdf/414001r.pdf. The LMARS Delivery areas map to 

the TDD Areas as follows.

LMARS Area TDD Areas

CONUS 48 Contiguous States

OCONUS1 Area A

OCONUS2 Area B

OCONUS3 Area C

OCONUS4 Area D

It should be noted that LMARS makes no distinctions between Airlift and Sealift delivery areas. 
DOD 4000.25-M Volume VI, TBD

C4-19 Enclosure 1, CHAPTER 4.

C4.6.5.4.2. Issue Processing Group row labels. Each Delivery area is 

further broken out into the three Issue Processing Groups (PROC GP1, PROC GP2, and PROC 

GP3) and the Total/ Average line applicable to each pipeline segment within and a grand 

“TOTAL” line at the bottom. Standard UMMIPS Priority Designator and IPG groupings apply. 

The Group Priority (GP) 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. The PROC GP1, PROC GP2, and PROC GP3 designations 

correlate directly with IPG I, IPG II, and IPG III described in DOD 4000.25-M, Chapter 4, 

paragraph C4.2.1.2.9. found at link 

http://www2.dla.mil/j6/dlmso/elibrary/manuals/dlms/pdf/DLMS_all.pdf . IPGs are groupings of 

Issue Priority Designators (IPDs) as below:

PDs 01, 02, and 03 form IPG I

PDs 04, 05, 06, 07, and 08 form IPG II

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

C4.6.5.5. Column/Pipeline Segment Heading and Data Descriptions. The 

following paragraphs define the pipeline segment headings and data content that appears under 

that heading for a particular row heading. Where applicable, DLSS Document Identifier Codes 

(e.g., A5_, AS_, and DRA) 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 their curser over the data value and clicks the value, the 

document numbers and their associated data will be presented. 

C4.6.5.5.1. Spreadsheet Report Columns B and C

• Logistics Pipeline Segment 1 – “Requisition Submission Time”

• Report Spreadsheet Heading “1 – “REQN SUBMIT”

• LMARS database name “RST-NODE”

• Columns B and C reflect the months 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 (CH1, 

CHA, BE9, and 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.
DOD 4000.25-M Volume VI, TBD

C4-20 Enclosure 1, CHAPTER 4.

C4.6.5.5.2. Spreadsheet Report Columns D & E

• Logistics Pipeline Segment 2, “Internal Service Processing Time”

• Report Spreadsheet Heading “2 – SERVICE PROCESS”

• LMARS database name “SPT-NODE”

• An example of Internal Service Processing is the processing by Navy FISCs. 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 

Inventory Control Point (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.5.3. Spreadsheet Report Columns F and G

• Logistics Pipeline Segment 3, “Inventory Control Point (ICP) Processing Time”)

• 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 a Materiel 

Release Order (MRO), A5_ transaction, a Table E listed equivalent, an AB_ (Direct Delivery 

Notice) transaction, or an 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.5.4. Spreadsheet Report Columns H and I

• Logistics Pipeline Segment 4, “Storage Activity Processing Time”

• Report Spreadsheet Heading “4 – STORAGE ACTIVITY”

• LMARS database name ‘SAPT-NODE”

• The time is measured from DAAS’ receipt of a defined MRO to the date 

shipped/released in an AS_/AU_ (Shipment Status) transaction. When Shipment Status is not 
DOD 4000.25-M Volume VI, TBD

C4-21 Enclosure 1, CHAPTER 4.

available, the date in a Materiel Release Confirmation (MRC), AR transaction, is used to close 

the segment. In the case of Direct Vendor Deliveries (DVDs), time is measured from DAAS’ 

receipt of an AB_ transaction, or AE_ transaction with BV status, to the date shipped/released in 

an AS_/AU_ or AR_ transaction. The number of shipments and average processing times are 

shown in Columns H and I respectively, similar to previous segments.

C4.6.5.5.5. Spreadsheet Report Columns J and K

• Logistics Pipeline Segment 5, “Storage Activity to Consolidation 

Containerization Point (CCP) Processing Time”

• 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: For CONUS Area reporting where the source of material is in the 

CONUS and the Customer delivery point is in the CONUS, these columns will be blank, 

since CONUS shipments don’t move through Consolidation Containerization Points, Ports 

of Embarkation or Ports of Debarkation.

C4.6.5.5.6. Spreadsheet Report Columns L and M

• Logistics Pipeline Segment 6, “CCP Processing Time”

• 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: For CONUS Area reporting where the source of material is in 

the CONUS and the Customer delivery point is in the CONUS, these columns will be blank, 

since CONUS shipments don’t move through Consolidation Containerization Points, Ports 

of Embarkation or Ports of Debarkation.

C4.6.5.5.7. Spreadsheet Report Columns N and O

• Logistics Pipeline Segment 7, “CONUS In-Transit Time”

• Report Spreadsheet Heading “CONUS IN-TRANSIT”
DOD 4000.25-M Volume VI, TBD

C4-22 Enclosure 1, CHAPTER 4.

• 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 be dependent upon 

whether or not 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 - OCONUS shipments moving through a CCP, time is measured 

from the CCP’s release to the Port of Embarkation’s (POE) 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. NOTE: For CONUS Area reporting where the 

source of material is in the CONUS and the Customer delivery point is in the CONUS, these 

columns will be blank, since CONUS shipments don’t move through Consolidation 

Containerization Points, Ports of Embarkation or Ports of Debarkation.

• 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 DRA, DRB, or D6S 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). Times and the number of shipments to a CONUS 

consignee or POE are shown. 

C4.6.5.5.8. Spreadsheet Report Columns P and Q

• Logistics Pipeline Segment 8, “POE Processing”

• Report Spreadsheet Heading “8 – POE ACTIVITY”

• LMARS database name “POET-NODE”

• POE receipt and release dates, provided by GTN or other intransit data 

transactions, are used to calculate OCONUS times. The average times and number of shipments 

processed by a POE will be shown. NOTE: For CONUS Area reporting where the source of 

material is in the CONUS and the Customer delivery point is in the CONUS, these columns 

will be blank, since CONUS shipments don’t move through Consolidation Containerization 

Points, Ports of Embarkation or Ports of Debarkation.

C4.6.5.5.9. Spreadsheet Report Columns R and S
DOD 4000.25-M Volume VI, TBD

C4-23 Enclosure 1, CHAPTER 4.

• Logistics Pipeline Segment 9, “POE to Port of Debarkation (POD) Intransit 

Time”

• Report Spreadsheet Heading “9 - POE to 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 intransit data transactions, if available, 

may also be used. Times and numbers for these columns are shown similar to the previous 

segments. NOTE: For CONUS Area reporting where the source of material is in the 

CONUS and the Customer delivery point is in the CONUS, these columns will be blank, 

since CONUS shipments don’t move through Consolidation Containerization Points, Ports 

of Embarkation or Ports of Debarkation.

C4.6.5.5.10. Spreadsheet Report Columns T and U

• Logistics Pipeline Segment 10, “POD Processing”

• 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: For CONUS Area reporting 

where the source of material is in the CONUS and the Customer delivery point is in the 

CONUS, these columns will be blank, since CONUS shipments don’t move through 

Consolidation Containerization Points, Ports of Embarkation or Ports of Debarkation.

C4.6.5.5.11. Spreadsheet Report Columns V and W

• Logistics Pipeline Segment 11, “In-Theater In-transit Time”

• 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: A DRA, DRB, or D6S 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 
DOD 4000.25-M Volume VI, TBD

C4-24 Enclosure 1, CHAPTER 4.

receipt, will be included in this segment. Average times and the number of In-Theater shipments 

are shown. 

C4.6.5.5.12. Spreadsheet Report Columns X and Y

• Logistics Pipeline Segment 12, “Receipt Take-Up Time”

• 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 DRA, DRB, or 

D6S. Quantity and Discrepancy Code fields in the DRA and 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.5.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 documents 

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), Perishable and Semi-Perishable orders. See Table G for their computation 

logic.

C4.6.5.5.14. Spreadsheet Report Columns Z and AA –

The very last two columns also show Total Order-Receipt but with the document numbers with 

the highest 5 percent in terms of longest times, in each area’s IPG, eliminated. The objective of 

these columns is to remove the top 5%, the outliers, and present counts and average times with 

the extremes removed. Note: These columnar calculations are not performed for the GUARD, 

RESERVE, and CONTRACTOR Major Reports. 
1 Enclosure 2

Enclosure 2, RESPONSE/COMMENTS RESOLUTION:

Organization Response/Comment Disposition

Air Force Concurs with comments. See table below for

disposition of comments.

USTRANSCOM Concur with comments. Three 

changes were provided in the 

document as track changes.

All changes accepted.

Detailed Air Force Comment Table:

1 C4-3 C.4.2.2.2 S Coordinator Comment: missing “to” in 

between learned and improve

Coordinator Justification: add missing word

Accepted

2 C4-3 C.4.2.2.3 S Coordinator Comment: “Data is not 

submitted on the DD Form 2829; CWT uses 

the data to fill out the DD Form 2829.” 

Coordinator Justification: What does CWT 

imply in this sentence? Sentence is confusing.

Accepted. Reworded to show 

DLA Transaction Services 

preparing the 2829 for posting 

to the LMARS Web site.

3 C4-4 C.4.3.1 S Coordinator Comment: “The LMARS data 

recording actual....” Add “of” between 

recording and actual

Coordinator Justification: add missing word

Accepted

4 C4-9 C.4.5.2 S Coordinator Comment: MILS stands for?

Coordinator Justification: Define MILS

Changed MILS to Legacy 

MILSTRIP/MILSTRAP

5 C4-10 C.4.6.1.1 S Coordinator Comment: EDI stands for?

Coordinator Justification: Define EDI

Spelled out acronym to 

Electronic Data Interchange

6 C4-10 C.4.6.1.1 S Coordinator Comment: XML stands for?

Coordinator Justification: Define XML

Spelled out acronym to 

eXtensible Markup Language

7 C4-10 C.4.6.1.2 S Coordinator Comment: IDE stands for?

Coordinator Justification: Define IDE

Spelled out acronym to 

Integrated Data Environment

8 C4-10 C.4.6.1.2 S Coordinator Comment: GTE stands for?

Coordinator Justification: Define GTE

Spelled out acronym to Global 

Transportation Network
2 Enclosure 2

9 C4-10 C.4.6.1.2 S Coordinator Comment: user defined format

Coordinator Justification: Capitalize first 

letter in each word

Fixed.

10 C4-13 C.4.6.4.2 S Coordinator Comment: Subsection is 

incorrectly numbered (C.6.4.2.1)

Coordinator Justification: Should start at 

C.4.6.4.2.1

Fixed.

11 C4-13 C.4.6.4.2 S Coordinator Comment: Missing punctuation 

Coordinator Justification: Insert a period at 

end of C.6.4.2.2

Fixed.

12 C4-13 C.4.6.4.2 S Coordinator Comment: Missing punctuation

Coordinator Justification: Insert a period at 

end of C.6.4.2.4

Fixed.

13 C4-13 C.4.6.4.2 S Coordinator Comment: Missing punctuation

Coordinator Justification: Insert a period at 

end of C.4.6.4.3.2

Fixed.

14 C4-15 C.4.6.5.1.1 S Coordinator Comment: “COMPOSITE”

Coordinator Justification: Remove underline

Fixed.

15 C4-2 C4.1.2 S Coordinator Comment: Common 

denominator among LRT, CWT and TDD 

performance measurements is that they all 

begin with the submissions of requisitions and 

end with the receipt of the ordered material is 

inaccurate.

Coordinator Justification: CWT 

measurement includes immediate fills at the 

retail level. Immediate fills do not begin with 

the submission of a requisition but a customer 

order document number.

Adjusted wording to address 

issue.

16 C4-17 C4.6.5.3.3 S Coordinator Comment: Need further 

explanation of how Planned orders are defined 

in the data set

Coordinator Justification: Need clarification

Paragraph C4.6.3.1.1 modified 

to provide additional clarity 

regarding the Rill Type Table 

composition, its usage, the 

mapping of the Fill Types to the 

LMARS Fill Type Report SubSections, and the web link to 

the current LMARS Fill Type 

Table.
3 Enclosure 2

17 C4-17 C4.6.5.3.5 S Coordinator Comment: Need further 

explanation of how un-planned orders are 

defined in the data set

Coordinator Justification: Need clarification

Paragraph C4.6.3.1.1 modified 

to provide additional clarity 

regarding the Rill Type Table 

composition, its usage, the 

mapping of the Fill Types to the 

LMARS Fill Type Report SubSections, and the web link to 

the current LMARS Fill Type 

Table.

18 C4-18 C4.6.5.4 S Coordinator Comment: Futher define 

OCONUS 1, 2, 3, 4 as specific locations or 

theater

Coordinator Justification: Need clarification

Added based on DOD 4140.1-

R, Appendix 8 language.

19 C4-18 C4.6.5.4.2 S Coordinator Comment: How does the supply 

priorities (01-15) allign with the three different 

IPG.

Coordinator Justification: Need clarification

Added mapping of IPG to IPD.

20 C4-24 c4.6.5.5.14 S Coordinator Comment: Do not agree with 

eliminating 5% as outliers

Coordinator Justification: The highest 5% 

should not be termed "outliers," but rather 

supply chain failures. While these transactions 

do have a disproportionate impact on overall 

average times, eliminating them excludes 

important data that should be analyzed as it 

directly and adversely impacts customer 

support.

LRT is computed both in total 

and with the 5% of outliers 

excluded. Since the stated 

purpose of this DLMS Change 

is to document the As-Is state of 

LMARS, any change to use of 

5% would require a separate 

PDC to be coordinated with the 

entire PM PRC.