Business Intelligence

Slides:



Advertisements
Similar presentations
Author: Graeme C. Simsion and Graham C. Witt Chapter 11 Logical Database Design.
Advertisements

Bus Matrix… the foundation of your Data Warehouse
Dimensional Modeling.
Tips and Tricks for Dimensional Modeling
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
Navigator Management Partners LLC Business Analysis Professional Development Day – Sep 2014 How to understand and deliver requirements to your Business.
Introduction to data warehouses
Dimensional Modeling Business Intelligence Solutions.
Dimensional Modeling CS 543 – Data Warehousing. CS Data Warehousing (Sp ) - Asim LUMS2 From Requirements to Data Models.
Data Warehouse IMS5024 – presented by Eder Tsang.
1 9 Ch3, Hachim Haddouti Adv. DBS and Data Warehouse CSC5301 Ch3 Hachim Haddouti Hachim Haddouti.
Data Warehousing - 3 ISYS 650. Snowflake Schema one or more dimension tables do not join directly to the fact table but must join through other dimension.
MIS 451 Building Business Intelligence Systems Logical Design (3) – Design Multiple-fact Dimensional Model.
Telecommunication Case Study CS 543 – Data Warehousing.
OLAP applications. Application areas OLAP most commonly used in the financial and marketing areas Data rich industries have been the most typical users.
Chapter 13 The Data Warehouse
Data Warehousing (Kimball, Ch.2-4) Dr. Vairam Arunachalam School of Accountancy, MU.
Data Warehousing DSCI 4103 Dr. Mennecke Introduction and Chapter 1.
Data Warehouse Toolkit Introduction. Data Warehouse Bill Inmon's paradigm: Data warehouse is one part of the overall business intelligence system. An.
Data warehousing theory and modelling techniques Building Dimensional Models.
Agenda Common terms used in the software of data warehousing and what they mean. Difference between a database and a data warehouse - the difference in.
Sayed Ahmed Logical Design of a Data Warehouse.  Free Training and Educational Services  Training and Education in Bangla: Training and Education in.
All rights reserved. © 2009 Tableau Software Inc. Dallas Cowboys: Sports Merchandising with Tableau Bill Priakos COO – Dallas Cowboys Merchandising Bill.
1 Brett Hanes 30 March 2007 Data Warehousing & Business Intelligence 30 March 2007 Brett Hanes.
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
Decision Support System Definition A Decision Support System is an interactive computer-based system or subsystem that helps people use computer communications,
Data Warehouse Architecture. Inmon’s Corporate Information Factory The enterprise data warehouse is not intended to be queried directly by analytic applications,
Organizing Data and Information AD660 – Databases, Security, and Web Technologies Marcus Goncalves Spring 2013.
Dimensional model. What do we know so far about … FACTS? “What is the process measuring?” Fact types:  Numeric Additive Semi-additive Non-additive (avg,
Data Warehouse and Business Intelligence Dr. Minder Chen Fall 2009.
DIMENSIONAL MODELLING. Overview Clearly understand how the requirements definition determines data design Introduce dimensional modeling and contrast.
Chapter 1 Adamson & Venerable Spring Dimensional Modeling Dimensional Model Basics Fact & Dimension Tables Star Schema Granularity Facts and Measures.
1 Data Warehouses BUAD/American University Data Warehouses.
BMI Consulting Business Intelligence Roadmap Business Analysis Requirements Subject Modeling.
Bus Architecture. Value Chain Identifies the natural logical flow of an organization’s primary activities Operational source systems produce snapshots.
1 Reviewing Data Warehouse Basics. Lessons 1.Reviewing Data Warehouse Basics 2.Defining the Business and Logical Models 3.Creating the Dimensional Model.
INVENTORY CASE STUDY. Introduction Optimized inventory levels in stores can have a major impact on chain profitability: minimize out-of-stocks reduce.
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
Overview of PeopleSoft Data Warehouse Implementation August 3, 2006.
UNIT-II Principles of dimensional modeling
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
June 08, 2011 How to design a DATA WAREHOUSE Linh Nguyen (Elly)
1 Copyright © 2009, Oracle. All rights reserved. Oracle Business Intelligence Enterprise Edition: Overview.
Dimensional Modeling Primer Chapter 1 Kimball & Ross.
Fundamentals of Information Systems, Sixth Edition Chapter 3 Database Systems, Data Centers, and Business Intelligence.
The Need for Data Analysis 2 Managers track daily transactions to evaluate how the business is performing Strategies should be developed to meet organizational.
Building the Corporate Data Warehouse Pindaro Demertzoglou Data Resource Management.
Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 9: DATA WAREHOUSING.
Building the Corporate Data Warehouse Pindaro Demertzoglou Lally School of Management Data Resource Management.
Atlantic Coast Operations Business Intelligence Mobility Project.
INTRO TO SAP EWM.
Operation Data Analysis Hints and Guidelines
Chapter 13 Business Intelligence and Data Warehouses
Chapter 13 The Data Warehouse
Data Warehouse—Subject‐Oriented
Fundamentals of Information Systems
Data Warehouse.
OLAP Systems versus Statistical Databases
Applying Data Warehouse Techniques
Overview and Fundamentals
Dimensional Model January 14, 2003
Inventory is used to illustrate:
Applying Data Warehouse Techniques
An Introduction to Data Warehousing
Applying Data Warehouse Techniques
Data Warehousing Concepts
Applying Data Warehouse Techniques
Review of Major Points Star schema Slowly changing dimensions Keys
Applying Data Warehouse Techniques
Presentation transcript:

Business Intelligence INVENTORY CASE STUDY

Introduction Optimized inventory levels in stores can have a major impact on chain profitability: minimize out-of-stocks reduce overall inventory carrying costs

We will examine this in our Analysis Services project Value chain example We will examine this in our Analysis Services project Value chain What is the primary objective of most analytic decision support systems ?  monitor the performance results of key business processes each business process produces unique metrics at unique time intervals with unique granularity and dimensionality each process typically spawns one or more fact tables value chain provides high-level insight into the overall enterprisedata warehouse

Some Common Questions related to Inventory How did the inventory level changed per product, per warehouse over time? How is the profitability of products in our inventory? How many times have we placed a product into an inventory bin on the same day we picked the product from the same bin at a different time? How many separate shipments did we receive from a given vendor, and when did we get them? On which products have we had more than one round of inspection failures that caused return of the product to the vendor? … etc.  BI helps answering these questions

BI Inventory Models The three main models discussed: Inventory Periodic Snapshot Inventory Transactions Inventory Accumulating Snapshot They are complementary models, and provide different information about the Inventory

Periodic Snapshot The most common inventory scheme Example of Retail Store Chain Inventory: The assumed atomic level of detail is: Inventory per product Per day Per Store Basic dimensions: Product Day Store Fact: Inventory

Simple Inventory Periodic Snapshot Usage: Provide information about inventory levels: Daily Inventory level Average Inventory level over a time period Problems: Inventory levels are semi-additive (i.e. NOT additive through each dimension)  Through the Date dimension the quantity on hand is NOT additive Historical Inventory data using daily granularity results in unreasonably huge amount of data over time  Suggestion to define distinct atomic time period for short and long term measures

Enhanced Inventory Periodic Snapshot Extra recorded facts Velocity of inventory movement becomes measurable Key concepts: Number of Turns Number of days’ supply Growth Margin Return on Inventory (GMROI)

Enhanced Inventory Periodic Snapshot Extra recorded facts measure daily Over a period Number of Turns Number of days’ supply GMROI

Enhanced Inventory Periodic Snapshot GMROI - Growth Margin Return on Inventory Turns Gross margin High GMROI lots of turns high gross margin Low GMROI low turns low gross margin GMROI is a standard metric used by inventory analysts to judge a company’s quality of investment in its inventory. We do not store GMROI in the fact table because it is not additive!!!

Inventory Transactions Receive product Place product into inspection hold Release product from inspection hold Return product to vendor due to inspection failure Place product in bin Authorize product for sale Pick product from bin Package product for shipment Ship product to customer Receive product from customer Return product to inventory from customer return Remove product from inventory Record every transaction that affects inventory:

Inventory Transactions Use: Measure the frequency and timing of specific transaction types Example: How many times have we placed a product into an inventory bin on the same day we picked the product from the same bin at a different time? How many separate shipments did we receive from a given vendor, and when did we get them? On which products have we had more than one round of inspection failures that caused return of the product to the vendor?

Inventory Accumulating Snapshot In progress!!! In a single fact table row we track the disposition of the product shipment until it has left the warehouse only possible if we can reliably distinguish products delivered in one shipment from those delivered at a later time also appropriate if we are tracking disposition at very detailed levels, such as by product serial number or lot number

Inventory Accumulating Snapshot

Fact Table Type Comparison Periodic Snapshot Transaction Accumulating Snapshot Time period represented Regular predictable intervals Point in time Indeterminate time span, typically short lived Grain One row per period One row per transaction event One row per life Table loads Insert Insert and update Row updates Not revisited Revisited whenever activity Date dimension End-of-period Transaction date Multiple dates for standard milestones Facts Performance for predefined time interval Transaction activity Performance over finite time

Value Chain Integration Integrating business processes together benefits: Intelligence aspects: Better understand customer relationships from an end-to-end perspective Observe information across business processes Technological aspects: Reusability Less resources used Question: How do we properly integrate all business processes in the enterprise? Answer: Data Warehouse Architecture

Data Warehouse Bus Architecture “Common structure to which everything can and is connected” Data Warehouse Bus Architecture: Defining a standard warehouse architecture (bus interface) to which different data marts can connect. Standardizes dimensions and facts that have uniform interpretation across the enterprise. Architectural framework for the overall design and separate data marts following the framework.

Data Warehouse Architecture Kimball vs. Inmon Bill Inmon and Ralph Kimball – the co-founders of the data warehouse concept and their views on data warehouse architecture Dependent Data Mart Structure (Inmon) Let everyone build what and when they want and we will integrate it if we need it. Each data mart gets information from the operational data base and then data is loaded in the data warehouse Data Warehouse Bus Structure (Kimball) Design everything then build. The data warehouse is responsible for loading data in the data marts from the operational database.

Bus Matrix The tool we use to document the Data Warehouse Bus Architecture A part technical, part management, part communication tool Business processes as ROWS Common dimensions as Columns

Bus Matrix (cont.) Rows : Columns: Business processes A business process translates into a First-Level Data Mart Each Data Mart spanning over multiple business processes translates into a Consolidated Data Mart (E.G. Profitability) Columns: Common Dimension used across the enterprise Consequences of improper or non-existent bus matrix: Isolated data marts blocking the coherent warehouse environment, narrowing down the scope of information to be viewed. Expansion of the data warehouse is nearly impossible

Conformed Dimensions What are conformed dimensions: The cornerstone of the Bus Architecture A single, coherent view of data across the enterprise that can be reused across different Data Marts. Conformed dimensions have: Consistent dimension keys Consistent attribute values Consistent naming, attribute definitions.

Conformed dimensions (cont.) Some characteristics of conformed dimensions Each conformed dimension has the same meaning in each Data Mart They are defined at the most granular level possible

Conformed dimensions (cont.) Some considerations when defining conformed dimensions Rolled-up dimensions Rolled-up dimensions – having higher level of granularity Rolled-up dimensions conform to the base-level atomic dimension if they are a strict subset of that dimension

Conformed dimensions (cont.) - Considerations (cont.) Dimension subsetting Two dimensions with same level of detail but representing different subsets of rows or columns Rolled-up dimensions are another example of dimension subsetting Advised Solution – dimension authority Has responsibility for defining, maintaining and publishing dimensions and their subsets to all Data Marts

Conformed Facts Conformed facts are: Facts used living in more that one data mart. Same rules and characteristics apply in designing and implementing them as with conformed dimensions Few more considerations are: Units of measure for the fact Identical labeling Underlying definitions and equations