*DLM 4000.25, Volume 2, January 22, 2024*

*Change 17*

**AP7.27 APPENDIX 7.27**

**PRODUCT QUALITY DEFICIENCY REPORT (PQDR) RELEVANT DATA ELEMENTS**

AP7.27.  GENERAL.  This appendix provides a consolidated reference resource for ***transaction sets,***data elements and their associated code sets applicable to Product Quality Deficiency Report (PQDR) submissions, subsequent communication between trading partners, and responses.  These ***transaction sets and***data elements are applicable in all DoD PQDR applications under the DLMS. Within the context of PQDR procedures, these ***transaction sets and*** data elements may be recognized by abbreviated names as indicated.  Refer to the DLMS Dictionary (Logistics Data Resources Management System (LOGDRMS) for additional PQDR data definitions and codes.

***AP7.27.1. PQDR Transaction Set Purpose Codes.***

***AP7.27.1.1. General Opening, Closing and Related Codes.  These codes process transactions that include but are not limited to; open, close, transfer, and return PQDRs to other PQDR processing points.***

***AP7.27.1.1.1. Original (Originator Forwards to Screening Point) (Transaction Set Purpose Code 00).  Used when the Originator forwards to the Screening Point.******Originators are required to execute this transaction set within 24 hours of discovery for Category I and three calendar days of discovery for Category II PQDRs.***

***AP7.27.1.1.2.  Forward to Action (Forward from Screening Point to Action Point) (Transaction Set Purpose Code FA). Used when the Screening Point forwards a PQDR to an Action Point and the Action Point does not exist within the same AIS.***

***AP7.27.1.1.3.  Forward to Support (Forward from Action Point to Support Point) (Transaction Set Purpose Code FS).  Used when the Action Point forwards a PQDR to a Support Point and the Support Point does not exist within the same system.***

***AP7.27.1.1.4.  Response (Final Reply from Support Point to Action Point) (Transaction Set Purpose Code 11).  Used when the Support Point completes their investigation and returns the PQDR to an Action Point and the Action Point does not exist within the same system.***

***AP7.27.1.1.5.  Completion Notification (Final Reply) from Action Point to Screening Point (Transaction Set Purpose Code CN).  Used when the Action Point completes their investigation and returns the PQDR to a Screening Point and the Screening Point does not exist within the same system.***

***AP7.27.1.1.6.  Not Processed (Misdirected) (Transaction Set Purpose Code 12).  Use to indicate that a PQDR was received by an incorrect Screening, Action, or Support Point and could not be processed.  The transaction returns the misdirected PQDR to the previous processing point.***

***AP7.27.1.1.7.  Delete (Retraction) (Transaction Set Purpose Code 03).  Used by Screening Points and Action Points to request ownership of a PQDR be transferred back to them.***

***AP7.27.1.1.7.1.  Where system capabilities exist within a single PQDR processing AIS, the AIS may be programmed to systemically move the PQDR back to the Screening Point or Action Point.  Use of (T-03) will not be programmed to systemically transfer a PQDR back to the Screening Point or Action Point from different AIS's.***

***AP7.27.1.1.8.  Rebuttal (Transaction Set Purpose Code RR).  Used to rebut an investigation response.  PQDR placed at the prior ownership level.***

***AP7.27.1.1.9.  Completion (Closure)(Transaction Set Purpose Code 53).  Used by Screening Point to close out and notify other PQDR processing points of PQDR process completion for a given PQDR.  Note: Only the Screening Point may perform this transaction.***

***AP7.27.1.2.  Exhibit Movement Transactions. PQDR exhibit movement transactions provide status and control over exhibit movements.  All PQDR processing points can use exhibit movement transactions.  Use of exhibit related transactions may not be used prior to Action Point acknowledgement of the PQDR.  Additionally, exhibit related transaction workflows must start with either an Action Point exhibit request or exhibit disposition.  The only exception to this rule will be when the PQDR is at the Support Point level after acknowledgment, where either the Action Point or Support Point may open the exhibit related workflows by sending an exhibit request transaction set. Use of this DLMS 842P for exhibit movement supplements the use of standard logistics transactions for receipt and shipment status.  When information copies of the receipt and shipment status are provided to the PDREP-AIS, they will be used to update the exhibit movement and disseminated as appropriate.***

***AP7.27.1.2.1.  Exhibit Request (Transaction Set Purpose Code 13) Used to request the exhibit and provide shipping information.***

***AP7.27.1.2.1.1.  When an exhibit is required to complete a PQD investigation, this transaction will open the ability to send exhibit shipped (T-14) and exhibit status update request (T-10) transactions.  If the T-14 or T-10 are provided prior to T-13, it will result in a transaction rejection.***

***AP7.27.1.2.1.2.  With exception to when the PQDR is at the Support Point level after acknowledgement, where either the Action Point or Support Point may transmit the request, initial use of this transaction at any other level will be restricted to the Action Point.  Action point use of this code will open the ability for the Screening Point to send the exhibit request transaction to Originator.***

***AP7.27.1.2.2.  Advance Notification (Exhibit Shipped Notification) (Transaction Set Purpose Code 14).  Used to provide exhibit shipment information to the requestor.***

***AP7.27.1.2.2.1.  When an exhibit is requested, the exhibit shipped transaction will open the ability to transmit the exhibit receipt (ER) transaction.***

***AP7.27.1.2.2.2.  When the PQDR is at the Action Point level after acknowledgement, use of this transaction will be limited to the Originator and Screening Point.***

***AP7.27.1.2.2.3.  If the PQDR has been assigned to a Support Point, and is at the Support Point after acknowledgement level, the Originator, Screening Point and Action Point may transmit the exhibit shipped transaction set.***

***AP7.27.1.2.2.4.  If the PQDR has been assigned to a Support Point, and the PQDR has been moved to the Action Point from Support Point level, all PQDR processing points may transmit this transaction.***

***AP7.27.1.2.3.  Exhibit Receipt (Transaction Set Purpose Code ER).  Used to document exhibit receipt. When the PQDR is located at the Action after acknowledgment level, only the Screening Point and Action Point may have use of this transaction.  After this point, either the Screening Point, Action Point, or Support Point may transmit an exhibit receipt transaction.  Note: If sent as a late exhibit receipt, PQDR is reassigned to the sender’s level.***

***AP7.27.1.2.4.  Not Found Exhibit Tracer (Transaction Set Purpose Code 10).  Used by exhibit requestor to request status or follow up on an exhibit request.***

***AP7.27.1.2.5.  Material Disposition (Final Materiel Disposition) (Transaction Set Purpose Code MD).  Material Disposition must be provided prior to PQDR closure.***

***AP7.27.1.2.5.1.  Used by the Screening Point, Action Point and Support Point after the investigation is complete to provide final materiel disposition instructions.  If a Support Point has been assigned and the PQDR is at the Support Point after acknowledgment level, only the Support Point may use this transaction at this level.***

***AP7.27.1.2.6.  Exhibit Disposition Confirmation) (Transaction Set Purpose Code ED).  Used by the current exhibit holder to confirm compliance with materiel disposition instructions.***

***AP7.27.1.2.6.1.  Use of this transaction may be used any time after Material Disposition (T-MD) has been provided and may continue to be used after the Screening Point closes the report (T-53).  This allows for reports to continue to be updated in situations such as long-term overhaul corrective actions by vendors that will take place over months or years, while not unnecessarily keeping the report open.***

***AP7.27.1.3.  General Information Transactions. The PQDR general information transactions provide information or status regarding the PQDR without changing ownership.***

***AP7.27.1.3.1.  Status (Acknowledge)Transaction Set Purpose Code 08). Used to acknowledge that a PQDR was received and provide current status to the previous point.  Screening Points, Action Points and Support Points are all required to provide this transaction set within 24 hours for Category I and three business days for Category II PQDRs.***

***AP7.27.1.3.2.  Incremental (Interim Reply) (Transaction Set Purpose Code 25).  Used by Support or Action Point to provide investigation status of the PQDR to the previous owner.***

***AP7.27.1.3.3.  Corrected (General Correspondence) (Transaction Set Purpose Code CO).  Used to transmit a general correspondence information concerning the PQDR status from the sender to the receiver, or to send corrections with an explanation of changes.******For inter-service PQDRs, the Originating Point may only submit this transaction to the Screening Point.  This transaction will also be used to inform other PQDR processing points when Major Data Element changes are required after they have acknowledged receipt of the PQDR.***

***AP7.27.1.3.4.  Follow-up (Follow-up for Status) (Transaction Set Purpose Code 45).  A systemically generated transaction used to request a status when a processing point has not provided investigation status via interim reply or the like.***

***AP7.27.1.3.5.  Cancellation (Transaction Set Purpose Code 01).  Used when a PQDR is cancelled.***

***AP7.27.1.3.5.1.  Cancellations may take place at the request of the Screening Point when major data element changes are required to a PQDR.  Major data element changes include the RCN, NIIN/NSN, contract number and CAGE.  These data elements have the ability to change the scope and responsible parties associated with the investigation.  Note: Only Screening Points may cancel a PQDR. and cancelled PQDRs cannot be reopened.***

***AP7.27.1.3.6.  Delegate to Alternate (Delegate to Alternate Support Point) (Transaction Set Purpose Code DA).  Used to document Action Point or responsible Support Point delegation to an entity that does not support PQDR investigations through a PQDR AIS, such as Engineering Support Activities (ESA).***

***AP7.27.1.3.7.  Transaction Set Purpose Code DA. may be used by either the Action Point or responsible Support Point without systemically changing the initial responsible Support Point.  Use of this transaction set in conjunction with the systemic assignment of a traditional Support Point, such as DCMA, will require PDREP-AIS to provide an information copy(T-22) to the Support Point assigned at the Support Point level for the PQDR.***

***AP7.27.1.3.8.  Transfer (Redirect/Transfer) (Transaction Set Purpose Code 47).  Used to redirect a PQDR to another Screening Point, Action Point, or Support Point within the component due to major data element changes when the Screening Point determines that a cancellation is not a preferred resolution.***

***AP7.27.1.3.9.  Reopen (Transaction Set Purpose Code RO).  Used when a PQDR is reopened by the system sending the transaction and a PQDR needs to be reopened in the receiving system.  This transaction notifies other systems that a PQDR has been reopened by the Screening Point, or that the other PQDR processing points (Originator, Action, or Support Point) have requested that the PQDR to be reopened.***

***AP7.27.1.3.10.  Status Update (Transaction Set Purpose Code SU).  Used to send an update to correct or append specific data fields in another AIS. This element may be populated/updated by the Screening Point, Action Point or Support Point for minor changes. Only the Screening Point for minor changes.  Only the Screening Point may use the SU transaction or make major data element changes (RCN, NIIN/NSN, Contract Number or CAGE Code).  In order for the Screening Point to make a major data element change using the SU transaction, the PQDR must be at the Screening Point level.  The use of the SU transaction other than specified will result in a (T-44).***

***AP7.27.1.3.11.  Notice of Defect (Transaction Set Purpose Code FC).  Used when Support Point sends PQDR investigation request to a contractor.***

***AP7.27.1.3.12.  Information Copy (Transaction Set Purpose Code 22).  Used to send information copy of PQDR to another system.  Used for dissemination to non-action activities outside of the PQDR process in another system.  Used to provide PQDR to other agencies with a need to know.  All data fields should be sent to present the entire PQDR to the receiver.***

***AP7.27.1.4.  System Transactions.  System transactions are used to confirm data receipt and communicate transaction failures to the sending system.***

***AP7.27.1.4.1.  Rejection (Transaction Rejection) (Transaction Set Purpose Code 44).  Used when the 842P transaction is non-compliant with this standard or when a recipient system of an 842P is unable to process a transaction due to its data requirements (i.e., duplicate RCN).  This transaction is both system generated, and user defined.***

***AP7.27.1.4.2.  Confirmation (Confirmation of Transaction Receipt) (Transaction Set Purpose Code 06).  Used by an automated IT system to confirm transaction receipt from another system.***

***AP7.27.2.  PRODUCT QUALITY DEFICIENCY REPORT SPECIFIC DATA ELEMENTS.***

***AP7.27.2.1.***Product Quality Deficiency Report (PQDR) Status Code.

***AP7.27.2.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.  

***AP7.27.2.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.2.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 ***with (T-53)***to indicate the circumstances under which a PQDR was closed.  Used with PQDR STATE = C.  

***AP7.27.2.2***.  Usage. Facilitates workflow efficiencies for functional users, and program management metrics for oversight and analyses of process performance and production issues.

***AP7.27.2.3****.*  DLMS 842P Reference***:  2/LQ01/1050 Code PQS Product Quality Deficiency Reporting Status Code.***

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

*********AP7.27.3*.**PRODUCT QUALITY DEFICIENCY REPORT (PQDR) REBUTTAL/ CONTROVERT CODE

***AP7.27.3.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.3.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.3.1.2.***  Reason: A single character alphabetic code indicating the reason for the rebuttal being generated. 

***AP7.27.3.2.***Usage. Provides mechanism to facilitate program oversight.

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

***AP7.27.3.4****.*  PQDR Rebuttal/Controvert Reason Codes are listed in Table AP7.27.T2:

***AP7.27.4****.*PRODUCT QUALITY DEFICIENCY REPORT (PQDR) CREDIT CODE

***AP7.27.4.1.***Definition.  A single character alpha code used to describe whether credit or other form of resolution is authorized.  

***AP7.27.4.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.  

***AP7.27.4.3*.**  DLMS 842P Reference: ***2/LQ01/1050/P2C – PQDR Credit Code (new data element).***

***AP7.27.4.4***.  PQDR Credit Codes are listed in Table AP7.27.T3

	AP7.27.5.  PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT CURRENT DISPOSITION CODE

		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.  

		AP7.27.5.3.  DLMS ***842P Reference: 2/LQ01/1050/CDC – Current Disposition Code (new data element).***

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

	AP7.27.6.  PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT ***DELIVERY REQUIREMENT***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/LQ01/1050 Code PQR Product Quality Exhibit Delivery Requirement Code.***

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

	AP7.27.7.  PRODUCT QUALITY DEFICIENCY REPORT (PQDR)***OPERATING TIME AT FAILURE*** CODE AP

		AP7.27.7.1.  Definition.  A two character alphanumeric code, used for measure of time or events as listed in Table AP7.27.T7 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.

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

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

***AP7.27.8.******Product Quality Deficiency Report (PQDR) Reject Advice Code.***

***AP7.27.8.1.  Definition.  A two-position alpha code used with transaction set purpose code 44, identifying the reason a transaction was rejected.***

***AP7.27.8.2.  Usage.  Informs the originator of a transaction, the reason for rejection, and indicates return of the transaction for correction and resubmission.***

***AP7.27.8.3.  DLMS 842P Reference: 2/LQ01/1050/RAC PQRD Reject Advice Code. (new data element)***

***AP7.27.8.4.  PQDR Reject Advice Codes are listed in Table AP7.27.T8:***

***Table AP7.27.T8. Reject Advice Code.***

***AP7.27.9.******Product Quality Deficiency Report (PQDR) Retract Reason Code.***

***AP7.27.9.1.  Definition.  A two-position alpha numeric code used with transaction set purpose code 03 to describe the reason for requesting the PQDR be returned to the previous level.***

***AP7.27.9.2.  Usage.  Request a PQDR be returned back to the previous level due to incorrect routing or to make major data element changes to the PQDR that could result in changes to the Screening Point, Action Point or Support Point. .***

***AP7.27.9.3.  DLMS 842P Reference: 2/LQ01/1050/PQC PQDR Retract Reason Code (new data element)***

***AP7.27.10.******Product Quality Deficiency Report (PQDR) General Correspondence Purpose Code.***

***AP7.27.10.1.  Definition.  A two-position alpha code used with transaction set purpose code CO, informing the purpose for the general correspondence.***

***AP7.27.10.2.  Usage.  Informs the recipient of the main purpose of the communication, i.e., gain in discrepant quantity, decrease in discrepant quantity, point of contact change, etc.***

***AP7.27.10.4.  DLMS 842P Reference: 2/LQ01/1050/GCP PQDR General Correspondence Purpose Code (new data element)***

******

***AP7.27.11.******Product Quality Deficiency Report (PQDR) Interim Reply Codes.***

***AP7.27.11.1.  Definition.  A two- position alpha code describing the current interim status causing delay the delay in the PQDR investigation.***

***AP7.27.11.2.  Usage.  Informs the recipient of the status and reason that the investigation is pending final completion.***

***AP7.27.11.3.  DLMS 842P Reference: 2/LQ01/1050/IRC PQDR Interim Reply Code (new data element).***

***AP7.27.12.******Product Quality Deficiency Report (PQDR) Cancellation Codes.***

***AP7.27.12.1.  Definition.  A two-position numeric code used with transaction set purpose code 01, describing the reason for PQDR cancellation.***

***AP7.27.12.2.  Usage.  Informs the recipient why the PQDR was cancelled.***

***AP7.27.12.3.  DLMS 842P Reference: 2/LQ01/1050/PCC PQDR Cancellation Code (new data element).***

***AP7.27.T12  PQDR Cancellation Codes***

***AP7.27.13.  Defect Code. Originators are required to provide a Defect Code as part of the Transaction Set Purpose Code 00 data transmission, detailing what the Originator believes the cause of deficiency is.***

***AP7.27.13.1.  Definition.  A three-position alpha numeric code detailing what the Originator of the PQDR believes is the detailed cause of the defect.  These codes are identical to the Detailed Cause codes required to be used by Action Point or Support Points at the conclusion of the PQDR investigation.***

***AP7.27.12.2.  Usage.  Informs the recipient what the Originator believes is the detailed cause of the quality deficiency.***

***AP7.27.12.3.  DLMS 842P Reference: 2/LQ01/1050/PDD PQDR Discovery Code (new data element).***

***Table AP7. 27.T13. Discovery Defect Codes***

***AP7. 27.3.  Product Quality Deficiency Investigative Closing Codes.***

***AP7. 27. 13.1.  The information to be entered in each data element is***

***dependent upon the type and cause of the deficiency and the information requested may not be appropriate in all cases. The information requested is typical when the cause of the deficiency is due to non-conformance with contract requirements.  The investigative closing codes provide specific details about the findings of the investigation.  Together these codes make up seven segments of investigation related data forming a nine-position code referred to as the Summary Code.***

***AP7.27.13.2.  The seven segments of closing data include (1) defect***

***responsibility, (2) severity of the defect, (3) broad classification of the cause, (4) detailed cause of the defect, (5) preventative action taken because of the defect, (6) corrective action taken for the defective materiel, and (7) disposition of the deficient materiel.  Each segment and their corresponding codes can be found in 27.T14 through 27.T20.***

***AP7.27.T14. SEGMENT 1 – Deficiency Responsibility - 1st Position***

***842P Reference: 2/LQ01/1050/DRC – Deficiency Responsibility Code (new data element).***

***Table AP7.27.T15. SEGMENT 2 - Severity of Defect - 2nd Position***

***842P Reference: 2/LQ01/1050/SDC – Severity of Defect Code (new data element).***

***Table AP7.27.T16.  SEGMENT 3 - Broad Cause - 3rd Position***

***842P Reference: 2/LQ01/1050/BCD – Broad Cause of Defect Code (new data element).***

***Table AP7.27.T17. SEGMENT 4 - Detailed Cause - 4th, 5th, and 6th Position***

***842P Reference: 2/LQ01/1050/PDC – PDQR Detailed Cause Code (new data element).***

***Table AP7.27.T18. SEGMENT 5 - Preventative Action 7th Position***

***842P Reference: 2/LQ01/1050/PAT – Preventative Action Taken Code (new data element).***

***Table AP7.27.T19. SEGMENT 6 - Corrective Action 8th Position***

***842P Reference: 2/LQ01/1050/CAT – Corrective Action Taken Code (new data element).***

***Table AP7.27.T20. SEGMENT 7 - Final Exhibit Disposition - 9th Position***

***DLMS 842P Reference: 2/LQ01/1050/FEC – Final Exhibit Disposition Code (new data element).***

AP7.27-8	APPENDIX 7.27