OSU IT Portfolio Planning
Project Proposal Data Sheet
Top Priority Name
Project Name
Date
OSD/EDW / Cognos implementation
Updated 5/31/12
Double Click to Update Header
3. Project Governance
1. Project Description/Issue Statement (may
include project triggers):
Role
The University had decided to move from an in-house
developed data warehouse solution to ellucian software
products ODS (Operational Data Store) and EDW
(Enterprise Data Warehouse). In addition, Cognos, an IBM
reporting tool, will also be installed and implemented. RAP
(Recruiting and Admissions Performance) and SRP (Student
Retention) will also be implemented as part of this project as
they utilize ODS/EDW.
The current reporting tool, BI/Query, no longer meets the
evolving business need of the University. Cognos was
purchased to replace this product. To take full advantage of
the reporting capabilities of Cognos, and to add new features
that build upon BRM, we need to revamp our underlying
data warehouse structure by implementing ODS/EDW. In
addition, RAP and SRP both utilize ODS/EDW and will
allow greater reporting capabilities for the business units.
2. Goals & Objectives:
Program Supported
This will support programs across campus that currently
utilize the existing Data Warehouses as well as new
packages such as BRM (Banner Relationship Management),
RAP (Recruitment & Admissions Performance) and SRP
(Student Retention Performance).
Business Objectives
Implementation of these products will provide consistent
data for analysis at various levels within the University.
These products are more fully integrated with Banner. The
current reporting tool no longer meets the needs of the
University. To more fully support the reporting needs, the
data warehouse needs to be revamped.
IT Objectives
Implement the new products in a timely manner to ensure
our customers have access to consistent timely data for
analysis and reporting. These products are standard ellucian
products, freeing IT resources from developing and
maintaining our in-house developed data warehouse
solution.
Last updated: 06-Mar-16
D:\533575707.doc
Page
1
Project Sponsor
Advisory Committee
Member
Advisory Committee
Member
Advisory Committee
Member
Org
Bob Nettles
Aaron Howell, Director, Business
Affairs and Record Custodian
Jacque Rudolph,, Director, Human
Resources and Record Custodian
Kent Kuo, Director of Enterprise
Computing & Registrar and Record
Custodian
Advisory Committee Sal Castillo, Director, Office of
Member
Institutional Research
Advisory Committee TBD, Business Center Director
Member
Advisory Committee TBD, International/ INTO
Member
Advisory Committee Jim Day, Enrollment Management
Member
Advisory Committee TBD, College of Business
Member
Advisory Committee Rosemary Garagnani, Assoc.
Member
Director, Graduate School
OSU IT Portfolio Planning
Project Proposal Data Sheet
Top Priority Name
Project Name
OSD/EDW / Cognos implementation
Updated 5/31/12
Date
Double Click to Update Header
4. Project Scope:
6. Key Project Deliverables
Scope
In
Out
Functional
There will be
changes in how
users create and
use the data
warehouse. The
warehouse may
have different
data fields. We
must also identify
which order to
implement the
transfer of
existing data
warehouse to the
ODS/EDW
We will not
support data
warehouse
refreshes so the
data is ‘live’; data
refreshes will be
done nightly.
Organizational
All other Scope
Most
Flexible
X
X
Schedule
Resources
Moderately
Flexible
Xdepending
on SCT
schedule
Last updated: 06-Mar-16
D:\533575707.doc
Milestone
Date (mm/yy)
Estimated Start Date
Estimated Finish Date
Update to PTVORGN
Implementation of ODS - Student
Implementation of RAP
Implementation of SRP
Implementation of ODS & EDW –
Financial Aid
Implementation of ODS & EDW –
Finance
Implementation of ODS & EDW – HR
Implemenation of ODS & EDW–
International
4/01/12
TBD
6/13
6/12 – 6/13
3/13 -5/13
4/13- 6/13
6/12 -6/13
1/13 – 3/14
7/13-10/14
1/14 – 12/14
8. Staffing estimates
5. Flexibility Matrix:
Scope
-
Update to PTVORGN table
Implementation and training of ODS – Student,
Financial Aid, Finance & HR modules
Implementation and training of RAP
Implementation and training of SRP
Implementation and training of EDW - Student,
Financial Aid, Finance & HR modules
Implementation and training on Cognos
Identification and Conversion of pilot units of
existing data warehouse to ODS/EDW
Identification and Conversion of existing priority
reports from current data warehouse to ODS/
EDW/ Cognos
7. Preliminary Schedule and Milestones:
There are some
changes needed to
the existing
systems
(particularly
PTVORGN table)
to support
ODS/EDW.
Least
Flexible
-
-
We do not expect
any
organizational
changes / issues
in the scope of
this project.
Hardware may
already be
purchased and in
house already.
System
-
Page
2
Role
Effort
Name/Org
Project Manager
Developer
SQL DBA
Data Integrator
Data Integrator
Core business unit
staff
75%
25-50%
25-50%
75%
75%
10-25%
Diana Lindsley / ECS
Mark Baldwin / ECS
To be determined
Patty Ross / ECS
Hollie Pitts / ECS
From each core office
OSU IT Portfolio Planning
Project Proposal Data Sheet
Top Priority Name
Project Name
Date
OSD/EDW / Cognos implementation
Updated 5/31/12
Double Click to Update Header
9. Dependencies, Assumptions and Constraints
-
10. Known Issues and Risks (of proposal)
Dependency - PTVORGN issues need to be
resolved
Assumption that we will have staff from each core
office as needed to participate in timeline needed
Assumption that all reports in current data
warehouses can be identified and that the report
owners will support the migration to Cognos
Assumption that ECS staff will be dedicated to the
project
Assumption that the current data warehouse and
ODS/EDW can run in parallel and be supported by
ECS staff for a prolonged period
Assumption that Single signon can be used
Assumption that these products will integrate with
Luminis
Assumptions that security models can be adapted to
accommodate the new environment
Assumption that we will refresh data in the data
warehouse (ODS/EDW) on a nightly basis
-
-
-
Risk of staff not being available when needed. ECS
has open positions for a data integrator and a new
DBA; these people will need to be hired and
trained
o One ECS staff member is transitioning to
the Data Integrator role; she will still
need training; we are developing a
transition plan to include training
-
Risk regarding Cognos licensing. Cognos has a
different licensing structure, which may impact
training, as well as the mix of centrally provided
reports versus those done by the core offices.
Risk of cost regarding Cognos licensing. With the
different licensing structure, we may have
increased costs for licenses, or a different mix of
licenses and staff that can run / develop reports.
Risk of lack of acceptance by users. With the
change from an existing, known tool to a new,
more complex tool, users may resist conversion of
their reports and acceptance of the new products.
Risk of availability of core office staff. Work will
need to be done by core office staff to identify and
asset with conversion of their reports, data needs in
the EDW, and testing.
Risk of delay due to integration with Single Signon
(CAS) and Luminis. We have experienced issues
with BRM integration with CAS and may
experience similar issues with ODS/EDW.
Risk of changing project sponsorship and data
custodians. Several people in these capacitities are
retiring; there is no clear line of succession at this
time. Project direction may change as we change
these key staff.
-
-
-
-
-
Last updated: 06-Mar-16
D:\533575707.doc
Page
3
Issue with PTVORGN to be resolved; ODS does
not expect this table to be used when using
FTVORGN. Meetings were held in September /
October to discuss the issue, though it is still
unresolved.
Issue - There was mention on the SCT Forums that
Oracle Streams is being discontinued. SCT is
implementing Materialized Views instead. This
version will not be ready until summer 2012. We
need to decide which to implement.
o Decision – some history tables are
compressed for storage after 2 – 2 ½ yrs;
Materialized Views do not support
compressed tables; because of the need for
historical data of about 10 yrs, we cannot
use Materialized Views, so we will use
Streams
OSU IT Portfolio Planning
Project Proposal Data Sheet
Top Priority Name
Project Name
Date
OSD/EDW / Cognos implementation
Updated 5/31/12
Double Click to Update Header
11. Key Success Factors
-
Key staff in core offices and departments trained in
and using Cognos Report Studio
Staff in core offices and departments trained in and
using Cognos Query Studio
ECS project staff (data intergrators and
programmers) trained in and using Cognos
Framework manager
Priority one reports converted to new ODS/EDW
ODS/EDW installed and running with little down
time; refreshes occurring on schedule
Security access and process determined and
implemented
EDW snapshots successfully running
12. Ties to OSU Strategic Plan
-
-
-
RAP & SRP will assist with target goals of
increasing First-Year Rentention and Six Year
graduation rate by identifying students not meeting
their goals (Goals 1 & 2)
RAP & SRP will assist with target goals of
recruiting high achieving students and minority
students by identifying and targeting these studnets
for recruitment (Goals 1 & 2)
ODS/EDW/Cognos will assist with improving the
information infrastructure to support the University
(Goal 3)
Last updated: 06-Mar-16
D:\533575707.doc
Page
4
DRAFT PROJECT TIMELINE