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 Account Manager
o Doug Gosnell Engagement Director
o Abhijeet Patil Project Manager
o Rohit Srivastava Solution Architect
 Background & Objectives
Project Business
Background Benefits
This project supports the
OneMontclair ERP Program at Solution
MSU specifically focused on Components Enable Better Controls
Transformation in the Financials PeopleSoft 9.2
area.
Business process improvement Implementation | Support Improve Visibility
cannot be readily supported by
the current platforms.
Conference
Workarounds and labor- Improve Operational
Room Pilots
intensive efforts are often SME | End Users Efficiencies
required to perform basic
university business functions.

Obtaining management
Change Mgt. Improve Productivity
information is difficult and time and
consuming. User Training
SME | End Users

Improve Reporting
Current FRS system is no longer
supported by the primary
vendor and is limited to only
regulatory updates
 Financials Transformation Roadmap
Set the Implementation Project
Foundation Scope
Extending the
Boundary
Institutionalize the Transform
New Chart of ed
Accounts and PeopleSoft
Finance System Phase 2:
Financials
Define New Chart Implement Applicatio
of Account following 6 n
Structure Phase 1: PeopleSoft
Implement following modules
11 PeopleSoft eSupplier
Phase 0: modules
Define New Chart of connection
General Ledger eSettlement
Accounts Structure Commitment Strategic
Control Sourcing
Accounts Payables Asset
eProcurement
Management
Purchasing Travel &
Receivables
Expenses
Billing
(including
Cash Management
Mobile
Project Costing
Integration)
Grants
Contracts
 Approach
Product Implementation
ERP products are based on Industry Best
Practices reflecting a vendors 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
Start Up and Build
Design

Schedule and Conference Room Pilot Configure Business Processes

Plan Finalize Design Develop Interfaces, Data
Conversions and Reports

01/2015 3/2015 4/2015 7/2015

System User
Integration &
Performance Training Acceptance
Testing Testing (UAT)
Go
Power & End User
Live!
Independent System Business Validation of
Validation Training on MSU System
configured 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 Reduce risk
Reduced Rework Reduced scope creep
Solution buy-in; early often Reduced ramp up latency
See to believe
 Conference Room Pilot (CRP) -
Iterative
June Sept Jan
14 14 15

Purpose
A first view of the PeopleSoft Application and basic flows to the MSU
CRP 0
SMEs.
Basic Business process cycles will be run with MSU master data and
CRP 1
the configuration impact showcased to MSU SMEs.
Business process cycles will be run with MSU master data and any
CRP 2 significant RICEW components built to address business gaps will
also be shown to the MSU SMEs.
Project Phase 1 -
Timeline
 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
People Quality Assurance built into the methodology
Communication
Effective Change ManagementEarly
Plan and Often
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 April 14
Meetings
Begin building Project Plan April 14
Prepare for CRP 0 April 14
Deliver University wide Kick-off April 14
Sample values for Chart of May 14
Accounts
Begin building Change May 14
Management Plan
Begin Interface and Conversion May 14
Strategies
CRP 0 begins June 14