The Organisation As A System An information management framework The Performance Organiser Data Warehousing.

Slides:



Advertisements
Similar presentations
The Organisation As A System An information management framework
Advertisements

Author: Graeme C. Simsion and Graham C. Witt Chapter 11 Logical Database Design.
Data Warehousing Design Transparencies
Designing MS-Access Tables
Dimensional Modeling.
Tips and Tricks for Dimensional Modeling
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Cognos 8 Training Session
1 Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal or quotation. An Introduction to Data.
IS 4420 Database Fundamentals Chapter 11: Data Warehousing Leon Chen
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
C6 Databases.
Copyright © Starsoft Inc, Data Warehouse Architecture By Slavko Stemberger.
Dimensional Modeling CS 543 – Data Warehousing. CS Data Warehousing (Sp ) - Asim LUMS2 From Requirements to Data Models.
Data Warehouse IMS5024 – presented by Eder Tsang.
Exploiting the DW data DW is a platform for creating a wide array of reports It solves data feed problems, but does not lead to specific decision support.
Data Warehousing Design Transparencies
MIS 451 Building Business Intelligence Systems Logical Design (3) – Design Multiple-fact Dimensional Model.
Data Warehousing DSCI 4103 Dr. Mennecke Introduction and Chapter 1.
Building a Data Warehouse with SQL Server Presented by John Sterrett.
Online Analytical Processing (OLAP) Hweichao Lu CS157B-02 Spring 2007.
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.
The Relational Database Model
DWH – Dimesional Modeling PDT Genči. 2 Outline Requirement gathering Fact and Dimension table Star schema Inside dimension table Inside fact table STAR.
Best Practices for Data Warehousing. 2 Agenda – Best Practices for DW-BI Best Practices in Data Modeling Best Practices in ETL Best Practices in Reporting.
Data Warehouse Architecture. Inmon’s Corporate Information Factory The enterprise data warehouse is not intended to be queried directly by analytic applications,
Dimensional model. What do we know so far about … FACTS? “What is the process measuring?” Fact types:  Numeric Additive Semi-additive Non-additive (avg,
OnLine Analytical Processing (OLAP)
Cube Intro. Decision Making Effective decision making Goal: Choice that moves an organization closer to an agreed-on set of goals in a timely manner Goal:
Program Pelatihan Tenaga Infromasi dan Informatika Sistem Informasi Kesehatan Ari Cahyono.
Data Warehousing Concepts, by Dr. Khalil 1 Data Warehousing Design Dr. Awad Khalil Computer Science Department AUC.
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.
Data Warehouse. Design DataWarehouse Key Design Considerations it is important to consider the intended purpose of the data warehouse or business intelligence.
1 Data Warehouses BUAD/American University Data Warehouses.
The Data Warehouse “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of “all” an organisation’s data in support.
BI Terminologies.
Operational vs. Informational System. Operational System Operational systems maintain records of daily business transactions whereas a Data Warehouse.
Decision Support and Date Warehouse Jingyi Lu. Outline Decision Support System OLAP vs. OLTP What is Date Warehouse? Dimensional Modeling Extract, Transform,
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
DIMENSIONAL MODELING MIS2502 Data Analytics. So we know… Relational databases are good for storing transactional data But bad for analytical data What.
Operation Data Analysis Hints and Guidelines EGN 5621 Enterprise Systems Collaboration Summer B, 2014.
UNIT-II Principles of dimensional modeling
Presented By: Solutions Delivery Managing Reports in CRMnext.
Building Dashboards SharePoint and Business Intelligence.
The Data Warehouse “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of “all” an organisation’s data in support.
1 Agenda – 04/02/2013 Discuss class schedule and deliverables. Discuss project. Design due on 04/18. Discuss data mart design. Use class exercise to design.
Pooja Sharma Shanti Ragathi Vaishnavi Kasala. BUSINESS BACKGROUND Lowe's started as a single hardware store in North Carolina in 1946 and since then has.
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.
1 Database Systems, 8 th Edition Star Schema Data modeling technique –Maps multidimensional decision support data into relational database Creates.
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.
The Concepts of Business Intelligence Microsoft® Business Intelligence Solutions.
Operation Data Analysis Hints and Guidelines EIN 6133 Enterprise Engineering Fall, 2015.
Building the Corporate Data Warehouse Pindaro Demertzoglou Lally School of Management Data Resource Management.
Operation Data Analysis Hints and Guidelines
Data warehouse and OLAP
Data Warehouse.
Star Schema.
Competing on Analytics II
Dimensional Model January 14, 2003
MIS2502: Data Analytics Dimensional Data Modeling
Data Warehouse and OLAP
MIS2502: Data Analytics Dimensional Data Modeling
MIS2502: Data Analytics Dimensional Data Modeling
Retail Sales is used to illustrate a first dimensional model
Dimensional Model January 16, 2003
Data Warehouse and OLAP
Presentation transcript:

The Organisation As A System An information management framework The Performance Organiser Data Warehousing

The Performance Organiser A data warehouse is a repository of an organization's electronically stored data, designed to facilitate reporting and analysis. A data warehouse is sometimes referred to as a data mart.

Data Warehousing The Performance Organiser Perhaps the two most well know forms of data stored in a data warehouse are: Datebases Data stored in rows and columns and related tables as a database Document Folders 01 -Design02 -Accounts 03 - Production Or a series of files, in multiple formats stored in a directory structure

Data Warehousing The Performance Organiser While both can be analysed and analysis tools exist to search and collate each of them, the sheer volume of data contained in either or both, can turn any analysis effort into a complex and time consuming exercise.

Data Warehousing The Performance Organiser As a consequence, there is a need for a third type of data storage that provides the means to store the analysis results of the bulk of data but also gives the the means to drill down into the main data stores if required.

Data Warehousing The Performance Organiser Datebases Document Folders 01 -Design02 -Accounts 03 - Production That third form is known as the Fact Table and enables the concept of On Line Analytical Processing

Data Warehousing The Performance Organiser A fact table consists of the measurements, metrics or facts of a business process. Fact tables have their own structure or schema. Often, when drawn, their schema takes the shape of a star, or snowflake, with the fact table surrounded by dimension tables, which as mathematically based summaries of main data tables.

Data Warehousing The Performance Organiser Fact tables provide the (usually) additive values that act as independent variables by which dimensional attributes are analyzed. Fact tables are often defined by their grain. The grain of a fact table represents the most atomic level by which the facts may be defined. The grain of a SALES fact table might be stated as "Sales volume by Day by Product by Store". Each record in this fact table is therefore uniquely defined by a day, product and store. Other dimensions might be members of this fact table (such as location/region) but these add nothing to the uniqueness of the fact records. These "affiliate dimensions" allow for additional slices of the independent facts but generally provide insights at a higher level of aggregation (a region contains many stores).

Data Warehousing The Performance Organiser Additive - Measures that can be added across all dimensions. Non Additive - Measures that cannot be added across all dimensions. Semi Additive - Measures that can be added across few dimensions and not with others.

Data Warehousing The Performance Organiser A fact table might contain either detail level facts or facts that have been aggregated (fact tables that contain aggregated facts are often instead called summary tables). Special care must be taken when handling ratios and percentage. One good design rule is to never store percentages or ratios in fact tables but only calculate these in the at the business of presentational level. Thus only store the numerator and denominator in the fact table, which then can be aggregated and the aggregated stored values can then be used for calculating the ratio or percentage at the business logic or presentational level.

Data Warehousing The Performance Organiser Fact table design approach: Identify a business process for analysis (like sales). Identify measures or facts (sales value), by asking questions like what number of XX are relevant for the business process (Replace the XX, and test if the question makes sense business wise). Identify dimensions for facts (product dimension, location dimension, time dimension, organization dimension), by asking questions which makes sense business wise, like 'Analyse by' XX, where XX are replaced with the subject to test. List the columns that describe each dimension (region name, branch name, business unit name). Determine the lowest level (granularity) of summary in a fact table (e.g. sales).

Data Warehousing The Performance Organiser If the business process is SALES, then the corresponding fact table will typically contain columns representing both raw facts and aggregations in rows such as: £12,000, being "sales for A store for 15-Jan-2005" £34,000, being "sales for B store for 15-Jan-2005" £22,000, being "sales for C store for 16-Jan-2005" £50,000, being "sales for D store for 16-Jan-2005" £21,000, being "average daily sales for A for Jan-2005" £65,000, being "average daily sales for B Store for Feb-2005" £33,000, being "average daily sales for C Store for year 2005" "average monthly sales" is a measurement which is stored in the fact table.

Data Warehousing The Performance Organiser The fact table also contains foreign keys from the dimension tables, where time series (e.g. dates) and other dimensions(e.g. store location, salesperson, product) are stored. All foreign keys between fact and dimension tables should be surrogate keys, not reused keys from operational data. The centralized table in a star schema is called a fact table. A fact table typically has two types of columns: those that contain facts and those that are foreign keys to dimension tables. The primary key of a fact table is usually a composite key that is made up of all of its foreign keys. Fact tables contain the content of the data warehouse and store different types of measures like additive, non additive, and semi additive measures.

Data Warehousing The Performance Organiser Fact table data provides the primary data feed for kpi reporting and monitoring. From KPIs come the status indicators for higher level monitoring mechanisms like scorecards and dashboards.

The Performance Organiser Single KPI Dashboard Data Warehousing Qualitative Quantitative Achievable mean Achievable Best Worst Time Qualitative or Quantitative Scale JFMAMJJASOND Current achievable mean = 22 Achievable mean = 28 Flag state = Green For each indicator provide additional documentary evidence

Data Warehousing The Performance Organiser No of widgets Produced No of widgets unfit for purpose

Data Warehousing The Performance Organiser The collation and summary of facts from main table data will mean running additional processes (typically out of normal working hours) which in turn will mean a time delay between the collation exercise and its readiness for delivery at the presentation or dashboard level. However, the speed of response for reporting purposes will be greatly enhanced

Data Warehousing The Performance Organiser Datebases Document Folders 01 -Design02 -Accounts 03 - Production A data warehouse typically consists of three data forms. Two, the databases and document libraries contain the bulk of an organisations data. The third form, Fact Tables, contain summary data, usually of the database content, the primary function of which is to provide accurate, timely analysis. Fact tables should provide the primary reporting source for kpis.

Data Warehousing The Performance Organiser While fact tables present their own information management issues, they are one of the key tools in an information managers armoury that facilitates decision support. Fact tables can be further supported by techniques like pattern recognition, but for majority of circumstances, a mix of fact tables and bulk data stores, linked by a common referencing system will meet the most significant reporting requirements information managers will meet