Progress Report

1
Progress Report

• The Sponsors Committee
• June 3, 2003

2
UF Bridges

• Goals
• Implement an ERP system to replace systems to be
  discontinued by the state
• Improve UF business processes by adopting best
  practices
• Methods
• Implement PeopleSoft systems - Finance, Human
  Resources, Payroll, Portal, Reporting, Student
  systems
• Browser-based systems hosted at the data center

3
Progress

• January 2002 July 2002
• - Vision Statement
• - Issued ITN
• - Evaluated Proposals
• - Scheduled Scripted Demonstrations
• - Started Negotiations
• - Formed Team

4
Progress

• July 2002-Dec 2002
• Select PeopleSoft
• Completed Conference Room Pilot
• Decision to implement Student systems
• Assemble team at Union Street Station
• Selected Implementation Partner
• Create System at the Data Center
• Jan 2003-June 2003
• Compete Business Analyses
• Begin Data Conversion
• Launch Web Portal

5
Next Steps

• July 2003 Dec 2003
• Final Design
• Final Configuration
• Final Computer Systems in Place
• January 2004 June 2004
• Parallel Operations
• Refinement
• Training

6
Important Dates

• March 31, 2003 New portal launched
• August 1, 2003 Reporting tools introduced
• May 1, 2004 New directory systems
• July 1, 2004 New Financial systems
• July 1, 2004 New HR and Payroll systems

7
Important Dates

• January 2006 Student Financial Aid
• March 2006 - Student Records
• May 2006 - Student Financials
• January 2007 - Student Admissions

8
New Student Systems

• Will provide access to data, flexible academic
  calendar, support for DCE, professional and
  graduate programs, integration with university
  systems
• Will significantly reduce the requirement for
  large mainframe systems at the data center

9
Changes in the Data Center

• The Data Centers infrastructure and operations
  demand and depend upon the integration of complex
  components - all of which must change.
• Platforms new hardware and software
• Processes adapt current, create new
• People - reassign/retrain existing, add new

10
Platforms must Change

• A mix and match of server hardware and software
  interoperate to build the PeopleSoft platform
  all of these components are changing.
• Network servers and Web servers
• Application servers and Database servers
• Storage servers and Backup servers
• Operating Systems OS/390 -------------gt
  AIX, W2K
• Transaction Processing CICS ----------------gt
  Tuxedo
• Database Management DB2 ------------------gt
  DB2
• Job Scheduling software home grown -------gt
  AppWorx
• Program Library software home grown -------gt STAT

11
Processes must Change

• Routine processes and standard procedures are
  required to run the PeopleSoft applications a
  few processes are new many are changing.
• Job Scheduling and Report Distribution
• System Backup and Recovery
• Database Administration and Security
  Administration
• Storage Management and Capacity Planning
• System Monitoring and Performance Tuning
• PeopleSoft Patches, Fixes, and periodic Upgrades
• OS and DBMS Patches, Fixes, and periodic Upgrades
• Business Continuity Planning and Disaster Recovery

12
People must Change

• During the project and for some time thereafter,
  additional staff will be required to support
  both the old and the new systems at the same
  time.
• Consultants will come and go.
• New People will be hired some will stay.
• Current Staff will be reassigned and retrained
  --
• A few will lead and blaze the trail for others.
• A few will choose to move on and out.
• A few will try but just wont make it.
• Most will follow and learn the way.

13

• UF Portal
• http//my.ufl.edu
• Project Web Site
• http//www.bridges.ufl.edu