1. URFinancials Project Project Review

2. Topics 2  The change from FRS (Financial Records System) to Workday  Software-as-a-Service (Saas) Cloud Solution via web  Easy and quick to implement configurations and adaptations  Scheduled 3x per-year updates (March, July, November)  Broad integration requirements and useful Best Practices  FRS implemented in 1984; need for more dynamics and flexibility  A partnership for growth  Workday provides software configuration and a link to developers  Deloitte provides implementation experience and Best Practices

3. Topics  Project Scope  Project Timeline & Methodology  Project Structure  Workday Overview  Challenges and Opportunities  Questions 3

4. Scope 4  Our primary focus is the elimination of high-risk financial information systems (FRS)  Team to recommend opportunities for business process improvement  Our implementation will be based on standard solutions  Chart of Account (COA) design and integration  General Accounting and Reporting  Fund Accounting / Post=Award Grant Management  Accounts Payable  Feedback is encouraged and welcome

5. Project Timeline & Methodology 5 Configure & Prototype Jun ‘13 Deploy July ‘14 Plan Jun ‘12 Test Nov ‘13 Architect Feb ‘13  Team Assembly  Charter  High-Level Plan  Team Training  Kick-Off  Initial Prototype  Design Workshops  Integrations Discovery  Design Review & Approval  Project Plan Update  Configuration Prototype  Unit Test, Validate Configuration  Build Integrations & Reports  Final Configuration Prototype  Create Test Cases & Scenarios  System Test  User Acceptance Test  Go-Live Check-list  Production Readiness Re-view  Go-Live  Post Production Support  Post Project Review

6. Project Structure 6 Executive Steering Committee Ron Paprocki – Exec. Sponsor Project Mgmt Team Doug Wylie, John Barden Jim Dobbertin – Project Manager Workday Product Advisory Group (with Georgetown, Brown, NYU, and Yale) Core Project Team (Phase 1) University Finance Advisory Committee General Ledger/COA Kathy Strojny /Patty Stevens Accounts Payable Marta Herman Grant Accounting Jeff Sullivan Support Teams (technical, deployment, communications, COA remediation) Functional Advisory Groups

7. Challenges & Opportunities  SaaS application concept – no customization but based on industry best practices  Internal resource allocation  Change management  Business process reviews and alignment  Organizational structure and job role definitions  Communications  Demonstrations, reviews and collaborations  Training  Chart of Accounts conversion  Potential for business process change prior to software implementation (reduce the variables required for go-live)  In-flight development of the software 7

8. Questions? 8 RoleNamePhoneEmail Project ManagerJim Dobbertin275-5768jdobbertin@finance.rochester.edu University ControllerDoug Wylie275-8567dwylie@finance.rochester.edu Associate CIOJohn Barden275-4900john.barden@rochester.edu G/L Team Co-LeadPatty Stevens785-5178patricia_stevens@urmc.rochester.edu G/L Team Co-LeadKathy Strojny273-1349kathleen_strojny@urmc.rochester.edu Accounts Payable Team Lead Marta Herman275-7880mrta@finance.rochester.edu Funds Accounting / Grant Mgmt. Team Lead Jeff Sullivan275-1648jpsullivan@finance.rochester.edu Technical Team LeadDoug Ryan273-2605doug.ryan@rochester.edu Find us at: www.rochester.edu/adminfinance/urfinancials

9. 9