Prepared Exclusively for - University of Wisconsin ... Coordinators 10.21.2016.pdf · • Use of OBIA if the fit/gap shows a positive fit • Alternative approach if not a fit •

© 2016 Huron Consulting Group. All rights reserved. Proprietary & Confidential.

Prepared Exclusively for:

OBIEE Implementation

1

© 2016 Huron Consulting Group. All rights reserved. Proprietary & Confidential. 2

Agenda

o Quick review of project scope and major deliverables

o Updates on first 2 weeks of progress; next steps

o Key points from meetings with campuses

o Your implementation plans

o Key points for you to discuss with your Executive Sponsors

o Reminder of 2nd training on RPD next week

o Feedback, questions and discussion


Origin of the project

3

UWS is replacing the legacy, system-wide reporting tool, Oracle’s Brio/Hyperion Interactive Reporting (IR) because support for this tool is ending soon, earliest in June 2017 although could be extended to end of life in spring 2018.

UWS is proceeding with a Business Intelligence (BI) tool (OBIEE 12c) as the replacement of choice.

© 2016 Huron Consulting Group. All rights reserved. Proprietary & Confidential.© 2016 Huron Consulting Group. All rights reserved. Proprietary & Confidential.

This 8 week project:

Initiate & Analyzephases of the IR replacement

Shared Queries

Student Pilot

Infrastructure


FIT/GAP ANALYSIS Conduct a fit gap analysis for OBIA HCM Analytics. Develop a fit/gap results document that shows level of fit and customizations needed to meet all

reporting requirements. Develop options for the future state data architecture for the shared queries including:

• Use of OBIA if the fit/gap shows a positive fit• Alternative approach if not a fit• Approach for InfoAccess, SFS and WISDM data sources.

Conduct option review sessions and facilitate the decision making process.

Shared Queries

IMPLEMENTATION PLAN Develop an implementation plan for the design, build, test, and deploy phases of the project

based on the option selected above.

5


INFRASTRUCTURE SETUP1. Review and recommend architecture details for Development, Test (QA), and Production environments.

2. Review and recommend the approach to configure OBIEE Authentication using the Wisconsin Federation of campus-specific SAML2 IdPs.

3. Review and recommend the approach for OBIEE Authorization.

4. Recommend and assist with implementing RPD change and configuration management processes compatible with the preceding items.

Infrastructure

6


DATA SOURCE ANALYSISAnalyze the current student reporting data models and determine if a conversion to a dimensional model (i.e. a data warehouse) will be needed.

DEVELOPMENT

Student Pilot

PILOT CAMPUS ENABLEMENT

7

• Develop a recommendation on whether a common student data model can be leveraged.• Develop the high level logical model for student data• Develop a template implementation plan for the three types of conversions

o Campuses already using a dimensional model o Campuses using a partial dimension model (RDS)o Campuses not using a dimensional model

Complete the IR to OBIEE Rationalization and prioritization (if needed) Document the requirements Work with the pilot campuses to build their implementation plans and establish the next

phase of work for each.


First 2 weeks / Updates and next steps

8

• Met twice with UW team • Began work on time-cost comparison for

three options:1. OBIEE & develop from scratch.2. OBIA & customize as required.3. Redevelop EPM as a true dimensional

warehouse.

• Met with all early adopter campuses to understand their current reporting environments and data models.

• Requested next level of information and simplified our original request for BQY (report) metadata extraction.

• Worked with the Central Data Request team to understand their purpose and the data they collect and disseminate.

• Kicked off this week. • Got briefed by central IT experts from the

Identity and Access Management group.• Began exploring current state of server,

hardware, and RPD to begin considering development recommendations.

Shared Queries Student PilotInfrastructure

Next steps: • Continue/complete detailed comparison of

delivered OBIA system and required queries.

• Complete time-cost model for 3 options above.

Next steps: • Prepare high-level current state

diagrams. • Distill metadata related to campus BQYs

(reports) to collect information we need to begin to prepare future state recommendations and to create a common data model.

Next steps: • Continue to flesh out recommendations,

partnering with central IT experts.


y

Summary of 1st meetings with early adopters

9

UW Eau Claire• Use many materialized views, primarily for

security• Institutional Research data brought into RDS• 200 queries identified as high-priority• Up to 95% of high-priority data model completed in

OBIEE 12c RPD

UW Milwaukee• Heavily reliant on RDS tables and views• Resolved to creating more strict star schemas in

the RDS • Many BQYs are very similar to others• Experimenting in OBIEE 12c• Wish there was a common student data approach

UW Stout• Use of RDS probably similar to UWM, although no

stated effort to make DW more dimensional• Query many different systems with IR• Experimenting in OBIEE 12c

UW Whitewater• Most IR queries are against views in CS• Open to idea of moving from CS to a Data Warehouse

as primary query target of OBIEE – want advice.• Interest in OBIA has been expressed.• Do mostly operational reporting (as do all campuses) –

little aggregation, so queries are responsive enough.• Would like reporting solution to do analytical reporting• Experimenting with OBIEE, bringing tables into

physical layer.

UW Green Bay• Create reporting copy of Campus Solutions nightly• Use PS Query against PSFT Operational Systems• Only 110 tables and views actively used• Want to continue to use CS as opposed to moving to

a DW• EAB APS purchase very much front of mind

UW Platteville • Have EPM as a DW• Have OBIEE 11g RPD in production• ETL Tool is Data Stage• Have the most dimensional schema• Can they stay on EPM after loss of support? Can

other campuses use EPM schema?• Want to see a common student system


Your implementation plans

Implementation Plan Implementation Approach ScheduleCost EstimateKey Success FactorsChange Management ApproachDependenciesMajor Phases and Tasks of ImplementationProject Management OverviewStaffing Requirements

Recommendations to assist your campus with your local process of converting

Overview of your Current / Future StateArchitectureReportingAnalysis ProcessSecurityApplication Support TeamChange Management/Training


Key points for your Executive SponsorsThank you for keeping your Executive Sponsors in the loop.

FYI: The Executive Sponsors are meeting about this project on 11/3.

1. Review of scope and progress you were briefed on today.

2. Alert them to your resource needs. (Your Executive Sponsor has agreed to secure resourcing for your local work on this; the BI Coordinator role is to assess and surface such needs.)


October 26-28. 8:30am-4:30pmRoom B1144A Biochemistry, Madison Campus

RPD Training

12

2nd offering of RPD training next week


Feedback, questions and discussion

What are you experiencing as this project kicks off?

What rumors are you hearing?

How can Huron help you?What could be clearer?


San Francisco | Chicago | New Yorkwww.huronconsultinggroup.com

14

Documents

Prepared Exclusively for - University of Wisconsin ... Coordinators 10.21.2016.pdf · • Use of OBIA if the fit/gap shows a positive fit • Alternative approach if not a fit •