Attachment 6. Quality Assurance Surveillance Plan.docx
DOCX document 78 KB Posted
- Attached to
- DRAFT FOPR for 24/7 NOC _ OASIS+ Total Small Business Federal contract opportunity
- Solicitation number
- FA880625RB003
- Issued by
- Department of the Air Force
About this file
This document is a Quality Assurance Surveillance Plan (QASP) for a 24/7 Network Operations Center support contract between the United States Space Force (USSF) Space Systems Command (SSC) and a contractor. The QASP outlines the government's roles and responsibilities, the contractor's representatives, and the performance standards and methods of surveillance that will be used to evaluate the contractor's performance. Key performance objectives include user satisfaction, timely completion of Tier 1 support and infrastructure tasks, and on-time delivery of contract data requirements. The government will use methods such as direct observation, periodic inspection, and user surveys to monitor performance and determine if it exceeds, meets, or does not meet the stated standards and acceptable quality levels. The QASP provides templates for documenting both acceptable and unacceptable performance.
The related federal contract opportunity is a draft Request for Proposal (RFOP) for a 24/7 Network Operations Center (NOC) support contract under the OASIS+ Total Small Business program. The solicitation is being issued by the Department of the Air Force.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 24x7 NOC FORP PCO Letter.pdf | ||
| Solicitation - Clauses and Provisions.pdf | ||
| Attachment 2. Placement Procedures.pdf | ||
| Attachment 5. Organizational Conflict of Interest Checklist.pdf | ||
| Attachment 3. Master Contract Data Requirements List.docx | DOCX document | |
| Attachment 4 Supply Pricing Table.xlsx | XLSX spreadsheet | |
| Attachment 7. Contract Security Classification Specification DD254.pdf | ||
| Attachment 8. Comments Resolution Matrix.docx | DOCX document | |
| Solicitation - FA880625RB003.pdf | ||
| Attachment 1. Stament Of Work.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT 6
24/7 Network Operations Center Quality Assurance Surveillance Plan
United States Space Force (USSF) Space Systems Command (SSC) Operational Space C2 Acquisition Delta (BCC)
Acquisition and Management of Supply Contract
Date 09 October 2024
1. PURPOSE.
This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate the delivery of the supply for the stated contract. This QASP explains the following:
· What will be monitored.
· How monitoring will take place.
· Who will conduct the monitoring.
· How monitoring efforts and results will be documented.
This QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. In addition, the QASP should recognize that unforeseen and uncontrollable situations may occur.
This QASP is a “living document” and the Government may review and revise it on a regular basis. However, the Government shall coordinate changes with the contractor. Updates shall ensure that the QASP remains a valid, useful, and enforceable document. Copies of the original QASP and revisions shall be provided to the contractor and Government officials implementing surveillance activities.
2. GOVERNMENT ROLES AND RESPONSIBILITIES.
The following personnel shall oversee and coordinate surveillance activities.
a. Procuring Contracting Officer (PCO) - The PCO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and shall safeguard the interests of the United States in the contractual relationship. The PCO shall also assure that the contractor receives impartial, fair, and equitable treatment under this contract. The PCO is ultimately responsible for the final determination of the adequacy of the contractor’s performance.
Assigned PCO: <enter name> Organization or Agency: <enter organization or Agency name> Telephone: <enter number> Email: <enter address>
b. Contracting Officer’s Representative (COR) - The COR is responsible for technical administration of the contract and shall assure proper Government surveillance of the contractor’s performance. The COR shall keep a quality assurance file. At the conclusion of the contract or when requested by the PCO, the COR shall provide documentation to the PCO. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. The contractor shall refer any changes they deem may affect contract price, terms, or conditions to the PCO for action.
Assigned COR: <enter name> Telephone: <enter number> Email: <enter address>
c. Other Key Government Personnel - <enter name or delete these lines if not applicable. This may include Performance Monitors, Inspectors, etc. who act on behalf of the COR to monitor performance.> Title: <enter title> Telephone: <enter number> Email: <enter address>
3. CONTRACTOR REPRESENTATIVES:
The following employees of the contractor serve as the contractor’s Program Manager and Task Manager for this contract. <Communication should occur with them during QASP development. It will help if they review the draft QASP and accept the final version.>
a. Program Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address>
b. Task Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address>
c. Other Contractor Personnel - <upon award, enter name or delete these lines if not applicable> Title: <enter title> Telephone: <enter number> Email: <enter address>
4. PERFORMANCE STANDARDS.
Performance standards define desired services. The Government performs surveillance to determine if the contractor exceeds, meets or does not meet these standards.
The Performance Requirements Summary Matrix, paragraph 4.1 in the Performance Work Statement includes performance standards. The Government shall use these standards to determine contractor performance and shall compare contractor performance to the Acceptable Quality Level (AQL).
| Performance Objective |
| Performance Threshold |
| Surveillance Method |
| Frequency |
| User Satisfaction/Engagement |
| 95% of survey Satisfactory or above |
| Survey |
| Quarterly |
| Enablement to Development Teams |
| 95% of survey Satisfactory or above |
| Survey |
| Quarterly |
Completion of Tier 1 support (Document a key Network performance area to assess)
| 90% on time completion |
| Survey |
| Quarterly |
| Completion of designated Infrastructure support tasks |
| 90% completion of tasks within designated timeframes |
| Survey/Periodic Inspection |
| Quarterly |
| Delivery of CDRLs on time |
| 90% on-time delivery of all data and reports |
| Periodic Inspection |
| Monthly |
5. METHODS OF QA SURVEILLANCE.
Various methods exist to monitor performance. The COR shall use the surveillance methods listed below in the administration of this QASP.
Regardless of the surveillance method, the COR shall always contact the contractor's task manager or on-site representative when a defect is identified and inform the manager of the specifics of the problem. The COR, with assistance from the contract specialist (CS), shall be responsible for monitoring the contractor’s performance in meeting a specific performance standard/AQL.
a. DIRECT OBSERVATION. (Can be performed periodically or through 100% surveillance and written documentation.)
b. PERIODIC INSPECTION. (Uses a comprehensive evaluation of selected outputs. Inspections may be scheduled [Daily, Weekly, Monthly, Quarterly, or annually] or unscheduled, as required.)
c. USER SURVEY. (Combines elements of validated user complaints and random sampling. Random survey is conducted to solicit user satisfaction.)
Surveillance results may be used as the basis for actions (to include payment deductions) against the contractor. In such cases, the Inspection of Services clause in the Contract becomes the basis for the PCO’s actions.
7. RATINGS.
Metrics and methods are designed to determine if performance exceeds, meets, or does not meet a given standard and acceptable quality level. A rating scale shall be used to determine a positive, neutral, or negative outcome. The following ratings shall be used:
| EXCEPTIONAL: |
| Performance significantly exceeds contract requirements to the Government’s benefit. |
| SATISFACTORY: |
| Performance meets contractual requirements. |
| UNSATISFACTORY: |
| Performance does not meet contractual requirements. |
8. DOCUMENTING PERFORMANCE.
a. ACCEPTABLE PERFORMANCE.
The Government shall document positive performance. A report template is attached. Any report may become a part of the supporting documentation for milestone payments, or other actions.
b. UNACCEPTABLE PERFORMANCE.
When unacceptable performance occurs, the COR shall inform the contractor. This will normally be in writing unless circumstances necessitate verbal communication. In any case the COR shall document the discussion and place it in the COR file.
When the COR determines formal written communication is required, the COR shall prepare a Contract Discrepancy Report (CDR), and present it to the contractor's task manager or on-site representative. A CDR template is attached to this QASP.
The contractor shall acknowledge receipt of the CDR in writing. The CDR will specify if the contractor is required to prepare a corrective action plan to document how the contractor shall correct the unacceptable performance and avoid a recurrence. The CDR will also state how long after receipt the contractor has to present this corrective action plan to the COR. The Government shall review the contractor's corrective action plan to determine acceptability.
Any CDRs may become a part of the supporting documentation for contract payment deductions, fixed fee deductions, award fee nonpayment, or other actions deemed necessary by the PCO.
9. FREQUENCY OF MEASUREMENT.
a. Frequency of Measurement.
During contract/order performance, the COR shall take periodic measurements, quarterly as specified in the AQL column of the Performance Standards Summary Matrix, and shall analyze whether the negotiated frequency of measurement is appropriate for the work being performed.
b. Frequency of Performance Assessment Meetings.
The COR shall meet with the contractor quarterly to assess performance and shall provide a written assessment.
Prepared by: Logan W. Bolitho, Maj, USSF
Signature – Contracting Officer’s Representative
PERFORMANCE REPORT
1. CONTRACT NUMBER: <insert number>
2. Prepared by: (Name of COR) <insert name>
3. Date and time of observation:
4. Observation:
<Examples of items to include in a report are:
- Method of surveillance.
- How frequently you conducted surveillance.
- Surveillance results.
- Number of observations.>
Prepared by: <Enter COR’s name>
| _____________________________ | ________________ | |
| Signature – Contracting Officer’s Representative | Date |
CONTRACT DISCREPANCY REPORT (CDR)
1. Contract Number: <insert number>
2. TO: (Contractor Task Manager or on-site representative) <insert name>
3. FROM: (Name of COR) <insert name>
4. Date and time observed discrepancy:
5. DISCREPANCY OR PROBLEM:
<Describe in detail. Identify any attachments.>
5. Corrective action plan:
A written corrective action plan < is / is not > required.
< If a written corrective action plan is required include the following. > The written Corrective Action Plan will be provided to the undersigned not later than < # days after receipt of this
CDR. >
Prepared by: <Enter COR’s name>
| _____________________________ | ________________ | |
| Signature – Contracting Officer’s Representative | Date |
Received by:
| _____________________________ | ________________ | |
| Signature - Contractor Task Manager or on-site representative | Date |
image1.png
File details come from the government source that posted it. Updated .