1. An Overview of the Workday Project Last Updated February 2011

2. Todays Goals Today we will: Share driving forces leading to the decision to partner with Workday. Review some of Workdays product features. Provide an update on the Workday Project. Address your questions and comments.

3. Background Information: Driving Forces Why are we undergoing a major system project? What are the driving forces?

4. Data access … Aligned systems … Less transaction time Background Information: Driving Forces Today:

5. Data access … Aligned systems … Less transaction time Background Information: Driving Forces Today: Many hands involved – duplication of effort Multiple disconnected systems – PeopleSoft, HR Online, Leave Accrual System, Taleo, custom shadow systems, etc. Decision makers lacking the information (ex. Salary Improvement Program) Costly to operate Cornell is about Learning, Discovery, Engagement

6. Background Information: Driving Forces 1 Data access: Cornell community members have real time information at their desktops to answer their questions. 2 Aligned systems: There is one system for all HR/Payroll activities (hiring, performance reviews, etc.) that talks to other Cornell systems (Taleo, Kuali, etc.) Resources are shifted from administrative/data entry tasks to enhanced support for faculty and staff. 3 Less transaction time:

7. Why Workday What is different about Workday?

8. What is Workday Workday at a Glance Founded by Dave Duffield 62, MBA 64 and Aneel Bhusri Provide web-based Software-as-a- Service (SaaS) solutions for HR, Payroll and Finance systems A next generation provider with: o 194 Customers (Georgetown University, first higher education customer as of July 2010) o 522 Employees Source: Workday

9. One HR/Payroll system to be integrated with Kuali, Taleo and various other Cornell systems (including other existing PeopleSoft applications) Why Workday Source: Workday Data access … Aligned systems … Less transaction time 1

10. Workday Key Features: HRMS/Payroll Applications Source: Workday Data access … Aligned systems … Less transaction time Designed for, accessible by a variety of users (via web/mobile) 2

11. Workday Key Features: HRMS/Payroll Applications Source: Workday Data access … Aligned systems … Less transaction time 4 Accessible, real-time reports/data 3 Workflow enabled (routing of info)

12. Data access … Aligned systems … Less transaction time Background Information: Why Workday – Driving Forces Tomorrow: Systems talking to each other

13. Why Workday What is Software-as-a-Service? What are the benefits of Software-as-a-Service?

14. Why Workday– SaaS Value Source: Wikipedia What is SaaS? Software as a service (SaaS), sometimes referred to as cloud technology is: Software that is deployed over the internet and/or run behind a firewall on a local area network or personal computer; A provider of licenses to an application, through a subscription or a "pay-as-you-go" model.

15. Why Workday– SaaS Value Source: Business Case document presented to ITCG (Aug 2010) Projected Lower Total Cost of Ownership

16. Background Information: Why Workday– SaaS Value Source: Workday New Product Releases – The Pace of Innovation (SaaS) 123456789 10 11 12

17. The Project How and when will Workday be rolled out? How will campus be involved?

18. The Project Structure

20. The Project: Initial Planning Timeline *DRAFT Deployment Plan Under Review Q3Q4Q1Q2Q3Q4Q1 201020112012 Design Stage Deploy Plan Stage Tentative Go-Live Checkpoints Build Test Stage We are here

21. What weve done »HCM, Benefits, Payroll Training »Determining steps & roles for HR processes/configuring the system »Integrations list & design »Initial prototype with Cornell data »Overview presentations to groups on campus What were doing to complete the Design Stage »Preparing Cornell data for our first data load into Workday »Configuration testing »Campus involvement in steps and roles for processes Design Stage Deploy Plan Build Test Project Update: Deployment Team

22. What weve done »Gathered inventory of pain points from HR and business leaders »Created parking lot of items generated from prototype development sessions »Prioritize according to design and configuration planning deadlines What were doing to complete the Design Stage »Identify issues requiring steering committee or sr. management review »Broaden campus involvement »Resolve deployment critical issues first »Establish system governance to review and approve post deployment optimization Design Stage Deploy Plan Build Test Project Update: Business Optimization

23. What weve done »Review of Position Management What were doing to complete the Design Stage »Review of the Job Requisition feature »Position Budgets and Commitment Accounting (integration with Kuali) »Job Requisitions »Multiple Jobs »iPEDs »Union Tracking Design Stage Deploy Plan Build Test Project Update: Strategic Advisory

24. Resources to Learn More 1.View the project website (http://www.hr.cornell.edu/wip/index.cfm)project website 2.Access short 5 minute demonstrations on the Workday website. Below are specific videos that may be of interest: Employee Experience Product Preview Manager Experience Product Preview Contextual Reporting Business Process Framework Performance Meets the Bottom Line Compensation Demo A full listing of demos is available at www.workday.comwww.workday.com 3.Email the project email box with your specific comments, suggestions, questions and concerns: projecthrms@cornell.edu.projecthrms@cornell.edu.