1. Welcome! BI Executive Sponsors October 13, 2015
Business Intelligence
@ University of Wisconsin
Wisconsin
Welcome!
BI Executive Sponsors
October 13, 2015

2. Agenda Status Update for new BI Solution MAJOR paradigm shift required
Review timeline
Project structure
MAJOR paradigm shift required
Semantic layer in modern BI tools is new
What this means for campuses
Executive Sponsor responsibilities
On your campus
Secure spending authority, resources for key roles on your campus
Vocal, visible champion
Support Project Coordinator
As a team
Govern timeline and resources
Manage risks
Discussion

3. BI RFP Status Update Will begin contract negotiation
Could take 1-2 months

4. Revised Timeline for Move to New BI Tool Replacing Interactive Reporting
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Campuses
Build Semantic Layer
Develop Dashboards
(15 months)
RFP Weighting
Tier 1 Scoring
UW System
Shared Queries Conversion Build Semantic Layer
IR Out of Support by Oracle
Select Finalists
Use Cases to Finalists
End of UW System Paid Maintenance; shut off IR Workspace
Software
Purchase
Begin Installation
Campus Admins; Two developers/campus training on new system toolset
RFP ‘On Street’
Score Demo, TCO; Select Vendor
Evaluate Vendor Responses
Vendor Presentations

5. Project Structure

6. BI Core Team Participants

7. Executive Sponsors Project Coordinators

8. Enlightenment – RFP for new BI software
Interactive Reporting
New BI software
Standalone query and reporting tool
An enterprise-level reporting with access to multiple data sources on a shareable enterprise data model called a semantic layer

9. Successful Tool Replacement Requires Paradigm Shift
Loss of familiar disruptive
Learn something new
Usually with inadequate training resources
Semantic layer and
Data silos
Ungoverned data environment
Inadequate data structures
Minimal BI infrastructure
Few data architects
All within context of embattled UW System
Budget cuts
Loss of staff

10. What is a Semantic Layer?
Why would we want one?

11. Software vendors successfully
Sell Systems that record data, e.g.,
Campus Solutions
HRS
SFS
etc
Without the facility to make data available for reporting and analysis

12. Why? Reporting secondary function to those purchasing ERPs
Reporting secondary function for vendors
Customer reporting needs differ
Thus, vendors offer lowest common denominator
ERPs designed to optimize transactions not flexible reporting and analysis

13. Thus . . .
Organizations wishing to make most of information need to FILL THE GAP
Create standard reports
Create data warehouse
Create suite of analytics
To some extent UW System campuses have done this.

14. Reporting Today  Tomorrow
Current: Use query Language  data tables
Future: Use Semantic Layer
Madison Student Data Model
Interactive Reporting
Platteville Subject Area
From Semantic Layer
Oracle’s OBIEE

15. Semantic Layer is . . .
Key component in successful BI Tool Implementation
Business representation of transaction data where users
Are insulated from technical details, e.g., creating data models
Create queries using familiar terms
Can include computed items
See data not as a collection of tables (needing joins) but rather a single organized list of business fields from multiple sources
Specify query by selecting fields
Point and click to customize report appearance . . .
Tables, crosstabs, graphs
Enables ‘self service’
Implements ‘single version of truth’

16. What does this mean for campuses?
Remember, UW-System’s Responsibility (CSRG)
Tool software replacement
Conversion of System-wide shared queries
Limited training of selected roles at campuses
Campus Admins
Two developers per campus
Responsibilities of Campuses
Assessment/conversion of queries/reports/jobs
Embedded in conversion is creation of semantic layer
Training of ad hoc query writers
Training of users of new system

17. Key roles for each campus
Executive Sponsor
Project Coordinator
Project Manager
BI Developer(s)
Semantic Layer development
Report development
Others . . .

18. Executive Sponsor Responsibilities . . . On your campus (from PMBOK)
Ultimately responsible for securing spending authority and resources for the project.
Ideally, should be the highest-ranking manager possible, in proportion to the project size and scope.
Vocal and visible champion, legitimizes the project’s goals and objectives, keeps abreast of major project activities, and is the ultimate decision-maker for the project.
Provides support for the Project Coordinator and has final approval of all scope changes, and signs off on approvals to proceed to each succeeding project phase.
This definition is from PMBOK

19. Executive Sponsor Responsibilities . . . As a team
Act as governing body for timeline/resources
Manage project risks for UW System
Assess risks that come up and decide how to mitigate
Ensure that a campus does not fall behind in implementation
Decide whether to cut off Interactive Reporting even though a campus is not ready
This definition is from PMBOK

20. Project Coordinator Responsibilities
Serve as member of BI implementation team
Identification of the campus BI administrator
Identification of two technical developers for training
Communicate with and coordinate training of campus Workspace users to ensure their understanding, support, commitment, and action during this transition
Communicate with and coordinate training of the ad hoc IR users to ensure their understanding, support, commitment, and action regarding their own local/specialized queries.
Review, access convert/consolidate/eliminate campus specific queries/reports to the new BI tool.

21. Discussion: Preparing for move to new BI tool . . . Madison campus example
Learning Analytics
Student Success Metrics
Consultation
Community
Services
Champion
Best Practices
Education
Support
Alignment with
Governance
BICOP
Ad-Hoc Queries
Operational Reporting
Budget Models
(3) Business Intelligence Community of Practice
Madison campus example
Data Dictionary
Business Logic Transformation
(4) Data Stewardship
Consistent Definitions
Policies & Standards
(1) Data Governance
Student HR
Financials
Budget
LMS
Data Sources

22. Discussion

23. Good-bye!
Next Meeting
November 17, 2015
Wisline Web