Get the word out: Ideas for communicating during a campus emergency

Provides information about the process and methods UC San Diego uses during a crisis or emergency situation on campus.

Transcript

1. Get the word out Communicating to the campus during an emergency
2. Brett Pollak @brettcpollak #uccsc2012 @campusweboffice
3. Agenda Overview of emergency reporting structure Classifications of emergencies Communication mechanisms Recent case study Improvements needed Open discussion
5. What we plan for…
6. What it ends up being…
7. Plan for likely scenarios Basis for response based in Incident Command System (ICS) • Creates a synthetic organization in the time of crisis
8. Incident Commander Operations Planning Logistics Finance & Administration Information Officer Liaison Officer Safety Officer
9. Emergency Operations Center
10. Severity 1 (low) Severity 2 (medium) Severity 3 (high) Emergency Types
11. Examples: • H1N1 Swine Flu, • Severe storms predicted or possible flooding Communications may contain info for “preventative measures” Severity 1 (low)
12. Communication Severity 1 (low)
13. Severity 1 (low)
14. Severity 1 (low)
15. Severity 1 (low)
16. Register for notifications
17. Register for notifications
18. Register for notifications
19. Other Communication Channels Channel 1610 (888) 308-8273
20. Examples: • Large magnitude earthquake • Fire approaching campus, etc. Some damage or affect to the campus (classes closed) may be immediately evident or likely to be evident in the near future Severity 2 (medium)
21. Severity 2 (medium)
22. Severity 2 (medium/high)
23. Severity 2 (medium/high)
24. Severity 2 (medium/high)
25. Severity 2 (medium/high)
27. DRAFT <script src= "http://ucsd.edu/common/_emergency‐ broadcast/message.js" type="text/javascript"> </script> Code to get banner
28. Examples: • Active on-campus shooter • Large scale on-campus fire, or other high impact incident Could potentially capture the attention of a state-wide, national, or international audience. Severity 3 (high)
29. UCSD home page becomes the emergency status page – Ensures viewers do not miss info updates – Lightweight: optimized to handle increased Web traffic – ucsd.edu/emergency would point here Severity 3 (high) Treatment
30. Examples: • Power Failures in datacenter • Fire or earthquake disables datacenter Backup generator Can run for ~4 hours before refueling Redundancy
31. Copy of CMS content & websites sent to UCOP each morning at 5:00 AM Limited number of accounts created (CMS not behind SSO) Utility created to switch DNS so content under ucsd.edu is being delivered from UCOP Web server environment. Disaster Recovery
32. Sept. 8, 2011 • Power outage across Southern CA • Power outage duration: ~20 hours Summary • Generators kicked in – No downtime • Cell towers became overloaded – Communication issues • Batteries needed to be charged via car chargers • Concerns about family safety balanced with campus safety Case study
33. Utilize social media Rock solid back channel for Communications Utilizing crowdsourcing to report status Better ‘local’ communication channels What we can do better