QASP.docx

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

1. Contract or Task Order Title (Add contract/task order number at award): Business Application Mapping Solution

2. Work Requirements:

· Task 1 - Provide Software Licenses and Maintenance Support

· Task 2 - Provide Technical Support

· Task 3 - Implementation of Business Application Mapping Solution

· Task 4 - Training

3. Primary Method of Surveillance:

There will be 100% inspection for all Tasks, except for subtasks as delineated below:

- Subtask 6.2.5 to Task 2 requires 50% inspection

- Subtasks 6.3.4, 6.3.5, 6.3.6, 6.3.7 and 6.3.8 to Task 3 require weekly random sampling

Acceptable surveillance methods include:

· 100 Percent Inspection. This is usually only the most appropriate method for infrequent tasks or tasks with stringent performance requirements, e.g., where safety or health is a concern. With this method, performance is inspected/evaluated at each occurrence. One hundred percent inspection is too expensive to be used in most cases.

· Random Sampling. This is usually the most appropriate method for recurring tasks. 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. Computer programs may be available to assist in establishing sampling procedures.

· Periodic Inspection: These services are monitored weekly, monthly, quarterly, semiannually, annually, etc. Periodic types of activities are perfect for periodic inspection because not only are they infrequent, but there is normally a predetermined, specified time frame within which the tasks must be accomplished. Therefore, you know exactly when to conduct the evaluations. Periodic inspections automatically become 100 percent evaluations or "100 percent checks." Inspections should be divided and scheduled by frequency: annual, semiannual, quarterly, monthly, weekly and as required. Sometimes services are required for which the time or frequency cannot be predicted, such as accident investigations, one-time special tasking by higher headquarters, etc. These would be labeled "as required inspections." Others are known and predictable such as the quarterly status report or the monthly travel report currently included in some DISA service contracts.

· Customer Input. Although usually not a primary method, this is a valuable supplement to more systematic methods. For example, in a case where random sampling indicates unsatisfactory service, customer complaints can be used as substantiating evidence. In certain situations where customers can be relied upon to complain consistently when the quality of performance is poor, e.g., dining facilities, building services, customer surveys and customer complaints may be a primary surveillance method, and customer satisfaction an appropriate performance standard. In all cases, complaints should be documented, preferably on a standard form.

4. Scope of Performance:

The scope of the application discovery effort is to acquire a Commercial Off-The-Shelf (COTS) software or appliance solution that has the capability to discover application and hardware interrelationships across OSI Net-work layers 2-7. The Offeror shall provide a COTS solution meeting all Government technical requirements listed in section 8, along with implementation services, on-site technical support, system documentation and training. The Offeror will support on-site installation, configuration, integration, testing and STIG remediation for the solution provided in pre-production, as well as the NIPR and SIPR environments. The implementation scope is to ensure the solution is fully operational in all three required networks. The design, install, and configuration of the enterprise solution are complete at the end of implement and all required interfaces are built and functional. Technical services support includes the Offeror conducting discoveries and completing service maps for a portion of DISA services with the guidance of government staff. The list of applications/services in section 5.1 may be deployed on any combination of test, NIPR and/or SIPR networks. The Offeror will also deliver installation, configuration, interface, training, administrative and user guide documentation for the DISA solution. The Offeror will deliver test documentation, and test procedures.

Overall, the Offeror shall provide implementation support to include engineering, system architecture, security posture, configuration, training and integration development for the solution. The Offeror will deploy their solution within DISA and produce accurate service maps and views for the pre-defined set of DISA services described in section 5.1. The integration efforts include integration with the DISA Enterprise ITSM instance. The vendor is required to propose their recommended method for this integration in their response.

DISA requires non-consecutive days for all installation support. Installation support will be required for the pre-production environment in Montgomery, AL or Oklahoma City, OK as well as a NIPRNet production environment, and a SIPRNet production environment located in Montgomery, AL or Oklahoma City, OK. Contractor staff may reside at any of the following locations during the implementation phase Denver, CO; Montgomery, AL or Oklahoma City. On-site offeror support is only required during the implementation phase. No follow-on technical services support is required.

5. Performance Standards:

Deliverables –

· Joint Project Management Plan

· Project Schedule

100% inspection

Deliverable – Solution Requirements Specification

100% inspection

Deliverables –

· Solution Design Specification (SDS)

· Configuration Design Document

· SDS Deployment Plan

· Initial Test Plan

100% inspection

Deliverables –

· Security Application Review

· Use Cases

· Revised Test Plan

100% inspection

Deliverable – Test Report

100% inspection

Deliverables –

· Installation Guide

· Customized User and Administrator Manual

100% inspection

Deliverable – Checklist of Tasks Completed

100% inspection

Deliverables –

· Final solution Documents including Solution Design Specification (SDS)

· Test Report

· Configuration Design Document

· Customized User and Administration Manual

100% inspection

Deliverable – Project Closure Meeting and project sign-off

100% inspection

Deliverables –

· Training Plan

· Training Curriculum

· Training Manuals/Documents

100% inspection

6. Acceptable Quality Level (AQL):

The AQL for this project is 95% due to the critical system administration triage and troubleshooting support provided by application mapping.

7. Evaluation Method:

The Contracting Officer’s Representative (COR) will document the time of verbal notification to the contractor. The COR will document the official time and date of notification on the Maintenance Call Record. The COR will review self-diagnostic systems logs, conduct a comparison with actual maintenance performance and otherwise verify and validate contractor performance. The contractor shall enter in the record the official time the system is restored to full operational status. The COR will confirm the date and time of problem resolution in the record.

8. Incentives (Positive and/or Negative):

There are no incentives for execution of a firm fixed price CLIN.

No invoice will be accepted in WAWF unless:

· Invoiced per stage after deliverable acceptance. The invoices are uploaded to WAWF noting the specific CLIN.

· Invoiced per trip after submitting travel receipts to the COR and resolving discrepancies IAW JFTR. A travel estimation approval must be submitted at least 7 days prior to trip and approved or travel will not be accepted.

· The vendor will invoice at the conclusion of each phase. The vendor shall invoice after each use of the subject CLIN.

Enclosure 6, QASP Page 1 of 1 Pages 09Jan2012/Version 1.2

Enclosure 6, QASP Page 5 of 5 Pages 09Jan2012/Version 1.2