1

Common Management System – CMS“CMS Status & Future”

Financial Officers Association April 2004

“CMS Status & Future”

William GriffithVice President, Division of Administration & FinanceChair, CSU System-wide CMS Executive Committee

2

Common Management System – CMS“CMS Status & Future”

AGENDA

• “CMS 101”

• CMS System-wide Status

• CMS Benefits

• CMS Future & Challenges

3

Common Management System – CMS“CMS Status & Future”

“CMS 101”

Why Me?

William H. Griffith

Vice President of the Division of Administration & FinanceCalifornia State University, Long Beach

Chair, CMS Executive Committee

4

Common Management System – CMS“CMS Status & Future”

“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

Common Management System – CMS“CMS Status & Future”

“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

Common Management System – CMS“CMS Status & Future”

“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

Common Management System – CMS“CMS Status & Future”

“CMS 101”

Complicated Model

Central Chancellor’s Office

Campuses

Unisys

PeopleSoft

CENIC • Corporation for Education Network Initiatives in California

8

Common Management System – CMS“CMS Status & Future”

PeopleSoft

CSU Governance & Operational Model

Unisys

CENIC

“CMS 101”

ExecutiveVice Chancellor

Business & FinanceChief Financial

OfficerAssistant Vice

ChancellorInformation Technology

Services

Senior DirectorCommon

Management System

Hardware Operations Support & Services(HOSS)

Software Operations Support & Services(SOSS)

Application Project Directors

Human Resources Users

Group

Finance Users Group

Student AdminFunction Team

TechnicalUsers Group

CMS Campus Project Directors

CMS ExecutiveCommittee

9

Common Management System – CMS“CMS Status & Future”

2001 2002 2003 2004 2005 2006 2007 2008

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

CSU CMS SYSTEMWIDEDEPLOYMENT PLAN

HR Baseline

Finance Baseline

Student Administration Baseline

7/01 3/04 10/08

7/01 3/04 10/08

2/02 10/02 3/04 10/08

11 Campuses Live 21 Campuses Live 24 Campuses Live

11 Campuses Live 15 Campuses Live 24 Campuses Live

8 Campuses Live 23 Campuses Live

3 CampusesLive

5 CampusesLive

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

Common Management System – CMS“CMS Status & Future”

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

Common Management System – CMS“CMS Status & Future”

CMS System-wide Status

Financial Planning

Campus Financial Plans

Suggest Capital Project Treatment

Hard Budget Times

Loans are Possible

12

Common Management System – CMS“CMS Status & Future”

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

Common Management System – CMS“CMS Status & Future”

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

14

Common Management System – CMS“CMS Status & Future”

Time After Go-Live

Po

ten

tia

l Be

ne

fit

Efficiency, Effectiveness

& Service

Stage 4:Create New Capabilities

“Change the Game”

“Get It In”

Efficiency

Stage 1:ERP Go-Live

Efficiency & Effectiveness

Stage 2:IncrementalImprovement

“Get It Working”

Efficiency, Effectiveness

& Service

Stage 3:ExtendCapabilities

“Get Alignment”

SOURCE: CGE&Y

CSU is still in an

early stage of the cycle

CMS Benefits

15

Common Management System – CMS“CMS Status & Future”

Unisys Decision Point

Ongoing Support, Upgrades & Maintenance

Other Future Activities

Potential Banner Campus Collaboration

PeopleSoft and Oracle

CMS Future & Challenges

16

Common Management System – CMS“CMS Status & Future”

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

17

Common Management System – CMS“CMS Status & Future”

Questions?