Board of Elections Foundations Google

1. Scope and Engagement Approach Scope: Description of Work New York State Board of Elections (NYSBOE) is seeking a Contractor to establish a modern, scalable data platform on Google Cloud that supports the publication and analysis of publicly available election data to enable transparent, publicly accessible insights into election activity while adhering to best practices in security, cost management, and scalability (“Services”). The agency has an existing Google and Salesforce tenants within which the vendor will be required to create the application. Applications mentioned in the CR are subject to support and change by the GCP vendor. Information will be made publicly available on a 24/7/365 basis. Traffic analysis and estimations should be considered in sizing the project to fit the future needs of the agency, System must be configured for maximum up time. System should adhere to FEDRAMP/SOC2 requirements for data ingestion, storage and export. The Google Platform is shared among applications used by the agency. A contractor should be familiar with use of the platform in a shared environment and not disturb or interfere with any projects running other applications or services. Procurement of the platform is out of scope for this project. Any project dependencies should be included in the cost proposal. The public information served to a website must meet current NYS branding requirements, WCAG 2.1 AA accessibility standards, adhere to mobile design standards and allow for language translation of any informational or static information on the site. Engagement Approach Using a phased approach, Contractor will first build a secure cloud foundation (Phase 1: Google Cloud Foundation). During this phase, Contractor will establish the foundational Google Cloud infrastructure required to securely support data ingestion, storage, access, and dashboarding activities in future phases. This work includes user access policies, network configuration, service enablement, and auditing. In the following phases (Phase 2: Project B – Municipal Election Data Management, and Phase 3: Project A – Campaign Finance Data Management), Contractor will implement a data warehouse for structured data ingestion and normalization in BigQuery’s (or GCP current recommended database) analytical database and dashboarding accessible to external audiences. Large size zip files created from the data and made available for download by the public is in scope for this part of the project and will require space and setup for public user access to the information. During Phase 2, Contractor will implement a Salesforce to GCP pipeline that ingests municipal voter and elections related data, stores results in BigQuery (or GCP current recommended database), and visualizes the output via a Looker Studio dashboard (or GCP current recommended data visualization platform). GIS file upload, storage, rendering and map creation is part of the scope of this phase. Integration with publicly available maps and the use of Google Map and possible API integration should be included in scope. During Phase 3, Contractor will implement a data warehouse of structured campaign finance data from Salesforce to the data warehouse in Google Cloud. The data will be visualized through a public-facing Looker Studio dashboard (or GCP current recommended data visualization platform), to be embedded in Salesforce Experience Cloud by NYSBOE, enabling transparent and accessible insights. Phase 4 – Hypercare, Contractor will provide post-implementation support of the stability, reliability, and usability of the solution delivered in earlier phases. A part-time Lead Engineer will be available to provide continuity and respond to operational issues. The Lead Engineer will serve as the technical point-of-contact for incident triage, minor issue resolution, and system uptime support across the integrated components of the project 2. Deliverables and Acceptance Technical Deliverables Table 1: Deliverables Phase Deliverable Phase 1: Google Cloud Foundation Google Cloud Organization: folder/project structure Project Bootstrap: Creation of baseline Google Workspace, users, roles, security controls, establish Google Cloud projects for future phases across IAM/Security, Networking Auditing, and API configuration, establish a data warehouse and file repository Phase 2: Project B – Municipal Election Data Management Configured Google Cloud project Secure Ingestion Pipeline BigQuery Normalized Schema Unified data model for storing normalized datasets Looker Studio Dashboard for exploring ingested data Ability to export large data sets and store associated flat files (images, GIS maps, assorted documents) Documentation package: pipeline configuration guide, onboarding instructions, schema definitions, and dashboard documentation. Phase 3: Project A – Campaign Finance Data Management Configure Google Cloud project Secure Ingestion Pipeline BigQuery Normalized Schema Unified data model for storming normalized datasets Ability to export large data sets and store associated flat files (images, GIS maps, assorted documents) Public Looker Studio Dashboard for exploring ingested data Documentation Package: pipeline configuration guide, onboarding instructions, schema definitions, and dashboard documentation Phase 4: Hypercare Incident Response Log Monthly Platform Health Reports Updated Technical Documentation and Change Record: A living set of technical documents reflecting changes or updates during HyperCare Technical Deliverables Acceptance Process The acceptance process for the technical deliverables will be as follows: NYSBOE will provide a list of approval owner’s names for each deliverable at the start of each project phase. The approval owner will be the single point-of-contact accountable for deliverable approval/signoff at completion of deliverable. If NYSBOE needs additional time to review an item, NYSBOE will have a period of five (5) business days from the completion of deliverable to communicate the specific reason(s) for non-acceptance of a deliverable. If NYSBOE fails to communicate any such non-acceptance within the five (5) business days period, the deliverable will be deemed to have been accepted by the NYSBOE. 3. Engagement Schedule and Service Location Engagement Schedule The contract is expected to last thirty-four (34) weeks. Service Location NYSBOE authorizes Contractor’s resources to work remotely off-site within the United States (U.S.), away from a NYSBOE location. 4. Engagement Price Fixed-Fee Milestone Billing This engagement will be executed as a fixed-fee engagement with milestone payments based on deliverables provided during a specified milestone and NYSBOE’s acceptance. Business enterprises awarded an identical or substantially similar procurement contract within the past five years: None