University of Florida ERP

1
University of Florida ERP

• Stakeholders Committee Meeting
• Wednesday
• February 26, 2003
• 200 PM
• Union Station Training Room

2
University of Florida ERPAgenda

• Introductions
• Vision Team
• Vision Statement
• Sponsor Committee
• Stakeholders Committee
• Advisory User Councils
• ERP Logo Project Name
• Project Organization
• Development Methodology
• Project Status
• Key Dates
• Questions

3
University of Florida ERP

• 33 Days Remaining for Portal Go-Live
• 155 Days Remaining for EPM Go-Live
• 490 Days Remaining for Financials Go-Live
• 855 Days Remaining for HR/PR Go-Live
• 1010 Days Remaining for Students Go-Live

4
University of Florida ERPVision Committee Members

• Anurag Agarwal
• Fred Cantrell, Chair
• Nur Erenguc
• Karen Fooks
• Chuck Frazier
• Sandy Goldstein
• Ken Hillier
• Joe Joyce
• Karen Kirkman
• Bill Montgomery
• Steve Pritz
• Mike Rollo

• Denise Stevens
• Denise Tanner
• Wayne Tharp
• Ken Tomlinson
• John Watson
• Scooter Willis
• Victor Yellen

5
University of Florida ERPVision Statement

• The University of Florida requires 10 systems
  with 10 systems integration
• 1) University Management
• 2) Vendor Relations
• 3) Human Resources
• 4) Payroll
• 5) Asset Management
• 6) Sponsored Programs
• 7) Student Administration
• 8) Instruction Value Chain
• 9) Technical Architecture/Infrastructure
• 10) Alumni and Friends

6
University of Florida ERPVision Statement

• The University of Floridas standard user
  interface is the ERP systems web portal.
• The University of Floridas self service
  transactions and financial transactions are
  processed by the ERP system.
• The University of Floridas master databases are
  maintained by the ERP system.
• The University of Florida numbering schema is the
  ERP systems numbering schema.
• The University of Floridas data dictionary is
  the ERP systems data dictionary.
• The University of Florida will eliminate the use
  of printed reports for management information.

7
University of Florida ERPUF Web Portal

• New service for the University community
• A single point of entry for university
  information and university work
• Will be available at http//my.ufl.edu
• Students registration, records, course
  materials, and student organization information
• Faculty scholarly information and news of
  research opportunities
• Staff information and system access relevant to
  their jobs
• UF home page will remain at http//www.ufl.edu

8
University of Florida ERP

• The University of Floridas standard user
  interface is the ERP systems web portal.
• The University of Floridas self service
  transactions and financial transactions are
  processed by the ERP system.
• The University of Floridas master databases are
  maintained by the ERP system.
• The University of Florida numbering schema is the
  ERP systems numbering schema.
• The University of Floridas data dictionary is
  the ERP systems data dictionary.
• The University of Florida will eliminate the use
  of printed reports for management information.

9
University of Florida ERP

• Combine Purchasing Accounts Payable
• Combine Human Resources Payroll
• Combine DSR Offices

10
University of Florida ERPVision Statement

• The University of Florida is to be self
  sufficient in providing user training and
  maintaining the ERP system.
• The University of Florida will adopt the ERP
  systems configuration tool set.
• The University of Florida will continue to
  support the Northeast Regional Data Center.

11
University of Florida ETRP

• A centralized ERP/PeopleSoft office will be
  established
• to maintain a help desk function, university wide
• training, security maintenance, installation of
  upgrades,
• fixes, compliance releases, application
  maintenance,
• etc.

12
University of Florida ERP
13
University of Florida ERPSponsor Committee

• The Sponsor Committee is composed of a select
  group University of
• Florida Vice presidents. The key responsibilities
  of the Sponsor Committee
• are to support the ERP process at the highest
  administrative level in the
• following manner
• Allocate and develop resources
• Support the Stakeholders Committee
• Resolve disputes
• Evaluate priorities
• Review progress
• Monitor transition of full University community

14
University of Florida ERPSponsors Committee

• Doug Barrett
• David Colburn
• Charles Frazier
• Mike Martin
• Win Phillips
• Ed Poppell, Chair
• Mike Rollo
• Charles Young

15
University of Florida ERP
16
University of Florida ERPStakeholders Roles

• The Stakeholders Committee is comprised of a
  select group of University of Florida
• executive management and key thought leaders
  from the university community.
• The key responsibilities of the Stakeholders
  Committee are
• Act as the steering group for the ERP project
• Guide the implementation via critical decision
  making and broad directional visioning
• Formulate strategies that will ensure the ERP
  installation is on time
• Formulate strategies that will ensure the ERP
  installation will serve the requirements of the
  University
• Evaluate and recommend business process redesign
  to afford the university the most efficient,
  effective and economical business practices

17
University of Florida ERPStakeholders Committee

• Anurag Agarwal
• Tony Brennan
• Fred Cantrell, Chair
• Jimmy Cheek
• Jim Crawford
• Chuck Frazier
• Paula Fussell
• Ken Hillier
• Marc Holt
• Joe Joyce
• Gary Koehler
• Charles Koenig
• Kathy Long
• Robert Miller

• Bill Montgomery
• Denise Stevens
• Denise Tanner
• Wayne Tharp
• Ken Tomlinson
• Chris Wadill
• Tom Walsh
• John Watson
• Victor Yellen

18
University of Florida ERPStakeholders Committee

• Ex Officio
• Nur Erenguc
• Functional Owner Liaison to the Stakeholders
  Committee
• Larry Ellis
• Karen Fooks
• Emily Hamby
• John Kruczek
• Steve Pritz
• Mike Rollo
• Tom Thomas

19
University of Florida ERP
20
University of Florida ERPAdvisory User Council
Role

• Goals
• Communicate Status
• Solicit Advice
• Cross Application Integration Issues
• Receive PS End-user Training
• AUC Contributions
• Future State Business process
• Workflow
• Security
• Reporting/Query Development
• User Based Training

21
University of Florida ERPAdvisory User Council
Workgroups

• Design
• Reporting
• Testing
• Training

22
University of Florida ERPAdvisory User Councils
Meeting Schedule
23
University of Florida Bridges ProjectLogo
24
University of Florida Bridges ProjectOrganization
al Structure
25
University of Florida Bridges ProjectMatrix
Organizational Structure
26
University of Florida Bridges ProjectMethodology
Overview

• P-A-T (Phase Activity- Tasks)
• Planning
• Fit/Gap
• Design
• Enhancements/Data Conversion
• Development
• Testing
• Training
• Deployment
• Post Implementation Stabilization

27
University of Florida Bridges ProjectCurrent
Project Status

• Scripted Demos
• PeopleSoft Purchase
• Conference Room Pilot
• University Implementation
• Hardware Installed
• Identified Current Interfaces, Feeder,
  Reports
• Developed Project Work Plans
• Continuing PeopleSoft Training Classes
• Documented Current/Future Business
  Processes
• Conducting Fit/Gap
• Conducting Configuration

28
University of Florida Bridges ProjectImplement
Vanilla
29
University of Florida Bridges ProjectKey Dates

• Portal - Mar/Apr 2003
• EPM - July/Aug 2003
• Financials - July 1, 2004
• HRMS/PR - July 1, 2004
• Jan 1, 2005
• Student - July 1, 2006

30
University of Florida Bridges Project

• Questions

31
University of Florida Bridges Project

• Approve Organizational Approach
• Approve Project Approach
• Approve the Project Logo
• Approve Meeting Schedule

32
University of Florida Bridges Project
33
University of Florida Bridges Project
34
University of Florida Bridges ProjectMeeting
Schedule Last Wednesday of the
Month

• March 26, 2003
• April 23, 2003
• May 28, 2003
• June 25, 2003
• July 30, 2003
• August 27, 2003
• September 24, 2003
• October 29, 2003
• November 26, 2003
• December 17, 2003

• January 28, 2004
• February 25, 2004
• March 31, 2004
• April 28, 2004
• May 26, 2004
• June 30, 2004
• July 28, 2004
• August 25, 2004
• September 29, 2004
• October 27, 2004
• November, 24, 2004
• December 29, 2004