DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

July 31, 2014 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

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

1007C, Code Updates to the DLMS 842P Product Quality Deficiency Report 

(PQDR) Data Exchange (Supply/Deficiency Reporting) 

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

Management System, is approved for implementation. This change has no impact on scheduled 

implementation of the DLMS 842P currently targeted for November 2015. The updated DLMS 

implementation convention will be posted to the Defense Logistics Management Standards 

Office Web at www.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp within 10 days from 

the above date. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 

703-767-0676; DSN 427-0676 or email Ellen.Hilert@dla.mil. Others may direct questions to 

their Service or Agency designated Supply PRC or DOD PQDR Committee representative. 

Attachment 

As stated 

cc: 

ODASD (SCI) 

DOD PQDR Committee 

ct?~~ Director 

Defense Logistics Management 

Standards Office 
Attachment to ADC 1007C

Code Updates to the DLMS 842P Product Quality Deficiency Report 

(PQDR) Data Exchange

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: NAVSEA Logistics 

Center Portsmouth

2. FUNCTIONAL AREA: Supply, Product Quality Deficiency Reporting 

3. REFERENCE: 

a. Approved DLMS Change 1007, New DLMS 842P, Product Quality Deficiency 

Report (PQDR) Data Exchange and Enhanced Exhibit Tracking via Standard Logistics 

Transactions, October 1, 2012

b. Approved DLMS Change 1007A, Enhanced Pre-positioned Materiel Receipt (PMR) 

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

c. Approved DLMS Change 1007B, Administrative Update to the DLMS 842P Product 

Quality Deficiency Report (PQDR) Data Exchange (Supply/Deficiency Reporting) Exhibit 

Tracking, July 18, 2013

d. DLM 4000.25, Volume 3, Chapter 4, Transportation Reference Tables for DLMS 

Transactions

4. APPROVED CHANGE(S):

a. Overview of Change: This ADC documents new and revised codes for use in 

processing Product Quality Deficiency Reports (PQDR) and updates the DLMS Implementation 

Convention (IC) 842P as approved for implementation (References 3.a. through c.). This change 

also includes minor corrections of typographical errors and clarification for appropriate use of 

specific data elements and administrative updates to convert the DLMS supplement to an 

implementation convention (IC). This change also establishes the DLMS as the authoritative 

code source for selected PQDR-related data elements.

b. Approved Change in Detail: Data elements definitions, characteristics, and 

applicable code values and/or code sources are provided/updated for the following data elements. 

Refer to Attachments 1 and 2 for details. 

 status codes

 rebuttal codes

 credit codes

 exhibit distribution status codes (previously known as exhibit accounted 

for/received codes) 

 standard carrier alpha codes (SCAC) for the exhibit carrier

 exhibit delivery requirement codes (previously known as exhibit required/

requested/hold code)

Attachment, ADC 1007C

Page 1
 materiel disposition codes

 operating time at failure codes

 time since installation codes

 time since new/overhaul codes

c. Revisions to DLM 4000.25 Manuals: 

(1) Revise DLM 4000.25, Volume 3, Chapter 4, Transportation Reference Tables 

for DLMS Transactions to add the DLMS 842P to the Table C4.T1., Transportation Reference 

Tables and DLMS Supply Transactions:

45 Standard Carrier Alpha Code (SCAC) 842P, 856, 856S, 940R, 

945A

(2) Establish DLMS Volume 2, Appendix 7.27, Product Quality Deficiency 

Report (PQDR) Relevant Data Elements, as shown at Enclosure 1. Update Appendix 7 Index 

accordingly.

(3) Revise the DLMS 842P IC as shown at Enclosure 2: 

d. Staffing Response to PDC 1007C:

Originator Response/Comment Disposition

1. Army Concur. Noted.

2. Navy Concur. Noted.

3. PQDR joint 

Service/Agency 

implementation 

team conference 

call, July 21, 

2014 and July 28, 

2014

1. The need for inclusion of the disposal 

condition code could not be validated for 

initial release. 

2. Identify the following new/revised data 

elements for limited functionality so as not to 

impact the implementation schedule for initial 

release. PQDR initiating systems will have 

capability to add or update these data elements. 

DLA EBS will have capability to accept these 

elements, but will not have update capability:

PQDR Exhibit Distribution Status Code

PQDR Exhibit Delivery Requirement Code

Operating Time Codes

Carrier SCAC

1. ADC updated to remove all 

references to the disposal 

condition code. 

2. ADC has been updated to 

reflect agreement that selected 

new/revised data elements will 

accepted by DLA EBS from 

the initiating system. EBS will 

not have capability to modify 

these data elements.

Attachment, ADC 1007C

Page 2
Originator Response/Comment Disposition

4. Air Force Concur with comment:

1. It looks like we will need to better define 

some additional codes.

Engine Start-up and Stop (Shut-down)

Take-off and Landings are different depending 

on where you are physically, i.e. shore based 

and carrier based.

I think we all need to get together and discuss 

each Service’s operating times to determine 

which can be combined and which are 

separate, i.e. flight hours and cycles can be the 

same as long as the time itself is measured in 

hours.

2. Following the review of the status codes, 

we've interpreted all "/" to mean "and". If it 

meant "or" then a further code would be 

required. 

The review produced two new Active (Open) 

codes. Our proposals are:

AS -- Awaiting Supervisor or Board Review 

AZ -- Active in Dispute

The review also produced three new or revised 

Complete (Closed) codes. Our proposals are:

CF -- No Investigation - Exhibit Unavailable 

CL -- Fix deferred to later evolution or 

modification 

CQ -- Further action pending

Noted.

1. New codes reviewed by 

joint Service/Agency 

implementation team on July 

21, 2014. Definitions 

acceptable as updated. Refer 

to Table AP7.27.T8 Operating 

Time Codes.

2. All codes containing slash 

reviewed by joint Service/

Agency implementation team 

on July 21, 2014. As a result, 

Code CC Inactive/

Nonresponsive Investigation 

updated to read 

“Nonresponsive Investigation”

5. Marine Corps Concur Noted.

6. DLA Concur. Noted.

7. USTRANSCOM Abstains; there is no impact to 

USTRANSCOM systems based on this 

change.

Noted.

Attachment, ADC 1007C

Page 3
5. REASON FOR CHANGE: The changes included in this document are for correction and 

clarification purposes. The changes will ensure common understanding of the data mapping for 

development of system interfaces. This change also establishes the DLMS as the authoritative 

code source for selected PQDR-related data elements allowing for quicker turn-around for 

updates.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Accurate information. 

b. Disadvantages: None identified.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Initial implementation is 

targeted for November 2015. Implementation of the new and revised data elements identified in 

this change are not intended to impact initial implementation. 

8. IMPACT:

a. DLMS Data Elements:

(1) The data elements impacted by this change are shown at Enclosure 1. 

(2) The DLMS Unit of Measure Conversion Table will be updated to carry new 

values to support potential use of this table when transmitting Operating Time at Failure, Time 

Since New/Overhaul, and Time Since Installation. Technically, these codes do not require 

conversion since they do not represent a unit of issue or a purchase unit; however, to preclude 

processing problems by implementing systems, these codes will be added to the table. The name 

associated with the code values will differ within PQDR applications.

X12 Code X12 Name DoD Code DoD Usage Notes

14 Shot 14 Catapult Shots

7A Landings 7A Landings Local code pending X12 data 

maintenance

7C Flight Hours 7C Flight Hours Local code pending X12 data 

maintenance

b. Automated Information Systems (AIS): Clarification and updates provided for 

development and implementation.

c. DLA Transaction Services: Clarification and updates provided for development and 

implementation.

d. Non-DLA Logistics Management Standards Publications: Component internal 

guidance may require update.

Attachment, ADC 1007C

Page 4
Enclosure 1, New DLMS Data Elements 

A new appendix will be added to DLMS Volume 2, Appendix 7, Data Elements and Codes, as 

AP7.27, PQDR Relevant Data Elements. 

In addition, the data elements listed below will be added to the DLMS Dictionary (Logistics Data 

Resources Management System (LOGDRMS) as PQDR-related data elements sourced under the 

DLMS. Additional PQDR data elements may be added to this appendix over time.

AP7.27 APPENDIX 7.27

PRODUCT QUALITY DEFICIENCY REPORT (PQDR) 

RELEVANT DATA ELEMENTS

AP7.27. GENERAL. This appendix provides a consolidated reference resource for data 

elements and their associated code sets applicable to Product Quality Deficiency Report (PQDR) 

submissions, subsequent communication between trading partners, and responses. These data 

elements are applicable in all DoD PQDR applications under the DLMS. The data elements 

listed below are included in this appendix. Within the context of PQDR procedures, these data 

elements may be recognized by abbreviated names as indicated. Refer to Product Quality 

Deficiency Report (PQDR) Program (DLAR 4155.24/AR 702-7/SECNAVINST 4855.5B/AFR 

74-61) the DLMS Dictionary (Logistics Data Resources Management System (LOGDRMS) for 

additional PQDR data definitions and codes.

• Product Quality Deficiency Report (PQDR) Status Code. 

Also referred to as Status Code.

• Product Quality Deficiency Report (PQDR) Rebuttal/Controvert Code. 

Also referred to as Rebuttal Code.

• Product Quality Deficiency Report (PQDR) Credit Code. 

Also referred to as Credit Code.

• Product Quality Deficiency Report (PQDR) Exhibit Distribution Status Code.

Also referred to as Exhibit Accounted For/Received Code.

• Operating Time at Failure.

• Time Since Installation.

• Time Since New/Overhaul.

AP7.27.1 PRODUCT QUALITY DEFICIENCY REPORT (PQDR) STATUS CODE

Staffing Note: PQDR Committee approved August 28, 2012. 

AP7.27.1.1. Definition. A two-character alpha-numeric compound code consisting 

of the PQDR STATE (active or closed) in the first position, and either the active PQDR's LAST 

KEY EVENT CODE or the closed PQDR's CLOSURE REMARK CODE in the second position. 

Enclosure 1, ADC 1007C

Page 1
AP7.27.1.1.1. PQDR STATE: A single character alphabetic code indicating 

whether the status of a PQDR is "Active" (permitted value = A) or "Closed" (permitted value = 

C) 

AP7.27.1.1.2. LAST KEY EVENT CODE: A single character alpha-numeric 

code used to indicate the last key event accomplished in processing an active PQDR. Used with 

PQDR STATE = A.

AP7.27.1.1.3. CLOSURE REMARK CODE = A code used to indicate the 

circumstances under which a PQDR was closed. Used with PQDR STATE = C. 

AP7.27.1.2. Usage. Facilitates workflow efficiencies for functional users, and 

program management metrics for oversight and analyses of process performance and production 

issues.

AP7.27.1.3. DLMS 842P Reference: 2/LQ01/1050 Code GK.

AP7.27.1.4. PQDR Status Codes are listed in Table AP7.27.T1:

Table AP7.27.T1. PQDR Status Codes

Code Literal

<Blank> Draft Record

A1 Child PQDR

A2 Screening Pt Request For Information

A3 Action Point Request For Information

A4 Support Point Request For Information

A8 Awaiting Verification Of Corrective Action

A9 Stock Screened PQDR

AB Under Engineering Review

AC Investigation Requested Of Action Pt

AD Action Point Accepted PQDR for Investigation

AE Exhibit Requested

AF Exhibit Shipped

AG Case/PQDR Reopened

AH PQDR Rebutted Back To Support Pt

AI Information Only/Trending Purposes

AJ Awaiting Credit Recommendation Or Credit Reversal

AK Awaiting Other Closing Delay

AM Awaiting Final Materiel Disposition Instructions

AN Awaiting Funds

AO Record Returned To Originator

AP Action Pt Inv Report Submitted

AQ Investigation Requested Of Support Pt

AR Awaiting Reqs Approval/ECP

CA Invalid PQDR

CC Nonresponsive Investigation

CD Defect Previously Investigated

Enclosure 1, ADC 1007C

Page 2
Table AP7.27.T1. PQDR Status Codes

Code Literal

CE Enhancement

CF Exhibit Unavailable

CG Investigation Completed Without Exhibit (Not Requested)

CH No Investigation - Exhibit Damaged

CI Information Only/Reliability Data

CJ Investigation With Damaged Exhibit

CK Contractor Unwilling To Investigate

CN Manufacturing Sources Or Technical Data No Longer Available

CO Child PQDR

CP Investigation Completed With Exhibit

CR Stock Screened PQDR

CS No Closing Data Received From External System

CT Missing Necessary Information

CU Investigation Could Not Validate Defect

CV Corrected And Verified

CW Isolated Incident/Acceptable Risk

CX Cancelled Record

CY Closed Under Warranty Provisions

CZ Administrative Closing

AP7.27.2. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) REBUTTAL/

CONTROVERT CODE

Staffing Note: PQDR Committee approved August 18, 2012. 

AP7.27.2.1. Definition. A 2-character alpha compound code, consisting of the 

rebuttal “Point Of Origin” (Screening Point, or Action Point) in the first position, and the rebuttal 

“Reason” in the second position.

AP7.27.2.1.1. Point Of Origin: A single character alphabetic code indicating 

who generated the rebuttal: Action Point (permitted value = A) or Screening Point (permitted 

value = S). Originator’s rebuttal generates an official correspondence to the screening point for 

review, but it does not open a closed record. Screening point may accept request to reopen for 

originator and reopen PQDR for further investigation.

AP7.27.2.1.2. Reason: A single character alphabetic code indicating the reason 

for the rebuttal being generated. 

AP7.27.2.2. Usage. Provides mechanism to facilitate program oversight.

AP7.27.2.3. DLMS 842P Reference: 2/LQ01/1050 Code CW.

AP7.27.2.4. PQDR Rebuttal/Controvert Reason Codes are listed in 

Table AP2.27.T2:

Enclosure 1, ADC 1007C

Page 3
Table AP7.27.T2 PQDR Rebuttal/Controvert Reason Codes

Code Literal

C Root Cause Not Addressed

D Responsible Party Not Addressed

E Corrective Action Not Addressed

F Disposition Not Addressed

G Credit Not Addressed

H Preventive Action Not Addressed

I Incomplete Or Incorrect PQDR Information On Closing Letter

M Multiple Reasons For Rebuttal

N Disagree With Closing Response/Findings

O Other - Not Covered By A Defined Code

R Repeat Rebuttal

S Response Truncated Or Not Submitted In Proper Format

T Case Reopened Due To Delayed Receipt Of Exhibit Or Data

U Update Or Change Requested

V Response Needs Clarification

W Response Is For Wrong PQDR

AP7.27.3 PRODUCT QUALITY DEFICIENCY REPORT (PQDR) CREDIT CODE

Staffing Note: PQDR Committee approved January 17, 2013. 

AP7.27.3.1. Definition. A single character alpha code used to describe whether 

credit or other form of resolution is authorized. 

AP7.27.3.2. Usage. Used by Screening/Action point to provide the originator with 

current status of financial liability on reported materiel. Secondary usage is to support 

management metrics. This code appears in the 10th position of the PQDR Summary Code.

AP7.27.3.3. DLMS 842P Reference: 10th position of PQDR Summary Code at

2/REF01/0700 Code X3 

AP7.27.3.4. PQDR Credit Codes are listed in Table AP7.27.T3

Table AP7.27.T3 PQDR Credit Codes

Code Literal

F Repaired by User

P Vendor Replacement

R Vendor Repair

S Source of Supply Replacement

T Source of Supply Repair

W Credit Authorized

X No Credit Authorized

Enclosure 1, ADC 1007C

Page 4
AP7.27.4 PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

DISTRIBUTION STATUS CODE1

Staffing Note: PQDR Committee approved January 17, 2013. Originally approved as “Exhibit 

Accounted For/Received Code.” 

AP7.27.4.1. Definition. Code indicates status/control of exhibit during the 

transportation process. Transportation process starts when the originator passes materiel to 

shipper and ends when consignee takes control of the materiel.

AP7.27.4.2. Usage. To ensure proper and effective processing in order to maintain 

valid PQDR resolution time frames

AP7.27.4.3. DLMS 842P Reference: 2/REF01/0700 Code KC.

AP7.27.4.4. PQDR Exhibit Distribution Status Codes are listed in Table AP7.27.T4:

Table AP7.27.T4 PQDR Exhibit Distribution Status Codes

Code Literal

1 In transit (user still owner, but not in control)

2 In staging, awaiting onward transportation

3 Received by Consignee 

AP7.27.5. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT

CURRENT DISPOSITION CODE

Staffing Note: PQDR Committee approved October 10, 2012. 

AP7.27.5.1 Definition. A single character alpha code, used to identify the status of 

exhibit materiel from originator point of view on initial PQDR Submission.

AP7.27.5.2. Usage. Provide mechanism to identify exhibit initial locations. This

code appears in the 13th position of the PQDR Summary Code.

AP7.27.5.3. DLMS 842P Reference: 13th position of PQDR Summary Code at

2/REF01/0700 Code X3

AP7.27.5.4. PQDR Exhibit Current Disposition Codes are listed in Table AP7.27.T5:

Table AP7.27.T5 PQDR Exhibit Current Disposition Codes

Code Literal

H Holding Exhibit

D Disposed or Destroyed

R Repaired

O Other 

1 Refer to ADC 1007C.

Enclosure 1, ADC 1007C

Page 5

 
AP7.27.6. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

DELIVERY REQUIREMENT CODE2

Staffing Note: Originally approved as “Exhibit Required/Requested Hold Code.” 

AP7.27.6.1. Definition. A single character alpha code, used to identify the status of 

exhibit materiel from the action or support point of view. 

AP7.27.6.2. Usage. Use to identify the Exhibit Delivery Requirement Code from the 

Action or Support Point. This provides verification that the exhibit is required and should be 

sent or held by originator. 

AP7.27.6.3. DLMS 842P Reference: 2/REF01/0700 Code KK.

AP7.27.6.4. PQDR Exhibit Delivery Requirement Codes are listed in Table 

AP7.27.T6:

Table AP7.27.T6 PQDR Exhibit Delivery Requirement Code

Code Literal

H Hold Exhibit

N Exhibit Not Required

Q Exhibit Required (but not Requested)

R Exhibit Requested

 AP7.27.7. OPERATING TIME CODES

 AP7.27.7.1. Definition. A two character alphanumeric code, used for measure of time 

or events as listed in Table AP7.27.T8 for data elements: Operating Time at Failure, Time Since 

New/Overhaul, and Time Since Installation. 

 AP7.27.7.2. Usage. Use to identify the quantity of time a unit entered operational 

service as a new or overhauled item to time the deficiency was discovered. Operating Time 

Codes are mapped as Unit of Measure Codes associated with the applicable quantified value for 

Operating Time at Failure, Time Since New/Overhaul, or Time Since Installation.

Staffing Note: Operating Time at Failure is also used in the DLMS 842A/W Supply 

Discrepancy Report (SDR) for Foreign Military Sales quality deficiencies (2/QTY01/2700). 

However, in the SDR the time is always expressed as hours and minutes without the use of the 

Operating Time Codes.

 AP7.27.7.3. DLMS 842P Reference: 2/QTY01/2700. 

2 Ibid.

Enclosure 1, ADC 1007C

Page 6

 
 AP7.27.7.4. Operating Time Codes are listed in Table AP7.27.T8:

Table AP7.27.T8 Operating Time Codes3

Code Literal Notes

03 Seconds

14 Catapult Shots Used to document the number of launches an aircraft has 

been launched, i.e. aircraft catapult systems and/or 

unmanned air vehicles.

7A Landings Used to document the number of landings an aircraft has 

completed.

7C Flight Hours Used to document the amount of time in hours that an 

aircraft/equipment has been flying.

1N Starts

B7 Cycles Use to indicate cycles of equipment, e.g., engine start-up 

and stop, or take-off and landings.

DA Days

DH Miles

FT Foot

HR Hours

IS Arrestments Used to document the number of times an aircraft has 

engaged arresting gear to stop forward momentum of a 

routine or emergency landing or an aborted takeoff.

MJ Minutes

MO Months

RH Running or Operating Hours

RO Rounds Fired

YR Year

UN Unit, other than listed above

3 Codes 7A and 7C are established Local Codes. A data maintenance action has been submitted for establishment of 

“7A – Landings” and “7C – Flight Hours” in a future X12 Version. Refer to ADC 1007C.

Enclosure 1, ADC 1007C

Page 7

 
Enclosure 2, DLMS IC Revisions

# Location Revision to

DLMS 842P PQDR 

Data Exchange

Reason

1. DLMS 

Introductory Notes

Remove the reference to Federal Notes and identify all introductory 

notes as DLMS Notes.

Add new Introductory Notes 3 and 4 (renumber remaining notes):

3. Users operating under the DLMS must reference the Defense 

Logistics Manual (DLM) 4000.25, Volume 2, Chapter 24, and 

Appendix 7.27 for supplemental guidance supporting information 

exchange under the Product Quality Deficiency Report (PQDR) 

Program (DLAR 4155.24/AR 702-7/SECNAVINST 4855.5B/AFR 

74-61) at:

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp. 

4. Refer to the DLMS Dictionary (Logistics Data Resources 

Management System (LOGDRMS)) for selected data element 

definitions and code values, or cross-reference to the authoritative 

code source:

www.dla.mil/j6/dlmso/eApplications/LogDataAdmin/dlmsdicdir.asp. 

Add ADC 1007C to DLMS Introductory Note 7:

- ADC 1007C, Code Updates to the DLMS 842P Product 

Quality Deficiency Report (PQDR) Data Exchange 

(Supply/Deficiency Reporting) 

Administrative updates 

to convert DLMS 

supplement to an IC and 

provide location of code 

source and guidance. 

To identify DLMS 

changes included in the 

DLMS IC.

Enclosure 2, ADC 1007C

Page 1
# Location Revision to

DLMS 842P PQDR 

Data Exchange

Reason

2. 1/BNR05/0200 Revise DLMS notes for CL, FI, OI, and RE:

CL Closed

DLMS Note:

Use to indicate that the PQDR is in a closed status. More 

detailed status codes are available in the section REF 0700. 

Where applicable, provide detailed status using the PQDR 

Investigation Status Code (2/LQ01/1050 Code GK).

FI Final

DLMS Note:

Use to indicate that the PQDR investigation is completed. More 

detailed status codes are available in the section LQ01. Where 

applicable, provide detailed status using the PQDR 

Investigation Status Code (2/LQ01/1050 Code GK).

OI Open, Waiting for Cause and Corrective Action 

Implementation

DLMS Note:

Use to indicate that the PQDR investigation is not complete. 

More detailed status codes are available in the section LQ01. 

Where applicable, provide detailed status using the PQDR 

Investigation Status Code (2/LQ01/1050 Code GK).

RE Reopened

DLMS Note:

Use to indicate that the PQDR status has changed from closed 

to open in the sending system. Detailed status codes are 

available in the section LQ01. Where applicable, provide 

detailed status using the PQDR Investigation Status Code 

(2/LQ01/1050 Code GK).

Changes reference from 

REF 0700 to LQ01

3. 2/REF01/0700 Revise DLMS note for existing Code X3, PQDR Summary Code 

(only Credit Code portion is being updated):

X3 Defect Code Number

DLMS Note:

(not all notes are shown)

Credit Code (10th position)

PQDRII Definition: The Credit Code. Use Codes C-No Credit 

(Commercial Supplier), F-repaired by

user, G-No Credit (Gov’t Supplier), N-Credit (Commercial 

Supplier), P-Vendor Replacement, R-Vendor

Repair, S-Source of Supply replacement, U-Unknown, W-Credit 

Authorized, X-No Credit Authorized,

Updates Credit Codes.

Staffing Note: The 

PQDR Summary Code 

is a data string 

composed of multiple 

data elements. Although

this is not the 

recommended data 

construct under DLMS, 

in this case, it is the 

method used by multiple 

Component systems and 

is perpetuated from 

Enclosure 2, ADC 1007C

Page 2
# Location Revision to

DLMS 842P PQDR 

Data Exchange

Reason

Z-Credit (Gov’t Supplier) A single character alpha code used 

to describe whether credit or other form of resolution is 

authorized. Use only codes: F-Repaired by user, P-Vendor 

Replacement, R-Vendor Repair, S-Source of Supply 

Replacement, T-Source of Supply Repair, W-Credit 

Authorized, X-No Credit Authorized.

Add Qualifier KC and associated DLMS note:

KC Exhibit Distribution List

1. Cite the applicable PQDR Exhibit Distribution Status 

Code. This code indicates status/control of exhibit during the 

transportation process. Use only codes: 

1-In transit (user still owner, but not in control) 

2-In staging, awaiting onward transportation 

3-Received by consignee

2. Refer to ADC 1007C.

Add Qualifier KK and associated DLMS note:

KK Delivery Reference

DLMS Note:

1. Cite the applicable PQDR Exhibit Delivery Requirement 

Code to identify the status of exhibit materiel from the action 

or support point of view. Use only codes: 

H-Hold Exhibit

N-Exhibit Not Required

Q-Exhibit Required (but not yet Requested)

R-Exhibit Requested

2. Refer to ADC 1007C.

legacy business rules. 

The Credit Code is one 

element among many in 

the data string.)

Adds new PQDR 

Exhibit Distribution 

Status Code. This was 

originally intended to be 

called the Exhibit 

Accounted 

For/Received Code and 

is renamed here for 

better alignment with the 

X12 name.

Staffing Note: DLA 

will have functionality 

to receive, but will not 

have update capability 

for this data element.

Adds new PQDR 

Exhibit Delivery 

Requirement Code. This 

was originally intended 

to be called the Exhibit 

Required/Requested/H

old Code and is 

renamed here for better 

alignment with the X12 

name.

Staffing Note: DLA 

will have functionality 

to receive, but will not 

have update capability 

for this data element.

4. 2/LQ01/1050 Revise DLMS note for Code GK:

GK Investigation Status Code

DLMS Note:

1. Use to identify the PQDR Investigation Status Code to 

indicate the current status of the PQDR. 

2. Use only valid codes as prescribed under the DLMS; see 

Update provided for 

clarification of the code 

source.

Enclosure 2, ADC 1007C

Page 3
# Location Revision to

DLMS 842P PQDR 

Data Exchange

Reason

introductory DLMS Notes 3 and 4. 

5. 2/LQ01/1050 Revise DLMS Note for Code CW:

CW-Controvert Code

DLMS Note:

1. Use to identify the PQDR Rebuttal/Controvert Code. Must 

use in a reply rebuttal transaction (BNR01Code=RR).

2. Use only valid codes as prescribed under the DLMS; see 

introductory DLMS Notes 3 and 4.

Update provided for 

clarification of the code 

source.

6. 2/QTY01/2700 Revise DLMS notes for existing Code 02.

01 Discrete Quantity

DLMS Note: 

1. Use to identify the quantity of Time Since Installation. This 

is the time elapsed between installation and materiel failure.

2. PQDRII field size = 7.

02 Cumulative Quantity

DLMS Note:

1. Use to identify the quantity of Time Since New/Overhaul. 

This is the time elapsed since the last repair, or initial use for 

new items, and materiel failure.

2. PQDRII field size = 7.

OT Number of Operating Periods at Failure

DLMS Note:

1. Use to identify the Operating Time at Failure (OTAF). This 

is a measurement of time prior to failure. It describes how long 

a part was operated before failure. Equates to SF368, Block 7.

2. PQDRII field size = 15.

Clarification.

Shown for context as 

applicable to unit of 

measure updates listed 

below. 

7. 2/QTY03/2700 Revise DLMS notes and insert addition unit of measure codes:

Composite Unit of Measure

DLMS Note: 

1. Use to identify the discrepant/deficient quantity. Use multiple 

repetitions as needed to identify additional quantities associated with 

the complaint.

2. DLMS users see the Unit of Issue and Purchase Unit Conversion 

Table for available codes, except as listed below for Operating Time 

at Failure, Time Since New/Overhaul, and Time Since Installation.

3. PQDRII Definition: Type of standard unit the materiel was 

packaged in. Also used for measure of time or events as listed below 

for Operating Time at Failure, Time Since New/Overhaul, and 

Time Since Installation.

Clarification.

New codes are 

authorized for Operating 

Time at Failure, Time 

Since New/ Overhaul, 

and Time Since 

Installation as identified 

in bold italics.

Codes 7A and 7C are 

established Local Codes. 

A data maintenance 

action has been 

submitted for 

Enclosure 2, ADC 1007C

Page 4
# Location Revision to

DLMS 842P PQDR 

Data Exchange

Reason

QTY03-01 Unit or Basis for Measurement Code

DLMS Note: 

1. For QTY01 code 01, 02, or OT use one of the following 

Operating Time Codes.

2. Refer to ADC 1007C.

Code Name

03 Seconds

14 Shots

DLMS Note: Use to indicate number of “Catapult Shots;” this is

the number of launches an aircraft has been launched, i.e. aircraft 

catapult systems and/or unmanned air vehicles.

7A Landings

DLMS Note: Used to document the amount of landings an aircraft 

has completed. Code 7A is established as a local code. A data 

maintenance action has been submitted for establishment of “7A –

Landings” in a future X12 Version.

7C Flight Hours

DLMS Note: Used to document the amount of time in hours that 

an aircraft/equipment has been flying. Code 7C is established as a 

local code. A data maintenance action has been submitted for 

establishment of “7C – Flight Hours” in a future X12 Version.

1N Count

DLMS Note: Use to indicate number of “Starts” (time failure code 

STA).

B7 Cycles

DLMS Note: Use to indicate cycles of equipment, e.g., engine startup and stop, or take-off and landings.

DA Days

DH Miles

FT Foot

HR Hours

IS Stops 

DLMS Note: Use to indicate number of “Arrestments;” this is the 

number of times an aircraft has engaged arresting gear to stop 

forward momentum of a routine or emergency landing or an 

aborted takeoff.

MJ Minutes

MO Months

RH Running or Operating Hours

DLMS Note: Use to indicate “Under/Steaming Hours”

RO Round

DLMS Note: Use to indicate “Rounds Fired”.

YR Year

UN Unit

DLMS Note: Use to indicate unit of measure is “Other” (i.e., than 

those listed here time failure code OTH)

establishment of “7A –

Landings” and “7C –

Flight Hours” in a future 

X12 Version.

Staffing Note: DLA 

will have functionality 

to receive new codes 14, 

7A, 7C, IS, RH, and YR, 

but will not have update 

capability for this data 

element.

Staffing Note: The data 

element 

Operating Time at 

Failure is also used in 

the DLMS 842A/W 

Supply Discrepancy 

Report (SDR) for 

Foreign Military Sales 

quality deficiencies

without the Operating 

Time Codes. 

Enclosure 2, ADC 1007C

Page 5
# Location Revision to

DLMS 842P PQDR 

Data Exchange

Reason

8. 2/N101/2800 Add Qualifier CA and associated DLMS notes:

CA Carrier

DLMS Note:

1. Use to identify the PQDR exhibit carrier by Standard 

Carrier Alpha Code (SCAC). Used by the shipping activity to 

identify the carrier transporting the exhibit. 

2. If the SCAC is not available, cite “Hand” (Hand Carry) or 

“DTS” (Defense Transportation Service), as applicable.

3. Refer to United States Transportation Command 

(USTRANSCOM) Reference Data Management (TRDM) for 

valid codes.

4. Refer to ADC 1007C.

Adds the SCAC for 

identification of the 

carrier transporting the 

exhibit.

Staffing Note: PQDR 

Committee approved 

February 7, 2013. 

Staffing Note: DLA 

will have functionality 

to receive, but will not 

have update capability 

for this data element.

9. 2/N103/2800 Add DLMS Code 2:

2 Standard Carrier Alpha Code

Adds SCAC value.

10. 2/NTE01/3500 Delete Code VEC and associated DLMS Note:

VEC-Verification Comments

DLMS Note:

1..Use to identify the Exhibit Accounted For providing 

verification that the exhibit arrived at the correct location.

2. PQDRII field size = 10.

Required information 

converted to a code list 

and remapped to PQDR 

Exhibit Distribution 

Status Code at 

2/REF01/0700 Code 

KC. 

Enclosure 2, ADC 1007C

Page 6