1. Welcome! BI Executive Sponsors August 4, 2016
Business Intelligence
@ University of Wisconsin
Wisconsin
Welcome!
BI Executive Sponsors
August 4, 2016

2. Agenda Information Items Updates from Operational Governance
CSRG Carryover Funding Request from
BI Consulting Services RFP Update
OBIEE 12c for analytical work
RPD Training Update
Updates from Operational Governance
Anand’s (Whitewater) replacement
Underway – Recommendation for Authorization/Authentication process
Clarifying questions? – Decision brief on single OBIEE RPD instance
Positioning HRS/SFS for OBIEE

3. Agenda Planning underway for Working with Consultants
Technical Infrastructure
Shared Queries: Work with Consultant to determine best path forward
Building Student Content in RPD
Early adopters
Later adopters
Campuses using CDR data
Consulting Engagement will Help Determine Timeline
Questions

4. Information Items 2016-17 CSRG Carryover Funding Request of $407,120
BI Consulting Services RFP
Nearing completion

5. Information Items OBIEE for Analytical Work
Question posed to HEDW forum:
The University of Wisconsin System is moving from Interactive Reporting to OBIEE 12c. Some campuses are using Tableau. For campuses in OBIEE what tools are used by Institutional Research offices for analytical work including medium complex models and just-in-time multi-source analyses?

6. Information Items OBIEE for Analytical Work Response from SUNY
We are also slowly phasing out our Hyperion Interactive Reporting (IR) system.  We have implemented OBIEE with BIPublisher locally to complement the SUNY-wide OBIEE system that has also been created.  BIPublisher seems to be the most natural replacement for IR in our environment.
You can do medium complex and just-in-time analyses using these tools, but it all depends on how you model your data and train your users.  If the data model isn’t created in a way that allows this, we have also seen that we can utilize existing dashboards and reports together to gather the data, then export it to another tool like SPSS, or Excel to do the real analyzing.
Something worth looking into might be the new Oracle Data Visualization tool that you can add on to OBIEE, I believe it is a separate license.  Like BIPublisher, you can upload your own data and mash it up with OBIEE subject areas, but you are also able to explore it with a little more flexibility, like in Tableau.

7. Information Items – RPD Training
Round 1 Complete; Trainees can model on their desktop
Round 2 Planning Underway; End of October or early November?

8. Information Items – Campus Admin Training
Campus Admin Training to be determined
Anticipating day-long class with Maverick trainer

9. Updates from Operational Governance
Campus representative replacement
Recommendation from Committee: Jen Chapek, Stout
Underway: Recommendation for Authorization/Authentication process
High-level requirements have been documented
Options presented to IAM TAG (July 27) for campus input
Further analyses of options is underway, specifically regarding central data source systems (HRS, SFS)
Decision Brief on Single OBIEE Instance: Any Questions?

10. Positioning HRS/SFS for OBIEE
Assessment approach
Current state – factors/risks
Current path
Recommended strategic path
Next steps

11. Executive Summary
Eight-week assessment of current data warehouse and reporting platforms supporting HRS and SFS and options for positioning these platforms for Oracle Business Intelligence Enterprise Edition (OBIEE) and operational reporting demands.
PeopleSoft Enterprise Performance Management (EPM)
WISDM/WISER
Brio/Hyperion Interactive Reporting
Output: Recommendations on short and long-term strategic roadmap for maintaining an enterprise reporting, business intelligence and data warehousing solution.

12. Factors / Risks - HRS/EPM Reporting
EPM Application (HRS data warehouse) is NOT Supported (being retired by Oracle).
Current tool to extract data from HRS and place in EPM is no longer supported.
Current EPM Database contains Custom Transformations and Objects. Packaged PeopleSoft objects are not used.
Other Pain Points include:
Heavy Operational Dependence on PS Query
Strong Reliance on Power Users

13. Factors/Risks: WISDM/WISER
Current system is stable, but dependent on custom built code with multiple legacy technologies. WISDM has extensive amounts of SQL encapsulated within its modules.
WISDM is not real-time and does not represent transactions from the current day of operation.
It could be difficult to maintain based on custom technologies in Development, ETL and Platform.
Current Data Integration (HRS, Campus Solutions) is limited in reporting landscape.
Limited developer knowledge - resources turnover.
Current project ongoing to update to current technology (WISER) and to bring in additional data (expense, projects etc.). 6

14. Current path for transitioning Shared Queries to meet June 2017 timeline
Build the OBIEE data source based on current EPM and Wisdm/Wiser data structures
Develop reports to replace the IR shared queries.

15. Current Path Implementation – Resource Estimates
Total Public IR Reports for conversion - 105
Note: This is based on the known Public IR Reports Count.
We still need to assess the total number and identify the technology (BIP, RPD/OBIEE) for conversion
Complexity
Simple
Medium
Complex
Total Hours
# of Reports 5 11 89
Effort (Hrs) 40 45 50
Hours
200
495
4895
5590
Aug 1st to HR go live (8 Months)
1280 Hours - Per Developer 
Developer 3 
3840
Data Modeler 1 
600
Architect
550
DW Analyst/BA
 Total Hours
Note: Project Manager and Systems Admin Roles are part of this solution who are not part of the
conversion and development estimate shown above.
Estimated cost:
~$593K for internal DoIT resources or ~$878K for consulting resources

16. Implications of current path
Resource availability, cost , schedule.
Accomplishes initial transition, but not optimal for supporting OBIEE ongoing.
Eventually need to build new data structures (particularly for HRS) to support analytical and predictive features of the new OBIEE tool.
Does not address HRS/EPM data warehouse situation. 12

17. Recommended strategic approach
Evaluate an additional Oracle tool (Oracle Business Intelligence Applications)
Solution for replacing EPM (proof of concept)
Enables move of IR shared queries
Delivers pre-built analytics and dashboards
Foundational for enhanced BI analytics/predictive analytics
Foundational for building a common enterprise data warehouse
Integrate OBIA Analytics – starting with HR Analytics
Build a plan for Common Enterprise Data Warehouse across Organization business functions (HCM, FIN, and potentially Campus Solutions).
Define Data Governance Strategy across UW Reporting and Business Intelligence landscape.

18. Recommended strategic approach:
Source - Oracle Corporation

19. Immediate Next steps: Work with BI consulting partner to:
Analyze feasibility of OBIA Proof-of-concept for HRS as approach for transitioning the Shared Queries and/or other strategies for dealing with the Shared Queries.
Determine realistic resource plan and timeline for the HRS shared query transition. Resource and funding availability to meet June 2017 uncertain. 16

20. Planning Underway for Work with BI Consultants
Technical Infrastructure
Statement of Work under development
Shared Queries: Work with Consultant to determine best path forward
Building Student Content in RPD
Early adopters
Leveraging Learners
Campuses using CDR data

21. Campuses Working with Consultant: Student Data

22. Determining Timeline Feasability of June 2017 Date
Consultant Engagement will assist in clarifying timeline
Infrastructure Configured and Managed
Shared Queries replaced in OBIEE
Moving Student content from IR to OBIEE
Until these are determined we can’t specify timeline

23. Questions?

24. Good-bye!
Next Update
September 1, 2016
Wisline Web