CIO Strategic Initiative: Cloud Enterprise Cloud Overview June 13, 2016 Monday 2:00-3:30 p.m. Smith 561

Agenda Meeting Purpose and Intended Outcomes Overview of HUIT Cloud Program CIO Council Strategic Initiative Workgroup Findings Enterprise Cloud Initiative Vision Next Steps

Meeting Purpose and Intended Outcomes The purpose of the meeting is to provide an overview of HUIT’s cloud program and to review the outcome of the Strategic Cloud Initiative workgroup. Provide an overview of HUIT’s Cloud Program Review the findings and outcomes from the Strategic Cloud Initiative workgroup Propose a vision for the Enterprise Cloud Initiative Review next steps

HUIT Cloud Program Overview February 2016 Cloud Liaison Committee formed to fill a migration backlog. PeopleSoft Dev environment resides in the cloud. June 2013 AWS Enterprise Support Agreement signed. October 2015 First draft of cloud service strategy created and shared with the HUIT community. July 2016 (PENDING) Cloud Firewall Implementation to support level 4 data in the cloud. Summer ‘14 Informal workgroup initiated to begin investigation of technology and processes needed to migrate on premise applications to the cloud. November 2015 Implemented DR for Aleph through CloudEndure, $20,000 saved annually over SunGard. April 2016 AWS cost optimization review results in IAM saving 22% monthly ($8,500) April 2017 (PENDING) PeopleSoft Prod environment resides in the cloud. June 2015 Qlikview, the first Production application, is deployed to AWS. March 2016 SOC and Program team migrate 42 applications from Campus Services via “L&S”. May 2016 Program team learns from the success of HBP and seeks to separate migration from architecture and operations support. PeopleSoft Test environment resides in the cloud. January 2015 Migration focused strategy to move 75% of existing and all new applications to the cloud. February 2015 HUIT Program is initiated. System Admins and DBAs transition from current role into the program. AWS selected as initial provider. January 2016 “Lift and Shift”migration method introduced to increase the pace of migrations. MIGRATIONS 522 400 300 200 31% of Goal 150 125 100 75 50 25 Feb ‘15 Apr ‘15 2016 Jun ‘15 Aug ‘15 Oct ‘15 Dec ‘15 Feb‘16 Apr ‘16 Jun‘16

Lessons Learned from the HUIT Cloud Program… 1 Get security and network design right before anything else 6 Don’t forget about cost management 2 Migrating to the cloud is just as much of a people initiative as a technical project 7 Do not turn all of the dials at once - it takes time to build a team, develop new skills, and learn new technologies 3 Reduce the amount of time staff is performing two jobs 8 Don’t be scared to change your strategy when new information presents a better way 4 Separate operations of cloud services from migrations from the start 9 Everyone is accountable for cloud, not just the migration team 5 Don’t build a program based on the potential of cost savings 10 Communicate successes and lessons learned openly and often

Enterprise Cloud Charge Enterprise Cloud Vision Strategic Cloud Initiative Workgroup The purpose of the workgroup is to identify Enterprise services that would improve the delivery of IT services, reduce costs, and minimize risks. Interviews Outreach CIO Higher Education Enterprise Cloud Charge Summary of Needs Enterprise Cloud Vision Key Stakeholders Cloud Vendors Discuss IT organization in the areas 1) current state of IT, 2) cloud services usage, 3) needs or benefits from cloud services Discuss current and prospective cloud services for the higher ed community Analyze needs to identify commonalities that can reduce costs, minimize risks, or improve IT services 6

Who Participated in Project Commencement 5/26 7

What we heard ... On Storage… On Cloud Hosting... “We need a place to keep it, not delete it” “Video is haunting us” On Cloud Hosting... "We do not not want to manage infrastructure" “We are looking to deploy a new research cluster” “We want to lower the activation barrier of use” On Cloud Education… "We would be interested in a "FAQ" style cloud guidance that clearly translates what solution to deploy for a specific purpose” On Disaster Recovery... “Disaster recovery is non existent and is a main driver for cloud” Commencement 5/26 On Data Center Replacement... "We would like to shed our data center in 4-5 years” “We are at the crossroads ready to think about major replacements for our data center “ On Cloud Security… "We would like to see FISMA compliant solution and believes that Harvard has the opportunity to be a leader in higher ed if we could solve this problem." 8

Self-Service Provisioning Data Center Replacement Summary of Needs Cloud Security Hosting Key Storage Training/Education Migrations HA/Failover HIGH Fileshare BC/DR Data Archive Research Computing Big Data Self-Service Provisioning Video Storage SaaS Training PaaS Architecture Backup App Migration Data Center Replacement (Reduce Cost, Minimize Risk, Improve IT Services) Value FISMA Consulting HIPAA HRCI LOW LOW Complexity (Effort to implement + Technical complexity + Barrier to adoption) HIGH

Key Findings from Industry and Higher Ed Top 5 reasons Higher Ed moves to AWS Cloud in Higher Education 1 Scalability and resiliency Cloud Adoption: Leader Areas of Focus Notre Dame is a leader in the adoption and implementation of cloud services. 54% of their applications in the cloud. Strategically addressing cloud storage and big data. 2 Disaster recovery Closing DC Transformation 3 Research Scalability 4 Mission critical workloads 5 Big data Cloud Adoption: Established Areas of Focus Cornell has a team supporting replatforming applications into the cloud. Their migration approach is focused on transforming traditional applications into platform independent PaaS containers. “Cloudification” Industry App portability Cloud agnostic “It starts with culture, not with how you move.” Biggest challenge is move Capex to Opex. Lift and shift for initial savings, and then start optimizing the applications. Ann Merrihew Sr. Manager, US Education Cloud Adoption: Emerging Areas of Focus Yale is developing a self-service portal to streamline delivery of cloud services. Additionally, they have implemented a cloud archive service for their on-premise data. DC Consolidation Shutdown of corporate data centers Automation and continuous optimization and cost reduction Self-service Data Management

Enterprise Cloud Initiative Vision Our Vision for the Enterprise Cloud Initiative Provide common, simple, cost-effective, and secure cloud services to enable the enterprise to shift University IT resources to a higher value-added purpose. Streamline the delivery of cloud services through self-service and automation Ensure Harvard’s cloud applications and data are maintained securely Manage the ongoing usage and associated costs associated with cloud services Establish shared services to reduce the ongoing management, costs, and discovery effort associated with silo projects Provide consolidated monitoring and operational support for applications to improve event responsiveness and correlation Strategic Objectives We prefer to buy or broker cloud services over building our own. We will provide the opportunity to adopt innovative cloud solutions supported by the best positioned School We will assess University-wide viability and ascertain clear value for any centralized service prior to implementation efforts We will actively seek out cost reduction and optimization solutions We will avoid vendor lock-in and ensure safeguards are in place to prevent unnecessary risk Guiding Principles % reduction in time to market for new application environments or access to IaaS resources by developers % reduction in the number of security findings in annual IT audits Reduction in service OpEx over on premise deployed solutions Reduction in number of disparate IT operational solutions % increase in the uptime of critical IT services during upgrades, crisis, or maintenance Key Performance Indicators

Next Steps Propose the establishment of a program to implement vision Establish governance model Create a program strategy and implementation plan Identify funding need and create FY17 ITCRB request Identify viable service opportunities based on Summary of Findings and CIO Council discussion Review potential partnership opportunities for each service with CIO community Conduct and assess pilots Build financial cases for potential services Communicate progress and report against the plan Ongoing outreach to CIOs to share their cloud transition progress

Thank you!