UCSF HR: HUMAN RESOURCES AND ACADEMIC SYSTEMS REPORT TO CBT June 8, 2012

Update  Project Updates  Academic Personnel (AP) Recruit  HR Service Request System (SRS)  UCPath 2

Academic Personnel (AP) Recruit 3  Delivers a single application that supports multiple campus-branded recruit sites  Hosted, developed, and maintained by UC Irvine  Enables a standard, confidential online faculty recruitment process, including automation of the application and search committee review activities  Generates point-in-time reports on the diversity of the applicant pool as compared to national availability pools from similar disciplines  Governance: UCSF Steering Committee for Academic Affairs Information Systems Initiatives (SCAAISI)  Oversight for AP Recruit and Advance  Key milestones/timing  June 30 – AP Recruit installed at UCSF  July – Build/test interfaces  August – Train departments and service providers  September – Roll out to campus

HR Service Request System (SRS) 4  Designed, developed and delivered SRS – a service request initiation and tracking tool – in January, 2012  Conducted rolling implementation as the five service centers went live (January through May)  Post go live, we are gathering feedback and analyzing our experience with the tool  Will assess any required changes/enhancements to assure on-going improvement  Approved enhancements will be programmed beginning June/July  Long-term disposition pending scope of UCPath case management tool

UCPath Overview 5  Mandatory participation by all campuses  UCSF is targeting the third (final) wave – Oct 2014  Timeline may shift for Wave 1, which will impact subsequent waves  UCPath finalization of Waves 2 and 3 still in progress  Replaces the current payroll/personnel system (PPS) and introduces a new Human Resource Information System (PeopleSoft)  Migrates all payroll related transactional* work, majority of benefits administration and some human resources transactional work (TBD) to a system-wide shared services center at Riverside  Details around processes/handoffs still being worked out  UCPath service center’s principle liaisons are the local campus service centers across UC * Excluding fund distribution changes

UCPath Systems Scope: Current Status 6  Scope  Payroll (PPS replacement)  Benefits Administration  HR/Personnel Management ("Workforce Administration”)  Case Management  Knowledge Management  Data repository/data warehousing  Update mechanism of payroll activity to GL to capture labor/fund distribution  Generic and tailored interfaces (over 100) to key systems including Effort Reporting, Timekeeping, Financial Systems, Academic Personnel Systems, etc.  Specific scope details still being designed  Anticipate gaps in such areas as staff recruitment, appointment/fund change calculations, and GL integration

UCSF Engagement with UCPath To Date 7  UCPath led by UCOP PMO  UCSF representatives are serving on these UCPath Groups  Executive Steering Committee (Strickland)  Management Group (Odato)  UCPath Center Interim Advisory Board (Leathers)  Practices Board (Odato, Leathers)  Functional Design Teams (various)  Conference Room Pilots (various)  Input to Technical Documents (various)  The UCSF Working Group for UCPath comprised of representatives from above teams; meets monthly to identify and triage key issues coming out of UC Path  UCSF Ad hoc Executive Group led by Plotts and Strickland monitor status and executive level issues needing triage

UCPath Next Steps for UCSF 8  Continue to monitor/provide input  Once wave implementation dates are more final, gear up for implementation  Anticipate a month effort  Will include project funding requirements as part of business systems strategic planning  Form UCSF work/implementation teams to complete fit/gap and readiness activities  Form Executive Committee for strategic oversight