1. Notification Requirements o Recipients: 40,000 to 50,000 students, faculty, staff. Additionally, campus visitors will be able to receive campus emergency notifications. o Channels: Text messages, emails, and phone calls. If recipient app is included in the solution, emergency alert push notifications must be sent to app users. o Response Time: To comply with the Clery Act, notifications must be sent out within ten minutes of an alert being initiated by administrators. o Modifiable pre-prepared or “Canned” templates for initiating the emergency alerts are desired. Authorized campus administrators should be able to quickly initiate the alert using incident-specific templates so that messages can be quickly modified. Possible criteria for consideration are: (1) Drop down menu/options for which campus, (2) type of emergency, (3) inserting date and time. 2. Integration Requirements • Banner Integration: The system should integrate with the Banner system to obtain the current list of recipients. • Integration: The system should pass emergency messages via Common Alert Protocol (CAP) to the campus current Alertus instance which operates on SHSU laptops and desktops. 3. Mobile App Requirements (if applicable to solution) • Platforms: Must support Apple iOS and Android systems. • Apps: Two separate mobile apps are required: o Recipient App: For students to receive emergency messages. o Administrator App: For administrators to send out emergency messages. • Accessibility: Both apps must comply with accessibility standards and laws. • Branding: The apps should allow for university branding. 4. Text Messaging Service • Delivery Confirmation: The system must provide delivery confirmation for text messages. 5. Data and Privacy • The system must comply with the Texas State University System Information Security & Accessibility Standards Exhibit. Additionally, the system should have a valid TX-RAMP certification.
