47QFSA24R0006_RFP_PWS_UCF_Atch2_QASP_2024-03-19.docx

Page of

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

Solicitation PIID: 47QFSA24R0006 Award PIID: TBD for Rapid Technology Augmentation Support (RTAS) in support of the Air Force Research Laboratory (AFRL) Spectrum Warfare Division, AFRL/RYW Rapid Technology Integration Office

Customer Support Center: Apex 2, Sector1 Contractor Name: TBD Anticipated Contract Period of Performance (PoP):

Effective Date of QASP: TBD

Table of Contents

1.0 - General Instructions This Quality Assurance Surveillance Plan (QASP) establishes the process for surveillance of contract performance in support of Air Force Research Laboratory (AFRL), Wright Patterson, AFB, Dayton, OH requirement for services, as detailed in the Performance Work Statement (PWS) for Rapid Technology Augmentation Support (RTAS).

This QASP has been completed in partial fulfillment of requirements established under Federal Acquisition Regulation (FAR) Part 46. It details the surveillance roles and responsibilities of the contract administration team and describes the specific contract elements subject to surveillance. Further, this QASP establishes the methods of surveillance to be employed, as well as the frequency and timing of that surveillance. The documentation produced through implementation of this QASP will serve to inform the Quarterly Contracting Officer’s Representative (COR) Report in accordance with the Federal Acquisition Service (FAS) Policy and Procedure (PAP) Memo 2020-03, and as implemented via the associated ASSIST Quarterly COR Report module, as well as the applicable Contractor Performance Assessment Report (CPAR). This QASP is filed under Tab 47, Surveillance, of the Electronic Contract File (ECF), and the surveillance documents produced in accordance with this QASP are filed as described in the applicable sections below. In short, this QASP establishes what must be surveilled, how it must be surveilled, and when surveillance must occur. Note: The format of the Quarterly COR Report is provided for via a template that is separate from this document.

This QASP is effective as of the date on the cover and supersedes all previous versions. In the instance of a conflict between this QASP and the associated contract, the contract shall prevail.

2.0 - Purpose The purpose of the QASP is to describe the systematic methods used to monitor performance and to identify the required documentation and resources to be employed. The QASP provides a means for evaluating whether the contractor is meeting the performance standards or quality levels identified in the PWS, and for ensuring that the Government pays only for the level of services received.

This QASP defines the roles and responsibilities of all members of the Integrated Project Team (IPT), identifies the performance objectives, defines the methodologies used to monitor and evaluate the contractor’s performance, describes Quality Assurance (QA) documentation requirements, describes the analysis of QA monitoring results, and provides a Performance Requirements Summary (PRS).

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

The QASP is not part of the contract, and it is not intended to duplicate the contractor’s QCP. 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.

2.1 – Performance Management Approach The PWS structures the acquisition around “what” service or quality level is required, as opposed to “how” the contractor should perform the work (i.e., results, not compliance). This QASP will define the performance management approach taken by the General Services Administration (GSA) to monitor and manage the contractor’s performance to ensure the expected outcomes or performance objectives communicated in the PWS are achieved. Performance management rests on developing a capability to review and analyze information generated through performance assessment. The ability to make decisions based on the analysis of performance data is the cornerstone of performance management; this analysis yields information that indicates whether expected outcomes for the project are being achieved by the contractor.

Performance management represents a significant shift from the more traditional QA concepts in several ways. Performance management focuses on assessing whether outcomes are being achieved and to what extent versus scrutiny of compliance with the processes used to achieve the outcome. A performance-based approach facilitates the contractor providing an innovative solution within the stated constraints that gives the Government the opportunity to receive outstanding results. A “results” focus provides the contractor flexibility to continuously improve and innovate over the course of the contract as long as the critical outcomes expected are being achieved and/or the desired performance levels are being met.

2.1.1 – Performance Management Strategy The contractor shall be responsible for the quality of all work performed. The contractor measures that quality through the contractor’s own Quality Control (QC) program. QC is applicable to all work performed under the contract and accordingly, for any contract featuring a prime contractor/subcontractor arrangement, the prime contractor’s QC program must also address how it will ensure the quality of all work that its subcontractors perform. The contractor’s QCP shall set forth the staffing and procedures for self-inspecting the quality, timeliness, responsiveness, customer satisfaction, and other performance requirements in the PWS. The contractor shall develop and implement a performance management system with processes to assess and report its performance to the designated Government representative. This QASP enables the Government to take advantage of the contractor’s QC program.

Government representative(s) will monitor performance and review performance reports furnished by the contractor to determine how the contractor is performing against communicated performance objectives. The Government will utilize performance data generated through surveillance in accordance with this QASP to manage contractual performance. Specifically, the Government will complete regular evaluations of contractor performance in accordance with the PRS. The Government will document those evaluations using the Quality Assurance Monitoring Form (QAMF) and the aforementioned Quarterly COR Report. These evaluations will inform the contractor’s rating in the applicable CPAR. Additionally, regular evaluations may lead to action by the Contracting Officer (CO), including, but not limited to, demands for Corrective Action Reports by the contractor, the issuance of Cure Notices, or the issuance of Show Cause letters. In summary, the surveillance completed and documented through implementation of this QASP will have real and meaningful impact upon the performance of the contract.

2.2 - Scope of this QASP This section of the QASP describes the contractual effort to which the QASP applies. Additionally, this section addresses any applicable and special concerns, to include surveillance under Indefinite Delivery contracting methods in the administration of the contract.

2.2.1 – Description of the Contractual Effort The AFRL Spectrum Warfare Division, AFRL/RYW, is charged with supporting the warfighter through the integration of various commercial off the shelf (COTS) components and government off the shelf (GOTS) components utilizing superior systems engineering principles to deliver unique capabilities that are both functional and secure. This technology integration includes the entire cycle, from assessment through production and sustainment. Task orders issued under this IDIQ may focus on technology integration at any phase or all phases of the lifecycle as defined in the specific requirement.

Using over a decade of experience running the Rapid Technology Integration Office, AFRL/RYW has found that advanced engineering analysis, coupled with direct interaction with the warfighter, is critical to delivering the best science and technology (S&T) necessary to successfully complete the United States mission.

The customers of AFRL/RYW are composed of a wide spectrum of users that include Senior Leadership in the United States Government (USG), Combatant Commands, Intelligence Agencies, and other Department of Defense (DoD) entities. Deployment solution environments may include in-garrison, mobile use, traveling, austere locations, and wartime conditions. These environments may be permissive or denied depending on the specific application and use case.

2.2.2 – Surveillance of the Indefinite Delivery Vehicle Effort Some deliverables are at the IDIQ level. These are overarching deliverables that provide summary level information and are most labor intensive at the beginning and ending of the contract. PMR is IDIQ level.

Most deliverables are at the Task Order level. Any deliverables that include sensitive information will be provided to the COR and/or Client as appropriate. The PWS for each Task Order will indicate which deliverables are required and their frequency.

3.0 - Roles and Responsibilities This section of the QASP specifies the roles and responsibilities of the applicable individuals regarding contract surveillance.

3.1 - Contracting Officer (CO) The CO is responsible for monitoring contract compliance, contract administration, and cost control and for resolving any differences between the observations documented by the COR and the contractor. The CO will typically designate one full-time COR as the Government authority for performance management. The number of additional representatives serving as technical inspectors depends on the complexity of the services measured, as well as the contractor’s performance, and said individuals must be identified and designated by the CO.

Assigned CO: Randi Williams Organization or Agency: GSA, FAS, AAS, Apex2, Sector 1 Email: randi.williams@gsa.gov Phone: (404) 861-1364

3.2 - Contract Specialist (CS) The Contract Specialist (CS) is a key liaison between the contracting officer, the client, and the contractor. The CS assists the contracting officer in ensuring contractual requirements are met. The CS may draft and initiate contract documents, research contractual issues, coordinate meetings, oversee compliance, review regulatory requirements, initiate CPARS, review and pay invoices, prepare task order and contract closeouts, and other government contracting functions.

Assigned CS: Rusty Singleton Organization or Agency: GSA, FAS, AAS, Apex 2, Sector 1 Email: rusty.singleton@gsa.gov Phone: (478) 383-9031

3.3 - Contracting Officer’s Representative (COR) The COR is designated in writing by the CO to act as their authorized representative to assist in administering a contract. COR limitations are contained in the written appointment letter. The COR is responsible for technical administration of the project and ensures proper Government surveillance of the contractor’s performance. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. Any changes that the contractor deems may affect contract price, terms, or conditions shall be referred to the CO for action. The COR will have the responsibility for completing QAMFs used to document the inspection and evaluation of the contractor’s work performance. Additionally, the COR is responsible for completing the Quarterly COR Report per the established template and ensuring that completed reports are filed in Tab 47 of the ECF. Government surveillance may occur under the inspection of services clause for any service relating to the contract.

Assigned COR: TBD Organization or Agency: AFRL Spectrum Warfare Division Email: TBD Phone: TBD

3.4 - Client’s Technical Point of Contact (TPOC) The CO may designate a TPOC for the technical administration of the contract. As a representative of the requiring activity, the TPOC may perform or assist in monitoring and assessing the contractor’s performance under the requirements of the PWS); inspecting and recommending acceptance of deliverables; reviewing invoices and recommending approval of payments; providing guidance and clarification of technical requirements, security-related issues, and Information Technology (IT) access.

The TPOC is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf which will:

a. Cause the contractor to perform work outside the scope of the contract.

b. Constitute a change as defined in FAR 52.243-1.

c. Cause an increase or decrease in the price of the contract.

d. Alter the period of performance or delivery dates.

e. Change any of the other express terms or conditions of the contract.

Assigned Client’s TPOC: TBD Organization or Agency: TBD Email: TBD Phone: TBD

3.5 - GSA Project Manager (PM) The GSA PM will rely on the COR and the TPOC to perform the on-site monitoring of the contractor. The GSA PM will stay in close contact with the COR and the TPOC in monitoring the contractor’s performance. The PM is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. Any changes that the contractor deems may affect contract price, terms, or conditions shall be referred to the CO for action.

Assigned GSA PM: Rusty Singleton Organization or Agency: GSA, FAS, AAS, Apex 2, Sector 1 Email: rusty.singleton@gsa.gov Phone: (478) 383-9031

4.0 - Surveillance Procedure

4.1 - The Performance Requirements Summary (PRS) The PRS is the “heart” of quality surveillance. The tasks, performance standards, and Acceptable Quality Levels (AQLs) in the matrix below are established in the contract PWS. The method of surveillance and frequency of surveillance are established by this QASP, and CPAR factors applicable to each task are annotated in this QASP PRS. These parameters have been chosen to ensure that contract surveillance supports and documents contractor performance.

The following provides a description of each column of the QASP PRS matrix.

a. Task: The tasks established in this QASP PRS are derived from those established in the contract PWS. The task provides a description of the work to be surveilled, as well as a PWS citation that associates the task with specific requirements.

b. Performance Standard: Performance standards established in the QASP PRS are derived from those established in the contract PWS. The performance standard describes the expected level of performance associated with a task.

c. Acceptable Quality Level (AQL): AQLs established in the QASP PRS are derived from those established in the contract PWS. The AQL provides a specific metric to allow the Government to determine whether contractor performance regarding a task is acceptable. For the purposes of this QASP, meeting the AQL for a task is commensurate with Satisfactory performance. Failure to meet an AQL constitutes Marginal or Unsatisfactory performance, depending upon the degree to which the AQL has been breached. Exceeding the AQL may constitute Very Good or Exceptional performance, but only if the Government realizes specific benefits, such as a higher quality deliverable or a reduction in contract cost. The IPT should exercise care when determining the AQL, and should avoid establishing perfection as the standard except in the rare instance when perfection is required.

d. Method: This QASP PRS establishes the method of surveillance for each task in the PRS matrix. The appropriate method is one that successfully compares the observed performance with both the performance standard and the AQL. Typical methods include 100 percent inspection, random sampling, periodic sampling/inspection, and customer/client feedback. However, the method selected is not necessarily limited to these options. Rather, the method selected may be tailored to a task to successfully determine whether observed performance meets the established standard and AQL. A best practice is to establish in the description of the method the individual(s) responsible for the surveillance (the “who”) as well as “how” surveillance will be accomplished. The contract COR will utilize the QAMF, Section 4.2, established in this QASP to document completion of surveillance in accordance with the method described.

e. Frequency: This QASP PRS establishes the frequency of surveillance for each task in the PRS matrix. The frequency of surveillance must be tailored with respect to the task, performance standard, AQL, and method. The contract COR will utilize the QAMF to document the date on which surveillance occurred to demonstrate compliance with the frequencies established in this QASP PRS. For example, a monthly status report to be surveilled via 100 percent inspection must be completed monthly.

f. Applicable CPAR Factor(s): This QASP PRS associates each surveillance activity with an applicable CPAR factor. Regular assessment of contractor performance using the CPAR Factors established in FAR 42.1503(h)(4) (e.g., Exceptional, Very Good) will support CPARs completed either annually, or at the conclusion of performance. IPTs should consult FAR 42.1503(h)(4) when determining which CPAR factors are applicable to a particular task and the associated surveillance.

Figure 1: The QASP PRS Matrix

Standard(s)

Meets Task Order requirements

As defined.

Performance

Meets Task Order requirements

As defined.

Performance

Meets Task Order requirements

As defined.

Performance

Meets Task Order requirements

As defined.

Performance

Meets Task Order requirements

As defined.

Performance

Meets Task Order requirements

As defined.

Performance

Professional and complete preparation and presentation.

Professional and complete preparation and presentation.

Professional and complete preparation and presentation

Transition-Out Plan meets requirements

Timely receipt of Release of Claims.

Figure 2: The QASP Deliverables Table

Standard(s)

C.3.6 C.3.6.1

Includes any task assignments and due dates On time Complete and accurate to a 98% performance standard

Complete and accurate to a 98% performance standard Days prior

TO = 1

IDIQ = 2

Schedule, Management

· presentation and

· verbal discussion.

Briefing shall be comprehensive, accurate and reflective of efforts for that month.

Briefing is complete, accurate, and reflective of all task order efforts during the prior month.

On-time delivery at performance standard of 98% accuracy

Plan includes required elements (at minimum).

Plan is practiced as part of corporate culture.

Plan accurately reflects KTR procedures & methodology.

Plan is followed at standard of 98%.

Plan is practiced as part of corporate culture.

Plan accurately reflects KTR procedures & methodology.

Plan is followed at standard of 98%.

Electronic format:

Microsoft Office or Adobe PDF Report is complete, accurate, and reflective of all task order efforts during the quarter.

On-time delivery at performance standard of 98% accuracy

Electronic format:

Microsoft Office or Adobe PDF Report is complete, accurate, and reflective of all task order efforts during the IDIQ performance period.

On-time delivery to performance standard at 98% level

Electronic format:

Microsoft Office or Adobe PDF

4.2 - The Quality Assurance Monitoring Form (QAMF) The Government will use the surveillance methods cited in the PRS to determine whether the performance standards and AQLs have been met by the contractor. The COR will document the Government’s quality assurance surveillance using the monitoring form using Attachment 3, QAMF Template. If the contractor has not met the AQLs, the contractor may be required to develop a Corrective Action Plan (Attachment 5) to show how and by what date it will bring performance up to the required levels.

The COR will upload a copy of the completed QAMF to the ECF as frequently as needed to comply with the PRS or at least once every three months. Completed QAMFs will be uploaded to ECF Tab 47, Surveillance.

4.3 - The Client Complaint Investigation Form Performance management drives the contractor to be customer-focused through initially and internally reviewing the quality of performance. When a customer complaint arises, a customer may use the Client Complaint Investigation Form (Attachment 4). Valid customer complaints must clearly set forth the detailed nature of the complaint, must be in writing and signed, and must be forwarded to the COR. The COR will investigate the complaint, using the Client Complaint Investigation Form and will inform the contractor of the complaint. If corrective actions have been taken or are planned, the COR may document in the Contract Corrective Action Plan (Attachment 5).

4.4 - The Quarterly COR Report A Quarterly COR report must be completed in accordance with FAS PAP 2020-03, and the controlling COR SOP. CORs should refer to the AAS Template for the quarterly COR report, which is provided for by way of a separate document. Regular completion of the QAMF will support completion of the Quarterly COR Report and inform its contents.

Timing for completion and filing of the Quarterly COR Report is dependent upon the award date of the applicable contract or order. As this contract was awarded on (TBD), Quarterly COR Reports associated with this QASP will be completed by the final days of (TBD).

Each Quarterly COR Report will be completed in accordance with the instructions provided in this with FAS PAP 2020-03 and filed under Tab 47, Surveillance, of the ECF.

5.0 - Attachments

5.1 - Attachment 1, Template Memorandum for Documenting Surveillance at Contract Level

[TEMPLATE FOUND ON FOLLOWING PAGE]

MEMORANDUM TO FILE

File completed memorandum in Tab 47 of each applicable order.

a. This memorandum documents the performance of contract surveillance at the contract level for the subject contract. See the Quality Assurance Surveillance Plan (QASP) filed in Tab 47 of the contract level Electronic Contract File (ECF) for details.

b. Surveillance products (e.g., deliverables, inspection reports) pertaining to contract surveillance are documented in accordance with the contract level QASP.

Insert Name Date

COR

(Insert organization)

5.2 - Attachment 2, Template Memorandum for Documenting Surveillance at Order Level

MEMORANDUM TO FILE

File completed memorandum in Tab 47 of base contract.

a. This memorandum documents the performance of contract surveillance at the order level for the subject contract. See the Quality Assurance Surveillance Plan (QASP) filed in Tab 47 of the order level Electronic Contract File (ECF) for details.

b. Surveillance products (e.g., deliverables, inspection reports) pertaining to contract surveillance are documented in accordance with the order level QASP.

Insert Name Date

COR

(Insert organization)

5.3 - Attachment 3, QAMF Template

QUALITY ASSURANCE MONITORING FORM

Quality Assurance Monitoring Form

CITATION

5.4 - Attachment 4, Client Complaint Investigation Form Template

CLIENT COMPLAINT INVESTIGATION FORM

Service: (Insert a brief description of the service that is being reviewed)

Surveillance Period: (Insert date/time of the surveillance period) Month XX, 20XX through Month XX, 20XX Date/Time that Complaint was Received: (Insert date/time) Month XX, 20XX at 11:00 am Eastern Time (ET) (modify based on actual time that complaint was received) Source of Complaint: (Insert information regarding the source of the complaint) Name: _____________________________________________________ Organization or Agency: _______________________________________ Email Address: ______________________________________________ Phone Number: ______________________________________________

Nature of Complaint: (Insert a description of the nature of the complaint)

Result of the Investigation: (Insert a summary of the results of the complaint investigation)

Date/Time that Contractor was Informed of Complaint: (Insert date/time) Month XX, 20XX at 11:00 am ET (modify based on actual time that service provider was informed) Prepared by: ______________________________ Date: _______________ Received by: ______________________________ Date: ________________

5.5 - Attachment 5, Corrective Action Plan Template

Contract Corrective Action Plan A. Administrative Information

Contract Number/Task Order Number:

Report Number:

Issue to (Contractor, Name, Title):

Issue by (COR):

Date of Issue:

Area of Concern (PWS Section, PRS #):

Suspense Date:

B. Description of Area of Concern (Describe in Detail and Ref. PWS (choose one) Section)

Finding 1 Impact

Finding 2 Impact

C. Contractor Response Insert a written Corrective Action Plan that details the corrective action of the Areas of Concern cited. Include the cause and actions taken to prevent recurrence by Suspense Date.

D. Government Response and Actions Taken COR Response to Contractor Corrective Action Plan and Action Taken to Prevent Recurrence - Indicate Acceptance, Partial Acceptance, Rejection with Rationale.

Insert CO Action: (If applicable, reduced payment, cure notice, show cause, other) E. Closeout

Contractor Notified

Client Representative

COR/CO

AAS QASP Template, 9/19/2022

image1.png image2.png