Hvordan sikres (mere) vrdi af

Business Intelligence projekter?

JORGEN.STEINES@PLATON.NET

WWW.PLATON.NET
1

Platon The Company

A leading Independent Information Management consulting company

Headquarters in Copenhagen, Denmark

220+ employees in 9 offices

300+ clients in 8 countries

Founded in 1999

Employee-owned company

Platon received good feedback in our satisfaction survey. Clients

cited the following strengths: experience and skill of consultants,
business focus and the ability to remain focused on the needs of
the client, and a strong methodological approach
Gartner July 2008
Platon

Nordens strste Information Management konference:

Keynote:
JAMES TAYLOR

Fokus p Business Intelligence og Master Data Management

Unikke internationale eksperter
Netvrksreception med underholdning af Jonatan Spang
Afsluttende netvrksmiddag

Vi glder os til at se dig og dine kollegaer d. 12. oktober 2011.

Vi er stolte over at annoncere rets
keynote-taler: n af de strste Business
Intelligence-guruer hele vejen fra San
Francisco i USA. James er en ledende
ekspert og forfatter indenfor regelbaseret
beslutningssttte (Decision Management
& Predective Analytics) og en anderkendt
keynote-taler ved diverse globale
konferencer.

Book allerede datoen i din kalender i dag!

Du kan flge udviklingen af programmet p
www.IM2011.net.

Platon

Side 3

28 unikke prsentationer, bl.a:

Agenda
What is BI

BI Governance
BI Adoption
BI requirement specification
Summing up

Platon

Data Warehouse & Business

Intelligence
The term Business Intelligence (BI) covers
the use of information to drive business
insight.

OLAP

Data
Warehouse

Data
Mining

Basically its about providing a better

foundation for decision makers by providing
information in the right form, in the right
Enterprise
quality, at the right time.

reporting

Analytical
applications
The term Data Warehouse covers the management of data

?!?

Data is extracted from operational systems and integrated in

the Data Warehouse environment in order to provide an
enterprise wide perspective, one version of the truth.

Business Intelligence

Platon

Page 5

Drivers for Business Intelligence

The
Multidimensional
Manager:
24 Ways to Impact your
Bottom Line in 90 days

CEO
Low profitability
Decreasing market share
Slow reaction to threats and opportunities
Challenges implementing business strategy
Challenges with mergers
. . .

Finance

IT

Marketing

HR

Cash flow problems

Low profitability
Losses on debts receivable
Inflexible planning process
CPM aspirations
. . .

Heterogeneous infrastructure
Data quality issues
Reporting back-log
Project delivery issues
. . .

Decreasing market share

Missing cross/up-sales
Bad campaign response
Slow time to market
CRM aspirations
. . .

Many types of employees

High employee turnover
Bad employee satisfaction
Decreasing competencies
Need for collaboration
. . .

Procurement
Unattractive prices
Bad service levels
Lack of supplier insight
Lack of market insight
Rising stock levels
. . .

Platon

Production and logistics

Quality issues
Falling service levels
Increasing lead time
Rising inventory levels
Resource bottlenecks
Increasing distribution costs
Inefficient processes
Extended value chain aspirations
Process outsourcing
Just-in-time aspirations
. . .

Page 6

Sales
Falling revenue
Missing cross/up sales
Increasing COGS
Missed opportunities
Bad forecasting
Decreasing prices
Complex markets
. . .

Service
Bad customer satisfaction
Increasing response time
More complaints
Random service levels
. . .

An example

Platon

Page 7

Predictive analytics
Codan - Fraud

It is estimated that 10% of all insurance claims are attempts to fraud

For Codan this equals 400 mill. DKR per year

Insurance claim

Insurance claim
- collect information

Risk of fraud is predicted

through a
data mining tool

- collect information

??

Standard case

Platon

Loss consultant
investigates

Standard case
Loss consultant
investigates
Page 8

Predictive analytics
Codan - Pricing

New model 100 x 100 meter cells

Old model postal codes

High risk
Low risk

Several parameters to determine the risk

Only a few from the customer
The rest is based on data

Platon

Page 9

Agenda
What is BI

BI Governance
BI Adoption
BI requirement specification
Summing up

Platon

10

IT Governance

Governance

Corporate governance

IT Governance: Specifying the decision rights and

accountability framework to encourage desirable
behavior in the use of IT
The opposite of Governance: Anarchy (from Greek: anarch,
"without ruler)
"No rulership or enforced authority.
"Absence or non-recognition of authority and order in any given sphere.
"Act[ing] without waiting for instructions or official permission... The root of
anarchism is the single impulse to do it yourself: everything else follows from
this.

Platon

11

BI Governance

BI Governance is the framework and processes for

determining the priorities, deployment practices, and
business value of enterprise business intelligence initiatives.

How do we resolve
conflicting interests?
Who decides what to
work on next?

How do we get executive level awareness

and support?

How can we be more

proactive and
anticipate changing
business needs?

Platon

12

How do we quantify
and track the values of
our BI investments?

BI Governance
- Business and IT standpoints

IT
DW

DBA

BICC

Data
modelling

Develop
ETL

User
support

Requirement
Specs

Design
Develop
Front end
reports
Standards
for reporting

Cost effectiveness

Platon

Analyze
information
Train
Users

Business
Innovation
Responsiveness

Reliability

Scalability

13

Execute
Bus. Proc.

Recommend
Actions

Flexibility

Operational efficiency

IT

Business
Business
Business
unit
unit
unit

BI Governance
- Organisational structure

Program
Board
Program level

BICC

Coordinate &
prioritize

DW

Operation level
Coordinate
& prioritize

Project level

Platon

Steering
Committee

Steering
Committee

Steering
Committee

Project A

Project B

Project C

14

Governance relationships
The purist would claim they are independent

IT Governance

Data Governance

Infrastructure and
operational applications

Information quality
and processes

BI Governance
Business performance
and decision support

Platon

Page 15

Governance relationships
IT Governance
Infrastructure
and operational applications

Business strategy alignment

Project portfolio management
Business value tracking
Legal compliance
Knowledge management
Service Level Agreements

Information quality
and processes

Business performance
and decision support

Data Governance
Platon

BI Governance
Page 16

Step 1: Define the governance

level of the BI Program
Step 1: Define the governance level of the BI Program
Step 2: Identify decision making bodies
Step 3: Define decision areas and decision rights
Step 4: Design and implement governance processes

Ad hoc

Degree of federation

BI Project prioritization
BI Architectures
BI Organisation

BI Methodology
BI Policies
BI Tools & Systems
Common Data Definitions
Platon

17

One way

Agenda
What is BI

BI Governance
BI Adoption
BI requirement specification
Summing up

Platon

18

What can drive better

deployment and adoption

Strategy
clarification

Other

Focus on usage

Better BI
adoption

Communication,
marketing and
branding

Platon

Organisational
Change
Management

19

Change Management
I can not live
without my
Excel sheets.

The successful companies focuses 70 % of

the implementation resources on processes,
education and other soft aspects and only 30
% on technology

I need my own
definitions.

Similar to ERP implementations?

I dont want my
results to be
visible for all.
We earn
money
anyway.

Lets build
it and they
will come.

The users

The managers
The BI people
Platon

Page 20

We know
what they
need.

Communication, marketing and

branding
Branding
Provides a single identity when communicating about your BI Program
Differentiates your product from other choices

Create a logo
Use it on reports, the intranet and all communications like newsletters,
status reports, presentations etc.

Extend your brand through report certification

A process of promoting a report to a mass audience
Further drives the data integrity of your BI program and builds user
confidence
Creates a adoption effect as management only wants to view reports
that have been branded and/or certified

Platon

Page 21

Agenda
What is BI

BI Governance
BI Adoption
BI requirement specification
Summing up

Platon

22

Does this look familiar?

Increasing costs to fix defects

discovered later due to
incorrect requirements

Analysis

Platon

Design

Development

23

Implementation

BI solution types
Ad hoc analytics / OLAP
Dashboards / cockpits

Balanced scorecard
Predictive analytics / data mining

Reporting

Performance management
GIS and other visualization

Alerts and exception

Analytical CRM
Platon

24

Types of (BI) requirements

What is the business
need, pain or problem?
What business questions
do we need to answer?

Business requirements
Information requirements

What data is necessary to

answer those questions?

Functional requirements

How do we need to use the

resulting information to
answer those questions?

Detailed report / usage requirements

Detailed layout etc

Other requirements
All the other stuff AKA non
functional requirements

How about defining the business processes that apply the new
information to managerial actions?

Platon

25

Design inspiration

David McCandless: The beauty of data visualization

Platon

The requirement specification

document The simple version
Introduction
Business requirements
Business process requirements
Information requirements
Functional requirements
Detailed report / usage req.
Other requirements

Platon

27

The requirement specification

document The really simple
version

Platon

28

The requirement specification

document The expanded version
Executive summary
Introduction
Business requirements
Business process requirements

Information requirements
Functional requirements
Detailed report / usage req.

Security requirements
Performance requirements
Operational requirements
Migration requirements
User doc. and training requirements
Other requirements
Platon

http://www.volere.co.uk/template.htm
29

Business process requirements

Change is the keyword

Textual description is ok
Or use a swim lane design where the workflow or supporting
instructions, procedures or use cases are changed

Procedure
Prioritize order based on
customer rating by

Use Case
When the sales rep enters
The system shows

Platon

30

Cover all information

requirements
Ask, ask, ask
Explain and exemplify - with all stakeholders
Facts

Business rules

Dimensions and hierarchies

Value sets

Timeliness
How fresh should the data be (update frequency)
Specific dates the new data is needed

History
How much calendar time should be covered
How about changes in hierarchies - program requirement could be
type 2 SCD and project requirement could be type 1 SCD

Platon

31

Does this look familiar?

Perhaps some more structured

techniques are needed?

Platon

32

The process & methods

The sub activities for specification process is outlined in the figure
below.

Identify
stakeholders

Consolidate
/ document

Platon

Clarify method
of collecting
requirements

Validate/
prioritize

Plan and invite

for meetings

Update
requirement
spec.

33

Prepare and
send material
or mindset at
meeting

Send for
review

Conduct /
collect

Verify and
sign off

The process & methods

Identify
stakeholders

Platon

Clarify method
of collecting
requirements

Plan and invite

for meetings

34

Prepare and
send material
or mindset at
meeting

Conduct /
collect

BI and Agile development

Platon

The effect of initial roll-out times

on project success

Platon

36

BI Requirements
- Business and IT standpoints

Accuracy
User Experience

Correctness

Speed

Reliability

BICC ?

Flexibility

Innovation
Ease of use

Platon

37

Scalability

Pay attention to data quality

Poor data quality is the second most common reason for BI

failure
Data quality is a big risk
Get a clear picture on data quality issues as early as
possible - during analysis or even before
Dont wait until the development takes place

Platon

38

Agenda
What is BI

BI Governance
BI Adoption
BI requirement specification
Summing up

Platon

39

Summing up

Value comes from decisions and changed behavior not

from providing reports
Information requirements are key in all BI projects

Make the right balance between time and perfection

Expect change and expect to manage change

Platon

40