uc san diego: how we communicate during a campus emergency
DESCRIPTION
Information about the process and methods used to communicate to the campus audience and beyond during a crisis or emergency.TRANSCRIPT
![Page 1: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/1.jpg)
Get the word outCommunicating to the campus during an emergency
![Page 2: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/2.jpg)
Brett Pollak@brettcpollak
#uccsc2012
@campusweboffice
![Page 3: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/3.jpg)
AgendaOverview of emergency reporting structure
Classifications of emergencies
Communication mechanisms
Recent case study
Improvements needed
Open discussion
![Page 4: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/4.jpg)
![Page 5: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/5.jpg)
What we plan for…
![Page 6: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/6.jpg)
What it ends up being…
![Page 7: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/7.jpg)
Plan for likely scenariosBasis for response based in Incident Command System (ICS)
• Creates a synthetic organization in the time of crisis
![Page 8: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/8.jpg)
Incident Commander
Operations Planning Logistics Finance & Administration
Information Officer Liaison Officer
Safety Officer
![Page 9: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/9.jpg)
Emergency Operations Center
![Page 10: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/10.jpg)
Severity 1 (low)
Severity 2 (medium)
Severity 3 (high)
Emergency Types
![Page 11: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/11.jpg)
Examples: • H1N1 Swine Flu, • Severe storms predicted or possible flooding
Communications may contain info for “preventative measures”
Severity 1 (low)
![Page 12: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/12.jpg)
Communication
Severity 1 (low)
![Page 13: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/13.jpg)
Severity 1 (low)
![Page 14: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/14.jpg)
Severity 1 (low)
![Page 15: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/15.jpg)
Severity 1 (low)
![Page 16: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/16.jpg)
Register for notifications
![Page 17: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/17.jpg)
Register for notifications
![Page 18: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/18.jpg)
Register for notifications
![Page 19: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/19.jpg)
Other Communication Channels
Channel 1610 (888) 308-8273
![Page 20: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/20.jpg)
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)
![Page 21: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/21.jpg)
Severity 2 (medium)
![Page 22: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/22.jpg)
Severity 2 (medium/high)
![Page 23: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/23.jpg)
Severity 2 (medium/high)
![Page 24: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/24.jpg)
Severity 2 (medium/high)
![Page 25: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/25.jpg)
Severity 2 (medium/high)
![Page 26: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/26.jpg)
![Page 27: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/27.jpg)
DRAFT
<script src= "http://ucsd.edu/common/_emergency‐broadcast/message.js" type="text/javascript"></script>
Code to get banner
![Page 28: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/28.jpg)
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)
![Page 29: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/29.jpg)
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
![Page 30: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/30.jpg)
Examples:• Power Failures in datacenter• Fire or earthquake disables datacenter
Backup generator
Can run for ~4 hours before refueling
Redundancy
![Page 31: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/31.jpg)
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
![Page 32: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/32.jpg)
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
![Page 33: UC San Diego: How we communicate during a campus emergency](https://reader033.vdocuments.us/reader033/viewer/2022060110/555e8deed8b42abd468b5814/html5/thumbnails/33.jpg)
Utilize social media
Rock solid back channel for Communications
Utilizing crowdsourcing to report status
Better ‘local’ communication channels
What we can do better