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 RequirementDeliverableDue Date / FrequencyAcceptance CriteriaResponsible Party
4.2.3.2.1IIS must be cloud‑based, hosted by vendorHosting architecture documentationAt proposal; updated at implementationAgency approvalVendor
4.2.3.2.2IIS must be compatible with major browsersBrowser compatibility test resultsPrior to go‑live; annuallySuccessful test reportsVendor
4.2.3.2.3IIS must operate efficiently on standard desktops/laptopsPerformance test resultsPrior to go‑liveAgency acceptanceVendor
4.2.3.2.4IIS must be accessible without elevated permissionsAccessibility verification reportPrior to go‑liveAgency confirms browser‑only accessVendor
4.2.3.4Maintenance & support servicesMaintenance/support plan (help desk, patches, monitoring, upgrades, docs)At contract execution; ongoingAgency approval of plan; timely updatesVendor
4.2.3.5Data stored exclusively in U.S.Data residency certificationAt contract execution; annuallyVendor certification; Agency verificationVendor
4.2.3.5.1.1Provide BCP/DR plansCopies of BCP/DR plansWithin 60 days of contract execution; upon requestAgency receiptVendor
4.2.3.5.1.2NIST alignment for BCP/DRStatement of alignment with NIST SP 800‑34Within 60 days of contract executionAgency confirmationVendor
4.2.3.5.1.3Annual BCP/DR testingTest summary report + corrective actionsWithin 30 days of test completionAgency acceptanceVendor
4.2.3.5.1.5Continuous improvement of BCP/DRUpdated BCP/DR plansWithin 60 days of lessons learned or changesAgency approvalVendor
4.2.3.5.1.6Annual certification of BCP/DRCertification statementAnnuallyAgency receiptVendor
4.2.3.7Initial planning session within 30 daysPlanning session agenda + finalized Project Plan & ScheduleAgenda: 5 days before session; Plan: 10 days after sessionAgency approval; attendance of key staffVendor (Agency participates)
4.2.3.7.1Finalized Project Plan must adhere to Implementation Plan (4.2.2.2)Finalized Project Plan & ScheduleWithin 10 days after planning sessionAgency approval; alignment with 4.2.2.2Vendor
4.2.3.8Vendor staffing resourcesStaffing plan identifying assigned resourcesAt contract execution; updated as staffing changesAgency approval; compliance with WV/OMIS policiesVendor
4.2.3.9Vendor provides project managerNamed Project Manager with qualificationsWithin 15 days of contract awardAgency approvalVendor (Agency provides monitor)
4.2.3.10Training requirementsDigital training videos + user guides/manualsPrior to go‑liveAgency approval of training materialsVendor
4.2.3.11.3Breach response per OMIS proceduresIncident response plan aligned with OMISAt contract execution; updated as procedures changeAgency approvalVendor
4.2.3.12.1.1FedRAMP Moderate/High authorizationProof of FedRAMP authorizationAt contract award; updates upon changesAgency verificationVendor
4.2.3.12.1.2FIPS 140‑2/3 validated cryptographyDocumentation of validated modulesAt contract award; updates upon changesAgency verificationVendor
4.2.3.12.1.3TLS compliance per NIST SP 800‑52TLS configuration documentation + test resultsAt contract award; updates within 12 months of new NIST/CDC publicationAgency verificationVendor
4.2.3.12.2.1SOC 2 Type II audit reportSOC 2 Type II audit reportWithin 60 days of contract executionAgency receiptVendor
4.2.3.12.2.2Updated SOC 2 Type II audit report annuallySOC 2 Type II audit reportAnnually, within 30 days of anniversaryAgency reviewVendor
4.2.3.12.3Annual penetration testing & vulnerability managementPenetration test report + remediation planAnnually; report within 30 days of test completionAgency review; remediation within 30 daysVendor
4.2.3.12.4.1Documented Secure SDLC processSecure SDLC documentationAt contract execution; updates as neededAgency approvalVendor
4.2.3.12.4.2Perform SAST/DAST scansSAST scan reports (per commit/build); DAST reports (quarterly & post‑release)OngoingAgency review; remediation within 30 daysVendor
4.2.3.12.4.4Track/document third‑party componentsThird‑party library/module inventoryOngoingAgency reviewVendor
4.2.3.12.4.5Continuous monitoringMonitoring reportsOngoing; annual penetration testingAgency reviewVendor
4.2.3.12.5Cloud provider attestationsFedRAMP authorization proof + U.S. residency evidence + OMIS compliance docsAt contract execution; updates upon changesAgency verificationVendor
4.2.3.12.6Vendor Attestation FormCompleted Attestation FormWithin 30 days of contract execution; annually or upon changesAgency receiptVendor
4.2.3.12.7Incident Response policy & planIR policy aligned with NIST SP 800‑61 + annual exercise reportsAt contract execution; annual exercises; updates within 6 months of revisionsAgency approvalVendor
4.2.3.12.8Audit & attestation requirementsDocumentation/evidence; updated attestation forms; remediation confirmationUpon request; annually; remediation within 60 daysAgency receipt and verificationVendor (Agency may audit/verify)

Deliverables

File details come from the government source that posted it. Updated .