DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

March 29, 2017

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

1176, Revised Procedures for Requisitioning under Inter-Service Maintenance 

Agreement (Project Codes 3AB, 3AD, 3BB) and Revised DLMS 832N Catalog

Data Support for Defense Logistics Agency (DLA) support of Navy Fleet 

Readiness Centers (FRCs) (Supply/MILSTRIP)

The attached change to DLM 4000.25, Defense Logistics Management Standards, and 

DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures, is approved for 

implementation. The updated DLMS Implementation Conventions (IC) will be posted to the 

Enterprise Business Standards Office Web at 

http://www.dlmso.dla.mil/elibrary/TransFormats/140_997.asp, within 10 days from the above 

date.

Addressees may direct questions to DLMS_MILSTRIP@dla.mil; Ms. Ellen Hilert, 

DOD MILSTRIP Administrator, e-mail: Ellen.Hilert@dla.mil, or Mr. Eric Flanagan, e-mail: 

Eric.Flanagan@dla.mil, MILSTRIP Alternate Others must contact their designated Supply 

PRC representative available at www.dlmso.dla.mil/eLibrary/ServicePoints/allpoc.asp.

HEIDI M. DAVEREDE 

Program Manager

Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)
Attachment, ADC 1176

Page 1

Attachment to ADC 1176

Revised Procedures for Requisitioning under Inter-Service 

Maintenance Agreement (Project Codes 3AB, 3AD, 3BB) and 

Revised DLMS 832N Catalog Data Support for Defense Logistics 

Agency (DLA) Support of Navy Fleet Readiness Centers (FRCs)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Army POC: Kurt Phoel, PEO EIS, SFAE-PS-AE-LMP, (862) 259-0186, 

kurt.m.phoel.ctr@mail.mil

b. DLMS Program Office POC: Ellen Hilert, MILSTRIP Administrator, 

DLMS_MILSTRIP@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Requisitioning and Distribution

3. REFERENCES:

a. ADC 103, Defense Automatic Addressing System (DAAS) Processing Rules for 

Project Code 3AD, July 23, 2003

b. Military Standard Requisitioning and Issue Procedures (MILSTRIP), Appendix 2.13, 

Project Codes

c. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, Supply

Standards and Procedures, Chapter 4, Requisitioning

d. Supply Process Review Committee (PRC) and Joint Physical Inventory Working 

Group (JPWIG) 13-1, Meeting focused on maintaining accountability during Organic Depot 

Maintenance and DMISA

e. Supply PRC and Joint Physical Inventory Working Group (JPWIG) 14-1, Meeting 

focused on accountability during Repair (Organic)

f. DLMS 842P, Product Quality Deficiency Report (PQDR) Data Exchange and 

Enhanced Exhibit Tracking via Standard Logistics Transactions

g. ADC 1007A, Enhanced Pre-positioned Materiel Receipt (PMR) Data for Product 

Quality Deficiency Report (PQDR) Exhibit Tracking, February 27, 2013

h. ADC 381, Procedures and Additional Data Content supporting Requisitions, 

Requisition Alerts, and Unit of Use Requirements under Navy Base Realignment and Closure 

(BRAC) Supply, Storage and Distribution (SS&D) Inventory Management and Stock Positioning 

(IMSP), July 1, 2010
Attachment, ADC 1176

Page 2

i. ADC 360, Procedures and Content Requirements for Catalog Data Support under 

Navy and Marine Corps BRAC, January 5, 2011

j. ADC 1159, New Supply Condition Code X, Suspended (Repair Decision Delayed), 

November 25, 2015

k. 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), September 12, 2012

l. Federal Logistics Information System (FLIS) Procedures Manual, DOD 4100.39-M, 

Volume 10.

4. REQUESTED CHANGE(S): Substantive updates subsequent to staffing are highlighted in

green.

a. Brief Overview: 

(1) This change revises and clarifies procedures supporting requisitioning under a 

Depot Maintenance Inter-Service Agreement (DMISA) or comparable agreement.

(a) Update Defense Automatic Addressing System (DAAS) to pass 

(rather than route) all requisitions containing Project Codes 3AB and 3BB to the activity 

identified by the routing identifier code (RIC)-To. This will allow DAAS to transmit the 

requisition to to the Principal (owner), rather than to the Federal Logistics Information System 

(FLIS) source of supply under DAAS routing rules. 

(b) Revise MILSTRIP to provide additional guidance specific to the use 

of Project Codes 3AB, 3BB, and 3AD, inclusive of the intended recipient of requisitions for parts 

needed to complete a maintenance action.

(c) Revise the MILSTRIP requisition data content rules to allow use of 

Supply Condition Code (SCC) by the repair agent when requisitioning for induction. The

following scenarios are included to clarify usage beyond the traditional requisitioning for 

unserviceable reparables (SCC F).

1. Use SCC Q (Suspended (Product Quality Deficiency)) for 

induction of a Product Quality Deficiency Report (PQDR) exhibit returned for warrantied repair.

2. Use SCC D (Serviceable (Test/Modification)) for induction of 

serviceable assets requiring maintenance/overhaul.

3. Use SCC G (Unserviceable (Incomplete)), as applicable, for 

induction of unserviceable reparables.

(2) This change also revises DLMS 832N Catalog Data Support transaction 

processing and data content. The primary focus is the DLA interface with Navy FRCs to provide 

additional catalog data content to enable requisitioning for induction as prescribed under this 

change.
Attachment, ADC 1176

Page 3

b. Background:

(1) A DMISA is a formal agreement, similar to a contract, whereby one military 

Service (the Repair Agent) agrees to provide depot maintenance support for another Service (the 

Principal). DMISAs are generally established to cover organic depot maintenance and related 

support functions for weapon systems, equipment end items, systems, subsystems, components, 

or commodity groups.

(2) Project Codes 3AB, 3AD, and 3BB were established to identify materiel 

requisitioned or shipped under a DMISA or comparable inter-Service agreement. 

(a) Project Code 3AB is used to requisition reparable items for induction 

to a designated repair activity for repair and return to an end user. 

(b) Project Code 3AD is used to requisition materiel (including both 

consumable and nonconsumable component parts) needed for performance of depot repair 

(overhaul and maintenance). 

(c) Project Code 3BB is used to requisition reparable items for induction 

to a repair activity for repair. 

(3) ADC 103 (Reference 3.a.) authorized requisitions containing Project Code 

3AD to bypass DAAS routing logic and be passed to the identified RIC-To in support of an 

inter-Service maintenance agreement. Passing the requisition was intended to allow the 

requisition to be directed to the Principal so that the Repair Agent can acquire materiel for use in 

the repair action that is already in the Principal’s inventory while ensuring that the requisition 

will not be rejected due to an unregistered user. It also eliminates the possibility that the source 

of supply will satisfy the requisition with a substitute item that may not be best suited for the 

repair. ADC 103 did not incorporate the reasons for the submission of requisitions to the 

Principal in the published MILSTRIP manual. 

(4) Following the release of ADC 103, the Army Logistics Modernization 

Program (LMP) implemented functionality to allow Army depot maintenance activities to 

requisition reparables for induction from the owning activity in support of DMISA and 

comparable inter-Service agreements. During this time, numerous transactions were routing 

back to LMP instead of the intended recipient. This occurred because the items were Armymanaged, and therefore, routed to the Army source of supply in accordance with MILSTRIP 

procedures. ADC 103 authorized passing of requisitions containing Project Code 3AD, but 

Project Codes 3AB and 3BB were not included in that change. As a workaround, the Army 

adopted the use of the DLMS 511R Referral Order (DIC A4_) as a way to bypass the source of 

supply indicated by the NSN. The Supply Process Review Committee Meeting (SPRC)

(Reference 3.d.) and Joint Physical Inventory Working Group (JPIWG) 14-01 Meeting 

(Reference 3.e.) identified a tasking to update the procedures associated with Project Codes 3AB, 

3AD, and 3BB. In addition to the Army-requested update to the DAAS logic, the Army

requested clarification of the definitions and procedures because it was difficult to distinguish 

between the codes due to limited information published in the MILSTRIP and DLMS manuals

(References 3.b. and 3.c.). 

(5) During weekly meetings of the ODASD(SCI)-led Supply Visibility – InterService Maintenance Working Group, Component representatives debated the appropriate party 
Attachment, ADC 1176

Page 4

to receive requisitions for piece parts including both consumable and nonconsumable parts. The 

group discussed alternatives for addressing these requisitions to the FLIS source of supply, the 

Primary Inventory Control Activity (PICA), the Secondary Inventory Control Activity (SICA), 

or the Principal. The chair asked each Service to research how their Service generates 3AD 

requisitions and recommend the most appropriate process for the future. 

(a) Ultimately, the group reached a consensus that (1) consumable item 

requisitions should be directed to the source of supply and (2) nonconsumable (reparable) item 

requisitions should be directed to the Principal.

(b) The Air Force representative noted that their maintenance activity 

supply system will have a significant problem switching over to send its requisitions for depot 

level reparable (DLR) parts to the Principal if there is an Air Force wholesale item manager for 

the stock number needed and this stock number is a stock funded item. The first problem is the 

fact the Air Force maintenance activity supply system is hard coded to send all requisitions to the 

Air Force wholesale system in this situation. The second problem is the fact the Air Force 

maintenance activity supply system has no funds to pay for these parts since the Air Force

wholesale system does not bill when it transfers materiel from its ownership to Air Force 

maintenance activity supply ownership. Software changes will be required, and process changes 

will be required (e.g., if the Air Force is the PICA, it cannot send a funded requisition to the 

Principal, so a MIPR is the only option currently available).

(6) Project Code 3AD Restriction to Nonconsumable Repair Parts. Proposed 

DLMS Change (PDC) 1176 retained the original guidance for applicability of Project Code 3AD 

to both consumable and nonconsumable repair parts. However, the PDC also contained 

alternative procedures to remove consumable items from Project Code 3AD procedures. A 

requisition for consumable parts would be submitted with no project code. DAAS would follow 

routine procedures to route these requisitions to the FLIS source of supply. Routing (rather than 

passing) the requisition could be advantageous after a logistics reassignment. The DLMS 

Program Office asked Components to indicate if they had a preference to restrict Project Code 

3AD to nonconsumable repair parts. The Army provided a recommendation to move forward 

with this alternative (see comment resolution table at ADC attachment paragraph 13). Given the 

advantage, and in the absence of other feedback or an identified requirement for continued use of 

Project Code 3AD for consumables, this approach has been applied to the ADC procedures.

(7) Expanded use of SCCs in Requisitioning for Maintenance Induction. 

During the staffing period, the Air Force recommended including additional SCC values for 

maintenance activity requisitions for induction. Under current procedures the SCC is not 

included in the requisition but traditionally applies to SCC F (Unserviceable (Reparable)). The 

original proposal supported inclusion of SCC Q for requisitioning of PQDR exhibits for

maintenance induction. The Air Force advised that there are additional SCCs applicable to 

reparables from DLA Distribution storage to the repair agent. Although the volume is small, it 

would be helpful if the repair agent could pull these assets into maintenance versus waiting on 

the principal to push these assets into maintenance. Based upon the Air Force recommendation, 

expanded use of the SCC has been applied to the ADC procedures. Here are some relevant 

examples to clarify the use of these additional SCC values. 
Attachment, ADC 1176

Page 5

(a) Example 1: SCC D (Serviceable (Test/Modification)). The Air 

Force is having the Army repair agent upgrade serviceable assets to a more preferred national 

stock number (NSN) version. The Air Force first has DLA reclassify SCC A assets to SCC D, 

and then these assets are issued to the local Army maintenance activity. The repair agent inducts 

under the original NSN and returns the modified SCC A asset under the new NSN, which then 

gets moved back over to DLA storage.

(b) Example 2: SCC G (Unserviceable (Incomplete)). The Army 

repair agent can't get the required serviceable replacement parts to fix an SCC F asset previously 

inducted. Based on the estimated shipment date for these parts, the repair agent decides it makes 

sense to return this asset, with unserviceable assets already removed, to local DLA Distribution 

storage using SCC G. When the replacement parts are finally received, the repair agents want 

this SCC G asset issued back to their facility so they can complete the repair. 

(8) DLA Catalog Data Support for FRC

(a) Discussion during Supply Visibility – Inter-Service Maintenance 

meetings and subsequent follow-on meetings with the Navy and DLA highlighted an ongoing 

problem applicable to Navy FRC requisitioning. Under ADC 381 (Reference 3.h.), DLA 

assumed consumable item support for Commander Fleet Readines Centers (COMFRC)

regardless of the FLIS source of supply (materiel provided under this agreement is commonly 

referred to as “YOTH”). Under the support agreement, the Navy FRC is expected to forward 

consumable item requisitions (or unfunded requisition alerts) to DLA. However, the FRC cannot 

comply with the existing BRAC rules because the FRC does not have a method of identifying 

which non-Navy managed items are reparables. The maintenance system at the FRC (NAVAIR 

Depot Maintenance System (NDMS)) has no FLIS interface; furthermore, the Navy has stated 

that no such interface will be established in the future. As a result, requisitions for both 

consumable and other Service-managed nonconsumable items are directed to DLA. DLA 

accepts these requisitions and re-requisitions the materiel from the Service source of supply. 

DLA has no visibility of the Principal and, therefore, cannot direct the nonconsumable repair part 

requisitions correctly (as formally documented in this ADC). The Air Force voiced their 

objections to the misrouted requisitions. DLA discussed various options for interim and long 

term solutions, and has agreed to provide additional catalog information for reparable items 

using their existing interface with NDMS for the DLMS 832N Catalog Data Support established 

under ADC 360 (Reference 3.i.). Rather than staffing the DLMS 832 revisions as a separate 

proposed DLMS change, the catalog data support enhancements for identification of reparables 

are included in this ADC by agreement between DLA and Navy. Although DLA support for the 

Navy under the BRAC rules is under review to develop an alternative approach requiring initial 

support within the Navy, the current plan is to move forward with the catalog data 

enhancements.

(b) Identification of Reparables. In order to satisfy the new 

requirement, the DLMS Program Office identified two approaches for reparables in the DLMS 

832N transaction and requested Component review. One approach mirrored the Logistics 

Metrics Analysis Reporting System (LMARS). LMARS uses the reparable indicator for items 

that the Components consider reparable to filter transactions to generate the Wholesale Inventory 

Control Point (ICP) Reparable National Stock Number Report (see ADC 1025 (Reference 3.k.)). 

For the alternative approach, the Navy and DLA requested inclusion of the following FLIS data 

elements related to identification of reparables: Nonconsumable Item Material Support Code 
Attachment, ADC 1176

Page 6

(NIMSC), Item Management Code (IMC), and the Depot Source of Repair Code (DSOR)

(allowing for multiple values). Additionally, DLA requested two unrelated updates to the DLMS 

832N which are incorporated in this ADC.

1. Net Price. Currently, DLA provides only the Navy net 

(exchange) price to the FRC. DLA requested reworking of the Net Price to allow multiple 

values identified by Service. This will provide appropriate information for FRC maintenance 

performed for other Services.

2. Change Transaction Processing. DLA indicated that there 

have been issues in the past when DLA provides a DLMS 832N change transaction to the 

Service, but it failed to post to the Service’s database because the original add transaction was 

not successfully processed. Because the change transaction contains all relevant data (rather than 

only updated information), the change can be processed independently. This is the same concept 

used for MILSTRIP requisitioning; it will be adopted for catalog data support as an authorized 

DLMS enhancement.

(c) As a result of Component feedback, this ADC adopts Navy/DLA 

recommendations.

c. Change in Detail:

(1) Modify DAAS to pass (instead of route) DLMS 511R (DIC A0_), 

requisitions, DLMS 511M (DIC AM_), requisition modifications, and DLMS 869F (DIC AT_) 

requisition follow-ups containing Project Codes 3AB and 3BB (as is currently done for Project 

Code 3AD).

(2) Revise MILSTRIP definitions for DMISA-related project codes and update 

narrative information provided in MILSTRIP guidance to clarify business rules and correct 

obsolete information.

(3) Revise the requisition format to allow identification of SCC for requisitioning 

of reparables for the purpose of maintenance induction. Procedures will support use of SCC D, 

F, G, and Q. Receiving activities will induct PQDR exhibits using SCC Q. 

Staffing Note: MILSTRIP procedures are applicable to inter-Service requisitioning under 

DMISA or comparable inter-Service agreement; however, Components may wish to support

intra-Component maintenance requisitioning using SCC W (Suspended (Repair Decision 

Delayed) with prior coordination between the Principal and the repair agent (see Reference 3.i.).

(4) Revise the DLMS 832N transaction and procedures as follows:

(a) Support additional data content for use in the DLA-Navy FRC 

interface. Refer to FLIS Procedures Manual, Volume 10 (Reference 3.l.) for definition and code 

values.

1. Add Non-Consumable Item Material Support Code (NIMSC). 

See FLIS Table 107.

2. Add Depot Source of Repair Code(s) (DSOR). See FLIS Table 

117. Allow multiple repetitions.
Attachment, ADC 1176

Page 7

3. Add Item Management Code (IMC). See FLIS Table 77.

4. Modify Net Repair Price (Exchange Price) field to allow 

multiple entries in conjunction with the Net Repair Price Phrase Data Service qualifier, to denote 

the impacted Service.

(b) Revise procedures applicable to the Navy catalog data support process 

to direct the receiving system to accept a Catalog Transaction Purpose Code CC (Catalog Record 

Changed) in same fashion as Code AA (New Catalog Record Added) transaction. Modified 

transactions contain all relevant data content and can be processed as an overlay. Accepting a 

modified transaction in the absence of a new record on file will resolve recurring issues when a 

receiving system fails to receive or does not react to a Code AA transaction. This procedure is 

optional for other trading partners; this ADC documents the process as an authorized DLMS 

enhancement requiring no prior coordination for implementation.

d. Revisions to DLM 4000.25 Manuals:

(1) Update MILSTRIP guidance (legacy and DLMS) as shown in Enclosure 1.

(2) Revise MILSTRIP, Appendix 2.13, Project Codes, Category C and D Table 

as follows:

CODE USE/REFERENCE

3AB

Service Codes:

All except B, D, K, P, and T

Used for requisition of reparable items for induction materiel 

shipments to a designated repair activity for repair and return to an 

end user as directed under existing agreements including Depot 

Maintenance Inter-Service Agreement (DMISA). DAAS will use 

the RIC-To to pass the requisitions to the activity indicated. 

3AD

Service Codes: 

All except B, D, K, P, and T

Used to identify materiel requisitioned for requisition of 

nonconsumable repair parts needed for performance of depot repair 

(overhaul and maintenance) under existing agreements including

Depot Maintenance Inter-Service Support Agreement (DMISA) 

items. DAAS will use the RIC-To (To) (rp 4-6) to pass the A0_

requisitions to the activity indicated. (This code will also assist in 

billing and credit processes.)

3BB

Service Codes: 

All except B, D, K, P, and T

Used for requisition of reparable items for induction materiel 

shipments to a repair activity for repair as directed under existing 

agreements including Depot Maintenance Inter-Service Agreement

(DMISA)or comparable inter-Service agreement. DAAS will use 

the RIC-To to pass the requisitions to the activity indicated. 

(Not applicable to repair and return. See Project Code 3AB)
Attachment, ADC 1176

Page 8

(3) Revise MILSTRIP, Appendix 3.2, Requisition as follows:

FIELD LEGEND

TYPE REQUISITION 

BLOCK NUMBER(S) 

(MANUAL) RECORD 

POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Blank

Supply Condition 

Code (SCC)

Block 23 70-80

(71)

Leave blank on inter-Component 

requisitions forwarded to the DLA and 

Government Services Administration 

(GSA) sources of supply.

a. This field is optional for intraComponent use

b. This field may be used for internal 

purposes on retained copies of 

requisitions.

c. When requisitioning specific 

reparables for induction under Depot 

Maintenance Inter-Service Agreement 

(DMISA) or comparable inter-Service 

agreement, cite the SCC applicable to 

the reparable item requested. 

Authorized SCCs include D, F, G, and 

Q. Requisitions for induction of a 

Product Quality Deficiency Report 

(PQDR) exhibit for warrantied 

maintenance will cite SCC Q.1

_______________

1 Refer to ADC 1176.

(4) Revise DLMS manual, DLM 4000.25, Volume 2, Chapter 23, Catalog Data 

Support, as follows.

(a) Navy Interface:

“C23.3.8.4. Modified Records. When the user entry modifies an existing record 

via the user unique screen application, the system will prompt the user will be prompted to save 

changes. This will trigger EBS to generate a DLMS 832N Catalog Data Support transaction 

citing Catalog Purpose Code CC, Catalog Record Changed. This record will contain all 

applicable data elements to build a record within Navy systems (allowing overlay, vice 

transmission of only the modified content). If the change is to an existing LSN record previously 

provided to a DSS site, a copy of the change will also be furnished. The system receiving a 

transaction identified by Catalog Purpose Code CC that is unmatched to an existing record in 

the database will accept the transaction and process it as a new record. 1”

_______________

1 Refer to ADC 1176. Staggered implementation applies.
Attachment, ADC 1176

Page 9

(b) Marine Corps Interface: 

“C23.4.7. Modified Records. When the user entry modifies an existing record via the 

user unique screen application, the system will prompt the user will be prompted to save 

changes. This will trigger the MCMC system to generate a DLMS 832N IA Catalog Data 

Support transaction citing Catalog Purpose Code CC, Catalog Record Changed. This record will 

contain all applicable data elements to build a record within the DSS system (allowing overlay, 

vice transmission) of only the modified content). The system receiving a transaction identified 

by Catalog Purpose Code CC that is unmatched to an existing record in the database will 

accept the transaction and process it as a new record. 1”

_______________

1 Refer to ADC 1176. Staggered implementation applies.

(5) Revise DLMS implementation conventions (ICs) DLMS 511R, 511M, and 

869F as shown in Enclosure 2. 

e. Transaction Flow: The DMISA process flows were identified during the 13-1 Supply 

Process Review Committee (SPRC) meeting; refer to DMISA Transaction Flow SPRC_JPIWG.pdf

(Reference 3.d.). The overall transaction flow is unchanged. However, DAAS added Project Codes 

3AB and 3BB to the DAAS edit allowing requisitions, requisition modifications, and follow-up 

transactions containing these project codes to be passed to the RIC-To.

f. Alternatives: Refer to PDC 1176 for original proposal.

5. REASON FOR CHANGE: This change adds Project Codes 3AB and 3BB to the DAAS 

processing rules established for Project Code 3AD, thereby negating the need to send referral or 

passing orders as a way to preserve the RIC-To in the transaction. This will allow requisitions 

containing Project Codes 3AB and 3BB to be passed (instead of routed) to the Principal under a 

DMISA, or a comparable agreement. This is beneficial as it will improve accountability during 

maintenance and standardize procedures across the Services.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) This change will allow proper transmission of requisitions for induction of 

assets into repair by all Services with minimal changes to MILSTRIP procedures. 

(2) The Principal will be able to recognize when the repair agent is trying to 

induct specific condition assets, including PQDR exhibits, rather than routine induction of a 

reparable in SCC F.

(3) The restriction of Project Code 3AD to nonconsumable repair parts will allow 

DAAS routing to the FLIS source of supply for consumables. This will ensure proper routing 

after a logistics reassignment. 

b. Disadvantages: Programming changes will be required to implement.
Attachment, ADC 1176

Page 10

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: Services will provide guidance to ensure compliance with DOD procedures 

requiring use of the requisition for induction to maintenance. Guidance must include use of the 

appropriate project code and authorize use of SCC.

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: 

a. The Air Force will document procedures for providing credit for return of reparable 

parts resulting from maintenance. It is not known at this time if a new project code to replace 

current use of Project Code 3AD for the carcass turn-in to trigger credit to repair agent will be 

appropriate. A brief description of this process is included in the Navy comments at ADC 

Attachment paragraph 13.

b. Components should evaluate their desire for additional update to the requisition 

format to include the PQDR Report Control Number (RCN) and provide feedback in their 

staffing response. Approved DLMS Changes in the 1007 series (Reference 3.f and 3.g.) provide 

functionality for inclusion of the PQDR RCN in the materiel release order (MRO) and prepositioned materiel receipt (PMR). Adopting this field in the requisition could further enhance 

requisitioning for induction to support systemic communication of the specific exhibit requested 

(when known) and perpetuation of the exhibit identification to the MRO.

Staffing Note: Components have not provided feedback on this aspect of the PDC 

documentation. If desired, Components must submit a separate proposal.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET:

a. DAAS: 

(1) Implement new project code DAAS logic within 30 days of the release of 

PDC 1176. DAAS reported implementation on May 19, 2016. Immediate implementation of 

this rule change was authorized by PDC as it was not considered a risk and ensured requisitions 

would be directed to the intended activity. 

(2) Implement map update for SCC within 30 days of the release an approved 

change.

b. For all others, phased and staggered implementation is authorized. Components must 

report implementation status to the DLMS Program Office. Component target dates for 

implementation should be no later than the target date for full DLMS compliance December 

2019.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available. The PDC requested that the 

Services provide savings and cost avoidances due to misrouted requisitions. The Services did 

not provide this information for inclusion in the ADC.
Attachment, ADC 1176

Page 11

11. IMPACT:

a. New DLMS Data Elements: New data elements are added to the DLMS 832N.

(1) Nonconsumable Item Material Support Code (NIMSC). A code 

identifying the degree of support received by an individual Secondary Inventory Control Activity 

(SICA) or identifying the Service(s) performing depot maintenance for a Lead Service (Primary 

Inventory Control Activity (PICA)). A nonconcumable item is defined as an item of supply that 

is managed by one or more Military Services as a nonconsumable (i.e., major end item, depot 

reparable, or nonstock-funded consumable). Code Source: DOD 4100.39-M Defense Logistics 

Information System (DLIS), Volume 10, Table 107.

(2) Item Management Code (IMC). A code identifying whether items of 

supply will be subjected to integrated management under the Defense Logistics Agency/General 

Services Administration or retained by the individual Military Services or other DoD 

components for management. Coding is accomplished under item management classification 

criteria. Codes are based on DOD criteria for items of supply. Code Source: DoD 4100.39-M 

Defense Logistics Information System (DLIS), Volume 10, Table 77, Part I.

(3) Depot Source of Repair Code (DSOR). A code identifying those activities 

that are approved to perform depot level maintenance for the Services. Code Source: DOD

4100.39-M Defense Logistics Information System (DLIS), Volume 10, Table 117, Part I.

(4) Net Repair Price Phrase Data Service Code. A code identifying the 

Service associated with the net (exchange) price for a repairable item that is unserviceable and is

turned in on an exchange basis (FLIS DRN 5235). Appllicable code values: A (Army), N 

(Navy), Air Force (F), or M (Marine Corps). Code Source: DOD 4100.39-M Defense Logistics 

Information System (DLIS), Volume 10.

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS):

(5) Army LMP to be enhanced to utilize DLMS 511R (DIC A0_), DLMS 511M 

(DIC AM_), and DLMS 869F (DIC AT_) transactions when requesting assets for induction 

under DMISA.

(1) All Components must ensure use of the appropriate project code when 

requisitioning under an inter-Service agreement.

(2) All Components must update requisitioning procedures to authorize/recognize 

use of SCC for requisitioning of PQDR exhibits, serviceable, and unserviceable assets for 

maintenance.

(3) Distribution Standard System: Revise logic for accepting DLMS 832N 

transactions for changes as new adds if the change is unmatched to the database. Insure DLMS 

832N transactions do not fail due to additional data content.
Attachment, ADC 1176

Page 12

(4) DLA Enterprise Business System and Navy NDMS: Revise catalog data 

support interface to support additional data content and to accept DLMS 832N transactions for 

changes as new adds if the change is unmatched to the database.

d. DAAS:

(1) Modify DAAS to pass (instead of route) DLMS 511R (DIC A0_), 

requisitions, DLMS 511M (DIC AM_), requisition modifications, and DLMS 869F (DIC AT_) 

requisition follow-ups containing Project Codes 3AB and 3BB. DAAS has already implemented 

this change based upon PDC 1176.

(2) Modify DAAS maps for inclusion of the SCC.

e. Non-DLM 4000.25 Series Publications: Update Service publications to reflect the 

updated definition for project codes and additional guidance for requisitioning under an interService agreement. Army update required for Army Regulation AR 725-50, Table C-27.

12. PROPOSED DLMS CHANGE (PDC) 1176 STAFFING RESPONSE/COMMENT 

RESOLUTION:

Originator Response/Comment Disposition

1. Army Concur with comment:

The Army-requested update to the DAAS logic, 

clarification of the definitions and procedures was 

requested since it was difficult to distinguish 

between the codes due to limited information 

published in the MILSTRIP and DLMS manuals.

"In the first word document enclosure on page 3, 

paragraph 5, subparagraph

(a) states: A consensus was ultimately reached that 

consumable item requisitions should be directed to 

the Source of Supply and non-consumable 

(reparable) item requisitions should be directed to the 

Principle".

The above statement should complement page 5, 

paragraph f: Alternatives

(Staffing Note:) "Components should indicate of 

there is a preference to restrict Project Code 3AD to 

non-consumable repair parts.

Functionally, this branch agrees that the Project Code 

3AD should be restricted to non-consumable repair 

parts.

Reason: Currently, GCSS-A activities route to 

NAMI (AJ2) based on the Source of

Supply equal to another Service RIC in the Army 

catalogue. In LMP, these items are coded as LCMC 

managed even though the Army LCMC doesn't plan,

Comments accepted. The ADC reflects 

revised business rules for use of Project 

Code 3AD. This project code will be 

restricted to use for nonconsumable 

repair parts.
Attachment, ADC 1176

Page 13

Originator Response/Comment Disposition

stock, store, nor issue these materials. Generally, 

LCMCs are registered on these items because the 

material is/was part of an Army-used weapon system

and the Army needs to receive cataloging, 

configuration information, etc. Because the ACMA 

RIC is equal to an Army LCMC, the profit centers on 

these materials are set to the LCMC profit center. 

These are consumable items, and are not stocked, 

stored, nor issued by the national level Army

registered activity, these materials should be 

considered Non-Army Managed Materials (NAMM) 

from a logistics and financial standpoint. We are 

working towards the requirement/resolution for LMP 

to allow the LCMCs to process consumable 

requisitions (and have the profit centers aligned 

correctly) the same way they currently process 

NIMSC 5 materiel today and, therefore, should

be segregated from the Project Code of 3AD.

2. Marine Corps Concur

During Interservice Maintenance Supply Visibility 

discussion with OSD SCI, the Marine Corps 

representative stated that the Marine Corps does not 

normally use the requisitioning procedures 

prescribed by MILSTRIP for induction into 

maintenance. Instead, the repair agent contacts the 

Principal off-line requesting the asset and the 

Principal generates the MRO.

Noted.

Components should follow MILSTRIP 

procedures. If the Marine Corps has 

cause for alternative procedures, these 

should be documented. The Marine 

Corps may recommend process 

deviations for inclusion in MILSTRIP 

if the Marine Corps considers these to 

be warrented.

3. Navy Concur

Recommend additional update to MILSTRIP for 

credit processing associated with Project Code 3AD. 

This method facilitates the processing of DMISA 

Agent Carcass Turn-in to Principal and Carcass 

Exchange Credits to the Agent Requisitioner on the 

original materiel requisition."

Clarification of above: Project code 3AD indicates 

the DMISA Agent Depot is ordering a Shop 

Replaceable Assembly (SRA) directly from the 

DMISA Principal (if required)-without regard to it 

normally being a user of the SRA-to complete a 

DMISA repair for the Principal. Carcass Exchange 

Credits would need to be triggered for the DMISA 

Agent "F" condition turn-ins. In other words, even if 

the other service is the PICA, SICA or not a 

catalogued user on the NIIN, the DMISA Agent 

Depot would order the SRA NIIN from Principal 

directly (not from its Service ICP) to support DMISA 

The Navy comments are noted, but 

update to MILSTRIP for the credit 

process is deferred for separate 

documentation and staffing. A new 

proposal is being drafted by the Air 

Force.
Attachment, ADC 1176

Page 14

Originator Response/Comment Disposition

work it is doing. The carcass turn-in should trigger 

an appropriate credit to the requisitioning depot 

document, with the turn-in being returned to the 

Principal "F" condition ownership stow. This would 

provide the Exchange Price to the Agent Depot for 

parts provided by the Principal to enable DMISA 

repairs for its materiel.

----------------------------------------------------------------

Internal Navy discussion identified the following 

requirements:

1. NDMS will be modified to accept and process 

additional information in the DLMS 832N. DLA 

will modify the DLMS 832N to pass the DMISA 

Principal FLIS Nonconsumable Item Material 

Support Code (NIMSC); Item Management Code 

(IMC); and the Depot Source of Repair Code 

(DSOR) to the FRCs so they can identify reparable 

items. This is acceptable to COMFRC.

The group agreed to caveat the above with the risks 

of not properly managing NSNs in FLIS. If FLIS 

information is not accurate, the Agent may not be 

able to identify the Principal and whether or not 

material is reparable.

2. NDMS will be modified to start using the project 

codes identified in PDC 1176. This is acceptable to 

COMFRC.

3. NDMS will be modified to send DMISA 

requisitions to the Principal. This is acceptable to 

COMFRC.

4. Interim Process: An interim process was 

discussed, to be implemented until the required 

system changes are complete (ECD early CY 2017). 

The process will consist of manual intervention on 

the shop floor to identify the Principle and apply the 

correct Project Code in accordance with the 

provisions of PDC 1176. The COMFRC business 

office will sign out a memo spelling out the required 

manual intervention.

5. Other Requirements: The group indicated two 

other necessary requirements:

----------------------------------------------------------------

NAVSUP WSS Comments:

1. For Army carcass inductions (project code 

3BB), Navy would have to require LMP to either 

place the fiscal year digit of the DMISA repair PO in 

------------------------------------------------

Noted. 

------------------------------------------------

No additional changes will be 

incorporated in this DLMS Change. If 

the Navy, in coordination with the other 

Services, requires additional 
Attachment, ADC 1176

Page 15

Originator Response/Comment Disposition

card column 12 of its requisition or upgrade DAC 

processing such that the DAC includes the funded 

DMISA repair order (PIIN) and line item of that 

order (CLIIN) on the DLMS DAC transactions. 

Navy also needs the fund code on the "F" condition 

requisition with project code 3BB to be 26.

2. For Air Force DACs, Navy needs card column 

11 of the document number to cite the fiscal year of 

the DMISA repair PO. If this new ADC 1176 

requirement disrupts this process, Navy input is 

required in terms of how the requisition number is 

constructed, and Navy wants the fund code to be 26. 

If Navy cannot control this process, then the Air 

Force D035K program needs to add PIIN and CLIIN 

to the DACs.

3. Project code 3AD indicates the Army, USMC 

or Air Force depot is ordering a Shop Replaceable 

Assembly (SRA) directly from the Navy—without 

regard to it normally being a user of the SRA—to 

complete a DMISA repair for the Navy. Credits 

would need to be triggered for the other service’s 

(Army/USMC/Air Force) "F" condition turn-ins. In 

other words, even if the other service is the PICA, 

SICA or not a catalogued user on the NIIN, the 

Army/USMC/Air Force depot would order the SRA 

NIIN from Navy ERP directly (not from its service 

ICP) to support Navy DMISA work it is doing. The 

carcass turn-in should trigger an appropriate credit to 

the requisitioning depot document, with the turn-in 

being returned to Navy ERP "F" condition ownership 

stow. Navy would need to walk through an example 

of these incoming orders to see how Navy ERP 

would handle them. On the flip side, where Navy 

FRCs are ordering a SRA from the Army/USMC/Air 

Force with 3AD, Navy needs to determine if an FTA 

should be triggered to provide credit. This may 

require a change to Navy ERP.

Navy ERP Comment:

1. PDC 1176 will have an impact on Navy ERP, 

based on the requirement to process Supply 

Condition Code Q.

FRC Questions/Comments:

1. Question: Does this PDC negate NDMS 

sending a copy of the 511R (A0_/A3_) for reparables 

to DLA, which they utilize to perform MOV and 

enhancements to the DLMS procedures 

addressed in ADC 1176, these should 

be documented separately by DLMS 

PDC.

A separate PDC is under development 

to address credit for exchange items.

Responses to FRC question 1: FRC 

procedures are impacted only to the 

extend that requisitions must be 

formatted to send requisitions for 

repairable parts to the Principal. 

Additional guidance pertaining to 

YOTH may result from ongoing 

discussions between Navy and DLA.

All other comments are noted.
Attachment, ADC 1176

Page 16

Originator Response/Comment Disposition

other Material Management functions on behalf of 

the FRCs?

2. NDMS will be modified to accept and process 

additional information in the 832N. DLA will 

modify the 832N to pass the DMISA principal FLIS 

NONCONSUMABLE ITEM MATERIAL 

SUPPORT CODE (NIMSC); ITEM 

MANAGEMENT CODE (IMC); and the DEPOT 

SOURCE OF REPAIR CODE (DSOR) to the FRCs 

so they can identify reparable items. There is a data 

accuracy risk if NSNs are not managed properly in 

FLIS. If FLIS information is not accurate, the agent 

may not be able to identify the principal and whether 

or not material is reparable. Note that the above 

changes to DLMS 832N will identify reparables but 

are not sufficient to identify the principal. Principal 

will need to be obtained from the NDMS workload 

data (PSA) prior to submitting requisitions. 

3. NDMS will be modified to start using the 

project codes identified in PDC 1176 and to send 

DMISA requisitions to the principal.

4. An interim process will be implemented until 

the required NDMS system changes are complete 

(ECD early CY 2017). The process will consist of 

manual intervention on the shop floor to identify the 

Principal and apply the correct Project Code in 

accordance with the provisions of PDC 1176. The 

interim process is dependent on completion of the 

832N update, and some modification to the NDMS 

DLR ordering function may be required to provide 

for the use of the new project code for interservice 

DLRs. The COMFRC business office will sign out a 

memo spelling out the required manual intervention.

5. NDMS does not currently requisition, report, 

or track DMISA end items. This process is handled 

offline between the DMISA workload planners and 

the DMISA Prime (customer), so any reporting 

problems would be in the DMISA Prime's system. 

There is a need to identify and levy requirements 

against an Automated Information System (AIS) to 

perform this process. CAV-ORM was mentioned as 

a potential candidate AIS, as it could be utilized for 

DMISA items similar to how it handles Navy intraservice assets today. For Navy assets, CAV-ORM is 

linked to Navy ERP, which creates the requisition 

and handles the accounting. For inter-service assets, 

CAV-ORM would rely on the other service’s system 

to perform these functions. If CAV-ORM is used, 

NAVSUP needs to consider the requirement for the 

Air Force to stow its "F" condition material in a colocated DLA DD.
Attachment, ADC 1176

Page 17

Originator Response/Comment Disposition

NAVSUP N3/4 Comments:

1. Before an AIS is selected to requisition, report 

and track DMISA items, functional business process 

changes are needed and will require documentation 

from COMFRC, NAVSUP N3/4 and NAVSUP 

WSS. Any functional and IT changes will be 

compliant with the DLMSO-prescribed DMISA 

workflows documented in the DLMSO SPRC brief 

dated 18 Apr 2013.

2. NAVSUP N3/4 will discuss business process 

changes with stakeholders and provide functional 

requirements to NAVSUP N6. NAVSUP N3/4, 

NAVSUP N6 and COMFRC will then identify the 

appropriate AIS based on the functional 

requirements.

 a. Change CAV-ORM to incorporate PDC 1176 

provisions in induction and custody control 

processes.

 b. Change DLA EBS to help NDMS distinguish 

between repairable and consumable items.

4. Air Force Concur with comment: 

AF MAJCOM AFMC is unable to support either

requirement in the near term. Requisitioning 

unserviceable/serviceable reparable repair parts from 

the Principal will take a major system change for 

D035A, D035K, and our financial system, D035J. 

CSRD in-draft. EDD 4-6 years.

Air Force prior comment:

Regarding identification of reparables, the Air Force 

responded: We recommend using the NIMSC code 

in the Navy/DLA code set. DoD 4100.39-M, 

Volume 10 contains the data values for: NIMSC 

(table 107), IMC (table 77) and DSOR (table 117). 

NSNs that contain an alpha (PICA) or numeric 

(SICA) are, by definition, nonconsumable. IMCs 

would be a little tricky. Some IMCs indicate 

consumable like IMC J, Q, T or V. IMC E

indicates reparable. The DSOR indicates the activity 

that performs depotlevel maintenance.

The Services were asked to comment on executing 

ADC 1176 requirements during Interservice 

Maintenance Supply Visibility discussion.

Specifically, if the Agent depot maintenance activity 

could (1) requisition from the Principle various 

condition codes (like Q, D, G & F) using project

Noted.

ADC 1176 authorizes staggered 

implementation. DLMS compliance 

target date is 2019. 

Requisitions forwarded to the FLIS 

source of supply will not drawdown 

parts held by the owner/principal and 

may be rejected due to an unregistered 

user edit. Inclusion of SCC is a 

beneficial enhancement, but a work 

around is available through off-line

communication. Recommend Air Force 

attempt to expedite implementation.
Attachment, ADC 1176

Page 18

Originator Response/Comment Disposition

code 3BB and (2) requisition serviceable 

nonconsumable component parts from

the Principle using project code 3AD.

Response: The Air Force will not be able to support 

either requirement in the near term. Requisitioning 

unserviceable/serviceable reparable repair parts from 

the Principal will take a major system change for 

D035A, D035K, and our financial system, D035J. 

At best we are 4-6 years away from being able to

do that.

The Air Force depot system, when the AF is the 

Principal, doesn't need any significant changes to 

implement this ADC. It is when the AF is the Repair

Agent that our depot system is significantly 

impacted.

If the AF Principal can't support a requisition with a 

3AD project code, it will be backordered. At that 

point, our PICA/SICA rules kick in. A

knowledgeable wholesale item manager should have 

no problem passing the requisition on to another 

service SoS. The odds are they won't, but now

we're back to a training issue; not a data system 

issue.

Prior Feedback: Air Force expressed concern that

we could cause irreversible harm (loss of 

property/loss of

life) if an AF Agent does not use a Principles 

repaired part when performing depot maintenance. 

I'm not overly concerned if the Principle/Agent

relationship is also a NIMSC 5 PICA/SICA. Where 

it gets "harry" is if there's a NIMSC 1,2,3,4,8 

relationship. Now we are dealing with parts

repaired under different repair specifications and 

owned by different Services.

5. DLA Concur

DLA identified requested updates to the 832N IC to 

support the new YOTH/DLR Routing:

The DSOR, IMC, and NIMSC fields in FLIS will 

help define who is the responsible entity for the 

Repairable material. The NIMSC and IMC define 

the item as Repairable (with layers) and the DSOR 

defines the responsible entity. 

We are providing the Repair Net Price and plan to 

bring it in from all Services if listed. Then we want 

to transmit it to the NDMS system (all of them), with 

Noted.
Attachment, ADC 1176

Page 19

Originator Response/Comment Disposition

their qualifier, so the NDMS system can determine 

which cost is actually associated. In today's 

environment, providing the Navy only Repair Price 

has worked for almost all materials. The problem is 

when the other services consider an item repairable 

and we do not have that Repair Net Price.

Regarding impact to other systems using an 832N 

interface with DLA EBS: If DSS and the Marine 

Corps can accept the 832Ns without modifications to 

their systems (after whatever updates occur), then 

that is great for them. However, since the 832N will 

have more loops (repair Net Price), additional fields 

(qualifiers for the extra Repair Net Price), and a 

longer 832N structure (because of the additions), I 

am not sure how any system could go unchanged. 

Unless they were originally designed with these extra 

capabilities without them being required.

6. DLMS 

Program Office The initial draft ADC identified the following LMARS procedures for identification of 

reparables:

 Component Approved 

Reparable Codes

FLIS DOD 4100.39-M Volume 10 Table 

Army A, D, H, F, O, L Table 87 -- Army Recoverability Codes

Air Force T, P, S, U Table 69 -- Air Force Expendability- Recoverability-ReparabilityCategory Codes

Marines D, 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, O Table 128 -- Coast Guard Reparability Codes

DLA None Table 130 -- Reparable Characteristics

Based upon Component feedback and agreement during the Supply Visibility – InterService Maintenance meetings, the more complex LMARS procedures are not 

necessary. Instead, this ADC adopts the Navy/DLA recommendation for new data 

content in the DLMS 832N.
Enclosure 1, ADC 1176

Page 1

Enclosure 1, MILSTRIP/DLMS Manual Revisions

Revise DLM 4000.25-1, MILSTRIP, as indicated in red bold, italics and strike-thru text.

Equivalent changes must be made to DLM 4000.25, DLMS, Volume 2, Supply Standards and 

Procedures, Chapter 4, Requisitioning.

“C2.23 REQUISITIONING REPARABLES FOR INDUCTION TO MAINTENANCE IN

SUPPORT OF AN INTER-SERVICE MAINTENANCE AGREEMENT 1

C2.23.1. When materiel scheduling a reparable item is scheduled for organic 

maintenance under a Depot Maintenance Inter-Service Agreement (DMISA) or comparable 

inter-Service support agreement, based on the repair schedule, the maintenance activity will 

requisition the materiel reparable item from the Principal (materiel owner) using an A0_ in the 

format specified in Appendix AP3.2. All requisitions will cite Advice Code 2J (fill or kill) in rp 

65-66, and the appropriate supply condition code in rp 71. Requisitions will cite Project Code 

3AB (repair and return under maintenance agreement) or 3BB (repair under maintenance 

agreement). When requesting specific assets, maintenance activities may cite the supply 

condition code (SCC) applicable to the reparable item requested. Authorized SCCs include D, 

F, G, and Q. Requisitions for induction of a Product Quality Deficiency Report (PQDR)

exhibit for warrantied maintenance will cite SCC Q. 

C2.23.2. Project Code 3AD supports requisitioning under a Depot Maintenance InterService Agreement (DMISA). When used, this project code will cause the requisition to be 

passed directly to the activity identified by the RIC in rp 4-6. DAAS routing rules will be 

overridden. If the submitting Component requires use of an alternate project code, (e.g., a 

contingency support project code), on a requisition for which 3AD functionality is also desired, 

the alternate project code would have precedence over the 3AD. In this situation, the requisition 

may be prepared as a passing order (DIC A3_) to preserve the proper destination while 

employing the Service-mandated project code. In response to requisitions citing Project Codes 

3AB or 3BB, the Principal will direct release of the reparable item from the storage activity to 

the repair agent. The Principal will establish a due-in and provide a pre-positioned materiel 

receipt (PMR) to the repair agent to ensure the item is receipted under the correct ownership 

(refer to MILSTRAP, Chapter 4).

C2.23.3. To preclude billing by the materiel owner, the A0_ requisition will also contain 

the following data elements to denote free issue. For A0_s submitted to:

C2.23.3.1. Air Force: For Air Force principals (RIC-To F**), use Project Code 

"3BB" in rp 57-59.

C2.23.3.2. Navy: For Navy principals (RIC-To NRP), use N00391 in rp 45-50,

Signal Code B in rp 51, and Fund Code 26 in rp 52-53. If RIC To is N32, use N00383 in rp 45-

50; if RIC TO is N35, use N00104 in rp 45-50.

C2.23.3.3. Army: For Army principals (RIC-To A** or B**), use Project 

Code"3BB" in rp 57-59; Fund Code GM in rp 52-53, and Signal Code D or M in rp 51.

 1 Refer to ADC1176. Staggered implementation of SCC for requisitions authorized.
Enclosure 1, ADC 1176

Page 2

C2.23.3.4. Marine Corps: For Marine Corps principals (RIC-To MPB), use 

Project code 3BB.

C2.23.4. Organic maintenance activities operating under a DMISA or comparable 

inter-Service support agreement will requisition nonconsumable repair parts required for a 

maintenance action using Project Code 3AD. Maintenance activities will direct reparable item 

requisitions to the Principal whose assets are intended are to be used for the repair (rather 

than to the source of supply). Directing requisitions to the Principal ensures appropriate 

actions are taken. 

C2.23.4.1. Directing requisitions to the Principal precludes rejection of the 

requisition because the repair agent may not be a registered user of the materiel. 

C2.23.4.2. Passing the requisition to the Principal reduces financial losses that 

would be incurred to purchase new materiel while previously purchased materiel is sitting in 

the Principal’s inventory. This will reduce inventory balances as intended at the designated 

Principal, and does not unnecessarily draw down inventory at the supply source.

C2.23.4.3. Requisitioning from the Principal eliminates the possibility that the 

source of supply will satisfy the requisition with a substitute item which may not be best suited 

for the repair. 

C2.23.4.4. This method of requisitioning facilitates accurate demand history 

capture at the source of supply (where it would otherwise be overstated) and improves 

forecasting by the Principal (where it would otherwise be understated).

C2.23.5. Organic maintenance activities will direct consumable item requisitions to the 

source of supply. Project Code 3AD does not apply. DAAS will process requisitions under 

MILSTRIP routing rules or by Service agreement.

C2.23.6. DAAS will pass requisitions (DIC A0_), modifications (DIC AM_), and 

follow-ups (DIC AT_) containing Project Codes 3AB, 3AD, and 3BB to the designated 

recipient (rather than routing to the source of supply).
Enclosure 2, ADC 1176

Page 1

Enclosure 2, DLMS Implementation Convention (IC) Revisions

# Location DLMS 511R Requisition 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1176, Revised Procedures for Requisitioning 

under Inter-Service Maintenance Agreement (Project 

Codes 3AB, 3AD, 3BB) and Revised DLMS 832N 

Catalog Data Support for Defense Logistics Agency 

(DLA) support of Navy Fleet Readiness Centers 

(FRCs)

Identifies DLMS 

Changes included in

the IC.

2. 2/LQ01/140 Add new DLMS Note to existing Code 83:

83 Supply Condition Code

DLMS Note:

DLMS Note:

1. Use to indicate the lowest acceptable condition of 

materiel when requisitioning from disposal DLA 

Disposition Services.

2. Use to indicate condition of previously purchased 

materiel. This is a restricted use applicable when a Service 

has entered into an MOA with DLA relative to Serviceowned stocks, centrally-managed/stored by DLA 

(1/BR06/020, Code RI).

3. Also authorized on an Intra-Army basis with BR02 

transaction type code A0 and BR06 action code

“J” to indicate the condition of materiel post-post issued 

by Army Single Stock Fund activities.

4. When requisitioning specific reparables for induction 

under Depot Maintenance Inter-Service Agreement 

(DMISA) or comparable inter-Service agreement, cite the 

supply condition code (SCC) applicable to the reparable 

item requested. Authorized SCCs include D, F, G, and Q. 

Requisitions for induction of a Product Quality 

Deficiency Report (PQDR) exhibit for warrantied 

maintenance will cite SCC Q. Refer to ADC 1176.

Clarification.

Expands 

functionality.
Enclosure 2, ADC 1176

Page 2

Location DLMS 511M Modification

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1176, Revised Procedures for Requisitioning 

under Inter-Service Maintenance Agreement (Project 

Codes 3AB, 3AD, 3BB) and Revised DLMS 832N 

Catalog Data Support for Defense Logistics Agency 

(DLA) support of Navy Fleet Readiness Centers 

(FRCs)

Identifies DLMS

Changes included in the

IC.

2. 2/LQ01/140 Add new DLMS Note to existing Code 83:

83 Supply Condition Code

DLMS Note:

1. Use to indicate the lowest acceptable condition of 

materiel when requisitioning from DRMS DLA 

Disposition Services.

2. When requisitioning specific reparables for induction 

under Depot Maintenance Inter-Service Agreement 

(DMISA) or comparable inter-Service agreement, cite the 

supply condition code (SCC) applicable to the reparable 

item requested. Authorized SCCs include D, F, G, and Q. 

Requisitions for induction of a Product Quality 

Deficiency Report (PQDR) exhibit for warrantied 

maintenance will cite SCC Q. Refer to ADC 1176.

Clarification.

Expands functionality.

Location DLMS 869F Requisition

Follow-up

i i

Reason

1. DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1176, Revised Procedures for Requisitioning 

under Inter-Service Maintenance Agreement (Project 

Codes 3AB, 3AD, 3BB) and Revised DLMS 832N 

Catalog Data Support for Defense Logistics Agency 

(DLA) support of Navy Fleet Readiness Centers 

(FRCs)

Identifies DLMS

Changes included in the

IC.
Enclosure 2, ADC 1176

Page 3

2. 2/LQ01/180 Add new DLMS Note to existing Code 83:

83 Supply Condition Code

DLMS Note:

1. Use when requisitioning from DRMS to indicate the 

lowest acceptable condition of materiel condition when 

requisitioning from DLA Disposition Services.

2. When requisitioning specific reparables for induction 

under Depot Maintenance Inter-Service Agreement 

(DMISA) or comparable inter-Service agreement, cite the 

supply condition code (SCC) applicable to the reparable 

item requested. Authorized SCCs include D, F, G, and Q. 

Requisitions for induction of a Product Quality 

Deficiency Report (PQDR) exhibit for warrantied 

maintenance will cite SCC Q. Refer to ADC 1176.

Clarification.

Expands 

functionality.

Location DLMS 832N Catalog Data Support Reason

1.

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1176, Revised Procedures for Requisitioning 

under Inter-Service Maintenance Agreement (Project 

Codes 3AB, 3AD, 3BB) and Revised DLMS 832N 

Catalog Data Support for Defense Logistics Agency 

(DLA) support of Navy Fleet Readiness Centers 

(FRCs)

Identifies DLMS

Changes included in the

IC.

2. 2/LIN01/0100 Revise DLMS Note for existing data element:

Assigned Identification

DLMS Note: 

1. Must use to identify the purpose of the transaction. Cite 

the applicable Catalog Transaction Purpose Code.

2. For DLA Disposition Services Catalog Data Support 

(Catalog Purpose Code CP) only codes AA, CC, and DD 

are applicable.

3. For Sales Contract Catalog Data Support (Catalog 

Purpose Code SC) only codes AA, CC, and DD are 

applicable. 

AA: New Catalog Record Added

CC: Catalog Record Changed

DD: Catalog Record Deleted

QU: Site Query for Catalog Record

MN: Multiple NSNs for Part Number/CAGE

NN: No record exists for NSN query

NL: No record exists for LSN query

NP: No NSN or LSN Found for Part Number/CAGE

RN: NSN Replaced

RS: Use NSN When Exhausted

Supports new procedures.
Enclosure 2, ADC 1176

Page 4

SN: NSN Substituted

NS: NSN Superseded

DN: NSN Discontinued; no Replacement

4. For SS&D Catalog Data Support, Catalog Purpose 

Code CC (Changed) may be processed as AA (Added) if 

the transaction is unmatched to an existing record in 

the receiving system. This is an authorized DLMS 

enhancement; Refer to ADC 1176.

3. 2/CTP/1700 Revise Segment level DLMS Note 2:

2. Use a second iteration of the CTP loop when needed to 

identify a net price. Use additional CTP loops when 

multiple net prices are provided by Service.

Clarifies usage.

4. 2/CTP02/1700 Revise DLMS Note for existing Code NET:

NET Net Item Price

DLMS Note:

1. Net Price for a repairable item that is unserviceable 

unit which has or will be turned in on an exchange

basis. Also referred to as exchange price for depot level 

repairables. (FLIS DRN 5235)

2. Use with Net Repair Price Phrase Code Data Service 

Code at CTP10. If multiple net prices are provide, must 

include the Net Repair Price Phrase Data Service Code.

Supports new data 

requirement.

5. 2/CTP10/1700 Open Condition Value and add DLMS Notes:

Condition Value

DLMS Note

Use for Net Repair Price Phrase Data Service Code with 

net (exchange) price (CTP02 Code NET) to denote the 

impacted Service. Cite A (Army), N (Navy), Air Force 

(F), or M (Marine Corps). Refer to ADC 1176.

Supports new data 

requirement.
Enclosure 2, ADC 1176

Page 5

6. 2/LQ01/3400 Add new Code IMC and associated DLMS Note:

IMC Item Management Code

DLMS Note:

Use with Catalog Purpose Code RC to identify the IMC. 

(FLIS Table 77). Refer to ADC 1176.

NMS Nonconsumable Item Material Support Code 

(NIMSC)

DLMS Note: 

1. Use with Catalog Purpose Code RC to identify the 

NIMSC (FLIS Table 107, DRN 0076). Refer to ADC 

1176.

2. Local code NMS is established for use in the 832N, 

version 4030. A data maintenance action will be 

submitted for establishment of NMS “Nonconsumable 

Item Material Support Code (NIMSC)” in a future 

version.

DSR Depot Source Of Repair (DSOR) Code

DLMS Note: 

1. Use with Catalog Purpose Code RC to identify the 

DSOR Code to identify the activities that are approved to 

perform depot level maintenance for the Services. Use 

multiple repetitions as applicable. (FLIS Table 117). 

Refer to ADC 1176.

2. Local code DSR is established for use in the 832N, 

version 4030. A data maintenance action will be 

submitted for establishment of DSR “Depot Source Of 

Repair (DSOR) Code” in a future version.

Supports new data 

requirement.