PODCAST_QASP_RFQ.doc
DOC document 72 KB Posted
- Attached to
- Podcast Services Federal contract opportunity
- Solicitation number
- H92240-17-T-0037
- Issued by
- United States Special Operations Command
About this file
QASP
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| PODCAST_PWS_RFQ.docx | DOCX document | |
| H92240-17-T-0037_RFQ.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
Quality Assurance Surveillance Plan
PODCAST SERVICES
1.0 PURPOSE.
1.1. This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance for the stated contract. This plan provides a basis for the Government to evaluate the quality of contractor performance. The oversight provided for in the contract and in this plan will ensure service levels reach and maintain the required levels throughout the contract term. This plan will provide the Government with a proactive way to avoid unacceptable or deficient performance, and provide verifiable input for required annual past performance evaluations. This QASP explains the following:
1.1.1. What will be monitored.
1.1.2. How monitoring will take place.
1.1.3. Who will conduct the monitoring.
1.1.4. How monitoring efforts and results will be documented.
1.2 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.
1.3 This QASP is a “living document” and the Government may review and revise it on a regular basis. However, the Government will coordinate changes with the contractor. Updates will ensure that the QASP remains a valid, useful, and enforceable document. Copies of the original QASP and revisions will be retained the contract file.
2.0 Government Roles and Responsibilities.
2.1 The following personnel will oversee and coordinate surveillance activities.
2.1.1 Contracting Officer (CO) - The CO will ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and will safeguard the interests of the United States in the contractual relationship. The CO will also assure that the contractor receives impartial, fair, and equitable treatment under this contract. The CO is ultimately responsible for the final determination of the adequacy of the contractor’s performance.
Assigned CO: WARCOM-Contracts Organization or Agency: Naval Special Warfare Center
2.1.2 Contracting Officer’s Representative (COR) –The COR is responsible for the technical administration of the contract, assuring proper Government surveillance of the contractor’s performance and keeping a quality assurance file. At the conclusion of the contract or when requested by the CO, the COR will provide documentation to the CO. 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 CO for action.
Assigned COR: TBD Other Key Government Personnel – TBD
2.1.3 Technical Representative(s) (TRs) – The requiring activity representative who may be assigned to provide technical/administrative assistance to the COR. TRs may be assigned to assist and support the COR with contractor surveillance but have limited authority to provide any technical direction or clarification directly to the contractor.
3.0 Contractor Representatives:
3.1 Contractor shall appoint an employee to serve as the primary point of contact responsible for coordinating issues relating to quality assurance and surveillance issues.
Program Manager – TBD
Other Contractor Personnel – TBD
4.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS).
4.1 Performance standards define desired services. The Government performs surveillance to determine if the contractor exceeds, meets, or does not meet these standards.
4.2 The Performance Requirements Summary Matrix includes performance standards outlined in the Performance Work Statement. The Government shall use these standards to determine contractor performance and shall compare contractor performance to the Acceptable Quality Level (AQL):
| Performance Objective |
| PWS Reference |
| Performance Standard (and AQL) |
| Method of Performance Assessment |
| Incentive (Positive and/or Negative) (Impact on Contractor Payments) |
Produce 25 (max) quality podcast episodes, including hosting, editing, effects, and transcript.
4.1, 5.1, Table 5.1A
Direct Observation:
1. Minimum length of 30 minutes, clear audio, consistent intro/outro;
2. Edited as necessary for clarity, length, security and appropriateness;
3. Verbatim transcript completed within 1 week after recording.
(Meets Standard)
| Inspection by COR |
| Positive: Letters of Commendation and/or Appreciation, favorable performance reviews. |
Negative: Poor performance will be documented.
1. Inspection/Acceptance and FAR Clause 52.212-4(a) and Termination for Cause FAR Clause 52.212-4(m) and 52.246-4 Inspections of Services.
4.3 The Government shall use a reduction in payments as a negative incentive. Incentives shall be based on meeting, or not meeting performance standards.
5.0 CONTRACT DELIVERABLES.
5.1 The Contractor shall provide all of the following documents during the course of the contract at the frequency noted in the table below:
| Deliverable Number |
| PWS Para. |
| Item Description |
| Due Date |
| Government |
POC(s)
| D001 |
| 4.1 |
| Podcast |
| Every two weeks after contract award. |
| COR: Kenneth Marra |
TR: Scott Williams
| D002 |
| 4.1 |
| Verbatim Transcript |
| Delivered with each podcast production. |
| COR: Kenneth Marra |
TR: Scott Williams
6.0. Ratings.
6.1 Contractor performance will be rated using the Contractor Performance Assessment Report (CPAR). Metrics and methods are designed to determine if performance exceeds, meets, or does not meet a given standard and acceptable quality level. The rating scale below will be used to determine a positive, neutral, or negative outcome.
| Rating |
| Contract Requirements |
| Problems |
| Corrective Actions |
| Exceptional |
| Exceeds Many – with Government Benefit |
| Few Minor Problems |
| Minor Problems; Highly Effective |
| Very Good |
| Exceeds Some – with Government Benefit |
| Some Minor Problems |
| Minor Problems; Effective |
| Satisfactory |
| Meets All |
| Minor Problems and Major |
| Major Problems w/Corrective Action |
| Marginal |
| Does Not Meet Some – with Government Impact |
| Serious; Recovery Possible |
| Marginally Effective; Not Fully Implemented |
| Unsatisfactory |
| Does Not Meet Most – with Government Impact |
| Serious; Recovery Not likely |
| Multiple Significant Problems; Ineffective |
7.0 DOCUMENTING PERFORMANCE.
7.1. Acceptable Performance. The Government will document positive performance. The most common format used for this action will be via CPARs. Any report may become a part of the supporting documentation for fixed fee payments, award fee payments, or other actions.
7.2 Unacceptable Performance. When unacceptable performance occurs, the COR will inform the contractor. This will normally be in writing unless circumstances necessitate verbal communication. In any case, the COR will document the discussion and place it in the COR file.
7.2.1. When the COR determines formal written communication is required, the COR will prepare a Contract Discrepancy Report (CDR), and present it to the contractor's manager or on-site representative. A CDR template is attached to this QASP.
7.2.2. The contractor shall be required to 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 will review the contractor's corrective action plan to determine acceptability.
7.2.3 Any CDR will become a part of the supporting documentation for contract payment deductions, fixed fee deductions, award fee nonpayment when applicable. The Government will use any completed CDR as part of an overall evaluation of Contractor performance when determining present or future contractual actions.
8.0 Frequency of Measurement.
8.1. During contract/order performance, the COR will take periodic measurements and analyze whether the negotiated frequency of measurement is appropriate for the work being performed.
8.2. The COR will interact with the contractor at least monthly and meet annually to assess performance and will provide a written assessment.
Signature – Contractor Program Manager
Signature – Contracting Officer’s Representative
Signature – Contracting Officer
Contract Discrepancy Report (CDR)
1. Contract Number: <insert number>
2. TO: (Contractor’s 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’s Manager or on-site representative
Date
File details come from the government source that posted it. Updated .