20100210_NGW_Section_J_Attachment_I_QASP_Template_FINAL.doc

Section J, Attachment J: Quality Assurance Surveillance Plan (QASP) Template HC1013-09-R-2004

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

(REMEMBER to delete all italicized text, contained within parentheses herein when completing your PWS. It is shown here for instructional purposes only and must not remain part of the final document.)

Contract Order Title: The NGW Solution (Example)

1. Purpose:

This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance 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.

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. Copies of the original QASP and revisions shall be provided to the contractor and Government officials implementing surveillance activities.

The following FAR clauses may apply depending on contract type:

52.246-4 Inspection of Services – Fixed-Price

2. Government Roles and Responsibilities:

The following personnel shall oversee and coordinate surveillance activities.

a. Contracting Officer (CO) - The CO 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 CO shall 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: (Upon award, Government will enter name.)

Organization or Agency: Defense Information System Agency

b. Contracting Officer’s Technical Representative (COTR) - The COTR is responsible for technical administration of the contract and shall assure proper Government surveillance of the contractor’s performance. The COTR shall keep a quality assurance file. The COTR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf.

Assigned COTR: (Upon award, Government will enter name.)

c. Other Key Government Personnel - (Upon award, Government will enter name, if applicable. This may include Performance Monitors, Quality Assurance experts, etc. who act on behalf of the COTR to monitor performance.)

3. Contractor Representatives:

The following employees of the contractor serve as the contractor’s program manager for this contract.

a. Program Manager – (Enter name.)

b. Other Contractor Personnel - (Enter name(s) or delete these lines if not applicable>

Title: <Enter title(s) or delete these lines if not applicable.)

4. Performance Standards:

(Performance standards establish the performance levels desired by the Government, the offeror shall propose a Service Level Agreement (SLA), including SLAs for outage credit and management thereof). Each SLA item shall be linked to the corresponding subfactor listed in the PWS. The Government performs surveillance to determine if the contractor exceeds, meets or does not meet these standards)

5. Method of Surveillance:

(List out methods of surveillance to ensure the Service Level Agreement is properly met. Surveillance methods shall provide accuracy, objectivity and insightfulness to the contract status. All surveillance methods shall specify the frequency: weekly, monthly, quarterly, etc. All surveillance methods shall be linked to the corresponding subfactor listed in the PWS.)

5.1 Bandwidth Usage Report (Example)

The Bandwidth Usage Report provides monthly data on:

· Bandwidth assignment and utilization by Ship/ MSOC vans

· Bandwidth availability by region

· Bandwidth usage by data type

5.2 Network Performance Report (Example)

The Network Performance Report provides monthly data on:

· Average Committed Information Rate by region

· Average Burstable Information Rate by region

· Average Contention Ratio by region

5.3 Monthly Outage Report (Example)

The Monthly Outage Report provides monthly data on:

· Satellite outages by regions.

5.4 Installation Report (Example)

The Installation Report provides monthly data on:

· Installation Man hours used

· Installation location

· Daily Activity Report

5.5 Operations and Maintenance (O&M) Report (Example)

The O&M Report provides monthly data on:

· Support Man hours used

· O&M Ship location

· Daily Activity Report

6. Documenting Performance:

6.1 Acceptable Performance:

The Government shall document positive performance. Any report may become a part of the supporting documentation for fixed fee payments, award fee payments, or other actions.

6.2 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 KO.

For Official Use Only, Not Releasable Under FOIA, Source Selection Information – FAR 2.101 and FAR 3.104

PAGE

Section J, Attachment I: Quality Assurance Surveillance Plan (QASP) Template v 1.0

HC1013-09-R-2004