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

2. Today’s Goals
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.

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:
Data access … Aligned systems … Less transaction time

5. Data access … Aligned systems … Less transaction time
Background Information: Driving Forces
Cornell is about
Learning,
Discovery,
Engagement
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
Is this university wide change a result of the need to reduce our operating budget, and what are the implications of leaving PeopleSoft?
Data access … Aligned systems … Less transaction time

6. 1 2 3 Background Information: Driving Forces 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
Is this university wide change a result of the need to reduce our operating budget, and what are the implications of leaving PeopleSoft?
Less “transaction” time:
Resources are shifted from administrative/data entry tasks to enhanced support for faculty and staff.

7. What is different about Workday?
Why Workday
What is different about Workday?

8. Founded by Dave Duffield ’62, MBA ’64 and Aneel Bhusri
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:
194 Customers (Georgetown University, first higher education customer as of July 2010)
522 Employees
Since this program was founded by the founder of People Soft, what are some of the advantages of workday over people soft?

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

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

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

12. Data access … Aligned systems … Less transaction time
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. Projected Lower Total Cost of Ownership
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) 1 2 3 4 5 6 7 8 9 10 11 13 12

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

18. The Project Structure
Why does Cornell want to go with this program since only one other institution of higher learning currently uses it?

19. The Project Structure

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

21. Project Update: Deployment Team
Plan
Design Stage
Build
Test
Deploy
What we’ve done
Attended HCM, Benefits, Payroll Training
Conducted business design workshops to determine steps & roles for HR processes/configuring the system
Established initial integrations list & design
Shared overview presentations to groups on campus
Sent Cornell data to Workday for our first data load into Workday
Data validation review of our first Workday Cornell environment
Configuration testing of our first Workday Cornell environment
What we’re doing to complete the Design Stage
Facilitate campus involvement via feedback session/demo of our first Workday Cornell environment (examine initial design of steps & roles)
Who: Laurie
Why: Give idea of our timeline, updates on project status for each effort
What:
Workday project methodology
Recognize from advanced materials
Iterative process throughout – building on prototypes
Dates
Planning for 1/1/2012 go-live – not finalized yet
Design stage – planning for mid-April – finalizing plans for iterations with campus – we’ll talk more about this in a few minutes
After we get through design phase and we determine our scope and resources, we’ll have a better feel for the timing for later phases - expect those dates to change
Stake in the ground at end of Design –
Definition of scope is a major outcome of the design stage
Lock on scope (note we still have the ability to adapt configurations later)
Checkpoints
Is the product ready?
Haven’t lost any functionality from current system
Configuration complete
Is Cornell technology to support it ready?
Integrations with campus systems – Taleo, Kuali FS, PS campus community, Kronos, etc.
Will depend on resources for our project as well as other projects
Is the campus ready?
Campus saturation
For each leg of the project, we’d like to provide a brief overview of what we’ve been doing & what we need to do to finalize the Design Stage
Deployment Update
Next slides:
BPO Update
Strategic Advisory Update

22. Project Update: Business Optimization
Plan
Design Stage
Build
Test
Deploy
What we’ve done
Gathered inventory of “pain points” from HR and business leaders
Created “parking lot” of items generated from prototype development sessions
Prioritized according to design and configuration planning deadlines
Established broaden campus team
Identify issues requiring steering committee or sr. management review
What we’re doing to complete the Design Stage
Resolve deployment critical issues first
Establish system governance to review and approve post deployment optimization
Who: Laurie
Why: Give idea of our timeline, updates on project status for each effort
What:
Workday project methodology
Recognize from advanced materials
Iterative process throughout – building on prototypes
Dates
Planning for 1/1/2012 go-live – not finalized yet
Design stage – planning for mid-April – finalizing plans for iterations with campus – we’ll talk more about this in a few minutes
After we get through design phase and we determine our scope and resources, we’ll have a better feel for the timing for later phases - expect those dates to change
Stake in the ground at end of Design –
Definition of scope is a major outcome of the design stage
Lock on scope (note we still have the ability to adapt configurations later)
Checkpoints
Is the product ready?
Haven’t lost any functionality from current system
Configuration complete
Is Cornell technology to support it ready?
Integrations with campus systems – Taleo, Kuali FS, PS campus community, Kronos, etc.
Will depend on resources for our project as well as other projects
Is the campus ready?
Campus saturation
For each leg of the project, we’d like to provide a brief overview of what we’ve been doing & what we need to do to finalize the Design Stage
Deployment Update
Next slides:
BPO Update
Strategic Advisory Update

23. Project Update: Strategic Advisory
Plan
Design Stage
Build
Test
Deploy
What we’ve done
Shared initial feedback on Position Management
Reviewed Job Requisition features, shared initial feedback
What we’re doing to complete the Design Stage and on-going
Position Budgets and Commitment Accounting (integration with Kuali)
Job Requisitions
Multiple Jobs
iPEDs
Union Tracking
Who: Laurie
Why: Give idea of our timeline, updates on project status for each effort
What:
Workday project methodology
Recognize from advanced materials
Iterative process throughout – building on prototypes
Dates
Planning for 1/1/2012 go-live – not finalized yet
Design stage – planning for mid-April – finalizing plans for iterations with campus – we’ll talk more about this in a few minutes
After we get through design phase and we determine our scope and resources, we’ll have a better feel for the timing for later phases - expect those dates to change
Stake in the ground at end of Design –
Definition of scope is a major outcome of the design stage
Lock on scope (note we still have the ability to adapt configurations later)
Checkpoints
Is the product ready?
Haven’t lost any functionality from current system
Configuration complete
Is Cornell technology to support it ready?
Integrations with campus systems – Taleo, Kuali FS, PS campus community, Kronos, etc.
Will depend on resources for our project as well as other projects
Is the campus ready?
Campus saturation
For each leg of the project, we’d like to provide a brief overview of what we’ve been doing & what we need to do to finalize the Design Stage
Deployment Update
Next slides:
BPO Update
Strategic Advisory Update

24. Resources to Learn More
View the project website (
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
the project box with your specific comments, suggestions, questions and concerns: