1. ADMINISTRATIVE SYSTEMS Information Session Tuesday, March 26, 2013

2. PRESENTATION OVERVIEW 1.Project Status – Overview – UCPath – Biweekly Pay – Kronos – Financial System 2.Comments 3.Questions

3. MASTER TIMELINE

4. UCPATH

5. UCPATH: GOAL ImplementShare Oracle/ PeopleSoft Human Capital Management System Payroll & HR BusinessProcesses Riverside Service Center Standardize across UC A UC system-wide project to streamline and standardize payroll and human resources processes across all UC locations.

6. UCPATH: STATUS Design Phase Complete The design phase was finished in December of 2012. Biweekly Pay Transition Nonexempt employees transitioned to biweekly pay in January. Transition Assistance Program Loan repayment via payroll deduction began March 13. Project Schedule The wave 1 go live date is July of 2014. UCSB’s go live date will be announced soon.

7. BIWEEKLY PAY

8. SYSTEMWIDE CONVERSION The biweekly conversion was a first step in preparing for UCPath.

9. JANUARY 2013 PAY (Nonexempt)

10. TRANSITION ASSISTANCE 661 loans granted (up to $1,000) 389 vacation cash outs processed (up to 80 hours) Loan application period extended through February 27, leading to 50 more applications.

11. TRANSITION ASSISTANCE Loans and vacation cashouts were issued on the February 1 paycheck. Extension loans were issued as applications were received throughout February. The first loan repayment deductions were made on the March 13 paycheck.

12. BIWEEKLY RESOURCES www.pmo.ucsb.edu PPS Preparer Toolkit Info Session Presentations Calendars Calculators Biweekly Timecard

13. FACTOR LEAVE ACCRUAL Standardizing leave accrual is a part of UCPath. Factor Leave Accrual was effective: – January 20, 2013 for Biweekly Nonexempt staff – February 1, 2013 for Monthly Exempt staff

14. WHAT IS FACTOR LEAVE? A pre-set, standardized factor that is multiplied by the number of hours on pay status during the pay period to achieve the leave accruals. Biweekly pay periods have 160 possible working hours Monthly pay periods vary, depending on the calendar month (160, 168, 176 or 184 hours)

15. FACTOR LEAVE RESOURCES www.pmo.ucsb.edu Overview Worksheets Calculations

16. KRONOS TIMEKEEPING

17. KRONOS: GOAL PaperOnline Access Anywhere Track Edits Electronic Storage Automatic Export Whiteout File Cabinet Manual PPS Input Implement Kronos as the official campus timekeeping system

18. KRONOS: STATUS Advisory Committee MSOs from academic and research departments are helping to standardize business processes and plan the deployment. Resources We are hiring a resource coordinator and contracting for more Kronos support services. Variable Multiple Funding Sources A potential solution is being tested now. The advisory committee will review it to determine whether it fulfills requirements.

19. FINANCIAL SYSTEM

20. FINANCIAL SYSTEM: GOAL Implement PeopleSoft Financials Get off the current mainframe Business Process Review MAJOR EFFICIENCIES Reporting Real- time Transparent

21. PHASE 1 DELIVERABLES In October of 2013, you will not notice major changes. The risk associated with the mainframe will be mitigated.

22. PHASE 1 SCOPE General Ledger (G/L) Chart Of Accounts (COA) Purchasing Interface from Gateway Accounts Payable (A/P) Budget Ledger (Commitment Control – KK) Asset Management (AM) Project Costing (PC)

23. PHASE 2 SCOPE Accounts Receivable Grants Contracts Billing

24. PHASE 1 TIMELINE PHASE 1 TIMELINE (Phase 1: October 2012 – October 2013) Discovery Oct-Nov 2012 Project Kick-off Project Charter Fit Gap Analysis Configuration Jan 2013 Configuration Documented Basic Conversions Extensions Mar 2013 Workflow Development Data Conversions System Integration Testing Adaptions Mar-Jun 2013 Develop Interfaces Reports Development User Acceptance Testing Deployment Jun-Sept 2013 User TrainingSecurityDeployment Data Migration

25. WHERE ARE WE NOW? Completed Unit Testing Tested the base configurations of each PeopleSoft Module. Teams “tried breaking” the module’s configuration. Failures during this testing required the base system configurations to be adjusted to meet UCSB requirements.

26. WHERE ARE WE GOING? Complete System Configuration 1.Functional Specifications 2.Technical Specifications 3.Develop Interfaces, Reports, and Convert Data 4.Complete System Configurations!

27. COMMENTS

28. QUESTIONS