Deliverables .xlsx
XLSX spreadsheet 15 KB Posted
- Attached to
- IMMUNIZATION INFORMATION SYSTEM (IIS)
- Solicitation number
- CRFP 0506 MIS2700000001 1
- Issued by
- Kanawha County, West Virginia
About this file
This is a Deliverables document for the West Virginia Immunization Information System (IIS) contract, outlining mandatory requirements and vendor responsibilities for delivering a cloud-based immunization management platform. The contract specifies that the IIS must be cloud-hosted by the vendor, compatible with major browsers, and operationally efficient on standard desktop and laptop computers. Key deliverables include hosting architecture documentation at proposal submission and implementation, browser compatibility test results prior to go-live with annual updates, performance testing reports, accessibility verification confirming browser-only access, and comprehensive maintenance and support services including help desk, patch management, monitoring, upgrades, and documentation. The vendor must establish a dedicated project manager within 15 days of contract award, conduct an initial planning session within 30 days of contract execution, and submit a finalized Project Plan and Schedule within 10 days following that session. Training requirements include digital training videos and user guides to be completed prior to system go-live, and the vendor must provide a staffing plan at contract execution with updates as staffing changes occur.
The contract imposes extensive security and compliance requirements, including FedRAMP Moderate or High authorization, FIPS 140-2/3 validated cryptography, TLS compliance per NIST standards, SOC 2 Type II audit reports due within 60 days of contract execution with annual renewals, annual penetration testing with remediation plans, and continuous SAST/DAST scanning with findings remediated within 30 days. Additional mandatory deliverables include business continuity and disaster recovery plans aligned with NIST SP 800-34, annual BCP/DR testing and certification, data residency certification confirming all data storage in the United States, an incident response plan aligned with OMIS procedures per NIST SP 800-61, documented Secure Software Development Lifecycle processes, third-party component tracking, and a completed Vendor Attestation Form. All deliverables require Agency approval or verification, with ongoing monitoring and annual compliance certifications throughout the contract period.
View the file
Other files
Show all 15
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
Sheet1
| Section Ref. | Mandatory Requirement | Deliverable | Due Date / Frequency | Acceptance Criteria | Responsible Party |
| 4.2.3.2.1 | IIS must be cloud‑based, hosted by vendor | Hosting architecture documentation | At proposal; updated at implementation | Agency approval | Vendor |
| 4.2.3.2.2 | IIS must be compatible with major browsers | Browser compatibility test results | Prior to go‑live; annually | Successful test reports | Vendor |
| 4.2.3.2.3 | IIS must operate efficiently on standard desktops/laptops | Performance test results | Prior to go‑live | Agency acceptance | Vendor |
| 4.2.3.2.4 | IIS must be accessible without elevated permissions | Accessibility verification report | Prior to go‑live | Agency confirms browser‑only access | Vendor |
| 4.2.3.4 | Maintenance & support services | Maintenance/support plan (help desk, patches, monitoring, upgrades, docs) | At contract execution; ongoing | Agency approval of plan; timely updates | Vendor |
| 4.2.3.5 | Data stored exclusively in U.S. | Data residency certification | At contract execution; annually | Vendor certification; Agency verification | Vendor |
| 4.2.3.5.1.1 | Provide BCP/DR plans | Copies of BCP/DR plans | Within 60 days of contract execution; upon request | Agency receipt | Vendor |
| 4.2.3.5.1.2 | NIST alignment for BCP/DR | Statement of alignment with NIST SP 800‑34 | Within 60 days of contract execution | Agency confirmation | Vendor |
| 4.2.3.5.1.3 | Annual BCP/DR testing | Test summary report + corrective actions | Within 30 days of test completion | Agency acceptance | Vendor |
| 4.2.3.5.1.5 | Continuous improvement of BCP/DR | Updated BCP/DR plans | Within 60 days of lessons learned or changes | Agency approval | Vendor |
| 4.2.3.5.1.6 | Annual certification of BCP/DR | Certification statement | Annually | Agency receipt | Vendor |
| 4.2.3.7 | Initial planning session within 30 days | Planning session agenda + finalized Project Plan & Schedule | Agenda: 5 days before session; Plan: 10 days after session | Agency approval; attendance of key staff | Vendor (Agency participates) |
| 4.2.3.7.1 | Finalized Project Plan must adhere to Implementation Plan (4.2.2.2) | Finalized Project Plan & Schedule | Within 10 days after planning session | Agency approval; alignment with 4.2.2.2 | Vendor |
| 4.2.3.8 | Vendor staffing resources | Staffing plan identifying assigned resources | At contract execution; updated as staffing changes | Agency approval; compliance with WV/OMIS policies | Vendor |
| 4.2.3.9 | Vendor provides project manager | Named Project Manager with qualifications | Within 15 days of contract award | Agency approval | Vendor (Agency provides monitor) |
| 4.2.3.10 | Training requirements | Digital training videos + user guides/manuals | Prior to go‑live | Agency approval of training materials | Vendor |
| 4.2.3.11.3 | Breach response per OMIS procedures | Incident response plan aligned with OMIS | At contract execution; updated as procedures change | Agency approval | Vendor |
| 4.2.3.12.1.1 | FedRAMP Moderate/High authorization | Proof of FedRAMP authorization | At contract award; updates upon changes | Agency verification | Vendor |
| 4.2.3.12.1.2 | FIPS 140‑2/3 validated cryptography | Documentation of validated modules | At contract award; updates upon changes | Agency verification | Vendor |
| 4.2.3.12.1.3 | TLS compliance per NIST SP 800‑52 | TLS configuration documentation + test results | At contract award; updates within 12 months of new NIST/CDC publication | Agency verification | Vendor |
| 4.2.3.12.2.1 | SOC 2 Type II audit report | SOC 2 Type II audit report | Within 60 days of contract execution | Agency receipt | Vendor |
| 4.2.3.12.2.2 | Updated SOC 2 Type II audit report annually | SOC 2 Type II audit report | Annually, within 30 days of anniversary | Agency review | Vendor |
| 4.2.3.12.3 | Annual penetration testing & vulnerability management | Penetration test report + remediation plan | Annually; report within 30 days of test completion | Agency review; remediation within 30 days | Vendor |
| 4.2.3.12.4.1 | Documented Secure SDLC process | Secure SDLC documentation | At contract execution; updates as needed | Agency approval | Vendor |
| 4.2.3.12.4.2 | Perform SAST/DAST scans | SAST scan reports (per commit/build); DAST reports (quarterly & post‑release) | Ongoing | Agency review; remediation within 30 days | Vendor |
| 4.2.3.12.4.4 | Track/document third‑party components | Third‑party library/module inventory | Ongoing | Agency review | Vendor |
| 4.2.3.12.4.5 | Continuous monitoring | Monitoring reports | Ongoing; annual penetration testing | Agency review | Vendor |
| 4.2.3.12.5 | Cloud provider attestations | FedRAMP authorization proof + U.S. residency evidence + OMIS compliance docs | At contract execution; updates upon changes | Agency verification | Vendor |
| 4.2.3.12.6 | Vendor Attestation Form | Completed Attestation Form | Within 30 days of contract execution; annually or upon changes | Agency receipt | Vendor |
| 4.2.3.12.7 | Incident Response policy & plan | IR policy aligned with NIST SP 800‑61 + annual exercise reports | At contract execution; annual exercises; updates within 6 months of revisions | Agency approval | Vendor |
| 4.2.3.12.8 | Audit & attestation requirements | Documentation/evidence; updated attestation forms; remediation confirmation | Upon request; annually; remediation within 60 days | Agency receipt and verification | Vendor (Agency may audit/verify) |
Deliverables
File details come from the government source that posted it. Updated .