Establishing 'Making it Happen' as a 'Formal & Predictable' Discipline

Data Quality Program Initiation	Data Quality Gaps Root Cause Analysis

ENCYCLOPEDIA→ Enterprise Intelligence → - Data Quality → - Data Quality Program →

Data Quality Program DMA

Data Mapping & Assessment includes data quality checks, data profiling, data volumes analysis and information chain analysis. It is a big subject and organized as a separate chapter. Please refer to chapter of Data Mapping & Assessment. This exercise has benefits of establishing quality baseline, build a more fact based business case and generating enough details to do an appropriate root cause analysis. Please refer to SEPARATE CHAPTER on Data Mapping & Assessment. This is because this as a concept is required for many Data Management initiatives (like Data Warehousing, Operational Data Stores etc..) as well. The outcome of this exercise is the Data Mapping & Analysis Report.

This page is going to short as there is a dedicated chapter on Data Mapping and Assessment. Data Mapping & Assessment is a subject, which is used for many applications with in Execution-MiH (BUSINESS INTELLIGENCE AND PERFORMANCE MANAGEMENT). It will be worthwhile to refer to this chapter before further reading.

How DMA is applied on Data Quality program?

Typically the entire Data Mapping & Assessment (DMA) needs to be done for a comprehensive Data Quality Program. However, if one is focusing on a very specific domain, one may limit oneself to a sub-set. DMA typically turns out to be a costly exercise. For projects which implement new business application OR a BI environment, it is easier to build a business case for DMA. This is because the benefits of a business application OR Data Warehouse is more quantifiable and these projects are more attractive to business. For a Data Quality program, one has to tread the path more care-fully.

As you will see in Data Quality Approach Options & Considerations, It is important for a DQ program to be careful in terms of what order list they are raising on DMA. (apart from the times, when all the hell has broken loose and the order to fix Data quality has come 'straight from the top'). That's why it is important for domain experts and business analysts should play an important role in ensuring the priorities.

A DQ program may not be in a position to ask for an across the board DMA. One has to have a high level judgment on the areas where the data quality issues could exist, and create the scope of DMA accordingly. For example- one will ask for DMA for spare-parts ordering flow and not for the entire sourcing process. One may say that without the end-to-end DMA, one will miss out the DQ issues, which are not in our radar. In other words-' what about the things we don't know that we don't know?'. There will be a risk without a comprehensive DMA, but there are realities of multiple priorities fighting for limited monies.

TIP- one way is to use the Data Warehouse OR enterprise IT application initiative to get your DMA done. So if there are any such projects going on, one can work with their owners to synergize with DQ program objectives.

The outcome of this exercise is Data Mapping & Assessment Report

Data Quality Program Initiation

Data Quality Gaps Root Cause Analysis

Relevant Links to this page