Conferences & Events
Events for all Levels and InterestsStay
Jump Start Your Career GrowthStay
Get on the Higher Ed IT MapStay
Uncommon Thinking for the Common Good™Stay
Campus Emergency Notification System
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
We are currently using ATI for our loud speakers on campus. The ATI system is used for chimes, sirens, and verbalizing emergency broadcast messages over the speakers. The speakers are loud enough that we hear them inside the buildings. In the past, ATI has done well at accommodating RAVE into their interface. We use RAVE for our texting portion. When we need to text an alert out to our Faculty/Staff and students, we go to the ATI interface and click on some button that invokes RAVE to text out the message. We love this setup because it gives one interface to our emergency responders. They don’t have to remember how to logon to this system and that other system when they are in ‘crazy mode’ trying to respond to an emergency.
Now, we have added Alertus. We are using Alertus to send a pop-up to all computer screens (Mac, Windows, and digital signs) on campus. The problem is that Alertus is another system that we need to integrate into this single interface. It was free to us. ATI is not accommodating that into their interface at this time. We have also learned that ATI is not CAP compliant. Currently, our emergency responders are having to remember how to access two systems to get an emergency message out to the campus through all the channels.
Does anyone have any suggestions as to what they are doing to build a one interface system? I am interested to know what others are doing to make this easy on their first responders. We need to re-visit the way we are doing it here I think.
Joann L. Williamson
Director of Network Systems, Architecture, & Infrastructure
Computer Services Department
University of South Carolina Aiken
471 University Parkway
Aiken, SC 29801