RFP Attach 10 - QASP_v5 14 Sep 12 50 hours.docx
DOCX document 32 KB Posted
- Attached to
- DREN III
- Solicitation number
- HC1013-11-R-0100
- Issued by
-
Defense Information Systems Agency
About this file
Attach 10 - QASP
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP Attach 11 Section L - Instructions to Offerors 03 Jan 2011.doc | DOC document | |
| RFP Attach 3 - DD254.docm | DOCM document | |
| RFP 03 Jan 2011.doc | DOC document | |
| RFP Attach 12 Section M - Evaluation Criteria 03 Jan 11.doc | DOC document | |
| RFP Attach 4 - Cross Ref Matrix.doc | DOC document | |
| RFP Attach 5 - Performance Information Sheet.doc | DOC document | |
| RFP Attach 9 - Request for Clarification Sample.xls | XLS spreadsheet | |
| RFP Attach 2 - PWS With Attachments 1 Dec 2010.docx | DOCX document | |
| RFP Attach 8 - PP Client Auth.doc | DOC document | |
| RFP Attach 7 - PP Consent Letter.doc | DOC document |
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
QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)
1. Defense Research Engineering Network (DREN III) Contract
2. Work Requirements:
| · Task 1 | Enterprise Management Controls. |
| · Task 2 | Implementation and Transition. |
| · Task 3 | Implementation and Transition Actions. |
· Task 4 - Install, Modify, Terminate, and Restore SDPs.
· Task 5 - Install, Modify, Terminate, and Restore Gateway Functions.
· Task 6 - Disaster Recovery and Contingency.
· Task 7 - Data Transfer Requirements.
· Task 8 - SDP Characteristics.
· Task 9 - SDP Functional Requirements.
· Task 10 - Contractor Verification of Services.
· Task 11 - Local Connectivity from SDP Sites to Secondary Sites.
· Task 12 - Ethernet and VLAN Services.
· Task 13 - Internet Protocol Service.
· Task 14 - Optical Services.
· Task 15 - Evolution of Existing Services.
· Task 16 - Contractor Simulation Environments and Test Labs.
· Task 17 - Network Management.
· Task 18 - Performance Management.
· Task 19 - Configuration Management.
· Task 20 - Network Management Reporting.
· Task 21 - Network Visibility and Customer Tool Sets.
· Task 22 - Domain Name Service.
· Task 23 - Customer Care.
· Task 24 - Service and Problem Management.
· Task 25 - Customer Care Data and Reports.
· Task 26 - Accounting Management.
· Task 27 - Customer Support and Instructional Services.
· Task 28 - Contract Phase Out.
· Task 29 - Phase Out.
3. Primary Methods of Surveillance:
Random Sampling: For the past ten years, the DOD HPCMP has developed and operated the DREN Active Measurement Program (DAMP). DAMP is a collection of high performance Linux servers running various open source and internally developed tools for measuring network performance. Both real time and long term archival data on latency, packet loss, throughput, and utilization are collected. This data is used by the Government to verify the latency and throughput requirements of the network and has been compared to similar data collected by the network provider to verify accuracy. The DAMPs also serve as performance measurement points for end users, and are vital to the identification and debugging of network performance problems.
4. Scope of Performance:
The contractor shall provide all labor, management, supervision, supplies, materials, equipment, and tools, not otherwise provided as Government furnished property (GFP) to perform the non-personal services required to acquire state of the art Wide Area Networking (WAN) services to support the Department of Defense (DoD) Defense Research Engineering Network (DREN) High Performance Computing Modernization Program (HPCMP). Current DREN networking capability is being provided under the DREN telecommunications services contract administered by the Defense Information Technology Contracting Organization (DITCO). This procurement will enable continuation of the DREN network capability under a follow-on contract.
SERVICE LOCATIONS AND DUTY HOURS. The contractor shall provide WAN services at locations specified in Attachment B of the Performance Work Statement on a 24 hour seven (7) day a week basis. Other locations may be specified in Task Orders as necessary.
5. Performance Standards:
| Performance Standard |
| Acceptable Quality Level |
| Method of Surveillance |
| Deliverable |
6.1.4 Subtask 4.
Progress Reporting
| Performance is based on the effectiveness of transition and progress report items. Issues are resolved in a satisfactory and timely manner. |
| Routine review of reports to verify items are tracked and resolved. Review Quarterly Progress Reports. |
| 1 |
6.1.5 Subtask 5.
Support for the DREN Configuration Control Board (CCB)
| CCB meetings will be conducted. All agenda items are tracked weekly by the Contractor and resolved on a satisfactory basis in a timely manner. Action items that are not resolved will be escalated. |
| Routine review of weekly meeting minutes to verify that agenda items are tracked and resolved as appropriate. Review Weekly CCB minutes. |
| 2 |
| 6.1.6 Subtask 6. DREN Technical Advisory Panel |
| Performance occurs with the planning and execution of the DREN TAP meeting and successful completion of assigned tasks. |
| Review of DREN TAP meeting agenda minutes. |
| 3 |
6.1.7 Subtask 7.
Operational and Management reviews
| Actions items are tracked quarterly and resolved in a satisfactory and timely manner. |
| Routine review of quarterly meeting minutes to verify that agenda items are tracked and resolved. Review Project Management Review. |
| 4 |
6.1.8 Subtask 8.
Annual Planning and Design Review
| Performance occurs with adequate planning for technology enhancements, network trends and equipment refresh. |
| Review of Annual Planning and Design Review. |
| 5 |
6.1.9 Subtask 9.
Annual DREN Networking and Security Conference
| Performance occurs with the planning and execution of the annual DREN conference. |
| Review of Annual DREN Networkers Conference. |
| 6 |
6.2 Task 2
Transition
| Plans are accepted on-time with only minor revisions required. |
| Review of Updated Draft IPC Plan, Comprehensive Implementation and Transition Plan Final Comprehensive Implementation and Transition Plan, Draft Master SDP Plan and Final Master SDP Plan. |
| 7,8,10, 11, 12, 13 |
| Task 6.3 Task 3 Implementation and Transition Actions |
| Performance is based on the successful execution of the IPC Demonstration. |
| Review of IPC Demonstration Report, SDP Site Surveys, and Individual SDP Reports. |
| 9 , 14, 15 |
| 6.3.3 Subtask 3. Transition Review |
| Performance is based on the effectiveness of transition. |
| Review of monthly reports and weekly meeting minutes. |
| 1,2 |
| 6.4.1 Subtask 1. Individual SDP Reports |
| As-built drawings accurately reflect the actual configuration of the installed SDP. All variations from the Master SDP Plan are identified. Acceptance test report includes all pertinent data regarding test results. |
| Review of individual SDP Reports. |
| 15 |
6.4.2 Subtask 2.
Acceptance Test Plan.
| Acceptance test is developed and executed with problems resolved in a satisfactory manner. |
| Review of Acceptance Test Plan component of the CITP and Master SDP Plan; Review of Individual SDP Reports. |
| 10, 11,12, 13, 15 |
6.4.3 Subtask 3.
SDP Modification.
| Reports are delivered on-time and executed with problems resolved in a satisfactory manner. |
| Review of proposed modifications |
| 14, 15 |
6.4.5 Subtask 5.
Termination/ Restoration
| Reports are delivered on-time and executed with problems resolved in a satisfactory manner. |
| Review of proposed actions. |
| 14, 15 |
6.5 Task 5.
Install, Modify, Terminate, and Restore Gateway Functions
| Performance based on effectiveness of network peers and gateway services. |
| Routine inspection of deliverable products and services. |
| N/A |
6.6 Task 6.
Disaster Recovery and Contingency
| Performance based on continuity of service delivery. |
| Routine inspection of deliverable products and services. |
| N/A |
| 6.7 Task 7. Data Transfer Services |
| Performance based on the quality of services delivered. |
| Routine inspection of deliverable products and services. |
| N/A |
6.8 Task 8.
SDP Characteristics
| SDP Data transfer rates for peak and sustained rates are defined in PWS Table 6.8.3a |
| Routine performance measurement and validation as described in Subtask 6. 8.1. |
| N/A |
6.9 Task 9.SDP Functional Requirements
6.9.1 Subtask 1. SDP and Service Availability Requirements
| SDP and Service Availability Requirements are defined in PWS Subtask 6.9.1. Each active SDP shall experience no more than 30 minutes of outage per month. |
| Routine method for performance evaluation as described in Task 18 will be evaluated based on routine review of network availability. Billing credits will be applied for outages exceeding limits described in Table 6.9.1a. |
| 16 |
| 6.9.2 Subtask 2. Network Performance Packet Loss. |
| The loss of IP packets submitted to the network shall not exceed 0.1% at any time. |
| Routine performance evaluation based on review of packet loss data. |
| 17 |
| 6.9.3 Network Performance: Latency. |
| Maximum roundtrip time in milliseconds (latency) for traffic over similar services deployed at two SDPs shall not exceed (.02 * Inter-SDP distance in kilometers) + 20. |
| Routine performance evaluation based on review of IP Latency data. At a minimum to consist of ICMP ping messages generated and measured at all networked SDPs once per minute, 24 hours per day year round and report results. |
| 18 |
| 6.9.4 Subtask 4. Network Performance Availability |
| Network Availability Requirements are defined in Subtask 6.9.4. The aggregate up time of all SDPs shall be such that Network Availability meets a minimum of 0.999 (99.9%) for each calendar month. |
| Routine method for performance evaluation as described in Task 6.18 will be evaluated based on routine review of network availability. Billing credits will be applied for total outages exceeding limits described in Table 6.9.4a. |
| 16 |
| 6.10 Task 10. Contractor Verification of Services |
| Contractor services are successfully delivered and demonstrated to operate as designed. |
| Review Individual SDP Report, Aggregate SDP Test Plan and Aggregate SDP Report. |
| 15, 19, 20 |
| 6.12 Task 12. Ethernet and VLAN Services |
| Services conform to requirements identified in the PWS. |
| Routine inspection of deliverable products and services. |
| N/A |
| 6.13 Task 13. Internet Protocol Service |
| Services conform to requirements identified in PWS. |
| Routine inspection of deliverable products and services. |
| N/A |
| 6.14 Task 14. Optical Services |
| Services conform to requirements identified in PWS. |
| Routine inspection of deliverable products and services. |
| N/A |
6.15 Task 15. Evolution of Existing Services
| Contractor services evolve to incorporate commercially available new enhancements over the life of the contract. |
| Review of Technology Insertion Proposals. |
| N/A |
6.17 Task 17. Network Management
| The network is monitored for fault management 24 hours a day, 7 days a week (7x24). Problems are identified, isolated and resolved within a timely manner. |
| Routine review of trouble tickets. Review of Performance Management Data and Network Management Reporting data. |
21,22
6.23 Task 23. Customer Care
| Service requests and Delivery Orders are completed accurately and in a timely manner (see Table 6.23.2a and Table 6.23.2b). |
| Routine review of Delivery Order tracking data and Service Provisioning Performance Report data. |
| 23, 24 |
| 6.24 Task 24. Service and Problem Management |
| The Help Desk/Networks Operations Center is responsive. Trouble reports are resolved in a satisfactory manner. Response and repair times are identified in Table 6.24.1a. |
| Routine review of Help Desk/Trouble ticket data as described in Task 6.24.1 |
| 25 |
| 6.25 Task 25. Customer Care Data and Reports |
| Problems are resolved in a timely and satisfactory manner (Table 6.25.a) |
| Routine review of Customer Care Problem Resolution Data Reports. |
| 26 |
6.26 Task 26.
Accounting Management
| DREN quality of service, costs and credits are maintained. |
| Routine review of Accounting Management Data. |
| 27 |
6.27 Task 27.
Customer Support and Instructional Services
| Adequate training and online customer support tools are provided. |
| Review of Instructional Services Training and Technical, Telecommunications Support/Engineering Studies and Customer Care Tools. |
| 28, 29, 30 |
6.28 Task 28.
Contract Phase Out
| Adequate planning and documentation is provided for transition. |
| Review of Contract Phase-Out Transition Plan. |
| 31 |
| 6.2.2.3 Element 3. Security. & 12. Security. |
| Adequate documentation, plans and procedures are in place and executed. |
| Routine inspection of deliverables. |
| 10, 11, 32, 33, 34 |
12.10 Certification and Accreditation (C&A) Support
| Security accreditation packages are submitted on time and executed with problems resolved in a satisfactory manner. Packages are maintained/updated when network configuration changes. |
| Periodic review of DIACAP package. |
| 35, 36 |
12.13.4 Security Incident Reporting.
| Monthly security reports submitted in a timely manner. Incidents handled IAW HPC CERT. |
| Routine review of monthly reports. |
| 37, 38, 39 |
12.13.5 Security Vulnerabilities.
| Security vulnerabilities addressed IAW DOD IAVA process, including reporting / mitigation dates. |
| Review of IAVA reports as required. |
| N/A |
12.13.6 Security Audit Reporting.
| Audit records shall be maintained in a manner consistent with PWS 12.13.6. |
| Periodic review of on- and off-line logs. |
| 40 |
12.13.7 Continuity of Operations.
Plans and procedures will be submitted in a timely manner.
| Review of plan and test results as they are generated. |
| 41 |
6. Acceptable Quality Level (AQL):
The AQL for this project is 99.9% due to the critical support provided by DREN operations.
7. Evaluation Method:
The Task Monitor (TM) will document the time of verbal notification to the contractor. The TM will document the official time and date of notification on the Maintenance Call Record. The TM 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 TM will confirm the date and time of problem resolution in the record.
8. Incentives (Positive and/or Negative)
This is a fixed price contract. No positive incentives are applicable to this requirement. Due to the nature of this requirement, performance standards are sufficiently high that positive incentives are impractical.
Penalties will take the form of held payment of IPC Phase 1 sites if the Government determines phase 1 initial performance test and associated test reports to be unacceptable .
Penalties in the form of outage credits will apply to the monthly recurring costs if a Service Delivery Point does not meet availability requirements or overall network availability falls below 0.999 (99.9%). The methodologies used to apply these credits are detailed in PWS sub-sections 6.9.1.3 and 6.9.4.2.
Attachment 10, QASP Page 1 of 7 Pages
Attachment 10, QASP Page 2 of 7 Pages
File details come from the government source that posted it. Updated .