1 CMS PROJECT OVERVIEW February 22, 2007

2 Agenda Answering the “Big Questions” Project Deliverable Dates Project Timelines

3 The Big Questions….. What’s a Go Live mean? What drives when applications are released? What's different in an implementation and in an upgrade? What is “core” and “non-core” mean to the campus? How will this process continue on our campus? How do all the CMS pieces fit together?

4 CSUF CMS Project Goals Statement The CMS Project at CSU Fullerton seeks to accomplish the following goals as part of its implementation of the People soft application: – Resolve long standing or currently identified issues with business functions through process or technical developments – Map business processes and facilitate central and distributed change in business operations – Provide all campus users tools and applications capable of limiting the number of systems on campus used to perform business functions or those that house protected data – Provide all campus users (central and distributed) an opportunity to voice their concerns and suggestions for process improvement

5 CSUF CMS Project Spreadsheet Understanding the Sections for HCM, FIS, CS: A. CSU/Vendor Timelines Includes product releases and/or upgrades from software vendors. These are most frequently Oracle, but also includes File net, Data Warehouse, and Hyperion B. CSU Campus Upgrade Timelines Includes activity pre-release activities at CMS central and the pilot campuses C. CSU Fullerton Implementation and Upgrade timelines Includes the different baseline “core” (lt. blue) and “non-core” (pink) applications that are included in the specific application suite. Includes many of the campus “modifications” (pink) made to the core applications. Implementation periods are noted in yellow blocks, Upgrades in green blocks. These periods are estimates on future possible dates. Purple blocks indicate cross application (HR & CS) agreed to upgrade months D. Other Projects with Impact Includes major CSU and campus systems and projects with impact in the CMS application development

6 CMS Timelines: HRIS/HCM 8.9 Project HCM 8.9 Upgrade Timeline – HANDOUT

7 CMS Project Deliverable Dates HCM/HR 8.9 Go Live – March 19, 2007 Go Live Timeline – System prep and central testing March – View only access to the system available during this period – Web site for Go Live Transition In Classroom Training: – Timekeepers – Student Worker Processors Must attend training by April 6 th or access is suspended Additional Functionality under Consideration: – Absence Management Distributed – TBD (August 07) – Recruit Solutions – TBD (Dec 2007) – Benefits Administration – TBD (July 2008)

8 CMS Timeline: FIS 8.4 Project FIS 9.0 Upgrade Timeline – HANDOUT

9 CMS Project Deliverable Dates FIS 8.4 Go Live – July 1, 2007 Go Live Timeline – System prep and central testing April 2007 Implementations in Parallel – Cashnet.com – Revenue Management Program - Fees in Trust – Hyperion Reports CSUF Functionality under Construction: – Department Level Security – Requisition Entry – Budget Transfer – Recharges

10 CMS Timelines: CS/HCM 8.9 Project Possible HCM 8.9 to 9.0 Upgrade Path – HANDOUT

11 CMS Project Deliverable Dates CS 8.9 Go Live – August 2007 to June 2008 Go Live Timeline – Phase I – delivering current functionality in new system – Phase II – delivering additional feature sets Implementations in Parallel – Hobson's EMT – Student Prospecting and recruitment – Ad Astra / Schedule 25 – Classroom Scheduling software – DARwin – Degree Audit System Upgrade CSUF Functionality under Consideration: – Business Unit Decisions – Housing Charges and Payments – Waitlisting

12 CMS Timelines: Support System Projects Possible HCM 8.9 to 9.0 Upgrade Path – HANDOUT

13 CMS Project Deliverable Dates Data Warehouse Implementation – Phase I - June 2007 Utilizing campus custom ETL and views – HR 8.9, FIS 8.4, CS 8.9 – Phase II – TBD 2008 CMS central use of Oracle EPM – HCM 9.0 (HR & CS), FIS 9.0 PeopleSoft Portal – Phase I – August 2007 People soft portal tool selected Access to PS portal pages through Campus portal (.Net) – Will change existing HR Self Service – Will provide new student authentication for students

14 CMS Project Committees Application Committees – Reports Development Tool Selected – Hyperion Brio – Oct 06 Hardware & Tool Installation – Feb 07 Next Steps – Specification of required reports – Identification of system and access method – Support and Training Strategy – Forms Development Tool Selected – File net E-Forms - Nov 06 Hardware & Tool Installation – Feb 07 Next Steps – Enhancement of Forms for Go Live Dates – Support and Training Strategy – Migration of forms to new E-Forms