DRAFT QASP Template Agile Professional Services 20260729.docx

Quality Assurance Surveillance Plan

For

Agile Professional Services

Add/ Contract #

24 July 2026

ACC-ORLANDO

Controlled by: ACC-ORL POC: PAQA Branch QAS

TABLE OF CONTENTS

Subject Page Number

1. Overview

2. Description of Services

3. Roles and Responsibilities

4. Contract Quality Requirements

5. Government Surveillance

6. Corrective Action Request (CAR)

7. Deduct Plan

8. Data Analysis

9. Acceptance of Services

10. COR Status Report

11. Service Contract Reporting (SCR) in the System for Award Management (SAM)

12. Contractor Performance Assessment Reporting System (CPARS)

13. Combating Trafficking In Persons

14. COR/Quality Assurance Surveillance Files

15. Government Furnished Property Surveillance Requirements

16. QASP Changes

1. Overview.

1.0 Purpose. This Quality Assurance Surveillance Plan (QASP) is a Government developed document used to ensure that the Government receives quality services and pays only for conforming services actually provided. The objective of this Labor Hour Commercial Services Contract is to acquire Agile Professional Services (APS) as an enterprise-wide transformation of the Government's service contracting capability. This contract will provide highly functional, outcome-focused, capability-centric acquisition, engineering, and headquarters support services. By shifting from legacy "designated-personnel" staffing models to an Agile, task-based enterprise capacity architecture at U.S. Army Capability Program Executive Simulation, Training, Test and Threat (CPE ST3) as defined in this Performance Work Statement (PWS), section {Insert appropriate PWS reference, e.g., section three (3)}. The Contractor shall perform to the standards specified in APS PWS. This Quality Assurance Surveillance Plan (QASP) identifies the methods and procedures the Government will use to ensure it receives the services to the desired standard, as identified in the PWS.

1.1. Intent. The intent of this QASP is to:

1) Ensure Contractor performance meets or exceeds contract terms, conditions, and specifications 2) Hold the Contractor accountable for quality control

3) Encourage the Contractor to take appropriate steps to control and improve quality

4) Ensure all sections of FAR 46 are applied as required and applicable

Accordingly, the Government will perform surveillance on the contract in accordance with this QASP but reserves the right to monitor the contract in any manner necessary, at any time necessary, and at all places necessary to ensure that the services rendered conform to contract requirements. The Government also reserves the right to perform quality assurance at the Subcontractor level, and at the contractor's place of business. Sub-contract service providers shall be accountable to the Contractor who, in turn is responsible to the Government. Resolution of non-conforming services discovered at the Subcontractor level will be addressed with the prime Contractor. The Government will not exercise any supervisory controls over the contract service providers performing the services herein.

2. Description of Services.

2.1. Scope of Work. The contractor shall cover the comprehensive lifecycle support of CPE ST3's diverse portfolio of over 370 products deployed at more than 400 locations worldwide. These services directly support the Department of War (DoW) and Allied Partners by ensuring statutory and regulatory testing, training, and threat requirements are met for DoW acquisition programs (e.g., Abrams, Bradley, Stryker, Apache, Chinook, Black Hawk) to enhance combat readiness, interoperability, and multi-domain operational effectiveness. Foreign Military Sales (FMS) support requirements are within the scope of this services contract. Accordingly, the government reserves the right to amend the Performance Work Statement, add line items, and make other such adjustments to orders for FMS requirements as necessary. The contractor shall not perform inherently governmental functions, nor provide labor categories or staffing constructs that imply Government authority. Direct procurement of tactical hardware or end-items is out of scope unless explicitly authorized as incidental to the execution of a defined service task.

2.2. Type of Contract. This will be a Labor-Hour Commercial Services “C” Type Contract in accordance with Federal Acquisition Regulations (FAR) Part 12.

3. Roles and Responsibilities. The following provides a synopsis for the roles and their respective authority during the performance of the contract:

3.1. Government.

3.1.1. Contracting Officer (KO). The KO is the only person authorized to direct changes in any of the requirements under this contract. In the event the Contractor effects any such change at the direction of any person other than the KO, the change will be considered to have been made without authority, and solely at the risk of the Contractor. No changes in, or deviation from the terms and conditions shall be affected, without a written modification to the contract, executed by the KO authorizing such changes.

3.1.2 Contracting Officer’s Representative (COR). The COR will monitor all technical and performance aspects of the contract and assist the (KO) in contract administration. The COR is authorized to perform the following functions:

· Assure that the Contractor performs the technical requirements of the contract

· Perform inspections necessary in connection with contract performance

· Maintain written and oral communications with the Contractor concerning technical and performance aspects of the contract

· Issue written interpretations of technical requirements, including Government drawings, designs, and specifications

· Monitor Contractor's performance and documents and notifies both the Contracting Officer and Contractor of all deficiencies

· Coordinate availability of Government furnished property

· Provide site entry of Contractor

ACC doesn’t use other acronyms to refer to and describe a COR. Terms such as the “COTR, “Onsite COR”, “TM”, etc. will not be used. Some personnel may be assigned as Alternate CORs, but other than a statement to that effect and what actions the KO expects that ACOR to take in the absence of the primary COR, there is no difference between a COR an Alternate COR, or other government surveillance personnel assigned to conduct contract oversight. Throughout the remainder of this QASP, The term “COR’ will be used to refer to all government surveillance personnel assigned to monitor the contractor’s performance on this contract.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost, price, or delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

The Contracting Officer shall use the DoD Joint Appointment Module (JAM) to electronically track COR nominations, appointments, terminations, and training certifications for each COR appointed to conduct oversight on this contract. The COR will upload their surveillance documents, such as COR Status Reports (CSR) COR trip reports, correspondence with the contractor, and other miscellaneous documents into the Surveillance and Performance Monitoring (SPM) module within the online contract file. JAM and SPM are available within the Procurement Integrated Enterprise Environment (PIEE) suite of tools at: https://piee.eb.mil/.

3.1.3. Alternate Contracting Officer’s Representative (ACOR). The Alternate COR is an employee of the U.S. Government provided by the Requiring Activities (RA) and appointed by the Contracting Officer to provide additional surveillance personnel in monitoring and documenting the contractor’s performance. These alternate surveillance support personnel may serve as on-site representatives of the COR in performance of actual contract surveillance if they meet all COR training and experience requirements and are appointed by the contracting officer as Alternate CORs (ACOR) in the Joint Appointment Module (JAM). This term will apply to other government surveillance personnel as defined in Army Regulation 70-13, paragraph 2-2 g.

3.1.4. Contract Administrator. The official Government representative delegated authority by the Contracting Officer to administer a contract. This individual is normally a member of the appropriate Contracting/Procurement career field and advises on all technical contractual matters.

3.1.5. Property Administrator. An authorized representative of the Contracting Officer appointed in accordance with agency procedures responsible for administering the contract requirements and obligations relating to Government property in possession of a Contractor.

3.6. Contractor.

3.6.1. Contract Manager. [If the Contractor has a Contract Manager, copy and paste the information from the PWS in Table 1, Key Positions for Contract Administration. If the Contractor does not have a Contract Manager, delete this paragraph.]

3.6.2. Program Manager. The Contractor responsible for running the program. May supervise the program team and manages conflicts within different departments. Plans and sets program goals and milestones and develops risk management strategies. Defines resources and schedules for the implementation of the program. Clearly defines requirements and sets targets accordingly. Recognizes areas for internal improvement and develops plans for implementing the improvements.

[If the Contractor has a Project Manager, copy, and paste the information from the PWS and insert in Table 1; Key Positions for Contract Administration. . If the Contractor does not have a Program Manager, delete this paragraph.]

3.6.3. Quality Manager. The Contractor responsible for promoting quality achievement and performance improvement throughout the organization. Develops, implements, communicates, and maintains a quality plan to bring the Contractor’s Quality Systems and Policies into compliance with quality system requirements. Directs the activities of contractor quality personnel to measure key quality characteristics of services delivered and processes from inception to completion. Establishes the standards of service for customers expected by the Requiring Activity. [If the Contractor has a Quality Manager, copy, and paste the information from the PWS and insert in Table 1; Key Positions for Contract Administration. . If the Contractor does not have a Quality Manager, delete this paragraph.]

For quick access, the contact information for the performance of this QASP is provided:

Government Personnel:

Table 1; Key Positions for Contract Administration

Contracting Officer

COR/ACOR

Contract Administrator

Property Administrator

Contractor Personnel:

Contract Manager

Project Manager

Quality Manager

4. Contract Quality Requirements.

4.1. Contractor’s Quality Control Plan/Program (QCP). The Government will evaluate the adequacy of the Contractor’s Quality Control Plan (QCP) performance under this contract in accordance with this QASP.

The Contractor’s quality control program is the means by which he assures himself that all work complies with the requirement of the contract PWS. It is essential that Government Surveillance Personnel understand that Quality Control (QC) is the responsibility of the contractor, and not the government.

As such, the government will focus their efforts on validating if the contractor is maintaining an adequate quality control inspection systems that ensures the contractor maintains evidence that services provided conform to contract quality requirements. The Contractor shall provide inspection data to the Government on request for validation.

The Contractor’s QCP shall include a process that can identify, prevent, and ensure non-recurrence of defective services.

4.2. Government Quality Assurance. This QASP describes what the Government will do to ensure that the Contractor has performed in accordance with the performance standards within the PWS.

This QASP describes:

· How the performance standards will be applied:

· The Performance Standard for each requirement in the PWS will be applied as prescribed in the PWS. Ensure that each Performance requirement within the PWS includes a Measurable performance standard in terms of quality, timeliness, or quantity.

· Ensure the method of assessing contractor performance against performance standards is included in this QASP

· Ensure each Performance Requirement includes an acceptable quality limit (AQL). AQL is the worst tolerable performance that is still considered acceptable.

Example: if “the contractor shall provide personnel support within 2 hours”, the AQL may be: + or - (+/-) 15 minutes.

· Which performance elements will be surveilled (Surveillance Checklist, attachment 4)

· All performance activities will be surveilled through-out the Period of Performance, using a risk-based approach. The selected items will be populated on the Monthly Checklist and placed on the Surveillance Schedule for each period surveilled.

· When the surveillance will be scheduled (Surveillance Schedule, attachment 3)

· Selected items for each month will be placed on the Surveillance Checklist and scheduled surveillance on the Monthly Schedule. Surveillance may be scheduled on a daily, weekly, or monthly frequency. However, each contractor requirement must be audited for compliance prior to invoice payment being made.

· The Acceptable Quality Limit (AQL)

· The AQL will be determined by the Requiring Activity, i.e., the COR.

· The nature of Government contract quality assurance actions that include the number of observations made and the number and type of defects (defect rate)

· Personnel conducting contractor performance surveillance will use attachment 4, Surveillance Checklist, or equivalent to answer the Performance question asked, and provide comments in the area provided on the checklist. These comments and metrics from the Checklist will be included on each CSR submitted during the Period of Performance.

5. Government Surveillance.

5.1. Methods of Surveillance. The following Methods of Surveillance may be utilized in monitoring the Contractors’ performance:

NOTE: The performance items selected for surveillance in this QASP as a minimum should contain those listed in the Performance Requirements Summary (PRS). The PRS is a stand-alone document that illustrates to the contractor the few, most salient items the government wishes the contractor to be aware of. The PRS is contained in the contract Performance Work Statement (PWS). See Attachment 1 for PRS items.

A. 100% Inspection will be reserved for the highest risk areas where consequence of failure may affect life or limb, or there is likelihood of mission failure

B. Random Sampling Will be used when a service is performed on a frequent basis and a statistically valid sample can be selected for audit. This is most appropriate method for frequently recurring tasks

C. Periodic Inspection Will be used when planned sampling of a service is at a specific predetermined date and time. This is most appropriate for tasks that occur infrequently, yet on a scheduled basis

D. Customer Feedback/Complaint. Not a valid method of surveillance, but a good indicator of areas where surveillance should be conducted or intensified.

The Customer Complaint Record, Attachment 2, will be placed at convenient locations for the end user of these services, and made available to document/record all complaints. The COR will collect the Customer Complaints each surveillance cycle and investigate for validity ASAP.

The following procedures will be followed when a complaint is received.

1. The COR/ACOR will investigate to determine the validity of the complaint

2. If the complaint is determined to be invalid, the COR will inform the person who submitted the complaint of the reason(s) as soon as practical

3. For validated complaints that are true contractual non-conformances, the procedures in paragraph 6 below will be applied

4. A Customer Complaint Log will be used to document each validated customer complaint and attached to the COR Monthly Surveillance Report in the SPM module

5.1.1 Surveillance Procedure: THIS SECTION WILL BE SPECIFIC TO YOUR CONTRACT, HOW YOU WILL EXECUTE YOUR SURVEILLANCE, THIS MAY ALSO SERVE AS GUIDANCE ALONG WITH A CONTINUTIY FILE FOR ANY REPLACEMENT COR(s). REPLACE OR MODIFY AS APPLICABLE, THE BELOW ARE SAMPLES THAT MIGHT BE USED (MODIFIED AS APPLICABLE FOR YOUR SITUATION).

Examples:

a. SAMPLE 1: The COR will evaluate the Contractor’s performance monthly against Performance Standards established in the contract. Evaluations will be to the extent practical to assure the contractor provides quality services IAW the requirements of the contract.

1. The COR will utilize the attached checklist(s) to track and document surveillance:

2. The COR will utilize the random sample site to identify the locations/units/areas to be sampled on a monthly basis, these locations will be documented and maintained on an excel spreadsheet….

b. SAMPLE 2 (Report driven deliverables): The COR will perform evaluations/validation of contractor supplied performance data.

1. The COR will review the Contractor supplied weekly reports, that are to include but not limited to a status summary and key milestones and progress for the current period and planned for the next period. These reports will be signed by the COR, verifying review and concurrence with the validity of the information. These reports will be included with the COR monthly report in the Surveillance and Performance Monitoring (SPM) module. (You may even develop a checklist that includes a simple list of items to be included that provides a means of checking the items and signing).

2. The COR will review the contractors’ supplied reports and validate ##% of the data accuracy supplied within utilizing (work orders/ automated data/approved schedule timeline… etc. (what will you look at to verify the report data they give you is accurate for your particular contract.)

i. I.E., all CAC card requests were completed within the required 8 minutes (this will be verified against the automated tracking system (time in/time out) to verify all customers/CAC cards were issued within 8 minutes)

ii. All work orders were processed within 3 days. The COR would verify this via a random sampling of work orders, WO request date/ WO completion date.

iii. All project deliverable milestone dates met. The COR will verify against the schedule and the deliverables received date.

c. SAMPLE 3: The COR will perform an analysis of Customer feedback and the contractor’s actions to identify performance trends and to ensure valid customer concerns are resolved timely.

1. The COR will review the contractor developed customer feedback website once a month, if any negative trends are identified the COR will follow up with the contractor.

d. SAMPLE 4: Using the contractor’s quality control program, the COR will schedule inspections before, during, or after the contractor’s Quality Manager (QM) scheduled inspections. If the COR discovers a deficiency(s), the COR will immediately notify the contractor’s QM for re-performance of the service to ensure compliance. If the standards are not met or if the contractor’s QM refuses to correct an identified deficiency, the COR will notify the contracting officer for appropriate action in accordance with the appropriate inspection of services clause.

1. NOTE: Once the contractors QCP is received the QASP should be updated to include how the COR will verify compliance to the contractor quality management systems per their QCP (I.E., make a checklist of things that will be reviewed or verify/validate using one of their checklist(s);

2. The COR will take a contractor identified discrepancy and evaluate the contractors follow-up/root cause analysis, corrective and preventive actions.

e. USE OF ACORS – THEIR ROLE IN SURVEILLANCE ACTIVITIES

ACOR DOCUMENTATION REQUIREMENTS

· Reports: Functional Area Reports supporting the Quality Assurance Surveillance Plan consist of immediate impact and monthly status reporting as outlined below.

· Impact Reporting: Government ACORs observing any situation or occurrence which poses a significant program impact will be reported to the COR using the most expeditious manner available. Unacceptable performance or quality of service for requirements specified in the PRS should be documented using the Surveillance Activity Checklist and Corrective Action Request (CAR) immediately provided to the COR for validation and disposition.

· Monthly Status Report: A report will be provided by each ACOR NLT 1 week following each month of the calendar year to the COR. The period of the report is from the first to the last day of that month and should address the contractor’s performance.

5.2. Surveillance Schedule. (Required) A Surveillance Schedule (Attachment 3) will be created each month. Locally generated equivalent is acceptable. The schedule is Controlled Unclassified Information “CUI” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Schedule will be completed at the beginning of each month during the Period of Performance (PoP) to schedule the upcoming month surveillance activity. Completed Surveillance Schedules will be filed in the online Surveillance and Performance Monitoring (SPM) module located within (https://piee.eb.mil) file for this contract, either as an attachment to COR Status Report (CSR) or uploaded separately in the Miscellaneous Documents Section.

5.3. Surveillance Checklists. (Required) A Surveillance Checklist (Attachment 4) will be created each month. Locally generated equivalent is acceptable. The Checklist is Controlled Unclassified Information “CUI” and is not releasable to anyone other than authorized Government personnel. Each Month’s Surveillance Checklist will be completed with the Surveillance Schedule. Completed Surveillance Checklist will be filed in the online Surveillance and Performance Monitoring (SPM) module located within (https://piee.eb.mil) file for this contract, either as an attachment to COR Status Report (CSR) or uploaded separately in the Miscellaneous Documents Section.

Note: Surveillance Schedules and Checklists are considered COR documentation and must be uploaded in the SPM module. SmartForm are available for use at the individual record level under “Add Smart Form”

5.4. Surveillance Documentation. Each months’ Completed Surveillance Documentation, to include the COR Status Report must be filed in the online Surveillance and Performance Monitoring (SPM) module located within (https://piee.eb.mil) for this contract. If the PWS/SOW/CDRL require "progress reports" from the contractor. The COR file will contain copies of all required progress reports.

The COR Status Report (Smart Form) must be utilized, supporting documentation can be uploaded as an attachment.

6. Corrective Action Request. A CAR is not a contract remedy itself. It is used as a letter to the contractor to document a nonconformance, notify the contractor of Government rejection of supplies or services (including construction) not conforming to contract requirements, and to require contractor corrective action. The purpose is to provide the contractor an opportunity to correct or replace nonconforming supplies and services when this can be accomplished within the required delivery schedule IAW FAR 46.407 and contract terms and conditions. Nonconformances identified in CARs must be traced to contractual requirements. CARs may be precursors to contract remedies but are not a required precursor to contract remedies. CARs should be included as part of performance information in Contractor Performance Assessment Reporting System (CPARS), Program Management Reviews, Performance Feedback Sessions, Award Fee Boards, and Incentive Fees. There are four CAR levels. The level of the CAR documents and communicates the seriousness of the nonconformance. To determine the appropriate CAR level, analyze the impact and/or effect of the nonconformance and associate that impact to one of the four levels as defined below.

6.1. Level I. CAR describes a deficiency on a product or service and is not a systemic breakdown of a process or system. It includes those nonconformances that are minor in nature and can be promptly corrected by the contractor, present no need for root cause analysis, no determination if other contract requirements are affected, present no need for further preventive action, and do not materially reduce the usability of the supplies, services, construction, or deliverables. While the Government must document the nonconformance and the contractor must correct the nonconformance, further actions and Government follow-up are not required, and no written response from the contractor is needed.

6.2. Level II. CAR describes deficiencies in a contractor’s processes or systems but are not a significant deficiency. Some examples of systems affected may be quality inspection / management systems, and CBS identified in DFARS 242.70, or are: Multiple deficiencies on products or services indicating a systemic issue throughout the process, or An escalation of repetitive Level I CARs for the same or similar nonconformance demonstrating the contractor is failing to institute effective corrective action and/or failing to implement effective quality and/or internal control(s). Level II CARs shall require the contractor to correct the nonconformance, perform root cause, and develop and provide a corrective action plan (CAP) acceptable by the government.

6.3. Level III. CAR describes deficiencies in a contractor’s system that is affecting a contract or program ability to meet cost, schedule or performance requirements, or are: A significant deficiency pursuant to DFARS 252.242-7005, “Contractor Business Systems” (CBS) or A failure to respond to Level II CARs, or to remedy a recurring nonconformance If not resolved satisfactorily, a Level III CAR may result in the initiation of available contractual remedies, such as reductions of payments, cost disallowances, revocation of government assumption of risk of loss, or business management system disapprovals, etc. Contractor shall be required to provide a CAP that is acceptable by the government.

6.4. Level IV: CAR documents a critical nonconformance of such serious nature that is issued to the contractor’s business segment or corporate management for their attention to both the nonconforming condition and the company’s corrective action, or when a Level III CAR has been ineffective. A Level IV CAR will result in a mandatory review of available contractual remedies, such as cost disallowance, reduction or suspension of payments, revocation of government assumption of risk of loss, CBS disapproval, or suspension of all product and service acceptance activities. Contractual remedies will be implemented IAW applicable FAR/DFARS clauses and/or ACC Acquisition Instructions if applicable. Action to suspend product or service acceptance will be accomplished via a Level IV CAR. Contractor shall be required to provide a CAP that is acceptable to the government.

6.5. CAR Process Flow: The following outlines the normal process flow for the corrective action process. Follow the steps provided within the PDREP CAR Module User Guide. Subparagraphs (f)-(j) below do not apply to Level I CARs). Level I CARs are considered closed immediately upon issuance.

k. Close the CAR

6.6. CAR System of Record (SOR). The PDREP CAR Module is the SOR for CAR’s processed and issued on ACC administered contracts. The CAR Module is one of the applications housed in the Product Data Reporting and Evaluation Program (PDREP) Automated Information System (AIS) located on-line at: https://www.pdrep.csd.disa.mil/default.htm. For access to this system, go to the PDREP website and click on the “REQUEST ACCESS” button and follow the directions for “US Government Access”. The website also includes user guides and manuals under the “REFERENCES” button. Review the “DoD Corrective Action Request” Manual for guidance on access and how to use this PDREP-AIS. Accessing the CAR Module will be enabled through PIEE in early calendar year 2024. To access through PIEE, add the appropriate role following the PIEE process. After the PIEE single sign on is enabled, the SOR may be accessed either through PIEE or PDREP. User Roles, refer to DoD CAR Manual for a description of the functions available to each role. NOTE: ensure COR’s register as a Functional Specialist under the contracting office DoDAAC they will support (ACC-ORL=W900KK) Proprietary Information. Do not include any proprietary information as part of the CAR in the SOR. It should normally be included only by reference (cite specific document and identifying paragraph number). Consult with your supporting legal office when determining if information is suspected to be proprietary.

6.7. Issuing a CAR to the Contractor. Address CARs to the appropriate level of contractor management based on the seriousness of the nonconformance. This requires subjective judgement by the reviewer(s) and issuing official. Consideration should also be given to established lines of communication with the contractor and/or contractor requested addressees. The following are guidelines for addressing CARs:

a. Level I CARs: Lower-level management responsible to correct the nonconformance (e.g. shop foreman /supervisor/ quality manager).

b. Level II CARs: Functional level manager responsible for corrective action (e.g. the quality manager or site manager).

c. Level III CARs: Top-level management on-site or locally.

d. Level IV CARs: Corporate-level management.

e. Subcontractors. If a subcontractor’s performance is nonconforming, address CARs to the prime contractor who is responsible for subcontractor performance and has privity of contract.

f. Verbal. It is appropriate to verbally notify the contractor when the Government identifies a nonconformance or potential nonconformance. Refrain from telling the contractor that ‘a CAR shall be forthcoming’ or the anticipated level of a CAR. Official notification of the nonconformance shall be through the PDREP CAR Module and issuance of the CAR.

g. Do not issue a CAR if the contractor self-identifies contractual nonconformances and takes timely and effective corrective action. If the corrective actions prove ineffective, then issuing a CAR is appropriate. Contractor identification and self-initiated corrective actions are not only desired behaviors but are a requirement of quality and quality systems required by clauses. Joint inspections (i.e. an inspection with both a Gov’t inspector and Contractor inspector) should be considered a Government inspection. Therefore, any nonconformance identified in a joint inspection would be considered a Government identified, not contractor self-identified nonconformance.

6.8. Timelines. Transmitting CARs to the Contractor. CARs are time sensitive and delayed issuance may have impacts on the requiring activity/supported unit’s mission; delay contractor corrective action; reduce the relevancy of lower-level CARs; or reduce the capability for the contractor to perform effective root cause analysis.

a. Level I CARs: The standard is to issue the CAR no later than (NLT) three business days after identification of the nonconformance.

b. Level II CARs: The standard is to issue the CAR NLT five business days after identification of the nonconformance.

c. Level III / IV CARs: The standard is to issue the CAR NLT ten business days after identification of the nonconformance.

6.9. Corrective Action Plan Due Date. When a Level II CAR and above is issued, a contractor CAP is requested with a designated number of days to respond. The CAR Module will default to 45 days but allows a contracting office to insert any number less than to respond. The recommended due dates are:

a. Level II CARs. Level II CARs in ACC should require no more than 10 business days to respond with a CAP.

b. Level III / IV CARs. Level III / IV CARs should require no more than 15 business days to respond, except for CARs related to CBS significant deficiencies. CBS related Level III / IV CARs will have up to 45 calendar days as allowed by DFARS 252.242-7005.

c. Extensions. Contractors may request an extension of the designated due date. This is acceptable for the government to allow when reasonably justified. All results of that correspondence will be entered into the PDREP CAR Module.

6.10. CAP Reviews. For Government review of contractor submitted CAPs, accept, or reject the CAP within 5 business days for Level II, and 10 business days for Level III / IV CARs. Use the PDREP CAR Module to input the decision and provide the contractor a formal response for acceptance or rejection. Government CAP Verification & Validation of Corrective Action/CAR closure. Timelines for verification and validation of corrective actions can vary depending on the severity of the CAR, and completion of milestones identified in the CAP. Once the Government has verified the contractor has implemented the CAP and validated the issues have been corrected and are acceptable to prevent further occurrence, close the CAR in the Module. Notify the contractor the CAR is closed via the CAR Module.

7. Deduct Plan. This acquisition {does/does not} include a Deduct Plan. {If acquisition does implement a Deduct Plan, explain in detail how deductions will be calculated and applied.}

8. Data Analysis. Data Analysis will be performed to identify trends in cost, schedule and/or performance risks. The results of Data Analysis will be documented in COR Status Report and may be used to adjust surveillance schedules and/or checklist items to increase or decrease surveillance, based on performance trends. Negative trends noted using Government data/observations could result in issuing the Contractor a Corrective Action Request (CAR) using the Product Data Reporting & Evaluation Program (PDREP) application accessible within PIEE. Trends noted using Contractor data will not result in a CAR unless the Contractor has not addressed the negative trend. QASP changes based on Data Analysis will be coordinated with the Contracting Officer for approval.

9. Acceptance of Services. When all services have been deemed acceptable and there is documented, objective, quality evidence to support acceptable performance, the COR will accept the services provided and authorize payment to the Contractor. Acceptance and payment will be made by approving the Contractor’s Receiving Reports in Wide Area Workflow at https://piee.eb.mil/ as a WAWF Inspector, and/or Acceptor.

10. COR Status Report. COR Status Reports (CSR) will be submitted on a monthly basis to the Contracting Officer via the Surveillance and Performance Monitoring (SPM) module. CSRs must be uploaded into the Surveillance and Performance Monitoring (SPM) module using the “Smart Form”. CSRs will be due NLT the 10th day of the month following the month of surveillance. CSRs will provide a synopsis of the Contractors performance for the inclusive dates of the report. The synopsis must contain a summary of surveillances performed, Customer Feedback if any, Corrective Action Request (CAR) if any, an analysis of the Contractors performance, recommended adjustments to surveillance schedules, and any other pertinent contract information IAW FAR 46.104, and the COR Appointment Letter. Completed Surveillance Checklists and CARs, if any, will be included as attachments to COR Status Reports. See para 5.4.

11. Service Contract Reporting (SCR) in the System for Award Management (SAM). https://www.sam.gov. Reporting Labor Hours. Service contractor reporting of information is required in the System for Award Management (SAM) when a contract or order- 1) Has a total estimated value, including options, that exceeds $3 million; and 2) Is for services in the following service acquisition portfolio groups (see PGI 204.1703 for a list of applicable product and service codes):

(1) Logistics management services.

(2) Equipment-related services.

(3) Knowledge-based services.

(4) Electronics and communications

The system allows industry to report all manpower data into a single Federal-wide portal. For Contractors who meet the SCR reporting thresholds (in excess of $3 million), your entity must be registered in SAM.

SCR requires contractors to enter the following information for their contract or order:

(1) The total dollar amount invoiced for services performed during the preceding Government fiscal year under the contract or order.

(2) The number of Contractor direct labor hours, to include first-tier subcontractor direct labor hours, as applicable, expended on the services performed under the contract or order during the previous Government fiscal year.

Contractor reporting is required annually, by October 31, on the services performed under the contract or order, including any first-tier subcontracts, during the preceding Government fiscal year (October 1-September 30). For indefinite delivery contracts, basic ordering agreements, and blanket purchase agreements, 1) Reporting is required for each order issued under the contract or agreement that meets the requirements of PGI 204.1703 and, 2) Service contract reporting is not required for the basic contract or agreement. Contracting officers shall ensure that the requirement to report contractor manpower is included in all contracts, task/delivery orders and modifications.

12. Contractor Performance Assessment Reporting System (CPARS). Documented surveillance data (COR Status Reports, Completed Surveillance Checklists, Customer Feedback and Corrective Action Report (CAR) if any will be used to support CPARS ratings. CPARS will be completed in accordance with AFARS, Subpart 5142.15 – Contractor Performance Information.

13. Combating Trafficking In Persons (CTIP). In accordance with PGI 222.17 and FAR 52.222-50, the KO will be notified immediately of any information from any source that alleges a Contractor employee, subcontractor and/or subcontractor employee has engaged in conduct that violates the United States Government “zero” tolerance policy regarding trafficking in persons.

14. COR/Quality Assurance Surveillance Files. The official COR/Quality Assurance Surveillance Files will be maintained in the on-line Joint Appointment Module (JAM) and Surveillance and Performance Monitoring (SPM) module IAW DoDI 5000.72, and DFARS PGI 201.602-2.

15. Government Furnished Property (GFP): This acquisition {does/does not} include GFP. {If acquisition does include GFP, reference Table 3 for surveillance requirements and insert the following} CORs will report surveillance outcomes IAW the Frequency column on Table 3 using the COR Status Report (CSR) via the Surveillance and Performance Monitoring (SPM) module. CSRs must be uploaded into the Surveillance and Performance Monitoring (SPM) module using the “Smart Form”. CSRs will be due NLT the 10th day of the month following the month of surveillance.

16. QASP Changes. This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications by the KO, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

Table 2; DOCUMENT REVISION HISTORY This table is specific for the template, remove the details and replace with your specific revision history information for your contract This QASP is a living document and, as such, may be changed as needed based on Data Analysis (trends), contract modifications, etc. The COR will send any recommended changes to the Contracting Officer for approval and the Contracting Officer must approve all changes.

1.0

COR NAME

Tables:

1. Key Positions for Contract Administration

2. Document Revision History

3. Government Furnished Property Surveillance Requirements

Attachments:

1. Performance Requirements Summary (PRS)

2. Customer Complaint Record

3. Surveillance Schedule

4. Surveillance Checklist

Table 3

Government Furnished Property (GFP) Surveillance Requirements

{Optional: if the contract has GFP}

Attachment 1

Contract/Task Order Performance Requirements Summary

(PRS)

{Optional: Insert/Attach the PRS from the Contract or Task Order here for convenient reference}

Required Services

Incentive (Positive and/or Negative)

EXAMPLE

Attachment 2 Customer Complaint Record

Attachment 3 Surveillance Schedule

The COR will develop a Surveillance Schedule for conducting surveillance. The COR may use the SPM Smart Form or any KO approved schedule.

Attachment 4 Surveillance Checklist(s)

The COR will develop a Surveillance Checklist for conducting surveillance. The COR may use the SPM Smart Form or any KO approved checklist.

image1.emf

PRS Example.docx QASP PRS Example

Product/Service

Requirement – SOW Reference

Performance Standard

Acceptable Quality Level (AQL)

Method of Surveillance

Remediation/Disposition

1. Contractor Quality Control Plan (QCP) MISTE BASE SOW 3.5.15

Full (100%) implementation and management of approved QCP accepted at time of contract award.

Compliance with approved QCP >98% of the time.

Periodic Inspection (minimum 4 times annually).

[I] When consistently met or exceeded annually, annual CPARS subfactor rating of Very Good or Exceptional.

[D] Standard not met 2 or more times annually, contractor considered contractually non-compliant. CAP required and annual CPARS subfactor rating no higher than Marginal. Other contractual remedies considered by Contracting Officer.

2. Data and Product Deliverables SOW 3.3 and

FAR clauses 52.246-2 Inspection of Supplies—Fixed-Price or 52.246-3 Inspection of Supplies – Cost Reimbursement

100% of deliverables are submitted timely and accepted by the Government upon initial submission.

>95% are accepted upon initial submission and are considered timely.

100% acceptable upon first resubmission.

100% review and inspection of all data and products.

[I] Contract compliance considered favorably for customer satisfaction and consideration of Option Exercise.

[D] Standard not met 3 or more times annually, Fixed Fee under CPFF reduced by 2% and Profit reduced by 3% under FFP. Potentially negative CPARS rating under Technical/Quality of Product or Service factor.

3.Contractor maintains adherence to IMP/IMS MISTE BASE SOW 3.4.2

Manage and track schedule status and accomplish all IMP/IMS milestones on schedule

100% schedule adherence demonstrated on the DO.

IMP/IMS tracking through monthly reports and status reviews.

[I] Contractor compliant with DO requirement and demonstrated good schedule control viewed favorably toward Government consideration of Option Exercise.

[D] Loss of schedule control and/or high variation is risk indicator requiring a CAP if schedule risk is imminent. Consistently poor performance results in annotated CPARS narrative for Schedule/Timeliness and may result in rating of no higher than marginal if schedule product delivery date not met.

4. (High dollar value Cost Reimbursement Orders only) Earned Value Cost and Schedule Performance tracked against EV reporting MISTE BASE SOW 3.4.3

Strict adherence to negotiated contract cost and performance schedules.

> 95% cost control demonstrated on the DO.

100% schedule adherence demonstrated on the DO.

Monthly Trend Analysis of EV data and other cost and schedule reporting requirements when EV is applied.

[I] Consistently positive SPI (> 1) and CPI (> 1) indicators viewed favorably toward Government consideration of Option Exercise. When consistently met or exceeded, annual CPARS Cost Control and/or Schedule/ Timeliness factor rating of Very Good or Exceptional for CPFF DO’s.

[D] Consistent or significant negative SPI (< 1) and CPI (<1) indicators viewed unfavorably toward Government consideration of Option exercise. CAP required and annual CPARS Cost Control and/or Schedule/ Timeliness factor rating no higher than Marginal.

5. Customer Satisfaction

No customer complaints with high levels of satisfaction reported. Contractor has established positive working relationship with Government customer that is maintained.

A Corrective Action Plan (CAP) has been approved to the Government’s satisfaction within 15 calendar days after notification.

Results of ongoing dialog and satisfaction survey results.

[I] Consistently high levels of satisfaction viewed favorably toward Government consideration of Option exercise. When consistently high levels are maintained annually, CPARS Management or Business Relations factor rating of Very Good or Exceptional.

[D] Negative satisfaction levels viewed unfavorably toward Government consideration of Option exercise. CAP required. Annual CPARS Management or Business Relations factor rating could be rated no higher than Marginal if CAP unsuccessful.

6. Program Management Reports and Reviews MISTE BASE SOW 3.4 and 3.4.1

100% accuracy presented in contract performance and risk management status.

>98% accuracy in reporting that demonstrates program outcomes are being properly managed and controlled.

Effectiveness of Program Management Function is validated through survey methods, performance monitoring and communication and feedback.

[I] Standard consistently met is viewed favorably toward Government consideration of Option Exercise. When consistently high levels are maintained annually, annual CPARS Management or Business Relations factor rating of Very Good or Exceptional.

[D] Negative satisfaction levels viewed unfavorably toward Government consideration of Option exercise. CAP required. Annual CPARS Management or Business Relations factor rating could be rated no higher than Marginal if CAP unsuccessful.

7. Subcontractor Management MISTE BASE SOW 3.4.8

100% compliant with Small Business Participation percentages evaluated for contract award. Subcontractor performance effectively monitored and controlled

>95% compliance on each delivery order

Monthly reporting and monitoring

[I] Contractor considered compliant for SBA reporting purposes. Favorable CPARS ratings under Small Business Subcontracting factor under annual ratings when standard consistently met.

[D] Contractor considered non-compliant and consideration of Liquidated Damages equal to the percentage non-compliance in the form of Fee/Profit reduction may be imposed in addition to negative CPARS if standard not consistently met.

image2.emf

ACC_ORL_Customer Compliant Record.pdf

Army Contracting Command Orlando (ACC-ORL)

CUSTOMER COMPLAINT RECORD

DATE OF COMPLAINT TIME OF COMPLAINT

SOURCE OF COMPLAINT

ORGANIZATION (Include name of person and contact information of person reporting the complaint for the organization

INDIVIDUAL (Include name and contact information)

NATURE OF COMPLAINT

CONTRACT NUMBER & REQUIREMENT REFERENCE

VALIDATION (document findings of validation of complaint), Complaint IS Valid (notify contractor)

Complaint IS NOT Valid

DATE / TIME CONTRACTOR INFORMED OF COMPLAINT CONTRACTOR NAME RECEIVING COMPLAINT

ACTION TAKEN BY CONTRACTOR

RECEIVED AND VALIDATED BY

Copy provided for filing (COR) DATE:

Customer Follow-up DATE:

TIME OF COMPLAINT:

NATURE OF COMPLAINT:

CONTRACT NUMBER REQUIREMENT REFERENCE:

VALIDATION document findings of validation of complaint Complaint IS Valid notify contractor Complaint IS NOT Valid:

Complaint IS Valid notify contractor: Off

Complaint IS NOT Valid: Off

DATE TIME CONTRACTOR INFORMED OF COMPLAINT:

CONTRACTOR NAME RECEIVING COMPLAINT:

ACTION TAKEN BY CONTRACTOR:

RECEIVED AND VALIDATED BY:

Copy provided for filing COR DATE Customer Followup DATE:

undefined: Off undefined_2: Off

Date1_af_date:

Organization:

Individual:

Date4_af_date:

Date5_af_date:

image3.emf

Surveilance Schedule Template.xlsx Sheet1

Surveillance Schedule

“FOR OFFICIAL USE ONLY”

Contract # Contractor:

Functional Area: Surveillance Period: See Below

COR: Date Submitted: Enter Date Created

Pargarph

Date

Note: Place an "X" in the paragraph column forecasting what PWS/SOW paragraphs are going to be inspected. This can be filled out once and uploaded in SPM. Monthly the COR would be required to upload the report and Surveillance Checklist.

image4.emf

COR Surveillance Checklist Template.xlsx Approve

5.00 010000

Sheet1

COR Surveillance Checklist Meeting Contract Requirements Method of Surveillance

Issue Date: Revision Date: Revision Number:

Contractor:

Contract Number:

Service Provided:

COR Name:

Date: PASS FAIL

Random Inspection

COMMENTS:

100% Inspection

COMMENTS:

Random Inspection

COMMENTS:

100% Inspection

COMMENTS:

Random Inspection

COMMENTS:

100%…