Floods Web Application and Integrated Camera System

The Vendor is required to provide GIS-based website with a new and improved ATX floods web application, a public-facing platform and key component of the city’s flood early warning system (FEWS).
- Web application and graphical user interface
•    Implement a new GIS-based ATX floods web application that includes select water crossings, cameras that monitor a subset of water crossings, and partner jurisdictions currently available on the existing ATX floods platform. 
•    The application may be an existing or custom developed solution. 
•    Enable the collection, storage, viewing, updating, addition, removal, and editing of geographic information, camera imagery, and sensor data. 
•    Create a public-facing map-based interface that displays near-real-time cellular camera images (every three [3] to five [5] minutes), and road closure updates on a color-coded map of low water crossings, segmented by time and jurisdiction. 
•    Provide the recommended technology and format for transmitting captured images from cellular-enabled cameras to the web application and ensure full compatibility with existing cameras and associated image file formats and document any additional supported formats. 
•    Ensure the web application is flexible and agnostic to technologies such as camera make and model and cloud hosting provider. 
•    Support future web application expansion to include additional partner jurisdictions and geographic areas. 
•    Provide address search functionality and allow users to subscribe to specific or multiple low water crossings for updates.
•    Define and document application performance levels and service level agreements (SLAS). 
•    Enable partner jurisdictions to update their closure information directly through the web application. 
•    Ensure compatibility with the city currently supported operating system (OS) and browser versions (current release minus 2) on desktops, tablets, and smartphones. 
•    Conduct workshops for requirements review, application and architecture design, overall solution validation, and provide a solution design document. 
•    Deploy all necessary licensing for the web application and supporting components. 
•    Configure the administrator dashboard according to the specified functional and nonfunctional requirements that will be provided. 
•    Create roles, user types, and role-based access based on the principle of least privilege. 
•    Create a cutover plan, listing out the step-by-step process to transition to production. 
•    Bring the production environment online to run in parallel with the existing ATX floods site for a transition period of approximately three (3) to six (6) months, followed by final cutover to the new platform as determined by the city. 
•    Provide comprehensive audit logging and change history, including all user actions, administrator actions, and versioned updates, with access restricted to authorized staff. 
•    Ensure the web application meets web content accessibility guidelines (WCAG) 2.1 AA for public-facing content. 
•    Support multilingual translation display and localization for public-facing content. List of city recommended languages includes Chinese simplified, Vietnamese, Arabic, Korean, French and Hindi. 
•    Refer to the “translation” link in the upper right corner of the city website as an example.
•    Implement the branding, style guide, uniform resource locator (URL) and domain name that we choose for the new website. 
•    If a new URL and domain are used, the existing URL and domain shall be forwarded to the new URL and domain. 
•    The system shall integrate with the cities existing Entraid identity and access management (IAM) platform for user authentication, authorization, and role-based access control (RBAC), with roles and user assignments provisioned via system for cross-domain identity management (SCIM) integration, leveraging existing security policies and single sign-on (SSO) capabilities.
- Administrator dashboard
•    Provide an administrator dashboard for managing site content, user accounts, water crossings, road closure status, cameras and images, notifications, messages, statistics, reports, and jurisdictional data. 
•    Develop the dashboard as a secure, username and password-protected interface that supports security assertion markup language (SAML), OpenID connect (OIDC) and SCIM capabilities for provisioning of user accounts. 
•    Include administrator dashboard functionality to add, remove, and edit geographic points, camera systems, and sensor systems. 
•    Include role-based access control aligned with city defined roles, and enable administrators to manage users, including adding, removing, and editing user records. 
•    Incorporate geographic points editable via both tabular and map-based interfaces. 
•    Provide functionality to view, add, edit, and remove cameras, feeds, and notifications. 
•    Enable administrators to view the location and update the status of any crossing within the system. 
•    Implement role-based access control based on the principle of least privilege, supporting multiple user types and allowing administrators to configure additional roles as needed. 
•    Provide support for secure access for multiple designated administrators, including partner jurisdictions contributing to the platform. 
•    Provide a solution that supports configurable notification rules and escalation paths for critical events, including flood-related closures and sensor alerts. 
•    Include configurable session timeout settings and automatic logout for inactive admin sessions within the dashboard. 
•    Include support for bulk upload, edit, and removal of crossings, cameras, and user records. 
•    Ensure the administrator dashboard is responsive and usable on tablets and smartphones.
- System architecture
•    Provide a SaaS based or cloud-hosted, high-availability system architecture for the ATX floods web application that supports 99.5% or greater uptime and dynamic scaling based on real-time usage and severe weather thresholds. 
•    Include documented policies for scaling behavior, resource efficiency, and availability guarantees. 
•    Provide a 15 (fifteen) minute recovery time objective (RTO) for both water crossing status and update of camera images for the system
•    Ensure compliance with the recovery point objective (RPO) to provide the most recently captured images and water crossing status within the RTO of 15 (fifteen) minutes, and restoration of a minimum of two (2) weeks of data within four (4) hours, and all data (a minimum of one [1] year) restored within 1 day. 
•    Document how these RTO and RPO commitments will be measured and reported and identify any associated service-level penalties if these objectives are not met.
•    Support and maintain development, testing, and production (dev, test and prod) application tier environments with clear deployment workflows and rollback protocols. 
•    Ensure the system architecture supports future coverage expansion for low water crossings across additional jurisdictions, including communities and counties in the central STATE region surrounding CITY and are a member of the capital area council of governments (CAPCOG). 
•    Ensure the system architecture supports integration of multiple partner camera networks beyond the existing deployment. 
•    Perform comprehensive stress testing of the system architecture and cloud environment at least twice per year. 
•    Provide a business continuity and disaster recovery plan and conduct a disaster recovery exercise at least once per year. 
•    Incorporate city information security-aligned security controls within the system architecture, ensuring data encryption in transit and at rest, supported by comprehensive access controls across all system layers. 
•    Comply with the information security controls defined in the “city low impact control set” spreadsheet 
•    Provide proposed architecture for incorporating live streaming. 
•    The document should include bandwidth requirements, storage implications and any changes to the existing architecture that may be required to support live video streaming. 
•    Conduct collaborative design workshops with the city project team and deliver a “Tobe” system architecture diagram that reflects the proposed implementation. 
•    Include architectural support for disaster recovery, automated failover, and system health monitoring, with documented recovery time objectives (RTO) and recovery point objectives (RPO). 
•    Provide a near real-time system performance dashboard accessible to authorized staff, including uptime, latency, and load metrics. 
•    Ensure compatibility with infrastructure-as-code (IAC) practices for repeatable, auditable deployments. 
•    Ensure that the secure sockets layer (SSL) site certificate for the website is properly managed and renewed.
- Project management
•    Provide a contracting mechanism, such as an inter-local agreement (ILA), for new partner organizations to participate in cost-sharing and purchase the inclusion of their area of jurisdiction into atxfloods.com and the integration of additional cameras. 
•    Provide a contracting mechanism for new partner organizations to purchase maintenance and support for their newly added area of jurisdiction on atxfloods.com
•    Provide an optional contracting MECHANISM for existing partner organizations such as homeland security emergency management (HSEM), capital area metropolitan planning organization (CAMPO), CAPCOG, etc., and other partner jurisdictions to contribute in a cost-sharing agreement. 
•    Provide a project plan that includes all the detailed project activities and work breakdown structure (WBS), and important deliverables and milestones. 
•    Provide a project schedule that includes bringing the production environment online and completing testing before the existing contract end-date in January of 2028 
•    Define clear city ownership of the application source code and site URL.
•    Document or provide existing user terms and conditions and privacy policy for the appropriate use of the ATX floods website. 
•    Conduct project kickoff meeting, as well as regular check-in meetings and working sessions as needed for the overall project.