you can get fries and coleslaw with the bi/dw combo!

STRICTLY PRIVATE AND CONFIDENTIAL

You Can Get Fries and Coleslaw With The BI/DW Combo!Steve Bond,Consulting Director

Sier

ra S

yste

ms

Strictly Private and Confidential

© Copyright 2006 Sierra Systems Group Inc.

Agenda

BI Today

BI Purpose

Why BI

Business Reflection

The Roadmap

The Framework– The Business– Design– Development– Implementation– Project

BI Successes

Sier

ra S

yste

ms



Business Intelligence

Business Intelligence

CPM – Corporate Performance Management

Data Warehouse

Perf

orm

ance

Man

agem

ent

Organizational Understanding

Enterprise Effic

iency

Single Source of Truth

Self Sufficiency

Optimiza

tion

ODS

Sier

ra S

yste

ms



The Purpose of BI

To help organizations meet their objectives by providing:– Relevant information– Accurate information– Timely information. . . .to support critical business strategies & processes

Successful BI is achieved by:– Consolidation multiple disparate data sources– Cleansing and transforming– Creating a single source of information– Accessible by business users using their language

Sier

ra S

yste

ms



Why BI?

Business Need– Data rich– Information poor

Technical Limitations– Multiple sources of data– Built to purpose

• Inconsistent data– Transactional systems vs.

analytical solutions

Sier

ra S

yste

ms



BI Reflects the Business

Executive Management

Strategic Objective 1A textual description of the objective



Objectives Actions

Objective 1 Action to support objective



StrategyBusiness Plan

MeasuresWorkforce

Management

Sier

ra S

yste

ms



BI Roadmap

Successful BI solutions are based on communicating and measuring the strategy of the organization

Think Big, Implement Small

BI Roadmap service identifies strategy, creates a prioritized roadmap through collaboration with business stakeholders and IT

Incremental process minimizes development and releases BI content to the business quickly

Change Management and Project Management reduce risk and increase success

Roadmap

BI Application Development&

ImplementationCh

ange

Man

agem

ent Project M

anagement

Strategy

Roadmap


ImplementationCh

ange

Man

agem

ent Project M

anagement

Roadmap


ImplementationCh

ange

Man

agem

ent Project M

anagement

Strategy

Sier

ra S

yste

ms



BI Roadmap

Stakeholder Interviews

Reporting and analysis reviews

Subject area identification and prioritization exercise

Source systems reviews

Technical complexity assessment

Toolset selection

Sier

ra S

yste

ms



BI Roadmap

Deliverables– Prioritized subject areas linked to organizational strategy– Information delivery framework– Enterprise information architecture– Toolset recommendation, RFP, proof of concepts– High level logical model– Project Plan– Cost estimates (hardware, software, consulting services,

internal resource time)– High level change management plan– High level education plan

Sier

ra S

yste

ms



BI Roadmap

Sier

ra S

yste

ms



BI Framework – The Business:Identify Business Pillars & Drivers

Strategy

‘Enabling Pillars’

Business Drivers– Key Performance Indicators– Keep it high level

Sier

ra S

yste

ms



BI Framework – The Business:Information Consistency & Presentation

Consistent KPI Development– Cascade throughout the

organization– Process for change

Presentation Layer– User classes require

different information displays

– Right information, right level at the right time

– End state scenarios

Sier

ra S

yste

ms



BI Framework – The Business:Prioritize the Business Requirements

Determine

Capture

Agree

Prioritize

Map– Business value vs. urgency– Preliminary mapping

Include organizational cultural aspects

Drill into 1 area

Sier

ra S

yste

ms



BI Framework – The Business:Go Into Detail

Determine KPI Measures– In detail

• By user classification– reports, etc.

• Frequency• Drill path

– Common Vocabulary– Source Systems

• Extraction complexity• Data quality

Sier

ra S

yste

ms



BI Framework – The Business

Establish high level business sponsorship

Let the business lead

Deliver to business objectives

Ensure common business language

Ignore business culture

Deliver volumes of technical documentation

Identify all KPI’s for all requirements in detail

Sier

ra S

yste

ms



BI Framework: The Design

OLAP – Denormalized– Constrained dimensions– Constrained facts– Write back and other

requirements– Business support

Metadata– Business– Technical

History– Years available

Data Quality– Audit– Correction process

ETL– Batch schedules– Error correction

Availability– Update requirements– Business requirements– User locations– Data quantities

Sier

ra S

yste

ms




Only when you understand:– Business requirements– Data requirements– Usage– Data quality– History– Metadata

Can you determine the overall architecture– ROLAP, MOLAP, HOLAP– Federated, Centralized

Start to consider your front-end, back-end and ETL tools!!!

Sier

ra S

yste

ms



BI Framework: Architecture Design

Envision the Grand DesignDashboards

(Portals)- Scorecards

- Personalised- Operational and Analytical Data

ERP

CRM

External

Other

Data Warehouse Staging Area

ETL(Extraction,

Transformation & Loading)

Enterprise Data Warehouse

&Reporting

Applications

Enterprise WideCentralised

Day Level Data

Application LayerData Mining Layer

ModellingAd-Hoc AnalysisStandard Reports

Operational, Operational Management & Analytical

Reports

ODS(Operational Data

Store)Near Real Time

ETL

ETL

ETL

EAI

Ad-Hoc Tools & Specialised Reporting

Marts

Mass Produced Operational Reports

Other Access Points

Sier

ra S

yste

ms



BI Framework: Architecture Design

Implement Incrementally

CRM

ERP

Enterprise Data Warehouse

&Reporting

Applications

Enterprise WideCentralised

Day Level Data

Dashboards(Portals)

- Scorecards- Personalised

- Analytical Data

Ad-Hoc Tools & Specialised Reporting

Marts

Sier

ra S

yste

ms




Aggressively define data model - incrementally

Have a data owner

Develop & maintain metadata, dictionary and repository

Use DW specific experience

Make sure architecture is cohesive, open, scalable & flexible

Compromise the model

Assume ‘one size fits all’

Purchase tools before you know your requirements

Assume existing skills are sufficient

Sier

ra S

yste

ms



BI Framework: Development

Proof of Concept– Proves technical tit– Proves business fit

Tool Evaluations– Consider multiple tools– Allow users to evaluate front-

end tools– Follow a consistent framework– Consider costs up front if

necessary

Sier

ra S

yste

ms




BI projects are extremely successful when iterative (agile) development processes are followed

Business testing is critical

Data reconciliation is critical

Expect issues with data quality, ETL processes & procedures and presentation layer re-work

Experienced teams should deliver in 3 month cycles

First implementation cycle may take up to 6 months

Iteration 1

Iteration 2

Iteration 3

Sier

ra S

yste

ms




Undertake a proof of concept

Use a tested BI implementation methodology

Develop incrementally

Expect some re-work– ETL– Report development

Include users– Report development

Big-bang approach

Keep the business in the dark

Shoe horn the project to your standard methodology

Exclude the business from the front-end tool selection

Avoid implementing ETL error handling and production monitoring

Sier

ra S

yste

ms



BI Framework: Implementation

User Training– Tool usage– Integration into role

Business As Usual Training– Technology & tools– Error handling– Batch schedule– Data lineage

Release to users in small, manageable batches

Floor walks

Sier

ra S

yste

ms




Performance Monitoring– Monitor usage daily & adjust to reality– Identify top and bottom reports– Assess user satisfaction

Communications Planning– Multi-channel communications to target users & business– Identify ‘win’ stories and communicate to management– Clearly communicate success criteria

Sier

ra S

yste

ms




Hand Over to Business As Usual– Establish support structure early– Ensure all teams know about ‘batch windows’

• Maintenance for source systems may require additional planning– Provide development team support for a defined period

Sier

ra S

yste

ms




Establish:– Training– Hand over– Success criteria– Communications

plans early in the process

Have a robust performance management plan

Use vendor only training

Expect BAU to quickly ‘pick up’ the system

Allow ‘wins’ to go unnoticed

Roll out in 1 go

Sier

ra S

yste

ms



BI Framework: Project

Use a phased approach– Business requirements– Discovery period

(3 to 8 week time frame)

Define phases by business delivery

Strong BI Project Manager

Organizational change management

Communications management

Sier

ra S

yste

ms




Establish clear resource plan & don’t remove resources– Use ‘seasoned’ internal resources

Ensure contingency is built-in throughout the plan, especially during the ETL phases

Allow for support, tuning and hand-over time well after the project has ‘delivered’

Plan for the sake of planning. Keep it reasonable, detailed BI plans go off-track.

Sier

ra S

yste

ms




Strong subject matter expertise

Experienced BI project management

Follow issue, risk, status, governance structures

Communicate, Communicate, Communicate!!

Not plan or update plan

Hide plan results

Ignore the business

Communicate to business in tech speak – translate to English

Wait for a 100% solution before release

Sier

ra S

yste

ms



BI Successes

BC Public Safety and Solicitor General

BC Attorney General

Various WA State Agencies

BC Ministry of Provincial Revenue

State of Connecticut

Los Angeles Police Department

BC Ministry of Management Services

BC Ministry of Employment & Income Assistance

City of Surrey

A & W

Boston Pizza International

Dimensional Fund Advisors

North Shore Credit Union

Tolko Industries

Vancouver Island Health Authority

Sier

ra S

yste

ms



Questions?

you can get fries and coleslaw with the bi/dw combo!

Documents