1 / 23

Data Quality in an Emergency Notification System

Data Quality in an Emergency Notification System. UCCSC Wednesday, June 17, 2009 1:30-2:30pm, 1003 Giedt Hall. Rev 3. Welcome!. Introductions Marian Sherrin Eric Goodman Audience Campus Alert System Status Statistics Collection Experience with Data Quality. Agenda.

dwayne
Download Presentation

Data Quality in an Emergency Notification System

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. Data Quality in an Emergency Notification System UCCSC Wednesday, June 17, 2009 1:30-2:30pm, 1003 Giedt Hall Rev 3

  2. Welcome! • Introductions • Marian Sherrin • Eric Goodman • Audience • Campus • Alert System Status • Statistics Collection • Experience with Data Quality

  3. Agenda • Data Quality Fundamentals • Building Data Quality Into the Project • Data Flows & Design Decisions Required • Results • Comparison to other Campuses • Questions and Answers

  4. Data Quality Fundamentals Keep the Goal in Mind!

  5. Building DQ into the Project Team Structure VC Student Affairs as team member helped with process and communication. We found it important to focus on Staff/Faculty and Students separately Chair: VC Vani Co Chairs: Chris Gaylord/ Doug Hartline Project Mgr: Marian Sherrin Chair: Biz Lead: Tech Lead: C:Marian Sherrin B:Alma Sifuentes T:Greg Gaither C: Naomi Gunther B:Cathy Schoenfeld/Nancy Degnan T: Bob Oberg C:Chris Gaylord B:Chris Gaylord C: Ed Titus T: Ed Titus/John Rudd C: Jim Burns Keep the Goal in Mind!

  6. Must Haves Set Data Quality Goals Early Keep the Goal in Mind!

  7. Desired Phase 1 Phase 1 Phase 1 NOT Req for Phase 1 NOT Req for Phase 1 Keep the Goal in Mind!

  8. High Level Project Timeline 3/21/08 4/2/08 6/1/08 7/1/08 July’08 July/Aug’08 Sept’08 Jan’09 May’09 T -2 T -1 T0 T1 T2 T3 T4 T6 T6 Student information collected Charge Letter Student and Non-University Contact Information collected with Fall Registration #2 Test of EOC and DOC Coverage #2 Campus Communication to Request for additional contact information Project Proposal Approved Campus Implementation Schedule Modifications made to AIS (if needed) Intercept July AIS Release New Student Orientation Contract Start date #1 Campus Communication includes request to update directory & CruzAlert Opt In Page for Staff & Faculty Project Charter Approved Student data mandatory for Winter’09 Phase 1 data transmitted to WARN #3Test of capability of email and cell SMS Required to improve data quality attributes: Accuracy Timeliness Validity Returning Student Communication Request for additional contact information #1 Test capability of office telephone systems Great opportunity to get to new students and their parents. New student cell phone completeness 85%! (returning students 4%) Returning student completeness rate increases from 4% to 98% (Cell – 83%, Landline 63%) (2% Opt Out) Keep the Goal in Mind!

  9. Student Screens Students choose type of phone Breaking into 3 boxes will help with validity, but format example has helped Students must validate information annually Opt-out capability was new

  10. Staff/Faculty Screens

  11. Staff/Faculty Screens Pre-populated with Name, Cruzmail address, and office phone You can change your office phone (without impacting directory info) or add a second one under Additional Phone Add your Cell phone for SMS/Text messages Home number may be used for campus closures Add an email in case CruzMail is out of service

  12. Data Flow Pinnacle Phone New: Campus Phones & Resident Hall Phones W.A.R.N. Broadcast RA DutyPhones New: RA Duty Phone AIS New: Opt Out Flag • New Extracts: • All Phones • All Work • All Home • All Cell WARN INCONNECT Currently Existed: Status & Data Identity Manager (also CruzMail ROO) CruzAlert Oracle Table PPS W.A.R.N. Command Only used high quality data: Employee Status Academic HR New New: RA Group Online Directory Student Housing

  13. Major Design Decisions • Student Workers – Count as students • Resident Advisors (RA) – Used SHO vs. PPS CTO Codes • RA Duty Phones – Manually load annually • Separations • From employment – Exclude via PPS • Graduation – Exclude via AIS • Dropping out, transferring – Exclude via AIS • Leaves, Sabbaticals, Temporary Assignments– Exclude • Summer Sessions/Non-degree– Include via AIS • Emeritus– Include (some still live on campus) • Sundry– Include (email only) • Visitors/Conferences – Include in Phase 2 – New Process • Parents – Not included in Phase 1 (students could use local phone)

  14. Key Actions Taken

  15. Completeness Actions From W.A.R.N. Command nightly • Annual Load All Campus Phones • Office • Reception • Hall • Classroom • Residence Halls • RA/CRE Duty Phones

  16. UCSC Results May 2009 Campus Population: 19,850 Active Students - 15,590 Employees - 4,260 Staff - 3,240 Faculty - 1,020 *100% covered by WARN Broadcast list covering ALL campus phones.

  17. Emergency Notification System Status (UC campuses)

  18. Methods & Results Methods Mandatory with Opt Out Opt In Hybrid UCSC Choice – Hybrid Mandatory for UC “owned” accounts/devices UCSC Email UCSC Networked Phones Student Residence Phones Mandatory with Opt Out Student phone contact via either: Cell/Mobile We create to WARN SMS Local Landline Employee Personal Data - Opt In Specific Office Phones Personal Cell phone We create WARN SMS Home/Alternate Phone Personal Email

  19. Methods & Results Methods Mandatory with Opt Out Opt In Hybrid UCSC Choice – Hybrid Mandatory for UC “owned” accounts/devices UCSC Email UCSC Networked Phones Student Residence Phones Mandatory with Opt Out Student phone contact via either: Cell/Mobile We create to WARN SMS Local Landline Employee Personal Data - Opt In Specific Office Phones Personal Cell phone We create WARN SMS Home/Alternate Phone Personal Email (1) 71% of staff/faculty specific phones in W.A.R.N. Command 100% of campus phones in W.A.R.N. Broadcast (2) Percent of total population, not just staff/faculty. (3) Source: UCR Larry L. Sautter Award Application, 2008 (4) Launch was April 2009.

  20. Key Takeaways • Understand Data Quality Fundamentals • Build Data Quality Into the Project • Keep the End in Mind • Teams • Goals • Schedule • Make the Right DQ Decisions • Measure Results • Continuously Improve

  21. Q&A

  22. Reference Sources • Larry P. English, Improving Data Warehouse and Business Information Quality, John Wiley & Sons, Inc., New York, NY. 1999 • DOD Guidelines on Data Quality Management (Summary), ~1997 http://www.tricare.mil/ocfo/_docs/DoDGuidelinesOnDataQualityManagement.pdf • Larry McGrath & Joel Nylander, UC Riverside Application for 2008 Larry L. Sautter Award, 2008

  23. Presenter/Contributor Biographies • Marian Sherrin • New to the University of California, Santa Cruz, in 2008. She was the Data Quality Manager for Intel’s Supply Chain Network from 1999-2005. • Eric Goodman • Joined the University of California, Santa Cruz in 1990. For the past several years has been the project manager of UCSC's Identity Management system.

More Related