Attachment_2_PRS_and_QASP_05JUN2015.doc

Performance Requirements Summary (PRS) and Quality Assurance Surveillance Plan (QASP)

1. Objective. This Performance Requirements Summary (PRS) and Quality Assurance Surveillance Plan (QASP) serves as the principal basis for assessing overall performance quality associated with this effort. This document will be used by the Government to assess the effectiveness of the Contractor’s management and technical services. This QASP provides the methodology by which the Contractor's performance will be monitored to determine compliance with established performance objectives and to establish performance benchmarks that ensure a quantifiable basis for measuring effectiveness. The plan is designed so that surveillance is limited to that which is necessary to verify the Contractor is performing management and technical services satisfactorily and relates directly to performance of the objectives delineated in the PWS.

2. Government Surveillance. The Government will identify an individual to function as the Contracting Officer’s Representative (COR) for this task, and the COR’s authority will be limited to administering specific aspects of the contract. The COR will not provide direction that is outside the scope of responsibilities delineated under this contract. The designated individual will:

· Maintain a detailed knowledge of the technical requirements of the contract

· Document Contractor performance in accordance with the QASP

· Identify and immediately forward notifications of deficient, or non-compliant performance to the Contracting Officer

· Approve priorities of support, resources, and associated schedules

3. Surveillance Methods. Surveillance of Contractor performance is the method used by the COR to determine whether the Contractor is effectively and efficiently complying with all terms and conditions of the task order. In addition to the COR, the government will also assign Technical Representatives (TRs) who will provide functional expertise to assist the COR in evaluating Contractor performance. The following methods of surveillance shall be used in the administration of this QASP and the standards are delineated in the below Performance Requirements Summary (PRS) table:

a. Demonstration. A qualification method that is carried out by operation and relies on observable functional operation. It does not require the use of instrumentation or special test equipment.

b. Analysis. A qualification method that is carried out by examining and assessing the application of techniques in order to determine if they are appropriate and sufficient. The quality of performance can be determined from Government or Contractor task-based or Management Information System (MIS) reports; or from Government observation of completed tasks. In some instances, reports may be available in the form of information on a Contractor's performance against contract requirements. Reports generally provide information regarding various characteristics of tasks and can, therefore, be used to determine acceptability of a Contractor's performance.

c. Inspections. Qualitative inspections can be accomplished through one of the following techniques:

· Random or Stratified Sampling: With random sampling, services are sampled to determine if the level of performance is acceptable. Random sampling works best when the number of instances of the services being performed is very large and a statistically valid sample can be obtained. Stratified sampling focuses on selected parts of total Contractor output for sampling. Computer programs may be available to assist in establishing sampling procedures.

· Periodic Inspection, Judgmental Inspection, or Planned Sampling: This method, sometimes called "planned sampling,” consists of the evaluation of tasks selected on other than a 100% or random basis.

4. Performance Requirements. Table 1 provides Performance Standards with corresponding reference to the PWS paragraphs, Acceptable Quality Levels and performance monitoring method.

Table 1 – Performance Requirements Summary

(What task must be accomplished to give you the desired result?)

Performance Standard

(What should the standards for completeness, reliability, accuracy, timeliness, quality and/or cost be?)

Acceptable Quality Level (AQL)

(How much error will you accept?)

Monitoring Method

(How will you determine that success has been achieved?)

Demo – D

Analysis – A

Inspect - I

3.2.10 General Requirements PSs & AQLs

3.2.10.1

3.2.10.2

3.2.10.4

AQL2A – 10% of task deliverables will be rejected no more than once

D, A, I

3.2.10.5

3.2.10.6

AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

D, A, I

3.3.2 HLO1 – Systems Engineering & Integration PSs & AQLs

3.3.2.2

3.3.2.4

3.3.2.5

AQL2B – 5% of specific task deliverables will be rejected no more than twice

D, A, I

3.3.2.6

3.4.2 HLO2 Mission Support PSs & AQLs

3.4.2.2

3.4.2.4

3.4.2.5

AQL2B – 5% of specific task deliverables will be rejected no more than twice

D, A, I

3.4.2.6

AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

D, A, I

3.5.2 HLO3 Systems Operations and Support PSs & AQLs

3.5.2.2

3.5.2.4

3.5.2.5

3.5.2.6

3.5.2.8

3.5.2.9

3.5.2.10

3.5.2.11

3.6.2 HLO4 Cybersecurity PSs & AQLs

3.6.2.2

3.6.2.4

3.6.2.5

3.6.2.6

AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

A, I

3.7.2 HLO5 Help Desk PSs & AQLs

3.7.2.2

3.7.2.4

3.7.2.5

3.7.2.6

3.7.2.8

3.7.2.9

3.7.2.10

5. Quality Assurance. Table 2 provides method and frequency of performance monitoring.

Table 2 - Quality Assurance Surveillance Plan (QASP)

(What task must be accomplished to give you the desired result?)

Performance Standard

(What should the standards for completeness, reliability, accuracy, timeliness, quality and/or cost be?)

Acceptable Quality Level (AQL)

(How much error will you accept?)

Monitoring Method

(How will you determine that success has been achieved?)

Demo – D

Analysis – A

Inspect - I Monitoring Frequency (How often will the COR & TRs monitor performance?)

Monthly – M

Random – R

3.2.10 General Requirements PSs & AQLs

3.2.10.1

3.2.10.2

3.2.10.4

AQL2A – 10% of task deliverables will be rejected no more than once

3.2.10.5

3.2.10.6

AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.3.2 HLO1 – Systems Engineering & Integration PSs & AQLs

3.3.2.2

3.3.2.4

3.3.2.5

AQL2B – 5% of specific task deliverables will be rejected no more than twice

3.3.2.6

3.4.2 HLO2 Mission Support PSs & AQLs

3.4.2.2

3.4.2.4

3.4.2.5

AQL2B – 5% of specific task deliverables will be rejected no more than twice

3.4.2.6

AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.5.2 HLO3 Systems Operations and Support PSs & AQLs

3.5.2.2

3.5.2.4

3.5.2.5

3.5.2.6

3.5.2.8

3.5.2.9

3.5.2.10

3.5.2.11

3.6.2 HLO4 Cybersecurity PSs & AQLs

M

3.6.2.2

3.6.2.4

3.6.2.5

3.6.2.6

AQL2C – Rejected deliverables will be corrected and resubmitted within three (3) business days or by the required completion date

3.7.2 HLO5 Help Desk PSs & AQLs

3.7.2.2

3.7.2.4

3.7.2.5

3.7.2.6

3.7.2.8

3.7.2.9

3.7.2.10