The alerting environment functional area shall focus on the following areas: I. General Alerting The solution should: 1. Natively support sending SMS alerts to registered user’s cell phones without the need to install a mobile application. 2. Natively support sending bulk email alerts to registered users to both TU and external email addresses. 3. Host and publish an RSS feed of all posted alerts accessible to TU’s web environment and our campus signage application. 4. Offer a desktop alerting application that runs on current Apple and Windows workstations. The app must be able to be remotely deployed in bulk or individually to all domain registered computers for unattended installation. II. Outbound Integrations The solution should: 1. Integrate with TU’s cloud and on-premises Cisco phone system to facilitate alert delivery by text to speech or from recorded voice messages to both desktop handsets and WebEx virtual phones. 2. Deliver text to speech or recorded voice alert messages to 46 fire panel annunciators (contact closure - line level audio), or offer an alternative interior annunciator solution. 3. Deliver text to speech or recorded voice alert messages to 10 outdoor Whelen siren/speaker annunciators (contact closure - line level audio). 4. Provide affirmative real-time indication of successful announcement of alerts sent to annunciators, preferred additional integration (not required): • Integrate with MS Teams for voice and messaging alerts III. Inbound Integrations The solution should: 1. Facilitate an automated alert arriving from the OmniLert Gun Detection system to be delivered to a limited group of recipients without human intervention. 2. Allow for physical panic button activations to target pre-defined groups of recipients. 3. Allow campus Cisco phone handsets to function as a panic button, triggering an alert to a pre-defined group of users. IV. Mobile App The solution should: 1. Include a mobile app for iPhone and Android platforms with panic button functionality. 2. Record and display in real-time the geo-location of the activated mobile device. 3. Facilitate camera access on the mobile device remotely to the alerting software operator. 4. Facilitate live video from the activated mobile device to the alerting software operator. 5. Permit the activated mobile device user to send photos to the alerting software operator. 6. Facilitate two-way text messaging between the activated mobile device user and the alerting software operator. 7. Provide one-click direct call for two-way audio communication between the activated mobile device user and the alerting software operator. V. Hosting The solution should: 1. Be primarily cloud hosted with on-premises appliances, if necessary, for secondary system integrations. 2. If there is an on-premises appliance, allow for an additional on-premises appliance to serve as a hot-swappable backup for redundancy. VI. Security and Compliance The solution should: 1. Be covered under current SOC2 type 2 2. Be WCAG compliant with all user web and mobile device interfaces 3. Utilize SSO for functional users and administrators VII. Features The solution should: 1. Allow for a minimum of 20 user-defined message content templates for rapid launch. 2. Allow for a minimum of 20 user-defined preset action routines for automated alerting procedures. 3. Facilitate automated scheduled bulk-loading of end user records from TU’s primary source to include a minimum of 2 phone numbers and a minimum of 2 email addresses for each user record. 4. Offer integrated data reporting for the following: a. Message delivery success/failures for all endpoints. b. Historical alerting details for all alerts to include date/time/sender/content/alert parameters/defined delivery endpoints. c. Panic button activity logs, including all subsequent follow-up actions taken with the user through their device. d. Gun detection incoming alerting activation logs. 5. Provide data export options for alerting activity records, endpoint registration status, panic button activity logs, and other tracked application data points needed for required reporting. VIII. Support The provider should: 1. Offer a 24/7 contact option for emergency environment issue reporting. 2. Offer multi-modal, on-demand training accessible 24/7. 3. Offer ad-hoc guidance and troubleshooting for environment managers and administrators
