1 / 17

Financial Officers Association April 2004 “CMS Status & Future” William Griffith

Financial Officers Association April 2004 “CMS Status & Future” William Griffith Vice President, Division of Administration & Finance Chair, CSU System-wide CMS Executive Committee. AGENDA “CMS 101” CMS System-wide Status CMS Benefits CMS Future & Challenges. “CMS 101”.

fidella-lerato
Download Presentation

Financial Officers Association April 2004 “CMS Status & Future” William Griffith

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. AGENDA • “CMS 101” • CMS System-wide Status • CMS Benefits • CMS Future & Challenges

  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

  4. “CMS 101” Why CMS? • Financial System Replacement • No System-wide HR System / SCO 21st Century Project • SA Products Varied Greatly • Support from Legacy Vendors Ending • Integrated Technology Strategy • Value and collaboration

  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

  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

  7. “CMS 101” Complicated Model • Central Chancellor’s Office • Campuses • Unisys • PeopleSoft • CENIC • Corporation for Education Network Initiatives in California

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

  9. 2001 2002 2003 2004 2005 2006 2007 2008 CSU CMS SYSTEMWIDE DEPLOYMENT PLAN Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 HR Baseline 11 Campuses Live 21 Campuses Live 24 Campuses Live 7/01 3/04 10/08 15 Campuses Live 11 Campuses Live Finance Baseline 24 Campuses Live 7/01 3/04 10/08 Student Administration Baseline 8 Campuses Live 23 Campuses Live 2/02 10/02 3/04 10/08 5 Campuses 3 Campuses Live Live 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

  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 2nd/3rd quarter 2006 • HRSA version 8.9 (approximately 2006) • version 8.0 support ends 3rd quarter 2007

  11. CMS System-wide Status • Financial Planning • Campus Financial Plans • Suggest Capital Project Treatment • Hard Budget Times • Loans are Possible

  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

  13. CMS Benefits • 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

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

  15. CMS Future & Challenges • Unisys Decision Point • Ongoing Support, Upgrades & Maintenance • Other Future Activities • Potential Banner Campus Collaboration • PeopleSoft and Oracle

  16. CMS Future & Challenges • 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

  17. Questions?

More Related