IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 2206<>-6221 

October 17,2013 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

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

Intra-Air Force Requirement for use of Priority Designator in DLMS 527D 

Prepositioned Materiel Receipt (PMR) (Supply/MILSTRAP) 

The attached change to Defense Logistics Manual (DLM) 4000.25, Defense Logistics 

Management System (DLMS) and DLM 4000.25-2, Military Standard Transaction Reporting 

and Accountability Procedures (MILSTRAP) is approved for immediate implementation. The 

updated DLMS implementation convention will be posted to the DLA Logistics Management 

Standards Office Web site at www.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp within 

1 0 days from the above date. 

Addressees may direct questions to Ms. Mary Jane Johnson, (703) 767-0677; DSN 427-

0677 or email: Mary.Jane.Johnson@dla.mil. Others may direct questions to their Service or 

Agency designated Supply PRC representative available at: 

www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: ODASD(SCI) 

Director 

DLA Logistics Management 

Standards Office 

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

Page 1 of 3

ATTACHMENT TO ADC 1080

Intra-Air Force Requirements for use of Priority Designator in DLMS 527D 

Prepositioned Materiel Receipt (PMR) (Supply/MILSTRAP)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Department of 

the Air Force, AFLCMC/ELS/HIAR, DSN 596-2012; Commercial (334) 416-2012

a. Technical POC: AFLCMC/HIAR, Integrated Logistics Solution – Supply (ILS-S)

b. Functional POC: AFLCMC/HIAR, ILS-S

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply - This requirement is mandatory for all

Pre-positioned Materiel Receipt (PMR) transactions originating from ILS-S (Air Force Retail

Supply)

b. Primary/Secondary Functional Process: Supply Chain Visibility and Accountability

3. REFERENCE: 

a. Defense Logistics Manual (DLM) 4000.25-2, Military Standard Transaction Reporting 

and Accountability Procedures (MILSTRAP)

b. Air Force Manual (AFMAN) 23-110

4. APPROVED CHANGE:

a. Background Information:

(1) Air Force uses the priority designator data under the Defense Logistics Standard 

Systems (DLSS) in the MILSTRAP (Reference 3.a.) legacy Document Identifier Code (DIC)

DW_, PMR (Other Than Procurement Instrument Source) transaction field, which is designated 

as multiuse for intra-Component data. Air Force cites the priority designator in DIC DW_, 

record position (rp) 60-61.

(2) Priority Designator is identified in Air Force Manual (AFMAN) 23-110 

(Reference 3.b.) for intra-Air Force use in rp 60-61 of MILSTRAP DIC DW_.

b. Description of Changes in Detail: This approved change request incorporates a data 

element in DLMS that is required to process accurately intra-Air Force data for the PMR. This 

change authorizes intra-Air Force use of the Priority Designator (LQ01 qualifier 79) in DLMS 

527D PMR.

c. Procedures:

(1) Revise DLM 4000.25-2 (MILSTRAP), Appendix 3.39 (DIC DW_), to 

acknowledge Air Force data currently used in MILSTRAP multiuse field designated for intra-
ADC 1080, Att

Page 2 of 3

Component use, in a footnote as follows (changes identified by bold red italics or double strikethough):

FIELD LEGEND

RECORD 

POSITIONS ENTRY AND INSTRUCTIONS

Multiuse 60-66 For intra-DoD Component use, enter data prescribed by the 

DoD Component.

1, 2, 3

1 For intra-Navy use, rp 60-66 identifies the standard unit price. (See ADC 63)

2 For intra-Army use, rp 60-61 identifies the priority designator. (See ADC 234)

3 For intra-Air Force use, rp 60-61 identifies the priority designator. (See ADC 1080). Priority Designator 

is identified in Army Regulation (AR) for intra-Army use in rp 60-61.

NOTE: As an administrative update, the MILSTRAP Administrator is deleting existing DIC DW_ footnote 3 

(i.e., “Priority Designator is identified in Army Regulation (AR) for intra-Army use in rp 60-61”). 

RATIONALE: It is not necessary or appropriate to cite the Service publication information in a DOD issuance. 

(2) Revise the DLMS 527D implementation convention (IC) as follows (changes 

identified by bold red italics or double strike-though):

Item Location Revision to 527D, Due-in/ Advance Receipt /Due 

Verification

Reason

1. DLMS 

Introductory 

Note

Add ADC 1080 to DLMS Introductory note 6:

- ADC 1080, Intra-Air Force Requirements for use of 

Priority Designator in DLMS 527D Prepositioned Materiel 

Receipt (PMR)

To identify DLMS 

changes included in the 

DLMS IC

2. 2/LQ01/130 Revise existing qualifier ‘79’ to add new DLMS note 2:

79 Priority Designator

DLMS Note: 1. Army uses to identify priority designator 

in nonprocurement source due-in and advance receipt 

information (ARI pre-positioned materiel receipt (PMR). 

Use of this data is meaningful to Army only. Army cites 

data in multiuse rp 60-61 of MILSTRAP DIC DF_ and 

DW_. Army Authorized DLMS migration enhancement 

for intra-Army use. See DLMS introductory note 4.g.

2. Air Force uses to identify priority designator in 

nonprocurement source PMR. Air Force cites data in 

multiuse rp 60-61 of MILSTRAP DIC DW_. Authorized 

DLMS migration enhancement for intra-Air Force use. 

See DLMS introductory note 4.g.

MILSTRAP 

Administrator 

administrative updates to 

DLMS Note 1.

Added DLMS note 2 to

document existing Air 

Force MILSTRAP data 

requirement in DLMS.

5. REASON FOR CHANGE: Air Force receiving systems that interface with the Air Force 

retail supply system require the priority designator to be on the PMR transaction (DLMS 527D

with Transaction Type Code DE/MILSTRAP legacy DIC DW_). The transaction fails when the 

priority designator is not present. Required for intra-Air Force use.
ADC 1080, Att

Page 3 of 3

6. ADVANTAGES AND DISADVANTAGES:

 a. Advantages: The major advantage to adding the priority designator to the transaction is that the 

527D PMR transactions will process successfully for due-ins created in the Air Force receiving systems. 

 b. Disadvantages: If the priority is not present in intra-Air Force PMR transactions, the 

transactions fail and Air Force users have to manually process the transaction into the system. This 

manual processing causes delays in receiving critical weapon systems spares. 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Upon release of the ADC.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF CHANGE: Air Force cost avoidance is defined by the number of hours 

spent having to manually research, edit, and reprocess each line of data to add in the missing priority 

field since the Contractor Inventory Control Point (CICP) software flags that field as 'mandatory'.

9. IMPACT: 

a. New DLMS Data Elements: None.

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS):

(1) Air Force: Changes as needed for intra-Air Force use of priority designator in 527D 

PMR under DLMS. The priority designator is already in use by Air Force systems using 

MILSTRAP legacy DIC DW_ PMR transactions. 

(2) DLA and Services other than Air Force: Approved change is for intra-Air Force use 

only; no system impact to other DOD Components.

d. DLA Transaction Services: Requires update to DLA Transaction Services maps to document 

Air Force data mapping for priority designator between legacy DIC DW_, rp 60-61 and DLMS 527D 

PMR (527D with 1/BR02/20 Transaction Type Code DE) for a mixed DLSS-DLMS environment.

e. Non-DLA Logistics Management Standards Office Publications: Air Force will 

update local Air Force policies as needed to document this DLMS requirement.

10. Proposed DLMS Change (PDC) 1080 Response Table:

Component Response to PDC 1080

Air Force Concur without comment

Marine Corps Concur without comment

Navy Concur without comment

DLA Concur without comment

USTRANSCOM Abstain