DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

December 8, 2022

MEMORANDUM FOR RECORD

SUBJECT: Administrative Defense Logistics Management Standards (DLMS) Change (ADC) 

1263A, Administrative Update to Correct Exemption Date

The attached approved administrative change is effective immediately. This 

administrative change does not change or eliminate any existing procedures or add any new 

procedures. The change is to fix the date to represent five years (as stated in ADC 1263).

The Defense Enterprise Data Standards Office (DEDSO) point of contact is Richard 

Morrow, DoDAAD PRC Chair, at 571-527-6692 or e-mail: EBSO.DoDAAD@dla.mil. 

Attachment

As stated

cc:

ODASD(Logistics)
 

Attachment, ADC 1263A 

Page 1 

ADC 1263A

Administrative Update to Correct Exemption Date in One DoDAAC 

to One RIC Change - MFR

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Defense Enterprise 

Business Data Standards Office (DEDSO), DoDAAD PRC Chair, Richard Morrow, at 571-767-

5256, email: DoDAAD@dla.mil. 

2. FUNCTIONAL AREA: DoDAAD

3. REFERENCES: DLM 4000.25, Defense Logistics Management Standards (DLMS), 

Volume 6, Chapter 2, Department of Defense Activity Address Directory.

4. PROPOSED CHANGE(S): 

a. Bottom Line Up-Front: 

(1) The change is to correct the year of the exemption date December 31, 2025. 

(2) This change has no impact on standard business processes, data standards, or 

systems.

(3) This change replaces ADC 1263. 

b. Overview: This change implements the rule that a Department of Defense Activity 

Address Code (DoDAAC) can only be associated to one Routing Identifier Code (RIC). The 

sections highlighted in yellow italics were changed during staffing. All the Components have 

concurred and the highlighted sections were added at the request of Air Force and Marines. 

They both needed more time to migrate to a one-to-one relationship, so this version adds an 

exception table to provide a way to bypass the edits for to up to five years. At the end of the 

exception period, the enforcement of one RIC to one DoDAAC will be enforced without 

exception. 

c. Background: 

(1) When the DoDAAD was created in 1962, the RIC was created as a shortened 

version of a DoDAAC to fit into an 80 record position transaction in order to identify the activity 

to which the transaction was to be routed. Every RIC was to associate to a single DoDAAC, as 

its shorthand version for an 80 record position transaction. The goal was to drop RICs once all 

records were DLMS and DLMS no longer would need to support backup compatibility with 

Defense Logistics Standard Systems (DLSS) and all transactions would route by DoDAAC. 

Today, 294 DoDAACs still relate to more than one RIC – 995 RICs in all. This many-to-one 

relationship between RICs and DODAACs impedes modernization efforts to transition to 

transaction routing by DoDAAC. Transitioning to DoDAAC-based routing is critical due to the 

limitations of the RIC (3-character code) in a modern, variable-length data environment. 
 

Attachment, ADC 1263A 

Page 2 

(2) The meta data of a RIC includes a RIC_DODAAC (the DoDAAC to which the 

RIC is associated), a single Type Address Code (TAC) address, a Major Command Code, a 

Create Date, and a COMMRI. The RIC TAC address should be identical to the TAC 1 address 

of the RIC_DODAAC, since the RIC is intended to associate to the DoDAAC for which it exists 

as a shorthand version. This address of the RIC was to facilitate the ability to contact the activity 

identified by the RIC to mail paper documents that were not automated by legacy MILS 

transactions, (e.g., proof of delivery, DD250s, reports of discrepancy, etc.). The mailing of these 

documents today has largely been automated via EDI transaction exchanges. Eighty percent of 

all RICs use the same address as the TAC 1 of the associated RIC_DODAAC. For purposes of 

shipping, the RIC is associated to a DoDAAC and the TAC 2 of the RIC_DODAAC provides the 

freight address for cargo movements. As mentioned previously, the RIC address is not for 

shipping. 

5. ROLES AND RESPONSIBILITIES: 

a. DAAS:

(1) DoDAAD Update Application: 

(a) Currently, the RIC field in the DoDAAC is not used (Reference 3.b.). 

DAAS will need to establish a RIC edit by using the RIC field in the DoDAAC to enforce a oneto-one relationship between DoDAAC to RIC. When adding or updating a RIC, the associated 

DoDAAC in the RIC_DoDAAC field is required. If the corresponding DoDAAC associated to 

the RIC_DoDAAC contains nothing in the RIC field, the RIC value will be updated in the 

DoDAAC record. If the corresponding DoDAAC contains a RIC in the RIC field, it must match 

the RIC currently being updated for that DoDAAC, or the RIC record update should be rejected 

with an error message (e.g., “the RIC DoDAAC contains a RIC that is different from the one 

being updated.”). 

(b) The address fields in the RIC must be changed to read-only and populated 

with the TAC 1 address of the RIC_DoDAAC on update. The RIC address will no longer be 

manually entered.

(c) When a RIC is deleted, the RIC field in the corresponding DoDAAC will be 

removed. The DoDAAC record itself will not be deleted, just the relationship between the RIC 

and the DoDAAC.

(d) For the DoDAAC update, when a DoDAAC is deleted, the corresponding 

RIC record must also be deleted. 

(e) Last, in the DoDAAC update page, the RIC field in the DoDAAC record 

(updated by the RIC update logic) must be displayed. It was removed by Reference 3.b. 

(f) Exception processing for the Cargo Movement Operations System (CMOS) 

to be implemented and remain in effect until December 31, 2025: 

1. DAAS will need to maintain an exception table of DoDAACs. 

This table will bypass the edits outlined above. If a DoDAAC exists in the exception table, the 
 

Attachment, ADC 1263A 

Page 3 

one-to-one edits will be ignored. This will allow the Air Force and Marines time to migrate their 

existing RIC dependent processing to DoDAAC/COMMRI for routing transactions. 

2. The exception table will be based on an existing series of 

DoDAACs. If required, Air Force and Marines may request EBSO (EBSO.DoDAAD@dla.mil) 

add an additional DoDAAC to the exception table or remove an existing one. When the 

exception period ends or both Air Force and Maines have completed their migration process 

from RIC to DoDAAC/COMMRI (whichever occurs first), the table will be emptied and the 

one-to-one relation for all DoDAACs and RICs will be enforced without exception. No 

extensions will be granted beyond December 31, 2025. 

(2) DoDAAD Database Update: DAAS will need to align all the one-to-one 

relationships that currently exist within the DoDAAD database. If there is already a one-to-one 

relationship between DoDAAC and RIC, the RIC field of the DoDAAC record must be updated 

with the corresponding RIC value from the RIC table. If there is not a one-to-one relationship, 

do not populate the RIC field within the DoDAAC record and the update application will make 

the update the next time the CSP edits the RIC. 

b. Components: 

(1) There are 284 DoDAACs that have more than one RIC associated to them – 775 

RICs in all. The affected records include GSA, Army, Air Force, USSOCOM, NGA, USMC, 

Navy, and DLA. This change includes the exceptions specifically requested by Air Force and 

Marines (see enclosure 1 to this attachment). 

(2) CSPs must review these records to determine if any of these RICs are still valid, 

and take one of the following options for action, according to the implementation schedule of 

this change: 

(a) Delete any RICs no longer required. 

(b) For any RICs that are required, assign them to another existing DoDAAC to 

achieve the one-to-one relationship, or 

(c) Clone the existing DoDAAC by creating new DoDAACs for each RIC, 

using the same data contained in the original DoDAAC, to achieve the one-to-one relationship. 

c. Defense Enterprise Data Standards Office: 

(1) Revisions to Defense Logistics Manuals: 

(a) Volume 6, Chapter 2: 

 C2.1.2.2. RIC. The RIC is a 3-character, alpha-numeric code that uniquely 

identifies a unit, activity, or organization that requires system ability to route transactions 

or receive transactions routed to it (e.g., source of supply) within logistics and financial 

business systems that use using DLMS and legacy, 80 record position formatted 

transactions (e.g., MILS). The RIC was originally conceived as a means to identify an 

activity in an abbreviated form in the limited MILS data environment, so as not to require 
 

Attachment, ADC 1263A 

Page 4 

the use of the longer six-character activity identifier of a DoDAAC, or a seven-character 

Communication Routing Identifier (COMMRI), but its use has since expanded. The first 

character position of the RIC designates the particular service/agency ownership of the 

record, the second and third characters are determined by the Central Service Point 

(CSP). See also paragraph C2.5 of this Chapter. 

C2.5.1. Purpose. The use of the RIC has evolved over time, and its originally

intended purpose was to identify an activity with only three characters, for the 

routing of MILS transactions to and/or from that activity. Every RIC must 

associate to one DoDAAC (the RIC_DODAAC), and any activity (DoDAAC) that 

requires MILS routing can only have one RIC to identify it. The RIC’s Type 

Address Code (TAC) must match the TAC 1 of the associated RIC_DODAAC. 

The TAC address was intended to be used for the mailing of paper documents to 

the activity for processes that were not automated by MILS transactions (e.g., 

proofs of delivery, reports of discrepancy, material inspection and receiving 

reports (DD250), etc.). The mailing of such documents has been largely replaced 

by DLMS transaction exchanges. Since this is a mailing address, RICs are not 

used for shipping. The RIC associates to a DoDAAC in the event that a shipping 

action is required to that activity. Shippers use the TAC2 of the RIC_DODAAC as 

the freight address for cargo movements. RICs serve multiple purposes: they may 

be supply source codes, intersystem routing codes, consignor (shipper) codes, etc. 

RICs are three-character codes associated with a DoDAAC and a unique seven 

character Communication Routing Identifier (COMMRI) for routing purposes. RICs are 

also discussed in DLM 4000.25-1, Military Standard Requisitioning and Issue 

Procedures (MILSTRIP), Appendix 2.3 - Routing Identifier Codes; DLM 4000.25, 

Volume 2, Appendix 7.2; and paragraph C2.5 of this Chapter.

C2.5.2. The DoDAAD is the official repository for DoDAACs and RICs, and DLA 

Transaction Services DAAS is the agent responsible for maintaining the DoDAAD, as 

well as for enforcing the data validation editing, routing, and electronic transmission of 

logistics transactions to the DoD Components, Federal Agencies, and contractors.

C2.5.4. Currently, there is an association in the DoDAAD between DoDAACs and 

RICs where a single DoDAAC can be associated to multiple RICs. 

 C2.5.5. 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 inter-S/A, and 

intra-S/A logistics transactions. The codes serve multiple purposes in that they are 

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

consignor (shipper) codes. Transaction Services maintains an electronic database of 

these codes. Users with accounts can access the database from the Transaction 

Services portal: https://www2.transactionservices.dla.mil/portal/portal.asp. Those 

without accounts can access the database, with limited functionality at 

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

C2.5.64. To qualify for assignment of a RIC, the facility/activity must have an 

assigned DoDAAC and be an integral and predetermined element of an established, 
 

Attachment, ADC 1263A 

Page 5 

legacy logistics system, and which activity requires the ability to route legacy (80 

rp) transactions. and must perform a general logistics control, distribution, and/or 

storage mission (to include bases, posts, camps, and stations, when applicable). 

 C2.5.7. The use of a RIC on any one document does not infer, imply, or intend 

that follow-on documentation from that location 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:

 C2.5.7.1. An address to indicate the intended recipient of the document 

for logistics actions.

 C2.5.7.2. Identification of the actual consignor (shipper) on supply type 

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

 C2.5.8. The first position of all authorized RICs will contain one of the 

characters depicting Service assignment as listed in DLM 4000.25, Volume 2, AP7.2., 

Service and Agency Codes .

 C2.5.9. The second and third positions may be in any combination of 

alphanumerics, except as noted in DLM 4000.25, Volume 2, Appendix 7.2. These 

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

 C2.5.10. Each S/A is responsible for the assignment of RICs to its facilities and 

activities. An S/A that has activities located at another S/A facility will assign its own 

RIC to the activity. An S/A that has assets located at another S/A facility will 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.) 

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

“Other DoD Activities.” 

 C2.5.11. Each S/A will designate a Central Service Point (CSP) with the 

responsibility to control, monitor, and submit/validate all RIC additions, revisions, and 

deletions relative to its S/A. In most cases the DoDAAC and RIC CSPs (or monitors) 

are the same. CSPs/monitors established for assignment of RICs are available at 

https://www.dlmso.dla.mil/CertAccess/SvcPointsPOC/ServicePoints/DoDAAD_Monitors.

pdf .

C2.5.12. RICs are maintained within the DoDAAD by CSPs and Monitors 

Transaction Services. The DoDAAD who serves as the focal point for receipt of all RIC 

additions, changes, and/or deletions, as submitted by CSPs/monitors. DAASDLA 

Transactions Services will monitor RIC code assignment for compliance with the above 

assignment rules. Interested parties may interrogate the DoDAAD for RICs through the 

EDoDAAD DAAS Transaction Services Website (CAC Required) at 

https://www2.transactionservices.dla.mil/eDODAAD_asearch/ric_menu.asp. 

(b) DoDAAD Data Elements. N/A
 

Attachment, ADC 1263A 

Page 6 

(2) New/Changes to Data Elements: None 

6. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Authorized for immediate 

implementation by DAAS upon publication of the ADC. The following critical deadline is

provided: 

a. DAAS. Target timeline for DAAS to implement in DoDAAD is 60 days from the 

publication of the ADC. 

b. Services/Agencies. Target timeline for implementation of the tasks outlined in 

paragraph 5.b. above is 120 days from the publication of the ADC. 

7. IMPACTS: 

a. Automated Information Systems (AIS): DoDAAD

b. Army and Air Force. Army and Air Force must make the necessary changes to their 

respective DoDAAC applications to mirror these changes to the DoDAAD upon publication of 

the approved change. 

c. Non-DLM Publications: The changes identified herein must be incorporated into the 

relevant Service/Agency-level DoDAAD management publications, including (but not limited 

to) the following: 

(1) 41 CFR, Federal Property Management Regulations 

(2) U.S. Army: AR 725-50 

(3) U.S. Air Force: AFMAN 23-230 

(4) U.S. Marine Corps: MCO 4400.201, Vol 2 

(5) U.S. Coast Guard: COMDTINST M4000.2 

(6) Defense Information Systems Agency: DISA Instruction 270-50-10 

8. PROPOSED DLMS CHANGE (PDC) 1263 RESPONSE/COMMENT RESOLUTION: 

Component Response/Comment Disposition

1 DAAS Concurs without comment – 3/19/2019 Noted

2 DLA Concurs without comment – 3/25/2019 Noted

3 DoDEA Concurs without comment – 3/26/2019 Noted

4 DeCA Abstain – 3/29/2019 Noted

5 DCMA Concurs without comment – 3/25/2019 Noted

6 WHS Concurs without comment – 3/26/2019 Noted

7 GSA Concurs without comment – 4/29/2019 Noted

8 Air Force Concurs with comment – 9/22/2020 Resolved

9 USMC Concurs with comment – 10/1/2020 Resolved at 10/1/2020 meeting
Enclosure 1, ADC 1263A

Page 1

Enclosure 1

Exception DoDAACs Associated to More Than One RIC

1. Air Force:

DoDAAC RICs DoDAAC RICs DoDAAC RICs DoDAAC RICs

FB2300 DPK FB4804 DEB FB6132 DPQ FB6540 DAN

FB2300 FDL FB4804 FEB FB6132 FD4 FB6540 FAN

FB2307 DU1 FB4809 DKN FB6141 DQU FB6562 DUP

FB2307 F3T FB4809 FKN FB6141 FQU FB6562 FUP

FB2316 DLJ FB4811 DXE FB6142 DQV FB6563 DUV

FB2316 FJL FB4811 FXE FB6142 FDP FB6563 FUV

FB2500 DMQ FB4814 DMH FB6151 DTP FB6606 DS8

FB2500 FMQ FB4814 FMH FB6151 FTP FB6606 FS8

FB2520 DMB FB4817 DA2 FB6152 DTK FB6633 DRJ

FB2520 FMB FB4817 FD2 FB6152 FTK FB6633 FRJ

FB2804 DMY FB4819 DLU FB6161 DNP FB6648 DAL

FB2804 FMY FB4819 FUM FB6161 FNP FB6648 FAL

FB2805 DZF FB4820 DGF FB6171 DTX FB6656 DNZ

FB2805 FZF FB4820 FG0 FB6171 FTX FB6656 FNZ

FB2812 DGA FB4830 DF5 FB6181 DBK FB6670 DHY

FB2812 FG7 FB4830 FFE FB6181 FBK FB6670 FJY

FB2823 DLW FB4832 DDF FB6201 DAU FB6675 DSM

FB2823 FWM FB4832 FDF FB6201 FAU FB6675 FSM

FB2835 DAV FB4850 DBP FB6202 DAW FB6703 DLD

FB2835 FFV FB4850 FBP FB6202 DAX FB6703 FMD

FB3010 DNJ FB4852 DYK FB6202 FAW FB6712 DJB

FB3010 FNJ FB4852 FYK FB6221 DPX FB6712 FJB

FB3020 DUZ FB4855 DYB FB6221 FDY FB7000 DWQ

FB3020 FUY FB4855 FYB FB6222 DQD FB7000 FWQ

FB3022 DNK FB4860 DEC FB6222 FQD FB7033 DBS

FB3022 FNK FB4860 FEC FB6223 DLS FB7033 FBS

FB3029 DUU FB4873 DUT FB6223 FSL FB7054 DWX

FB3029 FUU FB4873 FUT FB6231 DRF FB7054 FWX

FB3030 DVF FB4877 DXQ FB6231 FRF FD2020 F4U

FB3030 FVF FB4877 FXQ FB6232 DRK FD2020 FGZ

FB3047 DVW FB4887 DXK FB6232 FRK FD2020 YFG

FB3047 FDW FB4887 FXK FB6241 DNF FD2030 F8U

FB3089 DVQ FB4897 DXB FB6241 FNF FD2030 FHZ

FB3089 FV4 FB4897 FDB FB6242 DND FD2040 FFZ

FB3099 DWB FB4900 DR2 FB6242 FND FD2040 YFF

FB3099 FWB FB4900 FR2 FB6243 DNH FD2060 F2U

FB3300 DMN FB5000 DL2 FB6243 FG8 FD2060 FLZ

FB3300 FMN FB5000 FL2 FB6252 DTH FV0016 FL5

FB4407 DSW FB5004 DK9 FB6252 FTH FV0016 FVS
Enclosure 1, ADC 1263A

Page 2

DoDAAC RICs DoDAAC RICs DoDAAC RICs DoDAAC RICs

FB4407 FSW FB5004 FK9 FB6261 DSF FV4815 FKV

FB4417 DKV FB5799 D18 FB6261 FSF FV4815 DWG

FB4417 FYL FB5799 F18 FB6281 DYN FV4864 DYC

FB4418 DKY FB5806 DD9 FB6281 FYN FV4864 FSK

FB4418 FKY FB5806 FD9 FB6291 DBH FV5218 DAH

FB4419 DUQ FB5814 DDR FB6291 FBH FV5218 FZN

FB4419 FUQ FB5814 FDR FB6302 DBX FV5219 DAJ

FB4425 DJW FB5819 DZB FB6302 FBX FV5219 FZP

FB4425 FJW FB5819 FZB FB6303 DBW FV5293 DAK

FB4427 DZK FB5820 D09 FB6303 FBW FV5293 FZ3

FB4427 FZK FB5820 F9A FB6311 DXV FV5294 DZ4

FB4460 DUJ FB5832 DE3 FB6311 FXV FV5294 DZ6

FB4460 FUJ FB5832 FE3 FB6321 DHV FV5461 FJC

FB4469 DCD FB5833 DE4 FB6321 FH3 FV5461 FJD

FB4469 FCD FB5833 FE4 FB6322 DHF FV5683 DA3

FB4479 DJ5 FB5834 DE8 FB6322 FH5 FV5683 FV0

FB4479 F5J FB5834 FE8 FB6323 DHJ FV6433 D40

FB4484 DBY FB5860 D2B FB6323 FJJ FV6433 FCX

FB4484 FBY FB5860 FB2 FB6324 DHN FV6433 FCX

FB4486 DGB FB5897 DMP FB6324 FH2 FB2399 DFM

FB4486 FG1 FB5897 FMP FB6325 DHH FB2399 FZ9

FB4488 DKU FB5908 DX9 FB6325 FH0 FB4835 FWY

FB4488 FKU FB5908 FX9 FB6331 DKQ FB4835 DVY

FB4497 DJN FB6011 DMJ FB6331 FKQ FB4856 FUS

FB4497 FJN FB6011 FMJ FB6341 DRW FB4856 DUS

FB4524 DBG FB6012 DMK FB6341 FRW FB5205 DG8

FB4524 FBG FB6012 FMK FB6382 FJH FB5205 F8G

FB4528 DSB FB6021 DXH FB6383 DJF FB5209 DF2

FB4528 FSB FB6021 FXH FB6383 FJF FB5209 FE2

FB4540 D07 FB6022 DXP FB6391 DBF FB5230 DAS

FB4540 FCC FB6022 FXP FB6391 FBF FB5230 FAS

FB4600 DTV FB6031 DUF FB6401 DKW FB5240 DYT

FB4600 FTV FB6031 FUF FB6401 FKW FB5240 FYT

FB4608 DUB FB6032 DUN FB6411 DRU FB5260 DH4

FB4608 FUB FB6032 FUN FB6411 FRU FB5260 FH4

FB4610 DZD FB6041 DZN FB6421 DMX FB5270 DB6

FB4610 FZD FB6041 FZA FB6421 FMX FB5270 FB6

FB4613 DWZ FB6042 DYU FB6422 DNB FB5284 DB7

FB4613 FWZ FB6042 FYU FB6422 FBN FB5284 FB7

FB4620 DL7 FB6043 DYQ FB6423 DMZ FB5294 DH6

FB4620 FL7 FB6043 FYQ FB6423 FMZ FB5294 FJ6

FB4621 DQ8 FB6044 DZH FB6433 DVK FB5461 D5F

FB4621 FD8 FB6044 FZH FB6433 FVL FB5461 F5F

FB4625 DTJ FB6061 DWK FB6441 DXF FB5505 DTC

FB4625 FTJ FB6061 FWK FB6441 FXF FB5505 FTC
Enclosure 1, ADC 1263A

Page 3

DoDAAC RICs DoDAAC RICs DoDAAC RICs DoDAAC RICs

FB4626 DSH FB6071 DBV FB6451 DBU FB5518 DDV

FB4626 FSH FB6071 FB5 FB6451 FBU FB5518 FD0

FB4654 DPU FB6081 DJK FB6461 DKB FB5575 DFD

FB4654 FPU FB6081 FJK FB6461 FKB FB5575 FFD

FB4659 DRY FB6091 DLQ FB6471 DL8 FB5587 DEH

FB4659 FRY FB6091 FQL FB6471 FK8 FB5587 FE0

FB4661 DWH FB6101 DLB FB6476 DU8 FB5612 DCB

FB4661 FWH FB6101 FL0 FB6476 FU8 FB5612 FCB

FB4664 DYY FB6102 DLN FB6481 DKJ FB5621 DDQ

FB4664 FYY FB6102 FL1 FB6481 FKJ FB5621 FDQ

FB4668 DKP FB6103 DXL FB6482 DKK FB5681 DDH

FB4668 FKP FB6103 FXL FB6482 FKK FB5681 FDH

FB4686 DZY FB6112 DXD FB6491 DQW FB5682 DFU

FB4686 FZY FB6112 FXD FB6491 FQW FB5682 FFU

FB4690 DRV FB6121 DSK FB6492 DQZ FB5685 DFK

FB4690 FR3 FB6121 FS1 FB6492 FQY FB5685 FFK

FB4800 DKF FB6122 DSQ FB6493 DLX FB5804 FD7

FB4800 FKF FB6122 FSQ FB6493 FL9 FB5804 DD7

FB4801 DYD FB6123 DSX FB6501 DWY

FB4801 FYD FB6123 FSX FB6501 FW1

FB4803 DKX FB6131 DPW FB6521 DK7

FB4803 FKX FB6131 FNW FB6521 FK7

2. Marine Corps: 

DoDAAC RICs DoDAAC RICs DoDAAC RICs DoDAAC RICs

M94700 MG0 M94700 MGD M94700 MGQ M93636 MUP

M94700 MG1 M94700 MGE M94700 MGR M93636 MUS

M94700 MG5 M94700 MGG M94700 MGS M93636 MUT

M94700 MG6 M94700 MGG M94700 MGT M93636 MUV

M94700 MG7 M94700 MGK M93636 M0F M93636 MUW

M94700 MG8 M94700 MGL M93636 M0G M93636 MUX

M94700 MG9 M94700 MGM M93636 M0Z M93636 MUZ

M94700 MGA M94700 MGN M93636 MU7

M94700 MGB M94700 MGP M93636 MUF