Beruflich Dokumente
Kultur Dokumente
JORGEN.STEINES@PLATON.NET
WWW.PLATON.NET
1
Founded in 1999
Employee-owned company
Keynote:
JAMES TAYLOR
Platon
Side 3
Agenda
What is BI
BI Governance
BI Adoption
BI requirement specification
Summing up
Platon
OLAP
Data
Warehouse
Data
Mining
reporting
Analytical
applications
The term Data Warehouse covers the management of data
?!?
Business Intelligence
Platon
Page 5
CEO
Low profitability
Decreasing market share
Slow reaction to threats and opportunities
Challenges implementing business strategy
Challenges with mergers
. . .
Finance
IT
Marketing
HR
Heterogeneous infrastructure
Data quality issues
Reporting back-log
Project delivery issues
. . .
Procurement
Unattractive prices
Bad service levels
Lack of supplier insight
Lack of market insight
Rising stock levels
. . .
Platon
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
Insurance claim
Insurance claim
- collect information
- collect information
??
Standard case
Platon
Loss consultant
investigates
Standard case
Loss consultant
investigates
Page 8
Predictive analytics
Codan - Pricing
Platon
Page 9
Agenda
What is BI
BI Governance
BI Adoption
BI requirement specification
Summing up
Platon
10
IT Governance
Governance
Corporate governance
Platon
11
BI Governance
How do we resolve
conflicting interests?
Who decides what to
work on next?
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
Information quality
and processes
Business performance
and decision support
Data Governance
Platon
BI Governance
Page 16
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
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.
I need my own
definitions.
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.
Create a logo
Use it on reports, the intranet and all communications like newsletters,
status reports, presentations etc.
Platon
Page 21
Agenda
What is BI
BI Governance
BI Adoption
BI requirement specification
Summing up
Platon
22
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
24
Business requirements
Information requirements
Functional requirements
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
Platon
Platon
27
Platon
28
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
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
Business rules
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
Platon
32
Identify
stakeholders
Consolidate
/ document
Platon
Clarify method
of collecting
requirements
Validate/
prioritize
Update
requirement
spec.
33
Prepare and
send material
or mindset at
meeting
Send for
review
Conduct /
collect
Verify and
sign off
Identify
stakeholders
Platon
Clarify method
of collecting
requirements
34
Prepare and
send material
or mindset at
meeting
Conduct /
collect
Platon
Platon
36
BI Requirements
- Business and IT standpoints
Accuracy
User Experience
Correctness
Speed
Reliability
BICC ?
Flexibility
Innovation
Ease of use
Platon
37
Scalability
Platon
38
Agenda
What is BI
BI Governance
BI Adoption
BI requirement specification
Summing up
Platon
39
Summing up
Platon
40