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
Principles and Rules Listing Page

Data Marts should be ideally based upon a business process and not on a department.

Data-Marts as they start for a function or a department, can still be designed on a process or a theme.
 
This page of 'Principles and Rules' is linked to:  Data Warehousing, BI business intelligence end-to-end view, Data Analysis/OLAP, BI platform Tools Evaluation,

All of us are aware that Data Marts are a part of natural evolution towards a bigger data warehouse initiative. It does not mean that one cannot have big bang Data Warehouse initiatives, but they are generally rare. It also does not mean that Data warehouse and data marts cannot co-exist (Refer Data Warehouse vs Data Marts ). When you work on a data mart, it should be more around a business process (like Leads Management, order processing, Customer Service ) even if it touches multiple departments. For example customer service themes could include Quality Management, Product Management and Distribution Management etc. This ensures that you have a single dimensional model and a source of truth for a given theme.

In real life, in the initial stages of data marting, it becomes a challenge for the departments to work as a team to develop a common dimensional model. However, if this challenge is not over-come early, you will end-up with many data marts providing the same set of information.

The question is how to make individual departments to work to gather to make business process based Data-Marts. This challenge exists, when an organization is not thinking of an enterprise level data warehouse. The best way to handle it is to assign the business process champions and encourage them to drive the Data-mart initiatives. For example, while ops, sales and marketing all work on leads management, you may assign someone in marketing as the champion of overall success of leads management. This role will be like a practice head for leads management, who creates guidelines, best practices, tracking mechanisms etc for leads management. This role will be better equipped to drive data mart around leads management process.

This trick is lesser solution to 'head of information management' kind of enterprise level role, which will be driving data warehouse or data-mart initiatives. If you have an enterprise level role, that role can drive the choice of business themes and also the road-map of all DW efforts in the enterprise. In that case the challenge of process-based vs. functional data-mart will not be of much bearing.


Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Add extra buffer for ETL phase → Principles & Rules → Homework before interviews is must (Business Requirements Phase in Data Warehouse) → Principles & Rules → Excel is the competition, which should be challenged → Principles & Rules → Avoid Pure MOLAP → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Consolidate Data-Marts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards → Practice Techniques → Field Tips Series- Streamlining & reducing cost of Business Intelligence- Evaluate Open Source → Principles & Rules → Master Data Management- Making a Right Start → Practice Techniques → How to integrate stand-alone BI environments- Gradual Approach → Principles & Rules → Business owned applications are a reality- Manage it → Principles & Rules → New Data Standards- What about existing data and applications? → Principles & Rules → Handle Each Time-stamp in the Fact Table as a separate dimension → Principles & Rules → Keep Aggregates and Details data in different Fact tables → Principles & Rules → Some considerations for Infrastructure in Data Warehouse → Principles & Rules → For Core BI platform go for a single, established and robust player → Principles & Rules → Don't be guided only by the business requirements for your Business Intelligence → Practice Techniques → Using Synonyms and Views → 
 
Back
 
Relevant links to this page
Add extra buffer for ETL phase
Homework before interviews is must (Business Requirements Phase in Data Warehouse)
Excel is the competition, which should be challenged
Avoid Pure MOLAP
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Consolidate Data-Marts
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts
Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards
Field Tips Series- Streamlining & reducing cost of Business Intelligence- Evaluate Open Source
Master Data Management- Making a Right Start
How to integrate stand-alone BI environments- Gradual Approach
Business owned applications are a reality- Manage it
New Data Standards- What about existing data and applications?
Handle Each Time-stamp in the Fact Table as a separate dimension
Keep Aggregates and Details data in different Fact tables
Some considerations for Infrastructure in Data Warehouse
For Core BI platform go for a single, established and robust player
Don't be guided only by the business requirements for your Business Intelligence
Using Synonyms and Views
Additional Channels
Principles & Rules
Free Templates
Glossary
Key Performance Indicators

Most Popular Zones with list of pages crossing 25000 hits  →→→ 
Maximising Sales Performance
Sales Leads Generation through Events
Sales Objectives Clarity
Sales Synergies
Sales product Mix Profitability
Sales Leads Generation through Point of Sale
Read more...
  Customer Relationship Management
Supply Chain for Customer Service and Support
Customer Satisfaction & Retention- Data Management
Exit barriers for Customer Retention
Customer Satisfaction and Retention- Overview
Customer Segmentation approach
Read more...
  Human Resources & Leadership
Deliver Results
Fostering Innovation
Lead diverse and collaborative teams
Feedback does not mean only negative feedback
Act with Decisiveness
Read more...
 
 
Business Performance & Planning
Creating Strategy Blueprint
Strategic Planning leadership commitment
Business Objectives Drill Down
Strategy Blueprint Information Gathering
SWOT Analysis in Strategic blueprint Planning
Read more...
  Business Intelligence & Data Quality
Data Quality Gaps Root Cause Analysis
Don't fix before root cause Analysis
Business Intelligence Project Management Success Metrics
Sponsor for a Data Quality Program
What is MDM-CDI?
Read more...
  IT Vendors & Tools Management
Design & Analysis support and Wizards
Collaboration and Administration Support
OLAP Server Reliability
Vendor Delivery Support Model
OLAP Server write backs
Read more...