Page 2 Attachment, ADC 486

ADC 486

Administrative Change to Delete Document Identifier Codes QD1/QR1 

Routing Identifier Code Interrogation Request/Response Transactions

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: DLA Transaction Services, (937) 656-3745

b. Functional POC: DLA Logistics Management Standards, (703) 767-5111

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Routing Identifier Code (RIC) Inquiries

3. REFERENCES:

a. DOD 4000.25-1-S1, MILSTRIP Supplement Routing Identifier and Distribution Codes

b. DODI 4140.01, DoD Supply Chain Materiel Management Policy, December 14, 2011

c. DRAFT DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP)

4. APPROVED CHANGES:

a. Brief Overview of Change: Delete the Document Identifier Codes (DIC) QD1 Routing 

Identifier Interrogation Request and QR1 Routing Identifier Interrogation Response transactions. 

b. Background:

(1) DODI 4140.01 directed the conversion of the DOD 4000.25-1-S1 to DLM 4000.25-

1. During the review of the MILSTRIP Supplement for planned integration with DLM 4000.25-

1, Appendixes 2.3 (Routing Identifier Codes) and 2.12 (Distribution Codes), it was discovered 

that there were legacy references to the DIC QD1 and QR1 RIC Interrogation Request/Response 

transactions. 

(2) With the deployment of the enhanced Defense Automatic Addressing System 

(DAAS) Inquiry (eDAASINQ) system, RIC inquiries are now supported by directly querying the 

DLA Transaction Services electronic database for these codes; it is accessible from their website 

at https://www2.transactionservices.dla.mil/portal/portal.asp.

(3) Legacy Business Process: When an activity wanted to query DLA Transaction 

Services to ascertain the address for a particular RIC, they generated the DIC QD1 transaction 

and transmitted it to DLA Transaction Services. Upon successful query in the RIC database, 
Page 3 Attachment, ADC 486

DLA Transaction Services generated the DIC QR1 transaction with the address information and 

transmitted it to the activity that submitted the DIC QD1.

(4) History Search: DLA Transaction Services conducted a two year search (2010 to 

the present) in their database to determine if there were any DIC QD1 and QR1 transactions in 

their history.

(a) DIC QD1 – None received at DLA Transaction Services

(b) DIC QR1 – None generated by DLA Transaction Services

1. 2011: 38 received at DLA Transaction Services from COMMRI RUSADJB: 

NAVFAC Expeditionary Logistics Center Port Hueneme, CA 

2. 2010: 16 received at DLA Transaction Services from COMMRI 

RUSANMG: Northrop Grumman San Diego, CA

(5) While there were 54 DIC QR1 transactions received at DLA Transaction Services, 

they were not originated from DLA Transaction Services, the authorized data source for RIC 

information. This historical usage is not compliant with the legacy business rules as stipulated 

by the DOD 4000.25-1-S1. Additionally, the transaction formats used by the two field activities 

were not completely consistent with those stipulated by the DOD 4000.25-1-S1.

c. Describe Requested Change in Detail:

(1) Per the policy guidance in DODI 4140.01, convert the contents of the DOD 4000.25-

1-S1 into the DLM 4000.25-1. RIC information shall be integrated with DLM 4000.25-1, 

Appendix 2.3.

(2) Delete all references to the legacy DIC QD1 and QR1 transactions and associated 

business rules and processes.

(3) Advise the using community to make all RIC inquiries via the DLA Transaction 

Services Portal, using the eDAASINQ application. NOTE: A System Access Request (SAR) 

and Common Access Card (CAC) or External Certificate Authority (ECA) is required to access 

this application. To submit a SAR request, go to the following URL: 

https://www.transactionservices.dla.mil/sar/sar_menu.asp

(4) For those users unable to obtain access to eDAASINQ, you may access DAASINQ 

(public access version) by going to the following URL: 

https://www.transactionservices.dla.mil/DAASINQ/. 

(5) For those users with no internet access, the DLA Transaction Services helpdesk can 

assist. DSN 986-3247 or Commercial (937) 656-3247.

(6) For systems requiring high volume access to RIC information, making web inquiries 

impracticable, a data replication service is available. Contact DLA Transaction Services for 

more information on how to establish this service.
Page 4 Attachment, ADC 486

d. Revisions to DOD 4000.25 Manuals: See Enclosure 1 for changes to DLM 4000.25-1, 

Appendix 2.3.

5. REASON FOR CHANGE: Update the MILSTRIP manual to reflect current business 

processes for conducting RIC inquiries with the authorized data source at DLA Transaction 

Services. Ensure all users are querying from the single DOD authorized data source for RIC 

information.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Use of single authorized data source for RIC inquiries and streamlining of 

RIC inquiries via the web or through data replication.

b. Disadvantages: None noted. The isolated uses of DIC QR1 transactions were neither 

authorized nor compliant with DOD 4000.25-1-S1.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: June 2012

8. IMPACT:

a. Automated Information Systems (AIS): Components should verify and discontinue 

generation of DIC QD1/QR1 transactions.

b. DLA Transaction Services: Discontinue receipt and generation of DIC QD1/QR1 

transactions. Work with users to gain access to DAASINQ or eDAASINQ. For users without 

internet access, provide RIC interrogation support via the helpdesk. Work with systems desiring 

data replication services for RIC information.

c. Non-DLA Logistics Management Standards Publications: Components should update 

any local policies and procedures regarding the discontinuance of the DIC QD1/QR1 

transactions.
DLM 4000.25-1, XXXX 2012

Page 1 Enclosure 1, ADC 486

AP2.3. APPENDIX 2.3

ROUTING IDENTIFIER CODES 

AP2.3.1. Routing Identifier Codes (RIC) (located in rp 4-6, 67-69, and 74-76 of 

transactions) are assigned by Service/Agencies (S/A) for processing interS/A, and 

intraS/A logistical transactions. The codes serve multiple purposes in that they are 

supply source codes, intersystem routing codes, intrasystem routing codes and 

consignor (shipper) codes. DLA Transaction Services maintains an electronic 

database of these codes which are is accessible from their website1

http://www2.transactionservices.dla.mil/portal/portal.asp /.

AP2.3.2. To qualify for assignment of an RIC, the facility/activity must be an integral 

and predetermined element of an established logistical system and must perform a 

general logistical control, distribution and/or storage mission (to include bases, posts, 

camps, and stations, when applicable).

AP2.3.3. The use of an RIC on any one document does not infer, imply, or intend that 

follow-on documentation resulting from there from must contain the same RIC or any 

element thereof. It is a fundamental premise of Military Standard Requisitioning and 

Issue Procedures (MILSTRIP) that any RIC serves as only one of the following:

AP2.3.3.1. An address to indicate the intended recipient of the document for 

logistical actions.

AP2.3.3.2. Identify Identification of the actual consignor (shipper) on supply type 

release/receipt transactions originated within the distribution system(s).

AP2.3.4. All authorized RICs shall contain one of the characters depicting Service 

assignment as listed in MILSTRIP AP2.2., Document Identifier Codes (DIC)Service and 

Agency Codes, in the first position.

AP2.3.5. The second2 and third positions may be in any combination of alphanumerics. 

These positions may identify either a facility or activity of the S/A depicted by the first 

position.

AP2.3.6. Each S/A is responsible for the assignment of RICss to its facilities and 

activities. An S/A which that has activities located at another S/A facility shall assign its 

own RIC to the activity. An S/A which has assets located at another S/A facility shall 

use the RIC assigned by the S/A owning/operating the facility. (An appropriate RIC may 

be assigned to identify these assets when requested by the S/A owning the assets.) 

 1

DLA Transaction Services requires a user authorization to obtain information from their website. If you do not 

currently have approved access to DAAS (user id and password), please complete a request for access by going to 

the following website: https://www.transactionservices.dla.mil/sar/sar_menu.asp. 2

Y in second position identifies United States Coast Guard contractor use only when first position is Z.
DLM 4000.25-1, XXXX 2012

Page 2 Enclosure 1, ADC 486

Washington Headquarters Service (WHS) shall make RIC H_ series assignments for 

“Other DoD Activities.”

AP2.3.7. Each S/A shall designate a coordinator with responsibilities to control, 

monitor, and submit/validate all RIC additions, revisions, and deletions relative to its 

S/A. In most cases the DoDAAC and RIC coordinators (or monitors) are the same.

S/A coordinators established for assignment of RICs are available at: 

www.dla.mil/j6/dlmso/CertAccess/SvcPointsPOC/ServicePoints/DoDAAC_DOD_Monitors.pdf.

lAP2.3.8. DLA Transaction Services maintains the RIC database and serves as the 

focal point for receipt of all RIC database revisions. DLA Transactions Services shall 

monitor RIC code assignment for compliance with the above assignment rules. 

RIC database is published electronically and updated from requests for additions, 

changes, and/or deletions as submitted by the Component RIC coordinators. Interested 

parties may interrogate the RIC database through the DLA Transaction Services

website3 at https://www2.transactionservices.dla.mil/eDAASINQ/. 

 3 DLA Transaction Services requires a user authorization to obtain information from their website. If you do 

not currently have approved access to DAAS (user id and password), please complete a request for access by 

going to the following website: https://www.transactionservices.dla.mil/sar/sar_menu.asp.