2330042QASP.pdf

PR: FD2060-23-30042 QASP REVISION: 0 1

Quality Assurance Surveillance Plan (QASP) for

AN/ALM 280 Enhanced Automated Special Test Equipment (EASTE) Support, AN/ALQ-161A Subsystem Software Configuration, Engineering, Qualification and

Field Test Support for Preprocessor Flight Software (PFS), Integrated Facility for Avionics Testing (IFAST) and Engineering Support in the Electronic Warfare and Avionics Integration

Support Facility (EWAISF) for Electronic Warfare Integrated Reprogramming (EWIR)

Purchase Request: FD2060-23-30042

14 Oct 2022

PR: FD2060-23-30042 QASP REVISION: 0 2

1.0 Purpose

The Quality Assurance Surveillance Plan (QASP) is a government-developed document used to determine if the contractor’s performance meets the performance standards contained in the contract. The QASP establishes procedures on how this assessment/inspection process will be conducted. It provides the details associated with a continuous oversight process, to include:

• What will be monitored

• How monitoring will take place

• Who will conduct the monitoring

• How monitoring efforts and results will be documented

1.1 The contractor is responsible for implementing and delivering performance that meets contract standards using its Quality Control Plan. The QASP provides the structure for the government’s surveillance of the contractor’s performance and their Quality Assurance/Quality Control (QA/QC) actions to assure they meet contract standards. It is the government’s responsibility to be objective, fair and consistent in evaluating contractor performance.

1.2 The QASP is not part of the contract nor is it intended to duplicate the contractor’s Quality Control Plan. This QASP is a living document. Flexibility in the QASP is required to allow for an increase or decrease in the level of surveillance necessary based on contractor performance.

Copies of the QASP and any revisions may be provided to the contractor to facilitate open communication. In addition, the QASP should recognize and accommodate unforeseen or uncontrollable circumstances which might occur that are outside the control of the contractor.

The QASP should ensure early identification and resolution of performance issues to minimize impact on mission performance.

1.3 Objective(s)

The overall mission goal is to maintain and sustain the AN/ALQ-161A system, EASTE, EWAISF, and IFAST. The contractor's primary responsibility is to support planning, development, execution, post-test analysis, and, reporting of lab testing, including software configuration management functions. This acquisition provides the services required to support the B-1B Defensive Avionics Subsystem (DAS) Sustainment Update (DSU) ALQ-161A System.

These services include: (a) engineering support services for the AN/ALM-280, Enhanced Automated Special Test Equipment (EASTE), (b) engineering support for the AN/ALQ-161A system software qualification and test for all ongoing and future AN/ALQ-161A deficiency analyses, technical inquiries, Preprocessor Flight Software (PFS) block cycle change programs, and laboratory maintenance/upgrade efforts, (c) engineering support and configuration management support for the B-1B DSU efforts along with maintaining the Electronic Warfare Avionics Integrated Support Facility (EWAISF) and Integration Facility for Avionics System Testing (IFAST) in order to accomplish Electronic Warfare Integrated Reprogramming (EWIR) hardware in the loop (HITL) test and evaluation including Ops Recce.

1.4 Result(s)

PR: FD2060-23-30042 QASP REVISION: 0 3

The QASP is used for managing contractor performance assessment by ensuring that systematic quality assurance methods validate that contractor quality control efforts are timely, effective, and are delivering the results specified in the contract or task order. The QASP directly corresponds to the performance objectives and standards specified in the PWS. It provides specific details on how the Government will survey, observe, test, sample, evaluate, and document contractor performance results to determine if the contractor has met the required performance standards for the objectives in the PWS. Successful completion of the objectives for the performance of the contract constitutes success of the program.

1.5 Authority

Authority for issuance of this QASP is provided under Part 46 of the Federal Acquisition Regulation, Inspection of Services clauses, which provides for inspection, acceptance and documentation of the service called for in the contract or order. If commercial, quality assurance will be applied in accordance with commercial items clause.

2.0 Performance Assessment/Services Summary

The matrix below details the method of surveillance and frequency the Contracting Officer’s Representative (COR) will use to validate and inspect performance objectives. Inspection of each objective will be documented in the COR Surveillance File. Performance objectives define the desired outcomes and performance thresholds define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance.

2.1 Method of Surveillance

Performance Objective

PWS

Reference

Performance Threshold Method of Surveillance

The contractor shall respond to technical inquiries from

AFLCMC/WNY

and the B-1B user community.

4.1 The contractor shall provide response within

five (5) business days to all technical inquiries.

Method: Customer Feedback

Surveillance will be conducted monthly by applicable MTF member(s) reporting Contractor response time/performance to the COR.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

PR: FD2060-23-30042 QASP REVISION: 0 4

The contractor shall submit a report to document the results of the deficiency analysis.

4.2 4.4 4.4.2 4.4.8 4.4.9 4.4.10 4.4.12 4.4.13 4.4.14 4.4.15 4.5.4 4.5.5 4.5.6 4.11

Reports shall be technically accurate. The contractor shall report the status of each analysis investigation in the monthly status report. Following receipt of all comments, reports shall require no more than one (1) revision per report after the initial submittal.

Method: Periodic Inspection

Surveillance will be conducted monthly by the COR monitoring the monthly status report deliveries through the Governemnt Interlink Sharepoint.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall technically manage contractor work efforts and B- 1B DAS test programs.

4.4.16 Formal test cycles (FQT, FET, C&I, aircraft)

shall incur zero (0) schedule slips due to poor planning or execution of test activities by the contractor test manager. Formal tests shall miss zero (0) test objectives due to poor planning and/or executing of test activities by the contractor test manager.

Method: 100% Inspection

Surveillance will be conducted by the MTF member(s) monitoring test objectives and schedule.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall provide accurate engineering support for AN/ALQ-161A modification programs.

4.2 4.4 4.4.8 4.4.9 4.4.10 4.5.4 4.5.5 4.5.6

Engineering documentation submitted by the contractor shall be technically accurate, requiring no more than one (1) revision per document after the initial submission due to technical inaccuracies.

Method: Periodic Inspection

Surveillane will be conducted monthly by the MTF member(s) monitoring engineering documentation.

Surveillance will be documented semiannually by the COR in the PAR or

PR: FD2060-23-30042 QASP REVISION: 0 5

The contractor shall provide quality technical reviews of documentation generated during the development phase.

4.4.5 4.4.6 4.5.1 4.5.2 4.5.3

The contractor shall be allowed zero (0) EPRs per contract PoP attributed to a system or software requirement’s characteristics of ambiguity, validity, accuracy, completeness, and verifiability after completion of the design phase.

Method: Periodic Inspection

Surveillane will be conducted monthly by the MTF member(s) monitoring engineering documentation.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall submit problems detected during testing and data analysis in the form of EPRs or WRPRs as decided by the TSC/TRB process.

4.4.11 4.8.2 4.8.4 4.8.5 4.20

The contractor shall provide initial investigation on 100% of EPRs discovered during IFAST testing.

Method: Customer Feedback

Surveillance will be conducted monthly by the MTF member(s) monitoring EPRs for IFAST testing.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall provide red-lines of documentation changes via the

DAL.

4.4.5 4.4.9 4.4.14 4.11

Red-lined documents shall be technically accurate, and, following receipt of all comments shall require no more than one (1) revision per document after the initial submission.

Method: Periodic Inspection

Surveillane will be conducted monthly by the MTF member(s) monitoring DAL submissions.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall verify that work products sent to the TSC are

4.4.5 4.4.6 4.4.7 4.4.8 4.5.1

The contractor shall verify, via documentation, that 100% of work products sent to the TSC are reviewed by the contractor.

Method: Periodic Inspection

Surveillane will be conducted monthly by

PR: FD2060-23-30042 QASP REVISION: 0 6

reviewed by the contractor.

4.5.2 4.6.1 the MTF member(s) monitoring TSC deliverables.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall provide initial investigations for AISF generated EPRs.

4.4.9 4.4.10 4.4.11 4.5.5 4.5.6

The contractor shall provide initial investigation on 100% of EPRs discovered during EWAISF testing.

Method: Customer Feedback

Surveillance will be conducted monthly by the MTF member(s) monitoring EPRs for EWASIF testing.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall provide timely support of the PFS sustainment cycles.

4.4.1 4.4.2 4.4.3 4.8.4 4.20

The contractor shall incur zero (0) business days schedule slip to formal test phases due to poor planning or execution of test activities by the contractor.

Method: Customer Fedback

Surveillance will be conducted monthly by applicable MFT member(s) reporting Contractor response time/performance for PFS to the COR.

Surveillance will be documented semiannually by the COR in the PAR or

PR: FD2060-23-30042 QASP REVISION: 0 7

TSC/TRB process 4.4.11 4.8.2 4.8.4 4.8.5 4.20

The contractor shall provide initial investigation on 100% of EPRs discovered during IFAST testing.

Method: Customer Feedback

Surveillance will be conducted monthly by the MTF member(s) monitoring EPRs for IFAST testing.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall maintain program schedules and information in Program Status Notebooks.

4.8.2 The contractor shall not be the cause of more

than three (3) technical or schedule defects per book per week.

Method: Random Inspection

Surveillance will be conducted by the MTF member(s) reviewing deliverables upon receipt.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall maintain EPR and WRPR databases.

4.4.1 4.8.5 4.8.6 4.8.7

The contractor shall incorporate all database updates within one (1) business day (8 hrs) of receipt of EPR/WRPR updates.

EPR/WRPR updates requiring TSC approval shall be incorporated within one (1) business day of the TSC approval.

Method: Random Inspection

Surveillance will be conducted by the MTF member(s) EPR and WRPR databases.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall accomplish efforts in accordance with project schedules.

4.2 4.4.3 4.4.4 4.4.8 4.4.9 4.4.10 4.4.11

The contractor shall be allowed less than 10% schedule variance against project schedules for development, testing, investigations, and document support. This metric will be calculated quarterly.

Method: Periodic Inspection

Surveillane will be conducted monthly by the MTF member(s)

PR: FD2060-23-30042 QASP REVISION: 0 8

4.4.16 4.4.17 4.5 4.5.4 4.5.5 4.8.2 4.8.3 4.8.4 4.8.7 4.10.3 4.15.2 4.15.6 4.21 5.5.5 5.9 monitoring project schedules.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

The contractor shall conduct acceptable Contractor Safety Program.

5.5.6 On base work: no more than two (2) Class C

mishaps per contract year. Zero (0) Class A or B mishaps.

Method: Customer Feedback

Surveillane will be conducted by the MTF members or the COR documenting the mishap.

Surveillance will be documented by the COR in the applicable semiannual PAR.

The contractor shall comply with USAF wide and local security procedures.

4.8.9 4.8.11 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.2.8 5.2.9 5.5.5

The contractor shall be allowed zero (0) reportable security violations within a contract period of performance, as determined by the B-1B Security Classification Guide (SCG) and organizational procedures.

Method: Periodic Inspection/Customer Feedback

Surveillance will be conducted by the COR if applicable.

Surveillance will be documented by the COR in the applicable semiannual PAR or SPM COR Status Report.

Mishap Notification and Reporting

5.5.2 No more than one (1) instance of late mishap

notification per contract year.

Method: 100% Inspection or Customer Feedback

Surveillance will be conducted by the MTF member(s) or COR documenting the mishap.

PR: FD2060-23-30042 QASP REVISION: 0 9

Surveillance will documented by the COR in the applicable semiannual PAR or SPM COR Status Report.

Receipt of CDRL deliverable

4.10.2 4.10.3 5.8

There shall be no more than one (1) late submission(s) of deliverables per quarter.

The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Method: Periodic Inspection

Surveillance will be conducted by the MTF member(s) or COR monitoring receipt of deliverables.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

Quality of CDRL deliverable

4.10.1 There shall be no more than a total of five (5)

rejection(s) of deliverables per quarter. The Government will reject a deliverable if any technical errors or five (5) or more minor errors are found within the deliverable.

A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc.

The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection.

Method: Periodic Review

Surveillance will be conducted by the MTF member(s) or COR reviewing deliverables upon receipt.

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

Adherence to Contractor the Quality Management System (QMS)

5.9

Prior to contract/order award, the Contractor shall submit a QMS, including a QCP, for acceptance by the Government MFT. 100% compliance with the QMS is required.

Method: 100% Inspection

Surveillance will be conducted by the COR reviewing the contractor’s QMS to ensure that it is effective in bringing the desired results (performance is equal to or greater than the SS metrics).

PR: FD2060-23-30042 QASP REVISION: 0 10

Surveillance will be documented semiannually by the COR in the PAR or SPM COR Status Report.

Sub-Contractor Participation and Utilize Ability One in performance of CDRL deliveries

4.8.14 4.8.14.1 4.14 4.14.1

The Contractor shall deliver a Sub- Contractor Participation Report annually on all task orders no later than 30 calendar days after basic contract anniversary date.

Method: Period Inspection

Surveillance will be conducted annually by the COR.

Surveillance will documented by the COR in the applicable semiannual PAR or

2.2 COR Surveillance File Documentation

The COR will establish and maintain an online file containing training and surveillance documentation in the Procurement Integrated Enterprise Environment (PIEE) via the Joint Appointment Module (JAM) and Surveillance and Performance Module (SPM). At a minimum, the following documentation will be maintained in JAM/SPM by the COR or Contracting Officer, as applicable.

a. Joint Appointment Module (JAM)

• Training and Appointment DAU CLC 222, Contracting Officers Representative (COR) Online Training DAU ACQ 0030, Overview of Acquisition Ethics, or agency equivalent DAU DOD 0020, Combatting Trafficking in Persons (CTIP) for Acquisition &

Contracting Personnel SYS 600, Wide Area Workflow (WAWF) Intro Course QAPC-Led Training Certificate Contract Specific Training DAU CLC 206, CORs in a Contingency Environment (if applicable) Confirmation of reviewing JAM/SPM Training (Memo) Refresher training (16 CLPs every three years) Confirmation of filing the annual OGE 450

• Complete COR Experience (Agency & Technical Experience)

• Designation of Contracting Officer’s Representative (Smart Form)

• Termination of Contracting Officer’s Representative (Smart Form)

b. Surveillance & Performance Monitoring Module (SPM)

• QA Surveillance Plan

PR: FD2060-23-30042 QASP REVISION: 0 11

QASP, QASP revision(s)

• SPM Smart Forms COR Status Report (Surveillance, equivalent to PAR) Contract Discrepancy Report (equivalent to CAR) Trip Report (if applicable) Contractor Progress Report Review Correspondence Report Surveillance Schedule Surveillance Checklist Memorandum for the Record

• Manually Uploaded Documents (examples):

Other Surveillance Document

- Performance Assessment Reports (PARs)

- Corrective Action Reports (CARs)

Deliverables (CDRLs, including Contractor Status Reports) Safety Plan (Contractor) Integrated Master Schedule

- Master/Delivery Schedules

Other

- Contract, including modifications (if not in EDA)

- PWS, including revisions (if not in EDA)

- DD Form 254 (if not in EDA)

- CDRLs (Form 1423 - if not in EDA)

- Customer Complaint Records

- Documentation of Contractor payment (if not processed in WAWF)

- Trip Reports

- CAV-AF Repair Item Actions Report(s)

- Surveillance Schedule/Checklist

- Annual COR File Inspection Checklist(s)

2.3 Plan for Corrective Action

2.3.1 Unsatisfactory Contractor performance will result in the COR issuing a negative PAR or SPM Smart Form “COR Status Report” to the Contractor. The Contractor shall sign and return a negative PAR by the suspense date. The Contractor will be required to respond a COR Status Report by the suspense date. The Contractor shall explain the deficiency and identify the corrective action they shall take to resolve the deficiency and prevent recurrence. The COR will upload the negative PAR to the COR Surveillance File in SPM.

2.3.2 If repetitive negative PARs or a single negative PAR identifying critical Contractor non-compliance are issued without satisfactory resolution, the COR will initiate the CAR process.

However, the MFT reserves the right to issue a CAR at any time based on the severity of the Contractor non-compliance. The COR will prepare and sign the CAR, and forward to the Contracting Officer (CO) for signature. The CO will set a suspense date and submit the CAR to

PR: FD2060-23-30042 QASP REVISION: 0 12

the Contractor for corrective action. The Contractor shall sign and return the CAR by the established suspense date with a corrective action plan to the CO for acceptance by the MFT.

The plan shall include identification of the root cause and a get-well-date. The corrective action will be tracked and documented until the deficiency is resolved to the satisfaction of the MFT.

The COR will upload the CAR to the COR Surveillance File in SPM. The PCO will upload the CAR to the contract file. If the CAR process fails to resolve the deficiency, the MFT has the prerogative to issue an interim Contractor Performance Assessment Report (CPAR), and the CO has the right to invoke the Inspection of Supply/Services clause(s) identified in the contract/order.

2.3.3 CORs will establish a tracking system for corrective actions that includes date COR submitted CAR to PM/FSM, date reviewed by PM/FSM, date reviewed by CO, date issued by CO, contractor’s identified root cause, proposed corrective action, contractor follow-up actions, and get-well date.

2.4 Acceptance of Services

2.4.1 The Contractor shall submit/process payment requests and receipt/acceptance documents via Wide Area Workflow (WAWF). Services will be accepted by the COR.

2.4.2 CDRL deliverables shall be submitted using Government Interlink ALQ-161 Sharepoint site or transported by hard drive if applicable. The CDRL will determine submittal requirements; however, separately priced data must be submitted and accepted in WAWF in order for the Contractor to receive payment, and both separately priced and non-separately priced data must be accepted in WAWF in order for the contract line item to be closed out.

3.0 Roles and Responsibilities of Multi-Functional Team (MFT)

3.1 General Responsibilities

3.1.1 The MFT is responsible for ensuring the acquisition utilizes Performance-Based Service(s) Acquisition (PBSA) methods including establishment of performance thresholds, procedures to evaluate Contractor performance and positive/negative incentives to encourage the highest quality of services.

3.1.2 The MFT is responsible for conducting surveillance of Contractor performance to ensure Government requirements, including quality of services, cost and schedule, are met. The MFT will provide the results of their surveillance to the Contracting Officer’s Representative (COR) for input into the PARs, or COR Status Reports, and to the MFT member updating the Contractor Performance Assessment Reporting System (CPARS).

3.1.3 For contracts requiring higher-level quality requirements, the MFT is responsible for developing metrics in tracking the effectiveness of the contractors Quality Control Plan (QCP)/Quality Management System (QMS) tie to the SS, QASP, and CPARS. Ensure contracts requiring higher-level contract quality requirements include a SS performance objective that

PR: FD2060-23-30042 QASP REVISION: 0 13

encompasses MFT goals related to quality and directly relates to the CPARS category of “Quality”.

3.1.4 The MFT ensures contract oversight focuses on the adequacy and adherence of the contractor to their proposed QMS. The MFT shall focus on whether the COR or contractor is first in detecting defects and trends, who (COR or contractor) accomplishes more inspections, and, whether the contractor is proactively pursuing key QMS functions to ensure quality related problems or defects do not recur.

3.2 Contracting Officer’s Representative (COR)

3.2.1 The COR is responsible for providing continuous technical oversight of the contractor’s performance. The COR will use the QASP as the primary tool for conducting surveillance of the contractor’s performance. The COR shall keep a surveillance file that accurately documents the contractor’s actual performance. The purpose is to ensure that the contractor meets the performance standards contained in the contract.

3.2.2 Works with the MFT in conducting and documenting surveillance on Contractor performance. Reports unethical conduct and instances of fraud, waste and/or abuse to the Contracting Officer. Inspects and accepts/rejects deliverables during contract/order performance and at close-out to ensure contract/order terms and conditions are met. Develop an inspection schedule that shall comprise of at least ten percent of non-services summary items, as a recommended best practice. Monitors control and disposition of Government property.

Monitors Contractor payment and verifies it is commensurate with Contractor performance.

Documents Contractor performance via PARs, or SPM COR Status Reports, and CARs. Issues PARs, at a minimum, semiannually, and negative PAR(s) or CAR(s), as required.

3.2.2.1 If issuing a PAR, the COR will forward to the CO and the Contractor for signature.

After all signatures have been obtained, the COR uploads the signed PAR in SPM under “COR Documents” (select “Add Documents”, and then select the Document Type, “Other Surveillance Document”).

3.2.2.2 If issuing a COR Status Report, the CO will approve the report in SPM after submission.

The COR will print the report in pdf format and email it to the contractor. If the contractor responds to a negative report, the COR should upload the email correspondence with the contractor into SPM.

3.2.3 Participates in the annual inspection of the COR Surveillance File initiated by the PCO.

Documents the results of their review and any corrective action planned/executed in the Comments section of the Annual COR File Inspection Checklist. Signs the checklist.

3.2.4 Registers in PIEE as a COR. Self-nominates in JAM as the designated COR for the contract. Files the annual Office of Government Ethics (OGE) Form 450, Confidential Financial Disclosure Report. Establishes and maintains a COR File – training documentation is maintained in JAM, and surveillance documentation is maintained in SPM.

PR: FD2060-23-30042 QASP REVISION: 0 14

3.2.5 Establish a System for Award Management (SAM) Individual Account after designation as a COR to search and view Service Contract Reporting (SCR) information. After the contractor has submitted the SCR, the COR or PCO will review contractor reported information for reasonableness and consistency. If SCR revisions are required, the PCO will notify the contractor no later than November 15. By November 30, the contractor shall revise the report, or document the rationale.

3.2.6 Ensure contractor’s Quality Control Plan/Quality Management System (QMS) complies with contract requirements. CORs need to place special emphasis in ensuring the contractor’s QMS is being followed as written, plus is effective in bringing about the desired results – performance equal to or greater than the SS metrics, plus an inspection and corrective action program that identifies and fixes issues without having to be identified by the Government.

3.3 Contracting Officer’s Representative (COR) Supervisor

3.3.1 Upon the Contracting Officer’s request for COR support, selects a qualified nominee.

Confirms the COR nominee has no personal conflicts of interest, and verifies that the COR has the appropriate clearance for the contract/order. Ensures the COR files the annual OGE Form

450. Ensures the COR takes initial, annual and any additional training required by the contracting activity. Ensures the COR completes 16 hours of refresher training every three years after completion of QAPC-Led Training.

3.3.2 Registers for the SPM Manager Role via PIEE to obtain access to the COR’s Surveillance File in SPM. Ensures the COR registers in PIEE, and self-nominates as the designated COR for the contract in JAM. Upon email notification of the COR self-nomination, approves the nomination via email link. Conducts regular reviews of the COR Surveillance File to ensure surveillance documentation is timely and complete and to ensure the COR’s technical experience is complete and up-to-date. Participates in the annual inspection of the COR Surveillance File initiated by the PCO. Considers performance of COR duties in their annual appraisal.

3.4 Contracting Officer (CO)

3.4.1 Only individual authorized to enter into contracts and determines if a COR is required. If the requiring activity has not initiated a COR nomination in JAM, the CO submits a Request for Contracting Officer’s Representative Support memorandum to the requiring activity. Provides Contract-Specific Training to the COR.

3.4.2 Upon notification of COR Supervisor approval of the COR’s nomination, reviews the nomination in JAM, and completes the Smart Form Designation Letter. The contract must be awarded and in EDA to complete the designation process in JAM. The CO shall provide a copy of the designation memo to the Contractor. Upon notification of transfer/retirement of the COR, the CO shall complete the Termination Letter in JAM. The CO shall provide a copy of the termination memo to the Contractor, and designate the replacement COR.

3.4.3 Reviews the COR reports on contractor performance in SPM, and approves/rejects PARs, CARs, or COR Status Reports.

PR: FD2060-23-30042 QASP REVISION: 0 15

3.4.4 Establishes a SAM individual account. Reviews SCR data for reasonableness and consistency. Notifies the Contractor if any revision is necessary by 15 November of the following fiscal year.

3.4.5 Initiates the annual inspection of the COR Surveillance File. Documents the results of their review on the Annual COR Surveillance File Inspection Checklist. Uploads the checklist in SPM after the COR and COR Supervisor have provided their comments and signed it. Uploads the checklist under COR Documents (select “Add Documents”, and select category “Miscellaneous”, Subcategory “Other”, and label as “Annual COR File Inspection Checklist”).

3.5 Quality Assurance Program Coordinator (QAPC)

3.5.1 Supports the MFT in the development of the contract/order quality assurance requirements specifically ensuring the requirements are clearly stated and enforceable. Prior to contract/order award, provides training to CORs and COR management. Ensures training requirements are accomplished in accordance with DoDI 5000.72, DoD Standards for COR Certification.

Monitor records of all COR training records and conducts reviews of SPM records for assigned organizations.

3.5.2 Provides functional, not technical, support for JAM/SPM users including assistance with registration and role activation.

3.6 Contractor

3.6.1 Participates as a member of the MFT upon approval of the Justification & Approval (J&A) or Sole Source Justification (SSJ) if the acquisition is sole source, and upon contract/order award, if it is competitive.

3.6.2 The Contractor shall ensure the quality of services through a quality and/or inspection system. In order to meet the government’s quality requirements, a contractor’s QCP/QMS should be robust enough and resourced adequately to execute four key quality functions: 1) Detection of quality program problems and defects; 2) Identification of root causes for quality related problems/defects; 3) Correction of root causes related to detected problems/defects; and,

4) Follow-up to ensure quality related problems/defects do not recur; a mature QMS requires the contractor be the proactive party on quality issues. The goal is to obtain performance reflective of continuous improvement with no reliance on COR’s surveillance to detect problems/defects, determine root causes, or ensure quality related problems/defects do not recur.

3.6.3 Maintains an inspection process acceptable to the Government in accordance with the Inspection of Supply/Services clause(s) identified in the contract/order.

3.6.4 Signs and returns a positive PAR within five business days. Signs and returns a negative PAR with corrective action identified by the suspense date. Signs and returns a CAR with a corrective action plan by the suspense date.

PR: FD2060-23-30042 QASP REVISION: 0 16

3.6.5 Responsible for ensuring personnel, information, system, property, facility and, if applicable, international security requirements are met in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification, and applicable government regulations specified in the contract/order.

3.6.6 Reports all SCR data for each fiscal year, including a count of contractor/subcontractor personnel performing services; all contractor labor hours, including subcontractor labor hours;

the total amount invoiced; and required Tier 1 subcontractor information in SAM no later than 31 October of the following fiscal year in SAM. If notified by the Government, that change(s) are required, revises the report or provides rationale no later than 30 November.

3.7 Functional Services Manager (FSM)

3.7.1 The FSM provides primary program oversight, nominates the COR, ensures the COR is trained before performing any COR duties and supports the COR’s performance assessment activities.

3.7.2 The Functional Services Manager has determined these services are not mission-essential and will not continue in the event of a crisis. Reference PWS and QASP signature page.

4.0 Management Strategy

4.1 The MFT will meet and record minutes quarterly to review contractor’s performance. The COR will issue PARs, or COR Status Reports, documenting both satisfactory and unsatisfactory Contractor performance, at a minimum, semi-annually. The Contractor shall sign and return a positive PAR within five business days. The Contractor shall sign and return a negative PAR by the suspense date. The COR will upload the PAR in SPM.

4.2 Incentives

4.2.1 If Contractor performance meets or exceeds contractual requirements, positive incentives may include, but are not limited to, decreased surveillance (by revision to the QASP/Method of Surveillance), favorable CPARs and exercising options.

4.2.2 If Contractor performance does not meet contractual requirements, negative incentives may include, but are not limited to, increased surveillance, unfavorable CPARs, not exercising options and Government recourse authorized by the Inspection of Supply/Services clause(s) identified in the contract/order.

5.0 COR Surveillance File Inspection: The PCO will initiate the annual inspection of the COR Surveillance File. The PCO will document the results of their review on the Annual COR Surveillance File Inspection Checklist. The COR and COR Supervisor will document the results of their reviews and any corrective action planned/executed in the Comments section. After the COR and COR Supervisor sign the checklist, the PCO will upload the checklist in SPM.

PR: FD2060-23-30042 QASP REVISION: 0 17

6.0 Contractor Performance Assessment Reporting System (CPARS): The total estimated value of the contract exceeds $1,000,000.00; therefore, CPARS reporting is required.

6.1 The MFT will evaluate Contractor performance. The Assessing Official Representative (AOR) will review the PARs and other information contained in the COR Surveillance File to prepare and substantiate the CPAR. CPARS will be updated, at a minimum annually, documenting Contractor performance for the contract/order. The MFT should refer to the latest CPARS Guidance for CPAR processes and timelines, https://www.cpars.gov/sysreq.htm. Users can refer to Table 4.9 for the CPARs Timeline, and “Table 1 for the Business Sector, Dollar Threshold and Reviewing Official” information.

6.2 In evaluating the quality of contractor’s performance, the following performance ratings are used in documenting past performance. The areas rated may include: Quality, Schedule, Cost Control (if applicable), Management, Small Business Subcontracting (if applicable), and Regulatory Compliance.

Performance Rating

Criteria

Exceptional Performance meets contractual requirements and exceeds many to the government’s benefits. The contractual performance of the element or sub-element being assessed was accomplished with no problems and contractor actions were highly effective.

Very Good Performance meets contractual requirements and exceeds some to the government benefits. The contractual performance was accomplished with few minor problems for which corrective actions taken by the contractor were effective.

Satisfactory Performance meets contractual requirements. The contractual performance contains some minor problems for which corrective actions taken by the contractor were satisfactory.

Marginal Performance does not meet some contractual requirements. The contractual performance reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear marginally effective or were not fully implemented.

Unsatisfactory Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains serious problem(s) for which the contractor’s corrective actions appear or were ineffective.

7.0 Safety Requirements

7.1 Mishap Notification/Investigation: The Contractor shall report mishaps in accordance with the safety requirements identified in the PWS. The Contractor shall ensure the Safety Office, COR, and CO are notified of mishaps.

7.2 MFT Surveillance: MFT member(s) will report any potential safety hazards or actual mishaps to the COR. The COR will monitor Contractor reporting and review any mishap notifications. The COR will address safety and/or health issues in the PAR or CAR, as applicable.

https://www.cpars.gov/sysreq.htm

PR: FD2060-23-30042 QASP REVISION: 0 18

8.0 Trafficking in Persons: The MFT will inform the PCO if the contractor/subcontractor fails to comply with the requirements of FAR 52.222.50, Combating Trafficking in Persons.

The PCO will report any non-compliance in accordance with DFARS PGI 222.1704, Combating Trafficking in Persons. The COR should refer to the U.S. Department of State website, at http://www.state.gov/j/tip, for the latest guidance of monitoring trafficking in persons.

http://www.state.gov/j/tip

PR: FD2060-23-30042 QASP REVISION: 0 19

9.0 Signatures

By signing below, you are appointed to the MFT for this acquisition and accept the above responsibilities.

QAPC Date

Contracting Officer Representative (COR) Date

COR Supervisor Date

Contracting Officer Date

Contractor Date

By signing below, you are identifying these services as not mission-essential.

Functional Services Manager (formerly FC/FD) Date