3__QASP_DCS_IDIQ.docx
DOCX document 43 KB Posted
- Attached to
- Defense CollaborationServices (DCS)
- Solicitation number
- HC1047-19-R-4005
- Issued by
-
Defense Information Systems Agency
About this file
This document contains a Quality Assurance Surveillance Plan (QASP) and related federal contract opportunity for Defense Collaboration Services (DCS). The QASP provides a method to evaluate contractor performance for developmental and operational support of the DCS program, ensuring roles and responsibilities for product development and sustainment are clearly delineated. Performance will be monitored through document reviews, deliverable reviews, and weekly inspections. The acceptable quality levels and inspection methodology are defined for each performance standard. Unacceptable performance will be addressed through corrective action reports. The single-award IDIQ has a ceiling of $49.5 million over five years and the initial task order provides foundation and maintenance support for the DCS program. Engineering, software development, and integration support are required to maintain a file repository system and ensure efficient large file transfers. Expertise in DoD infrastructure, cloud services, and cybersecurity is needed to manage the program and maintain accreditation.
QASP DCS IDIQ
View the file
Other files
Show all 23
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. Contract or Task Order Title (Defense Collaboration Services (DCS) Developmental and Operational Sport
2. Purpose:
This QASP provides a systematic method to evaluate performance for the stated contract. This QASP explains the following:
· What will be monitored?
· How monitoring will take place.
· Who will conduct the monitoring?
· How monitoring efforts and results will be documented.
This QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. In addition, the QASP should recognize that unforeseen and uncontrollable situations may occur.
This QASP is a “living document” and the Government may review and revise it on a regular basis. Updates shall ensure that the QASP remains a valid, useful, and enforceable document. Copies of the original QASP and revisions shall be provided to the contractor and Government officials implementing surveillance activities.
3. Roles and Responsibilities:
The following personnel shall oversee and coordinate surveillance activities.
Program/Project Manager (PM) – The PM provides program oversight and supports the COR’s performance assessment activities.
Contracting Officer (KO) – The KO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and shall safeguard the interests of the United States in the contractual relationship. The KO shall also ensure that the contractor receives impartial, fair, and equitable treatment under this contract. Determine the final assessment of the contractor’s performance.
Contracting Officer’s Representative (COR) – The COR is responsible for providing continuous technical oversight of the contractor’s performance. The COR uses the QASP to conduct the oversight/surveillance process. The COR shall keep a Quality Assurance file that accurately documents the contractor’s actual performance. The purpose is to ensure that the contractor meets the performance standards contained in the contract. The COR is responsible for reporting early identification of performance problems to the KO. The COR is required to provide an annual performance assessment to the KO which will be used in documenting past performance. The QASP is the primary tool for documenting contractor performance. The COR is not empowered to make any contractual commitments or to authorize any contractual change on the Government’s behalf.
Other Key Government Personnel- This may include performance monitors, inspectors, technical experts, workforce service division and center directorate level security personnel, requirements office, or others (i.e. users) who provide information that helps the COR monitor contractor performance.
4. Primary Method of Surveillance
• Each Document Reviewed 6.1
• Each Deliverable Reviewed 6.2
• Weekly Inspections of Documents and Services 6.3 – 6.16
Surveillance Matrix
The Surveillance Matrix (Appendix 1) is the list of performance objectives and standards that must be performed by the contractor. This matrix details the method of surveillance the COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR file.
Performance objectives define the desired outcomes. Performance Standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance. The Government performance surveillance, using this QASP, to determine the quality of the contractor’s performance as it relates to the performance element standards. The AQL performance Standard Table should be used to form the foundation of the COR’s inspection checklist.
5. Performance Standards:
| Task |
| Requirement |
| Acceptable Quality Level (AQL) |
| Method of Surveillance |
6.1
Updates to the contracts Management Plan
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
| Each document will be reviewed. |
6.2
DCS Engineering Support
| Performance occurs with no required re-performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
6.3
DCS Tier 3 Support
| Performance occurs with no required re-performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner. |
| Weekly inspection of deliverable products and services. |
6.3
DCS Tier 3 GTMS/ITSM Processing
Access and review all Tier 3 Incident Tickets and Problem Tickets daily 95% of the time.
Weekly inspection of deliverable products and services.
6.3
| DCS Tier 3 GTMS/ITSM Processing |
| Within one working day, annotate on the GTMS Tier ticket a status update 95% of the time. |
Weekly inspection of deliverable products and services.
6.3
| DCS Tier 3 GTMS/ITSM Processing |
| Ensure all incident tickets in the tier 3 queue have updates every 30 days 95% of the time. |
| Weekly inspection of deliverable products and services. |
| 6.3 |
| DCS Tier 3 GTMS/ITSM Processing |
| Ensure 95% of the monthly incident tickets for Tier 3 are opened and reviewed. |
| Each deliverable will be reviewed. |
| 6.3 |
| DCS Tier 3 GTMS/ITSM Processing |
| Ensure 95% of the monthly incident tickets for Tier 3 are updated |
| Each deliverable will be reviewed. |
| 6.3 |
| DCS Tier 3 GTMS/ITSM Processing |
| Ensure 95% of the monthly incident tickets for Tier 3 are either closed, escalated to Tier 4, or de-escalated to Tier 2 |
| Each deliverable will be reviewed. |
6.4
DCS Training and Service Desk Support
| Performance occurs with no required re-performance or re-work at least 90% of the time. Problems that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
6.5
Enterprise Collaboration Open Services Support (Optional)
| Performance occurs with no required re-performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
6.6
Developmental and Operational Support (Optional)
| Performance occurs with no required re-performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
6.6.1
DCS Developmental Support
Ensure any Plan of Action and Mitigation (POA&M) are resolved within on or before the date of the Government approved POA&M 95% of the time.
Each deliverable will be reviewed.
6.6.1
DCS Developmental Support
Apply full SDLC processes to the development effort 95% of the time.
Each deliverable will be reviewed.
6.6.1
DCS Developmental Support
Apply Capability Maturity Model Integration (CMMI) Level 3 processing to the development effort.
Each deliverable will be reviewed.
6.6.2
DCS Developmental and Operational Support
Ensure modifications to support Information Assurance Vulnerability Management (IAVM) are corrected on or before the designated suspense date 90% of the time.
Each deliverable will be reviewed.
| 6.7 |
| DCS Service Analysis and Situational Awareness Capability |
| Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
6.8
DCS Compliance Test Support (Optional)
| Performance occurs with no required re-performance or re-work at least 80% of the time. Problems that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
| 6.9 |
| Cybersecurity Support (Optional) |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 80% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.10 |
| New Infrastructure Migration and Integration Support |
| Delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 80% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.11 |
| Tech Refresh Integration Support |
| Delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 85% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.12 |
| Customer Requirement Integration Support |
| Delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 85% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.13 |
| Implementation Support |
| Delivered on time at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner |
| Each deliverable will be reviewed. |
| 6.14 |
| Customer Engagement Support |
| Delivered on time at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner |
| Each deliverable will be reviewed. |
| 6.15 |
| Tiered Support |
| Ensure all incident tickets in the tier 1 queue have been resolved or routed to the appropriate team within their priority metric 95% of the time. |
| Each deliverable will be reviewed. |
| 6.15 |
| Tiered Support |
| Ensure 95% of the monthly incident tickets for Tier 2 are updated |
| Each deliverable will be reviewed. |
| 6.15 |
| Tiered Support |
| Ensure 90% of the monthly incident tickets for Tier 2 are either closed, escalated Tier 3 |
| Each deliverable will be reviewed. |
| 6.16 |
| Engineering Design Documentation |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 80% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.16 |
| Software Development and Integration |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 80% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.16 |
| System Documentation |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 95% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.16 |
| Software Documentation |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Performance occurs with no required re-performance or re-work at least 80% of the time. Problems that occur are minor and are resolved in a satisfactory manner Each deliverable will be reviewed.
| 6.16 |
| Software Development / Integration Updates via Software Forge |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
Each deliverable will be reviewed.
| 6.16 |
| Request For Change (RFCs) |
| Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner. |
| Each deliverable will be reviewed. |
| 6.16 |
| Static Code Analysis Reports |
Materials contain required information and are delivered on time at least 95% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.
Each deliverable will be reviewed.
6. Documenting Performance:
Acceptable Performance.
The Government shall document positive performance. A Performance Assessment Report (PAR) template is attached (Appendix 2). Any report may become part of the supporting documentation for fixed price payments, award/incentive fee payments, Contractor Performance Assessment Reporting System (CPARS) entries, or other actions. Government acceptance of services permits the contractor to invoice for the service fee.
Unacceptable performance.
Unacceptable contractor performance can be identified by customer complaints (Appendix 3) or upon schedule surveillance evaluations. When unacceptable performance occurs, the COR shall inform the contractor. This will normally be in writing unless circumstances necessitate verbal communication. The COR shall document the discussion and place it in the COR file and provide a copy to the KO.
When the COR determines formal written communication is required, the COR shall prepare a Corrective Action Report (CAR). The CAR is forwarded to the KO for dissemination to the contractor. A CAR template is attached to this QASP (Appendix 4).
The contractor shall acknowledge receipt of the CAR in writing. The CAR will specify if the contractor is required to prepare a corrective action plan to document how the contractor shall correct the unacceptable performance and avoid a recurrence. The CAR will also state how long after receipt the contractor has to present this corrective action plan to the KO and COR. The Government may withhold payment for services until corrective action is taken. The Government shall review the contractor's corrective action plan to determine acceptability. Upon Government acceptance of the corrected services the contractor will be permitted to invoice for the service fee.
Any CAR may become a part of the supporting documentation for contract payment deductions, fixed fee deductions, award fee nonpayment, CPARS or other actions deemed necessary by the KO.
7. 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 and will conduct ad hoc reviews of the contractor's compliance throughout the remainder of the contract. The contractor will monitor compliance as required by FAR 52.222-50, Combating Trafficking in Persons, and report any issues to the KO.
8. Acceptable Quality Level (AQL):
The AQL’s for this project are listed in Section 5 of this QASP under the third column of the table “Acceptable Quality Levels”. The AQL’s are represented in percentages as well as meets/does not meet timeliness criteria, quality, and levels of reliability.
9. Evaluation Method:
10. Performance Rating
The COR will evaluate deliverables IAW the Performance Standards found in Section 5 of this QASP under the fourth column of the table “Method of Surveillance”. The COR will check that deliverables are turned in on time and will rely on Subject Matter Expert (SME) to verify tests and inspections. All deliverables will be evaluated for depth and breadth of technical discussion and how they meet the requirements of the PWS.
In evaluating the quality of contractor’s performance, the following performance ratings may be used (same as CPAR ratings).
Performance Rating Criteria
| Exceptional |
| Performance meets contractual requirements and exceeds many to the government’s benefits. The contractual performance of the element or sub-element being assessed was accomplished with no problems and contractor actions were highly effective. |
| Very Good |
| Performance meets contractual requirements and exceeds some to the government benefits. The contractual performance was accomplished with few minor problems for which corrective actions taken by the contractor were effective. |
| Satisfactory |
| Performance meets contractual requirements. The contractual performance contains some minor problems for which corrective actions taken by the contractor were satisfactory. |
| Marginal |
| Performance does not meet some contractual requirements. The contractual performance reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear marginally effective or were not fully implemented. |
| Unsatisfactory |
| Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance contains serious problem(s) for which the contractor’s corrective actions appear or were ineffective. |
Appendix 1 - Surveillance Matrix
Performance Standards Acceptable Quality Levels Methods of Calculation
| Surveillance |
| Results/Ratings |
Information Technology (IT) Service Integration and Delivery Performance Management
High level of (xyz) satisfaction with Contractor delivery management of IT Services (includes the Service Desk services and the SITEC).
Target Criteria:
90% of all survey respondents are Satisfied, More Than Satisfied, or very Satisfied
Minimum Acceptable:
> 85% of all survey respondents are Satisfied, More Than Satisfied, or Very Satisfied with Contractor delivery management of all SITEC IT Services Calculation:
The number of users who were Satisfied, More Than Satisfied, or Very Satisfied divided by the total number of completed surveys returned.
At least XX(insert number) Government personnel must complete and return surveys for the results to have at least a 90% confidence factor with a 5% error rate.
Measurement Interval – The Measurement Interval is three (3) months for the first year and then every six (6) months thereafter.
Measurement Period – The Measurement Period begins at 00:01 on the first day of the month and ends at 24:00on the last day of the month.
Source of Measurement Data – Data will be collected from management surveys containing satisfaction criteria specified by (xyz) that are either developed internally by (xyz) personnel or by a (xyz) selected impartial 3rd party.
Method of Surveillance – Customer feedback. The Government will issue customer satisfaction surveys to designated Government SITEC management representatives from (xyz) (Contractors cannot participate), , and survey responses will be tabulated to determine overall satisfaction with Contractor delivery management of IT Services using a five (5) category scale. The scale is: Dissatisfied, Less than Satisfied, Satisfied, More than Satisfied, Very Satisfied.
Timing of Measurement – Measurements are taken within five (5) days of the end of the Measurement Period.
Reporting Frequency: - Reporting to commence upon Contract Award and continue throughout the Period of Performance.
Monthly reporting of Service Level Agreement (SLA) and / or QASP attainment to periods survey. Quarterly survey reporting from (xyz) during the first year, semi-annual thereafter.
(Exceptional Very Good Satisfactory Marginal Unsatisfactory)
(A rollup of assessment of the Surveillance Inspection Results to develop an overall rating for this objective)
PERFORMANCE ASSESSMENT REPORT (PAR)
(If more space is needed, use reverse and identify by number)
| 1. CONTRACT/TASK ORDER NUMBER |
| 2. CONTRACTOR |
| 3. TYPE OF SERVICES |
4. QUALITY ASSURANCE PERSONNEL (COR) SIGNATURE AND DATE
| 5. COR PHONE |
| 6. SUSPENSE DATE |
I. PERFORMANCE
7. |_| DEFICIENCY (CHECK ALL BOXES THAT APPLY)
|_| NEW
|_| REPEAT
|_| NO DEFICIENCY NOTED
8. SERVICES SUMMARY or PWS PARAGRAPH ITEM REVIEWED
| 9. BRIEF DESCRIPTION OF DEFICIENCY (IF DEFICIENCY BOX WAS CHECKED) |
| 10. DETAILED PERFORMANCE ASSESSMENT |
II. CONTRACTOR VALIDATION
11. CONTRACTOR REPRESENTATIVE |_| CONCUR |_| NON-CONCUR
12. CORRECTIVE ACTION ESTIMATED COMPLETION DATE
13. CONTRACTOR REPRESENTATIVE CORRECTIVE ACTION AND PREVENTION OF RECURRENCE OR REASON FOR NON-CONCURRENCE OF COR CITED DEFICIENCY
III. ACTION CORRECTED
14. |_| CONCUR |_| NON-CONCUR COR SIGNATURE AND DATE
15. COR REMARKS (REQUIRED)
6. CONTRACTOR REPRESENTATIVE REMARKS
Appendix 2 – Performance Assessment Report
Appendix 3 – Customer Complaint Record
CUSTOMER COMPLAINT RECORD
DATE/TIME OF COMPLAINT
SOURCE OF COMPLAINT
ORGANIZATION
BUILDING NUMBER
INDIVIDUAL
PHONE NUMBER
NATURE OF COMPLAINT
CONTRACT REFERENCE
VALIDATION
DATE/TIME CONTRACTOR INFORMED OF COMPLAINT
ACTION TAKEN BY CONTRACTOR
RECEIVED/VALIDATED BY
Appendix 4 – Corrective Action Report
CORRECTIVE ACTION REPORT (CAR)
(If more space is needed, use reverse and identify by number)
1. CONTRACTOR
2. CONTRACT NUMBER
3. TYPE OF SERVICES
4. FUNCTIONAL AREA
5. SUSPENSE DATE
6. CONTROL NUMBER
7. DEFICIENCY |_| MAJOR |_| MINOR
FINDING:
FINDING IMPACT:
Please respond with a written corrective action plan that details the corrective action of the cited deficiency, the cause of the deficiency, and actions taken to prevent recurrence by Suspense Date in Block 5. If date was not entered in Block 5, the contractor is not required to provide a response.
8. QUALITY ASSURANCE PERSONNEL (COR)
TYPED NAME AND GRADE
SIGNATURE AND DATE
9. ISSUING AUTHORITY
TYPED NAME AND GRADE
SIGNATURE AND DATE
10. COR RESPONSE TO CONTRACTOR CORRECTIVE ACTION AND ACTION TAKEN TO PREVENT RECURRENCE
11. COR DETERMINATION
|_| ACCEPTED |_| REJECTED
12. CLOSE DATE
Enclosure 6, Page 1 of 2 Pages 17Jul2013/Version 2
Encl 3, QASP 16May19
File details come from the government source that posted it. Updated .