QASP3609 .doc
DOC document 49 KB Posted
- Solicitation number
- TIRNO-09-R-00017
About this file
Attachment J-5
View the file
Other files
| File | Type | Posted |
|---|---|---|
| TIRNO09R00017-A0004 1 .rtf | RTF text file | |
| CLARIFICATION QUESTION4.doc | DOC document | |
| Sect_508_sect-j-eval.xls | XLS spreadsheet | |
| Q A61609.doc | DOC document | |
| TIRNO09R00017-A0003 1 .rtf | RTF text file | |
| TIRNO09R00017-A0002 1 1 .rtf | RTF text file | |
| CLARIFICATION QUESTIONS | — | |
| TIRNO09R00017-A0001 1 .rtf | RTF text file | |
| vpat.doc | DOC document | |
| SCPMaR Technical Evaluation Matrix v1 5.doc | DOC document | |
| SCPMaR Requirements Checklist v1 5.doc | DOC document | |
| Copy of sect_508_sect-j-eval.xls | XLS spreadsheet | |
| SCPMaR_BSRR_v3 2 4.doc | DOC document | |
| SCPMaR CONOPS_v1 4 3.doc | DOC document | |
| TIRNO09R00017v11.rtf | RTF text file | |
| IRM 10.8.20.pdf |
Show all 16
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
Attachment J-5
QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)
1. Overview
This IRS Quality Assurance Surveillance Plan (QASP) provides the procedures and guidelines that will be used in evaluating technical performance of the Contractor for software maintenance and support services in a performance-based Performance Work Statement. The IRS’ QASP is not part of the contract, but is provided to the Contractor solely as information. A copy of this plan is furnished to the Contractor in the solicitation package and with the contract so the Contractor can propose the methods that the IRS should use in evaluating performance on the contract and to address any concerns that the Contractor may have prior to initiation work .
2. Purpose
The purpose of the QASP is to:
(a) Define the role and responsibilities of participating IRS officials;
(b) Define the types of work to be performed with required end results;
(c) Describe the evaluation methods that will be employed by the IRS in assessing the Contractor’s performance, and
(d) Describe the process of performance assessment documentation.
3. Authority Authority for issuance of this QASP is provided under Solicitation Section E – Inspection and Acceptance, which provides for inspections and acceptance of the services and documentation called for in the contract to be accomplished by the Contracting Officer or duly authorized representative.
4. Scope To fully understand the roles and the responsibilities of the parties, it is important to first define the distinction in terminology between the Contractor’s approach to quality control and the QASP.
The QASP on the other hand, is put in place to provide IRS surveillance oversight of the Contractor’s quality control efforts to assure that they are timely, effective and are delivering the results specified in the contract. The QASP is not a part of the contract nor is it intended to duplicate the contractor’s quality controls. The IRS will provide the contractor an information copy of the QASP as an attachment to the solicitation to support the contractor’s efforts in developing quality controls that will interrelate with the IRS’s QASP.
INSPECTION
Inspection shall be at the place of performance and delivery as stated herein.
GENERAL ACCEPTANCE CRITERIA
The general quality measures as set forth below will be applied to each Deliverable received from the Contractor under this PWS. Any perceived conflict between quality measures referenced in Section E of solicitation and the quality measures listed below should be immediately reported to the Contracting Officer’s Technical Representative.
Accuracy ‑ Deliverables shall be accurate in presentation, technical content, and adherence to accepted elements of style.
Clarity ‑ Deliverables shall be clear and concise; engineering terms shall be used, as appropriate. All diagrams shall be easy to understand and relevant to the supporting narrative.
Specifications Validity ‑ All Deliverables must satisfy the requirements of the Government as specified herein.
File Editing ‑ All text and diagrammatic files shall be editable by the Government.
Format ‑ Deliverables shall be submitted in hard copy (where applicable) and in media defined in the PWS. The Deliverable format may change from Sub-task to Sub-task. Hardcopy formats shall follow Treasury/IRS Directives and shall be consistent with other similar efforts.
Timeliness ‑ Deliverables shall be submitted on or before the due date specified in the Schedule of Deliverables Section of this PWS or submitted in accordance with a later scheduled date established by the Contracting Officer.
SPECIFIC DELIVERABLE ACCEPTANCE CRITERIA
| Deliverable No. |
| Specific Deliverable Acceptance Criteria |
| 1 |
| Orientation Briefing – demonstrate a complete understanding of the work to be completed under this PWS. |
| 2 |
| Input to ELC Documentation – delivered documents must accurately reflect deployed solution. |
| 3 |
| Solution Design Documentation - delivered document must include recommended architecture; HW/SW specifications; deployed infrastructure; a secure configuration manager configuration, including database configuration, infrastructure, user permissions, and console options; server and workstation test plans; risk management and risk mitigation processes. |
| 4 |
| Project Schedule - a project schedule that adheres to the approved deployment strategy and that deploys the SCPMaR solution across the IRS enterprise by December 31, 2010. |
| 5 |
| Security Posture Assessment Processes - delivered process and workflows must include: |
· Assessment processes and workflows for security configuration, patch-level management and enumeration of vulnerabilities
· automated and on-demand assessments; documented process must accurately reflect the automated and on-demand security assessment process as directed by IRS's Security Policy and Procedures team and the SCPMaR PO.
| 6 |
| Security Posture Reporting Processes - delivered processes and workflows must produce security posture reports and dashboards as defined by IRS's Security Policy and Procedures team and the SCPMaR PO. |
| 7 |
| Security Configuration and Deviation Management Processes - delivered processes and workflows must align with IRS's security configuration and deviation management and change control processes. |
| 8 |
| Risk Management Processes - delivered solution and process workflow must adhere to IRS's enterprise risk management processes. |
| 9 |
| Integrated Security Compliance Posture Reports – delivered reports must correlate data ingested from existing IRS tools and, at a minimum, should contain the following IRS-defined security posture metrics: 1) Degree of compliance to IRS-defined security configuration, 2) Degree of compliance to IRS-defined patch-level, 3) Enumeration of IRS identified security vulnerabilities, for an IRS-defined computing asset (or group of computing assts) as defined in the BSRR. Delivered reports must accurately reflect the IRS’s enterprise security compliance posture while adhering to FISMA reporting requirements as well as IRS specific reporting requirements. |
| 10 |
| Security Compliance Posture Monitoring and Reporting (SCPMaR) System – delivered system must provide the capability to support prior listed deliverables (5 - 9) and meet requirements as defined in the BSRR. |
| 11 |
| SCPMaR System Training Guides - delivered training guides must accurately reflect solution deployed at the IRS and provide sufficient instructions by role and responsibility to the users on its use. Delivered documents and training must include: |
· User training guide
· Administrator training guide
· Instructor PowerPoint presentations
· User Training sessions
| 12 |
| Standard Operating Procedures (SOP) Document – delivered SOP must include standard operating procedures for the SCPMaR system including: |
· user roles and responsibilities
· operations and maintenance
· change control procedures
· disaster recovery procedures
5. IRS Resources
The following definitions for IRS resources are applicable to this plan:
Contracting Officer (CO) – A person duly appointed with the authority to enter into, administer, or terminate contracts and make related determinations and findings on behalf of the IRS.
Contracting Officer’s Technical Representative (COTR) – An individual(s) designated in writing by the CO to act as their authorized representative to assist in administering a contract. The source and authority for a COTR is the Contracting Officer. COTR limitations are contained in the written letter of designation. The COTR will, in addition to providing documentation to the Contracting Officer, maintain a complete Quality Assurance File. The file will contain copies of all reports, evaluations, recommendations and any actions related to the IRSs performance of the quality assurance function. All such records will be retained for the life of this contract. The COTR shall forward these records to the Contracting Officer at termination or completion of the contract.
Government Task Manager (GTM) – An individual(s) appointed by an IRS site of contract performance to provide on-site support and assistance to the COTR.
6. Methods of Quality Assurance Surveillance
The contractor shall propose methods of Quality Assurance Surveillance to which their performance under this contract will be monitored.
File details come from the government source that posted it. Updated .