CN&GT_Support_Services_QASP_-_Final_-_Preaward.pdf

BY ORDER OF THE HQ ACC ACQUISITION

DIRECTOR MANAGEMENT AND

INTEGRATION CENTER

30 Jan 2017 Revision: 1

CN&GT Support Services

(FA4890-XX-X-XXXX)

Quality Assurance Surveillance Plan

COMPLIANCE WITH THIS DOCUMENT IS MANDATORY

NOTICE: This Document is available in digital format through ACC AMIC/DRQC

OPR: ACC AMIC/DRQC Reviewed by: ACC AMIC/PMC William J. McKee, NH-03 Michael T. Maynard, NH-04 Quality Assurance Manager Division Chief/Program Manager

Accepted by: ACC AMIC/PKDA James A. Robinson, NH-03 Contracting Officer

REVISIONS

REVISION DATE DESCRIPTION INITIALS &

DATE

Original 19 Sep 16 Original Document WJM 19 Sep 16 1 30 Jan 17 Minor updates WJM 30 Jan 17

TABLE OF CONTENTS

Section Page

1.0 SCOPE 4

1.1 Purpose 4

1.2 Application

1.3 Related Documents

2.0 MANAGEMENT LOCATIONS AND KEY PERSONNEL 4

2.1 Contract Management Locations 4

2.2 Contract Management Team 4

2.3 Contractor Key Personnel 5

3.0 CONTRACT SURVEILLANCE 6

3.1 Surveillance Methods 6

3.2 Surveillance Documents 8

3.3 Assessing Performance 9

4.0 INVOICES RECIEPT ACCEPTANCE and PROPERTY TRANSFER

(iRAPT)

4.1 Validating Receiving Reports 12

4.2 Certifying Receiving Reports 12

4.3 Rejecting Receiving Reports 12

5.0 CONTRACTING OFFICER REPRESENTATIVE (COR) FOLDER 13

TABLES

1 Deliverables 8 2 Services Summary 9 3 Non-conformance Notifications 10 4 COR Folder Tabs and Contents 13

ATTACHMENTS 14

1 First or Second Notice Template 14 2 Corrective Action Request (CAR) Template Surveillance Checklist 15

1.0 Scope. The Quality Assurance Surveillance Plan (QASP) is applicable to personnel performing contract surveillance audits in accordance with (IAW) Federal Acquisition Regulation (FAR) Part 46, Quality Assurance; Department of Defense FAR Supplement (DFARS) Subpart and PGI 201.602-2 , Contracting Officer Responsibilities; Air Force FAR Supplement (AFFARS) Mandatory Procedures (MP) 5346-103, Contracting Office Responsibilities, The Quality Assurance Program; Air Force Instruction (AFI) 63-138 Acquisition of Services, AFI 63-501 Air Force Acquisition Quality Program; and organizational policy. It is designed to provide the Contracting Officer’s Representative (COR) a systematic surveillance method for each service identified in the Performance Work Statement (PWS) for each contract. The COR develop the methods for administering and evaluating contract performance. The Quality Assurance Program Coordinator (QAPC) and Program Manager (PM) or Contracting Manager (CM), will review these methods, which are then accepted or rejected by the Contracting Officer (CO).

1.1 Purpose. This document defines the surveillance policy, procedures, and associated methods used by CORs for planning, preparing, performing, analyzing, and reporting Contractor performance. This QASP provides a systematic surveillance method to evaluate the services received from the Contractor, and NOT to address the details of how the Contractor accomplishes the work.

1.2 Application: This QASP is used by all parties involved with assessing Contractor performance and is for the use of PMs, QAMs, CORs and CO. The Contractor may receive a courtesy copy in order to further enhance communications with the Contractor, but shall not be considered as part of the contract.

1.3 Related Documents

Contract FA4890-XX-X-XXXX ACC AMIC Quality Management System Manual

2.0 MANAGEMENT LOCATIONS AND KEY PERSONNEL.

2.1 The address for Contracting Management is:

ACC AMIC/PKDA

Building 664 129 Andrews St. (Suite 110)

JBLE 23665-2788

2.2 Contracting Management Team.

Contracting Officer (CO). Contracting Officer (CO): CO duties are detailed in FAR subpart 1.602-2, Contracting Officer Responsibilities, and AFFARS MP5346.103, Contracting Officer Responsibilities. The CO is the ONLY Government agent authorized to contractually obligate the Government. The CO is also the individual who will sign any notifications to Contractors regarding performance issues and accepts Government surveillance methods utilized for each http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/01.htm#P1506_47227 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/affars/MP5346.103.htm#P-1_0 task order (TO). The CO (James Robinson) can be reached at DSN: 575-7706 or Commercial 757-225-7706.

2.2.1 Contract Manager (CM): The CM is the Government agent within the contracting office who performs day-to-day administration of the contract.

2.2.2 Program Manager (PM). The PM maintains overall program management responsibility and is the lead to ensure mission accomplishment. The PM serves as the principal technical expert on the multi-functional team and provides guidance and approvals for the technical effort as it relates to an element of work solely within the existing requirements of the contract. In addition, the PM coordinates with the CO for all contractual issues. The PM is the interface between the requirement owner(s) and the CO, and also manages the program budget within appropriated funds. The PM (Mike Maynard) can be reached at DSN: 574-9495 or Commercial (757) 764-9495.

2.2.3 Quality Assurance Program Coordinator (QAPC)/Quality Assurance Manager (QAM).

The QAPC assists the CO and QAM in managing the overall QA program and supports customers in developing and adhering to TO-specific QASPs. The QAPC (William McKee) can be reached at DSN: 574-9373 or Commercial 757-764-9373.

2.2.4 Contracting Officer Representative (COR). CORs are assigned, designated and have responsibilities as outlined in MP503.1.602-2(d). The COR is ultimately responsible for implementing all QA matters and procedures. COR(s) should be at a level where other duties don’t prevent proper oversight of Contractor performance. The COR must maintain both technical competency and evaluation proficiency in Contractor surveillance procedures. The COR cannot assume duties until assigned by the requiring agency, completed COR required training (CO/QAPC and CO led training), and appointed by the CO.

2.2.4.1 To be effective, CORs must maintain professional, non-adversarial relationships, which include positive and open communications with the QAM, CO, PM, and the Contractor. The foundation of this relationship is built upon regular, objective, fair, and consistent evaluations of Contractor performance against contract requirements, and the ability to discuss inspection results, trends, and items of mutual interest with all affected parties.

2.2.4.2 Primary COR: The Primary COR is fully trained and qualified in the quality assurance program. The Primary COR assists with requirements development and definition, performance work statement (PWS) modifications, deficiency resolution, and manages the overall risk and past performance (CPARS) programs. The Primary COR is responsible for assisting with the development of audit schedules, creating the monthly report in the Contract Management System (CMS) and providing guidance and advice to the PM and CO. The COR issues all First and Second notices and submits Corrective Action Requests (CAR) to the CO, and tracks all nonconformances. For the purposes of this QASP, the Primary COR and the QAM are the same individual.

2.2.5 Contractor Key Personnel. TBD

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/affars/MP5301.602-2(d).htm#TopOfPage

2.2.6 Project Manager (PM). The Contractor’s PM is TBD. The PM is responsible for the overall execution of the task order. This individual will serve as the focal point for the CM/CO and/or PM assigned to the contract and may interface with the customer, as needed.

3.0 CONTRACT SURVEILLANCE. The COR function is responsible for a wide range of surveillance requirements that effectively measure and evaluate Contractor performance. The Contractor, not the Government, is responsible for task order management and Quality Control (QC) actions to meet the terms of the contract. However, because of the non-commercial nature of the work performed by Contractors, the Government cannot rely solely on the Contractor’s quality program but must have a method to oversee the entire contracting process. The Government does this through the QASP and can inspect or test all services called for by the contract, to the extent practicable, at all times and places, during the term of the contract. The COR contribution is comprised of professional, non-adversarial relationships, which include positive and open communications with the CO, PM, QAPC/QAM, and the Contractor. The foundation of this relationship is built upon regular, objective, fair, and consistent COR evaluations of Contractor performance against contract requirements, and the ability to discuss inspection results, trends, and items of mutual interest with the Contractor. The COR uses the methods in this QASP and the PWS to achieve this goal.

3.1 Surveillance Methods. Three primary methods of surveillance are normally used: one hundred percent inspection, periodic audits and customer complaints. Other methods of surveillance may be implemented based on contractor performance. Information obtained from these activities may be used to ascertain whether or not Contractor performance is compatible with contract and mission objectives and by the CO for actions relating to the Contractor.

3.1.1 One Hundred Percent Inspection. This method will be used for Contractor submissions, products, and deliverables (tangible items). CORs will use the one hundred percent inspection method to evaluate all reports delivered under paragraph 9.0. The COR in conjunction with the CO, PM, QAPC/QAM, accepts or rejects these products based on the criteria and performance standards as outlined in the Services Summary. The COR also documents all results of inspection actions, and subsequent Contractor re-performance taskings, if applicable.

3.1.2 Periodic Audit. This type of surveillance consists of evaluating products/services not surveilled via one hundred percent inspection or by customer survey, and is implemented at a pre-defined frequency. An example of periodic audit is performing monthly inspections of class training conducted by the Contractor or weekly inspection of a Contractor’s process in developing training manuals.

3.1.3 Customer Survey or Customer Complaint. Although usually not a primary method, this is a valuable supplement to other, more systematic methods of surveillance. For example, in a case where random sampling indicates unsatisfactory service, customer complaints can be used as substantiating evidence. In certain situations, where customers complain consistently when the quality of performance is poor (e.g., dining facilities, custodial services), customer surveys and customer complaints may be a primary surveillance method, and customer satisfaction an appropriate performance standard. In all cases, complaints will be documented, preferably on a standard form. All customer complaints will be forwarded to the COR. Information obtained from customer complaint activities may be used by the CO for actions relating to the Contractor.

3.1.4 Random sampling may be used as an audit technique. This type of audit is used for a large control group where 100% inspection is not feasible. Random sampling requires a complete listing of all the items in the population.

3.2 Surveillance Documents.

3.2.1 Deliverables. All deliverables will be reviewed for timeliness, accuracy, and format (See Table 1).

Table 1 – Contract Deliverables Deliverable Details

Management/Staffing Plan Organizational Conflict of Interest (OCI) Plan

Reference: PWS paragraphs 4.5.1 and 4.5.2 Due Date: All items/plans shall be submitted as part of the Proposal, and will be incorporated into the contract.

Delivery: All documents shall be delivered IAW the specified PWS paragraphs and IAW the criteria established in the RFP.

Updates: The Contractor shall provide any changes or updates to the USG CO, PM and COR for USG review and acceptance prior to Contractor implementation.

Quality Manual

Reference: PWS paragraph 3 and subparagraphs and 4.5.3 and subparagraphs Due Date/Delivery: The Contractor shall deliver a complete Quality Manual to the USG PM and COR NLT 30 calendar days after contract award.

Updates: The Contractor shall provide any changes or updates to the USG PM and COR for USG review and acceptance prior to Contractor implementation.

Enterprise-wide Contractor Manpower Reporting Application (eCMRA)

Reference: PWS paragraph 4.5.4 Due Date/Delivery: The Contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract by completing all required data fields at http://www.ecmra.mil. Details: Reporting will be for the labor performance during each USG FY, 1 October - 30 September of each calendar year. While inputs may be reported any time during the FY, all data shall be reported NLT 31 October of each calendar year.

Contractors may direct questions to the eCMRA help desk.

Initial Performance Report

Reference: PWS paragraph 4.5.5 Due Date/Delivery: The Contractor shall report contract status to the USG COR and PM for USG review and acceptance NLT 30 calendar days after ID/IQ contract award.

Contractor’s progress, status report, and management report

Reference: PWS Paragraph: 4.5.6 Due Date: Monthly, 15th of each month Delivery: The Contractor shall report contract status to the USG CO, COR and PM

Contractor Post TDY Trip Reports

Reference: PWS Paragraph: 4.5.7 Due Date: 5 duty days after each TDY Delivery: The Contractor shall provide reports to the USG CO, COR and PM http://www.ecmra.mil/

3.2.2 Services Summary. The Services Summary is a list of critical tasks that must be performed by the Contractor, the performance threshold, and the method of surveillance the COR will use to validate/inspect these tasks. Inspection of each task will be documented in the COR folder or the Contractor Management System (CMS).

Table 2 Services Summary

Performance Objective Performance Standard Performance Threshold

Provide qualified people for contract performance PWS paragraph 2.0 and subparagraphs

Qualified personnel are in place at performance start.

Performance is acceptable when qualified personnel are in place for contract performance with minimal to no delays in performance start, unless previously negotiated by the CO.

Retain personnel with specified/awarded qualifications PWS paragraph 6 and subparagraphs

Effectively replaces/substitutes personnel, both USG-identified and Contractor-identified

Performance is acceptable when:

a) Vacancies do not exceed 14 calendar days (Key personnel)/28 calendar days (all non-key personnel) after date vacancy occurs to submission of replacement candidate to PM/COR for CO acceptance AND (for OCONUS positions) simultaneous submission of CCR to USG IAW Foreign Clearance Guidance, unless otherwise approved in writing or directed in advance by the CO AND

b) Key personnel hired by the Contractor to perform OCONUS work and submitted in the CCR adhere to the itinerary/plan in the approved CCR for performance start, unless otherwise approved in writing or directed in advance by the CO AND

c) There is no mission impact (outside of the established/agreed upon timeline required to process OCONUS employees for in country performance) due to position vacancies or unqualified personnel

Deliverables Management*

PWS paragraph 2.0 and subparagraphs *Deliverables also include all documents listed under the section titled “document development”

Develop and submit all required deliverables

Performance is acceptable when:

a) 100% of deliverable requirements are met and received on time* AND

b) Information is current and accurate *Non-current or inaccurate deliverables (or those with conflicting information) may be considered late

Provide a proactive system of quality control and quality assurance practices and procedures that is effective in delivering only products and services that meet or exceed all cost, schedule and performance specification of this PWS (3 and subparagraphs)

Develop, document, implement, maintain and continuously improve a comprehensive higher-level QMS that complies with the most current version of the ISO 9001 QMS standard.

Performance is acceptable when no Major Nonconformances are identified.

3.2.3 Contractor’s Quality Control Plan (QCP). The Contractor’s QCP is a set of procedures intended to ensure that a performed service adheres to the requirements of the PWS. The procedures are written for that specific contact rather than an overarching QCP that may apply to multiple contracts. Any deviations from the QCP will be treated as a non-conformance and documented in accordance with this QASP.

3.3 Assessing Performance. CORs must document Contractor performance on each contract.

CORs will assess Contractor performance based on contract requirements. The results will be the foundation of the Contractor Performance Assessment Report (CPAR), which is completed by the PM and CO.

3.3.1 Inspections. The COR may perform inspection/surveillance at any time during contract performance IAW FAR 252.246-2 through 5, as applicable. The COR will retain all audit and inspection documentation until contract closeout, unless otherwise approved by the CO.

3.3.2 Non-conformances and Deficiencies. Audit or Inspection results that fall below contractual standards shall be identified as non-conformances or deficiencies. The COR will track all non-conformances in the non-conformance log.

3.3.2.1 Types of Non-conformance.

3.3.2.1.1 Minor Non-conformance: A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. A minor non-conformance normally does not increase risk to the Government.

3.3.2.1.2 Major Non-conformance: A major non-conformance is a non-conformance that adversely impacts mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. A major non-conformance also increases risk to the Government.

An example of increasing risk would be significant number of recurring non-conformances, which indicates inadequate preventive measures or actions, thus lowering the Government’s confidence that quality services will be provided on time and at cost.

3.3.2.2 Non-conformance Notification. If a non-conformance is found during inspection of the Contractor’s performance, the COR will determine the type of notification based on the category of the non-conformance (see Table 3) and pursue non-conformance resolution per paragraph 3.4.

3.3.2.2.1 First or Second Notices (see Attachment 1). As shown in Table 3, First and Second Notices provide written notification from the Government to the Contractor of minor non-conformances. Initial minor non-conformances should be addressed with a First Notice to the

TABLE 3 – NON-CONFORMANCE NOTIFICATIONS

Non-conformance Category Notification Type Minor

Step 1: First Notice Step 2: Second Notice

Major Corrective Action Request (CAR) applicable Contractor representative. The COR may coordinate with the PM prior to delivering the notice to the Contractor for action. The First and Second notices will be issued with a suspense date for the contractor’s reply (typically 10 business days. If the Contractor fails to respond by the suspense date, the COR will follow-up with the Contractor and may issue a second notice. If the Contractor fails to resolve the issue as documented in the Notice, the COR may elevate the issue to the next level (Second Notice or CAR). Corrective/preventive actions initiated and/or completed by the Contractor will be verified by the COR and documented accordingly (typically on the CAR form).

3.3.2.2.2 Corrective Action Requests (CAR) (see Attachment 2). As shown in Table 3, a CAR provides written notification from the Government to the Contractor of significant performance discrepancies. The COR will draft the CAR and coordinate with the PM/MFT for review as necessary. Once the review is final, the CAR will be sent to the CO. The CAR will be routed NLT ten duty days after the event to the CO for review and signature, as the CO is the only person who has authority to issue a CAR to the Contractor.

3.3.2.2.2.1To satisfactorily close-out a CAR, the following criteria must be met: the Contractor must meet the suspense; the corrective action must have already begun; and the Contractor's actions must correct the non-conformance and if applicable, be within specified standards.

3.3.2.2.2.2 If the corrective action is deemed UNSATISFACTORY by the COR/MFT, an *estimate of the Government's loss due to the deficient performance (if applicable) will be forwarded to the CO for review. Once the review is complete, the CAR will be annotated with the USG’s estimated loss and be sent to the CO for action.

*The estimate may account for loss or destruction of property, supplies, or equipment, and hours lost to re-perform the task. If the task cannot be re-performed, indicate the number of hours it ordinarily would have taken to do the task, if known.

3.3.2.2.3 The COR will maintain a non-conformance log documenting all First and Second Notices and CARs. Please review the log for required fields. If a field header has a red triangle in it, click on the triangle and instructions will be provided. The COR log is maintained in the PMT file plan.

3.3.3 Services Summary Reporting. CORs will perform services summary inspections (Table

2) a minimum of as described below.

3.3.4 COR Report. A report (typically documented in CMS) will be provided based on the SS requirements. CDRLs will be reviewed IAW due dates, and the QCP will be reviewed upon delivery and then QC activities will be reviewed. The report will consist of the results of the SS review and a memo (as part of the e-mail that includes the checklist) detailing any concerns or areas where the contractor exceeded requirements. Should CMT be utilized, the report will be maintained in the CMT system, e-mailing will not be required. Minor and major non-conformances shall be submitted immediately (instead of delivering with the report). In addition, any significant concerns shall be up channeled immediately.

4.0 Invoices Receipt Acceptance and Property Transfer ((iRAPT) formerly (WAWF). The COR/QAPC/QAM (may be the same individual) will review and recommend acceptance or rejection of contractor submitted Receiving Reports to the PM within 7 days of contractor submission in iRAPT.

To access the receiving report, log into iRAPT, select the Government, Acceptor, Acceptance Folder tab; then type in the contract and delivery order (task order) number. The Shipment Number column in IRAPT is the Receiving Report number

4.1 Validating Receiving Reports (RR). The COR/QAPC/QAM (may be the same individual) will review and validate all IRAPT receiving reports (Shipment Number in IRAPT) ensuring that:

• The Contractor submitted a combination invoice/receiving report

• The report reflects the correct contract and TO number

• Beginning and ending dates being billed are stated and accurate

• The correct CLIN(s) is(are) charged for billing period

• A description of the services is provided (Firm Fixed Price, Labor Hour, Travel, Materials

• The correct amount is charged, to include applicable handling rates

• Invoiced travel was pre-approved

• Back-up documentation is attached that includes a Contractor invoice with current and cumulative hours (for FFP LOE contracts) and amounts, as applicable

• A breakout of any other charges, as agreed to by the CO or required by the TO, is attached in IRAPT.

4.2 Certifying and Accepting RRs. Certification of services is performed by the appointed COR. After validation of services is performed by the QAM per paragraph 4.1 above, the QAPC/QAM will complete a “CNGT CHECKLIST FOR ADMINISTRATIVE REVIEW AND APPROVAL OF PAYMENT REQUEST” form as verification that the invoice was accurate. In turn, the form will then be forwarded to the PM for their review and acceptance. Once again, the COR will verify the RR, and the PM accept.

4.3 Rejecting Receiving Reports. If during the COR review, a RR is found to be incomplete, incorrect, etc, the COR will annotates the errors/issues on the CNGT checklist and then email the contractor (cc the PM and Contracting Officer) of the errors/issues found. If the RR is already in iRAPT, the PM may elect to reject and annotate the rejection details in the Miscellaneous Info tab in the comments block as follows:

• List details regarding all unsatisfactory services or incorrect invoice information

AND

• Instruct the Contractor to contact DFAS to have the invoice rejected back to the Contractor; this will allow the Contractor to make the same correction on both the receiving report and invoice, since combination invoices/receiving reports are required.

The rejecter will then return to the Header tab and click the “Reject to Initiator” block. Anyone other than the QAM may reject receiving reports in IRAPT, but only when services/invoices have been reviewed and rejected by the QAM in writing per the paragraph above. After rejecting the receiving report, e-mail the PM and CO the contract number, receiving report number, and reason for rejection

As a final caveat, in the event of extended absences of the PM or COR/QAM/QAPC, the present party may complete the acceptance/rejection actions (referenced above) of the absence party to ensure invoices are processed in a timely manner incompliance/intent of the Prompt Payment Act.

5.0 *COR FOLDER. The Primary COR will establish and maintain a COR folder for each task order; an electronic version of the folder may be kept. The COR folder will contain the information outlined below in Table 4. Documentation is kept for the life of the contract and provides necessary continuity should COR duties transition during the course of the contract.

The COR will receive instructions from the CO on disposition or archival procedures upon contract completion.

*These files may be incorporated into the CO’s or PM’s file plan (or CMT) and do not require to be maintained as a separate entity.

TABLE 4 – COR FOLDER TABS & CONTENTS

Tab Title Items to Include

1 General Correspondence 2 COR Appointment Letter(s) (Typically maintained in CMS) Assignment/nomination letter(s), appointment letter(s) and Government/Contractor relationships guidance

3 COR Training (Typically maintained in

CMS)

COR certificates for DAU, QAPC and CO Led training

4 Contract/Task Order, Modifications, PWS, Pricing

Contract for current level of effort, any modifications and most current PWS/amendment on contract, and Contractor’s contract/task order pricing

5 Quality Assurance Surveillance Plan, Surveillance Checklist (min: SS)

Contract/task order QASP, approved surveillance checklist, and completed surveillance checklists

6 Contractor’s Quality Control Plan Deliverable 7 First & Second Notices, Corrective

Action Reports (CAR) Non-conformance log, First and Second Notices and CARs issued to Contractor

8 Contractor Deliverables CDRLs, deliverable specified in contract/task order, reports, etc.

Attachment 1

First or Second Notice Template

DEPARTMENT OF THE AIR FORCE

HEADQUARTERS AIR COMBAT COMMAND

ACQUISITION MANAGEMENT AND INTEGRATION CENTER

JOINT BASE LANGLEY-EUSTIS VA

(Date)

MEMORANDUM FOR (Contractor, ATTN: Contractor POC)

FROM: ACC AMIC/DRT

SUBJECT: First/Second Notice for Contract for (brief name for non-conformance) on TORP

XXXX

1. Contracting Officer Representative: (Mr/Ms First Last)

2. Office: (COR Office symbol)

3. Date of First Notice: (if 2nd notice, if 1st notice delete)

4. Reference: (PWS section and paragraph; Deliverable, Services Summary (SS), or email)

5. Reference Text: (State what action the Contractor should have performed IAW the reference above)

6. Description of Non-Conformity: (provide objective evidence of the Contractor’s performance discrepancy(ies))

7. Date response due from Contractor: (dd-mm-yyyy)

8. Contractor POC: (Mr/Ms First Last)

9. Contractor’s Input (Provide correction action):

10. COR Review (COR comments to reply):

11. Date Closed: (dd-mm-yyyy)

(signature block will be determined by ACC AMIC)

CC: Contracting Officer Representative

Attachment 2

Corrective Action Request (CAR) Template

CORRECTIVE ACTION REQUEST (CAR)

1. Request Initiated By: 2. CAR Number:

3. Date:

Click here to enter a date.

4. Contract Number(Or Location if Internal):

5. Issued To:

6. Date Action Plan is Required: Refer to CO Letter

Describe the nonconformity. Use continuation sheet if necessary. Attach or embed any relevant records, documents, or evidence.

7. What is the nonconformity (Provide a brief statement summarizing the finding):

8. Requirements (Include Contract (SS first then PWS reference) SEE TDY CLAUSE, Anti-Deficiency Clause, Base Contract, TORP para 6.0, 9.3 and PWS for IDIQ contracts., AFI, TO, Commercial Publications, and similar references.

Additionally, include all contractor Operating Instructions, Work Instructions, and similar references. Include excerpts from the references to substantiate the nonconformity):

9. Objective Evidence (Record objective evidence of the non-conformity. Include pictures, records, documents to substantiate):

10. Risk Rating: (This Risk Rating is for the initial finding. State the probability (likelihood) of reoccurrence and the resultant impact (consequence) to the mission/program. Select appropriate drop down item for the likelihood and consequence of the nonconformity.) https://afkm.wpafb.af.mil/DocView.asp?DocID=6082614 Please click “Unlock Ratings to enable drop downs. Once you have selected the “Likelihood” and “Consequence” ratings, click “Lock Ratings” to lock selections (ratings should turn a light gray color).

LIKELIHOOD

Lock Ratings

5 - Nearly Certain (71-100%)

CONSEQUENCE

4 - Significant degradation in technical performance/Program critical path affected

RISK LEVEL

High

11. Action Plan (As a minimum, this plan shall include elements a – f as listed below. Use this space for all responses to include follow up responses.

a. Action taken to fix the problem (correction)

b. Root cause analysis of the problem

c. Corrective action on the root cause of the problem

d. Action(s) taken to prevent recurrence to include the follow-up plan (how and when)

e. Action(s) required by the contractor’s Quality Plan

f. All supporting evidence to support actions taken such as updated manuals, instructions, procedures, etc. (embed in this section to maintain a single point document unless size is restrictive or security policies prevent embedding. In these cases, provide location of the documents)

This is an auto-expanding field, use as much space as necessary.

12. Evaluation of Action Plan (If multiple responses are required due to partial or non-acceptance, include date of each evaluation/verification):

CAR CLOSE-OUT (Initials and Date)

13. Functional (Coord) 14. PM (Coord) 15. COR (Approve) 16. QAM (Approve) 17. CO (Approve) //signed/xxx/ddmmyy// //signed/xxx/ddmmyy// //signed/xxx/ddmmyy// //signed/xxx/ddmmyy// //signed/xxx/ddmmyy//

QMSF 8.3-1 CAR FORM – Rev-10 17 Dec 2012

PREVIOUS EDITION MAY BE USED

https://afkm.wpafb.af.mil/DocView.asp?DocID=6082614