Scribd
Upload
11 views23 pages

Grocery Store Data Warehouse: Dr. Navneet Goyal Professor Computer Science Department BITS, Pilani

The document outlines the design and implementation of a data warehouse for a chain of grocery stores in the US, detailing business processes such as sales, inventory, and procurement. It describes the star schema structure, types of facts, and the importance of modeling promotion dimensions to analyze the effectiveness of promotional strategies. Additionally, it provides insights into database sizing and the overall architecture of the data warehouse, including various dimensions and fact tables.

Uploaded by

pratikkange@gmail.com
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
11 views23 pages

Grocery Store Data Warehouse: Dr. Navneet Goyal Professor Computer Science Department BITS, Pilani

The document outlines the design and implementation of a data warehouse for a chain of grocery stores in the US, detailing business processes such as sales, inventory, and procurement. It describes the star schema structure, types of facts, and the importance of modeling promotion dimensions to analyze the effectiveness of promotional strategies. Additionally, it provides insights into database sizing and the overall architecture of the data warehouse, including various dimensions and fact tables.

Uploaded by

pratikkange@gmail.com
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 23

Grocery Store

Data Warehouse

Dr. Navneet Goyal


Professor
Computer Science Department
BITS, Pilani
Business Processes
• Sales
• Inventory
• Procurement
• Order Management
• Promotion
Value Chain

Retailer Issues Deliveries @ Retailer WH


Purchase Order Retailer WH Inventory

Retail Store Retail Store Deliveries @


Sales Inventory Retail Store
The Scenario
•A chain of grocery stores in the US
• 100 stores
• 60,000 individual products on the shelves in
each store
• 6,000 products (on an average) sell each day in a
given store
• Each product belongs to a subcategory
• Each subcategory belongs to a category
• Each category belongs to a department
Some Terms

• SKU (Stock Keeping Units)


• UPC (Universal Product Codes)
• EPOS ( Electronic Point of Sales)
What Management is
Interested In?
• Ordering logistics

• Stocking shelves
• Selling products
• Maximize profits
Data Warehouse:
Design Steps
Step 1: Identify the Business Process

Step 2: Declare the Grain

Step 3: Identify the Dimensions

Step 4: Identify the Facts


Star Schema

Product FK Location
Dimension FK Dimension

Sales Fact
Table

Time FK Promotion
Dimension FK Dimension
The “Classic” Star
SchemaFact Table
Store STORE KEY
Time Dimension
Dimension PRODUCT KEY
STORE KEY
PERIOD KEY PERIOD KEY
Store
Description Dollars_sold
Units Period Desc
City
Dollars_cost Year
State
District ID Quarter
District Desc. Month
Region_ID Day
Product Dimension
Region Desc.
Regional Mgr. PRODUCT KEY
Product Desc.
Brand
Color
Size
Manufacturer
Types of Facts
 Fully-additive-all dimensions
 Units_sold, Sales_amt

 Semi-additive-some dimensions
 Account_balance, Customer_count
28/3,tissue paper,store1, 25, 250,20
28/3,paper towel,store1, 35, 350,30
Is no. of customers who bought either tissue paper or
paper towel is 50? NO.
 Non-additive-none
 Gross margin=Gross profit/amount
 Note that GP and Amount are fully additive
 Ratio of the sums and not sum of the ratios
Facts for Grocery Store
1. Quantity sold (additive)
2. Dollar revenue (additive)
3. Dollar cost (additive)
4. Customer count (semi-additive, not additive along
the product dimension)
Fact Table for Grocery
Store
Field name Example Description/Remarks
Values
Date key (FK) 1 Surrogate key

Product key (FK) 1 Surrogate key

Store key (FK) 1 Surrogate key

EPOS transaction 100 Trancsaction number generated by the


no. Operational system to record sales

Sales Quantity 2 No. of units bought by a customer

Sales amount 72 Amount received by selling 2 units

Cost amount 65 Cost price of 2 units


Promotion Dimension
 Causal Dimension
 Which causes or being the cause
 Promotion conditions include
 TPRs
 End-aisle displays
 Newspapers ads
 Coupons
 Combinations are common
Promotion Dimension
 Management is interested in knowing how
effective their promotion schemes are
 Promotion are judged on the basis of:
 Lift and Baseline sales
 Time shifting
 Cannibalization
 Growing the market
Modeling Promotion
Dimension
 Difficult to capture the effect of promotion
 Little or NO provision in operational system
to capture promotions
 Multiple promotion schemes at the same time
 Promotion schemes applicable to many
products
 Different grain than sales
 What about products that were on promotion
but not sold?
Modeling Promotion
Dimension
 Captures combination of promotion techniques in
effect at the time of sale
 Promotions are generally at a higher grain than sales
fact table
 Adding a promotion dimension is thus possible
 Promotion and product relationship is captured
implicitly in the fact table
 But we are missing out on one important piece of
information
 Products on promotion that did not sell
Modeling Promotion
Dimension
 Different causal conditions are highly
correlated
 Create one row for each combination of
promotion conditions
 All stores run 3 promotion mechanisms
simultaneously, but a few stores are not able
to deploy end-aisle displays
 One record for combination of 3
 One record for combination of 2
Modeling Promotion
Dimension
 In one year, there may be 1000 ads, 5000 TPRs, and
1000 end-aisle displays
 Only 10000 combinations of these three conditions
affecting a particular product
 A sample promotion dimension
Promotion key Coupon type
Promotion name Ad media type
TPR type Display Provider
Promotion Media type Promotion Cost
Ad type Start Date
Display type End Date……
 Include a NO promotion in effect row in promotion
dimension
Modeling Promotion
Dimension
 Promotion Coverage Factless Fact Table
 Same Dimensions apply as that for Sales fact table
 So what is different?
 Is the grain different?
 One row in the fact table for each product in a store each
day ( or week ) regardless of whether the product was
sold or not
 NO FACTS INVOLVED!!
 How to find products that were on promotion on a day
but did not sell?
Database Sizing

FACT TABLE SIZE


 3 year data
 100 stores
 Daily grain
 60,000 SKUs
 Sparsity = 10%
 4 dimensions (16 bytes)
 4 facts (16 bytes)
Total Size=3x365x100x6000x3220 GB
Sample Data Warehouse
Time Dimension
Product Dimension
Store Dimension
Promotion Dimension
Sales Fact Table
Promotion Coverage Fact Table
Q&A
Thank You

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy