An Overview of the Workday Project Last Updated February 2011

1. An Overview ofthe Workday Project Last Updated February 2011

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

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

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

5. Background Information: Driving Forces Today: Cornell is about Learning, Discovery, Engagement • 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 Data access … Aligned systems … Less transaction time

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.) 3 Less “transaction” time: Resources are shifted from administrative/data entry tasks to enhanced support for faculty and staff.

7. Why Workday What is different about Workday?

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

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

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

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

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

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

14. Why Workday– SaaS Value • 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. Source: Wikipedia

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

16. Background Information: Why Workday– SaaS Value New Product Releases – The Pace of Innovation (SaaS) 12 10 11 1 2 3 4 5 6 7 8 9 Source: Workday

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

18. The Project Structure

19. The Project Structure

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

21. Test Project Update: Deployment Team What we’ve 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 we’re 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 Plan Design Stage Build Deploy

22. Test Project Update: Business Optimization What we’ve 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 we’re 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 Plan Design Stage Build Deploy

23. Test Project Update: Strategic Advisory What we’ve done • Review of Position Management What we’re 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 Plan Design Stage Build Deploy

24. Resources to Learn More • View the project website (http://www.hr.cornell.edu/wip/index.cfm) • 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.com • Email the project email box with your specific comments, suggestions, questions and concerns: projecthrms@cornell.edu.