QASP_Matrix_HICS_Tech_Refresh.docx
DOCX document 22 KB Posted
- Attached to
- Hazardous Inventory Control Systems for Windows (HICSWIN) Contractor Support Services Federal contract opportunity
- Solicitation number
- N0018920QQ001
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| N0018920QQ001.pdf | ||
| HICSWIN_-_SSJ_-_R_Redacted.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
QUALITY ASSURANCE SURVEILLANCE PLAN AND MATRIX
HICS Tech Refresh
1.0 PURPOSE
This Quality Assurance Surveillance Plan (QASP) is a Government developed and applied document used to make sure that systematic quality assurance methods are used in the administration of the Performance Based Service Contract (PBSC) standards included in this contract. The intent is to ensure that the Contractor performs in accordance with performance metrics set forth in the contract documents, that the Government receives the quality of services called for in the contract and that the Government only pays for the acceptable level of services received.
2.0 AUTHORITY
Authority for issuance of this QASP is provided under FAR 52.246-4 – Inspection of Services – Fixed Price, which provides for inspections and acceptance of the articles, services, and documentation called for in the contract to be accomplished by the Contracting Officer or their duly authorized representative.
3.0 SCOPE
The Contractor, and not the Government, is responsible for management and quality control actions necessary to meet quality standards set forth by the contract. The QASP is put in place to provide Government 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 Management Plan. The Government may provide the Contractor an information copy of the QASP as an Attachment to the solicitation to support the Contractor’s efforts in developing its plan for maintaining the levels of quality anticipated to be delivered under the terms of the contract.
4.0 RESPONSIBILITIES
The Government resources shall have responsibilities for the implementation of this QASP as follows:
· Contracting Officer – The Contracting Officer ensures performance of all necessary actions for effective contracting, ensures compliance with the terms of the contract and safeguards the interests of the United States in the contractual relationship. It is the Contracting Officer that assures the Contractor receives impartial, fair and equitable treatment under the contract. The Contracting Officer is ultimately responsible for the final determination of the adequacy of the Contractor’s performance.
· Contracting Officer’s Representative (COR) – An individual designated in writing by the Contracting Officer to act as his authorized representative to assist in administering a contract. The source and authority for the COR is the Contracting Officer. COR limitations are contained in the written letter of appointment.
· Technical Point of Contact (TPOC) – An individual that is the program expert and is designated as the technical point of contact. The TPOC works directly with the contractor and provides an assessment of the contractors’ performance back to the COR.
5.0 METHODS OF QA SURVEILLANCE
The below listed methods of surveillance shall be used in the administration of this QASP. The QASP Matrix (attached) describes the methods of surveillance that may be used to monitor the services and deliverables to be provided under the contract.
· Random Monitoring – Random monitoring shall be conducted if and when deemed necessary to ensure compliance with the terms of the contract. The COR will conduct the random monitoring.
· Random Checks/Inspections – Random checks will be conducted to ensure compliance with the terms of the contract. The COR will conduct the random monitoring.
6.0 IDENTIFIED QA SURVEILLANCE ITEMS
The PBSC items that have been identified for surveillance are identified in the Performance Work Statement (PWS).
7.0 DOCUMENTATION
The COR will maintain a complete Quality Assurance Surveillance file. The file shall contain such documents as copies of all receiving reports, evaluations, recommendations, and any other actions related to the Government’s performance of the quality assurance function. All such records will be retained for the life of this contract.
8.0 ANALYSIS OF CONTRACTOR PERFORMANCE
The analysis of contractor performance shall be conducted at the end of each month and serves to provide a summary of the Contractor’s performance to the Contracting Officer and the Contractor. Overall performance is important in determining whether to increase, decrease or maintain the current level of surveillance and/or whether to initiate corrective action to bring the Contractor’s work up to the standards of the specification.
QASP MATRIX
Performance Element
| Performance Requirement |
| Surveillance Method |
| Frequency |
| Acceptable Quality Level |
| Procedures to be taken when performance standards are not met |
| 5.1.1 Research applicable law and security/privacy regulations, standards and policies |
| 100% of law, regulations, standards and policies shall be researched. |
| TA shall review status reports and conduct spot checks. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.2 Refresh code IAW code technical specifications |
| 100% of refreshed code shall be IAW technical specifications. |
| TA shall review code periodically to ensure in line with technical specs. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.3 Conduct regular code analysis to identify any possible issues/deficiencies in the business rules of the module code |
| Report any concerns to the TA within 5 days of identification |
| TA will ensure ctr meets the due date by reviewing status reports. |
| Weekly |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.4 Perform maintenance on the HAZMAT code base |
| Complete existing schedules with no more than 5% variance past the due date, as defined in the Project Plan. |
| Existing schedules will be reviewd by the TA during scheduled weekly status meetings |
| Weekly |
| 95% |
| FAR Clause 52.212.4 |
| 5.1.5 Verify code is compliant with DISA Application STIGS and development. |
| Ctr shall fix/update code until zero Cat I and II Findings are identified. |
| Results of HP Fortify scans will be reviewed during scheduled weekly meetings. |
| Weekly |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.6 Perform end-to-end unit testing |
| Ctr shall develop test plans. |
| TA will review test plans to ensure cover all requirements. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.7 Document and maintain timeliness, completeness and problem id for the development of the HAZMAT effort |
| Ctr shall complete existing schedules with no more than 5% variance past the due date, as defined in the Project Plan. |
| Existing schedules will be reviewed with TA during scheduled weekly status meetings. |
| Weekly |
| 95% |
| FAR Clause 52.212.4 |
| 5.1.8 Document, update and maintain technical specs for programs and interfaces |
| Ctr shall complete existing schedules with no more than 5% variance past the due date, as defined in the Project Plan. |
| Existing schedules will be reviewed with TA during scheduled weekly status meetings. |
| Weekly |
| 95% |
| FAR Clause 52.212.4 |
| 5.1.9 Write test cases, prepare test data and conduct testing. |
| Ctr shall develop test cases and supporting data to verify the successful functioning of all (100%) identified unit reqts and document the results from conducting the test. |
| TA will review test cases to ensure they cover all requirements. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.10 Conducting and documenting the IST |
| Ctr shall conduct IST test cases with supporting data to verify the successful functioning of all (100%) identified unit reqts and document the results from conducting the test. |
| TA will review the IST test tasks to ensure they cover all (100%) requirements. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.11 Provide input and complete tasks in development of training strategy |
| Ctr shall provide training procedures for all (100%) system components they develop. |
| TA will review the procedures for accuracy and completeness. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.12 Provide input and complete tasks in development of data migration strategy |
| Ctr shall supply procedures and solutions to covert production data from currently deployed systems to the system under development by due date assigned by TA. |
| TA will review procedures and test results and ensure due dates are met. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.13 Provide input and complete tasks in development of a data archiving strategy |
| Ctr shall develop data archiving procedures for shipboard and enterprise data by due date assigned by the TA. |
| TA will review procedures and test results and ensure due dates are met. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.14 Provide input and complete tasks in development of data transfer strategy |
| Ctr shall develop data transfer procedures for shipboard and enterprise data by due date assigned by the TA. |
| TA will review procedures and test results and ensure due dates are met. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.15 Coordinate system testing |
| Ctr shall conduct system test cases with supporting data to verify success functioning of all (100%) identified unit reqts and document the results |
| TA will review system test tasks to ensure they cover all (100%) reqts. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.16 Provide knowledge transfer/ mentoring events |
| Ctr shall perform when requested by TA. Ctr shall report knowledge transfer tasks on a monthly basis via written status reports. |
| TA will review status reports from ctr and govt personnel and conduct informal interviews |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.17 Provide implementation support |
| Ctr shall perform this task when requested by the TA by assigned due dates. |
| The TA will ensure due dates are met. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.18 Provide customer support, maintenance, and sustainment |
| Ctr shall perform this task when requested by the TA by assigned due dates. |
| The TA will ensure due dates are met. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.19 Assist in maintaining the HAZMAT application IAW timelines defined in the code specs. |
| Ctr shall complete existing schedules with no more than 5% variance past the due date, as defined in the Project Plan. |
| Existing schedules will be reviewed with TA during scheduled weekly status meetings. |
| Weekly |
| 95% |
| FAR Clause 52.212.4 |
| 5.1.20 Complete tasks in and document User Acceptance Testing. |
| Ctr shall resolve all (100%) documented findings. |
| TA will review results to ensure all (100%) tests are accurate and successful. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.1.21 Provide post implementation assistance to customers. |
| Ctr shall provide support to all (100%) post implementation issues assigned. |
| TA shall review all entries in configuration mgmt. tool to ensure completeness. |
| As requested |
| 100% |
| FAR Clause 52.212.4 |
| 5.2.1 Implement and support IA policies, principles and practices |
| Ctr shall follow identified policies, principle and practices. Tests for IA compliance shall be performed during all (100%) test events. |
| TA will review test results to verify compliance. |
| As required |
| 100% |
| FAR Clause 52.212.4 |
| 5.2.2 Ensure completion of annual IA training |
| Completion required by due dates identified. |
| TA will receive completion certificates. |
| As required |
| 100% |
| FAR Clause 52.212.4 |
| 6.5 Monthly Status Reports |
| Submit monthly status reports |
| TA and COR will review |
| Monthly |
| N/A |
| FAR Clause 52.212.4 |
| 6.6 Travel Reports |
| Sent electronically to TA and COR within 7 days after travel |
| TA and COR will review |
| As required |
| N/A |
| FAR Clause 52.212.4 |
| 6.7 Knowledge Transfer/Mentoring |
| Reported in monthly status report |
| TA and COR will review |
| Monthly |
| N/A |
| FAR Clause 52.212.4 |
-If performance is within acceptable levels, it will be considered to be satisfactory. If not, overall performance may be considered unsatisfactory.
INCENTIVES/DISINCENTIVES:
The COR will make an annual report on Contractor Performance (CPARS or other annual report). The contractor’s failure to achieve satisfactory performance under the contract, reflected in the COR’s annual report, may result in termination of the contract and may also result in the loss of future Government contracts.
In accordance with the inspection of services provisions of the contract, the contractor will be incentivized to provide quality products in a timely manner since the Government can require the Contractor, at no additional cost, to replace or correct work that fails to meet contract requirements.
For each item that does not meet acceptable levels, the Government may issue a Contract Discrepancy Report (CDR). CDRs will be forwarded to the Contracting Officer with a copy sent to the contractor. The contractor must reply in writing within 5 days of receipt identifying how future occurrences of the problem will be prevented. Based upon the contractor’s past performance and plan to solve the problem, the Contracting Officer will determine if any further action will be taken.
File details come from the government source that posted it.