1 / 43

Welcome! Academics and Events in One Database:

Welcome! Academics and Events in One Database:. How publishing event data from a single source can enhance communication, minimize risk and assist in disaster preparedness. Tammy Miller Business Analyst / Application Administrator University of Idaho tmiller@uidaho.edu. Opened in 1892

gram
Download Presentation

Welcome! Academics and Events in One Database:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Welcome!Academics and Events in One Database: How publishing event data from a single source can enhance communication, minimize risk and assist in disaster preparedness

  2. Tammy Miller Business Analyst / Application Administrator University of Idaho tmiller@uidaho.edu

  3. Opened in 1892 Research-based, public land grant institution Main campus in Moscow, Idaho plus three branch campuses 12,000 students, including grad students

  4. Why store academic and special events together?

  5. Lots of great reasons Single source for event data: • Basis for master calendar • Accurate space utilization analysis • Know where people are congregated on campus • Avoid double-booking classroom space • Automate building controls and signage

  6. Academics integrated with Special Events in 2007

  7. Environment Changes over Time • Contracted for event scheduling software to be delivered via SaaS late 2009 • Upgraded to new event scheduling tool that includes calendar publication • Began creating event calendars for internal use: • Calendar for report production in RO • Calendar of smart rooms for Classroom technology group

  8. 2010 – The story behind this story

  9. It was a busy summer…

  10. I was on vacation…

  11. And sleeping soundly when…

  12. No chilled water was reaching the NOC

  13. July 2, 2010 in IdahoPipe break floods UI building with 6 feet of waterDamage in the ‘six-figure’ rangeMoscow-Pullman Daily News The University of Idaho’s J.A. Albertson Building is closed indefinitely after a nearby water line broke late Tuesday or early Wednesday and flooded the building’s electrical room with about 6 feet of water.

  14. Meanwhile, in another city in another state An application server stops functioning and doesn’t fail-over The server is restarted But University of Idaho Citrix permissions are somehow lost And in the morning, no one is able to sign in to the Events application

  15. Emergency + no data = very bad!

  16. What can we do…?

  17. We can leverage one of our new tools!

  18. Location calendars can serve as a source for redundant data: Application servers separate from Publisher servers (distinct data sources) Immediate access to event data Data can be easily communicated (shared)

  19. Constructing Location-based Calendars

  20. View what is happening in one room, on one floor, or in the entire building:

  21. Click on an event for details

  22. Select from all or any events to report

  23. Many options for data delivery!

  24. The data is shareable:

  25. Event detail in email:

  26. Download event data to another calendar:

  27. Key data elements in calendars that are critical to emergency response: Location Head count Event sponsor contact information

  28. Key elements of calendars useful for emergency management: Quick access to relevant data No time consuming queries or reports to produce Multiple ways to communicate the data

  29. Key elements of calendars useful for emergency management: Role in preparedness Role in response Role in recovery

  30. Expanding on the available key data:

  31. Add links to floor plans

  32. Add links to calendars for other buildings in proximity

  33. Event data flow and distribution:

  34. What makes these calendars private? Events are unfiltered, everything published Building plans are sensitive data Web search for URL is not activated Distributed to select audience Option to protect with password

  35. Issues with location calendars Data feeds are batched, not live Duplicate events occasionally created If event moves, old and new location listed Canceled reservations not always removed All campus events not accounted for

  36. How were location calendars received?

  37. Location calendar distribution: Registrar’s staff Building managers Building schedulers Landscape and Exterior Services Emergency and Security Services Facilities and Building Services

  38. Academic and Special Events in one place Many reasons for taking this approach – the most compelling are: • Ability to analyze space utilization • Ability to communicate where people are congregated on campus at any time

  39. Caveats Not all activities represented in event database Calendar data should be double-checked against a standard query or report run against the event data source Publishing calendars for emergency use might inspire you to become a first responder

  40. Be Prepared!

  41. Questions?

  42. Tammy Miller Business Analyst / Application Administrator University of Idaho tmiller@uidaho.edu

  43. Thank you!

More Related