Attachment J.2 - Sample Quality Assurance Surveillance Plan (QASP).pdf

PDF 136 KB Posted

Attached to
Feed the Future Haiti Resilience and Agriculture Sector Advancement (HRASA) Activity
Solicitation number
72052120R00024
Issued by

View the file

Other files

Show all 18

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SAMPLE

Quality Assurance Surveillance Plan (QASP)

PROGRAM NAME

1. Purpose: This QASP specifically corresponds to Section C – PERFORMANCE BASED WORK

STATEMENT (PWS) in Contract/Task Order # [ Type in award number and program name]. The

PWS discusses the requirements and standards of performance of the award. This document provides a surveillance plan sufficient to ensure Contractor performance and compliance with the FAR.

2. Surveillance Frequency and Sampling Method(s): The objective of this Surveillance Plan is to evaluate how the [Name of program] Task Order is being performed by [Contractor Name] in the

[Place of Performance]. Quality Assurance methods include: Random Sampling, 100% Inspection, Scheduled Observations, Unscheduled Observations, User Survey, Validated User /Customer

Complaints, Periodic Inspection, and Others as appropriate.

3. Planning: [Provide a narrative in this section giving summary QASP information about each deliverable that will be evaluated. The entries should match the deliverables specified in the task order. Do not repeat the technical specification from the PWS for each subtask, but focus on narrating how you will carry out quality assurance on the deliverables. You may order these QASP deliverables in any sequence you find convenient.]

Planning Table: Fill this out based on the narrative above. Describe the quality assurance surveillance method you will use for each.

Del. # Del. Type Performance Standard Acceptable

Quality Level Method Used Frequency

Summary Planning Table

Deliverable. No. Number the Summary Table rows sequentially so they can be referred to in the Detailed Evaluation/Decision/Action Table.

Deliverable Type Give a descriptive name of the deliverable, like Monthly Status Report;

Management Plan; Software Design Specification; Transition Plan, etc.

Performance Standard Using objective and measurable terms, describe the standard of quality you expect the deliverable to adhere to. For example, restores desktop computer service within four hours of receiving trouble report during business hours.

Acceptable Quality Level State what level of quality for a deliverable will make it an acceptable deliverable. For example, meets performance standard 95% of the time.

SAMPLE QASP

Method Used Explain how you will inspect deliverables to determine if the performance standard is met. Methods include 100% inspection (often used for written products), random or scheduled inspections, testing, etc.

Frequency State how often inspections will take place.

Evaluation /Decision / Action Table

Del. #

E ac h D el iv er ab le

In st an ce o r

R e

D el iv er y

P er fo rm an ce

S ta n d ar d

A cc ep ta b le

Q u al it y L ev el

M et h o d U se d

F re q u en cy

E v al u at io n D at e

C o m p li an ce L ev el

C au sa ti o n

F ac to r

E ff ec t o n

M is si o n

A ct io n

R eq u ir ed

D at e A ct io n

R eq u ir ed b y

C o m m en t

Reference Del. No. Use the number in the Summary Table for the deliverable type being evaluated.

Deliverable Type Use the same descriptive name of the deliverable as used in the Summary

Table. Add any information necessary to make it unique, like the date of a monthly status report, or re-delivery information about a second or subsequent delivery of the same product.

Performance Standard Summarize the standard of quality stated in the Summary Table.

Acceptable Quality Level Summarize the AQL stated in the Summary Table.

Method Used Summarize the method description stated in the Summary Table.

Frequency Repeat the frequency of inspection stated in the Summary Table.

Evaluation Date Give the date of the specific evaluation. For recurring deliverables, give the date of the particular instance of the deliverable. For re-deliveries, give the date of the re-delivery.

Compliance Level Results of the evaluation. Report this in the same objective and measurable terms used to state the performance standard.

Causative Factor If the evaluation is not satisfactory, explain any causative factors.

Effect on Mission If the evaluation is not satisfactory, explain any impact on the mission.

SAMPLE QASP

Action Required If the evaluation is not satisfactory, explain any action needed.

Resubmission of a deliverable may be one possibility.

Date Action Required By This action date should be in alignment with any statements in the PWS as to redelivery requirements.

Comment Add any explanatory comments that may be appropriate.

File details come from the government source that posted it. Updated .