Planning and Deploying Enterprise Reporting and BI

1
Planning and Deploying Enterprise Reporting and BI

• TJ Rains, PMP
• ERP Administrator/Banner Project Manager
• Emporia State University
• trains_at_emporia.edu

2
Agenda

• Introduction
• Banner _at_ ESU Project Overview
• Operational Data Store and Enterprise Data
  Warehouse Overview
• Enterprise Reporting Goals and Objectives
• Reporting Tool Evaluation and Selection Process
• Implementation
• Lessons Learned So Far

3
Banner _at_ ESU Project Background

• Kicked Off in March of 2005
• Will Close Out in December of 2007
• Guiding Principles and Objectives
• Replace in house developed heterogeneous legacy
  administrative systems with an integrated ERP
  system.
• Improve Business Processes and Streamline
  Operational Efficiencies.
• Create a Secure Single Point of Entry to
  University Information Resources.
• Expand Self Service Information Access to all
  University Constituents.
• Refine Security Standards and Procedures.

4
Banner _at_ ESU Project Background

• Banner and Partner Systems Implemented
• Luminis Portal Live March 2006
• Banner Advancement - Live July 2006
• Banner Finance Live July 2006
• ODS Live July 2006
• Cognos 8 BI Live July 2006
• Appworx Live July 2006
• Evisions Live July 2006
• Workflow Live July 2006
• ePrint Live July 2006
• RMS Housing Live January 2007
• Banner Financial Aid Live March 2007
• Banner Student Live March 2007
• Touchnet Payment Gateway Live May 2007
• Banner HR Live July 2007
• EDW Live December 2007

5
ODS

• Sungard HE ODS
• Sungards Defininition - Operational data store
  is based on standard higher education data models
  developed by SunGard Higher Education in
  partnership with their clients. ODS is a system
  intended for providing a consistent view of
  intuitional data to empower end user operational
  and ad hoc reporting.
• Realistic Definition The Operational data store
  is an oracle database instance batch populated
  from production data views and transformed into a
  flattened relational structure to ease report
  writing efforts.

6
EDW

• Sungard HE EDW
• Sungards Defininition - A data warehouse built
  from the ODS, based on a standard OLAP model
  developed by SunGard Higher Education in
  partnership with their clients. EDW is formatted
  to capture point-in-time, aggregated, historical
  data for enterprise level information needs
  supporting business analytics including trend
  analysis and forecasting.

7
ODS/EDW/Cognos - Diagram
8
Enterprise Reporting

• Driving Goals and Objectives
• Provide users with the ability to sort, filter,
  drill down, query, and build ad hoc reports on
  the web in a user-friendly environment.
• Reduce paper based reports.
• Provide reports with drill down capability.
• Eliminate Shadow reporting data stores and report
  development systems.
• Consolidate reporting and analysis skills by
  using one primary reporting and analysis toolset
  for operational and analytical reporting.
• Develop reports and analytics to accurately
  measure University strategy performance.

9
Align with Institutional Strategy
Performance Areas
Financial
Academic
Student
Operational
Process Areas
Planning budgeting
Fundraising
Assessment tracking
Financial aid analysis
Human Resource analysis
Resource allocation
Financial reporting analysis
Retention analysis
Benefits analysis
Course enrollment tracking
Financial forecasting
Recruiting analysis
Faculty workload
Program profitability
Student demographics
Program review
10
Project Staff and Org

• Banner _at_ ESU Executive Committee
• Banner _at_ ESU Steering Committee
• Banner _at_ ESU Project Director CIO
• Banner _at_ ESU Project Manager
• DBA Staff
• Report Developers
• Institutional Research Staff

11
Charge

• To deploy the Sungard HE ODS and EDW systems to
  support each Banner functional areas reporting
  needs utilizing the Cognos Reporting tool.
• Assumptions for this project include
• We will use a common data source
• We will work to develop common data definitions
  (i.e. FTE)
• We will develop a process to freeze historical
  data
• We will discuss data needs not delivered in the
  ODS and define an approach to fit these gaps
• We will endeavor to share reports
• We will discuss the owner, access, and
  distribution of reports for quality control and
  standardization
• We will commit appropriate time to this project
  as negotiated by the group
• We will change our input and processing
  procedures if necessary to meet our reporting
  needs
• We will ensure the appropriate level of security
  has been implemented to control data access
• We will define all requirements for a new
  reporting toolset.
• We will evaluate top reporting products and
  choose a system for purchase and implementation.
  

12
Reporting Tool Evaluation

• Analyze
• At the time of evaluation, SunGard did not
  specify a supported reporting tool for ODS and
  EDW.
• A detailed product analysis was performed on each
  of the top reporting competitors using the
  following high level criteria.
• Provide a common reporting toolset for both
  operational and analytical reporting
• Provide a robust security framework making use of
  the Oracle and Banner security infrastructure
• Provide a web based reporting delivery and
  management system
• Provide web based ad hoc reporting functionality.
• Detailed requirements were defined and a
  comparison matrix was developed to support the
  decision making process.

13
Reporting Tool Evaluation

• Define Selection Pool for Onsite Demonstrations
• Narrowed the pool to
• Cognos
• Business Objects
• Oracle Discoverer
• Conducted Product Demonstrations
• Invited Functional/Technical Reporting Users
• Surveyed Attendees on the key selection criteria
• Selected Cognos 8 BI as the product for
  implementation.

14
Cognos 8 BI Implementation

• Installation
• Server Installation
• SunGard ODS Meta Data Layer Integration
• Single Sign On
• LDAP Configuration
• Luminis Portal Configuration for Single Sign On
• Training Plan
• On Site Cognos Report Studio Training
• On Site ODS Report Development Training for each
  Banner Module.

15
Lessons Learned so far

• Choose your project team wisely (functional
  Champion)
• Phased rollout with limited users
• Address potential staffing needs
• Data validation process
• Define a custom report request process for
  prioritization purposes.
• Training considerations
• Technical (OWB ODS)
• Functional (come prepared to write reports!)

16
Thank You!
Check 2007