Common Management System – CMS “CMS Status & Future” 1 Financial Officers Association April 2004 “CMS Status & Future” William Griffith Vice President, Division of Administration & Finance Chair, CSU System-wide CMS Executive Committee

Common Management System – CMS “CMS Status & Future” 2 AGENDA “CMS 101” CMS System-wide Status CMS Benefits CMS Future & Challenges

Common Management System – CMS “CMS Status & Future” 3 “CMS 101” Why Me?  William H. Griffith Vice President of the Division of Administration & Finance California State University, Long Beach Chair, CMS Executive Committee

Common Management System – CMS “CMS Status & Future” 4 “CMS 101” Why CMS?  Financial System Replacement  No System-wide HR System / SCO 21 st Century Project  SA Products Varied Greatly  Support from Legacy Vendors Ending  Integrated Technology Strategy  Value and collaboration

Common Management System – CMS “CMS Status & Future” 5 “CMS 101” Initial CMS Objectives  Integrated Software Suite vs. Best of Breed  Voluntary Collaborative  Common Baseline Software  modify once, not 23 times  Single Maintenance Organization  Shared Data Center(s)  Common hardware, operating systems, and data base software  Campuses have separate databases, not one large database  Minimize Modifications  Flexibility in:  meeting unique campus needs  implementation  Administrative Best Practices

Common Management System – CMS “CMS Status & Future” 6 “CMS 101” What is CMS Today?  PeopleSoft - Human Resource, Student, Finance  Mandated System  Common Baseline Software  Single Maintenance Organization  Single Outsourced Data Center – Unisys  separate campus databases  Modifications: HR – 65, Finance - 41, SA - 61  Not an IT Project  Best Practices  Largest ERP in Higher Education

Common Management System – CMS “CMS Status & Future” 7 “CMS 101” Complicated Model Central Chancellor’s Office Campuses Unisys PeopleSoft CENIC Corporation for Education Network Initiatives in California

Common Management System – CMS “CMS Status & Future” 8  PeopleSoft CSU Governance & Operational Model Unisys CENIC “CMS 101” Executive Vice Chancellor Business & Finance Chief Financial Officer Assistant Vice Chancellor Information Technology Services Senior Director Common Management System Hardware Operations Support & Services (HOSS) Software Operations Support & Services (SOSS) Application Project Directors Human Resources Users Group Finance Users Group Student Admin Function Team Technical Users Group CMS Campus Project Directors CMS Executive Committee

Common Management System – CMS “CMS Status & Future” 9 CMS System-wide Status CMS Deployment Timeline and Campuses Implemented to Date For Finance 8.4 Upgrade: 2 Campuses Live 1 Campus Will be Live Next Week 20 Campuses will Live on 8.4 by End of 2004

Common Management System – CMS “CMS Status & Future” 10 CMS System-wide Status Between 2005 and 2008: HR 3 campuses to implement Finance 4 campuses to implement SA 15 campuses to implement Known Upgrades Finance version 8.8 (approximately 2005) version 8.4 support ends 2 nd /3 rd quarter 2006 HRSA version 8.9 (approximately 2006) version 8.0 support ends 3 rd quarter 2007

Common Management System – CMS “CMS Status & Future” 11 CMS System-wide Status Financial Planning Campus Financial Plans Suggest Capital Project Treatment Hard Budget Times Loans are Possible

Common Management System – CMS “CMS Status & Future” 12 CMS System-wide Status JLAC Audit Audit Timetable Audit Theme Difference in Vision Politics Changes in How We Do Business: Defined Core & Non-Core CMS Functionality Formal Procurement Policies & Feasibility Studies Conflict of Interest Process Data Warehousing Regular Financial Project Reporting

Common Management System – CMS “CMS Status & Future” 13 Current Technology Increased Functionality Student Administration is area of biggest gain Web Enablement Self-Service Students Faculty Economics Standardization Efficiency & Effectiveness Better Planning & Management Information CMS Benefits

Common Management System – CMS “CMS Status & Future” 14 Time After Go-Live Potential Benefit Efficiency, Effectiveness & Service Stage 4: Create New Capabilities “Change the Game” “Get It In” Efficiency Stage 1: ERP Go-Live Efficiency & Effectiveness Stage 2: Incremental Improvement “Get It Working” Efficiency, Effectiveness & Service Stage 3: Extend Capabilities “Get Alignment” SOURCE: CGE&Y CSU is still in an early stage of the cycle CMS Benefits

Common Management System – CMS “CMS Status & Future” 15 Unisys Decision Point Ongoing Support, Upgrades & Maintenance Other Future Activities Potential Banner Campus Collaboration PeopleSoft and Oracle CMS Future & Challenges

Common Management System – CMS “CMS Status & Future” 16 In Summary: Collaboration is a Compromise by Definition Issues Exist and Need to be Fixed Big Challenges of Complexity, Capacity, and Communication On balance, Better Off Collectively than if Campuses had Implemented Separately CMS Future & Challenges

Common Management System – CMS “CMS Status & Future” 17 Questions?