1. UCCSC BIRDS OF A FEATHER: CLOUD SERVICES AT THE UC

2. The Cloud Opportunity Harness the power of consumer technology for teaching, research and administration (e.g. Google Apps, You Tube). Scale services massively up or down easily based on need (e.g. Amazon Web Services, ServiceNow). Move costs from a “CAPEX” to “OPEX” model for predictable spend based on consumption. Provide services that the community actually wants to use. Let vendors run commodity IT services that add no distinction, focus on the mission!

3. The Cloud Problem Each UC campus has hundreds of cloud services in use by faculty, staff, and students Sensitive UC data can go into services with poor security and privacy safeguards using “click through agreements” Campus units creating new forms of “shadow IT” in the cloud Campus IT can’t move fast enough to provide services to shift demand Cloud has to form a central part of IT strategy, but it’s often unclear how and when to move to or integrate cloud services

4. Some UC-wide Cloud Solutions Tap IT, security, procurement, legal, risk, compliance expertise to get better agreements with cloud vendors. Systematically identify and prioritize campus cloud computing needs Give campuses guidance on deploying cloud services Move faster, faster, faster!

5. Some Campus Cloud Solutions Create a delivery model in Central IT. Embrace the push from your constituents. Ruthlessly prioritize what IT services are important. Retire old services and offer new ones. Objectively prioritize what services to offer first, not based on the loudest voice Don’t let cost allocation issues stop you. Pay for it centrally or find your coalition of the willing. Privacy and security are hard issues, consider all the concerns but insist on taking a risk-based approach. Take some calculated risks, learn and grow from them!

6. UC Cloud Services Workgroup Charter Develop strategy for acquisition of cloud Services for UC enterprise – Define security, privacy, contract requirements Employ UC multi-discipline, multi-campus resources for Workgroup – Evaluate current state of Cloud Services usage – Identify UC enterprise requirements for Cloud Services Negotiate and issue agreements for Cloud Services for the UC enterprise – Design communication channels for implementation of Cloud Services for the UC Enterprise – Assist with implementation plans across all campuses

7. Workgroup Members Charged by the ITLC and CPO Bill Cooper: UCB, IT, TAS—David Willson UCD, Asst. CIO—Gabe Youtsey* UCI, CISO—Isaac Straley UCLA—Compliance Officer, Marti Arvin UCLA, IT, TAS—Tom Trappler UCM, IT, TAS—Gabe Edwards UCOP IT Policy—Stephen Lau UCOP, OGC—Kathleen Quenneville UCOP, Procurement—Dianne Yoder* UCOP, Risk Mgmt—Gary Leonard UCSD, IT—Brett Pollack *co-chairs

8. Services we are working on Service/CategoryUC-wide Contract HIPAA BAARequirementsDeployment Guide Box ✔ (I2) ✔ N/AJuly 2014 SalesforceJuly 2014 ✔ August 2014 Dropbox Google Apps ✔ N/A Azure ✔✔ N/A Office 365 ✔✔ N/A Amazon Web Svcs ✔ N/AAugust 2014 Endpoint Protection (e.g. CrashPlan, Druva) August 2014

9. Some Discussion Questions Do you have any questions about the work of the UC Cloud Services Working Group or other ITLC or Procurement groups related to cloud services?

10. Some Discussion Questions How can we work better as a UC system to provide cloud services in support of our common mission of teaching, research and service?

11. Some Discussion Questions What successes are you having on your campuses in rolling out cloud services and what are keys to that success? Any failures you have learned from?

12. Some Discussion Questions What cloud services hold the most promises for your campuses? What are fads that are fading? Some categories: – Educational technology – Research support – Infrastructure – End user services

13. Reach out anytime Dianne Yoder Asst. Director, Procurement Services UCOP 510-587-6496 Dianne.yoder@ucop.edu Gabriel Youtsey Interim Assistant CIO UC Davis 530-752-0701 gdyoutsey@ucdavis.edu