RFP Att 2 QASP_FACT-E.pdf

CUI

Quality Assurance Surveillance Plan Version 5.0

For

Foreign Affairs Counter Threat – Equivalency

Course (FACT-E)

PANORL-24-P-0000 001139

DATE

Caryn H. McGraw MSG Shea Myatt Contracting Officer Contracting Officer’s Representative

ACC-ORLANDO SATMO

Controlled by: Army Controlled by: ACC-ORL CUI Category: PROCUREMENT Distribution/Limited Dissemination Control:

FEDCON

POC: MSG Shea Myatt, (407) 592-9786

“Source Selection Information- See FAR 2.101 and 3.104”

2 | Page

Table of Contents

1. Overview

2. Description of Services

3. Roles and Responsibilities

4. Contract Quality Requirements

5. Government Surveillance

6. Non-Conforming Performance

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) .. 16

12. Contractor Performance Assessment Reporting System (CPARS)

13. Combating Trafficking in Persons (CTIP)

14. COR/Quality Assurance Surveillance Files

15. QASP Changes

3 | Page

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 provided. The objective of this non-personal services contract is to provide the Security Assistance Training Management Organization (SATMO) contracted training support for the Foreign Affairs Counter Threat Equivalency (FACT-E) course.

This QASP identifies the methods and procedures the Government will use to ensure it receives the services to the desired standard, as identified in the Performance Work Statement (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. 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 provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform FACT-E training to prepare military, Department of Defense (DOD) civilians and contracted personnel for Security Assistance Team (SAT) missions world-wide. The focus of the training is on Anti- Terrorism/Force Protection and Survival, Evasion, Resistance, and Escape tactics, techniques, and procedures (TTP).

4 | Page

2.2. Type of Contract. This will be a firm fixed price contract.

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 for 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.

5 | Page

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 regarding 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.2.1 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- 2g.

3.1.3. 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.4. 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.2. Contractor.

3.2.1. Contract Manager. The Contractor responsible for managing the contract and making sure they follow all terms and conditions.

3.2.2. Project Manager. The Contractor responsible for running the program. May supervise the program team and manage conflicts within different departments. Plans https://piee.eb.mil/

6 | Page 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. The Contractor shall provide a PM who shall be responsible for the performance of the work under this contract.

3.2.3. Site Lead. The Contractor is responsible for executing day to day execution of the contracted training with the Military TAFT members and the country. Responsible for the daily execution of the contracted training to include, but not limited to confirming daily, weekly, and monthly class schedules with the Military TAFT members and the country, managing instructors’ work schedule, and maintaining training information.

The Contractor shall designate one (1) member of the instructor team to serve as the in- country Site Lead.

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

Table 1: Key Positions for Contract Administration

Government Personnel:

Title Name Phone E-mail Contracting Officer Caryn McGraw (520) 714-5532 caryn.h.mcgraw.civ@army.mil Contract Specialist NAME NUMBER EMAIL

COR/ACOR MSG Myatt, Shea (407) 592-9786 Shea.p.myatt.mil@army.mil

Contractor Personnel:

Title Name Phone e-mail Contract Manager TBD TBD TBD Project Manager TBD TBD TBD Quality Manager TBD TBD TBD

4. Contract Quality Requirements.

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

The Contractor’s quality control program is how he assures himself that all work

7 | Page 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 system 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, reference Attachment 1 –

Performance Requirements Summary.

- All performance activities will be surveilled throughout 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

8 | Page 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:

• 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.

• 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.

• 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.

• Third Party Audit SATMO will use military members stationed in Halmstad and working on the Patriot case as a method to answer specific questions about performance when provided by the COR. SATMO will use information from the third-party audit as the primary means for monthly evaluations.

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

The Customer Complaint Record, Attachment 4, will be placed at convenient locations for the end user of these services, and made available to

9 | Page 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:

a. The COR will perform evaluations/validation of Contractor supplied performance data.

1. The COR will review the Contractor supplied daily, weekly, or monthly reports, that are to include but not limited to CDRLs A001 – A004. These reports will be inspected by the COR to verify, review, and concur with the validity of the information. These reports will be included with the COR monthly report in the Surveillance and Performance Monitoring (SPM) module.

2. The COR will review the Contractors’ supplied reports and validate the data accuracy supplied within utilizing (work orders/ automated data/approved schedule timeline, invoices and WAWF supporting documentation.

10 | Page

b. The COR will perform an analysis of Customer feedback, if any, and the

Contractor’s actions to identify performance trends and to ensure valid customer concerns are resolved timely. The COR will review any correspondence received by the country, if any negative trends or mission critical instances are identified the COR will follow up with the Contractor.

5.2. Surveillance Schedule. The frequency of surveillance will be determined by the

PRS Attachment 1.

5.3. Surveillance Checklists. (Required) A Surveillance Checklist (Attachment 4) will be created each month. Locally generated equivalent is acceptable. The Checklist is “FOR OFFICIAL USE ONLY” 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.

5.4. Surveillance Documentation. Each month’s 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) file for this contract. The COR Status Report (Smart Form) must be utilized, supporting documentation can be uploaded as an attachment.

Non-Conforming Performance. A Corrective Action Report (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 with 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), Note: Surveillance Schedules and Checklists are considered COR documentation and must be uploaded in the SPM module. Smart forms are available for use at the individual record level under “Add Smart Form”

11 | Page

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 with one of the four levels as defined below.

5.5. Level I (Minor). 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 with 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 with one of the four levels as defined below.

5.6. Level II (Major). 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.

5.7. Level III (Critical). 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

12 | Page business management system disapprovals, etc. Contractor shall be required to provide a CAP that is acceptable by the government.

5.8. 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.

5.9. 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.

a. Identify a contract nonconformance;

b. Create a CAR;

c. Review the CAR;

d. Coordinate and approve the CAR;

e. Issue the CAR to the contractor;

f. Receive and review the contractor’s CAP;

g. Accept/reject the contractor’s CAP;

h. Oversee contractor corrective action using a risk-based approach;

i. Receive notification from the contractor that corrective action is accomplished;

j. Verify corrective action was accomplished satisfactorily;

k. Close the CAR

5.10. 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.

https://www.pdrep.csd.disa.mil/default.htm

13 | Page

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.

5.11. 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.

14 | Page

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.

5.12. 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.

5.13. 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

15 | Page 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.

5.14. 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.

6. Deduct Plan. This acquisition does not include a Deduct Plan.

7. 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 Nonconformance Report. Trends noted using Contractor data will not result in an NCR unless the Contractor has not addressed the negative trend.

QASP changes based on Data Analysis will be coordinated with the Contracting Officer for approval.

8. 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.

9. COR Status Report. COR Status Reports (CSR) will be submitted monthly 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

16 | Page 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 surveillance performed, Customer Feedback if any, NCRs 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 NCRs, if any, will be included as attachments to COR Status Reports. See para 5.4.

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

(SAM).

Reporting labor hours is not required under a Foreign Military Sales (FMS) type contract or task order.

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

12. 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.

13. 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.

14. 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.

DOCUMENT REVISION HISTORY

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

17 | Page

Officer must approve all changes.

Version # Effective Date Originator Summary of Changes Basic DATE A. Vassilopanagos Initial

Attachments:

1. Performance Requirements Summary (PRS)

2. Complete Contract Deliverable Requirements List (CDRL)

3. Customer Complaint Record

4. Surveillance Checklist

18 | Page

Attachment 1

Contract/Task Order Performance Requirements Summary (PRS)/ Surveillance Schedule

Performance Requirement Summary (PRS)/Surveillance Schedule

Required Services (Tasks)

Performance Objectives

Acceptable Quality Levels (AQL)

Method of Performance Assessment

Remedy

PRS # 1

The Contractor shall transmit a Status Report to the COR in Microsoft-Word or PDF format detailing how each mission, training objective, end-state, and deliverable was accomplished.

(CDRL A001)

MONTHLY

The Contractor shall provide all required training at the level required by this PWS.

These reports shall include a detailed status of all training (with dates, places, etc.), ll support provided for technical or logistic activities or other as required by this PWS, a detailed depiction of all issues encountered and/or any reasons for the cancellation of training.

The Contractor shall submit Status Reports inclusive of all reportable events to the COR on time.

No more than 1% of the status reports may be later than the specified period AND/OR no more than 1% of any events may go unreported.

100% Inspection of Status Reports.

Action shall be re-performed until it is determined acceptable, at no additional cost.

The results of this performance objective will be used for reporting contractor performance in CPARS.

The rating will be based upon the results of monthly metrics.

19 | Page

20 | Page

Performance Requirement Summary (PRS)/Surveillance Schedule

Required Services (Tasks)

Performance Objectives

Acceptable Quality Levels (AQL)

Method of Performance Assessment

Remedy

PRS # 2

The Contractor shall transmit Monthly Billing Invoices through the Wide Area Workflow (WAWF) system monthly.

A copy of the monthly billing invoice and all supporting documentation shall be sent to the Contract Specialist and the COR for Inspection and/or Feedback.

(CDRL A002)

MONTHLY

The Contractor shall provide a complete invoice.

All COST related expenses shall be broken down and include supporting documentation sufficient to determine the prices to be fair and reasonable.

A copy of the invoice along with the supporting documentation shall be provided to the COR and the Contract Specialist.

The Contractor shall submit invoices to the COR on time.

No more than two invoices submitted in a twelve-month period shall include billing errors, missing required supporting documentation or be later than the specified period.

100% Inspection of monthly contractor submitted invoices.

Action shall be re-performed until it is determined acceptable, at no additional cost.

The results of this performance objective will be used for reporting contractor performance in CPARS.

The rating will be based upon the results of monthly metrics.

21 | Page

Attachment 2, Complete CDRL Listing:

1.1. Contract Requirement Deliverable List (CDRL) A001

Status Report. Unless otherwise stated, the Status Report will be due by the 5th business day of every month or as otherwise noted in the individual paragraph and submitted via email to the COR/Contract Specialist. This CDRL contains the following:

Training Status Report. The contract shall report all training conducted to the COR in Microsoft-Word or PDF format) detailing how each mission, training objective, end-state, and deliverable was accomplished. The report will also include a student roster and student progress. The Contractor shall describe all training completed, all issues encountered, and any reasons for the cancellation of training.

Contractor Assessment Report. The Contractor shall submit a report on the previous months self-assessment in accordance with the Contractor’s quality assurance plan.

The number of self-assessments conducted within the month shall be dependent upon the complexity of the mission and the success/failure rate of previous assessments. The results of the assessment and any corrective actions shall be included in the report. Self-assessments shall begin in the first month following the Government’s acceptance of the Contractor’s quality control plan.

Data Rights. The Contractor shall develop, maintain, and provide to the COR a continuous report that identifies and tracks all documents under this mission, as they are created or become available, considered to be Government owned data rights. The Contractor shall also identify and track any document or other under this mission not considered protected under these rights, along with the justification for omitting them. After review and/or discussions, a PCO determination will be made.

Roster. The Contractor shall develop, maintain, and provide to the COR a Contractor personnel roster which shall include names and positions of all Contractor personnel, security clearance(s) as well as indicating which employees were issued CAC or other forms of government identification cards. The roster will include a listing of all members’ phone numbers that have been verified and maintained by the Site Lead. The Contractor will provide a list of who is assigned a PLB to include PLB by name, model, hex ID (or operating ID), battery expiration date, and serial number. The Contractor shall provide notification within five (5) business days when changes are made thereafter.

Isolated Personnel Report (ISOPREP). The Contractor shall track all ISOPREP completions, to include all completed ISOPREP Forms (DD Form 1833 or equivalent).

22 | Page

All USG Contractor personnel will complete an ISOPREP form prior to departure to duty location. Personnel attending FACT will complete the ISOPREP with the SATMO S2 Section. To use PRO-FILE, the user will need a CAC enabled computer connected to a .mil or .gov domain. To use PRO-FILE, the user will need a CAC enabled computer connected to a .mil or .gov domain. ** All ISOPREP forms must be turned into SATMO S2 at least ninety-six (96) hours prior to deployment.

Personnel Status Report (PERSTAT). The Contractor will maintain, and be prepared to report, full accountability of all personnel at any time. The Contractor shall report a summary of contract responsibilities, illnesses, and projected time-off. The Contractor shall report all scheduled time-off a minimum of thirty (30) business day in advance with a plan to ensure all mission requirements are covered. The Contractor shall always maintain and report a full accountability of deployed personnel. The Contractor shall include a listing of Contractor employees who quit, were fired or other during the previous month and the date their CACs were turned in. ** The Contractor shall ensure that all requests for information pertaining to the Contractor’s personnel are provided to SATMO and the COR in the event of an incident that requires Personnel Recovery plans to be implemented.

After-Action Report. The Contractor shall maintain detailed notes during the performance of this training mission. At the conclusion of this mission, the Contractor shall provide an After-Action Report (AAR) / Lessons Learned report to the COR/Contract Specialist and SATMO. ** The Contractor shall submit a final Status Report within twenty (20) business days of contract completion that includes the After-Action Report.

Contingency Reports: The Contractor shall submit contingency reports as required by SATMO Policy Memo 19 Reportable Event - Incident Requirements.

1.2 CDRL A002 – Billing Invoices.

Monthly Billing Invoices. The Contractor shall transmit monthly billing invoices through the Wide Area Workflow (WAWF) system for Inspection and/or Feedback. The Contractor shall provide copies of monthly invoices with itemized charges to both the COR and Contract Specialist.

Supporting Documentation. Invoices that include a request for reimbursement of costs incurred (other than Firm Fixed Priced Contract Line-Item Numbers (CLINs), shall include copies of supporting documentation and shall be sent separately to the COR.

Acceptable supporting documentation includes but is not limited to an itemized breakdown of costs, Point of Sale receipts, and other necessary supporting details for

23 | Page any expenses other than standard, recurring basic services. Supporting documentation on expenses greater than $500 shall also include the preapproval that is required for all items that are being proposed against a cost CLIN.

Other Direct Travel Costs (ODC) (COST). Contract ODCs that are associated with this case in accordance with the PWS will be submitted for COR review and KO approval prior to purchase. The Contractor shall submit written requests for ODCs, for both travel and other, to the COR/Contract Specialist at least fifteen (15) business days prior to need date. Contractor shall ensure all ODCs are pre-approved by the COR prior to expenditure of funds.

24 | Page

Attachment 3

Customer Complaint Record

ACC_ORL_Customer Compliant Record.pd

25 | Page

Attachment 4 Surveillance Checklist(s)

COR SURVEILLANCE CHECKLIST Template COR Inspection Checklist & Data Report (Fixed Firm Price

Contract) Period Of

Performance:

Contractor: From:

Contract Number: To:

Service Provided: Meeting

Contract Requirements? COR Name:

Date: YES No

Comments:

Comments summary, to include, positive trends, negative trends, concerns, customer comments, and any additional COR comments:

To populate the checklist, find in the PWS: "The Contractor Shall...”, Then, make that requirement a checklist item by converting the requirement to a question: “Did the Contractor …"

Each "Yes" can be graded as a 1, and each NO graded as a 0. Once the checklist is complete, the COR may generate a quantifiable performance rating using these numbers as metrics.

26 | Page

Surveillance Checklist.xlsx

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