Attachment 5 - QASP.docx

Quality Assurance Surveillance Plan (QASP) for Public Address Mass Notification System (PAMNS) and Code Blue Help Point System Maintenance Support Services

1.0 Introduction

This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate the services provided by the contractor in accordance with the Statement of Work (SOW) for the maintenance and support of the Public Address Mass Notification System (PAMNS) and the Code Blue Help Point systems at the VA Salt Lake City Healthcare System (SLCHCS).

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.

2.0 Purpose

The purpose of this QASP is to ensure services provided by the contractor are performed in accordance with the contract requirements, and to ensure the continuous operation, reliability, and performance of the PAMNS and Code Blue Help Point systems within the designated facilities.

3.0 Performance Objectives and Measures

The primary performance objectives and measures are derived from the contract's Scope of Work and objectives.

4.0 Methods of Surveillance

The performance of the contractor will be monitored by the COR through the following methods of surveillance:

· Random Inspections: Unscheduled checks to verify compliance with contract requirements.

· Periodic Inspections: Scheduled reviews of preventive maintenance and repair work.

· Customer Feedback: Gathering feedback from facility staff on contractor performance and responsiveness.

· Review of Reports and Documentation: Analyzing reports such as Initial Assessment Reports, Monthly Maintenance Reports, and Detailed Repair and Upgrade Reports.

5.0 Documentation and Reports

Contractor is required to submit the following reports as specified in the SOW:

· Initial Assessment Report: Within 30 days of contract start date.

· Monthly Maintenance Reports: By the 5th business day of each month, detailing all activities performed, the condition of the systems, and any recommendations.

· Detailed Repair and Upgrade Reports: Within 5 days of task completion.

· Updated Inventory and System Condition Reports: Annually.

6.0 Evaluation Procedures

· Daily Work Logs: The contractor shall use a daily log system at the facility indicating times of arrival and departure along with a description of the work performed.

· Review Meetings: Regular review meetings between the contractor and the COR to discuss performance, issues, and improvements.

· Performance Reviews: The COR will conduct formal performance reviews to assess the contractor’s adherence to the SOW and QASP.

7.0 Performance Thresholds

The COR shall take immediate action to address any deviations from the performance objectives and standards. Any serious or consistent failures to meet the required AQL might result in formal corrective actions ranging from contractor notification to contract termination or non-renewal.

8.0 Roles and Responsibilities

Contracting Officer (CO): Responsible for awarding and administering the contract.

Contracting Officer’s Representative (COR): Responsible for the day-to-day monitoring of the contractor's performance and compliance with the contract. The COR will also ensure that any identified issues are addressed promptly.

9.0 Signatures

Signature – Contracting Officer Representative

Signature – Contracting Officer