The vendor required to provide emergency notification system must enhance emergency communications and integrate with provincial and national alerting systems, where possible, to support emergency evacuations and other emergency-related notifications.
- System requirements:
• Be fully cap-cp compliant to ensure compatibility with standards.
• Require district administrators to sign in with single sign on using microsoft ENTRA id.
• Support data migration from existing systems, i.e., subscribers (57,000) to emergency notifications.
• Allow users to receive relevant information, which is determined by their current location, and users can choose to receive notifications for geographical areas of their choosing.
• Allow users to receive notifications for and from a variety of communication channels (email, text/SMS), etc. of their choosing.
• Be an interoperable system that allows different communication systems, devices and agencies to share data and communicate seamlessly during emergencies.
• This shall include the following standards:
o Include mobile apps and plug-in and secure API integration into the current website, mapping GIS (Esri) and possible news feed and social media that meet independent accessibility requirements for public sector accessibility standards and multilingual alert capability.
o Alerts must be accessible on smartphones, feature phones, desktop computers and other commonly used devices.
o The system must allow authorized agencies (municipal, provincial, federal) to share data and coordinate messaging in real time.
• Include training, implementation support, and ongoing helpdesk services (24/7) in a timely and efficient manner
• Allow simple registration and de-registration with minimal collection of personal information.
• Data collection must comply with state public sector privacy and data protection regulations
• Provide the ability to correct previously published information or alerts without re-notifying all users.
• Provide notification broadcast to public users simultaneously and deliver within 10 minutes of sending.
• Provide the ability for emergency management website to communicate with the third-party system to either send or receive data to reduce duplication of processes.
• Provide the district with metrics of delivery, read and click through rates.
- System preferences:
• Be compatible with provincial and federal alerting frameworks where applicable, such as the integration with other official alerting systems including:
o Center for flood advisories and warnings
o Drive state for transportation incidents
o Earthquake early warning system
o Environment country for severe weather alerts
o Alert ready national alerting system
• Enable notifications to be delivered through broadcast intrusive alerts to public communication infrastructure, including:
o Radio and television broadcasts.
o Digital displays, such as road signs, transit screens, and other electronic displays that can be used to extend reach of emergency notifications.
o Wireless alerts to mobile phones allowing people on the move to stay informed.
- Requirements:
1. Implementation to ‘go-live’:
• Test environment:
o Provide a test environment mirroring production for configuration testing, training, and validation.
o Data conversion and transfer: vendor shall be responsible for extracting, converting, and loading all current account data from the central current systems into the new system, such as the current 57,000 subscribers to emergency notifications.
o District staff will assist with data extraction as required.
• Training and documentation:
o Vendor shall deliver comprehensive training for district staff, including role-specific sessions and onboarding support.
o Documentation provided must include user guides, administrative manuals (as applicable) to support ongoing use.
• Post-implementation support:
o Provide support during the initial stabilization period following go-live.
o This shall include; troubleshooting, performance optimization, minor configuration adjustments, and resolution of early-stage issues.
2. Ongoing licensing and support:
• System hosting and data storage: provision of secure hosting infrastructure and data storage services, compliant with the district’s privacy and security requirements.
• Licensing and subscriptions: all necessary system licenses, subscriptions, and renewals required to operate the system throughout the contract term.
• System security: continuous monitoring and enforcement of security protocols, including updates aligned with evolving cybersecurity standards.
• Maintenance and support services, including:
o Emergency helpdesk technical support: available 24/7, 365 days per year for critical system issues.
o Customer support: available Monday to Friday, 7:30 am to 4:30 pm pacific standard time for general inquiries and assistance.
o System maintenance: includes all required system updates, bug fixes, and resolution of technical errors or performance issues.
- Budget: $15,000
- Contract Period/Term: 3 years
- Questions/Inquires Deadline: January 12, 2026
