33
From Data Warehouse to Business Intelligence: The Michigan Journey John Gohsman University of Michigan Sean Mallin iStrategy Solutions Presenters:

From Data Warehouse to Business Intelligence: The Michigan Journey

  • Upload
    armine

  • View
    70

  • Download
    0

Embed Size (px)

DESCRIPTION

From Data Warehouse to Business Intelligence: The Michigan Journey. John Gohsman University of Michigan. Presenters:. Sean Mallin iStrategy Solutions. Michigan Facts. Three campuses Ann Arbor (40,000 students, 23,000 faculty/staff) - PowerPoint PPT Presentation

Citation preview

Page 1: From Data Warehouse to Business Intelligence: The Michigan Journey

From Data Warehouse to Business Intelligence:

The Michigan Journey

John Gohsman University of Michigan

Sean Mallin iStrategy Solutions

Presenters:

Page 2: From Data Warehouse to Business Intelligence: The Michigan Journey

Michigan Facts• Three campuses

– Ann Arbor (40,000 students, 23,000 faculty/staff)– Dearborn & Flint (12,000 students, 1,800

faculty/staff)• Health System

– Includes: Medical School, 3 hospitals, 30 health centers and120 outpatient clinics (13,000 total employees)

• Financial Picture– Annual Budget >$4 Billion (10% from State of

Michigan)– $823M research funding per year (NIH 47%, NSF

9%, DOD 8%)– Endowment: $6 billion

• Michigan values its highly decentralized nature– “Coordinated autonomy”

Page 3: From Data Warehouse to Business Intelligence: The Michigan Journey

iStrategy Facts• Sean to complete…

Page 4: From Data Warehouse to Business Intelligence: The Michigan Journey

Presentation Outline

• The Data Warehouse Foundation

• Moving to Business Intelligence• Demonstrations• What’s Next

Page 5: From Data Warehouse to Business Intelligence: The Michigan Journey

The

80s

Page 6: From Data Warehouse to Business Intelligence: The Michigan Journey

1980s

Source: OTLP

Tools: PL/1, ASI/Inquiry

Users: Programmers, Power (10’s)

Exec

Decision Support

Management

Operational

INFORMATION

MATURITY

FINDEV

L HR STU PUR

Page 7: From Data Warehouse to Business Intelligence: The Michigan Journey

The

90s

Page 8: From Data Warehouse to Business Intelligence: The Michigan Journey

• Established Data Administration– Strategic Data Planning– Policy, Guidelines (Data as an

Asset)– Governance

(Stewards/Managers, not Owners)

– Data Modeling Services, Naming Conventions

• Built Data Warehouse– Financials, Human Resources,

Student, Fundraising– Relational approach for

flexibility

1980sEarly 1990s

Source: Oracle Data Warehouse

Tools: GQL

Users: Power (100’s)

Page 9: From Data Warehouse to Business Intelligence: The Michigan Journey

• Strategic Data Plan published–Replace all legacy

systems–Need new technical

platform• Bought PeopleSoft

ERP• Commit to replace

each data set

1980s1995

Source: Oracle Data Warehouse

Tools: GQL

Users: Power(~ 1,000)

Page 10: From Data Warehouse to Business Intelligence: The Michigan Journey

• 1998– Developed DW principles and

vision– Student Recruiting and

Admissions– Financials

• Financials delivers majority of reports via DW

• 2000– Rest of Student Administration

• 2001– Human Resource Management

System

1980s1998-2001

Source: ODS and Oracle Data Warehouse

Tools: PS Query and Business Objects

Users: Power and Casual (~2000)

Page 11: From Data Warehouse to Business Intelligence: The Michigan Journey

2000and

Beyond

Page 12: From Data Warehouse to Business Intelligence: The Michigan Journey

• Execs wonder about ERP ROI?– Operational efficiency but…

• Are we leveraging data for improved decision-making

• Units making progress– M-Dash and M-Stat in Medical

School (Xcelsius)– UHR defines and delivers

metrics; also pushes key info via email/Excel

• Establish Advisors on Information Management Strategy (AIMS)– Develop strategy

1980s2005

Source: ODS and Oracle Data Warehouse

Tools: PS Query and BusinessObjects

Users: Power and Casual (~2000)

Page 13: From Data Warehouse to Business Intelligence: The Michigan Journey

Presentation Outline

• The Data Warehouse Foundation• Moving to Business

Intelligence• Demonstrations• What’s Next

Page 14: From Data Warehouse to Business Intelligence: The Michigan Journey

• AIMS delivers BI Strategy– Leverage BI Framework– (use framework slide?)– Issues

• Lack of campus readiness or awareness

• Silo approach• Lack of applications• Complicated data

structures• Limited tools• Missing infrastructure

1980s2006

Source: ODS and Oracle Data Warehouse

Tools: PS Query and BusinessObjects

Users: Power and Casual (~2000)

Page 15: From Data Warehouse to Business Intelligence: The Michigan Journey

UM BI Framework Adapted from Gartner

ResearchData Sources FIN Student HR Devl Unit-

specific

InfrastructureData Warehouse, ODS, ETL, Data Quality, Metadata, Data Marts

Applications and FunctionalityAd hoc query/reporting, standard/canned reporting, statistical analysis,data mining, predictive modeling, presentation/alert/push technology

Process Performance mgt, methodology,

education

Strategy

Tools BI end user tools, BI developer tools, XCelsius, OutlookSoft Everest

Users

OrganizationSkills, BI Competency

Community

Page 16: From Data Warehouse to Business Intelligence: The Michigan Journey

• AIMS recommendations– Build awareness via BI Community

• BI Council– BI Community of Experts,

Communications, Data, Training/Methods

– Address user segments; increase market

• Power (1500), operational (8000), casual/guided analysis (>10,000)

– Increase tools portfolio, infrastructure

• Browser-based, solutions for execs, managers, etc.

– Improve data structures• Aggregate, derive = dimensional,

OLAP• Incorporate into Administrative Systems

Strategic Plan 1980s2006

Advisors on Information

Management Strategy (AIMS)

Business Intelligence Council

(BIC)

Training & Methods

Subgroup

Communi-cations

Subgroup

DataSubgroup

BI Community of Experts

(BICE)

Page 17: From Data Warehouse to Business Intelligence: The Michigan Journey

Web ReportingOperational Power ToolsData from Multiple

Sources

Entry Points

Page 18: From Data Warehouse to Business Intelligence: The Michigan Journey

Vision

Application Specific (e.g. PeopleSoft) Reporting

Web-Based Reporting for Predefined

Reports

Business Objects

Reporting

User Group 1(~10,000 users)

User Group 2 (~5000 users)

User Group 3(~3000 users)

Three Gateways for Reporting

Page 19: From Data Warehouse to Business Intelligence: The Michigan Journey

• Create BI Council and subgroups• Created annual BI Awards• Parallel progress while campus

readiness improves– Decision to upgrade Business

Objects and acquire site license– Decision to build web reporting

solution for guided analysis (internal controls, PI reports)

– Decision to acquire cubes for Financials and partner to develop HR metrics cube

– Research archive/purge, ETL/CDC tools

1980s2007-2008

Source: ODS, Oracle DW, SQL Server

Tools: PS Query, Business Objects, Proclarity, .Net

Users: Power and Casual (~2000)

Page 20: From Data Warehouse to Business Intelligence: The Michigan Journey
Page 21: From Data Warehouse to Business Intelligence: The Michigan Journey

Presentation Outline

• The Data Warehouse Foundation• Moving to Business Intelligence• Demonstrations• What’s Next

Page 22: From Data Warehouse to Business Intelligence: The Michigan Journey

iStrategy: HR Metrics

Page 23: From Data Warehouse to Business Intelligence: The Michigan Journey

M-Reports

Page 24: From Data Warehouse to Business Intelligence: The Michigan Journey

M-Reports Vision

M-Reports will deliver business intelligence to users in a customizable user interface

• Alerts, metrics and personalized reports based on user profile, preferences and role based security

• Guided analysis through data• Data sourced from multiple underlying

databases (production, ODS, Data Warehouse, unit data)

• MAIS and University units can develop and publish content

Page 25: From Data Warehouse to Business Intelligence: The Michigan Journey

Presentation Outline

• The Data Warehouse Foundation• Moving to Business Intelligence• Demonstrations• What’s Next

Page 26: From Data Warehouse to Business Intelligence: The Michigan Journey

Creating a BI Organization

• Increase size of team• Expand mission, increase functions

– Add Analytical skills– Increase Application Development– Enhance BI Community– Increase Consulting and Training– Enhance Data Administration– Improve Data Set Development– Increase Tools Support

Page 27: From Data Warehouse to Business Intelligence: The Michigan Journey

Deliver More Solutions

• More cubes, dimensional models• Broad content in M-Reports• Dashboards (KPIs, personalized

thresholds)• Push (reports, alerts)• Predictive Analytics• Workflow• Process Management

Page 28: From Data Warehouse to Business Intelligence: The Michigan Journey

• Build a solid foundation• Deliver to campus

– Provide different data structures and a portfolio of tools to meet different needs

• Engage campus– Executive leadership– Community awareness and

understanding• Make progress at all levels of

framework

1980sSummary

Source: ODS, Oracle DW, SQL Server

Tools: PS Query, Business Objects, Proclarity, .Net

Users: Power and Casual (15,000)

Page 29: From Data Warehouse to Business Intelligence: The Michigan Journey

For More Information

Visit:• www.bi.umich.edu• http://www.mais.umich.edu/stratplan/index.html• http://www.mais.umich.edu/reporting/index.html• http://spg.umich.edu/pdf/601.12.pdf

Or contact:[email protected]@istrategysolutions.com

Page 30: From Data Warehouse to Business Intelligence: The Michigan Journey

Microsoft

M-Reports

Proclarity

BusinessObjects

ETL

HE (PeopleSoft)

FIN (PeopleSoft)

Development

eResearch

Reporting Copy

(PeopleSoft)

Enterprise Data Warehouse

OracleHRFin

GL Stu

Devl PR

BI Tools

ETL

iStrategy

FIN

iStrategyHR

InternalCubes

U-M Business Intelligence Overview

Page 31: From Data Warehouse to Business Intelligence: The Michigan Journey

Legacy data sets

M-Pathwaysdata sets

Business

Objects

M-PathwaysOracle 10g

Data WarehouseOracle 10g

Predefined Reports

Ad Hoc Queries

Extract/Transform using

SQR

HEPeopleSoft (Ver. 9)

FINPeopleSoft (Ver.

8.8)

Load

BI ToolsBusinessObjects XIR2

WebI and Infoview

Relational Data Warehouse Environment

Page 32: From Data Warehouse to Business Intelligence: The Michigan Journey

U-M Star Schemas/Cubes: M-Reports

Single

Purpose Star Schemas

Internal Controls

Staging BI Tools

Sources

Multi Purpose Star

Schemas

iStrategy

Staging BI Tools

Sources

Page 33: From Data Warehouse to Business Intelligence: The Michigan Journey

M-Pathways

M-Reports Design Schema (Temp Pay Example)

Using MS Reporting

Services for Grids and Graphs.

Need to decide about additional

sw.

Assumption: No direct access to

LCC from outside an application (including UI)

Web services are very simplistic

BLL Components contain all

business logic

DAL Components build and pass

SQL/MDX Commands

Cubes vs. Relational

Security Layer

Web Services

Business Logic Layer

Data Access Layer

Data Bases

M-Reports Portal

Non M-

Reports UI

External Customer

s

Security Component

(written in-house)

Temp Pay

Get Temp Pay

Get Temp Pay By Funding

Dept

M-Reports BLL

Get Distinct Campus

Temp Pay BLL

Get Temp Pay

Get Temp Pay By Funding

Dept

M-Reports DAL

Build General Parms

Select Distinct Campus

Temp Pay DAL

Select Temp Pay

Future

Future