1. Defining Emergency Response for College IT Mike Osterman Whitman College

2. slide 2 CLAC 2006 Hanford Nuclear Reservation Umatilla Chemical Weapons Depot Local fault line Wildfires Floods Mt. St. Helens WALLA Washington

3. slide 3 CLAC 2006 Institutional Planning Emergency planning exercises Systems/telecom an afterthought –Assumed to “just work” –Easy to set up Low budget priority for emergency infrastructure

4. slide 4 CLAC 2006 Ready for small-scale problems 2 server rooms –Separate power grids –Sufficiently distant Tape backups –3 off-site locations Redundant paths to Internet Most servers have remote backup

5. slide 5 CLAC 2006 Previous “attempts” Overly ambitious –Commercially co-located server –Hours of backup power –Too costly to justify –Poor follow-through Tulane University

6. slide 6 CLAC 2006 Refocusing Key technology goals –Provide information to the outside –Ability to locate people –Contact information for family members Personnel concerns –Where is the information? –Who is responsible? CLAC Survey

7. slide 7 CLAC 2006 City-wide mass casualty exercise

8. slide 8 CLAC 2006 First pass Emergency information web sites –http://emergency.whitman.eduhttp://emergency.whitman.edu –http://emergencyblog.whitman.edu/http://emergencyblog.whitman.edu/ –Basic hosting with commercial host DNS authority to ISP –Web-based DNS admin –Geographically distinct infrastructure No ERP solution in place –Text file to USB drive

9. slide 9 CLAC 2006 Where we’d like to be Co-located server at peer institution(s) Easier means for updating emergency page Better ERP solution Identify staff at peer institutions for IT help

10. slide 10 CLAC 2006 Survey on reciprocal hosting What does emergency hosting mean? What do you already have in place? Where would you like to be?

11. slide 11 CLAC 2006 Survey Results 12 respondents Desired solutions –Emergency Information –Mirrored ERP system –Email accounts Conclusions –No “one size fits all” solution –Grouping will be challenging –Define different levels of partnership –Security & liability issues

12. slide 12 CLAC 2006 Where do we go next? Consortially coordinated effort Peer to peer pairing ? Discussion list: clac_reciprocal@lists.whitman.edu