Associate VP, Technology Strategy Cloud Seeding Progress and Lessons Terry Gray, PhD Associate VP, Technology Strategy UW Technology UTAC 30 October 2009
Premises Cloud computing is a big deal UW should encourage use of cloud services, consistent with compliance obligations Compliance risk is reduced via partner contracts A dual-vendor strategy is appropriate for UW Including faculty, staff and students maximizes collaboration potential
Progress MS and Google pilots successfully completed Contracts done (both vendors, covering fac/staff) Campus launch for students & alums (9/28/09) CSE launch for students, faculty, staff Planning for 2010 phase-out of student UA svcs (Per STF Committee funding decision)
Lessons Free services are not free Collaboration Barriers Pushback Moving targets, startup problems, service culture Cloud Conundrum: Integration adds value & cost Collaboration Barriers Multiple account madness Interoperability Pushback Students: “Where's the beef?” (vs. existing options) Faculty: privacy, security, data ownership/mining Help desk load: OK so far (no forced migrations yet)
Challenges Institution Concerns Individual Concerns Operational risk Financial risk Compliance risk Individual Concerns Service maturity Privacy Interoperability
Interoperability example: the calendaring problem Google Calendar User Outlook/ Exchange User IT Staff http://www.loc.gov/exhibits/bobhope/images/vcvg20.jpg
Preliminary Results 28 Sep – 26 Oct OL = Microsoft Outlook Live GA = Google Apps for Edu Accounts OL GA Students 1,800 3,400 5,200 Alumni Total 3,600 7,000 ← Alumni OL pilot launch Spring 2009 Email OL + GA EXTERNAL DESKMAIL TOTAL Students 2,500 25,000 22,000 50,000 OL=700, GA = 1,800
Preliminary Costs (all staff time) May-Sep Project Cost (Funded by deferring other projects) Outlook Live: $ 200K Google Apps: $ 50K Generic: $ 75K (UW Tech direct labor costs only; Does not include CSE or any other units)
2010 Plans Cloud Service Enhancement On-Premise Service Retirement Faculty / Staff launch SSO for Outlook Live Group management features Improved calendar interoperability Refine acceptable use policies On-Premise Service Retirement Student UA services (at least email) Central Exchange/Sharepoint services moving to Microsoft BPOS (dedicated, for fee) Progress gated by svc maturity & support cost Migration concern (no $ incentives to move) Often cheaper to leave existing servers running
Questions?