peoplesoft-financials-implementation

Report
Project Kickoff
PeopleSoft Financials
Implementation
April 2, 2014
Finance Team
o Montclair State University Team
o Donald Cipullo
CFO
o Edward Chapel
CIO
o Samir Bakane
Executive Director - OneMontclair
o Catherine Rush
Director of Financial Systems
o Frank Downing
Project Manager
o Cognizant Team
o Vasundhar Kolli
o Doug Gosnell
o Abhijeet Patil
o Rohit Srivastava
Account Manager
Engagement Director
Project Manager
Solution Architect
Background & Objectives
Business Benefits
Project Background
This project supports the ‘OneMontclair’
ERP Program at MSU specifically focused on
Transformation in the Financials area.
•
•
•
•
Business process improvement cannot
be readily supported by the current
platforms.
Workarounds and labor-intensive
efforts are often required to perform
basic university business functions.
Obtaining management information is
difficult and time consuming.
Current FRS system is no longer
supported by the primary vendor and is
limited to only regulatory updates
Solution Components
 Enable Better Controls
PeopleSoft 9.2
Implementation | Support
Conference Room
Pilots
 Improve Visibility
 Improve Operational Efficiencies
SME | End Users
 Improve Productivity
Change Mgt. and
User Training
SME | End Users
 Improve Reporting
Financials Transformation Roadmap
Set the Foundation
Implementation Project Scope
Extending the Boundary
Institutionalize the New
Chart of Accounts and
Finance System
Define New Chart of
Account Structure
Phase 0:
Define New Chart of
Accounts Structure
Phase 1:
Implement following 11
PeopleSoft modules
 General Ledger
 Commitment Control
 Accounts Payables
 eProcurement
 Purchasing
 Receivables
 Billing
 Cash Management
 Project Costing
 Grants
 Contracts
Phase 2:
Implement following 6
PeopleSoft modules
 eSupplier
connection
 eSettlement
 Strategic Sourcing
 Asset Management
 Travel & Expenses
(including Mobile
Integration)
Transformed
PeopleSoft
Financials
Application
Approach
“Product Implementation”
ERP products are based on ‘Industry Best Practices’
reflecting a vendor’s interpretation of the best/most
effective way to perform a business transaction.
 Product Implementation is the process of mapping
overall process vision to product capabilities
 Product can usually be configured for alternative
process flows thus avoiding customizations that add to
long term costs
 Business Process Definition and User Adoption will be
the key to overall success of the Implementation
Project Phases
4/2014
5/2014
11/2014
Assessment
Build
and
Start Up
Design
Schedule and Plan
01/2015
System Integration &
Performance Testing
Conference Room Pilot
Finalize Design
Configure Business Processes
Develop Interfaces, Data Conversions
and Reports
4/2015
3/2015
Training
7/2015
User Acceptance
Testing (UAT)
Go Live!
Independent System Validation
Power & End User Training on
MSU configured system
Business Validation of System
Conference Room Pilot
(CRP)
What is CRP?
Conference Room Pilot is a walk-through of business solution designs by core
project team members with key project stakeholders and SMEs.
Why CRP?
CRPs provide a forum to articulate the solution to enable business scenarios.
Benefits of the CRP
 Accelerated build
 Reduced Rework
 Solution buy-in; early often
 See to believe
 Reduce risk
 Reduced scope creep
 Reduced ramp up latency
Conference Room Pilot
June ‘14
(CRP) - Iterative
Sept ‘14
Jan ‘15
Purpose
CRP 0
A first view of the PeopleSoft Application and basic flows to the MSU SMEs.
CRP 1
Basic Business process cycles will be run with MSU master data and the
configuration impact showcased to MSU SMEs.
CRP 2
Business process cycles will be run with MSU master data and any significant RICEW
components built to address business gaps will also be shown to the MSU SMEs.
Project Phase 1 - Timeline
Phase
April
May
June
July
August
Sept
Oct
Nov
Dec Jan-15
Feb
March April
May
June
July
Aug
Sept
1234123451 234 12341234512 3412341234512341 234123451 23412341234512341234 1 23451234
Startup
Assessment
Design
Build
Data Conversion & Recon
SIT
Training
UAT
Go Live and Support
Post Production Support
CRP 0
CRP 2
CRP 1
Phase 2 Activities
April
May
June
July
August
Sept
Oct
Nov
Dec
Jan-15
Feb
March
April
May
June
July
Aug
Business Commitment
SME Time Usage Max 20-40 hrs per week
SME Time Usage High 15-20 hrs per week
SME Time Usage Medium 10-15 hrs per week
SME Time Usage Min 5-10 hrs per week
Sept
Critical Success Factors
Process
• Effective project plan accommodates University resource availability
• Risks and Issues identified and mitigated
• Program/Project Team continued focus on “OneMontclair”
• Measurable improvements to Business Processes
• Clear and usable documentation
• Quality Assurance built into the methodology
• Communication Early and Often
People
• Effective Change Management Plan
• Training delivered @ Point of Need
• Empowered Users able to define business process with minimal
customizations
• Enthusiastic & Supportive User Community
Technology
• Core System extensible for future capabilities
• Data – high transparency, “single source of truth”, improved
auditability
• Improved accessibility, automation & web integration (workflow,
mobile, e-processes)
Next Steps
Key Upcoming Activities
Month
Finalize Governance and Schedule Meetings April ‘14
Begin building Project Plan
April ’14
Prepare for CRP 0
April ’14
Deliver University wide Kick-off
April ‘14
Sample values for Chart of Accounts
May ’14
Begin building Change Management Plan
May ’14
Begin Interface and Conversion Strategies
May ‘14
CRP 0 begins
June ’14

similar documents