DHQCAP15MP60007_CMMS_QASP.docx

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

1. Contract or Task Order Title: Computerized Maintenance Management Software (CMMS) Solution

2. Work Requirements:

· Task Area 1 – Software

· Task Area 2 – Technical Support

· Task Area 3 – Implementation of the CMMS Solution

· Task Area 4 – Operations Support

· Task Area 5 – Option Year Software Support

· Task Area 6 – Optional on-site data collection for Stuttgart-Vaihingen, Germany for the CMMS Solution

· Task Area 7 – Optional on-site data collection for Bahrain for the CMMS Solution

3. Primary Method of Surveillance: Random sampling, training surveys, and 100% inspection of deliverable products and services as specified below.

4. Scope of Performance: The scope of this requirement is to provide a COTS solution meeting all Government technical requirements in the Performance Work Statement (PWS) which includes software licenses, implementation services, onsite technical support, system documentation, training, and software/solution maintenance. The contractor shall provide implementation support to include engineering, system architecture, security posture, configuration, implementation, training, data migration/data collection, and integration development for the solution. The contractor shall deploy a fully functional and accredited CMMS environment in Montgomery, AL and Oklahoma City, OK. DISA personnel will work side-by-side with vendor personnel during the system implementation effort, so that DISA personnel are capable of supporting/sustaining all of the infrastructure identified in the PWS for additional service environments at the DISA Defense Enterprise Computing Centers (DECCs) with minimal support from the contractor.

5. Performance Standards/Acceptable Quality Level:

Task 3 Implementation of CMMS Solution (PWS para 6.3)

Deliverables –

· Weekly Activity Report

· Monthly Status Report

Subtask 1 - Stage 1 - Project Setup and Initiation (PWS para 6.3.1)

Deliverables –

· TIM Minutes

· Approved Draft Project Management Plan

· Approved Draft Engineering/Implementation Plan

· Solution Requirements Document

Subtask 2 - Stage 2 – Solution Requirements Definition (PWS para 6.3.2)

Deliverables

· Solution Requirements Specification

· Final Project Management Plan

· Final Engineering/Implementation Plan

· Test and Integration Plan

Subtask 3 - Stage 3 – Solution Install, Configuration, and STIG (PWS para 6.3.3)

Deliverables –

· Installation Guide

· Draft Configuration Design Document

· PO&AM Documentation

Subtask 4 - Stage 4 – Production Deployment and Integration (PWS para 6.3.4)

Deliverables –

· Final Engineering Solution Design Document

· Final Configuration Design Document

· Knowledge Transfer Activity Document

Subtask 5 - Stage 5 – Testing and Quality Assurance (PWS para 6.3.5)

Deliverable

· Testing and Quality Assurance Report

Subtask 6 - Stage 6 – Configuration Documentation and Backup (PWS para 6.3.6)

Deliverables –

· Systems Configuration Documentation

· Backup Strategy Documentations

Subtask 7 - Stage 7 – Implementation and Handoff (PWS para 6.3.7)

Deliverables

· Finalize Project Documentation

· Implementation Sign-off Letter

Task 4 – Operations Support (PWS para 6.4)

Subtask 1 – Classroom training

Subtask 2 – Training Materials

Task 5 - Option Year Software Support (PWS para 6.5)

Task 6 – Optional on-site data collection for Stuttgart-Vaihingen, Germany (PWS para 6.6)

Task 7 – Optional on-site data collection for Bahrain (PWS para 6.7)

6. Mandatory or regulatory compliance items: The contractor will provide initial proof of compliance with regulatory and compliance items contained in the contract. The Contracting Officer’s Representative (COR) and the contracting officer (KO) will evaluate the initial submission. The COR and KO will conduct ad hoc reviews of the contractor’s compliance throughout the remainder of the contract.

7. Evaluation Method: The COR will track the response to the requirements of inspected tasks, conduct a comparison with actual maintenance performance, and otherwise verify and validate contractor performance. Service desk ticket logs and automated reports generated from the software will be used as documentation and compared to the AQL specific to the task.

8. Incentives (Positive and/or Negative): All minimum standards will be met. Any negative performance will be officially documenting the Contractor Performance Assessment Reporting System (CPARS). The incentive is established by using a FFP CLIN for the conclusion of each phase.

Enclosure 6, Page 1 of 4 Pages 17Jul2013/Version 2