Mass Notification and Alert System

The vendor required to provide installation, data migration, and support of a software-as-a-service (SaaS) mass notification and alert system.
- The installation and support of a mass notification system for 10,000 recipients. 
- The mass notification system will directly support emergency events, public events, and airport operations.
- SaaS mass notification and alert system for 10,000 recipients. 
- The system shall be able to send and receive messages across a variety of platforms by different methods. 
- The services shall include implementation, configuration, migration, training, and on-going maintenance and support including system upgrades, fixes, and updates.
- System requirements
1. Notification and alert
•    The system must have the capability to send notifications and alerts via to email, text messages (SMS), landline, VoIP, and mobile phones (android and iOS), and all mobile app platforms including iOS and android.
2. Configuration and integration
•    The system shall integrate with the airports authority’s airport operations, public safety and emergency management awareness systems. 
•    This includes computer-aided dispatch (cad) system, lightning detection system, workday human capital management system, airport communicator (PASSUR), and surface management system.
•    The system must be able to send messages using simple mail transfer protocol (smtp) to a group email address and distribute to all contacting methods. 
•    The contractor must ensure the notification or alert can integrate with the computer-aided dispatch (cad) system through the smtp.
- Functional requirements
1. Send and receive
•    Able to receive and send notifications and alerts 24/7/365.
•    Able to send real-time notifications and alerts from external data sources, including, but not limited to, the national weather service 
•    Able to send and receive messages across a variety of platforms including voice. 
•    Able to send notifications and alerts ad hoc and through templates.
•    Notification and alert variables must include text, selection, dropdowns, date, time, geographic area and ad hoc capabilities.
•    Must have a test environment (sandbox) for notifications and alerts. 
•    Send at least 50,000 notifications and alerts to recipients at one time. 
•    Schedule and save notifications, alerts, and calls for a specific date and time. 
•    Create and send text-to-speech notifications and alerts. 
•    Must have the capability to attach images and documents to notifications and alerts. 
•    Able to create an unlimited number of notification and alert groups and sub-groups.
•    Send notifications and alerts to registered customers based upon geographic area of the incident or emergency
•    Able to load and save geographic boundaries for notifications and alerts. 
•    Send multiple notifications and alerts in one instance to different groups simultaneously. 
•    Each user must be provided with a unique identifier (example: airports authority’s email address). 
•    User contact fields must include first name, last name, email address, agency type, organization, campus, worksite location, message reception types. 
•    User contact must be able to be assigned to groups and subgroups.
2. Templates
•    Must be able to create, copy, edit and save templates for all notifications and alerts. 
•    Templates must have the capability to add an unlimited number of variables. 
•    Templates and variables must be able to be copied and edited. 
•    Standard variables such as date, time, user, notification group name(s) must be able to be prepopulated in the templates before the notification or alert is sent. 
•    Templates must be able to be assigned an unlimited number of groups, sub-groups and individuals.
3. Conference calls
•    Must be managed (initiated and ended) by the notification or alert sender and an account administrator. 
•    Conference calls can be conducted from a computer, a VoIP, landline phone or mobile phone.
•    Must have the capability to conduct, record and manage conference calls, including callback and reverse conference calls. 
•    Recording and documentation of the conference call must be available for download for a minimum of 18 months. 
•    Must provide at least 4 conference call numbers that can be assigned to departments or an incident and event. 
•    Each conference call line must have the capability to automatically initiate when two participants arrive without a code. 
•    Notifications and alerts must contain a hyperlink to conference call information for quick selection. 
•    Each conference call line must have the capability to mute participants and remove participants from the call. 
•    Each conference call line must have the capability to host a minimum of 250 attendees.

- Contract Period/Term: 2 years
- Pre-Proposal Conference Date: February 18, 2026
- Questions/Inquires Deadline: February 20, 2026