IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

September 12, 2012 

MEMORANDUM FOR PIPELINE MEASUREMENT PROCESS REVIEW COMMITTEE 

(PM PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 1025, 

Update of Routing Identifier Codes, DOD Activity Address Codes, Reparable/Nonreparable National Item Identification Numbers, and Combatant Command 

designations in the Logistics Metrics Analysis Reporting System (LMARS) (Staffed 

as PDC 481) 

The attached change to DLM 4000.25, Defense Logistics Management System (DLMS), 

Volume 6, Chapter 4, Pipeline Measurement, the Logistics Metrics Analysis Reporting System 

(LMARS) business rules is approved for implementation. The changes to the DLMS Website 

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm pubs.asp will be posted within 10 days from the 

above date for implementation planning. Target implementation date for DLA Transaction 

Services LMARS changes is estimated to be complete by February 2013. 

Addressees may direct questions to Mr. Kenneth Deans, Chair, Pipeline Measurement 

PRC at 703-767-2611, DSN 427-2611 or email: Kenneth.Deans@dla.mil. Others must contact 

their Component designated representative. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

C!d~4UY Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program G Printed on Recycled Paper 
Attachment, ADC 1025

Page 1

ADC 1025

Update of Routing Identifier Codes, DOD Activity Address Codes, Reparable/Nonreparable National Item Identification Numbers, and Combatant Command Designations

in the Logistics Metrics Analysis Reporting System (LMARS) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: DLA Transaction Services, 937-431-8000

b. Functional POC: DLA Logistics Management Standards, 703-767-2611, DLA HQ, 

J33, 703-767-7297

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Logistics Metrics

b. Primary/Secondary Functional Process: LMARS

3. REFERENCES:

a. DOD 4140.1R Supply Chain Materiel Management Regulations

DLM Manual 4000.25, Defense Logistics Management System, Volume 6, Chapter 4, 

LMARS 

Business Rules: https://www2.transactionservices.dla.mil/lmars/busrules.asp

b. DLA Logistics Management Standards Memorandum, November 29, 2011, subject: 

Approved DLMS Change (ADC) 462, Defense Logistics Management System, Volume 6, 

Chapter 4, Pipeline Measurement, Logistics Metric Analysis System (LMARS) available at:

www.dla.mil/j-6/dlmso/elibrary/Manuals/DLM/V6/v6c4.docx

c. Deputy Assistant Secretary of Defense, Supply Chain Integration, Memorandum, 

September 24, 2010, subject: Establishment of the Pipeline Measurement (PM) Process Review 

Committee (PRC).

d. DLA Logistics Management Standards Memorandum, September 21, 2011, Approved

DLMS Change (ADC) 448, Implementation of International Organizations for Standardization 

(ISO) 3166-1 Codes for the identification of Countries and their Subdivisions, available at: 

www.dla.mil/j-6/dlmso/eLibrary/Changes/approved5.asp. 

4. APPRROVED CHANGES(S):

a. Brief Overview of Change: This change updates specific LMARS configuration and 

business rules that Components/Agencies have implemented since the Customer Wait Time 

Committee ceased its operation several years ago. Changes from PDC 481 are highlighted in 

yellow. 
Attachment, ADC 1025

Page 2

 (1) Each Component/Agency shall provide an updated, current listing of the Routing 

Identifier Codes (RIC) of each activity/location that functions as a wholesale Inventory Control 

Point Supply Processing Time (ICP) for that Component. Refer to Pipeline Segment Three of 

LMARS.

 (2) Each Component/Agency shall provide a listing of those RICs that shall be used by 

DLA Transaction Services to indicate Service Processing Time in Pipeline Segment Two of 

LMARS, prior to the ICP processing the requisition for release to a storage activity.

 (3) Each Component shall provide either a listing or business logic to identify all 

Department of Defense Activity Address Codes (DoDAACs) that identify National Guard or 

Reserve units for that Service for appropriate Guard and Reserve reports.

 (4) United States Transportation Command (USTRANSCOM) shall provide the 

business logic to identify the DoDAACs assigned to each Combatant Command (COCOM) to 

coordinate its reporting of Time Definite Delivery (TDD) LMARS reports. 

 (5) Components/Agencies shall validate reparable codes by Component to ensure the

Table contains the code set for reparable NIINs that will be used to flag reparables in the FLIS 

catalog by Component. These NIINs are used to filter transaction data to generate the Wholesale 

ICP Reparable NSN Reports.

b. Background:

 (1) LMARS uses the RICs provided by the Components to filter transactions into the 

correct segment categories for specific LMARS reports. Each document number that contains a 

Requisition TO-RIC and each Materiel Release Order (MRO) that contains a FROM-RIC that is 

contained in the Components’ RIC listings will be included in the appropriate ICP reports 

generated by LMARS.

 (2) LMARS also uses the RICs as defined by the Components to identify which 

requisitions were routed to a Service processing point prior to routing to the ICP. Refer to 

Pipeline Segment Two of LMARS.

 (3) LMARS uses the National Guard/Reserve DoDAACs to filter transactions into 

appropriate Guard and Reserve reports; they are also used to eliminate transactions from the ICP 

reports. 

 (4) LMARS will use the DoDAAC/COCOM data provided by USTRANSCOM to 

coordinate its reporting of TDD data with existing TDD reporting generated by 

USTRANSCOM.

 (5) LMARS will use the reparable indicator of NIIN items that the Components 

consider reparable to filter transactions into the Wholesale ICP Reparable National Stock 

Number report.
Attachment, ADC 1025

Page 3

 (6) Procedures, data elements, processing details in use today: 

 (a) The current list of Service RICs is used to filter transactions into either Service 

Processing Time (LMARS Segment Two) or ICP Processing Time (LMARS Segment Three)

was developed by the former Customer Wait Time Committee members during their meeting(s). 

Members voted to approve and implement the list during the meeting(s), and DLA Transaction 

Services coded the list in the LMARS report routines. 

 (b) Previously both the Army and Marines sent National Guard/Reserve listing to 

DLA Transaction Services on or before the 25th of each month via Secure File Transfer Protocol 

(SFTP). If DLA Transaction Services does not receive an updated file it uses the previous 

month’s file to produce the Guard and Reserve reports. DLA Transaction Services has not 

received an update “in many years”, so the listing currently in use is several years old. 

 (c) Navy notified DLA Transaction Services that there are no Navy Guard or 

Reserve activities, so no Navy Guard or Reserve reports are generated. 

 (d) Air Force provided DLA Transaction Service with a static list of Guard 

DoDAACs Fx5999 through Fx5970. Although this listing has not been reevaluated “in many 

years”, LMARS still uses it as the basis for the Air Force Guard units included in the report.

 (e) The COCOM listings previously were e-mailed to the LMARS program 

manager by the COCOMS on or before the 25th of each month. DLA Transaction Services has 

not received an update “in many years”, and as a result has ceased to produce the COCOM 

reports due to the lack of accurate data.

 i. USTRANSCOM’s Strategic Distribution Database (SDDB) maintains a 

country to COCOM assignment logic table. The list was manually developed by RAND nearly 

ten years ago and has been manually updated, as required, by DLA Operations Research in 

support of the SDDB. The country code used in the listing is usually a MILSTRIP code; 

however, there are several codes that are assigned as "placeholders" for regional country 

designations (e.g., Atlantic, Pacific, East Africa, Mediterranean, and West Africa) that are not 

MILSTRIP-compliant codes. There also country designations wherein there are multiple country 

codes to designate separate countries.

 ii. DLA Transaction Services systemically derives assignment of COCOMs in 

the DoDAAD, which is housed at DLA Transaction Services. The country code to COCOM 

assignment is derived from a table generated by TRANSCOM Reference Data Management 

(TRDM) team. The TRDM table joins two other TRDM tables (COUNTRY and LOGISTICSGEOGRAPHIC-REGION) to provide the updates to the DoDAAD at DLA Transaction Services. 

The COUNTRY table is sourced from National Geospatial-Intelligence Agency, while the 

LOGISTICS-GEOGRAPHIC-REGION is sourced from Chairman of the Joint Chiefs of Staff 

Manual (CJCSM) 3150.15C. In the column called CTRY_LOG_PLN_RPT_ID of the 

COUNTRY table, TRDM decodes the first character of the value and maps it to the first 
Attachment, ADC 1025

Page 4

character of the LOG_GRG_CODE in LOGISTICS-GEOGRAPHIC-REGION and then derives 

the COCOM based on the value in the LOG_GRG_TX column.

 iii. Based on a comparative analysis of the current SDDB COCOM assignment 

table and the DoDAAD COCOM assignment derived from the TRDM, USTRANSCOM, DLA 

Logistics Management Standards, and DLA Transaction Services agreed to use the DoDAAD 

COCOM assignment as the authoritative source for non-mobile units.

 iv. Components previously sent the Reparable NIIN list to DLA Transaction 

Services on a monthly basis via FTP, if there were any updates to the list. These lists are used to 

filter transaction data to generate the Wholesale ICP Reparable NSN Report. To ensure that the 

Reparable NIIN list is accurate, DLA Transaction Service needs each Component to validate 

reparable codes to ensure the Reparable list is current and up-to-date.

c. Approved Change in Detail:

 (1) Update of Component RIC: Each Component validated the RICs accurately 

identifying their wholesale ICPs for both Pipeline Segments Two and Three of LMARS. Once 

this change is approved and implemented in LMARS, an annual review of RICs will be initiated 

by the Chair of the Pipeline Measurement PRC. If the Components require a change prior to the 

annual review, they will submit an encrypted email to the Chair, PM PRC with the requested 

change.

 (2) Update of Service’s National Guard and Reserve Unit DoDAACs

 (a) Army: DLA Transaction Services will modify LMARS to query the 

DoDAAD. If the Major Command field in the DoDAAD contains either the value AR or NG, 

which correlates to the AESIP Assignment Codes of AR and NG, and the first digit of the 

DODAAC = W then flag the DoDAAC in LMARS as Army Guard/Reserve. 

 (b) Marine Corps: DLA Transaction Services will modify LMARS to query the 

DoDAAD and if the Major Command field in the DoDAAD contains the value R1, and the first 

digit of the DODAAC =’ M” then flag the DoDAAC in LMARS as Marine Corps Reserve. 

 (c) Navy: Navy confirms that no Navy Reserve units exist. 

 (d) Air Force: DLA Transaction Services will modify LMARS to query the 

DoDAAD to systemically identify Air Force National Guard units by flagging Guard 

DoDAACs Fx5999 through Fx6569 and Air National Guard DoDAACs Fx6600-6799.

 (3) COCOM Designations

 (a) To ensure synchronization with the USTRANSCOM’s TDD data reporting, 

LMARS will begin a phased implementation to assign COCOMs based on the Ship-To 

DoDAACs in Phase I. Phase II – IV are approved for future implementation.
Attachment, ADC 1025

Page 5

 (b) Phase I (Non-Mobile Units): 

 i. For purposes of the LMARS/SDDB harmonization project, Mobile

units are defined as Navy Service/Agency designator code DoDAACs (i.e. V, R). This aligns 

with the business logic used by the SDDB.

 ii. Source of COCOM Designation is the DoDAAD.

 iii. For all LMARS processing, DLA Transaction Services will use the 

state, country, and COCOM values for the Ship-To DoDAAC of each transaction at the time a 

shipment status record (DLMS 856S/Document Identifier Code (DIC) AS_; DLMS 945A/DIC 

ARO, DLMS 856S/DLMS 945A/DIC AU_) is established. 

 iv. During the life cycle of a document number, the state, country, and 

COCOM values may change for various reasons, such as change in Ship-To DoDAAC or change 

in addressing information for the DoDAAC in the DoDAAD. However, for LMARS purposes, 

the state, country, and COCOM values in the LMARS database, established at receipt of a 

shipment status transaction, will never change for the remaining life of the document number.

 v. State, country, and COCOM values shall be based on the DoDAAD Type 

Address Code (TAC) 2; if no TAC 2 is available, then the TAC 1 will be used. 

 vi. Transactions citing DoDAACs that are missing a state, country, or 

COCOM value or use APO, FPO, or DPO addresses will be "&" filled in the correlating data 

field of the Logistics Response Time (LRT) file.

(c) Phase II (Mobile Units): FUTURE PDC 

 i. For purposes of the LMARS/SDDB harmonization project, Mobile

units are defined as Navy Service/Agency designator code DoDAACs (i.e. V, R). This aligns

with the business logic used by the SDDB.

 ii. Source of COCOM Designation is the Cargo Routing Information

File (CRIF).

iii. Naval Logistics Support Center granted permission for DLA 

Transaction Services to use the CRIF for LMARS COCOM assignments.

 iv. DLA Transaction Services will need to develop appropriate tables, 

business rules, and maintenance of data content. Business rules will need to include logic to use 

the transportation mode/method, Issue Priority Group/Transportation Priority, and effective dates 

of routings, to identify the applicable port code/COCOM assignment. These will be defined in a 

future PDC.

 v. DLA Transaction Services will need to add the air/surface archive from 

the SDDB to facilitate in transit shipments at time of implementation of this new COCOM 

assignment logic in LMARS.
Attachment, ADC 1025

Page 6

 vi. DLA Transaction Services will need to add the Port of Debarkation to 

the LRT File. For the weekly LRT files, the COCOM assignment will be based on the CRIF 

routing. For the monthly LRT files, the COCOM assignment will be updated if the ship changed 

COCOMs during the elapsed time between the weekly and monthly runs for the LRT files.

(d) Phase III (Reporting Regions within COCOMs): FUTURE PDC

 i. DLA Transaction Services will need to modify LMARS to establish 

reporting regions within a COCOM to facilitate unique TDD standards set for a group of 

countries in a COCOM or for a location within a country within a COCOM.

 ii. The Uniform Materiel Movement and Issue Priority System (UMMIPS)

Area functionality needs to be evaluated to determine if the logic aligns with that used by the 

SDDB.

 iii. A key/method for identifying special locations within a country (e.g., 

POD) needs to be identified so that a unique reporting region can be flagged for that particular 

location.

 iv. A method to identify logic for grouping countries (e.g., country code) 

needs to be identified so that a group of countries can be assigned a reporting region for TDD 

purposes.

 v. Based on new business rules to establish reporting regions, any new data 

elements in support of the new business process will be added to the LRT file.

(e) Phase IV (MILSTRIP Exception Address Reporting): FUTURE PDC

 i. DLA Transaction Services will need to modify LMARS to establish a 

methodology for identifying the COCOM when the requisition/materiel release order carries an 

exception address.

 ii. The challenge is to derive the COCOM assignment based on clear text 

addressing, being able to extract the country code so that it can be bounced against the

aforementioned logic in the previous COCOM Assignment Phased implementation. The 

DoDAAD TAC 2 address is not a valid source since the exception address overrides the normal 

TAC 2 addressing. 

(4) Reparable NIIN Designations

 (a) Components validated Reparable Codes to accurately identify the reparable 

NIINs for their respective Component. Required changes submitted by Components for codes 

identified by the FLIS tables indicated below were submitted in their comments to this ADC.

Once these reparable codes are approved and implemented in LMARS, an annual review of 
Attachment, ADC 1025

Page 7

codes will be initiated by the Chair of the Pipeline Measurement PRC. (changes are in bold 

yellow italics). 

Component Approved Reparable Codes FLIS DOD 4100.39-M Volume, 10 Table October 1010

Army: A, D, H, F, O, L Table 87 -- ARMY RECOVERABILITY CODES

Air Force: C, T,P,S,U Table 69 -- AIR FORCE EXPENDABILITYRECOVERABILITY-REPARABILITY-CATEGORY CODES

Marines: D, H, F, O, Z, L Table 57 -- MARINE CORPS RECOVERABILITY CODES

Navy: 7G, 7R, 7H, 7Z, 7E

G,H,Q,X,E

Table 62 -- NAVY COGNIZANCE CODES

Table 63 – NAVY MATERIEL CONTROL CODES

Coast Guard: R, H, O Table 128 -- COAST GUARD REPARABILITY CODES

DLA: None Table 130 -- REPARABLE CHARACTERISTICS 

DLA currently does not send a listing of reparables for inclusion in the LMARS reparables 

report. DLA does not wish to include reparables in the LMARS reparable report at this time.

Navy generally uses Navy Cognizance Codes to identify Depot Level Reparables; there are some 

uses within Navy ERP of the Navy Materiel Control Codes.

STAFFING NOTE: The table above lists the current values of REPARABLE-CODE on file in 

DAAS for reparable NIINs with recommended changes by Service. The source of these codes 

DOD 4100.39-M, FLIS Manual, Volume 10 

(http://www.dlis.dla.mil/PDFs/Procedures/vol10.pdf),

 b). DLA Transaction Services will modify LMARS to flag NIINs as reparables 

based on the Component and FLIS code designations.

(5). ISO 3166-1 Country Code (pending transistion to new country code standard 

ADC 448B) compliance. DLA Transaction Services will ensure compliance with ISO 3166-1, 

Codes for the representation of names of countries and their subdivisions – Part 1: Country 

codes, as detailed in ) ADC 448. This will be accomplished by LMARS using the country codes 

as associated with a particular DoDAAD record for a DoDAAC. Since the DoDAAD will 

maintain the ISO 3166-1 country code compliance, LMARS by default will be compliant.

d. Revisions to Defense Logistics Manual (DLM) 4000.25 Manuals:

 (1) DLM 4000.25, Volume 6, Chapter 4, revises C4.6.3.1.2. Table D (changes are in 

bold yellow italics). Component wholesale ICPs RICs for Pipeline Segments Two and Three of 

LMARS. 

Component Code(s)

Army A12, A35, AKZ, AP5, B14, B16, B17, B46, B56, B64, B69, 

BR4,BAM

Navy N21, N23, N32, N35, N52, N77, NFZ, NRP

Air Force DLJ, FFZ, FGZ, FG5, FHZ, FLS, FLZ, FL5, FPD, FPZ, FZZ, F2U, 

F4U, F6U, F74, F77, F7U, F8U, F06, F01, F13, F09,F81, 
Attachment, ADC 1025

Page 8

F78,F85,F83,F52, F43, F59, F16, F20, F28, F56, F63, F50

Marine Corps M00, MA6, MA7, MA8, MA9, MPB,MHQ, LB2, LC3, LC5

Coast Guard ZIC, ZNB, ZNC, ZQC,ZYD

DLA S9C, S9E, S9G, S9I, S9M, S9P, S9S, S9T, SMS

GSA GSA

 (2) 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 LMARS output reports. These 

tables are provided at www.dla.mil/j6/dlmso/Archives/PMPRC/documents/KeyLMARSTables.docx

 e. Transactions Flow: No changes to transaction flow are required.

d. Alternatives: None identified at this time.

5. REASON FOR CHANGE: Tables of RICs, DoDAACs, COCOMs, and Reparable NIINs 

maintained by DLA Transaction Services have not been updated by Components for a number of 

years. As a result, some reports that were at one time generated by LMARS are no longer being 

generated; other reports contain out-of-date, erroneous information. Updating these lists will 

enable LMARS to generate current, up-to-date reports. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Implementation of these changes will enable LMARS to generate useful, 

up-to-date reports. 

b. Disadvantages: None identified.

7. ESTIMATED TIME LINE/IMPLEMENTION TARGET: DLA Transaction Services 

will provide implementation dates of this ADC when they become available.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: N/A

9. IMPACT: 

a. New DLMS Data Elements: No new DLMS Data Elements are required. 

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS): None

d. DLA Transaction Services: DLA Transaction Services will modify LMARS and LRT 

files.
Attachment, ADC 1025

Page 9

 e. USTRANSCOM’s Strategic Distribution Database (SDDB): USTRANSCOM will 

need to ensure that the SDDB retains COCOM assignment logic for items in Phases II through

IV, until such time as those changes are incorporated into LMARS via separate ADC.

10. PDC COMMENTS DISPOSITION

Response/Comment Disposition

Concurs with comments. DLA Transaction Services states that RIC SMS should remain as the only ICP 

RIC for DLA. Table 130 is the source for reparable codes, but DLA does not 

intend to submit a list for inclusion in LMARS at this time.

Concurs with comments. Air Force requested recoverable codes S, U to be added and C be deleted from 

the Recoverable Codes list used by AF. AF National Guard DoDAACs read are 

Fx5999 through Fx6569) and Air Force Reserve DoDAAC are Fx6600- Fx6799." 

Following CSWS ICP RIC to be added: F16, F20, F28, F56, F63 and the following 

CSWS ICP RIC deleted FFZ, FLS, FPZ, F6U, F7U, F50 from LMARS ICP Listing.

Concur with comment. Army Recoverable Codes: no change.

MAJCOM designations for Army request RIC B56 and B56 be removed AND BR4 

and BAM be addded from LMARS ICP RIC LIST

Army DODAAC flag for Reserve (AR) and Nagtional Guard (NG).

Concur with comment. All Marine Corps Reserve Unites can be identified with DODAAC MAJCOM R1 

idendtifier. Marine Corps reaparable code = D and L

Marine Corps ICP RICS: addMPB, MHQ, LB2, LC3, LC5 and delete M00, MA6, 

MA7, MA8, MA9

Concur with comment. NAVY ICP RICS are NRP, NFZ and N52. 

Navy reply in addition to stated recoverble codes G, H, Q, X and E they also use 

congiznace codes 7G, 7R, 7H, 7Z, 7E. 

Concur as written Noted

Marine Corps

Navy

United States Coast Guard

Organization

DLA Transaction Services 

Air Force

Army