Quality Assurance Surveillance Plan (QASP).docx

CUI//PROCURE

Quality Assurance Surveillance Plan (QASP)

· Transition-In Plan (A004)

· PEO DHMS Cost, Schedule, Performance (CSP) Report (A006)

· Contractor Work Breakdown Structure (CWBS) (A007)

· Cost and Hour Report (A008)

· Technical Data Report (A008)

· Monthly Progress Report (MPR) (D006) Timeliness: 100% of reports are submitted on or before the due date.

Quality: The QCP, Transition-In Plan, CSP, CWBS, Cost and Hour Report, Technical Data Report, MPR, and all subsequent monthly updates (as applicable) require no more than 4 minor[footnoteRef:1] corrections for accuracy or completeness. A report requiring correction for a material inaccuracy fails the AQL. [1: Minor is defined as an imperfection or deviation from the quality standard that does not affect the usability, safety, or core functionality of the performance objective. ]

Report is more than 2 business days late OR requires correction due to material inaccuracy.

Does Not Meet Some Contract Requirements:

Report is 1-2 business days late OR requires more than 5 minor1 corrections.

Meets Contract Requirements:

Report is submitted on time and requires no more than 4 minor1 corrections.

Meets & Exceeds Some Contract Requirements: Recurring Report is submitted on time and requires no more than 2 minor1 corrections.

Meets & Exceeds Many Contract Requirements: Recurring Report is submitted ahead of schedule and requires zero corrections.

Initial Baseline: The initial baseline IMS is successfully established and approved within the timeframe specified in the PWS or task order after requiring no more than 1 minor revision cycle.

Updates: All subsequent IMS updates are submitted on time and require no more than 2 minor1 corrections for logic or status.

Initial: Requires more than 2 major[footnoteRef:2] revisions, causing a significant delay to the project baseline. [2: Major is defined as an omission, substantive flaw, or material inaccuracy that does not affect the usability, safety, or core functionality of the performance objective. ]

Updates: Submitted more than 2 business days late OR contains fundamental flaws (e.g., invalid critical path, broken logic) requiring complete rework.

Does Not Meet Some Contract Requirements:

Initial: Requires 1 major2 revision cycle to be deemed acceptable.

Updates: Submitted 1-2 business days late OR requires more than 2 minor1 corrections or 1 major2 logic correction.

Meets Contract Requirements:

Initial: Approved after no more than 1 minor1 revision cycle.

Updates: Submitted on time and requires no more than 2 minor1 corrections.

Meets & Exceeds Some Contract Requirements: Initial: Approved with only minor1 comments on the first draft (no revision cycle needed).

Updates: Submitted on time and requires only 1 minor1 correction.

Meets & Exceeds Many Contract Requirements:

Initial: Submitted ahead of schedule and approved on first submission with no changes required. Updates: Submitted ahead of schedule with zero corrections, and the contractor proactively identifies risk and schedule optimization opportunities.

· Implementation Plan (A010)

The Deployment Approach and Implementation Plan require more than 2 major2 revision cycles, causing significant delay to the project baseline.

Does Not Meet Some Contract Requirements:

The Deployment Approach and Implementation Plan require 2 major2 revision cycles to be deemed acceptable by the Government.

Meets Contract Requirements:

The Deployment Approach and Implementation Plan is acceptable after no more than 1 major2 revision cycle.

The Deployment Approach and Implementation Plan is submitted ahead of schedule and accepted on first submission with no changes required.

Validation accuracy is 98% or greater with no critical errors on the first pass.

No instances of data loss (i.e., non-recoverable) for patient records are permissible.

Data accuracy rate is less than 99.5% for all critical data elements that are recoverable.

A non-recoverable patient record data loss has occurred.

Does Not Meet Some Contract Requirements:

Post-migration validation confirms an accuracy rate between 99.5% and 99.89% for critical data elements that are recoverable.

There is no instance of patient record data loss (i.e., non-recoverable).

Meets Contract Requirements:

Post-migration validation confirms a 99.9% or greater data accuracy rate for critical data elements.

There is no instance of patient record data loss (i.e., non-recoverable).

Meets & Exceeds Some Contract Requirements: Data accuracy rate is greater than 99.95% for all critical data elements that are recoverable.

There is no instance of patient record data loss (i.e., non-recoverable).

Meets & Exceeds Many Contract Requirements:

Data accuracy rate is 100% for all critical data elements that are recoverable.

There is no instance of patient record data loss (i.e., non-recoverable).

Functionality: No more than 1% of all hardware delivered and connected fails during validation.

Timeliness: More than 5% of shipments are late.

Condition: More than 3% of the total hardware is damaged due to improper packaging and handling.

Functionality: More than 3% of hardware does not function when validated.

Does Not Meet Some Contract Requirements:

Fails to meet one of the AQL thresholds:

Timeliness: 2.1% to 5% of hardware shipped is late.

Condition: 1.1% to 3% of hardware is damaged due to improper packaging and handling.

Functionality: 1.1% to 3% or greater of hardware fails during validation.

Meets Contract Requirements:

Timeliness: No more than 2% of hardware shipped is late.

Condition: No more than 1% of the hardware is damaged due to improper packaging and handling.

Functionality: 1% of hardware does not function when validated.

Meets & Exceeds Some Contract Requirements: Timeliness: 100% of hardware shipped is on time.

Condition: Less than 0.5% of the hardware is damaged due to improper packaging and handling.

Functionality: Less than 0.5% of hardware does not function when validated.

Meets & Exceeds Many Contract Requirements: Timeliness: 100% of hardware shipped is on time.

Condition: 100% of hardware is fully functional upon validation.

Functionality: 100% of hardware has zero damage due to improper packaging.

More than 3% of medical products fail when validated.

Does Not Meet Some Contract Requirements:

2% of medical products fail when validated.

Meets Contract Requirements:

More than 98% of medical products function when validated.

Meets & Exceeds Some Contract Requirements:

99% of medical products function when validated.

Meets & Exceeds Many Contract Requirements:

100% of medical products are fully functional upon validation.

Training Curriculum and supporting Training Plan are acceptable after no more than 1 major2 revision cycle.

Deployment Readiness: ≥95% of total population trained[footnoteRef:3]. [3: Trained means that a user has passed the competency assessment with a score of 80% or higher.]

Deployment Readiness: <90% of total population trained3, forcing a "No-Go" decision.

Does Not Meet Some Contract Requirements:

Deployment Readiness: 90% - 94.9% of total population trained3.

Meets Contract Requirements:

Deployment Readiness: ≥95% of total population trained3.

Meets & Exceeds Some Contract Requirements:

Deployment Readiness: ≥98% of total population trained3.

Meets & Exceeds Many Contract Requirements:

Deployment Readiness: 100% of total population trained3.

REMEDY: Provide remediation training.

PCO to negotiate "consideration" due to mission impact.

REMEDY: Provide remediation training at no additional cost.

Patient safety issue(s) occur OR less than 80% of ‘Severity 1’ (system-down) incidents are resolved during the Post Deployment support period.

Does Not Meet Some Contract Requirements:

No patient safety issue(s). 80% - 89% of ‘Severity 1’ (system-down) incidents are resolved during the Post Deployment support period.

Meets Contract Requirements:

No patient safety issue(s). 90% of ‘Severity 1’ (system-down) incidents are resolved during the Post Deployment support period.

Meets & Exceeds Some Contract Requirements:

No patient safety issue(s). >95% of ‘Severity 1’ (system-down) incidents are resolved during the Post Deployment support period.

Meets & Exceeds Many Contract Requirements:

No patient safety issue(s). >98% of ‘Severity 1’ (system-down) incidents are resolved during the Post Deployment support period.

The Transition-Out Plan is rejected by the Government OR the Transition-Out Plan is submitted late (<54 days prior to the end of the task order).

Does Not Meet Some Contract Requirements:

The Transition-Out Plan is rejected by the Government OR the Transition-Out Plan is submitted late (54-60 days prior to the end of the task order).

Meets Contract Requirements:

The Transition-Out Plan is accepted by the Government. All required documentation, credentials, and system artifacts are successfully transferred to the Government sustainment team 60 days prior to the end of the task order.

The Transition-Out Plan is accepted by the Government. All required documentation, credentials, and system artifacts are successfully transferred to the Government sustainment team 62 days prior to the end of the task order.