DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 


8725 JOHN J . KINGMAN ROAD 


FORT BELVOIR, VlRGINIA 22060-6221 


IN REPLY 

REFER TO 

DLMSO 	 July 01,2010 

MEMORANDUM FOR DLA AND NAVY PROCESS REVIEW COMMITTEE MEMBERS 

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

Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and 

Unit of Use Requirements under Navy BRAC SS&DIIMSP (SupplylFinance) (Staffed as 

PDC 366A) 

The attached ch<l:nge to DOD 4000.2S-M, DLMS, is approved for implementation. The updated 

DLMS Supplement will be posted to tbe Defense Logistics Management Standards Office (DLMSO) 

Web site http://www.dla.mil/j-6/dlmso/eiibraryffransFormatslfonnats.asp within 10 days from the 

above date for implementation planning. This change is required for an upcoming Defense Logistics 

Agency (DLA) Enterprise Business System (EBS) release to support Base Realigrunent and Closure 

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

(IMSP). 

DLA J-33 will provide procedures for the Navy BRAe SS&D/IMSP processes for inclusion in 

DOD 4000.25-M, DLMS , Volume 2. Depending on DLA's approach, the overall procedures will 

either be published under a separate ADC as a chapter to the DLMS manual. or specific procedures 

for each process may be published as addendums to the various BRAC SS&DIIMSP ADCs. 

Addressees may direct questions to the DLMSO point of contacts Ms. Ellen Hilert, email: 

Ellen.Hilert@dla.mil or Ms. Mary Jane Johnson, email Mary.JaneJohnson@dla.mil. Others must 

contact their Component designated Supply Process Review Committee representative. 

Director 

Defense LOgistics Management 

Standards Office 

Attachment 

cc: 

ADUSD(L&MR)SCI 

Finance PRC (DLA & Navy) 

Supply PRC for remaining Components 
ADC 381 

Attachment, Page 1 

 

ADC 381 

Procedures and Additional Data Content supporting Requisitions, 

Requisition Alerts, and Unit of Use Requirements under Navy BRAC SS&D/IMSP 

1. ORIGINATOR: Defense Logistics Agency, DLA J-331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/ Logistics – Multiple functions (see listed transactions in 

Enclosure 1)

3. REFERENCES: 

a. Functional Requirements for DLA’s implementation of Base Realignment and Closure 

(BRAC) Retail Supply, Storage And Distribution (SS&D)/Inventory Management and Stock 

Positioning (IMSP) Spiral 2. 

b. DLMSO memorandum dated April 08, 2010, subject: Proposed Defense Logistics 

Management System (DLMS) Change (PDC) 360A, Establishment of DLMS Supplement (DS) 832N, 

and Catalog Data Support for Navy BRAC SS&D/IMSP. 

c. DLMSO memorandum dated April 21, 2010, PDC 366, Procedures and Additional Data 

Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy BRAC 

SS&D/IMSP. 

d. AT&L Memorandum transmitted April 21, 2010, subject: Proposed Changes in support 

of Navy BRAC Inventory Management and Stock Positioning (IMSP) Spiral II. This memo 

documents ADUSD(L&RM)SCI direction provided to DLA and Navy authorizing immediate 

implementation of this DLMS change. 

4. REQUESTED CHANGE: 

a. Description of Change: This change establishes additional data elements on multiple 

DLMS transactions supporting the DLA interface with Navy Shipyards (NSY) and Fleet Readiness 

Centers (FRCs) operating under the Navy-DLA BRAC 2005 SS&D concept of operations (CONOPS). 

This is one of a series of change proposals designed to support implementation of the Navy-DLA 

BRAC requirements. Significant revisions/updates subsequent to the original PDC 366A staffing

are identified by yellow highlighting. DLMS Supplement mapping detail not previously 

available is included in this document. This document reflects agreements resulting from the 

Distribution Standard System (DSS) Critical Design Review (CDR).

(1) Requisition Alert. This proposal establishes a new business process referred to as the 

“requisition alert” (previously referred to as Navy demand signal) which is basically an unfunded 

requisition providing advance notification of a requirement. DLA will use the requisition alert for 

stock positioning/procurement action to ensure that materiel will be available for immediate issue 

when subsequently requisitioned by the Navy Shipyard (NSY) or Fleet Readiness Center (FRC). This 

business process uses existing DLMS transactions but requires a new DLMS data element to 

distinguish this function. In addition, many unique supporting data elements are being added to the 

transaction exchange. The new data elements will also be made available in the standard DLMS 
ADC 381 

Attachment, Page 2 

requisition format, and may be perpetuated from the requisition alert in accordance with the business 

process which varies by NSY or FRC. The Requisition Alert functionality includes associated 

submission of modifications, follow-ups, and cancellations. 

(2) Materiel Identification. This proposal also establishes requirements to support the 

new categories of materiel identification as proposed for the Navy BRAC support under PDC, 360A 

Establishment of DS 832N, Catalog Data Support for Navy Base Realignment and Closure BRAC 

SS&D)/IMSP (reference 3.b). The cataloging data will include two new methods of materiel 

identification which are incorporated in this proposal. Both categories are identified by a Local Stock 

Number (LSN). 

(3) Unit of Use LSN. There are items cataloged as an NSN within the DoD/Navy 

systems, but which will be issued to the Navy in a unit of use which is less than Federal Logistics 

Information System (FLIS) unit of issue. These items will be assigned a unique LSN to be used 

internally within DLA systems. DLA will maintain inventory balances, generate issues, and post 

inventory adjustments against the LSN material number. These LSNs will also reflect a unit of use 

and not the FLIS unit of issue. The Navy will maintain balances, generate issues and requisition alerts 

and post all subsequent actions against the actual NSN. DLA-generated DLMS transactions will carry 

both the unit of use LSN and the FLIS NSN. An indicator in the beginning segment of the transaction 

is often used to draw attention to this form of materiel identification. 

(4) Part Numbered Item LSN. There will be items cataloged as an LSN, for which the 

CAGE/part number combination does not have an identified NSN. Due to system limitations 

associated with the material number field within the NSY Material Access Technology (MAT) 

application and the FRC Material Resource Planning (MRP) II application, the CAGE and part number 

combination cannot be used to identify these items in requisitions and subsequent transactions. 

b. Background: As a result of the 2005 BRAC decision, retail supply, storage and distribution 

functions and associated infrastructure supporting the Navy industrial/maintenance sites will transfer 

to DLA. The Navy sites consist of 2 NSYs and 3 FRCs. The intent of the directive is to significantly 

improve combat effectiveness while reducing costs by developing a world-class, cost-effective supply 

chain focused on readiness; taking every opportunity to eliminate waste, reduce touches, reduce cost, 

and improve readiness. DLA will be the material provider for all standard and non-standard, DLA 

managed and non-DLA managed, consumable material required for fulfillment of industrial activity 

(IA) requisition alerts by re-warehousing actions at a collocated DSS depot, redistribution from within 

the Distribution Standard System (DSS) network, requisitioning from another Service/Agency, 

material purchases both onsite, at DSCR/DSCC/DSCP or local manufacture to support the BRAC 

designated Industrial Activity’s operation, maintenance, and production. The IA will retain its 

industrial make/buy work planning decision responsibilities, as well as requisition alert creation 

responsibilities for planned and emergent material requirements determined via the material planning 

tools used at these sites. The IA will generate a trigger to DLA, referred to as a requisition alert, 

indicating the need for materials. This requisition alert will be unfunded and include all current data 

elements on a MILSTRIP requisition and the requested additional data elements. DLA will apply 

unique processing logic based on these additional data elements. Once a maintenance job is scheduled 

for execution to commence, the IA will submit funded requisitions for DLA owned materiel positioned 

at the IA worksite as a result of the previously submitted unfunded requisition alerts. 

c. Detailed Procedure: 
ADC 381 

Attachment, Page 3 

(1) The IA will perform the material determination within the local planning system. Once 

requirements are determined, the IA site will attempt to source the requirement from locally owned 

stock (e.g., Future Use Material). 

(2) When assets are not available locally to fulfill the entire required quantity, the IA 

system will determine if the item required is a production consumable or a Depot Level Repairable 

(DLR), Nuclear Support Consumables, or Navy Program Owned Material (even COG). Program 

Owned Material is supplied by Hardware System Commands to perform alternation or configurations 

changes to weapon systems.

(3) If the item is a DLR, Nuclear Support Consumables, or Program Owned Material, then 

a funded passing order (511R, MILSTRIP A3A) will be generated and forwarded to DAASC for 

transmission to the designated source of supply, and a copy will be provided to DLA (SMS) based on 

the “party to receive copy” information contained in the 511R.1

(4) If the item is considered a production consumable item, then an unfunded requisition 

alert (511R with a requisition alert qualifier, MILSTRIP A0A/A0D) will be generated, with RIC-To 

SMS. DAAS will route all requisition alerts to DLA whether or not DLA is the Integrated Item 

Manager for the item requisitioned. If only partial quantity is available under a previously filled order, 

the unfunded requisition alert identified as a referral order (511R, MILSTRIP A4A/A4D) will be 

suffixed to retain association with the original document number. 

d. DLA will evaluate the IA requisition alert requirements to determine the appropriate 

method of fulfillment including expediting outstanding material fulfillment actions, reassignment/rewarehousing of unprotected stock at local site, redistribution from within the DSS network, 

requisitioning to another Service/Agency, or new procurement. All actions against the requisition alert 

will be relayed back to the originating activity with a Supply Status, 870S2

. 

(1) When material is available locally, DLA will notify DSS to protect/re-warehouse 

material in support of the FRC or NSY request using a DLMS Warehouse Service Request, 940S, 

Service Performed Code 7. DSS will reply with a 943A, Warehouse Service Advice, certifying when 

action is complete.3

(2) When there are no assets available at the co-located site, the DLA Enterprise Business 

System (EBS) will backorder the requisition alert and send Supply Status code to the requesting IA 

site. 

(a) For NSY orders, EBS will then send a DLA funded requisition to Navy ERP 

for a search of Real-time Reutilization Asset Management (RRAM)4

 system free issue assets prior to 

 

1

 Refer to PDC 404, Transaction Copies Required for DLA Support of Navy BRAC SS&D/IMSP DLRs, Navy ProgramManaged Materiel, and Nuclear Consumable Support Materiel, April 14, 2010. 2

 Refer to PDC 406, New and Revised Supply Status Procedures to Support “Virtual Receipt” and Requisition Alert 

Processes under Navy BRAC SS&D/IMSP, April 20, 2010. 

3

 Refer to PDC 384, New DLMS Supplement (DS) 940S, Warehouse Service Request (for Materiel Protection/ReWarehousing, Staging, and Picklist/Callout), New DS 943A, Warehouse Service Advice, and Associated Procedures under 

Navy BRAC SS&D/IMSP, April 20, 2010. 

4

 The Navy RRAM application provides a mechanism for automated requisitioning of residual (excess) assets. NSY sites 

(but not FRCs) are entitled to RRAM support under Navy business rules. 
ADC 381 

Attachment, Page 4 

obtaining required materiel through other fulfillment processes. 5

(b) For both FRC orders and any unfilled NSY orders subsequent to the RRAM 

asset search, when assets are available within the DLA network EBS will generate a Redistribution 

Order to move the material to fulfill the request. When assets are reported received at the requesting 

NSY or FRC collocated DSS depot site, EBS will re-warehouse and protect the material against the 

open requisition alert. 

(c) When no assets are available within the DLA network, EBS will obtain 

material through other fulfillment processes (e.g., direct vendor delivery, expedited purchase, other 

Service requisitioning). EBS will send the prepositioned materiel receipt document (PMRD) to the 

receiving DSS IA depot reflecting the requisition alert document number, JO and KO as applicable for 

NSY and FRC sites for use by DSS to protect these assets. 

e. DLA will receive store, issue, and inventory items in support of the IA site maintenance 

mission. Once material is in DLA ownership the material will be protected from global distribution to 

other DLA customer unless specific business rules are met on the non-industrial customer requisition. 

The protection will be done for the NSY sites using the document number and JO provided on the 

requisition. Material positioned for the FRCs will be protected using a Purpose Code E. Refer to 

(Enclosure 2) for breaching rules of protected stock. Note: Issue Priority Group (IPG) I 

requirements from other customers may penetrate protected stock; for FRC sites it will be 

systemic, at the NSY sites, because of the tie to a specific job, it will require a manual release.

f. Navy funded requisitions will be submitted EBS (RIC-SMS) for both DLA and non-DLA 

managed production consumables at the time the IA determines when a job is scheduled for execution. 

(1) NSY sites will generate a funded requisition to DLA reflecting a new customer 

requisition document number, and the previously submitted requisition alert document number, JO and 

KO. 

(2) FRC sites will generate a funded requisition to DLA reflecting a new customer 

requisition document number, but the previously submitted requisition alert document number will not 

be included. 

(3) NSY and FRC funded requisitions will contain the following requisitioner DoDAACs. 

DAAS will route funded Navy orders with these DoDAACs and a RIC-To of SMS to DLA whether or 

not DLA is the Integrated Item Manager for the item requisitioned. 

 FRC EAST Cherry Point N65923 

 FRC SE, Jacksonville N65886 

 FRC SW San Diego N65888 

 PHNSY & IMF Pearl Harbor N32253 

 PNSY Portsmouth NH N39040 

 NNSY Norfolk N42158 

 PSNS & IMF Puget Sound N4523A 

 

5

 Refer to PDC 385, Procedures and Assignment of Navy DODAACs to DLA for Use on DLA Requisitions to Military 

Service/GSA SoSs in Support of Navy IAs under BRAC SS&D/IMSP, April 15, 2010. 
ADC 381 

Attachment, Page 5 

g. DLA will react to the funded request for material and the unique data elements (see table 

below). 

(1) EBS will determine if protected assets are available at the co-located site for NSY 

request by matching to the previous requisition alert document number, applicable suffix code and JO 

before generating a material release order (MRO) to DSS. The match is done to ensure protected 

material is released to the appropriate job only. 

(2) FRC request will not require validation of original requisition alert document numbers 

prior to release of materiel, but EBS will search Purpose Code E assets for release prior to Purpose 

Code A. 

(3) For both NSY and FRC sites, when no protected assets are available at the co-located 

site EBS will search for non-protected assets at the same co-located site. When no unprotected assets 

are at the co-located site the DLA network will be searched for available assets and source according 

to current EBS sourcing logic. If no assets are available, the funded request will be backordered. 

Supply Status will be provided as applicable. 

(4) In instances when the material supporting a funded order is issued from DSS through 

the current post/post process, the Requisition Alert Document Number, Job Order and Key Operation 

Number must be included on the 511R (with the post-post directed MRO indicator) submitted to the 

material owner. The material confirmation will also reflect the same data elements. 

h. For both unfunded requisition alerts and funded Navy requisitions submitted to DLA EBS 

(RIC SMS) there will be instances when the requesting activity requires a quantity in less than the 

standard unit of issue established on the FLIS record for a specific NSN. In these instances, the 511R 

requisition will have a beginning segment code indicating it is a unit of use requisition for the unit of 

use measure and quantity. 

(1) Only the FLIS NSN is reflected on unit of use requisitions submitted by Navy NSY or 

FRC. However, the unit of use indicator will be included. DLA-provided transactions pertaining to 

requisition alert or funded requisition (e.g., supply status, material release order) will include the unit 

of use indicator and both the FLIS NSN and unit of use LSN. Exception: The Navy obligation is 

established at the NSN for calculating the unit of use price, although the interfund bill will reflect the 

LSN (without cross-reference to the NSN). 

(2) When a unit of use requisition alert or Navy funded requisition quantity can be 

converted (quantity requested is a multiple of the FILS unit of issue) to a full unit of the FLIS standard 

unit of issue, EBS will generate a Supply Status reflecting BG status code to the requesting site. The 

requisition alert or funded request will reflect the NSN and not the unit of use LSN for this request. 

(3) For post-post directed MROs, if the issue is for other than the FLIS standard unit of 

issue, DSS logic will ensure the material has been previously re-identified to an applicable LSN. 

When the transaction is sent to the material owner the correct unit of use qualifier, LSN and NSN will 

be reflected as applicable. If the material is required in the unit of use and has not been re-identified 

from the NSN, operational procedures for the DLA personal will allow a manual process to re-identify, 

notify the material owner with 947I, D8K and D9K, and issue the material. 

i. Requisition Alert Modification: There may be instances when a Requisition Alert has not 
ADC 381 

Attachment, Page 6 

been completed in EBS and the NSY site requires the modification of the JO or KO numbers, when 

this occurs the use of 511M, Request for Modification will be submitted to EBS from MAT. Staffing 

Note: A list of modifiable data elements will be provided for inclusion in the ADC procedures. 

DLMSO has tentatively identified modifiable data elements in the DLMS Supplement table notes for 

the 511M, Requisition Modification, shown in Enclosure 7. 

(1) If the modification is successful a supply status with BK status code will be returned to 

the requesting site. If the modification is unsuccessful a supply status with B2 status code will be 

returned to the requesting site. 

(2) If the requisition alert has been completed (material has been receipted and protected) 

the NSY site will submit an 846A Request for Asset Re-identification to modify or delete requisition 

alert document number or JO or KO.6 

(3) If the document number in the request does not exist within EBS, this request will be 

treated as an original request and processed through current logic for requisition alerts. 

j. Requisition Alert Cancellation: If a request for cancellation is received for an unfunded 

requisition alert, EBS will provide immediate BQ status to the Navy and when required take additional 

actions to attempt to cancel the unneeded material being procured or requisitioned from another 

Service/Agency. There are several checks to be applied when determining if the cancellation request 

can be accomplished. 

(1) If the requisition alert is currently on backorder the request for cancellation will be 

successful and Supply Status with BQ status will be provided to the FRC or NSY under status 

distribution rules. No further EBS action required. 

(2) If the requisition alert resulted in a new procurement action, BQ status will be returned 

to the FRC or NSY under status distribution codes. If the procurement action is a direct vendor 

delivery (DVD), EBS will attempt to cancel the procurement based on MILSTRIP cancellation rules. 

If the cancellation is successful, the PMRD will be cancelled. If the DVD cannot be cancelled, EBS 

will update the protection table to remove the reference to the document number for NSY sites and 

amend the PMRD to remove reference to requisition alert document number, JO and KO. When the 

material is receipted, it will be available for global distribution, no protection will be applied. 

(3) If the requisition alert resulted in a requisition to another Service/Agency, EBS will 

provide BQ status to the FRC or NSY under status distribution rules and then generate a cancellation 

request to other Service/Agency based on MILSTRIP cancellation rules as applicable. The PMRD 

will be amended to remove reference to the requisition alert document number, JO and KO. If any 

material is receipted it will be available for global distribution and no protection will be applied. 

k. Requisition Alert Inquiry (869A, AF_) Process: If a Requisition Inquiry (869A, AF_) is 

received, EBS will determine if the request is for an unfunded requisition alert based the requisition 

alert follow-up qualifier in the beginning segment of the transaction. There are different scenarios that 

may occur when determining response to the customer. 

(1) If the document number in the request does not exist within EBS, Supply Status with 

BF status code will be returned to customer. 

 

6

 Refer to PDC 376, Revise DLMS Supplement (DS) 846A, Asset Reclassification to Support BRAC SS&D/IMSP 
ADC 381 

Attachment, Page 7 

(2) If the follow-up is by document number only or by document number and suffix, but 

only the document number matches an existing record within EBS, then supply status will be provided 

on the entire quantity for document number, e.g., document number with Suffix Code A, quantity of 5, 

document number with suffix code B, quantity of 2, supply status will be provided for each suffix 

code. 

(3) If the follow-up is by document number and suffix which match an existing record 

within EBS, then EBS only provides status for that suffix. 

(4) For follow-ups matching EBS records, EBS will provide the current status and 

estimated shipping date (ESD) based upon MILSTRIP follow-up response rules. 

(a) If the status code is equal to PQ (Protected Quantity), supply status is 

generated. 

(b) If status code is equal to BB and the ESD is not past due, the status and ESD 

will be returned. 

(c) If status code is equal to BB and the ESD is past due, EBS will determine 

new ESD based on due-in delivery dates, update the order within EBS with the new ESD and generate 

status to customer with updated data. 

(5) EBS will generate subsequent follow-up actions to other service managers and update 

with the requisition alert with any supply status received as a result of the DLA follow-up action. 

l. Requisition Alert Follow-up (869F, AT_) Process: If a Requisition Follow-up (869F, 

AT_) is received, EBS will determine if the request is for an unfunded requisition alert based on the 

requisition alert follow-up qualifier in the beginning segment of the transaction. 

(1) If the document number in the request does not exist within EBS, the request will be 

treated as an original request and processed through current logic for requisition alerts. 

(2) If the document number in the request is found the request will follow the steps outlined 

for the 869A, AF_. 

m. Post-Post Scenarios. 

(1) In instances when the material supporting a funded order is issued from DSS through 

the current post-post process, the Requisition Alert Document Number, Job Order and Key Operation 

Number must be included on the 511R (with the post-post directed MRO indicator) submitted to the 

material owner. The material confirmation will also reflect the same data elements. 

(2) For post-post directed MROs, if the issue is for other than the FLIS standard unit of 

issue, DSS logic will ensure the material has been previously re-identified to an applicable LSN. 

When the transaction is sent to the material owner the correct unit of use qualifier, LSN and crossreference NSN will be reflected as applicable. If the material is required in the unit of use and has not 

been re-identified from the NSN, operational procedures for the DLA personal will allow a manual 

process to re-identify, notify the material owner with 947I, D8K and D9K, and issue the material. 

n. Other Transactions. There are many transactions which have a requirement to identify, 
ADC 381 

Attachment, Page 8 

when applicable, the unit of use indicator and the unit of use LSN with its associated NSN, for 

example: 

(1) Prepositioned Material Receipt Document (PMRD), 527D, generated from NSY or 

FRC to DSS in support of material returns to DLA. 

(2) Materiel Returns Supply Status (870M) generated from DLA to the NSY or FRC, as 

credit is determined. 

(3) Receipt (527R) generated by DSS. 

(4) Issue (867I) generated by DSS. 

(5) Materiel Receipt Acknowledgement (527R) generated by the Navy IAs. 

(6) Inventory Related Transactions. As a result of DSS maintaining inventory balances 

at the unit of use level against the LSN assigned for this purpose any Location Reconciliation Request, 

846R, Physical Inventory Reports, 846P, and Inventory Adjustments, 947I, will also reflect a unique 

qualifier indicating when the transaction(s) is related to the unit of use LSN with the NSN as a cross 

reference. 

5. DLMS Supplement Updates: 

a. The table below (beginning on attachment page 9) identifies the additional data content in 

the relevant DLMS transactions although the primary focus is on the requisition. The requisition 

modification and the requisition follow-up may be used as requisitions when the original requisition 

alert is not available in supply source records, and, therefore, all elements associated with the original 

Requisition Alert is carried in each of these transactions. These data fields will be available for both 

the standard requisitioning procedures and for the requisition alert. Subsequent inclusion of these data 

elements in other DLMS transactions is required per Enclosure 1, and shown in detail with applicable 

DLMS notes in the DLMS Supplement Tables included in Enclosure 7. 

b. Modification. The new data elements identified, excluding quantity and unit of use, below 

are modifiable on the requisition modification (subject to verification in the ADC).

c. Unit of measure. There will be instances when the requesting activity requires a quantity in 

less than the standard unit of issue established on the FLIS record for a specific NSN. There will only 

be one unit of use established per NIIN, to be used for all Navy BRAC SS&D sites as applicable. The 

requesting IA will requisition by NSN, but will include the unit of use identifier indicating the quantity 

and unit of measure are for less than the standard unit of issue. This qualifier will be included on all 

subsequent transactions for the requisition alert or funded requisition such as supply/shipment status 

and material release order/confirmation. 

(1) Transactions reflective of a quantity less than unit of use are not reflective of the FLIS 

unit of issue and will contain an indicator for receiving system to process as a unit of use. 

(2) Unit of use values will be within the common set of values for DoD units of issue. The 

equivalent X12 value will be passed in the transaction per existing DLMS requisitioning procedures. 
ADC 381 

Attachment, Page 9 

d. Concept for Use of Specific Qualifiers for Document Numbers. All transactions will 

have a reference segment with the TN qualifier for the transaction document number and when 

required, transactions will also carry a second iteration of the of the reference segment with qualifier 

PWC for the requisition alert document number. That is, if both the funded and unfunded document 

numbers are carried in the same transaction, the unfunded (alert) document number will be specifically 

identified. If only the unfunded document number is carried in any transaction, the unfunded 

document number will be carried in the standard document number field using TN qualifier (even 

thought this is the requisition alert document number). However, when a Warehouse Service Request 

(e.g. staging request) submitted prior to a funded requisition the request will have only one document 

number, the requisition alert document number. 

(1) An example of this concept is applicable in the original requisition alert with the 

requisition alert identifier. This requisition alert will only have a single transaction document number 

(N9 segment with qualifier TN). Supply and shipment status, follow-ups, cancellation, etc., against the 

original requisition alert will also only have the single transaction document number. Since the PMRD 

and Distribution Depot receipt will cite the primary document number, which is identified in the N9 

segment with qualifier TN, there will need to be a second N9 iteration with qualifier PWC that 

identifies the requisition alert document number/suffix associated with the Navy requirement. 

(2) When a funded order is submitted subsequent to the alert by the NSY, the funded order 

will carry two N9 segments for document numbers: one with qualifier TN for the standard transaction 

document number of the funded requisition, and one with qualifier PWC for the requisition alert 

document number. Since subsequent supply and shipment status, follow-ups, cancellation, etc., 

against the funded requisition will contain both the standard transaction document number and the 

original alert document number two reference segments will be used (citing both TN and PWC 

qualifiers). 

(3) DLA does not see a need for the Navy (or other Services) to return any of the new data 

elements, since EBS will have the data internally cross-referenced to outbound transactions. 

Component applications should not fail DLA transactions due to this content. 

e. New and revised DLMS data content is discussed in the table below. 

f. Enclosure 1 lists the specific transactions addressed by this change proposal, and provides a 

matrix indicating that additional data elements are being added to each. This matrix also includes 

some cross-referencing to other Navy BRAC SS&D IMSP DLMS Changes. 

g. Enclosure 2 provides the business rules for breaching of protected stock.

h. Enclosure 3 provides updates to the data element Reason for Requisitioning, which was 

previously unused, but was available as a DLMS enhancement. 

i. Enclosure 4 provides updates to the data element Delivery Priority Code to support a new 

use under BRAC requirements. 

j. Enclosure 5 provides updates to the data element Utilization Code to support a new use 

under BRAC requirements. 

k. Enclosure 6 provides flow diagrams for applicable to this proposal. 
ADC 381 

Attachment, Page 10 

l. Enclosure 7 shows the DLMS Supplement (DS) revisions with specific content to support 

this change. For actual DLMS transaction formats refer to the DLMSO internet site eLibrary under 

DLMS Supplements to Federal Implementation Conventions - Transaction Sets, available at: 

http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp. 

m. Enclosure 8 identifies comments and concurrences subsequent to staffing of the proposal. 

n. Enclosure 9, lists DLMS changes supporting the Navy BRAC SS&D/IMSP CONOPS. 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

1 Requisition Alert 

Indicator 

Code to distinguish the requisition alert/modification/ 

cancellation/follow-up from the standard requisitioning 

transactions. Staffing Note: In the 511R, used with 

Transaction Type Codes for the Requisition (Code AO) or the 

Requisition Referral Order (Code BN), when suffixing a 

previous requirement is applicable. Note: Referral Order apply 

to NSY sites only on suffixed Requisition Alerts. 

1 

2 Unit of Use Indicator Code used to indicate that the transaction quantity and unit of 

issue are associated with a unit of use. The requisition and 

requisition alert use this identifier to correctly interpret the 

requirement since the only materiel identification will be the 

NSN. However, follow-on transactions applicable to unit of 

use will normally contain both the NSN and LSN. 

2 

3 Unit of Use The unit of measure representing the lowest level of use to be 

stored, inventoried, and sold (i.e., a unit of measure less than 

the standard FLIS cataloged unit of issue). The code set for the 

unit of use will be within the common set of values for DoD 

unit of issue. 

2 

 4 Party to Receive Copy7 Used to identify the organization to be provided a copy of this 

transaction. 

3 

5 Materiel Identification: 

National Stock Number 

(NSN) 

or 

Local Stock Number 

(LSN) 

The materiel identification is the identification by which the 

materiel is receipted, stored, inventoried and sold. There will 

be two material identifiers in this category: 

 

This LSN is used to identify either materiel which has been 

broken down to the lowest level of use to be stored, inventoried 

and sold (a unit of measure which is less than the standard 

cataloged unit of issue) or an item for which no NSN has been 

assigned to the CAGE/part number combination. The LSN 

NSN or 

LSN = 13 

MTC Tag 

No. = 32 

 

7

 PDC 404, Transaction Copies Required for DLA Support of Navy BRAC SS&D/IMSP Depot Level Reparables (DLRs), 

Navy Program-Managed Materiel, and Nuclear Consumable Support Materiel 
ADC 381 

Attachment, Page 11 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

or 

Materiel Control Tracking 

Tag Number8

value will normally be systemically assigned by EBS, but may 

also be a number assigned by the Navy and adopted by DLA 

when the Navy site comes under BRAC procedures. 

Navy requisitions for unit of use requirements carry only the 

NSN; however, subsequent transactions will normally carry 

both the NSN and LSN. 

LSN construct will depend upon the use of the number: 

 a) 5975 LL 789 1234 – The use of “LL” in the NATO field 

of the LSN indicates the number was assigned within MAT or 

MRPII prior to IMSP implementation. 

 b) 5975 N* 123 6789 – The use of “N*” in the NATO field of 

the LSN indicates the number was systemically assigned within 

EBS for an item which has no valid NSN assigned in FLIS. 

 c) 5975 U0 909 4321 – The use of “U” in the first position of 

the NATO field indicates the LSN was systemically assigned 

within EBS in support of a unit of use requirement. 

The materiel control tracking tag (MCT Tag) number is used to 

identify the materiel (e.g. ripout or courtesy storage) where no 

other materiel identification will apply. This type of materiel 

identification is not applicable to the requisition processing. 

The MCT tag suffix may be embedded in the MCT Tag number 

data field. May include special characters. 

6 Job Order Number Used at by NSY maintenance activity identifying a particular 

package of work. The first two positions are the Work 

Category Number, the next three positions are the Availability 

Number, and the remaining five digits make up the Work 

Breakdown Structure. 

Requisition alert document number, suffix code and JO will be 

key data elements to releasing issues at Naval Shipyards. 

Alphanumeric. Required for both funded and unfunded 

requisitions from NSY sites. 

10 

 

8

 Refer to PDC 393, Document Process for Material Control Tracking (MCT) Tag Number and Revise DLMS 527D, 527R, 

867I, 940R, and 945A in Support of Navy BRAC SS&D/IMSP 
ADC 381 

Attachment, Page 12 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

7 Key Operation Number The logical division of a Job Order which may be scheduled to 

be performed without significant interruption, and which can be 

closed out to further charges upon completion. This value will 

be a reference field on all transactions. 

 

Alphanumeric. Required for both funded and unfunded 

requisitions from NSY sites. 

3 

8 Requisition Alert 

Document Number 

Document number reflected on the initial requisition alert 

which is an unfunded request used only by the Navy in support 

of the DLA-Navy BRAC interface. 

The requisition alert document number will only be uniquely 

identified when used in combination with another document 

number; otherwise ,the requisition alert document number may 

be identified by context (that is by its use in a requisition alert 

transaction). 

This field will be used on both Funded requisitions and 

unfunded requisition alerts by NSY sites. 

This field will be used on unfunded requisition alerts only by 

FRC. 

14 

9 Requisition Alert 

Document Suffix Code 

The suffix code reflected on the original requisition alert. It is 

used only when the requisition alert is created as a variant of the 

511R Requisition Referral Order (MILSTRIP A4_). Prior to 

the NSY exiting the request from their system they search for 

local Navy owned assets if found the same document number is 

used for the remaining quantity to DLA but a suffix is assigned. 

This allows them to reflect the entire quantity for a material and 

availability on a single document number. The requisition alert 

document suffix will only be uniquely identified when used in 

combination with another document number; otherwise it may 

be identified by context (i.e., by its use in a requisition (referral) 

alert transaction). 

The Requisition Alert Document Number, Requisition Alert 

Suffix Code, and JO will be key data elements to releasing 

issues at NSY. 

1 
ADC 381 

Attachment, Page 13 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

10 Reason for Requisitioning 

Code 

Code used to identify the use of the material requirement. 

Metrics may be measured based on the code value. 

The following will be used on funded requisitions and 

Requisition Alert Transactions for either FRC or NSY sites 

D - Direct Material Inventory (DMI) 

E - End use delivery 

M - Mission Support Material (MSM).item 

S - Nuclear shop delivery 

U - Rip out/courtesy storage (not applicable to requisitioning 

process ) 

This field may be used on both Funded requisitions and 

unfunded requisition alerts by NSY sites. 

This field will be used on funded requisition only by FRC. 

 

FRC will use only ‘E’ and there is no metric associated with its 

use. 

Note: Requires update to existing DLMS definition established 

as a placeholder for a future enhancement to include Navy use 

(Enclosure 2). 

1 

11 Requirement Churn 

Reason Code 

Code used as a basis for metrics, tracking request for material 

after the start of availability at a shipyard. The churn code will 

be used to track an agreed to strategic metric between NSY 

sites and DLA. 

Churn is defined as all material orders required by the mechanic 

to complete planned work above what was originally identified 

during the pre-planned process, ordered and delivered after the 

start of the availability. The causes of churn vary widely and 

are tracked by 15 corporate established codes. This code 

allows measuring to ensure the correct material is being stocked 

on hand within each shipyard. This data element does not apply 

to facilities, cranes, service project or nuclear item request. 

9 Default for pre-planned items 

G Growth 

N New Work 

A Additional Task Group Instructions (TGI), material 

required 

T TGI omitted material 

S Substitution of ordered material 

1 
ADC 381 

Attachment, Page 14 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

M Mistake (wrong material ordered) 

L Lost material 

D Material Damaged/unusable 

W Wrong material delivered 

R RDD unacceptable 

Q Quality Assurance (QA) Inspection reject 

X Expired Shelf life 

E Empty consumable Bin material 

C Consumable material purchase or replenishment 

U Un-ship/Rip out material called down for re-install 

Applicable to both funded and unfunded requisitions from NSY 

sites. 

12 Delivery Priority Code Code used by NSY sites to reflect material has an urgency of 

need within the maintenance shop and must be delivered within 

one hour of receipt of the issue request. Value will be X (1 hour 

issue) when applicable. 

DSS has a unique indicator which can be set to exclude 

additional cost for delivery priority at the BRAC SS&D sites. 

Applicable to funded requisitions at NSY sites. 

Note: Requires update to existing DLMS definition to include 

Navy use (Enclosure 2). 

 

1 

13 Quality Inspection Code Code indicating the level of quality inspection to which the item 

must be procured and inspected. Applicable to both unfunded 

and funded requisitions at NSY and FRC sties. 

Referred to as Quality Inspection Code at NSY sites. 

Standard Nuclear Inspection Codes: 

 Code Meaning 

 A - Nuclear level 1 

 C – Non-Level Nuclear (NLN) 

 G - Nuclear Assigned Materiel (NAM) 

 D -No Inspection Required (used at PNSY and not NNSY) 

 E - No Inspection Required (used at NNSY and PNSY) 

Standard Non-Nuclear Inspection Codes: 

 Code Meaning 

1 - Level 1 material 

2 - Level 2 CIM (Controlled Industrial Material) 

3 - Level 3 Local Technical Inspection 

1 
ADC 381 

Attachment, Page 15 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

4 - No inspection required 

 

Notes: 

The FRC will use codes 3 or 4. 

NAM is defined as non-shipbuilding materiel used to assist 

accomplishment of Naval nuclear work, but is not Naval 

nuclear material. 

14 Shop Store The number that identifies the shop store designated to carry 

Mission Support Material for distribution to End-Use shops and 

other customers. 

Applicable to both funded and unfunded requisitions at NSY 

sties. 

Note: Shop Store is mapped in the DLMS transaction to the 

data field that was previously defined for Shop Service Center 

by ADC 284A for use by the Air Force. Its use is expanded by 

this DLMS change. 

Max 3 

15 Picklist Control Number Control number assigned to identify a specific job for which 

materials are being requisitioned or assembled together in 

support of the FRC or Shipyards. 

Reflected on FRC funded requisitions only. 

NSY will be reflect on both funded and unfunded requisitions. 

31 

16 Utilization Code This code provides receiving clerks immediate identity of 

nuclear related materiel code 2305 material and to invoke 

manual process of contacting Nuclear Engineering Department 

for delivery instructions. This value will be reflected in the 

first digit of the serial number in the document number as well 

as in the utilization code. 

V - Routine Contact 

Z - Immediate Contact Required 

Staffing Note: Utilization Code is an existing DLMS data 

element intended to eliminate embedded data content as a 

future DLMS enhancement. Usage is expanded by this change. 

See Enclosure 5. 

1 

17 Delivery Location Location to which materiel is to be delivered. May include 

building number. 

30 

18 Customer Order 

Acceptance Record 

Identifies Customer Order Acceptance Record (COAR) 

applicable to Job Order Number. The COAR will reflect the 

Work Category Number (position 1-2) and the Availability 

Number (position 3-5). It represents the customer order for 

which reporting is required Alpha Numeric field. 

5 
ADC 381 

Attachment, Page 16 

New or Modified Data Content 

# 

Data Content Usage Notes/Definition Field Length 

19 Work Order Number This is a key control number for an MRPII document that 

details and maps work performed and remaining work to be 

performed for a product being repaired or manufactured. Used 

by FRC only. 

10 

(max 10 - 

min 8) 

m. Alternatives: None identified 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Enterprise Business System (EBS), Material Access Technology (MAT), 

Material Resource Planning (MRP) II and Distribution Storage System (DSS), will be able to comply 

with DLMS standards for the BRAC IMSP Spiral 2 process

b. Disadvantages: Asset visibility obscured by non-standard materiel identification and unit 

of use. Re-engineering is required by trading partners. 

7. IMPACT: 

 a. Planned Implementation Date: December 2010. 

 b. Policy Coordination: 

 (1) On March 11, 2010, the Assistant Deputy Under Secretary of Defense, Logistics and 

Materiel Readiness, Supply Chain Integration, ADUSD(L&MR)SCI, authorized DLA and Navy to 

proceed with development of procedures, including the cataloging data exchange, supporting 

requisitioning and materiel storage at less than the unit of issue and for requisitioning of non-NSN 

items using a local stock number for identification. Due to the policy implications of this PDC, the 

concept was presented to ADUSD(L&MR)SCI for approval subsequent to initial staffing. In response, 

ADUSD(L&MR)SCI recommended a review of the unit of issue for materiel currently issued to the 

Navy at unit of use to ensure that unit of use is not the more accurate unit of issue for these items. 

Should FLIS cataloging updates result from the review, significant savings might be realized. 

ADUSD(L&MR)SCI also identified a requirement that an NSN must be assigned when the items have 

three or more demands in one year (applicable to Local Stock Numbers cataloged for non-NSN partnumbered materiel. Although approving the unit of use concept in order to meet the IMSP timeline, 

ADUSD(L&MR)SCI also requires exploration of an enterprise solution for future use. 

 (2) Requires update to supply chain management policy to recognize requisitioning and 

storage using unit of use in support of IMSP. Requires update to supply chain management policy to 

recognize the requisitioning of part numbered items cataloged to a local stock number (vice 

submission of part numbered requisitions) under IMSP. 

 (3) Requires methodology for ongoing evaluation of inventory levels where materiel was 

purchased by DLA to satisfy a requisition alert. This review is to ensure inventory does not 
ADC 381 

Attachment, Page 17 

accumulate due to lack of a Navy funded requisition or delayed cancellation of the requirement. 

 c. Integrated Data Environment (IDE)/Global Transportation Network (GTN) 

Convergence (IGC). This change is a new business process and impact must be assessed by 

developers. 

 d. Asset Visibility (AV) Application (Defense Logistics Information System). Assets 

identified by non-standard material identification types will not be recognized by third parties in AV 

unless the cross-references established by the DLMS 832, Catalog Data Support, transaction are 

known to AV. 

 e. Logistics Response Time(LRT)/Customer Wait Time (CWT). No corresponding updates 

have been made to LRT/CWT to identify and properly handle requisition alerts and IA site funded 

requisitions which will cause distortion of metrics. 

 f. Prepositioned Materiel Receipt Document (PMRD) and Wide Area Workflow 

(WAWF) Destination Acceptance: DSS WAWF functionality is currently being expanded to 

facilitate WAWF acceptance for direct vendor delivery (DVD) shipments to co-located Distribution 

Depot customers. This functionality requires a PRMD in order to link the DVD document number to 

the WAWF Advance Shipment Notice (856). When materiel is ordered from DLA without prior 

requisition alert, DLA will not provide a PMRD. It is believed that the Navy will not provide a PMRD 

in this situation when materiel is intended to be receipted and stored within the DD under Navy 

ownership. Additionally, in the situation where the funded requisition without prior requisition alert 

is not directed to DD storage (End Use Code E), there would not be PMRD applicability; however, 

responsibility for WAWF destination acceptance may not be clearly defined. Destination acceptance 

under WAWF is a DoD requirement that may require additional coordination to ensure interface 

requirements are addressed. 

 g. DAAS: 

 (1) New data elements will be authorized on multiple DLMS transaction; however, there 

will be no transmission to legacy systems resulting from conversion to a MILSTRIP format for the 

Requisition Alert transactions (identified by the “future” flag in the beginning segment). None of the 

new elements are to be perpetuated to applicable MILS formats. 

 (2) Copies of transactions and changes to routing rules are documented in separate PDCs. 

This PDC requires passing of Navy IA requisitions to DLA in lieu of the Source of Supply. 

 (3) The requisition alert does not apply to MRA Reports, LMARS, or to pull history for 

SDR pre-population because no shipments are made on this document number. However, it is 

appropriate to perform basic requisition edits in DMARS and to reflect the requisition alert and 

matching status transactions in WebVLIPS. WebVLIPS display must include the requisition alert 

indicator. Additionally WebVLIPS must recognize where unit of use applies and adjust the unit of 

issue (“U/I”) display or otherwise indicate unit of use ("U/U"). 

 (4) Although not an immediate requirement, DAAS is also requested pursue development 

of a way to associate the display of the funded requisition with the requisition alert when both values 
ADC 381 

Attachment, Page 18 

are known and associated (e.g. for NSY requisitions which includes both values); perhaps through 

hyperlink. 

 h. DLMS Data Elements. 

 (1) This proposal modifies code values for three existing DLMS data elements. 

Refer to the table above for definitions and characteristics. Refer to Enclosure 3, 4, and 5 (for Reason 

for Requisitioning, Delivery Priority Code, and Utilization code, respectively). 

 Reason for Requisitioning 

 Delivery Priority Code 

 Utilization Code 

 (2) This proposal establishes new data elements and addresses data elements used on 

related Navy BRAC SS&D/IMSP DLMS change proposals (refer to Enclosure 7). 

 Requisition Alert Indicator 

 Unit of Use Indicator 

 Unit of Use Price 

 Requisition Alert Document Number 

 Requisition Alert Document Suffix Code 

 Job Order Number 

 Key Operation Number 

 Requirement Churn Reason Code 

 Quality Inspection Code 

 Picklist Control Number 

 Shop Store (Shop Service Center) 

 (3) This proposal adds previously established data elements to additional transactions 

as specified in the DLMS Supplement tables below. 

 
ADC 381 

Enclosure 1, Page 1 

Enclosure 1, Transaction Impact 

Under this process, the following data elements are required in the listed DLMS transactions as 

indicated. 

Data elements not already available will be added under this proposal. 

Staffing Note: This list does not include DLMS transactions associated with interfund billing; 

therefore, interpretation of logistics bills may be problematic due to unit of use and LSNs. 

 511M, Modification 

 511R, Requisition 

 527D, Due-in/Advance Receipt/Due Verification 

 527R, Receipt, Inquiry and Response and MRA 

 842A/W and 842A/R, SDR and SDR Reply 

 842C/I and 842C/R, Stock Screening Request and Reply 

 842S/Q and 842S/R, Storage Quality Control Report 

 846I, Asset Status Inquiry/ Report 

 846P, Physical Inventory Request 

 846R, Location Reconciliation Request 

 846A, Asset Reclassification 

 867I, Issue 

 869A, Requisitioning Supply/Assistance Request 

 869C, Requisition Cancellation 

 869F, Requisition Follow-Up 

 856S, Shipment Status 

 870M, Materiel Returns Status (FTZ) 

 870S, Supply Status 

 940R, Materiel Release 

 940S, Warehouse Service Request 
ADC 381 

Enclosure 1, Page 2 

 943A, Warehouse Service Advice 

 945A, Materiel Release Advice 

 947I, Inventory Adjustment 
Data Element Matrix 

Data Element 511R 

Includes Post-Post 

511M 527D 527R 947I 940R 945A 867I 869A 869C 869F 870S 856S 842A 842S 8

Requisition Alert Indicator 

Yes Yes No No No No No No Yes Yes Yes No No No No N

Requisition Alert Document Number 

Yes Yes Yes Yes Yes 

ADC 376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes 

PDC 387A

Yes Y

Requisition Alert Document Suffix Code 

Yes Yes Yes Yes Yes 

ADC 376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes 

PDC 387A 

Yes Y

Job Order Number Yes Yes Yes Yes Yes 

ADC 376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes 

PDC 387A

Yes Y

Key Operation Number 

Yes Yes Yes Yes Yes 

ADC

376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes 

PDC 387A 

Yes Y

Requirement Churn Reason Code 

Yes Yes No No No No No No Yes No Yes Yes No No No N

Reason for Requisitioning Code 

Yes Yes Yes Yes No Yes Yes No Yes No Yes Yes Yes No No N

Delivery Priority Code Yes Yes No No No Yes Yes No Yes No Yes Yes Yes No No NQuality Inspection Code 

Yes Yes Yes Yes No Yes Yes Yes Yes No Yes Yes Yes No No N

Shop Store Yes Yes No No No Yes Yes Yes Yes Yes Yes Yes Yes No No NPicklist Control Number 

Yes Yes No No No Yes Yes Yes Yes No Yes No No No No N

 MCT Tag Number (MCT Tag Suffix is no longer a separate data element) 

No No Yes 

PDC 393

Yes PDC 393 

Yes 

ADC 376 

Yes PDC 393

Yes PDC 393

Yes PDC 393

No No No Yes Yes No No N

Unit Price/Unit of Use Price

No No No No No Yes Yes Yes No No No Yes Yes No No N
Data Element 511R 

Includes Post-Post 

511M 527D 527R 947I 940R 945A 867I 869A 869C 869F 870S 856S 842A 842S 8

Unit of Use Indicator Yes Yes Yes Yes Yes 

ADC 376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Y

LSN Yes Yes Yes Yes Yes 

ADC 376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Y

NSN for cross-reference 

Yes No Yes Yes Yes 

ADC 376 

Yes Yes Yes No No No Yes Yes Yes Yes Y

Party To Receive Copy, Status, or Reports 

Yes PDC 404 

Yes PDC 404 

No Yes 

PDC 404 

No No No No Yes 

PDC 404 

Yes PDC 404 

Yes PDC 404 

No No No No N

Utilization Code Yes Yes Yes No No Yes Yes No Yes Yes Yes Yes Yes No No NDelivery Location Yes Yes Yes No No Yes No No No No Yes No No No No NCustomer Order Acceptance Record (COAR) 

Yes Yes Yes Yes Yes 

ADC 376 

Yes Yes Yes Yes Yes Yes Yes Yes Yes 

PDC 387A 

No Y

Work Order Number No No No No No Yes Yes Yes No No No Yes 

ADC 379 

No No No N
ADC 381 

Enclosure 2, Page 1 

Enclosure 2, BRAC SS&D Rules for Breaching Protected Stock 

The business rules for breaching of protected stock at both ALC’s and FRC’s sites will be systemically 

accomplished based on the parameters with an internal EBS table. The table within EBS is 

configurable by plant, therefore can be site specific. 

Any breaching of protected stock will be done on the same business rules at NSY sites, but will be 

accomplished manually. 

 1) There is no other stock available for issue within the DLA network 

 2) The request contains an IPG 1, a NON-Standard RDD or a JCS Project code. 

Staffing Note: This originally proposed business rules require additional clarification prior to formal 

publication. An ADC addendum will be provided to document this portion of the business process. 
ADC 381 

Enclosure 3, Page 1 

Enclosure 3, Reason for Requisitioning 

Update the DLMS Dictionary definition as indicated below. 

Name: Reason For Requisitioning Code 

Alias: Reason For Requisitioning Code or Use Code (LQ01/Qualifier 98) 

Definition: 

Identifies the reason for submission of the requisition or the type of materiel 

requirement applicable to a requisition, requisition alert, or materiel release 

order. 

Remarks: Also referred to as “Use Code.” This data element was originally established as a placeholder for a 

DLMS enhancement. The only authorized use is by Navy industrial activities requisitioning from DLA under 

industrial support agreement or for Navy-owned materiel stored in a distribution depot (For Navy usage 

alphabetic codes apply).

Data Code Characteristics: Type: Id Min: 001 Max: 002 

1 Routine Preventive Maintenance 

2 One-Time Special Requirement 

3 Headquarters Sponsored Program 

4 Inventory Maintenance (Increased Levels) 

5 Stock Replenishment 

6 Retail Range Add 

7 Provisioning/Insurance Item 

8 Reordered Item (Lost/Damaged In Shipment) 

9 Planned Maintenance 

10 Corrective Maintenance 

11 General Use Materiel 

12 Damage Control 

14 One Time Change 

15 General Use Consumable 

16 Habitability 

17 Planned Program Item 

18 Emergent Repair Item 

19 Fixed Allowance 

20 Organizational Equipment 

21 War Reserves 

D Direct Material Inventory (DMI) 

E End Use Delivery 

M Mission Support Material (MSM) Item 
ADC 381 

Enclosure 3, Page 2 

U Ripout/Courtesy Storage 

S Nuclear Shop Delivery 
ADC 381 

Enclosure 4, Page 1 

Enclosure 4, Delivery Priority Code 

Update the DLMS Dictionary definition as indicated below. 

Name: Delivery Priority Code 

Alias: 

Delivery Rank (Priority) (X12 4030-LQ01/Qualifier R3) 

Assured Delivery Indicator (X12 4010-LQ01/Qualifier KJ) 

Definition: Communicates special processing priority requirements to the Distribution Standard 

System (DSS) for distribution depot shipments under agreements with DOD Components. May be 

used by Navy industrial sites requisitioning from DLA under BRAC IMSP agreement to identify 

one-hour delivery requirement (Code X). 

Remarks: Delivery Priority Codes carry no precedence in ICP asset allocation decisions. Asset 

allocation decisions are controlled by UMMIPS as defined in DOD supply chain materiel management 

regulation (4140.1-R) and by the Military Standard Requisitioning and Issue Procedures (4000.25-1-

M). 

 

Data Code Characteristics: Type: Id Min: 001 Max: 001 

 

Code Definition 

A Immediate release (all users) 

B Bearer (Navy) 

H Hot (Navy) 

O Overnight (Navy) 

Q Quick (Navy) 

T Next day delivery (SBSS stock relates to Air Force delivery priority 7) 

U Twelve (12) hour delivery (MIC stock replenishment/bench stock relates to Air Force delivery 

priority 6) 

V Eight (8) hour delivery (production issues relate to Air Force delivery priority 4) 

W Four (4) hour delivery (maintenance line relates to Air Force delivery priority 3) 

X One (1) hour delivery (AWP/work stoppage relates to Air Force delivery priority 2 or Navy 

industrial activity requirement) 

Y Thirty (30) minute delivery (anticipated MICAP relates to Air Force delivery priority 5) 

 Z Thirty (30) minute delivery (MICAP relates to Air Force delivery priority 1) 
ADC 381 

Enclosure 5, Page 1 

Enclosure 5, Utilization Code 

Update the DLMS Dictionary definition as indicated below. 

Name: Utilization Code 

Alias: Utilization Code (X12 4010 and higher - LQ01/Qualifier AJ) 

Definition: Identifies the purpose of the transaction. 

Remarks: Position 11 of the MILSTRIP document number consists of any alpha or numeric 

characters with the exception of the reserved alpha codes listed below. The reserved codes are defined 

under this Logistics Qualifier (AJ). 

Source: DLMS Manual (DOD 4000.25-M) and Military Standard Requisitioning and Issue Procedures 

(MILSTRIP) (DOD 4000.25-1-M AP2.7 (Appendix AP2.7) 

Data Code Characteristics: Type: Id Min: 001 Max: 001

CODE EXPLANATION 

 

E Navy exception "ship to" for deployed naval units 

G Navy exception "ship to" for deployed naval units 

J Inventory control point (ICP) interrogations or offers of excess, and requisitions resulting from the 

interrogations or offers (denotes inter-service supply support transactions between ICPs). 

K Requisitions submitted to Defense Reutilization And Marketing Offices (DRMOs) and General 

Services Administration (GSA) for excess property located at a DRMO that is requested as a result 

of reviewing manual screening lists, e.g., excess personal property lists (EPPLs) and GSA regional 

catalog listings. 

L Requisitions submitted to DRMOs which result from physical screening of property at the DRMO; 

referred to as "Local Area Screening" without any consideration of the distance traveled by the 

screener. 

M ICP/IMM-directed disposal release orders resulting from BRAC. This value is not currently 

approved for use on other transaction types. 

N Transactions for components reclaimed by military activities or contractors through end item 

reclamation. (This code is cited when forwarding components to stock by activities preparing 

shipping or turn-in document.) 

P Requisitions for excess contractor inventory that has been reported on DD Form 540 or referred by 

the Contractor Inventory Redistribution System (CIRS) either mechanically or by listing. 

Q Requisitions and related transactions or documents for items reclaimed from aircraft and 

equipments by the Aerospace Maintenance And Regeneration Center (AMARC). 

R Requisitions submitted to DRMS and/or DRMOs from ICPs or IMMs based on final asset 

screening notice of surplus personal property. 

S Requisitions submitted to DRMS and/or DRMOs from ICP or IMM based on a front end screening 
ADC 381 

Enclosure 5, Page 2 

notice of excess personal property. 

T Requisitions submitted to DRMS and/or DRMOs from ICP or IMM based on a management 

decision for recoupment of known transfers to disposal. 

U Product Quality Deficiency Report (PQDR) and Supply Discrepancy Report (SDR) related 

transactions when the original requisition number is not known. (MILSBILLS). 

W Navy exception "ship to" for deployed naval units 

V Nuclear related materiel code 2305 material requires manual routine contact of Nuclear 

Engineering Department for delivery instructions 

Y Requisitions resulting from interrogation of the interrogation requirements information system. 

Z Nuclear related materiel code 2305 material requires manual immediate contact of Nuclear 

Engineering Department for delivery instructions. 
ADC 381 

Enclosure 6, Page 1 

Enclosure 6 Transaction Flow Diagram Extract 

Flows applicable to this ADC are included in this enclosure (as of 5/27/2010) 

Spiral 2 Process Flow List: 

1.0 = Material Master 

1.1a = MMR-NSN/LSN (Query) Request for Material Master creation & Record Establishment 

1.1b = MMR – NSN Query and Record Establishment (NSY primary) 

1.2 = MMR- Tailored Change Notice 

2.0 = Forecast/Gross Demand 

2.1 = FRC Gross Demand Plan (GDP) Signal 

2.1a = DLA GDP Filtering 

3.0 = Requisition Alert 

3.1 = FRC Net Requisition Alert 

3.2 = Requisition Alert Initiation (NSY) 

3.3 = Requisition Alert – NSY – Call-In Process Overnights – Non-DLA Managed 

3.4 = Off Station / Tiger Team Support 

4.0 = Level Setting 

4.1 = Level Setting 

5.0 = Protection 

5.1 = Protection 

5.2 = FRC Breaching (Auto) 

5.3 = Breaching (Manual) 

6.0 = Fulfillment 

6.1 = Fulfillment Requisition Alert/ Issue Order 

6.2 = EMALL Ordering with MILSTRIP 

6.3 = DLA Government Purchase Card 

6.4 = Local Purchase Auto Solicitation 

6.4a = Local Purchase Manual Solicitation 

6.5 = Local Manufacturing 

6.6 = Non-Production Material Procurement by NSY/FRC external to DLA 

7.0 = Receiving 

7.1 = Navy Funded Receiving 

7.2 = DWCF Funded Receiving 

7.3 = Staging (NSY) 

7.4 = Material Returns 

7.5 = Picklist and Staging Update for DSS 

8.0 = Quality 

8.1 = Inspection 

8.2 = DLA and Navy Owned PQDR 

8.3 = SDR at Receiving 

8.4 = SDR Discovery after Issue 

9.0 = Funded Requisition 

9.1 = Funded Requisition processing for DLA Owned Material on hand at the DSS IA Worksite 

9.1a= Issue of Navy IA Material (DSS IA Worksite) 
ADC 381 

Enclosure 6, Page 2 

9.2 = Funded Requisition processing for DLA Owned Material not on hand at the DSS IA Worksite 

9.3 (2011) = NSY Planned Material for Nuclear Support – 2011 and Prior 

9.3 (2012) = NSY Planned Material for Nuclear Support – 2012 and Later 

9.4 = Post-Post / Walk Ups & Walk -Thru DSS IA Worksite 

9.5 = Funded Requisition Processing for Non Production Material 

10.0 = Requisition Maintenance 

10.1 = Material Obligation Validation 

10.2 = Change of JON/KO or WO 

10.3 = Requisition Maintenance 

10.4 = Status Process 

10.5 = DLA Automated Follow Up 

11.0 = End-to-End Processes 

11.1 = Less Than Unit of Issue 

11.2 = Program Sponsor Furnished Material Process 

11.3a = Rip out & Custody Storage (Receive, Store, & Issue) 

11.3b = Rip out & Custody Storage (Modification of a Key-Op) 

11.3c = Rip out & Custody Storage (Re-occurring movement to/from Repair Shop) 

11.3d = Rip out & Custody Storage (Sub-component Re-assembly) 

11.4 = Navy Funded DLR and Even Cog 

12.0 = Special Processes 

12.1 = DLA Owned Reconciliation Process 

12.2 = Navy Owned Reconciliation Process 

12.3 = Inventory On Hand Update 

12.3a= Navy Owned Inventory Adjustments 

12.4 = HAZMAT – Receiving Process for DSS IA Worksite 

12.5 = HAZMAT – Funded Requisition Process for DSS IA Worksite 

12.6= MAT NSY MSM Attrition Logic 

12.7= NWCF-SM & DM Capitalization (FRC) 
ADC 381 

Enclosure 6, Page 3 

1. User (Buyer/Planner) creates Requisition Alerts in MRP II -> 2 

User (Buyer/Planner) logs in to MRP II to view their assigned items for Weeks 0, 1, and 2. 

User (Buyer/Planner) reviews output to decide material and quantity to be ordered. According to their 

discretion/expertise, the Buyer/Planner will make adjustments to the recommended Requisition Alert. 

2. IF4a formats one 511R requisition (A0A) for each item and sends the 511R to DAASC on a real time basis. 

IF4a assigns the original document number using the DLA site Purple DODAAC (S7N008 FRCE, S7N009 

FRCSE, S7N010 FRCSW). Format of 511R depends on the type of item being requisitioned. (Refer to 

Business Rules) -> 2a, 2b, 2c 

2a. Non-DLA NSN -> 3 

2b. DLA NSN -> 3 

2c. LSN -> 3 

3. DAASC receives and routes the 511R transaction to EBS -> 4 

EBS processes the 511R and responds accordingly. -> 4a, 4b, 4c 

4a. If stock is not on-hand at the DD/DSS IA Worksite, DLA will generate the 511R with a N__DLA document 

number, a signal code to indicate the destination and billing. For 511Rs, Signal Code ‘C’ will be used to 

indicate shipments to the requisitioner and Signal code ‘L’ for shipments to the Supplementary Address. The 

requisition alert document number is maintained and cross-referenced to DLA document number internally 

within EBS and the 511R is sent to DAASC for routing to the Non-DLA Source of Supply. -> 4a1, 4d 

4a1. DAASC routes the 511R to the Non-DLA Source of Supply -> 4a2 

4a2. Non-DLA Source of Supply receives the 511R from DAASC and provides Status to EBS.-> Status Process 

4b. 511R for DLA-Managed NSNs is received for EBS fulfillment -> 4d 
ADC 381 

Enclosure 6, Page 4 

4c. 511R for LSNs are received into EBS and sourced based on asset availability within the Network or to the 

On-site DLA Buyer ->4e 

4d. DLA owned Material at the supporting DD is available for protection to support Requisition Alert or assets 

are moved internally with DLA network to support Requisition Alert to the IA worksite. EBS will send a 940S, 

Re-warehouse and Protection Request, to request re-warehousing and protection of assets through DAASC-> 

4d1 

4d1. DAASC receives and passes the 940S, Re-warehouse and Protection Request, to DSS -> 4d2 

4d2. DSS receives 940S, Re-warehouse and Protection Request, when material has been re-warehoused to DSS 

IA Worksite, DSS will confirm action with a 943A, Stow Confirmation, forwarded to DAASC -> 4d3 

4d3.DAASC receives and passes the 943A, Stow Confirmation, to EBS -> 4d4 

4d4.EBS receives and processes the 943A, Stow Confirmation, to protect material under ownership purpose 

code E. An 870S, Supply status with Status code ‘PQ’ will be sent to DAASC->4d5 

4d5. DAASC receives and passes the 870S, Supply Status (PQ status code) to IF9 ->4d6 

4d6. IF9 updates MRP II and closes the Requisition Alert -> END 

NOTE: If DLA purchases the material see DWCF Receiving 

4e. 511R is processed in accordance with the Fulfillment Requisition Alert / Funded Requisition process (for 2a, 

2b, 2c) -> Fulfillment Process 
ADC 381 

Enclosure 6, Page 5 

1. Completed JML is passed to MAT from MRQT. 

2. MAT screens against Navy locally owned assets prior to passing the Requisition Alert to DLA. 

For FUM and excess MAT will send the 940S (reflecting staging/pick list info) and 846A to reassign the local 

assets to Requisition Alert document number through DAASC to the local DSS IA worksite (if partial fill from 

FUM, remainder requirement passed to DLA as a Requisition Alert with Cost reservation). -> 2a, 3, 4 

If not found in FUM or excess, MAT generates 511R Requisition Alert, updates Cost, and, if applicable, creates 

a 940S (with the appropriate Action Code) and passes to DAASC via PS I/O F. -> 3, 4 

2a. DAASC receives and passes 940S/846A to DSS IA Worksite -> 2a1 

2a1. DSS will receive 940S and 846A from Navy; updating protection and establishing pick-list data as 

applicable for Navy owned assets -> 2a2 

2a2. DSS IA Worksite replies with 943A, Stow Confirmation to DAASC in response to 940S for protection of 

Navy owned assets ->6 

2a2. DSS IA Worksite replies with 947I,(Asset Reclassification Response) to DAASC in response to 846A for 

protection within DSS as Navy Owned -> 6 

3. MAT’s existing interface to Cost will update the reservation table in Cost for the future A0_ issue document. 

-> END 

4. DAASC receives, routes, and validates the 511R Requisition Alert (to EBS) -> 5 
ADC 381 

Enclosure 6, Page 6 

 DAASC receives and passes the 940S, Pick List data for the 511R, Requisition Alert to DSS (when 

applicable) – 5b2 

5. EBS receives and processes the Requisition Alert and sources accordingly -> 5a, 5b 

 If the use code is M, material should be pulled from local DLA MSM shop stores. 

 If there is no M Use code and the material is available locally, EBS sources to the local IA worksite. 

5a. If stock is not on-hand at the DD/DSS IA Worksite, DLA will generate the 511R with a N__DLA document 

number, a signal code to indicate the destination and billing. When an advice code of “2W” has been assigned 

to the DLA 511R, the quantity of the material not available for free issue from RRAM will be cancelled with 

‘CM’ status. When no advice code has been assigned to the DLA 511R, the quantity of the material not 

available for free issue from RRAM will be issued from Navy owned stocks or backordered from Navy 

fulfillment action. See Navy ERP processing rules Table for RRAM in the 3.2 worksheet and PDC 385. NSY 

requisition alert document number is maintained and cross-referenced to DLA document number internally 

within EBS. The 511R from EBS will always be at the FLIS Unit of Issue and will be forwarded to DAASC for 

routing to NRP (RIC) -> 5a1 

5a1. DAASC receives, validates and passes the 511R to NRP -> 5a2 

5a2. NRP (RRAM) receives the 511R from DAASC and provides Supply Status to EBS. ->5a3 

If there’s a ‘2W’ Advice Code and RRAM material is available in total or partial quantities, NRP will generate 

the BN status back to EBS. EBS will send the BN Status to NSY site on the open requisition alert and 

create/send a PMRD to the DSS IA Worksite on behalf of the Navy reflecting both DLA document number, 

Requisition Alert document number, JO/KO, and local Navy RIC. Any deficient quantity will be cancelled with 

‘CM’ status to EBS. -> Status Process. 

If there’s no Advice Code and RRAM material is available in total or partial quantities, NRP will generate the 

BN status back to EBS. EBS will send the BN Status to NSY site on the open requisition alert and create/send a 

PMRD to the DSS IA Worksite on behalf of the Navy reflecting both DLA document number, Requisition Alert 

document number, JO/KO, and local Navy RIC. For any deficient quantity, NRP will issue or backorder the 

deficient material quantity and generate the BA or BB status back to EBS. EBS will send the BA or BB Status 

to NSY site on the open requisition alert and create/send a PMRD to the DSS IA Worksite. -> Status Process. 

5a3. EBS will receive status back from RRAM via DAASC.-> Status Process 

DLA will send supply status received from NRP for DLA N__DLA documents Requisitions to NSY cross 

referenced with Requisition Alert document number ->Status Process 

 If there are RRAM assets available, EBS will create a PMRD. ->7 

5b. If DLA Owned material is available locally at the supporting DD, EBS sends 940S , Re-warehouse and 

protection request, to DAASC- -> 5b1 

5b1 DAASC receives and passes the 940s, re-warehouse and protection request, to DSS -> 5b2 

5b2 DSS receives 940s to re-warehouse and protect DLA assets or to provide delivery information to DSS. If 

511R and 940S contain a QA code indicating the need for inspection, the material re-warehoused from the DD 

must be inspected at the NSY IA site receiving area prior to storage (refer to flow 8.1; Inspection). -> 5b3, 2a2 

5b3 when request completed DSS generates and passes 943A, stow confirmation, to DAASC - > 6 

5c. 511R for LSNs is received and processed for EBS fulfillment -> Fulfillment Requisition Alert/ Issue Order 

process 

6. DAASC receives and passes the 947I, (Asset Reclassification Response) 943A (Stow Confirmation) to NSY 

Hold Queue (Navy Owned Material) or 943A to EBS (DLA owned Material) -> 6a,6a1 
ADC 381 

Enclosure 6, Page 7 

6a. PS I/O F pulls the 947I (Asset Reclassification Response) and 943a (Stow confirmation) transaction and 

passes it to MAT -> 8 

6a1. EBS receives and processes 943A and adjusts protection table ->6a2 

6a2. EBS sends 870S, Supply Status, PQ status code to DAASC -> 6a3 

6a3. DAASC receives and passes 870S, Supply Status, PQ status code, to PS I/O F for DLA assets protected for 

Requisition Alert->6a4 

6a4. PS I/O F pulls the 870S, Supply Status, PQ status code transaction and passes it to MAT -> 8 

7. EBS sends PMRD transaction to DAASC for DSS IA Worksite supporting the Industrial Activity. -> 7a 

7a. DAASC receives, validates and routes, PMRD and forwards to DSS IA Worksite supporting the Industrial 

Activity -> 7b 

7b. DSS receives the PMRD and updates its file ->END 

MAT updates the Requisition Alert JML document number appropriately. -> END 
ADC 381 

Enclosure 6, Page 8 

1. Shipyard personnel screens local assets and determines material not available and high priority which requires 

call-in for overnight delivery->2 

2. MRQT passes MAT a 3ZF transaction creating a Requisition Alert and assigns a document number (JML) 

without transactions or a MAT screen is used to create the Requisition Alert without transmission of an A0_. 

Also, a reservation is provided to Cost.->3 

3. Manual Collaboration between Shipyard personnel and DLA on-site personnel to call-in order to the Source 

of Supply (SOS). ->3a 

3a. DLA on-site personnel access EBS system to retrieve appropriate DLA Document Number assignment 

based on the requesting site and manually inputs the requisition into EBS.->3b 

3b. EBS assigns a DLA document number.->3c 

3c. DLA on-site personnel makes phone call to the service requesting urgent material. -> 3c1 

3c1. Service sends the (870S, AE_) Status transaction to EBS. -> 4 

4. DLA IA personnel will create Sales Order in EBS with the Requisition Alert document number and other 

pertinent data and the Purchase Order reflecting Due-In from the other Service which generates (AE_) Status 

back to NSY. ->4a, 4b 

4a. EBS sends the (870S, AE_) Status-> Status Process 

4b. EBS generates the 527D, PMRD and sends to DAASC. ->4b1 

4b1. DAASC receives, validates and routes PMRD to the DSS IA worksite. ->4b2 

4b2. DSS IA worksite records 527D, PMRD transactions. ->5 

5. Service ships the material to DSS IA worksite> 6 

6. DSS IA worksite receives Material.->DWCF Funded Receiving Process 

 MAT triggers the material call out, to issue material to production. 
ADC 381 

Enclosure 6, Page 9 

Completed JML is passed to MAT from MRQT 

MAT screens against Navy locally owned assets as in 3.2 Requisition Alert Initiation Process (NSY) prior to 

passing the demand signal to DLA. 

• For FUM and excess MAT will send the 846A and 940S to reassign the local assets to Requisition Alert JML 

document number. DSS IA worksite will complete the re-assignment as in 3.2 NSY Requisition Alert. Material 

will be shipped to the off station location and delivered in accordance to the instructions of the 940S. 

MAT updates Cost to establish a reservation and validation for future issue.->1a 

1a. If not found in FUM or excess, 511R Requisition Alert and 940S (if applicable) are created and passed to PS 

I/O F. 511R document with a supplementary address for the Remote Site location will trigger EBS sourcing 

process (MSM shop store issues at Off Station Location or shipping of Requisition Alert from another network 

depot/source of supply to the off station location.) -> 1b 

1b. PS I/O F receives and sends 511R A0_ to DAASC from the PS I/O F out folder. ->1c 

1c. DAASC receives validates and routes the 511R A0_ to EBS and 940S to DSS IA Worksite. ->2 

2. EBS receives the 511R A0_ from DAASC.->2a, 2b 

2a. EBS sources the material. This will include screening RRAM for any free issue material as discussed in flow 

3.2. -> Fulfillment Process Flows (3.2, 6 series and 9 series) 

2b. EBS creates and sends outbound Status.->Status Process 

3. DSS IA Worksite Remote terminals receive material and processes in accordance with the 940S. ->Receiving 

Process 

4. MAT remote sites initiate the issue.->Issue Order Process 
ADC 381 

Enclosure 6, Page 10 

NOTE: if there is no remote terminal off –site location (for example: Tiger Teams) then the Requisition Alert 

would be staged at the DSS IA Worksite and the shipyard would request issue orders for packaging and 

shipping to remote location. 
ADC 381 

Enclosure 6, Page 11 

1a. FRC Gross Demand Plan and NSY forecast are passed to EBS-Manugistics on a weekly basis from 

appropriate Navy system via Flat File (see flow 2.1 for process). -> 2a 

1b. FRC and NSY Requisition Alerts are generated as required from Navy systems and sent to EBS via the 

(A0_) 511R data set -> 2b 

2a. EBS-Manugistics performs forecasting evaluation based on set parameters to determines levels, automatic 

buys or output to demand plan. -> 3 

2b. EBS reacts to the Requisition Alert to place material within the fence for FRC and NSY. Material placed 

within the fence at NSY will be protected by document number and Ownership Purpose (O/P) Code in EBS. 

Material placed inside fence at FRC will be protected via O/P Code and protection level indicator. -> 3 

3. EBS-Manugistics passes the Protected Levels to EBS-SAP. In addition to levels protection indicators can be 

manually set to prevent automatic breaching of on hand quantities at or above those levels. -> 4 

4. EBS levels will be passed to DSS IA Worksite via existing interfaces. Levels and indicators will be passed to 

NSY and FRC via 832N Change Notice (refer to process flow 1.2). See Level Setting flow for additional detail. 

-> END
ADC 381 

Enclosure 6, Page 12 

1. Requisition for a Non-Industrial Activity customer (or a different Industrial Activity) is received in EBS as 

part of the Issue Order process.->2 

2. EBS processes the sales order. The only available stock is protected at an FRC Industrial Activity. EBS 

(Global ATP) determines that the sales order meets the business rules for breaching stock. EBS automatically 

sources the sales order with the protected stock from the Industrial Activity. ->2a 

2a. MRO (940R, A5_) is sent from EBS to DAASC. ->2a1 

2a1. DAASC receives, validates and routes MRO (940R, A5_) to DSS IA Worksite. ->2a2 

2a2. DSS IA Worksite processes MRO (940R, A5_) ->3 

3. DSS IA worksite delivers material to customer. ->4 

4. DSS IA Worksite confirms shipment of material and sends Material Confirmation, (945A, AR_) and 

Shipment Status, (856S, AS_) to DAASC. ->4a, Status Process, Inventory Update Process 

4a. DAASC receives, validates and routes Material Confirmation, (945A, AR_) and to EBS. ->4b 

4b. EBS closes sales order, decrements inventory, and bills customer. -> End 

Note: When MRP II is notified of on-hand assets, if applicable from the Netting process will generate a new net 

Requisition Alert as applicable. ->FRC Net Requisition Alert Process. 

5. EBS generates monthly report for sales orders breaching protected stock at FRCs. Report will reflect: 

customer DoDAAC, quantity, IPD, RDD, Project Code. ->End
ADC 381 

Enclosure 6, Page 13 

• 1. Requisition for a Non-Industrial Activity customer (or a different Industrial Activity) is received in 

EBS as part of the Issue Order process. ->2 & 3 

• 2. EBS processes the sales order. The only available stock is protected at a different Industrial Activity. 

EBS (Global ATP) determines that the sales order does NOT meet the business rules for automatic 

breaching stock at FRCs. EBS does not automatically source the sales order from the protected stock 

and places the sales order on backorder. ->3 

• 3. The customer initiates a request for lateral support (within protected levels) by contacting the 

Customer Account Specialist (CAS). ->4a 

• 4a. The CAS reviews backorder with EBS. ->4b 

• 4b. The CAS also contacts the POC (NSY/FRC DLA Personnel)) at the Navy Industrial Activity Site 

for material release permission. ->4c 

• 4c. The NSY/FRC DLA Personnel POC will collaborate with Industrial Activity production planning. -

> 4d1 

• 4d1. If the Industrial Activity agrees to release the assets, the CAS will source the order with the 

protected stock. ->4e 

• 4d2. If the Industrial Activity does not agree to release the stock, the sales order remains on backorder 

and follows standard backorder processing. ->4e 

• 4e. The NSY/FRC DLA Personnel communicates to the CAS the approval or disapproval of the release 

of the protected stock. ->4f 

• 4f. If approved, the CAS releases the backorder in EBS. ->5a1 

• If not approved->END 

• 5a1. EBS sends A5_ (940R) and Supply Status (856S, AE_) to DAASC -> 5a2 
ADC 381 

Enclosure 6, Page 14 

• Supply Status (870S,AE) is passed to customer -> Status Process. 

• 5a2. DAASC receives, validates, and routes A5_ (940R) to DSS IA Worksite -> 5a3 

• 5a3. DSS IA Worksite processes A5_ (940R). -> 6 & 7a 

• DSS will provide on-hand asset balance when MRO is processed via the 947I, DZA -> Inventory 

Update Process 

• 6. DSS IA Worksite delivers material to customer. -> END 

• 7a. DSS IA Worksite generates AR0 (945A) to EBS and generates an AS8 (856S) to DAASC. -> 7b 

• 7b. DAASC receives, validates and routes the AR0 (945A) to EBS and AS8 (856S) to customer as 

applicable. ->7c, Status Process 

• 7c. EBS processes AR0 (945A) updates inventory balance and bills customer. ->END. 

. 
ADC 381 

Enclosure 6, Page 15 

1a. User requests material in MAT A0_ Funded document created, MAT sends funded obligation request to 

COST and 940S via DAASC to DSS. The A0_ funded requisition and picklist information gets sent to PS I/O F 

-> 1a1, Picklist & Staging Process 

1a1. PS I/O F pushes the 511R funded document or the 527R DRA to DAASC. ->2, 9 

1b. User requests material in MRP II and is captured by IF5 -> 1b1 

1b1. IF5 creates a DLMS format 511R (A0_), validates funding availability in DIFMS and creates and sends 

940S Pick List via DAASC to DSS IA Worksite -> FI, 2, Picklist & Staging Process 

2. DAASC receives, validates and routes the 511R to EBS -> 3 

3. EBS receives and processes the 511R -> 4 

4. EBS directs shipment via 940R, forwards to DAASC ->5 

 - EBS provides status -> Status Process 

 - EBS provides inventory On Hand Update 

5. DAASC receives, validates and routes the 940R to DSS IA worksite ->6 

6. DSS IA worksite receives and processes 940R. ->6a 

NSY Note: In some cases EBS may direct that the issue be fulfilled with material re-warehoused from the DD 

site which may not have been inspected as prescribed by the NSY QA code. If the 511R, 940R or 940S contain 

a QA code indicating the need for inspection, the material re-warehoused from the DD must be inspected at the 

NSY IA site receiving area prior to storage (refer to flow 8.1; Inspection). 

FRC Note: For FRCs, any required inspection will be done after issue and prior to delivery of material to the 

Artisan. Inspection will be based on the picklist local DSS IA will notify QA. DSS will close local manifest 

and generate the 870S with PD status when material is placed in the QA cage. 
ADC 381 

Enclosure 6, Page 16 

6a. DSS IA worksite retrieve picklist or JO/KO from DSS table -> 6b 

6b. DSS IA worksite picks, packs by picklist or JO/KO listing -> 6c, 6d 

6c. DSS IA worksite delivers material to Artisan and generates 870S (AE_) with Delivery Status ”PD” to 

DAASC -> 7b Note: For NSYs, 870S with “PD” status will indicate badge number of artisan who 

accepted delivery. 

6d. DSS IA worksite provides shipment status in the form of an 856S (AS_), and Material Release Confirmation 

in the form of 945A (AR_) to DAASC -> 7a, 7b, Status Process 

7a. DAASC receives and passes Material Release confirmation in the form of 945A (AR_) to EBS -> 7a1 

7a1. EBS receives Material Release Confirmation (945A (AR_)) and generates interfund billing to customer -

>END 

7b. For MAT, DAASC will distribute the 856S (AS_) and the 870S (AE_) with ”PD” to the NSY Pull Queue -

>8b 

 For MRP II, DAASC will distribute an 856S (AS_) and an 870S (AE_) with ”PD” to MRP II through IF13 -

>8a 

8a. IF 13 will receive the 856S and 870S with PD status and process the 870S. This creates the virtual receipt to 

MRPII, which creates and sends the 527R (DRA) to DAASC  1a1,9 

8a1. Virtual receipt updates the DIFMS for MRP II ->END 

8b. PS I/O F will pull the 856S (AS_) and 870S (AE_) with ”PD” from the DAASC NSY Pull Queue and pass 

into MAT ->8b1 

8b1. MAT receives the 856S (AS_) and 870S (AE_) with ”PD”, and updates MAT and COST. This creates the 

virtual receipt in MAT, which creates and sends the 527R (DRA) (could be multiple on same Doc#) that is sent 

to the PS I/O F, which pushes the 527R (DRA) to DAASC  1a1,9 

9. DAASC receives, validates and routes the 527R (DRA) to EBS ->10 

10. EBS receives527R (DRA) data and updates sales order appropriately -> End 
ADC 381 

Enclosure 6, Page 17 

Navy IA users call for material to be issued to a JO/KO or Work Order using MRP II (FRCs) or MAT (NSYs). -

> 1a, 1b 

For NSYs issues may be preceded by a change to existing job order on NSY owned item (Ex: FUM) Refer to 

10.2 Change /cancellation of JON/KO after receipt flow 

1a. IF5 is triggered by a pick list requirement to be satisfied from FRC owned material on hand in the DSS IA 

Worksite and generates a 940R (A5_) and 940S and sends to DAASC. -> 2, Pick list & Staging Update (940S) 

1b. Based on user input, MAT generates a 940R (A5_) and 940S and sends to DAASC for material that is NSY 

owned and on hand at the DSS IA Worksite. -> 1b1, Picklist & Staging Update (940S) 

1b1. PSI/OF receives and sends the 940R (A5_) to DAASC. -> 22 

2. DAASC receives, validates and routes the 940R (A5_) to the DSS IA Worksite. -> 3 

3. The DSS IA Worksite issues the Navy IA owned material to the appropriate JO/KO (NSY) or Work Order 

(FRC) and sends an 856S(AS_) as shipping status -> 4, Status Process 

4. DSS IA worksite sends the 945A AR_ material release confirmation to DAASC. -> 4a,4b 

4a. DAASC receives and passes the Material Release Confirmation 945A, AR_ to IF5. ->4a1 

4a1. IF5 processes the 945A AR_ material release confirmation in MRP II as status and holds pending receipt of 

the 870S (AE_) with PD status ->5a1 

4b. DAASC places the 945A AR_ material release confirmation in the NSY Hold queue. -> 4b1 

4b1. PSI/OF pulls the 945A AR_ material release confirmation from the NSY hold queue and processes in 

MAT as status and holds pending receipt of the 870S (AE_) with PD status ->5b1 

5. After DSS IA worksite delivers material to the Artisan, DSS sends 870S (AE_) with “PD” delivery 

notification status to DAASC. -> 5a,5b Note: For NSYs, 870S with “PD” status will indicate badge number of 
ADC 381 

Enclosure 6, Page 18 

artisan who accepted delivery. 

5a. DAASC receives and passes the 870S (AE_) delivery notification status to IF5. ->5a1 

5a1. IF5 processes the 870S (AE_) delivery notification with PD status, matches it to the 945A (AR_) on hold, 

and completes the original 940R (A5_) in MPRII -> END 

5b. DAASC places the 870S (AE_) delivery notification status with PD Status in the NSY Hold queue. -> 5b1 

5b1. PSI/OF pulls the 870S (AE_) delivery notification with PD status from the NSY hold queue, matches it to 

the 945A (AR_) on hold, and completes the original 940R (A5_) in MAT -> END 

FRC Note: For FRCs, any required inspection will be done after issue and prior to delivery of material to the 

Artisan. Inspection will be based on the picklist local DSS IA will notify QA. DSS will close local manifest 

and generate the 870S with PD status when material is placed in the QA cage. 
ADC 381 

Enclosure 6, Page 19 

1a. User requests material in MAT A0_ (511R) Funded document created, MAT sends funded obligation 

request to COST. The A0_ funded requisition gets sent to PS I/O F -> 1a1, Picklist & Staging Update Process 

1a1. PS I/O F pushes the 511R to DAASC ->2a 

1b. User requests material in MRP II and is captured by IF5 -> 1b1 

1b1. IF5 creates a DLMS format A0_ (511R) , validates funding availability in DIFMS and creates and sends 

Pick List to DSS IA Worksite -> FI, 2a, Picklist & Staging Update Process 

2a. DAASC receives, validates and routes the 511R to EBS ->2b 

2b. EBS receives and processes the 511R ->3a 

3a. EBS determines material availability; directs shipment via 940R and forwards to DAASC ->3b, Status 

Process 

3a1. EBS backorders request when material is not available and provides status -> Status Process 

3b. DAASC receives, validates and routes the 940R to the appropriate storage activity ->3c 

3c. Storage activity receives and processes 940R ->4a 

4a. Storage activity picks, packs and ships the material. Material Release Confirmation and Shipment status are 

passed to DASSC -> 4b, 4a1, Status Process 

4a1. DSS IA Worksite physically receives material ->5a 

4b. DAASC receives Material Release Confirmation, 945A (AR_) and passes to EBS-> 4c 

4c. EBS receives Material Release confirmation and generates Interfund billing to customer ->END 

5a. DSS queries picklist table to receive picklist & staging updates->5b 

5b. DSS will use logic to check picklist to determine to store or deliver of material to the Artisan . >5b1 or 

5b2 
ADC 381 

Enclosure 6, Page 20 

FRC Note: For FRCs, any required inspection will be done after receipt and prior to delivery of material to the 

Artisan. Inspection will be based on the picklist local DSS IA will notify QA. DSS will close local manifest 

and generate the 870S with PD status when material is placed in the QA cage. 

5b1. If the picklist line does not reflect “E” use code, DSS IA worksite stores the material in Custody Storage 

to await callout by Artisan and generates 527R (D6A) to DAASC -> 6a 

5b2. For all picklists lines with E use code DSS will 

consolidate material 

create local manifest 

generate an PA Arrival Notification Status (870S) for assets received from network site->5c, 6a 

Additional delivery information will be obtained from picklist table 

5c. Upon delivery or system parameters, local manifest will be closed and generate a PD Delivery Notification 

Status (870S) to DAASC-> 6a 

DSS will obtain signature confirmation or badge number when required 

6a. DAASC receives the Material receipt, 527R (D6_) or 870S PA Arrival and PD Delivery Notification Status 

-> 6a1, 6a2 

For MAT, DAASC will put the 527R (D6_) or 870S PA Arrival and PD Delivery Notification Status in NSY 

Pull Queue 

6a1. IF13 will receive and process 870S, PA Arrival and PD Delivery Notification Status and completes due in 

MPRII and sends trigger to update DIFMS and creates the 527R (DRA) to DAASC -> 7, 8 

6a2. PS I/O F will pull the 527R (D6A) or the 870S, PA Arrival and PD Delivery Notification Status from the 

DAASC NSY Pull Queue and pass to MAT -> 6a3 

6a3. MAT receives the 527R (D6A) or the 870S; updates MAT and COST, and creates the 527R(DRA) that is 

sent to the PS I/O F, which pushes the 527R(DRA) to DAASC ->7a 

7a. DAASC receives, validates and routes the 527R (DRA) to EBS ->7b 

7b. EBS receives 527R (DRA) data and updates sales order appropriately ->END 

8. IF14 receives the trigger and updates DIFMS for MRP II ->END
ADC 381 

Enclosure 6, Page 21 

Note: NAVICP and Material for Nuclear support are routed from the DSS IA worksite receiving dock to the 

Nuclear SS/Staging and NAVICP 99 SS receiving dock without using the new DSS Manifest capability and the 

associated 870S transactions with arrival or departure status codes. All Nuclear or NAVICP material receipt 

processing is performed in MAT. 

Note: When request is for DLR item or another Service an A3_ will be generated, otherwise an A0_ will be 

generated. 

1. JMLs are completed in MRQT and forwarded to MAT. -> 2 

2. MAT receives the JMLs and determines whether a JML was prepared and released by the Nuclear 

Department. 

 * If the MRQT JML requirement and the assigned document number (V series for system assigned or Z series 

for emergent or urgent material requirements) identifies Originator Code 2305 (JML Block 99 = Nuclear 

Department), then MAT will continue the Nuclear JML processing logic-> 3 

3. MAT determines whether the requested item is NSY owned or NAVICP Managed (NSY: Future Use 

Material (FUM) , Nuclear Excess and Nuclear Shop Stores or NAVICP Shop Store: 1H, 3H, 1R, 5R). If Yes -

>3a, If No->4 

3a. MAT searches NSY owned inventories/NAVICP Shop Store and processes IAW the MAT Logic in sub 

process flows 9.3a (2011) or 9.3b (2012). The Outcomes of the sub processes are: 

 * If not available (Warehouse Refusal/NIS) and not NAVICP Managed, then the item requested is re-entered 

into the MAT processing logic. -> 4 

 * If NSY FUM/Nuclear Shop Stores (SS) and not NAVICP Managed, the JML Document Number is 

assigned/posted in MAT. -> END 
ADC 381 

Enclosure 6, Page 22 

 * If NAVICP Managed and greater than "S" days (a parameter to be set in MAT), then MAT will create a 

NAVICP Program Planned Requirement (PPR) and send it to DAASC. -> 6 

 * If NAVICP Managed and less than "S" days (a parameter to be set in MAT), then MAT will create a NSY 

511R (A3_) Funded Requisition and send it to DAASC. -> 6 

4. If not satisfied by previous steps, then MAT determines whether the requested item is DLA Owned. 

 * If yes, MAT will create a NSY 511R (A0_) Funded Requisition. ->6 

 * If no, MAT will continue processing the requested item. ->5 

5. By default, the remaining requested items are determined by MAT to be Other IM Owned. MAT will create 

a NSY 511R (A3_) Funded Requisition for release to DAASC. ->6 

6. The NSY’s PSI/OF takes all outbound transactions (511Rs & NAVICP PPRs->7, 527R (DRA)s & BK_s-

>15) and sends them to DAASC. ->7, 15 

7. DAASC receives 511R (A0_/A3_)s and NAVICP PPRs for processing. ->7a, 7b, 7c 

7a. DAASC validates the 511R (A3_) documents only and routes the 511R (A3_) documents or NAVICP PPRs 

to NAVICP. ->7a1 

7a1. NAVICP receives 511R (A3_)s & NAVICP PPRs. For 511R/A3_s, NAVICP creates a 940R (A5_) and 

corresponding status transaction, and sends them to DAASC. Additionally, NAVICP will use the PPRs with 

RDDs to plan redistribution or procurement actions to preposition NSY PPR requirements in MAT’s NAVICP 

Shop Store in the NSY. -> 8, Status Process 

7b. DAASC validates and routes 511R (A0_) documents to EBS for processing ->7b1 

7b1. EBS receives 511R (A0_) documents, creates a 940R (A5_) and corresponding status transaction and sends 

them to DAASC. ->8, Status Process 

7c. DAASC validates and routes 511R (A3_) documents to Other Service Inventory Managers (Other IM) ->7c1 

7c1. Other Service Inventory Managers (Other IM) receives 511R (A3_) documents, creates a 940R (A5_) and 

corresponding status transaction and sends them to DAASC. ->8, Status 

8. DAASC receives 940R (A5_) documents, validates and routes to: 

 * A Service warehouse activity or a DLA Network DSS site ->8a; 

 * The DSS IA Worksite that supports the NSY, when EBS has unprotected material (EBS “A” Purpose Code 

assets) available for issue. -> 9 

 * If the only DLA assets available are EBS Protected Assets (“E” Purpose Code) and the NSY 2305 funded 

requisition is high priority, then the Manual Breaching process will be executed to fulfill the requirement. -> 

Breaching (Manual) 

8a. A Service warehouse activity (e.g. Army Warehouse) or DSS Network Site receives the 940R (A5_) from 

the Inventory Manager and issues/ships the material to the NSY’s DSS IA Worksite and sends the 945A (AR_) 

via DAASC to the originating Inventory Manager with 856S shipment status sent to DAASC for the ordering 

NSY. -> 8b; 10 for 10a, 10b or 10c as appropriate; Status Process 

8b. The DSS IA Worksite receives material issued/shipped from a Service warehouse activity (e.g. Army 

Warehouse) or DSS Network Site and recognizes the Nuclear Engineering Material Support Department (NSY 

2305) requisition serial number series or NAVICP 87 and sorts the material for direct delivery to the Nuclear 

Shop Store/Staging/NAVICP Shop Store receiving dock. -> 9b 

9. The DSS IA Worksite receives the Inventory Manager’s 940R (A5_) document from DAASC and 

commences processing the Material Release Order (940R (A5_)) -> 9a 

9a. When the DSS IA Worksite processes the Inventory Manager’s 940R (A5_), the material is issued for 

delivery to the NSY’s Nuclear Shop Stores/Staging/NAVICP 87 Shop Store receiving dock. Additionally, a 

945A (AR_) is created and sent to DASSC for routing to the appropriate Inventory Manager and a 856S 

shipping status is created and sent to DAASC for routing to the appropriate NSY for MAT update. -> 9b 

9b. Material staged for the NSY’s Nuclear Shop Stores/Staging/NAVICP 87 Shop Store is delivered to their 

receiving dock. -> 9c 

9c. Material for NSY 2305 support is received from the DSS IA Worksite for receipt processing in MAT. -> 9d 

9d. Material for NSY 2305 is receipt processed in MAT and is either delivered to the artisan (“E” Use code) or 

is received in MAT for Nuclear Shop Stores, Staging or NAVICP 87 Shop Stores (Non “E” Use code). -> 13 

10. DAASC receives and validates the 945A (AR_) and 856S. ->10a, 10b, 10c, 10d 

10a, 10b and 10c,DAASC routes 945A (AR_) to the appropriate Inventory Manager (EBS, NAVICP or Other 

Inventory Managers) and 856S Shipping Status to the NSY Hold Queue for NSY retrieval. DAASC receives 

the MAT generated 527R (DRA), with new code indicating virtual receipt by the NSY or 527R (D4_/D6_ ) 

receipt and routes them to the appropriate Inventory Manager. 945A (AR_), 856S Shipping Status, 527R/DRA 

(receipt confirmation) or MILS DZAs to the appropriate Inventory Manager (10a, 10b, 10c) and an 870S (AE_) 

and 527R/DRA (receipt confirmation) placed in the NSY Hold Queue for NSY retrieval (10d). ->11a, 11b, 11c, 

12 

10c1 MAT’s NAVICP Shop Store in the NSY receives and commences processing the 940R (A5_). -> END 
ADC 381 

Enclosure 6, Page 23 

11. No process flow - block 11. This is a header only. -> 11a, 11b, 11c. 

11a, 11b, 11c. NAVICP, EBS, or Other Service systems receive and process the 945A (AR_) to update their 

files and bill the customer. -> END 

12. The NSY’s PSI/OF pulls 856S from the DAASC NSY Hold queue and delivers the 856S to MAT for 

processing. -> 13 

13. As a result of material received into MAT in step 9d, MAT generates and sends via DAASC 527R (D6_), 

527R (DRA) with new code indicating virtual receipt by the NSY, and 867i to the appropriate Inventory 

Manager as required. -> 13a, 13b ,13c 

13a. NAVICP receives and processes the 527R (D6_), 527R (DRA) with new code indicating virtual receipt by 

the NSY and 867i as appropriate for NSY material orders or MAT’s receipt of NAVICP’s directed 

prepositioned material. -> END 

13b. & 13c. EBS (13b) and Other Service Inventory Management Systems receives the 527R (D6_) and 527R 

(DRA) with new code indicating virtual receipt by the NSY, and process as appropriate. -> END 

14. For Repairable, MAT creates and releases a BK_ to PS I/O F, which sends it to DAASC ->15 

15. DAASC receives, validates and routes the BK_ transaction to eRMS for processing. Note: Navy ERP 1.1 

will replace steps 14 &15 by direct data entry into Navy ERP 1.1. -> END 
ADC 381 

Enclosure 6, Page 24 

1. Industrial site customer has an urgent need for material stored at DSS IA Worksite: 

1a. Customer takes necessary documentation (comparable to a 511R/A0_) to DSS IA worksite for issue DLA IA 

Material -> 2 

1b. Customer takes necessary documentation (comparable to a 940R/A5_ ) to DSS IA worksite for issue Navy 

IA Owned Material -> 2 

 NOTE: 1a and 1b for NSY sites the original Requisition Alert document number, suffix code, and JO/KO 

must be if material was requested originally on a JML included on documentation and on DSS entry. 

2. DLA personnel physically located at the DSS IA worksite enters Post-post action (SMOK screen) with 

additional data elements, as applicable into DSS ->2a, 3, 4 . 

2a. DSS IA Worksite personnel pull the material and customer leaves with the material ->END 

3. DSS IA Worksite sends the post-post transaction, 511R (C0_) for DLA owned material and 867I (D7_) for 

Navy Owned material to DAASC -> 3a, 

Note: Shipment and delivery status and material confirmation are generated by DSS and routed by DAASC to 

the appropriate material owner as indicated in Note 1 in Flow 9.4. 

3a. DAASC receives, validates, and routes the post-post transaction to EBS. -> 3b (for the 511R CO_) or to 3c 

for FRCs or 3d for NSYs (for the 867I D7_) 

3b. EBS receives 511R (C0_) and creates sales order ->END 

3c. FRC for Navy IA owned receives 867I (D7_). -> IF13 

3d. NSY for Navy IA owned receives 867I (D7_) -> PSIOF 

4. DSS IA Worksite sends Material Release Confirmation, 945A (AR_) -> 5a 

 Shipment status 856S (AS_) and 870S (AE_) with Delivery Status “PD” to DAASC -> 5a 
ADC 381 

Enclosure 6, Page 25 

 Note: For NSYs, 870S with “PD” status will indicate badge number of artisan who accepted delivery. 

5a. DAASC receives and validates the Material Release Confirmation 945A (AR_) and Shipment status, 856S 

(AS_) and 870S (AE_) based on media status code->5a1, 5a2 or 5a3 

5a1. DAASC distributes the Material Release Confirmation 945A (AR_) to EBS ->5a1a 

5a1a. EBS processes Material Release Confirmation, 945 (AR_) and bills customer -> END 

5a2. DAASC routes the Shipment Status, 856S (AS_) and 870S (AE_) with Delivery Status “PD” to IF13 -

>5a2a 

5a2a. IF13 processes virtual receipt (see Note 1 on chart) and issue into MRPII, creates DRA, 527R (for DLA 

owned material) and updates DIFMS ->6a 

5a3. DAASC routes the shipment status, 856S (AS_) and 870S (AE_) with Delivery Status “PD” to NSY Hold 

queue ->5a3a 

5a3a. NSY PSI/OF passes shipment status, 856S (AS_) and 870S (AE_) with Delivery Status “PD” to MAT -

>5a3b 

5a3b. MAT updates walk thru documents for virtual receipt (see Note 1 on chart), creates DRA, 527R (for DLA 

owned material) and COST -> 6b 

6. DRA processing: 

6a. IF13 passes the Receipt acknowledgement, 527R (DRA) to DAASC. ->6b 

6b. MAT passes the 527R (DRA) to DAASC through PS I/O F -> 6c 

6c. DAASC receives, validates, and routes the 527R (DRA) to EBS. ->6d 

6d. EBS post the 527R (DRA) updating sales order ->END
ADC 381 

Enclosure 7, Page 1 

Enclosure 7, DLMS Supplement (DS) Revisions 

Section A - DS 511R Requisition 

Item 

# 

Location DS 511R Requisition 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 5:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP 

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BR01/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 1/BR06/20 Add qualifier and DLMS note:

83 Future 

DLMS Note: 1. Used by Navy industrial activities (IAs) to identify a 

Requisition Alert allowing stock positioning or procurement action in 

response to the forecasted future funded requirement. The requisition 

alert is an unfunded requirement. Use with BR02 Qualifier A0 or BN 

only. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the 

requisition alert from the 

standard requisition. 

4. 1/N101/70 Update DLMS notes for existing qualifiers ZL:

ZL Party Passing the Transaction 

DLMS Note: Use in passing orders and referral orders to identify the 

organization forwarding the transaction for further processing. Also 

used to identify the party transmitting a requisition image transaction.

Administrative corrections. 

Staffing Note: DLMSO 

understanding is that 

requisition image transactions 

by a unique qualifier, but the 

data mapping will be 

consistent to the standard 

requisition and this ZL 

mapping is not required. 

5. 2/N901/20 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify the associated Job Order (JO)

Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 2 

Item 

# 

Location DS 511R Requisition 

Revision 

Reason 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

TN Transaction Reference Number 

DLMS Note: 1. Must use to identify the transaction number of the 

requisition. This is the document number. 

2. When used in the requisition alert (BR06=83), this will be the 

requisition alert document number. The requisition alert document 

number is an authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used by Navy Shipyards to associate the funded requisition with a 

previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

WP Warehouse Pick Ticket Number 

DLMS Note: 1. Use to identify the picklist control number assigned 

to identify a specific job for which materials are being requisitioned 

and assembled together in support of planned maintenance. 

2. Cite the picklist control number in N903 due to field length. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Staffing Note: Delivery 

Priority Code relocated to the 

LQ segment. See below. 

Staffing Note: Qualifier 

PWC not used on original 

requisition alert because the 

requisition alert document 

number is mapped to the 

Qualifier TN when only one 

document number is included 

in the transaction. 

6. 2/N903/20 Mark Data Element N903 as Used Data Element supports field 

length for picklist control 

number 

7. 2/N907-01/20 Add DLMS new note 4 to existing qualifier:

W8 Suffix 

DLMS Note: 1. Use with N901 Code TN to identify the document number 

suffix. Use is limited to when the transaction is identified as a referral order with 

BR02 transaction type code BN and is referring a quantity less than the original 

requisition quantity to another supply source. 

2. Also authorized on an Intra-Army basis with BR02 transaction type code A0, 

BR06 action code “J” and N901 code TN for identification of the post-post 

partial issue of material by Army Single Stock Fund activities. 

3. Use with N901 Code F8 to identify the prior requisition document number 

suffix if applicable. Authorized DLMS enhancement for BRAC IMSP only. 

Refer to ADC 352 and ADC 359.

4. When used in the requisition alert (BR06=83), or when used in 

association with the Requisition Alert Document Number (Qualifier 

PWC, above), this will be the requisition alert document suffix. Use 

with BR02 Qualifier BN only. The requisition alert document number 

suffix is an authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 3 

Item 

# 

Location DS 511R Requisition 

Revision 

Reason 

8. 2/PO106/30 Revise the data element level not and add the following qualifiers and 

DLMS notes:

DLMS Note: 1. Use only one of codes A1, A2, A4, FB, FS, FT, MG, SW, YP 

or ZZ to identify the material requisitioned. Must use the National Stock 

Number (NSN) (code FS) when known, except when appropriate for brand 

name subsistence items identified by a Subsistence Identification Number. 

2. For DLMS use, only the following codes are authorized. 

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. When the unit of use indicator is included (1/BR01/20=ZZ), the 

NSN ordered will be interpreted as a unit of use requirement so that 

the order may be processed against the associated DLA-assigned LSN. 

The requested quantity is expressed in the unit of use for the LSN in 

lieu of the unit of issue for the identified NSN. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral 

II requirements. 

9. 2/PO108/30 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is identified 

as the primary materiel identification (applicable to post-post process). 

Authorized DLMS enhancement under DLA industrial activity 

support agreement. 

Cross-reference NSN would 

only be used in post-post 

situation where the transaction 

is prepared by DSS. 

10. 2/DD02/60 Update DLMS notes for existing qualifiers 74:

74 Demand Code 

DLMS Note: 1. Must use to identify the applicable Demand Code 

indicating whether the demand is recurring or nonrecurring. 

2. Demand code added to the Referral Order (A4_) format by Approved 

MILSTRIP Change 44.

3. Stratification of quantity by demand code is a potential future

DLMS enhancement; see introductory DLMS note 3a.

Administrative update for 

clarification (revision not 

associated with BRAC usage). 

11. 2/DD10/60 Update DLMS notes for existing qualifiers 98: 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code used 

by Naval IAs to identify the use of the materiel. 

 2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 4 

Item 

# 

Location DS 511R Requisition 

Revision 

Reason 

12. 2/LQ01/140 Add the following qualifiers and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code 

indicating the level of quality inspection to which the item must be 

procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

EWR Evaluate Work Candidate Reason Lookup 

DLMS Note: 1. Use to identify Requirement Churn Reason Code to 

identify material orders required by the industrial site to complete 

planned work above what was originally identified during the preplanned process, ordered and delivered after the start of the 

availability. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use to identify a specialized purpose for which the 

requisition is submitted.

2. Under DLSS, this is the first position of the document serial number 

within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note. 

KJ Assured Delivery Indicator 

DLMS Note: 1. Use to indicate the Delivery Priority Code for 

material which has an urgency of need within the maintenance shop 

and must be delivered within one hour of receipt of the issue request. 

Value will be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral 

II requirements. 

13. 2/N101/180 Add the following qualifier and DLMS note:

DZ Delivery Zone 

DLMS Note:  1. Use to provide the DELIVERY LOCATION 

indicating where the material is to be staged/stored. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

14. 2/N101/180 Update DLMS notes for existing qualifiers XN:

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between Service industrial/maintenance sites and 

DLA to identify the Shop Service Center (SSC) associated with a 

requisition. Also used to identify a Shop Store. 

2. This may be used in the basic requisition, requisition alert or in the Post-Post 

(DI Code C0A) DLMS 511R submitted to DLA. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 5 

Item 

# 

Location DS 511R Requisition 

Revision 

Reason 

15. 2/N103/180 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements. 

Section B - DS 511M Requisition Modification 

Item 

# 

Location DS 511M Requisition Modification 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 5:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP 

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BR01/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 1/BR06/20 Add qualifier and DLMS note:

83 Future 

DLMS Note: 1. Used by Navy industrial activities (IAs) to identify a 

Requisition Alert allowing stock positioning or procurement action in 

response to the forecasted future funded requirement. The requisition 

alert is an unfunded requirement. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the 

requisition alert modification 

from the standard requisition 

modification. 

4. 2/N901/20 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify, or to modify, the Job Order (JO) 

Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify, or to modify, the Key Operation (KO) 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 6 

Item 

# 

Location DS 511M Requisition Modification 

Revision 

Reason 

Number associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

TN Transaction Reference Number 

DLMS Note: 1. Must use to identify the transaction number of the 

requisition. This is the document number. 

2. When used in the requisition alert (BR06=83), this will be the 

requisition alert document number. The requisition alert document 

number is an authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used by Navy Shipyards to associate the funded requisition 

modification with a previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

WP Warehouse Pick Ticket Number 

DLMS Note: 1. Use to identify, or to modify, the picklist control 

number assigned to identify a specific job for which materials are 

being requisitioned and assembled together in support of planned 

maintenance. 

2. Cite the picklist control number in N903 due to field length. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

5. 2/N903/20 Mark Data Element N903 as Used Data Element supports field 

length for picklist control 

number 

6. 2/N907-01/20 Add DLMS new note 4 to existing qualifier:

W8 Suffix 

DLMS Note: 1. Use with N901 code TN to identify the document number 

suffix. Use is limited to when the initial 511R transaction is identified as a 

referral order with BR02 transaction type code BN and is referring a quantity 

less than the original requisition quantity to another supply source, with the 

exception of a modifications from the supply source to a procurement activity. 

For these modifications, enter the suffix as shown in the procurement request; 

otherwise leave blank. 

2. Also authorized on an Intra-Army basis with N901 code TN for identification 

of the post-post partial issue of material by Army Single Stock Fund activities 

when the initial 511R transaction BR02 transaction type code is A0 and BR06 

action code is “J”. 

3. Use with N901 Code F8 to identify the Prior requisition document number 

suffix if applicable. Authorized DLMS enhancement for BRAC IMSP only. 

Refer to ADC 352 and ADC 359.

4. When used in modification of the requisition alert (BR06=83), or 

when used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. Use with BR02 Qualifier BN only. The requisition 

alert document number suffix is an authorized DLMS enhancement 

under DLA industrial activity support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 7 

Item 

# 

Location DS 511M Requisition Modification 

Revision 

Reason 

7. 2/PO106/30 Revise the data element level note and add the following qualifiers and 

DLMS notes:

DLMS Note: 1. Use only one of codes A1, A2, A4, FB, FS, FT, MG, SW, YP 

or ZZ to identify the material requisitioned. Must use the National Stock 

Number (NSN) (code FS) when known, except when appropriate for brand 

name subsistence items identified by a Subsistence Identification Number. 

2. For DLMS use, only the following codes are authorized.

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. When the unit of use indicator is included (1/BR01/20=ZZ), the 

NSN ordered will be interpreted as a unit of use requirement so that 

the order may be processed against the associated DLA-assigned LSN. 

The requested quantity is expressed in the unit of use for the LSN in 

lieu of the unit of issue for the identified NSN. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral 

II requirements. 

8. 2/PO108/30 Add the following qualifier and DLMS notes:

FS National Stock Number

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is identified 

as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. Refer 

to ADC 381.

Cross-reference NSN would 

only be used in post-post 

situation where the transaction 

is prepared by DSS.

Modification not applicable to 

the post-post scenario. 

9. 2/DD02/60 Update DLMS notes for existing qualifiers 74:

74 Demand Code 

DLMS Note: 

1. Must use to identify, or to modify, the applicable Demand Code 

indicating whether the demand is recurring or nonrecurring. 

2. Demand code added to the Referral Order (A4_) format by Approved 

MILSTRIP Change 44.

3. Stratification of quantity by demand code is a potential future

DLMS enhancement; see introductory DLMS note 3a. 

Administrative update for 

clarification (revision not 

associated with BRAC usage). 

10. 2/DD10/60 Update DLMS notes for existing qualifiers 98: 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify, or to modify, the Reason for 

Requisitioning Code. Used by Naval IAs specifying use of the 

materiel requirement. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral 

II requirements. 

11. 2/LQ01/140 Add the following qualifiers and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify, or to modify, the Quality Inspection 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 8 

Item 

# 

Location DS 511M Requisition Modification 

Revision 

Reason 

Code indicating the level of quality inspection to which the item must 

be procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

EWR Evaluate Work Candidate Reason Lookup 

DLMS Note: 

1. Use to identify, or to modify, the Requirement Churn Reason Code 

to identify material orders required by the industrial site to complete 

planned work above what was originally identified during the preplanned process, ordered and delivered after the start of the 

availability. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 

1. Use to identify a specialized purpose for which the requisition is 

submitted. 

2. Under DLSS, this is the first position of the document serial number 

within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note. 

KJ Assured Delivery Indicator 

DLMS Note: 

1. Use to identify, or modify, the Delivery Priority Code for material 

which has an urgency of need within the maintenance shop and must 

be delivered within one hour of receipt of the issue request. Value will 

be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

12. 2/N101/180 Add the following qualifier and DLMS note:

DZ Delivery Zone 

DLMS Note:  1. Use to provide the DELIVERY LOCATION 

indicating where the material is to be staged/stored. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

13. 2/N101/180 Update DLMS notes 1 and 3 for existing qualifiers XN:

XN Planning/Maintenance Organization 

DLMS Note: 

1. Use between Service industrial/maintenance sites and DLA to 

identify, or to modify, the Shop Service Center (SSC) or Shop Store. 

2. Modifier transactions may not be used to change this field.

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements. 

Allows modification of SSC, 

or Shop Store 
ADC 381 

Enclosure 7, Page 9 

Item 

# 

Location DS 511M Requisition Modification 

Revision 

Reason 

14. 2/N103/180 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: 

Use with N101 Code XN to identify the Shop Service Center or Shop 

Store. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements. 

Section C - DS 869A Requisition Inquiry/Supply Assistance Request

Item 

# 

Location DS 869A Requisition Inquiry/Supply 

Assistance Request Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 5:

- ADC 381, Procedures and Additional Data Content 

supporting Requisitions, Requisition Alerts, and Unit of Use 

Requirements under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BSI07/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 1/BSI09/20 Add the following qualifier and DLMS note:

83 Future 

DLMS Note: 1. Used by Navy industrial activities (IAs) to identify 

a Requisition Inquiry/Supply Assistance Request on a Requisition 

Alert allowing stock positioning or procurement action in response 

to the forecasted future funded requirement. The requisition alert 

is an unfunded requirement. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the 

requisition alert follow-up from 

the standard requisition followup. 
ADC 381 

Enclosure 7, Page 10 

Item 

# 

Location DS 869A Requisition Inquiry/Supply 

Assistance Request Revision 

Reason 

4. 2/LIN02/050 Revise the data element level note and add the following qualifiers 

and DLMS notes:

DLMS Note: Use only one of codes A1, A2, A4, FB, FS, MG, SW,

YP, or ZZ to identify the material as indicated in the most recent 

status transaction. 

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. When the Unit of Use Indicator is included (BSI07=ZZ), the 

NSN will be interpreted as a unit of use requirement. Unit of use 

is an authorized DLMS enhancement under DLA industrial 

activity support agreement. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 

5. 2/REF01/105 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify the Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used by Navy Shipyards to associate the funded requisition 

Inquiry/Supply Assistance Request with a previously submitted 

requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

TN Transaction Reference Number 

DLMS Note: 1. Must use in 2/HL/010 transaction loops to identify 

a transaction number assigned to the transaction. This is the 

document number. 

2. When used with the requisition alert indicator (BSI09=83), this 

will be the requisition alert document number. The requisition 

alert is an authorized DLMS enhancement under DLA industrial 

Supports Navy BRAC Spiral II 

requirements. 

Staffing Note: Verify 

Requisition Alert Document 

Number/Suffix is applicable to 

the 869A. 
ADC 381 

Enclosure 7, Page 11 

Item 

# 

Location DS 869A Requisition Inquiry/Supply 

Assistance Request Revision 

Reason 

activity support agreement. Refer to ADC 381. 

WP Warehouse Pick Ticket Number 

DLMS Note: 1. Use to identify the picklist control number 

assigned to identify a specific job for which materials are being 

requisitioned and assembled together in support of planned 

maintenance. 

2. Cite the picklist control number in REF03 due to field length. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

6. 2/REF04-01/105 Add DLMS note 2 to existing qualifier W8:

W8 Suffix 

DLMS Note: 1. Use with REF01 code TN to identify a transaction 

number suffix when the original requisition has been split. 

2. When used with the Requisition Alert Indicator (BSI09=83), or 

when used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. The Requisition Alert Document Number 

Suffix is an authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 

7. 2/N101/110 Revised DLMS notes for existing qualifier XN:

XN Planning/Maintenance Organization 

DLMS Note:

1. Use between Service industrial/maintenance sites and DLA to 

identify the Shop Service Center (SSC) or Shop Store. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Expands existing usage for 

Navy BRAC Spiral II 

requirements. 

8. 2/N103/110 Revise DLMS Note for existing qualifier 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: 

Use with N101 Code XN to identify the Shop Service Center or 

Shop Store. Refer to ADC 284A. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements. 

9. 2/LQ01/180 Add the following qualifiers and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code 

indicating the level of quality inspection to which the item must be 

procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

EWR Evaluate Work Candidate Reason Lookup 

DLMS Note: 1. Use to identify Requirement Churn Reason Code 

to identify material orders required by the industrial site to 

complete planned work above what was originally identified 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 12 

Item 

# 

Location DS 869A Requisition Inquiry/Supply 

Assistance Request Revision 

Reason 

during the pre-planned process ordered and delivered after the 

start of the availability. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

KJ Assured Delivery Indicator 

DLMS Note: 

1. Use to indicate the Delivery Priority Code for material which 

has an urgency of need within the maintenance shop and must be 

delivered within one hour of receipt of the issue request. Value 

will be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 

1. Use to identify a specialized purpose for which the requisition is 

submitted. 

2. Under DLSS, this is the first position of the document serial 

number within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note.

Section D - DS 869C Requisition Cancellation

Item 

# 

Location DS 869C Requisition Cancellation 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 3:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BSI07/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. When included, the quantity and unit of measure 

values associated with this transaction are applicable to the unit of 

use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 
ADC 381 

Enclosure 7, Page 13 

Item 

# 

Location DS 869C Requisition Cancellation 

Revision 

Reason 

3. 2/BSI03/20 Add the following qualifier and DLMS note:

CO All Orders – Unshipped Items 

DLMS Note: 

1. Used as a Requisition Alert Indicator by Navy industrial 

activities (IAs) to identify a Requisition Alert Cancellation. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the 

requisition alert cancellation from 

the standard requisition 

cancellation. 

Staffing Note: BSI03 Qualifier 

CO is used rather than the BSI09 

83 Future (the qualifier value 

used in the requisition and the 

requisition modification), because 

mapping to the BSI09 would 

preclude future use of the DLMS 

enhancement for universal and 

mass cancellation applicable to 

requisition alerts. 

4. 2/REF01/105 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

TN Transaction Reference Number 

DLMS Note: 1. Must use to identify the transaction number of the 

requisition to be cancelled. 

2. When used in cancellation of the requisition alert (BSI03=CO), 

this will be the requisition alert document number. The 

requisition alert document number is an authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used by Navy Shipyards to associate the funded requisition 

cancellation with a previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 14 

Item 

# 

Location DS 869C Requisition Cancellation 

Revision 

Reason 

5. 2/REF04-01/105 W8 Suffix 

DLMS Note: 1. Use with REF01 code TN to identify a transaction 

number suffix when the original requisition has been split. 

2. When used in cancellation of the requisition alert (BSI03=CO), 

or when used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. The requisition alert document number suffix is 

an authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

6. 2/LIN02/050 Revise the data element level note and add the following qualifiers 

and DLMS notes:

DLMS Note: Use only one of codes A1, A2, A4, FB, FS, MG, SW or 

YP to identify the material shipped. Must use the National Stock 

Number (NSN) when known, except, when appropriate, for brand 

name subsistence items identified by a Subsistence Identification 

Number. 

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. When the unit of use indicator is included (1/BSI07/20=ZZ), 

the NSN cancelled will be interpreted as a unit of use requirement 

so that the cancellation may be processed against the associated 

LSN. The cancelled quantity is expressed in the unit of use for the 

LSN in lieu of the unit of issue for the identified NSN. 

Authorized DLMS enhancement under DLA industrial activity 

support agreement. 

SW Stock Number 

DLMS Note: 

1. Use to identify the local stock number (LSN). 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 

7. 2/N101/110 Add the new qualifier and DLMS notes:

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between Service industrial/maintenance sites 

and DLA to identify the Shop Service Center (SSC) or Shop Store. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 

Staffing Note: Added to 

transaction for consistency, 

although not requested in 

Enclosure 1 matrix.

8. 2/N103/110 Add the new qualifier and DLMS notes:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 15 

Item 

# 

Location DS 869C Requisition Cancellation 

Revision 

Reason 

9. 2/LQ01/180 Update DLMS notes for existing qualifiers AJ:

AJ Utilization Code 

DLMS Note: 

1. Use to identify a specialized purpose for which the requisition is 

submitted. 

2. Under DLSS, this is the first position of the document serial 

number within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note. 

Supports Navy BRAC Spiral II 

requirements. 

Section E - DS 869F Requisition Follow-Up 

Item 

# 

Location DS 869F Requisition Follow-Up 

Revision 

Reason 

1. DLMS 

Introductory Notes 

Added ADC 381 to DLMS Introductory note 5:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BSI07/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 2/BSI09/20 Open BSI09 and add the following qualifier and DLMS note:

83 Future 

DLMS Note: 1. Used by Navy industrial activities (IAs) to identify a 

follow-up on a Requisition Alert allowing stock positioning or 

procurement action in response to the forecasted future funded 

requirement. The requisition alert is an unfunded requirement. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the 

requisition alert follow-up from 

the standard requisition followup. 
ADC 381 

Enclosure 7, Page 16 

Item 

# 

Location DS 869F Requisition Follow-Up 

Revision 

Reason 

4. 2/REF01/105 Add the following qualifier and revise DLMS notes:

DLMS Note: 1. In 2/HL/010 transaction loops, use only one of codes 

1I, EQ, FQ, MF, NS, S6, WL, ABV, or XD to identify the material 

requisitioned. Must use the National Stock Number (NSN) when 

known, except, when appropriate for brand name subsistence items 

identified by a Subsistence Identification Number. 

NS National Stock Number 

DLMS Note: 1. Must use in 2/HL/010 transaction loops to identify 

the National Stock Number (NSN) when known. Use to identify the 

NSN. 

2. When the unit of use indicator is included (1/BSI07/20=ZZ), the 

NSN ordered will be interpreted as a unit of use requirement so that 

the order may be processed against the associated DLA-assigned 

LSN. The requested quantity is expressed in the unit of use for the 

LSN in lieu of the unit of issue for the identified NSN. Authorized 

DLMS enhancement under DLA industrial activity support 

agreement. 

S6 Stock Number 

DLMS Note: 1. Use in 2/HL/010 transaction loops to identify the 

publication stock number. Use to identify the local stock number 

(LSN). 

2. Applicable to Navy IAs requisitions and requisition alerts. May 

be used for identification of LSNs for part-numbered items in lieu of 

a part-numbered requisition. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

ABV Book Number 

DLMS Note: Use for publication stock number. This is a DLMS 

enhancement for future use.

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

TN Transaction Reference Number 

DLMS Note: 

Supports Navy BRAC Spiral II 

requirements. 

Staffing Note: The 869F 

previously assigned the S6 

qualifier as a DLMS 

enhancement for the publication 

stock number. Since this was a 

future enhancement, the S6 

qualifier is re-assigned for the 

local stock number for 

consistency in the mapping for 

Navy BRAC. The publication 

stock number is re-assigned to 

Qualifier ABV, Book Number, 

as a placeholder for future use. 
ADC 381 

Enclosure 7, Page 17 

Item 

# 

Location DS 869F Requisition Follow-Up 

Revision 

Reason 

1. Must use in 2/HL/010 transaction loops to identify a transaction 

number assigned to the transaction. This is the document number. 

2. When used in the requisition alert follow-up (BSI09=83), this will 

be the requisition alert document number. The requisition alert is 

an Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used by Navy Shipyards to associate the funded requisition 

follow-up with a previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

WP Warehouse Pick Ticket Number 

DLMS Note: 1. Use to identify the picklist control number assigned 

to identify a specific job for which materials are being requisitioned 

and assembled together in support of planned maintenance. 

2. Cite the picklist control number in REF03 due to field length. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

5 2/REF04-01/ 

105 

W8 Suffix 

DLMS Note: 1. Use with 2/REF/105 REF01 code TN to identify the 

document number suffix. Use is restricted to when initial 511R is a 

referral order identified with BR02 transaction type code BN. 

2. Also authorized on an Intra-Army basis for identification of the 

post-post partial issue of material by Army Single Stock Fund 

activities. This use is allowed when the initial 511R is a requisition 

identified with BR02 transaction type code A0 and BR06 action code 

is “J”. 

3. Use with REF01 Code F8 to identify the prior requisition document 

number suffix if applicable. Authorized DLMS enhancement for 

BRAC IMSP only. Refer to ADC 352 and ADC 359. 

4. When used in the requisition alert follow-up (BSI09=83), or when 

used in association with the Requisition Alert Document Number 

(Qualifier PWC, above), this will be the requisition alert document 

suffix. The Requisition Alert Document Number Suffix is an 

Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 

6. 2/LQ01/180 Add the following qualifiers and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code 

indicating the level of quality inspection to which the item must be 

procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

EWR Evaluate Work Candidate Reason Lookup 

DLMS Note: 1. Use to identify Requirement Churn Reason Code to 

identify material orders required by the industrial site to complete 

planned work above what was originally identified during the preSupports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 18 

Item 

# 

Location DS 869F Requisition Follow-Up 

Revision 

Reason 

planned process ordered and delivered after the start of the 

availability. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use to identify a specialized purpose for which the 

requisition is submitted. 

2. Under DLSS, this is the first position of the document serial number 

within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note 4a. 

KJ Assured Delivery Indicator 

DLMS Note: 1. Use to indicate the Delivery Priority Code for 

material which has an urgency of need within the maintenance shop 

and must be delivered within one hour of receipt of the issue request. 

Value will be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

7. 2/N101/110 Add the following qualifier and DLMS note:

DZ Delivery Zone 

DLMS Note:  1. Use to provide the DELIVERY LOCATION 

indicating where the material is to be staged/stored. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

8. 2/N101/110 Update DLMS notes for existing qualifiers XN:

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between Service industrial/maintenance sites and 

DLA to identify the Shop Service Center (SSC), or Shop Store. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381. 

Expands existing usage for Navy 

BRAC Spiral II requirements. 

9. 2/N103/110 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for Navy 

BRAC Spiral II requirements. 
ADC 381 

Enclosure 7, Page 19 

Section F - DS 846I Asset Status Inquiry/ Report 

Item 

# 

Location DS 846I Asset Status Inquiry/ Report 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 6:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 2/BIA01/010 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 2/LIN02/10 Add new DLMS notes to qualifier FS and add new qualifier SW with 

DLMS notes:

DLMS Note: 1. Use only one of A1, A2, A4, FB, FS, MG, SW, YP 

or ZR to identify the item reported. Must use National Stock Number 

(NSN) when known except when appropriate brand name subsistence 

items are identified by the Subsistence Identification Number or 

when industrial activity materiel is identified by Local Stock 

Number or Material Control Tracking (MCT) Tag Number. 

FS National Stock Number 

DLMS Note: Use to identify the NSN. 

SW Stock Number 

DLMS Note: 

1. Use to identify the local stock number (LSN). 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral 

II requirements. 

4. 2/LIN04/10 Add new qualifier and DLMS note:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is 

identified as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Refer to ADC 381. 
ADC 381 

Enclosure 7, Page 20 

Section G - DS 870S Supply Status 

# Location DS 870S Supply Status Revision Reason 

1. DLMS Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 4:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes included 

in the DLMS Supplement 

2. 1/BSR11/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of use 

requirements. Navy BRAC sites 

will requisition using the NSN; 

however the unit of measure and 

quantity are applicable to the unit 

of use. 

3. 2/REF01/87 Added new qualifier CO and associated notes:

CO Customer Order Number 

DLMS Note: 

1. Use to identify the Customer Order Acceptance Record (COAR) 

applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

Supports Navy BRAC Spiral II 

requirements. 

4. 2/REF01/87 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used in support of Navy Shipyards to associate the funded 

requisition with a previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

TN Transaction Reference Number 

Federal Note: Must use to identify the customer assigned transaction 

number.

DLMS Note: 1. This is the document number. 

2. When status is applicable to a requisition alert, this field will 

perpetuate the alert document number. The requisition alert is an 

Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 21 

# Location DS 870S Supply Status Revision Reason 

5. 2/REF04-01 Add the following qualifier and DLMS Note:

W8 Suffix 

DLMS Note: 1. When used in association with the Requisition Alert 

Document Number (Qualifier PWC, above), this will be the 

requisition alert document suffix. 

2. The Requisition Alert Document Number Suffix is an Authorized 

DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 

6. 2/N101/90 Update DLMS notes for existing qualifiers XN:

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between Service industrial/maintenance sites and 

DLA to identify the Shop Service Center (SSC) or Shop Store.

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381. 

Expands existing usage for Navy 

BRAC Spiral II requirements. 

7. 2/N103/90 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for Navy 

BRAC Spiral II requirements 

8. 2/PO105/150 Add new qualifier UM and DLMS Note:

UM Price per Unit of Measure 

DLMS Note: 1. Use with Unit of Use Indicator (BSR11=ZZ) to 

identify the unit price applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 

9. 2/PO106/150 Revise the data element level note and add the following qualifiers and 

DLMS note:

DLMS Note: Use one of codes A1, A2, A4, FB, FS, FT, MG, SW, YP 

ZR, or ZZ to identify the material which will be provided as indicated 

by the status code. Must use the National Stock Number (NSN) when 

known, except when appropriate brand name subsistence items are 

identified by the Subsistence Identification Number or when 

maintenance/industrial activity materiel is identified by Local Stock 

Number or Material Control Tracking (MCT) Tag Number.

FS National Stock Number 

DLMS Note: Use to identify the NSN. 

ZR Service Control Identification 

DLMS Note: 1. Use to identify Material Control Tracking (MCT) 

Tag Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN (with 1/BSR11/20=ZZ), the 

applicable NSN will be included for cross-reference (at P0110-11). 

May also be used for identification of LSNs assigned for partnumbered item requisitioning. 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 22 

# Location DS 870S Supply Status Revision Reason 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

10. 2/PO110/150 Add the following qualifiers and DLMS notes:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included (1/BSR11/20=ZZ) and the Local Stock Number 

(LSN) is identified as the primary materiel identification. Authorized 

DLMS enhancement under DLA industrial activity support 

agreement. 

RV Repair Tag Number

DLMS Note: Use with Code ZR to identify the MCT tag number 

suffix.

When a unit of use LSN is 

identified above, the NSN will be 

included here. 

11. 2/LQ01/145 Add the following qualifiers and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code 

indicating the level of quality inspection to which the item must be 

procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

EWR Evaluate Work Candidate Reason Lookup 

DLMS Note: 1. Use to identify Requirement Churn Reason Code to 

identify material orders required by the industrial site to complete 

planned work above what was originally identified during the preplanned process ordered and delivered after the start of the 

availability. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use to identify a specialized purpose for which the 

requisition is submitted. 

2. Under DLSS, this is the first position of the document serial number 

within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

4. DLMS enhancement; see introductory DLMS note 3a. 

KJ Assured Delivery Indicator 

DLMS Note: 

1. Use to indicate the Delivery Priority Code for material which has 

an urgency of need within the maintenance shop and must be 

delivered within one hour of receipt of the issue request. Value will 

Staffing Note: LQ qualifiers 

added to supply status for 

consistency. 
ADC 381 

Enclosure 7, Page 23 

# Location DS 870S Supply Status Revision Reason 

be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Section H - DS 856S Shipment Status

# Location DS 856S Shipment Status Revision Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 3:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BSN01/0200 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. This applies when the 

materiel identification is by Local Stock Number assigned for unit of 

use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 2/LIN02/0200 Revise the data element level note 1and add the following qualifier and 

DLMS note:

1. Use one of codes A1, A2, A4, FB, FS, FT, MG, NN, SW, YP ZR, or 

ZZ to identify the materiel shipped. Must use National Stock Number 

(NSN) when known, except, when appropriate, brand name subsistence 

items are identified by the subsistence identification number or when 

maintenance/industrial activity materiel is identified by Local Stock 

Number or Materiel Control Tracking (MCT) tag number. An 

exception is also authorized for CAV Shipment Status where materiel 

may be identified by the National Item Identification Number (NIIN) 

when the Federal Supply Code (FSC) is not available. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN (with 1/BSN01/0200=ZZ), the 

applicable NSN will be included for cross-reference (at LIN04-05). 

May also be used for identification of LSNs assigned for partnumbered item requisitioning. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

ZR Service Control Identification 

DLMS Note: Use to identify Materiel Control Tracking (MCT) tag 

number. The MCT tag number is an authorized DLMS enhancement 

under DLA industrial activity support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 24 

# Location DS 856S Shipment Status Revision Reason 

4. 2/LIN04/0200 Add the following qualifiers and DLMS notes:

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator 

is included (1/BSN01/0200=ZZ) and the Local Stock Number (LSN) is 

identified as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

RV Repair Tag Number

DLMS Note: Use with Code ZR to identify the MCT tag number 

suffix.

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

5. 2REF01/1500 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance Record 

(COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document Number 

when status is provided on the associated funded requisition. 

2. Used in support of Navy Shipyards to associate the funded 

requisition with a previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PA Price Area Number 

DLMS Note: 1. Use for shipments to disposal to indicate actual or 

estimated pricing information. 

2. Available for all other shipment status as an optional data field to 

perpetuate the actual or estimated unit price from the associated supply 

status or material release order. This is an authorized DLMS 

enhancement. 

3. A field size exceeding 7 positions (5 digits dollars and 2 digits cents) 

may not be received or understood by the recipient’s automated 

processing system. 

4. Under DLMS the unit price will be expressed as R9.2. Authorized 

DLMS migration enhancement; see introductory DLMS 2f. 

5. Use to identify the unit of use price when the unit of use indicator 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 25 

# Location DS 856S Shipment Status Revision Reason 

(1/BSN01/0200) is present. Authorized DLMS enhancement under 

DLA industrial activity support agreement. Refer to ADC 381. Unit of use price was not 

requested, but DSS provides unit 

price on DLMS 856S as a 

DLMS enhancement.

6. 2/REF04-

01/1500 

Add DLMS Note 2 to existing qualifier W8

W8 Suffix 

DLMS Note: 1. Use with REF01 code TN to identify the transaction 

number suffix.

2. When used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. The Requisition Alert Document Number Suffix is 

an authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 

7. 2/N101/2200 Revise DLMS note 2 for existing qualifier XN: 

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between Service industrial/maintenance sites and 

DLA to identify the Shop Service Center (SSC) or Shop Store.

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381.

Supports Navy BRAC Spiral II 

requirements. 

8. 2/N103/2200 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for Navy 

BRAC Spiral II requirements 

9. 2/LQ01/3500 Add the following qualifiers and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code indicating 

the level of quality inspection to which the item must be procured and 

inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use to identify a specialized purpose for which the 

requisition is submitted. 

2. Under DLSS, this is the first position of the document serial number 

within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note 2a. 

R3 Delivery Rank (Priority) 

Staffing Note: All requisitionrelated LQ qualifiers added to 

shipment status for consistency. 
ADC 381 

Enclosure 7, Page 26 

# Location DS 856S Shipment Status Revision Reason 

DLMS Note: 1. Use to indicate the Delivery Priority Code for material 

which has an urgency of need within the maintenance shop and must 

be delivered within one hour of receipt of the issue request. Value will 

be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Section I - DS 940R Material Release 

Item 

# 

Location DS 940R Material Release 

Revision 

Reason 

 1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 6:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/W0501/0200 Add new qualifier and DLMS note:

Z Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

3. At this time a local code ‘Z’ is established for use in 940R, version 

4030. A data maintenance action will be submitted for establishment 

of ‘Z-Mutually Defined’ in a future version.

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 2/W0104/0200 Revise the data element level note 1and add the following qualifiers 

and DLMS notes:

DLMS Note: Use only one of codes A1, A2, A4, FB, FS, FT, MG, 

SW, YP, ZR, or ZZ to identify the material. Must use National Stock 

Number (NSN) when known, except when appropriate brand name 

subsistence items are identified by the Subsistence Identification 

Number or when maintenance/industrial activity materiel is 

identified by Local Stock Number or Materiel Control Tracking 

(MCT) tag number. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN may be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered item requisitioning. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements.

4. 2 /W0106/0200 Add the following qualifiers and DLMS notes:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

2/W1207/20 
ADC 381 

Enclosure 7, Page 27 

Item 

# 

Location DS 940R Material Release 

Revision 

Reason 

indicator is included and the Local Stock Number (LSN) is identified 

as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

5. 2/N901/0400 Revise DLMS notes for existing qualifier WO:

WO Work Order Number 

DLMS Note: 

1. Use as needed to identify a maintenance work order number or job 

number.

2. Use when transaction includes Component-unique MRO exception 

data; see introductory DLMS note 4e. 

3. DLMS enhancement; see introductory DLMS note 4a. 

1. Use to identify a maintenance work order number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

3. Also applicable to MRO Exception Data Transaction (ICP to DSS 

Storage Activity). Legacy mapping may populate with work order or 

job order number, pending full DLMS implementation Refer to ADC 

71A. 

Supports Navy BRAC Spiral II 

requirements.

Allows for pre-existing usage 

although full DLMS should 

now use separate data fields 

for work order and job order 

numbers. 

6. 2/N901/0400 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Used in support of Navy Shipyards to associate the funded 

requisition with a previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

WP Warehouse Pick Ticket Number 

DLMS Note: 1. Use to identify the picklist control number assigned 

to identify a specific job for which materials are being assembled 

together in support of planned maintenance. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements.
ADC 381 

Enclosure 7, Page 28 

Item 

# 

Location DS 940R Material Release 

Revision 

Reason 

7 2/N907-01/0400 Add new DLMS note 2 for existing qualifier:

W8 Suffix 

DLMS Note: 1. Use with N901 code TN for all transactions other than 

redistribution orders, to identify the transaction number suffix.

2. When used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. The Requisition Alert Document Number Suffix is 

an Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

8 2/AMT01/0800 Revise DLMS notes for existing qualifier:

LI Line Item Unit Price 

DLMS Note: 1. Use with material release order transactions to 

indicate the unit price. 

2. A field size exceeding 7 positions (5 digits dollars and 2 digits 

cents) may not be received or understood by the recipient’s automated 

processing system. 

3. Under DLMS the unit price will be expressed as R9.2. Authorized 

DLMS migration enhancement; see introductory DLMS 4f. 

4. The DLMS field length is authorized when this transaction supports 

the Retail Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS. 

5. Use to identify the unit of use price when the unit of use indicator 

(W0501=Z) is present. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 

9. 2/N101/1100 Add the following qualifier and DLMS note:

MQ Delivery Location 

DLMS Note:  1. Use to provide the delivery location indicating 

where the material is to be staged/stored. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

10. 2/N101/1100 Revise DLMS notes for existing qualifier XN: 

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between the source of supply and the Distribution 

Depot warehouse storage system to identify the Shop Service Center 

(SSC) or Shop Store.

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381.

Supports Navy BRAC Spiral II 

requirements.

11. 2/N103/1100 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements 

12. 2/LQ01/1300 Add the following qualifier and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code 

indicating the level of quality inspection to which the item must be 

procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 29 

Item 

# 

Location DS 940R Material Release 

Revision 

Reason 

support agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use to identify a specialized purpose for which the 

requisition is submitted. 

2. Under DLSS, this is the first position of the document serial 

number within the document number. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

4. DLMS enhancement; see introductory DLMS note 4a. 

R3 Delivery Rank (Priority) 

DLMS Note: 

1. Use to indicate the Delivery Priority Code for material which has 

an urgency of need within the maintenance shop and must be 

delivered within one hour of receipt of the issue request. Value will 

be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Reason for Requisitioning 

Code and Utilization Code 

perpetuated to MRO for 

consistency and visibility.

Section J - DS 945A Material Release Advice 

Item 

# 

Location DS 945A Material Release Advice 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 5:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/W0601/20 Add new qualifier and DLMS note:

Z Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

3. At this time a local code ‘Z’ is established for use in 945A, version 

4010. A data maintenance action will be submitted for establishment of 

‘Z-Mutually Defined’ in a future version.

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 2/W1207/20 Revise the data element level note and add the following qualifiers and 

DLMS notes:

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 30 

Item 

# 

Location DS 945A Material Release Advice 

Revision 

Reason 

DLMS Note: Use only one of codes A1, A2, A4, FB, FS, FT, MG, SW,

YP, ZR or ZZ to identify the material. Must use National Stock Number 

(NSN) when known, except when appropriate brand name subsistence 

items are identified by the Subsistence Identification Number or when 

maintenance/industrial activity materiel is identified by Local Stock 

Number or Materiel Control Tracking (MCT) tag number. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN may be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered item requisitioning. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4 2/W1217/20 Add the following qualifiers and DLMS note:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator 

is included and the Local Stock Number (LSN) is identified as the 

primary materiel identification. Authorized DLMS enhancement 

under DLA industrial activity support agreement. 

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

5. 2/N901/40 Add new DLMS note 2 to existing qualifier WO:

WO Work Order Number 

DLMS Note: 1. Use to identify a maintenance work order number.

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

6. 2/N901/40 Add the following qualifiers and DLMS note:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance Record 

(COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

WP Warehouse Pick Ticket Number 

Supports Navy BRAC Spiral II 

requirements.
ADC 381 

Enclosure 7, Page 31 

Item 

# 

Location DS 945A Material Release Advice 

Revision 

Reason 

DLMS Note: 1. Use to identify the picklist control number assigned to 

identify a specific job for which materials are being assembled together 

in support of planned maintenance. 

2. Cite the picklist control number in N903 due to field length. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

7. 2/N907-01/40 Revise DLMS Notes for existing qualifier:

W8 Suffix 

DLMS Note: 1. Use with N901 Code TN to identify the transaction number 

suffix. 

2. When used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. The Requisition Alert Document Number Suffix is 

an Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements.

8. 2/AMT01/60 Revise DLMS Notes for existing qualifier:

NT Unit Value 

DLMS Note: 

1. Use in CAV Material Release Confirmation transactions to indicate 

the unit price of an item. 

2. Use to identify the unit price applicable to the materiel identified by 

the release confirmation supporting NSYs and FRC under DLA 

industrial activity support agreement. Authorized DLMS 

enhancement; Refer to ADC 381. 

3. Under DLMS the unit price will be expressed as R9.2. 

Supports Navy BRAC Spiral II 

requirements.

9. 2/N101/80 Revise DLMS note 2 for existing qualifier XN: 

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between the source of supply and the Distribution 

Depot warehouse storage system to identify the Shop Service Center 

(SSC) or Shop Store.

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 284A & 381.

Supports Navy BRAC Spiral II 

requirements.

10. 2/N103/80 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements 

11. 2/LQ01/100 Add the following qualifier and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code indicating 

the level of quality inspection to which the item must be procured and 

inspected. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use to identify a specialized purpose associated with 

this document number. 

2. Under DLSS, this is the first position of the document serial number. 

3. Authorized DLMS enhancement under DLA industrial activity 

Supports Navy BRAC Spiral II 

requirements.
ADC 381 

Enclosure 7, Page 32 

Item 

# 

Location DS 945A Material Release Advice 

Revision 

Reason 

support agreement. Refer to ADC 381.

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

KJ Assured Delivery Indicator 

DLMS Note: 1. Use to indicate the Delivery Priority Code for material 

which has an urgency of need within the maintenance shop and must 

be delivered within one hour of receipt of the issue request. Value will 

be X (1 hour issue) when applicable. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Section K - DS 947I Inventory Adjustment. Refer to ADC 376 - all proposed updates have been 

relocated. 

Section L - DS 527D Due-in/Advance Receipt/Due Verification 

# Location DS 527D Due-in/Advance Receipt/Due Verification 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 6:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BR01/20 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 2/LIN02/10 Revise the data element level note 1 and add the following qualifiers and 

DLMS notes:

1. Use only one of codes A1, A2, A4, FB, FS, FT, MG, NN, SW, YP, ZR, 

or ZZ to identify the materiel. Must use National Stock Number (NSN) 

when known except when appropriate, brand name subsistence items are 

identified by the Subsistence Identification Number or when 

maintenance/industrial activity materiel is identified by Local Stock 

Number or Materiel Control Tracking (MCT) tag number. An exception 

is also authorized for CAV where materiel may be identified by the 

National Item Identification Number (NIIN) when the Federal Supply 

Code (FSC) is not available.

SW Stock Number 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 33 

# Location DS 527D Due-in/Advance Receipt/Due Verification 

Revision 

Reason 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. 2/LIN04/10 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator 

is included and the Local Stock Number (LSN) is identified as the 

primary materiel identification. Authorized DLMS enhancement under 

DLA industrial activity support agreement. 

When a unit of use LSN is 

identified above, the NSN will 

be included here.

5. 2/N901/90 Add qualifier CO:

CO Customer Order Number 

DLMS Note:  

1. Use to identify the Customer Order Acceptance Record (COAR) 

applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

Supports Navy BRAC Spiral 

II requirements. 

6. 2/N901/90 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document Number. 

2. Authorized DLMS enhancement under Navy/DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral 

II requirements. 

7. 2/N907-01/90 Add the following qualifier and DLMS notes:

W8 Suffix 

DLMS Note: When used in association with the Requisition Alert 

Document Number (Qualifier PWC, above), this will be the requisition 

alert document suffix. The Requisition Alert Document Number Suffix 

is an Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral 

II requirements. 

8. 2/LQ01/130 Add the following qualifier and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code indicating 

the level of quality inspection to which the item must be procured and 

inspected. 

Supports Navy BRAC Spiral 

II requirements.
ADC 381 

Enclosure 7, Page 34 

# Location DS 527D Due-in/Advance Receipt/Due Verification 

Revision 

Reason 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

AJ Utilization Code 

DLMS Note: 1. Use only with due-in transactions to identify Quality 

Deficiency Report (QDR) related transactions when the original 

requisition transaction number is not known (utilization code U applies) or 

as applicable under DLA industrial activity support; otherwise, do not 

use. 

2. Under DLSS, this is the first position of the document serial number. 

3. DLMS enhancement; see introductory DLMS note 4a.

9. 2/N101/210 Add the following qualifier and DLMS note:

DZ Delivery Zone 

DLMS Note:  1. Use to provide the DELIVERY LOCATION 

indicating where the material is to be staged/stored. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Section M - DS 527R Receipt/Inquiry and Response and MRA 

# Location DS 527R Receipt, Inquiry and Response and MRA 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 6:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP 

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BR01/20 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381. 

Code to distinguish the unit 

of use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 2/LIN02/10 Revise the data element level note 1 and add the following qualifiers w/ 

DLMS notes:

DLMS Note: 1. Use only one of codes A1, A2, A4, FB, FS, FT, MG, NN, 

SW, YP, ZR, or ZZ to identify the materiel. Must use National Stock 

Number (NSN) when known, except when appropriate brand name 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 35 

# Location DS 527R Receipt, Inquiry and Response and MRA 

Revision 

Reason 

subsistence items are identified by the Subsistence Identification Number

or when maintenance/industrial activity materiel is identified by Local 

Stock Number or Material Control Tracking (MCT) Tag Number.. An 

exception is also authorized for CAV where materiel may be identified by 

the National Item Identification Number (NIIN) when the Federal Supply 

Code (FSC) is not available.

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be included 

for cross-reference. May also be used for identification of LSNs assigned 

for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

4. 2/LIN04/10 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator is 

included and the Local Stock Number (LSN) is identified as the primary 

materiel identification. Authorized DLMS enhancement under DLA 

industrial activity support agreement. 

When a unit of use LSN is 

identified above, the NSN 

will be included here. 

5. 2/N901/ 90 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance Record 

(COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document Number. 

2. Used by Navy Shipyards to associate the requisition follow-up with a 

previously submitted requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral 

II requirements. 

6. 2/N907-01/90 Add the following qualifier and DLMS notes:

W8 Suffix 

DLMS Note: When used in association with the Requisition Alert 

Document Number (Qualifier PWC, above), this will be the requisition 

Supports Navy BRAC Spiral 

II requirements. 
ADC 381 

Enclosure 7, Page 36 

# Location DS 527R Receipt, Inquiry and Response and MRA 

Revision 

Reason 

alert document suffix. The Requisition Alert Document Number Suffix 

is an Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

7. 2/LQ01/130 Add the following qualifier and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code indicating the 

level of quality inspection to which the item must be procured and 

inspected. 

2. Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381. 

98 Reason for Requisitioning Code 

DLMS Note: 1. Use to identify Reason for Requisitioning Code 

identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral 

II requirements. 

Section N - DS 842A/W Supply Discrepancy Report (SDR) and DS 842A/R SDR Reply 

# Location DS 842A/W Supply Discrepancy Report (SDR) 

and 842A/R SDR Reply Revision

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 381 to DLMS Introductory page to both SDR Report and SDR 

Reply:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP 

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1BNR01/0200 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 2/LIN02/0200 Add the following qualifier and DLMS notes:

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

New qualifiers added to identify 

the type of discrepant materiel. 
ADC 381 

Enclosure 7, Page 37 

# Location DS 842A/W Supply Discrepancy Report (SDR) 

and 842A/R SDR Reply Revision

Reason 

4. 2/LIN04/0200 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator 

is included and the Local Stock Number (LSN) is identified as the 

primary materiel identification. Authorized DLMS enhancement under 

DLA industrial activity support agreement. 

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

Section O - DS 842C/I Stock Screening Request and 842C/R Stock Screening Reply 

Item 

# 

Location DS 842C/I Stock Screening Request 

and 842C/R Stock Screening Reply 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 381 to DLMS Introductory page to both Stock Screening 

Request and Stock Screening Reply:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1BNR01/0200 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 2/LIN02/0200 Add the following qualifier and DLMS note:

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

New qualifiers added to identify 

the type of materiel. 

4. 2/LIN04/0200 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is 

identified as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

When a unit of use LSN is 

identified above, the NSN will 

be included here. 
ADC 381 

Enclosure 7, Page 38 

Item 

# 

Location DS 842C/I Stock Screening Request 

and 842C/R Stock Screening Reply 

Revision 

Reason 

5. 2/REF01/0700 Add the following qualifiers to and DLMS notes to both the Request 

and Reply:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements. 

6. 2/REF01/0700 Add the following qualifier and DLMS note:

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

7 2/REF04-01/0700 For 842C/I add the following as DLMS note 3:

For 842C/R mark Data Elements REF04-01 and REF04-02 Used and 

add qualifier W8 w/ DLMS note:

W8 Suffix 

DLMS Note: When used in association with the Requisition Alert 

Document Number (Qualifier PWC, above), this will be the 

requisition alert document suffix. The Requisition Alert Document 

Number Suffix is an Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 381.

Section P - DS 842S/Q Storage Quality Control Report (SQCR) and 842S/R SQCR Reply 

Item 

# 

Location DS 842S/Q Storage Quality Control Report (SQCR) 

and 842S/R SQCR Reply Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 381 to DLMS Introductory page to both SQCR and 

SQCR Reply:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 
ADC 381 

Enclosure 7, Page 39 

Item 

# 

Location DS 842S/Q Storage Quality Control Report (SQCR) 

and 842S/R SQCR Reply Revision 

Reason 

2. 1BNR01/0200 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy BRAC 

sites will requisition using the 

NSN; however the unit of 

measure and quantity are 

applicable to the unit of use. 

3. 2/LIN02/0200 Add the following qualifier and DLMS notes:

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification 

of LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

New qualifiers added to identify 

the type of materiel. 

4. 2/LIN04/0200 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is 

identified as the primary materiel identification. Authorized 

DLMS enhancement under DLA industrial activity support 

agreement. 

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

5. 2/REF01/0700 Add the following qualifiers and DLMS notes to both the Report 

and Reply:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Staffing Note: Requires 

verification that JO/KO applies 

to SQCR and reply (reply 

only?). 

6 2/REF01/0700 Add the following qualifier and DLMS note:

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Staffing Note: Requires 

verification that Requisition 

Alert Document Number/Suffix 

applies to SQCR and reply 

(reply only?). 
ADC 381 

Enclosure 7, Page 40 

Item 

# 

Location DS 842S/Q Storage Quality Control Report (SQCR) 

and 842S/R SQCR Reply Revision 

Reason 

7 2/REF04-01/0700 For 842S/Q add the following as DLMS note 2:

For 842S/R mark Data Elements REF04-01 and REF04-02 Used and 

add qualifier W8 w/ DLMS note:

W8 Suffix 

DLMS Note: When used in association with the Requisition Alert 

Document Number (Qualifier PWC, above), this will be the 

requisition alert document suffix. The Requisition Alert 

Document Number Suffix is an Authorized DLMS enhancement 

under DLA industrial activity support agreement. Refer to ADC 

381.

Section Q - DS 846P Physical Inventory Request 

Item 

# 

Location DS 846P Physical Inventory Request 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 6:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 2/BIA01/010 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 2/LIN02/010 Revise the data element level note 1 and add the following qualifiers 

w/ DLMS notes:

1. For 1/BIA02/20 codes AD, DD, TC, and TF, use only one of codes A1, A2, 

A3, A4, FB, FS, MG, SW, YP, ZR or ZZ to identify the item of inventory. 

Must use National Stock Number (NSN) when known except when 

appropriate brand name subsistence items are identified by the subsistence 

Identification Number or when maintenance/industrial activity 

materiel is identified by Local Stock Number or Material Control 

Tracking (MCT) Tag Number.

ZR Service Control Identification 

DLMS Note: Use to identify Materiel Control Tracking (MCT) tag 

number. The MCT tag number is an authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Refer to ADC 381. 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

New qualifiers added to 

identify the type of billed 

materiel. 
ADC 381 

Enclosure 7, Page 41 

Item 

# 

Location DS 846P Physical Inventory Request 

Revision 

Reason 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

4. 2/LIN04/0200 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is 

identified as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

RV Repair Tag Number

DLMS Note: Use with Code ZR to identify the MCT tag number 

suffix.

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

Section R - DS 846R Location Reconciliation Request 

Item 

# 

Location DS 846R Location Reconciliation Request 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 6:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 2/BIA01/010 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with 

this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Code to distinguish the unit of 

use requirements. Navy 

BRAC sites will requisition 

using the NSN; however the 

unit of measure and quantity 

are applicable to the unit of 

use. 

3. 2/LIN02/010 Revise the data element level note 1 and add the following qualifiers 

w/ DLMS notes:

1. For 1/BIA02/020 code LC, use only one of codes A1, A2, A3, A4, FB, FS, 

MG, SW, YP, ZR or ZZ to identify the item of inventory. Must use National 

Stock Number (NSN) when known except when appropriate brand name 

subsistence items are identified by the subsistence Identification Number or 

when maintenance/industrial activity materiel is identified by Local 

Stock Number or Material Control Tracking (MCT) Tag Number.

ZR Service Control Identification 

DLMS Note: Use to identify Materiel Control Tracking (MCT) tag 

number. The MCT tag number is an authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Refer to ADC 381. 

New qualifiers added to 

identify the type of billed 

materiel. 
ADC 381 

Enclosure 7, Page 42 

Item 

# 

Location DS 846R Location Reconciliation Request 

Revision 

Reason 

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. 2/LIN04/010 Add the following qualifier and DLMS notes:

FS National Stock Number 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is 

identified as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

RV Repair Tag Number

DLMS Note: Use with Code ZR to identify the MCT tag number 

suffix.

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

Section S - DS 870M Material Returns Supply Status 

# Location DS 870M Material Returns Supply Status 

Revision 

Reason 

1. DLMS Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 4:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements 

under Navy BRAC SS&D/IMSP

Identifies DLMS Changes included 

in the DLMS Supplement 

2. 1/BSR11/20 Add qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity, price, and unit of measure values associated 

with this transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Code to distinguish the unit of use 

requirements. Navy BRAC sites 

will requisition using the NSN; 

however the unit of measure and 

quantity are applicable to the unit 

of use. 

3. 2/REF01/87 Add the following qualifiers and DLMS notes:

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance 

Record (COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

Supports Navy BRAC Spiral II 

requirements. 

Staffing Note: Verify requirement 

for requisition alert document 

number /suffix and JO/KO on the 

870M. 
ADC 381 

Enclosure 7, Page 43 

# Location DS 870M Material Returns Supply Status 

Revision 

Reason 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document 

Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. 2/REF04-01 Mark Data Element REF04-01 as Used and add the following qualifier 

and DLMS Note:

W8 Suffix 

DLMS Note: When used in association with the Requisition Alert 

Document Number (Qualifier PWC, above), this will be the 

requisition alert document suffix. The Requisition Alert Document 

Number Suffix is an Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 

5. 2/PO103/150 Revise Federal Note:

Unit or Basis for Measurement Code 

Federal Note: Use to identify the unit of issue for the required 

material. Use to identify the applicable unit of measure. 

DLMS Note: DLMS users see the DLMS Unit of Issue and Purchase

Unit Conversion Table for available codes 

Supports Navy BRAC Spiral II 

requirements. 

6. 2/PO104/150 Revise DLMS note:

Unit Price 

DLMS Note: 1. Applicable to the reply to the customer asset report. 

2. Under DLMS the unit price will be expressed as R9.2. Authorized 

DLMS migration enhancement; see introductory 

DLMS 4f.

Supports Navy BRAC Spiral II 

requirements. 

Removes restricted applicability to 

responses to customer asset report 

(FTE). 

7. 2/PO106/150 Revise the data element level note and add the following qualifier and 

DLMS note:

DLMS Note: Use only one of codes A1, A2, A4, FB, FS, MG, SW, YP and ZZ 

to identify the material. Must use the National Stock Number (NSN) when 

known or when maintenance/industrial activity materiel is identified 

by Local Stock Number.

SW Stock Number 

DLMS Note: 1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements. 

8. 2/PO108/150 Add the following qualifier and DLMS notes:

FS National Stock Number 

When a unit of use LSN is 

identified above, the NSN will be 

included here. 
ADC 381 

Enclosure 7, Page 44 

# Location DS 870M Material Returns Supply Status 

Revision 

Reason 

DLMS Note: 

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use 

indicator is included and the Local Stock Number (LSN) is identified 

as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Section T - DS 867I Issue 

Item 

# 

Location DS 867I Issue Revision Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 381 to DLMS Introductory note 7:

- ADC 381, Procedures and Additional Data Content supporting 

Requisitions, Requisition Alerts, and Unit of Use Requirements under 

Navy BRAC SS&D/IMSP

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/BPT01/20 Add new qualifier and DLMS note:

ZZ Mutually Defined 

DLMS Note: 1. Use to identify the Unit of Use Indicator. When 

included, the quantity and unit of measure values associated with this 

transaction are applicable to the unit of use. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

Code to distinguish the unit of 

use requirements. 

3. 2/REF01/30 Add the following qualifiers and DLMS notes:

DLMS Note: 1. Must use National Stock Number (NSN), when known, 

to identify the materiel, except when appropriate brand name subsistence 

items are identified by the Subsistence Identification Number or when 

maintenance/industrial activity materiel is identified by Local Stock 

Number or Material Control Tracking (MCT) Tag Number. An 

exception is also authorized for CAV where materiel may be identified 

by the National Item Identification Number (NIIN) when the Federal 

Supply Code (FSC) is not available. 

S6 Stock Number 

DLMS Note: Use to identify the publication stock number.

1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN, the applicable NSN will be 

included for cross-reference. May also be used for identification of 

LSNs assigned for part-numbered items. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

ABV Book Number 

Supports Navy BRAC Spiral II 

requirements. 
ADC 381 

Enclosure 7, Page 45 

Item 

# 

Location DS 867I Issue Revision Reason 

DLMS Note: Use for publication stock number. This is a DLMS 

enhancement for future use.

77 Work Package 

DLMS Note: 1. Use to identify a maintenance work order number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

9R Job Order Number 

DLMS Note: 1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

CO Customer Order Number 

DLMS Note: 1. Use to identify the Customer Order Acceptance Record 

(COAR) applicable to the Job Order Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 (or as applicable). 

86 Operation Number 

DLMS Note: 1. Use to identify the Key Operation (KO) Number 

associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

PWC Preliminary Work Candidate Number 

DLMS Note: 1. Use to identify a Requisition Alert Document Number. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

WP Warehouse Pick Ticket Number 

DLMS Note: 1. Use to identify the picklist control number assigned to 

identify a specific job for which materials are being requisitioned and 

assembled together in support of planned maintenance. 

2. Cite the picklist control number in REF03 due to field length. 

3. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381.

4. 2/REF03/30 Revise Data Element DLMS Note 1 and 4:

1. Use only with REF01 codes CU, WF and WP.

2. Use with REF01 code CU to identify issue category information. 

3. DMLSS/TEWLS use with REF01 code WF to identify the Local 

Catalog Identification. 

4. Use with REF01 code WP to cite the picklist control number.

Available data field length in 

REF03 support picklist control 

number 

5. 2/REF04-01/30 Add the following qualifier and DLMS notes:

NS National Stock Number 

DLMS Note: 1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator 

is included and the Local Stock Number (LSN) is identified as the 

primary materiel identification. Authorized DLMS enhancement 

under DLA industrial activity support agreement. 

When a unit of use LSN is 

identified above, the NSN will 

be included here. 

6. 2/REF04-01/30 Revise DLMS Notes for existing qualifier: Supports Navy BRAC Spiral II 

requirements.
ADC 381 

Enclosure 7, Page 46 

Item 

# 

Location DS 867I Issue Revision Reason 

W8 Suffix 

DLMS Note: 1. Use with REF01 code TN to identify the issue document 

number suffix. 

2. Use with REF01 code RV to identify the Previous Movement Document 

Number Suffix. 

3. Use with REF01 code Q5 to identify the MCT tag number suffix.

3. When used in association with the Requisition Alert Document 

Number (Qualifier PWC, above), this will be the requisition alert 

document suffix. The Requisition Alert Document Number Suffix is 

an Authorized DLMS enhancement for under DLA industrial activity 

support agreement. Refer to ADC 381.

6. 2/AMT01/140 Add the following qualifier and DLMS Note:

NT Unit Value 

DLMS Note: Use to identify the unit price applicable to the materiel 

identified by the issued. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 381.

Supports Navy BRAC Spiral II 

requirements.

7. 2/N101/50 Revise DLMS note 2 for existing qualifier XN: 

XN Planning/Maintenance Organization 

DLMS Note: 1. Use between Service industrial/maintenance sites and 

DLA to identify the Shop Service Center (SSC) or Shop Store. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements.

8. 2/N103/90 Update DLMS notes for existing qualifiers 92:

92 Assigned by Buyer or Buyer's Agent 

DLMS Note: Use with N101 Code XN to identify the Shop Service 

Center or Shop Store. Refer to ADC 284A & 381. 

Expands existing usage for 

Navy BRAC Spiral II 

requirements 

9. 2/LQ01/270 Add the following qualifier and DLMS notes:

T05 Inspection Parameters 

DLMS Note: 1. Use to identify the Quality Inspection Code indicating 

the quality level of inspection which the item must be procured and 

inspected to. 

2. Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381. 

Supports Navy BRAC Spiral II 

requirements.
ADC 381 

Enclosure 8, Page 1 

Enclosure 8, DLMS Change Concurrence/Comment Resolution 

 Submitter Response Response 

1. DLA Concur 

2. Chief, Spiral II 

Integration Office 

(J-62, Robert 

Therriault) 

Concur with updated data content. 

3. IMSP Team 

(J-333, Annette 

Spry) 

In addition to the current mapping the IMSP design needs to 

include the following 

1) Request Delivery Location be included on the 511R, 511M, 

940R, 527D and the 869F: 

Currently mapped only to the 940S and 943A as a 30 position text 

field, in these additional transactions the NSY sites would be 

passing a max of 5 positions to indicate the building where the 

material is to be staged/stored. This will assist in the stow process 

of receipts for DMI material at the NSY sites. 

2) Request an additional field be added to all transactions which 

reflect the Job Order: 511R, 511M, 527D, 527R, 947I, 940R, 

945A, 867I, 869A, 869C, 869F, 870S, 856S, 846P, 842C, 

870M,846I, 940S and 943A: 

COAR –Customer Order Acceptance Record, this will reflect the 

Work Category Number (position 1-2) and the Availability Number 

(position 3-5). Alpha Numeric field. Customer order for which 

reporting is required. 

3) Correct values for the Utilization code, values should be V for 

Routine Contact and Z – Immediate Contact required. PDC has 

vales of X and Z. 

4) Request additional data element Work Order be added to 

DLMS transactions 870S, 945A and 867I: 

This is a 10 position, max 10, min 8. Alphanumeric field. Used by 

FRC only. Work Order is a key control number for an MRPII 

document that details and maps work performed and remaining 

work to be performed for a product being repaired or manufactured 

by an FRC. 

5) Delete MCT Tag Number Suffix. Subsequent to the DSS 

Critical Design Review it was determined that the Navy MAT 

system will maintain visibility of the components and DSS will 

only maintain visibility by a single consolidated value for the MCT 

tag included the suffix when applicable. 

All changes adopted in ADC. 

COAR: 842A/W was not listed in 

original request, but it does include a job 

order number. Added for re-staffing in 

PDC 387A 

Note: Navy recommendation to include 

“Optional Key” was later withdrawn by 

IMSP team. 
ADC 381 

Enclosure 8, Page 2 

4. DDC 

CDR Action Item 

Resolution 

There are currently 3 shop stores that are unmanned at NNSY that 

carry 32 lines of materiel.(SS 23, 51 and 74) We assume the 

operations at PSNSY is similar. 

The process entails: 

1. Mechanic takes materiel and provides a chit to the SS 

operator/supervisor 

2. SS enters chit into MAT to obtain Navy doc no. 

3. SS enters Post-Post in DSS using Navy Doc no obtained 

4. SS closes Post-Post issue in DSS, recording badge number/ 

signature of recipient (on chit) - Badge number will be recorded 

internally in DSS during the behind the scenes manifesting. 

5. DSS replenishes unmanned SS level 

Business Rules 

• EBS ensures levels are maintained thru buys/RDO’s etc 

• DSS maintains levels as in AF Model 

• NNSY operational processes are in place to ensure success of 

this model 

• Inventory imbalances will be bought by Navy 

• MAT will generate DOCNO for POU/WALK-UP Issues 

(Post-Post) and not exit transactions 

• DSS must record the Badge Number of the recipient of the 

materiel. 

High level procedures to be included in 

DLMS manual and DD guidance 

5. Navy Concur 

6. Army Concur 

7. Marine Corps Concur 

8. DMLSS/JMFLDC Concur 

9. DAASC DAASC needs guidance on processing rules: 

If requisition alert transactions are to be excluded from 

WEBVLIPS, LOTS, MRA, SDR and LMARS but they need to go 

through DMARS, then DMARS needs to code RP 160 with a 

LOTS non parsing code. It appears that the "action code" could be 

used to set RP 167 (COPY_DOC). LOTS will not put them on the 

database and these other systems will never see them. 

If these transactions are never sent to DMARS, they should be 

coded as pass thru and not put on LOTS. Then WEBVLIPS, MRA, 

SDR and LMARS will never have access to them. There will be no 

changes to LOTS. 

The requisition alert does not apply to 

MRA Reports, LMARS, or to pull 

history for SDR pre-population because 

no shipments are made on this document 

number. However, it is appropriate to 

perform basic requisition edits in 

DMARS and to reflect the requisition 

alert and matching status transactions in 

WebVLIPS. WebVLIPS display must 

include the requisition alert indicator. 

Additionally WebVLIPS must recognize 

where unit of use applies and adjust the 

U/I display or otherwise indicate "U/U." 

Although not an immediate requirement, 

we would like to see a way to associate 

the display of the funded requisition 

with the requisition alert when both 

values are known and associated (e.g. 

for NSY requisitions which includes 

both values); perhaps through hyperlink. 
ADC 381 

Enclosure 8, Page 3 

DAASC Response. The associated live 

reqn. must contain the DOCNO. of the 

requisition alert in order for us to link it. 

Some would, some would not. We 

could link the ones we had. 

DAAS will most likely implement, 

similar to the RF Tag, with a requisition 

alert table separate from the A table and 

use WEBVLIPS to join the two. 

It will alleviate a lot of issues that might 

develop because things don't always go 

as they are supposed to in the logistics 

world. None of the downstream systems 

will even see it and accidental duplicate 

DOCNO will not be an issue. Also it 

will save space because we will need 

to store only the reqns. and status for the 

alerts. Storing on the A table will result 

in a lot of unused space. 

10. DPAP 

IUID/WAWF PM 

Contractor 

Support 

The PDC references that impact to WAWF needs to be considered. 

.. not sure what the impacts may be unless some of the delivery 

sites using this material issued/ordered/shipped at Unit of Use 

versus Unit of Issue level include Contractor DoDAACs (or 

operated sites) and the material will be GFP. If this will be GFP, 

then it may impact not only WAWF but also the GFP Hub. Please 

advise if the sites involved in this scenario is ONLY DoD sites or if 

Contractor sites will also be involved. 

One more comment: Within this PDC you reference the Material 

Control Tracking Tag concept (Attachment Page 10) outlined in 

PDC 393. In our comments to that PDC, we advised that consistent 

with SIM and IUID policy, the UII of the property should be used 

versus using the MCT concept. 

Therefore any decision on PDC 393 would apply to this change as 

well. 

Some sites may be contractor-operated; 

however, unit of use will only apply to 

the DLA support for the requirement. If 

vendor shipments are required, DLA 

will take ownership and subsequent to 

acceptance, position the materiel in the 

IA worksite, and then convert to the unit 

of use. 

Refer to PDC 393 comment resolution. 

11. DLMSO 1. The only change we have identified for post-post specifically is 

the inclusion of the cross-reference NSN when a unit of use LSN is 

used. Are any of the other 511R data elements going to be added to 

the screen for C0A/C01? 

2. The PDC Enclosure 2 provided a table display of criteria 

applicable to DLA breaching rules for protected materiel. Since 

updates to this table were not available at the time of ADC 

publication and there are areas which require correction or 

clarification, and several sites were not addressed, the table has 

been removed for publication with the DLMS manual procedures. 

1. I had identified them in PDC 366 as 

the JO, KO and the Requisition alert 

document number. 

In instances when the material 

supporting a funded order is issued from 

DSS through the current post/post 

process, the Requisition Alert Document 

Number, Job Order and Key Operation 

Number must be included on the 511R 

(with the post-post directed MRO 

indicator) submitted to the material 

owner. The material confirmation will 

also reflect the same data elements. 

 For post-post directed MROs, if the 

issue is for other than the FLIS standard 

unit of issue, DSS logic will ensure the 

material has been previously re-
ADC 381 

Enclosure 8, Page 4 

identified to an applicable LSN. When 

the transaction is sent to the material 

owner the correct unit of use qualifier, 

LSN and NSN will be reflected as 

applicable. If the material is required in 

the unit of use and has not been reidentified from the NSN, operational 

procedures for the DLA personal will 

allow a manual process to re-identify, 

notify the material owner with 947I, 

D8K and D9K, and issue the material. 
ADC 381 

Enclosure 9, Page 1 

Enclosure 9, Navy BRAC SS&D/IMSP PDCs/ADCs 

The following table lists DLMS changes supporting the Navy BRAC SS&D/IMSP CONOPS. 

PDC 

# 

PDC 

Date 

TITLE 

(Status) 

ADC 

# 

ADC 

Date 

1. 358 8/10/09 New Advice Code for Surge Requirements of Mission Support Material 

(MSM) under Navy BRAC IMSP (MILSTRIP/Supply) 

338 9/28/09 

2. 360A 4/08/10 Establishment of DS 832N, Catalog Data Support for Navy BRAC 

Retail Supply, Storage and Distribution (SS&D)/IMSP 

(Marine Corps requirements being clarified for inclusion and separate 

staffing; ADC will include both Navy and Marine Corps in consolidated 

transaction format. Awaiting DLA input.) 

367 

3. 366A 5/06/10 Procedures and Additional Data Content supporting Requisitions, 

Requisition Alerts, and Unit of Use Requirements under Navy BRAC 

SS&D/IMSP (Supply/Finance) 

381 7/1/10 

4. 376A 5/06/10 Revise DLMS 846A Asset Reclassification and 947I Inventory 

Adjustment to Support Navy BRAC SS&D/IMSP, with DLMS Data 

Mapping (Supply) 

376 

5. 380 11/24/0

9 

Management Code for Product Quality Deficiency Report (PQDR) 

Replacement Requisitions (MILSTRIP/MILSTRAP/Supply) 

352 2/18/10 

6. 384 4/20/10 New DLMS Supplement (DS) 940S, Warehouse Service Request (for 

Materiel Protection/Re-Warehousing, Staging, and Picklist/Callout), 

New DS 943A, Warehouse Service Advice, and Associated Procedures 

under Navy BRAC SS&D/IMSP (Supply) 

380 

7. 385 4/15/10 Procedures and Assignment of Navy DODAACs to DLA for Use on 

DLA Requisitions to Military Service/GSA Sources of Supply (SoSs) in 

Support of Navy Industrial Activities (IAs) under BRAC SS&D/IMSP 

(Supply/DoDAAD) 

368 

8. 386 4/9/10 Alternative Procedures for Material Obligation Validation (MOV) under 

Navy BRAC SS&D/IMSP (MILSTRIP/ Supply) 

369 6/22/10 

9. 387 

387A 

4/19/10 

6/24/10 

Supply Discrepancy Report (SDR) Procedures, including additional 

Navy Document Number under Navy BRAC SS&D/IMSP 

(Supply/SDR) 

371 

10. 388 4/15/10 Requisitioning for Off-Station Forward Site Support and New NonInventory affecting Denial Management Code indicating Off-Station 

Materiel under Navy BRAC SS&D IMSP (MILSTRIP/MILSTRAP/ 

Supply) 

370 5/18/10 

11. 389 4/19/10 Request for Discrepancy Indicator Code to Identify 527R Material 

Receipt Acknowledgement (MRA) Generated Based on “Virtual 

Receipt” to Support Navy BRAC SS&D/IMSP (Supply/Finance) 

372 5/21/10 

12. 393 4/16/10 Document Process for Material Control Tracking (MCT) Tag Number 

and Revise DLMS 527D, 527R, 867I, 940R, and 945A in Support of 

Navy BRAC SS&D/IMSP (Supply) 

373 
ADC 381 

Enclosure 9, Page 2 

PDC 

# 

PDC 

Date 

TITLE 

(Status) 

ADC 

# 

ADC 

Date 

13. 394 4/20/10 Revise DLMS 846I Asset Status Report in Support of Navy BRAC 

SS&D/ IMSP (Supply) 

374 6/24/10 

14. 401 4/15/10 New Management Code for Navy Funded Non-Production Support 

Materiel Ordered under BRAC SS&D/IMSP (MILSTRIP/ MILSTRAP 

Supply) 

375 

15. 404 4/14/10 Transaction Copies Required for DLA Support of Navy BRAC 

SS&D/IMSP Depot Level Reparables (DLRs), Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel 

377 6/23/10 

16. 405 4/15/10 Revise DLMS 947I Inventory Adjustment to Identify Loss due to 

Destructive Test in Support of Navy-DLA BRAC SS&D/IMSP 

(Supply/Finance) 

 

17. 406 4/20/10 New and Revised Supply Status Procedures to Support “Virtual 

Receipt” and Requisition Alert Processes under Navy BRAC 

SS&D/IMSP (MILSTRIP/ Supply) 

379 6/15/10 

18. 324A PDC Addendum to ADC 324, BRAC Materiel Returns (Revised 

Procedures and Internal DLA Oversight Requirement) (MILSTRIP/ 

Supply) 

 

19. 412 6/17/10 New Denial Management Code to Support the New Protection Process 

at the NSYs when Requisition Alert/ Job Order do not Match Records 

under BRAC SS&D/IMSP (MILSTRIP/MILSTRAP/Supply)