12
PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

Embed Size (px)

Citation preview

Page 1: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

PeopleSoft Financials 2009-10 Enhancement Plan

June 18, 2009

Page 2: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

2

Common Issues and Themes Purchasing card process Slow performance / response time of system Ad hoc reporting, data access Separation of duties, internal controls Procurement – match exceptions,

professional services, roles & responsibilities ISO & auxiliary activity, especially RAR and U

Stores Efficiency and workload on users

Page 3: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

3

What’s Working General ledger functions Sponsor reporting and invoicing Travel Treasury, cash, endowment functions Non-sponsored accounts receivable Budgeting Tuition and fees revenue accounting Vendor payment functions Debt and construction accounting

Page 4: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

4

FY 2010 Priorities Address Users’ issues:

Identify user issues Develop user priorities Evaluate alternatives for addressing issues Implement workable solutions

Continue to deliver hands-on support to users Helpline Training Services Central business units

Page 5: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

5

Identification of Issues

70+ issues identified by users (EFS Functional Steering Committee, FSUN, GMUN, Certified Approvers, RRC managers, etc) Purchasing Card Reporting Procurement Workflow / Separation of duties COA related System Performance Logistics HR / Workload

Page 6: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

6

Enhancement Methodology

Analyze Design Build Test

Gather / Analyze

Requirements

Create Functional

and Technical Designs

Build work object

Develop test

Conditions and scripts

Execute system test

Leverage OIT implementation project methodology

Page 7: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

7

Define Requirements

1.5- 2 hour sessions per category As many sessions as required Interactive discussion

Objectives Discuss issues and concerns Validate business requirement

Participants – 40+ Users FSC members or delegates FSUN members Certified Approvers GMUN members Department users

Page 8: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

8

Preliminary requirement classification

Page 9: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

9

DRAFT:Enhancement Rollout Gantt

Page 10: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

10

Ad Hoc Reporting There is a great need for:

Better access to data Better definition of what the data means User friendly tools to manipulate and

analyze data “Canned” reports cannot be the sole

solution to reporting Data warehouse solution

Page 11: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

11

Enhancement ProjectParticipation & Consultation

EFS Functional Steering Committee FSUN Board & membership Certified Approvers Resource Responsibility Center managers GMUN Board & membership Senate Committee on Finance & Planning Twin Cities Deans CRAD President & Senior VPs

Page 12: PeopleSoft Financials 2009-10 Enhancement Plan June 18, 2009

12

Next Steps

Complete requirements definition Continue working with users to finish prioritizing

issues Develop work plan and resource requirements for

enhancement effort Obtain senior executive approval for scope and

resources Begin design/policy sessions