Sales Management Customer Relationship Human Resources Business Performance BI & Data Quality IT Tools & Vendors

  Register
Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline
   Performance Scorecard vs. Execution Scorecard BI Mixed Data Access  

ENCYCLOPEDIA→   Enterprise Intelligence  →   -  BI End-to-End  →   -  Business Intelligence Architecture Scenarios  → 

Three Tier Data Warehouse -Business Intelligence Architecture

This scenario has a Data Warehouse supplying to Data Marts.

In the environments, which are advanced and have grown over time, this is the most probable state. As per this topology, the Staging Area feeds into the Data Warehouse and the data warehouse feeds into the independent Data Marts.

This BI Architecture raises two questions:

The first question is on why to have additional layers of data marts, if Data Warehouse exists? There are many reasons for the same:

  • A Data Mart already in use: If a data mart exists, and has been used extensively, this approach ensures a complete transparency from a user point of view.
  • Reducing Network Traffic: In large organizations, you may not like to have the users across the globe to be accessing a central data Warehouse. Data Marts on local servers are created to allow a faster response with reduced WAN traffic.
  • Security: Data Mart creates a physical barrier to deter the users to access the irrelevant information.
  • Easy operation: For the power users it is important to be able to configure, browse and create views over the limited set of dimensions and measures useful for them.

The second question is the reverse of the first one. That is- what’s the need for Data Warehouse , when Data Marts exist? One can directly load the data from the staging database. The concept of foundation dimensions & measures and Dimensional Model can be implemented in the staging database level. The reasons for the relevance of Data Warehouse in this topology are as follows:

  • A Data Warehouse provides quick access refresh for the data marts: A Loading process from staging takes greater amount of time. As Data Warehouse structure and layout is very similar to a Data Mart, this refresh takes lesser degree of time.
  • Flexibility in creating of changing the Data Marts: In this topology, a Data Mart can be changed quite fast (unless it is introducing a dimension, measure OR an attribute which does not exist in Data Warehouse) as it has no impact on Data Warehouse design OR the ETL process. Loading direct from staging will impact the changes done to Data Mart design.
  • A Data Warehouse may still be accessed for information outside of a Data Mart: Sometimes a data warehouse will be accessed for transaction level reports OR some ad-hoc analysis requirements, which don’t warrant the creation of a Data-Mart. Therefore the core purpose of Data Warehouse to serve as a enterprise system of record, still needs to be fulfilled.

   Performance Scorecard vs. Execution Scorecard BI Mixed Data Access  
All Topics in: "Business Intelligence Architecture Scenarios" Chapter
 One tier business intelligence with Staging area →  Two tier Data Warehouse Architecture- Independent Data Marts →  Two tier Data Warehouse Architecture- Staging and Data Warehouse →  Three Tier Data Warehouse + Data Mart BI Architecture →  Mixed Data Access Business Intelligence Architecture →  Business Intelligence Metadata Architecture centralized distributed Scenarios → 
More on BI Architecture Scenarios
One tier Data Warehouse
2 tier DW Architecture- Independent Data Marts
Two tier DW Architecture- Staging and DW
BI Mixed Data Access
BI Metadata Architecture Scenarios
BUY BI & Data Management Vendors & Tools Evaluation Kit
BUY largest on-line Data-Quality Management Kit
Additional Channels
Principles & Rules
Free Templates
Key Performance Indicators

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales Channel Retention, Support and Engagement
Sales Channel Management Overview
Sales Compensation Management
Sales Campaign Business Intelligence
Sales Leads Classification and prioritization
  Customer Relationship Management
Supply Chain for Customer Service and Support
Customer-Centric product-service management
Customer Knowledge and Organizational Knowledge
Customer Satisfaction & Retention- Data Management
Customer Value and Profitability-Overview
  Human Resources & Leadership
Setting Strategic Intent and Alignment
Lead diverse and collaborative teams
Fostering Innovation
Develop Self and Others
Fitting leadership dimension in employee performance
Business Performance & Planning
Strategic Business Plan
Shifting the mind-set to leading Indicators- KPIs
A KPI should be simple -but it depends
Individual goal Sheet
Never design performance systems for specific KPI
  Business Intelligence & Data Quality
Data Warehouse Implementation Deployment
BI Competency Centre- Establish Phase
Rationalization of Information
Data Warehouse Change and Enhancement
Data Warehouse is beyond Analytics
  IT Vendors & Tools Management
Collaboration and Administration Support
Technical Evaluation- Interoperability
Metadata Tool administration Security
Vendor Delivery Support Model
Business Intelligence Vendor Evaluation