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

Sign-in   Register
Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline
  Traditional vs. Holistic View of Execution Management  

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

One tier Data Warehouse

This is most basic set-up having a staging database accessed by end-user tools

This may look like a staid scenario, but even today more than 80% of the enterprises are working on this set-up.

This is the most basic of the information delivery topology and does not include any Data Warehouse OR a Data Mart. As per this topology, data is pulled out from the source systems and placed in a common staging database. Most of the organizations have this level of basic topology. This is not a strategic decision , but an inevitable operational need. This topology can provide excellent source of production/schedule reporting and also some degree of low intensity analysis using front-end analysis tools.

There can be following levels of sophistication:

Basic Level

Objective is to have offline reporting to ensure no impact on production and have reporting across the systems.

  • The entire set data tables are cut & paste from the source systems. It may not however, include the log and other control tables.
  • No historical information. This is typical overwrite.
  • Data is in as much normalized state as the source systems.
  • No Transformation OR standardization of data.
  • No aggregates.
  • Standard & scheduled production reports.

Medium Level:

Objective is to have more sophisticated and cleaner staging and also allow some level of aggregate analysis. This should allow the reports covering the time spans.

  • Data is pulled out selectively in terms of tables and fields with in the tables.
  • The historical data is appended.
  • Data is in normalized state.
  • Some derived attributes and aggregates are generated.

High Level:

Objective is to provide a clean repository with a level of standardization & uniformity. It has the following additional features:

  • The interlinking of diverse Customer codes, references, product codes etc. by changing the codes OR by creating the mapping tables. This enables a true-blue enterprise wide reporting.
  • Medium level of Cleansing of data. This means that the key
  • Many derived attributes and aggregates.

If an organization has reached to the “High Level” state (without any Data Warehouse), it has progressed at least 30% of the journey in achieving Information Management journey. By this time organization has understood most of quality issues and resolved some of them. The reporting teams have gone through the first set of Extraction and Transformation experience.

 

  Traditional vs. Holistic View of Execution Management  
 
 

Was this page helpful?
 
 
More on BI Architecture Scenarios
2 tier DW Architecture- Independent Data Marts
Two tier DW Architecture- Staging and DW
3 Tier DW -Business Intelligence Architecture
BI Mixed Data Access
BI Metadata Architecture Scenarios
BUY BI & Data Management Vendors & Tools Evaluation Kit
Read more...
BUY largest on-line Data-Quality Management Kit
Read more...
Additional Channels
Principles & Rules
Free Templates
Glossary
Key Performance Indicators



Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales productivity
Sales Cost and Profitability Overview
Sales Compensation Management
Sales Process Management
Sales Behavior
Read more...
  Customer Relationship Management
What is Customer Segmentation?
Customer Segmentation Actions
Customer Value and Profitability- BI
Customer Knowledge and Organizational Knowledge
Supply Chain for Customer Service and Support
Read more...
  Human Resources & Leadership
Customer Focus
Roles and Level based Competency Segregation
Fitting leadership dimension in employee performance
Developing Leaders- Few Leadership Traits
Develop Self and Others
Read more...
 
 
Business Performance & Planning
Strategic Vision and Mission
Creating Strategy Blueprint
Never design performance systems for specific KPI
Stakeholder test for Scorecard
Strategic Planning leadership commitment
Read more...
  Business Intelligence & Data Quality
Data Warehouse ETL Transformation
Invest in Naming strategy
Master Data Management vs. BI vs. Metadata
Avoid Pure MOLAP
Super-flexible Data warehouse
Read more...
  IT Vendors & Tools Management
Multi Cube OLAP Architecture
Vendor Delivery Evaluation Training
Technical Customization Evaluation
Vendor Delivery Support Model
Data Quality through Data Integration Tools
Read more...