eCommerce EDW Reporting

Workshop 1a – Business Process

Thursday 18th June 2009
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to 10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

2
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to 10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

3
Overview of Workshop

 Review the approach we will be taking over the next 8 weeks

 Brief view on Business Reporting Models, so we are talking
the same language
 Review of the Business Process for Finance Reconciliation
and how the existing reports support it
 Discuss the existing reports to understand any issues or
enhancements including consolidation and data gaps
 Produce a candidate list of reports for the new solution
 Discuss the look and feel of these reports for prototyping

4
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to
10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

5
Introductions

 Project Team
– M&S
– Project Manager Gill McCaffery
– Business Analyst Barbara McLennan
– Capgemini
– Project Manager Gary Richardson
– Solution Architect Richard Farrant
– Data/ETL Architect Craig Barrick
Name:
 Business Users Role:
Critical Success Factors:
Biggest Issue:
Best Improvement:
6
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to
10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

7
eCommerce EDW Reporting Scope

 The first phase of eCommerce EDW Reporting is only

considering the following messages
– Drop Ship
– Purchase Confirmation
– ICOS

 Any requirements related to Seller Central reports that cannot be

delivered in this phase will be captured for future use
 Reporting requirements will be aligned to the existing business
process
– The business process is being reviewed as a separate exercise during this
nine week period

8
Elaboration Phase – Work Package 1 (Time boxed and Prototype Based)
9 weeks

Project & Stakeholder Management

 3 iterations focusing on aligning to the business
process and prototyping different report priorities
Work Package 1 The
Work Package 2 top priority reports will
Workgo through
Package2 iterations.
3 Work Package 4 & 5

Workshop Design Design

Objectives & Design Issue Final BRD, HLD,
Workshop Workshop Workshop Version of All Data Model,
Prioritise Review Review Review All Deliverables Data Flows
Reports Priority 1 reports Priority 2 reports Reports for Sign Off Sign Off
1 week 2 weeks 2 weeks 2 weeks 1 week 1 week

Workshops and Prototypes

Business
Requirements Sign Off
And Business Report Report BRD
Reporting Process Build Build Consolidation
Iteration 1 Iteration 2 Iteration 3

Review Review Review

Sources Finalise
Sources Sources Data Sign Off
Define Data Define Data Define Data
Requirements Contracts High Levell
Requirements Requirements
Data Data Model
Data Mart & Data Mart & Data Mart & Data Flows
Finalise Data Contracts
HW design HW design HW design
Data Model
Iteration 1 Iteration 2 Iteration 3

ETL & EDW ETL & EDW ETL & EDW Sign Off
ETL And Design Design Design
ETL & EDW HLD
EDW Requirements Iteration 1 Iteration 2 Iteration 3 & Preliminary
Application ETL design

9
Deliverables

 Work Package 1
– High Level Design
– Conceptual Data Model and Entity Level Data Flows
– BRD
– Prototype for the reports
– Development Test Strategy
– Detailed Plan for Work Package 2 and High Level Plan for WP 3 and 4.

 Benefits to M&S
– The detailed Business and Reporting Requirements created through an iterative
approach and based on a prototype will provide M&S the confidence that the
solution that is being built will be accepted and will meet the business
expectations.
– Data Contracts will be reviewed to support the Business Requirements.
– The code used during elaboration to build the prototype will be an accelerator
during the construction phase.

10
Workshop Process – Preparation (Week 1)
Preparation Business Processes and Prioritisation

Inputs Process Outputs

Seller
Central Process
Reports Existing Report
Collate Report Matrix
Knowledge
Identify High Level
Cottage Business Processes
Industry •Agree Priority
Reports Owners
•Identify Process Owner
And
•Identify Sub Processes
Business Attendees
•Identify Attendees
Process •Map SC Reports
Knowledge •Map CI Reports

Data Business
Contracts Analysis Reporting Workshop
Model Schedule

11
Workshop Process – Iteration 1 Business Process (Week 2/3)
Preparation Workshop 1a/b/c/d – Objectives and Prioritisation

Inputs Process Outputs

Seller
Central Candidate
Updated Process Report Matrix
Reports Process Reports by
Analysis Report Priority
Matrix
Review & Categorisation
Cottage •Used Max 20
Iteration 2
Industry •Duplication Reports
Reports •Issues Look & Feel
•Enhancements
•Not Used Max 20
•Data Issues Iteration 3
•Obsolete Reports
•New Requirement Look & Feel

Data Business
Contracts Analysis Reporting Data
Model Gaps

12
Workshop Process – Iteration 2 First Tranche (Week 4/5)
Preparation Workshop 2 – First Tranche Reports

Iteration 2 Inputs Process Outputs

Reports
Look & Feel
Prototype Reports Updated
Iteration 2 Prototype Process
Iteration 2 Only
Reports I2 Only Report
Matrix
Max 20
Review Prototype
BRD •Purpose
V0.1 •Consolidate
Agreed
•Priority
Prototype
Data •Data
Changes
Contracts •Layout
•Navigation
Data •Drill Down
Model
Data ETL and EDW Validated
Gaps Requirements Business
Data Report
Flows Model
HLD
V0.1

13
Workshop Process – Iteration 3 Second Tranche (Week 6/7)
Preparation Workshop 3a – Second Tranche Review

Inputs Process Outputs

Iteration 3 Updated
Reports Possible Consolidation Process
Look & Feel Report
Matrix
Max 20

Initial Review of
Iteration 3 Reports
following Iteration 2
for possible
consolidation

Process
Report Iteration 3
Matrix Reports
Possible Consolidation Look & Feel

14
Workshop Process – Iteration 3 Second Tranche (Week 6/7)
Preparation Workshop 3b – Second Tranche Reports

Iteration 3 Inputs Process Outputs

Reports
Look & Feel
Prototype Reports Consolidation to a Updated
Iteration 3 Prototype maximum of 30 Process
Iteration 3 Only
Reports I3 Only Report
Matrix
Max 20
Review Prototype
BRD •Purpose
V0.2 •Consolidate
Agreed
•Priority
Prototype
•Data
Changes
•Layout
•Navigation
•Drill Down
Update
Iteration 2 I2 Report Validated
Prototype
Prototype Prototype Business
With
Changes Changes Report
Changes
Model

15
Workshop Process – Consolidation and Review (Week 8)
Preparation Workshop 4 – Consolidation and Review

Inputs Process Outputs

Limited to a Updated
maximum of 30 Process
Report
Matrix
Review Prototype
BRD •Purpose
V0.3 •Consolidate
•Priority
•Data
•Layout
•Navigation
•Drill Down
Update
Iteration 2/3 I2/3 Report Validated
Prototype
Prototype Prototype Business
With
Changes Changes Report
Changes
Model

16
Workshop Process – Review and Sign Off (Week 9)
Preparation Workshop 5 – Sign Off Review

Inputs Process Outputs

Requirements Stream
Reports
Complete Prototype
Prototype

Complete BRD
BRD Review Deliverables
V1.0 •BRD
•Report Prototype
Data / ETL Stream •HLD
HLD Sign Off
•Conceptual Data Model
Complete HLD V1.0 •Entity Level Data Flows
•Development Test Strategy
•(Next WP Plans)
Data
Complete Data Model Model

Data
Complete Data Flows Flows

Test Stream
Development Test
Test Strategy V0.1
17
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to
10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

18
What needs reporting?

 Our approach is to capture the Reporting Requirements and

validate them against a “business reporting model” to confirm
that we have all the required data
 What is a business reporting model?
– It defines the following functionality in a graphical format:
– What we want to add up?
– What we want to analyse by?

 We have created models for each of the Messages that we will

use later to validate your report requirements
 Before doing this we have put together an example model for
Motor Insurance as a simple introduction to this process which
we will walk through

19
What does a “business reporting model” look like?

Analyse by

Analyse by
Analyse by

What we want Analyse by

Analyse by to add up?

Analyse by
Analyse by

Analyse by

An Octopus or a Spider
… now for a worked example
20
What we want to Add Up?

 Typical questions:
– How much premium did we
•Premium collect?
•Claim – How much claims did we pay?
•Loss Ratio [Claim/Premium]
– What Loss Ratio are we running
at?

… so now lets see what we want to analyse by

21
What we want to analyse by?

Analyse by Time  Typical questions:

– What is the average age
of drivers?
Analyse by Customer
– What models of cars do
we insure?
•Premium – What is the longest
•Claim Analyse by Car policy period?
•Loss Ratio
[Claim/Premium] – What locations do we
insure?
– Who is the top broker?
Analyse by Geography

Analyse by Broker

22
Now we can ask better questions

Analyse by Time  Typical questions:

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

23
More detail on Analyse by Time

Analyse by Time
•Premium
•Claim
Q Ye
•Loss Ratio
M ua ar
[Claim/Premium] Ho Da on rt e
ur y th r

 Each of the items is a level, these levels allow you to group up the data for
example
 Year 2009
– Quarter 1 – 2009
– January 2009
– 01/01/2009
» 01/01/2009 12:00:00

24
Other Possibilities - What do 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

25
Other Possibilities - What do 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

26
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 will form the
basis of our reporting requirements
– It clearly shows what can be reported
– It enables us to validate that the required data is present in the data
contracts

 The next step will be to prototype the reports and review the
results

27
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to
10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

28
eCommerce Business Process Review

 Inputs
– Existing Report Layouts/Examples
– Our understanding of the Business Process
– Your knowledge and experience

 Outputs
– High Level Business Process for Finance Reconciliation
– Candidate List of Reports that are required

29
eCommerce Business Process Review

Process Message Accounting Impact

Order DN – Demand Notification

Marks and Spencer

Placed TS – Trans-Shipment Request
Amazon

Amendment DC – Demand Cancellation

OF – Order Fulfilment
Pick
Ship ASN – Advance Shipment Notification

Confirmation PCN – Purchase Confirmation

30
Business Process – Finance Reconciliation

 Within this Business Process we have identified the

following sub processes which we will need to
understand from a reporting perspective
– International and UK VAT
– Business Reporting of Sales
– Commercial Sales
– SAS v Amazon
– Payments
– Bank Reconciliation

31
Supporting Reports – Seller Central

 From our initial analysis the following Seller Central reports

are currently used to support this process
– 005 Order Discount Summary – 150 Staff Discount Usage
– 006 Self Supply Payment by Promo Tracking
– 151 Payment Reversal Report
ID – 154 Payments Pending Weekly
– 010 No Payment Refund
– 157 Web/Phone Channel
– 011 CATS Report – 158 Store Order Channel
– 017 Written Off Stock
– 159 Home delivery Channel
– 019 Delivery Receipts – 160 Store Delivery Channel
– 029 Departmental Sales
– 168 Uncollected Order Value by Store
– 052 Gift Service Receipts
– 171 SVC Sales by Shipment
– 144 Promo Certificates Issued – 173 Departmental Sales for ISA Orders
– 145 Concessions Redeemed
– 174 Order Discounts for ISA Orders
– 146 Outstanding Balance for Concessions
32
Business Process – Collaborative Session

Finance Reconciliation and Bank Reconciliation

The following reports are required by Finance to carry out the Financial reconciliation : 004 Goodwill, 005 Order Discount, 006 Self Supply, 010 No Payment Refund, 011 CATS Report, 019 Delivery Receipts, 029 Departmental Sales, 052 Gift Receipts, 144 Promo Certificates Issued, 145
Concessions Redeemed, 154 Payments Pending Weekly, 173 Departmental Sales ISA Orders. NOTE: The ISA information reported is for orders paid for on the platform only , orders paid for at POS are reported by POS.
Seller Central

Report 011
HSBC
Download to a Streamline
Access the reports for AMEX
predefined destination
the previous week Diners
(Excel), save in a new
week Chargecard
FASS

Summarise data as
The difference between
Save the data in the shown below using Transfer data onto the
sales and tenders is Transfer information to Reconcile payments
Log into Seller Central designated tab for each pivot tables ready for posting summary (SAS
calculated and the main Journal with the banks
report entry on the SAS report Report)
displayed

Rep 029 Dept Sales Rep 019 Del Receipts Rep 052 Gifting Receipts
information
SAS Sales

Net Sales - General ISA Order Foods ISA Order Foods

Net Sales - Foods ISA Order GM ISA Order GM
ISA Order Gift Vouchers ISA Order Gift Vouchers
Personal GV Sales PCA Order Foods PCA Order Foods
Sales less refunds PCA Order GM PCA Order GM
(net figure). The PCA Order Gift Vouchers PCA Order Gift Vouchers
figures are calculated WEB Order Foods WEB Order Foods
before any discounts WEB Order GM WEB Order GM
WEB Order Gift Vouchers WEB Order Gift Vouchers
Revenue less refunds before
any discounts Revenue less refunds before any discounts

Rep 005 Order Discounts

SAS Tenders

Rep 011 CATS Report Rep 145 Concession Details Rep 010 Non- Rep 006 Self Supply
Information

HSBC Takings Concessions Redeemed Food

Payment Refunds Payments by Promotion
Streamline Concessions used towards New WEB Customer
Refunds not paid Tracking ID
AMEX payment of an order Employee Discount
(shown as a negative)
Gift Card (SVC) Delivery
Original payment is a
Diners General Marketing Incentive
concession, refund is
Chargecard Summary of discounts
reported on here
Takings, refunds and applied, net of any applied to
net figures refunds

Rep 154 - Pending Rep 144 Concessions Issued Rep 171 SVC Sales Rep 173
Payments Weekly Use this in conjunction with by Shipment Departmental Sales
Analyse the aged debt report 145 to calculate the Analyse the Amazon for ISA Orders
Other

company liability. Do not use 146 figures against the Compare with the ISA
as it is inaccurate (this should be Bemrose information orders on report 029
used to show the complete
picture)

33
eCommerce Business Process - Checkpoint

 Confirm that we have satisfied our exit criteria

– High Level Business Process for Finance Reconciliation
– Documented Process including Sub-Processes
– Existing Reports with the Process or Sub-Process that they support
– Candidate List of Reports that are required in the new
solution
– Note any modifications to the business process that the new
solution may facilitate

34
Agenda

 Overview of the Workshop (10:00 to 10:15)

 Introductions (10:15 to 10:30)
 Scope and Approach to the Requirements Phase (10:30 to
10:45)
 Approach to Business Reporting Models (10:45 to 11:15)
 Coffee Break (11:15 to 11:30)
 eCommerce Business Process Review (11:30 to 12:00)
– From a Finance Reconciliation Perspective

 eCommerce Reporting Requirements (12:00 to 13:00)

– To support the Business Process for Finance

35
eCommerce Reporting Requirements

 Inputs
– Candidate List from Requirements section
– Existing Report Layouts/Examples
– Business Reporting Model aka Spider / Octopus

 Outputs
– Consolidated Report List
– Issues and Enhancements
– Report Look and Feel for Prototyping
– Data Gaps for Investigation

36
Drop Ship DN – Demand Notification

LOCATION
STORE ID
SHIP TO ADDRESS
TIME WAREHOUSE ID
EARLIEST SHIP DATE
LATEST SHIP DATE
EARLIEST DELIVERY DATE
LATEST DELIVERY DATE
EARLIEST NOMINATED DELIVERY DATE
LATEST NOMINATED DELIEVRY DATE
ORDER FACT

QUANTITY_TO_COMMIT
CUSTOMER_PRICE
NET_PRICE

PRODUCT
STORAGE TYPE
ORDER DEPT
STROKE NUMBER
ORDER LINE COLOUR CODE
CUSTOMER_ORDER_NUMBER COLOUR
IS GIFT PRIMARY SIZE

VENDOR
PARTY ID

37
Drop Ship TS – Trans Shipment

LOCATION
SOURCE WAREHOUSE ID
DESTINATION WAREHOUSE ID

TIME
SHIP BY DATE
RECEIVE BY DATE

ORDER FACT

QUANTITY_TO_SHIP

PRODUCT
ITEM ID

VENDOR
PARTY ID

38
Drop Ship DC – Demand Cancellation

LOCATION
WAREHOUSE ID

PRODUCT
ITEM ID

ORDER FACT

QUANTITY_TO_CANCEL

VENDOR
PARTY ID

39
Drop Ship OF – Order Fulfilment

LOCATION
STORE ID
TIME SHIP TO ADDRESS
BILL TO ADDRESS
ORDER DATE
EARLIEST SHIP DATE
LATEST SHIP DATE ORDER FACT
EARLIEST DELIVERY DATE TAX_AMOUNT
LATEST DELIVERY DATE PACKING_SLIP_AMOUNT
EARLIEST NOMINATED DELIVERY DATE CREDIT_CARD_AMOUNT
LATEST NOMINATED DELIEVRY DATE GIFT_WRAP_AMOUNT
PROMO_AMOUNT
GIFT_CERTIFICATE_AMOUNT
CHECK_AMOUNT
SHIP_CHARGE_AMOUNT
TRANSACTION_FEE_AMOUNT
SHIP_CHARGE_TAX
COD_CHARGE_AMOUNT
PRODUCT
QUANTITY_TO_SHIP ITEM_ID

ORDER SUB_TOTAL, ORDER_TOTAL

BALANCE_DUE
ORDER LINE
CUST ORDER NUMBER
VENDOR ORDER NUMBER
IS GIFT
IS COD
PAYMENT TYPES

VENDOR
PARTY ID

40
Drop Ship ASN – Advance Shipment Notification

LOCATION
WAREHOUSE ID

TIME
READY TO SHIP DATE
MANIFEST DATE

ORDER FACT

QUANTITY_SHIPPED
QUANTITY_NOT_SHIPPED
PACKAGE_WEIGHT

PRODUCT
ITEM_ID
SHIPMENT
SHIP_METHOD

VENDOR
PARTY ID

41
PCN – Purchase Confirmation

LOCATION
TIME STORE ID
ORDER DATE DELIVERY STORE ID
POSTED DATE RETURN WAREHOUSE
ITEM ARRIVAL DATE CUSTOMER ADDRESS
ORDER FACT
RETURN DATE BILL ADDRESS
SHIP_CHARGE
GIFT_WRAP_CHARGE
TOTAL_REVERSAL_AMOUNT
QUANTITY
ITEM_PRICE
PROMOTION_AMOUNT
SHIPMENT_QUANTITY
SHIPMENT_ITEM_PRICE
ORDER PRINCIPAL_AMOUNT
ORDER LINE SHIPPING_AMOUNT
TAX_AMOUNT
ORDER ID SHIPPING_TAX_AMOUNT
PAYMENT CHANNEL RESTOCKING_FEE_AMOUNT
MERCHANT PROMOTION ID
ADJUSTMENTS
RESTOCKING_FEE_TAX_AMOUNT
GIFTWRAP_TAX_AMOUNT
PRODUCT
PROMOTION ADJUSTMENTS SURCHARGE_AMOUNT SKU
RETURN_SHIPPING_AMOUNT TITLE
OTHER_AMOUNT SUPPLIER COLOUR CODE
COLOUR
SIZE
RANGE CODE
ITEM PRICE

RETURN
RETURN LINE
RETURN ITEM
RETURN CODE

42
43
Report 154 Pending Payments Weekly

 Fact : Measure
– Selling Value : SUM (ORDER_TOTAL) ?
– Delivery Charge : SUM (SHIP_CHARGE_AMOUNT)
– Gift Wrap Amount : SUM (GIFT_WRAP_AMOUNT)
– Free Delivery Promotion : SUM(PROMO_AMOUNT) WHERE …
– Staff Discount : SUM(PROMO_AMOUNT) WHERE …
– Concessions : SUM(PROMO_AMOUNT) WHERE …
– Other Promotions : SUM(PROMO_AMOUNT) WHERE …
– Net Pending Payments : SUM (BALANCE_DUE) ?

 Dimensions : Hierarchies
– Order Date : Date (Financial Calendar)
– Order Channel: ?
– Order ID: ?
– Department: Location
44
44
Report 154 Pending Payments Weekly

 Supporting Business Process

– Weekly Reconciliation of . . .
 Issues
– Issues
– Data Gaps
– Size?
– Performance?
 Opportunities
– Improvements
– Parameters
– Aggregation
– Drill Down
– Currencies
– Gross and Net values
– Dates
45
45
Business Reporting Requirements – Collaborative Session

For each report in Consolidated Candidate List:

Z – Measures

S – Selection Criteria Definitions Required

T – Report Tabs
X

Y Z
Required Drilldowns
with Hierarchies

D – Data Gaps I – Issues

46
47
48
49
50
51
52
53
54
55
56
57
58
eCommerce Reporting Requirements - Checkpoint

 Confirm that we have satisfied our exit criteria

– Consolidated Report List for Prototyping
– For each report in candidate list
– Issues and Enhancements
– Report Look and Feel for Prototyping
– Data Gaps for Investigation

59
Wrap Up and Next Steps

 Wrap Up
– Benefits and Concerns
– Review of Issues

 Next Steps
– Remaining Business Process Workshops
– Follow Up Finance Meeting 26th June if Required
– Prototyping of Reports
– Review of Report Prototypes w/c 6th July

 Thank You for your time!

60