SR4 Workshop

1. Stock Movement Reporting (SR4) in EDW
Design Workshop
Tuesday 23rd October 2007

2. 2
 Overview and expectations
 Introductions of Team Members
 Approach to the Discovery and Prototype
 Approach to Business Reporting Model
 SR4 Reporting Requirements
Agenda

3. 3
Overview and Expectations
 Review of the approach we will taking over the
next 8 weeks
 Brief view on Business Reporting Models, so we
are talking the same language
 Review of the reporting requirements gathered
thus far, including a skeleton model and a
breakdown of data requirements

4. 4
 Overview and expectations
 Introductions of Team Members
 Approach to the Discovery and Prototype
 Approach to Business Reporting Model
 SR4 Reporting Requirements
Agenda

5. 5
 Overview and expectations
 Introductions of Team Members
 Approach to the Discovery and Prototype
 Approach to Business Reporting Model
 SR4 Reporting Requirements
Agenda

6. 6
Approach to the discovery and prototype
Business
Requirements
And
Reporting
Data
ETL And
EDW
Application
Design
Workshop
Objectives
22/10/2007
Design
Workshop
Review
13/11/2007
Design
Workshop
Review
20/11/2007
Report
Requirement
Sign Off
29/11/2007
Report
Build
Iteration 1
Data Mart &
HW design
Iteration 1
Data Mart &
HW design
Iteration 2
Data Mart &
HW design
Iteration 3
Review
Sources
Define Data
Requirements
Finalise
Data
Contracts
Finalise
Data Model
ETL & EDW
Design
Iteration 1
Finalise
ETL & EDW
Design
Review
Sources
Define Data
Requirements
Review
Sources
Define Data
Requirements
Report
Build
Iteration 2
Report
Build
Iteration 3
ETL & EDW
Design
Iteration 2
ETL & EDW
Design
Iteration 3
ETL
HLD
Sign Off
14/12/2007
Workshops and Prototypes
ETL & EDW
Requirements
Elaboration Build of Priority Components
Elaboration Build of
Priority Components
Data Contract
Data Model
Sign Off
06/12/2007
Project & Stakeholder Management
34 weeks
10 weeks
Construction
Elaboration Transition
8 weeks

7. 7
 Overview and expectations
 Introductions of Team Members
 Approach to the Discovery and Prototype
 Approach to Business Reporting Model
 SR4 Reporting Requirements
Agenda

8. 8
What needs reporting?
 Ideal approach is to extract the required reports
from a “business reporting model”
 What is a business reporting model in essence it
has two parts:
– What we want to add up?
– What we want to analyse by?
 So how do we go about getting the requirements
right?

9. 9
Will this “Business Reporting Model” Work
 We create the “business reporting model” simply
on a flip chart,
 Then we walk thru the model to see if we can
get the reports out!
 Simple, really!
 Here is how we do it …using Motorcar Insurance

10. 10
What will this model look like? Don’t laugh a Squished Octopus
What we want
to add up?
Analyse by
Analyse by
Analyse by
Analyse by
Analyse by
Analyse by
Analyse by
Analyse by
… now for a worked example

11. 11
What we want to Add Up?
•Premium
•Claim
•Loss Ratio [Claim/Premium]
 Typical questions:
– How much premium did we
collect?
– How much claims did we pay?
– What Loss Ratio are we
running at?
… so now lets see what we want to analyse by

12. 12
What we want to analyse by?
•Premium
•Claim
•Loss Ratio
[Claim/Premium]
Analyse by Time
Analyse by Car
Analyse by Customer
Analyse by Broker
Analyse by Geography
 Typical questions:
– What is the average
age of drivers?
– What models of cars
do we insure?
– What is the longest
policy period?
– What locations do we
insure?
– Who is the top broker?
… so now lets join things up

13. 13
Now we can ask better questions
•Premium
•Claim
•Loss Ratio
[Claim/Premium]
Analyse by Time
Analyse by Car
Analyse by Customer
Analyse by Broker
Analyse by Geography
 Typical questions:
– What location is the
worst insured area
based on claims paid
for the 2007 year?
– What colour car in
London driven by
males is the most
profitable in terms of
Loss Ratio?
– Who are our top ten
brokers based on
Premium for last year?
– What is the premium
trend over the last five
years in terms of
Geography?

14. 14
More detail on Analyse by Time
•Premium
•Claim
•Loss Ratio
[Claim/Premium]
Analyse by Time
 Each of the items is a level, these levels allow you to group up the
data for example
 Year 2007
– Quarter 1 – 2007
– January 2007
– 01/01/2007
» 01/01/2007 12:00:00

15. 15
Now we will look at some of elements in a little more detail, What we want
to Add Up?
 What we want to Add Up?
– Things like Premium and Claim are measures
– Things like Loss ratio (Claim/Premium) are
calculated measures
– By default measures are usually additive but you can
do other domain aggregate functions such as
average, count etc.
– We store them in the database as facts, because
that’s what they are facts about an action

16. 16
Now we will look at some of elements in a little more detail, What we want
to analyse by?
 What we want to analyse by?
– We call the “analyse by” a dimension
– Levels within the dimension allow the facts to be
grouped up and summarised
– The groups are called hierarchies

17. 17
What have we done?
 We have created a dimensional model called a
star schema
 It contains facts and dimensions
 We now have a business reporting model that
can be easily

18. 18
 Overview and expectations
 Introductions of Team Members
 Approach to the Discovery and Prototype
 Approach to Business Reporting Model
 SR4 Reporting Requirements
Agenda

19. 19
SR4 Initial Requirements Model
Value of Adjustment
% Availability
Net Waste
Sell-Outs
Lines not sold (count)
Estimate Change (value)
Stock Count number
Stock Count %
Stock Count % inaccuracy found
Time
Store
Adjustment Type
Stock Count Type
Product
Department

20. 20
Provide Stock Accounting Consolidated Data
 Measures
– Value of Adjustment (+-) – Money
 Dimension
– Adjustment Type (are there any categories?)
– Store (what consolidation – geographical or type)
– Date/time period

21. 21
Time Adjustment Type Stock Adjustment Price
2008D050 Self Supply 25,656.38
2008D052 Good Will Exchange 40,234.98
2008D052 Soiled & Damaged 12,567.23
Time Manager Reductions Selling Adjustment Price
2008D049 RTM 23,546.67
2008D050 Manager Reduction 41,345.67
Uxbridge, 121
Paddington, 654
Stock Accounting Consolidated Data
SACD01
Stock Accounting

22. 22
Provide Consolidated Management Information
 Measures
– Adjustment Value
 Dimensions
– Adjustment Type (are there any categories?)
– Store (what consolidation – geographical or type)
– Department
– Date/time period (Weekly and/or consolidated?)

23. 23 23
Consolidated Management Information
Time Department Adjustment Type Stock Adjustment Value
2008D050 Men’s Self Supply 25,656.38
2008D052 Children Good Will Exchange 40,234.98
2008D052 Women Soiled & Damaged 12,567.23
Time Adjustment Type Manager Reductions Selling Adjustment Value
2008D049 Underwear RTM 23,546.67
2008D050 Food Manager Reduction 41,345.67
Uxbridge, 121
Paddington, 654
CMI01
Consolidated Management Information

24. 24
Store Stock Diagnostic (General)
 Measures
– Value of Adjustment (+-) – (value)
– % Availability (what exactly is this – snapshot, average etc?)
– Net Waste (value)
– DAS Adjustment (What is this?)
 Dimensions
– Adjustment Type (are there any categories?) (Stock Loss is a type)
– Store (what consolidation – geographical or type)
– Date/time period (Weekly and/or consolidated?)
– Product (hierarchy?)

25. 25
Store Stock Diagnostic (Performance)
 Measures
– Sell-Outs
– Stock Count number
– Stock Count %
– Stock Count % inaccuracy found
– Lines not sold (count)
– Estimate Change (value) – what is this?
 Dimensions
– Stock Count Type (standard/targeted)
– Store (what consolidation – geographical or type)
– Date/time period (Weekly and/or consolidated?)
– Product (hierarchy?)

26. 26 26
Store Stock Diagnostic
Time Stock Adjustment Adjustments Type Stock Adjustment Value Target
2008D050 Mgr Discount Price reduction %50 %40
2008D052 Loss Internal Use %45 %50
2008D052 Date Expired Waste 1200 1500
Time Store loss Adjustments Type Stock Adjustment Value Target
2008D049 Mgr Discount Price reduction 1400 1500
2008D050 Date Expired Waste %81 %70
Uxbridge, 121
Paddington, 654
SSD01
Store Stock Diagnostic