RIAS PHASE II
Oracle General Ledger, Financial Reporting
and Data Warehouse
3/15/2016
Agenda

Introductions

University’s Strategic Direction

RIAS Phase I Recap

RIAS Phase II Project Scope and Benefits

Project Organization and Staffing

Project Methodology

Communications and Training

Project Timeline

Critical Success Factors

Project Status

Next Steps
3/15/2016
RIAS Phase II
1
University’s Strategic Direction

University’s strategic direction





Rutgers Integrated Administrative System (RIAS) project
supports the University’s strategy


3/15/2016
Provide employees with tools and data to make better decisions
Provide an integrated financial/business system
Migrate from paper based to web based electronic business
processes
Streamline business processes to take advantage of best business
practices
Phase I Procure to Pay – July 2002
Phase II – Financial Accounting & Reporting
RIAS Phase II
2
RIAS Phase I Recap

3/15/2016
Procure to Pay Business Process

7 modules (Internet Procurement; Purchasing; Payables,
General Ledger, Human Resources, Inventory; Exchange)

Online requisitioning and approval routing

Elimination of 9 part paper purchase orders

Preferred suppliers with RU negotiated pricing on Exchange

Student Refunds and Employee Reimbursements

Internal Suppliers
RIAS Phase II
3
What is RIAS Phase II

Scope

Implement Oracle General Ledger module

Redesigned Financial Data Warehouse

Reporting Solution

Infrastructure Upgrades
3/15/2016
RIAS Phase II
4
What is RIAS Phase II

Oracle General Ledger

Implement full functionality of Oracle General Ledger module and
turn down of mainframe Financial Accounting System

Oracle GL will be University’s Official Set of Books

Online ability to create, change and approve journal entries, non
salary budget adjustments

Online approvals and routing of journal entries and non salary
budget adjustments using the requisition hierarchy

Eliminate paper journal entries and non salary budget adjustments
3/15/2016
RIAS Phase II
5
What is RIAS Phase II

Oracle General Ledger

Convert all remaining departmental purchase orders over to Internal
Suppliers

Online Financial Information System (OFIS) will remain for historical
reporting purposes and to support Budget System functionality

Customizations and extensions will be minimized

Provide a spreadsheet interface for importing and exporting data

Establish budgetary control and performing funds checking where
appropriate

Explore Mass Allocation functionality
3/15/2016
RIAS Phase II
6
What is RIAS Phase II

3/15/2016
Financial Data Warehouse

Redesign the financial data warehouse (FDW) to better meet the
University’s reporting needs

Architect a warehouse that will be scalable as additional modules
are implemented

Provide accessible information associated with Payables,
Purchasing and the General Ledger

Data Provisioning
RIAS Phase II
7
What is RIAS Phase II

Reporting Solution

Provide a more robust data warehouse and web-based reporting
solution

Standard reports (“certified”)

Standard reports with the ability to use parameters, change sorts

Ad hoc reporting

Drill down capabilities
3/15/2016
RIAS Phase II
8
What is RIAS Phase II

3/15/2016
Infrastructure

New hardware and new network

Upgrade operating system Solaris 8 – Solaris 10

Upgrade Oracle applications to version 11.5.10

Upgrade Discoverer to version 10g

Common Portal

Sign-on strategy

Security Extended Budget Responsibility Code (EBRC) will be used
to manage access to data
RIAS Phase II
9
Project Organization

Functional and Technical Teams

Oracle Consulting

Supporting Partnerships





3/15/2016
Project Management Team
Business Managers Group
Technical Advisory Group
Data Provisioning Partners
Supplemental Systems Committee
RIAS Phase II
10
Project Organization
RIAS Phase II Organization Chart
Executive Steering
Committee
Project Management Team
Director Enterprise
System &
Operations
Don Gordon
Associate
Director ESO
Tim Hayes
Associate
Director ESO
Bob Allen
Network &
Windows
Joni Squillaro
Associate
Director EAS
Bill Thompson
Project Manager
EAS
Glenn Oldis
Unix System
Administrator
Dmitry Berezin
Desktop
Support
John Lyons
RU DW DBA
John Radvanski
RU Apps DBA
Carl Lages
Key
Project Office
Functional Team
Technical Team
Oracle Team
Project Office
Director Enterprise
Application
Services
Joe Percoco
Program Director
Steve DiPaolo
Associate
Director EAS
Ellen Law
Project Managers
EAS
Dina Laurence
Marty Pepe
Reggie Greene
Application
Developer
Legacy Testing
RU Technical
Project Manager
Eileen Markey
Project Manager
Oracle
Ed DeVogelear
Technical Team
Lead
Sobhan Nandamuri
Oracle GL
Technical Lead
Bharat Patel
Oracle DW Lead
Russ Gilkeson
Application
Developer
Piyush Patel
Oracle Technical
Implementor
TBD
Oracle Architect
Mike Hennessy
Application
Developer
Meera Kadaba
Application
Developer/ System
Admin
Jery George
Application
Developer
Sue Gross
Project Admin.
Assistant
Joy Kerr
Oracle GL Architect
Ravi
Heggadadevankote
Project
Management Team
Supplemental
Systems Group
Data Provisioning
Partners
Technical
Advisory Group
RU Functional
Project Manager
Tim Stein
Oracle GL
Functional Lead
George Konefal
Data Warehouse/
Reporting Lead
Jim Mehalik
Report Developer
Oracle ETL
Specialist
TBD
Oracle Security
Architect
Roger Raj
Business
Managers Group
(BMG)
Grant Functional
Specialst
Linda Fowler
Oracle Report &
Data Access
Specialist
Ashish Kashalkar
Amit Bhatnagar
Grant Functional
Support
GL Functional Lead
Betsy Cafiero
GL Functional
Support
Budget Functional
Specialist
Mary Tamasco
Communications
Training, and
Change
Management
Ann Griffin
Trainer
TBD
End User
Functional
Support
Purchasing
Functional
Support
Oracle DBA
TBD
Application
Developer
Greg Martin
Consultant
Nirul Allahbaksh
3/15/2016
RIAS Phase II
11
Project Management Methodology

Issue Management


Documentation


JIRA will be used to track issues and action items
IProjects will be used as the document repository
Application Implementation Methodology (AIM) for General
Ledger implementation effort and Data Warehouse Methodology
(DWM) for Data Warehouse effort
3/15/2016
RIAS Phase II
12
Communication and Training

Developing a communication plan


Developing a training and change management strategy


Implement a communication hierarchy to allow two way
communication between the project management team and the
university
Prepare the university for a successful adoption of the new system
A variety of methods will be used to foster communications







3/15/2016
Website
FAQs
Newsletter articles
Demos
Campus visits
“Partnerships”
Surveys and Questionnaires
RIAS Phase II
13
RIAS Phase II Timeline
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
1st Q 2008
Requirements/Definition
Communications/Training
Solution Design
Build
CRP 1
CRP 2
SIT
UAT
Transition
3/15/2016
RIAS Phase II
14
Critical Success Factors

Strong management support of the project mission and goals

A thorough understanding of the project risks, assumptions and expectations
throughout the project duration

A committed and well informed Project team and Business Managers group

Clear and consistent communication on the project goals and objectives

Involvement of users throughout the project

Realistic schedule with sufficient resources to meet expected goals

Clear roles and responsibilities to assure accountability, ownership and quality

Easy to use reporting solution

Users are properly trained

Minimizing customizations and extensions
3/15/2016
RIAS Phase II
15
Where are We

3/15/2016
Completed Activities

Timeframe

RFP Process

March – August 2006

Account Number Transition

June - July 2006

Project Team Training

October 2006

Hardware Sizing

October 2006

Annex I Renovations

October – December 2006

Oracle Database Upgrade

November 2006

RU project Team Staffing

January – June 2007

Oracle Staffing

January – June 2007

Hardware, Network Migration

July 2007

Operating System Upgrade

July 2007

SFTP Migration

July 2007
RIAS Phase II
16
Where are We

Activities in Progress

Reporting Inventory and Analysis

Reporting Attributes Inventory and Analysis

Data Conversion Design and Strategy

Inbound and Outbound Interfaces Design

Technical Architecture
 11.5.10 Preliminary testing and impacts
 Test environments build in progress

Data Warehouse Design and Modeling

General Ledger
 Requirements gathering
 Gap analysis
 Document current business process flows
3/15/2016
RIAS Phase II
17
Next Steps

3/15/2016
Activity

Timeframe

Kickoff Letter

August 2007

Appointment of BMG and finalization of
the communications hierarchy

August 2007

Expansion of PMT

July - August 2007

RIAS Website

August 2007

RIAS Phase II “road show”

August 2007 – September 2007

CRP1 Evaluation and Solution Design

August 2007 – September 2007

11.5.10 Impacts and Strategy

August 2007 – September 2007

“Build” begins

August 2007

Outreach

Data Provisioning

Supplemental Systems Group

July 2007 – August 2007
RIAS Phase II
18
Questions
3/15/2016
RIAS Phase II
19