Data Quality vs MDM

Article Index

So where should you start?

Obviously, it depends on your business requirement.

Master Data Management needs Data Quality

To use an analogy. data quality is the horse to the master data management cart. For a while the horse will be able to carry the required load. Eventually, the load may become to much for the horse and a full Master Data Management solution may be required. In this case, the data quality "horse" will continue to provide the pulling power that allows the cart to function.

On the other hand, the expensive cart is fundamentally useless without a functional horse.

This position is summaroised by Aberdeen Research analyst, Nathaniel Rowe. "If you put MDM in place but you're using old, substandard data, you won't see much value from the effort," he said. "You'll have issues with the data if it isn't standardized."

 "If you only have the budget to do data quality, that's more important, but keep looking toward the horizon for the next step,"

Data quality should not jut be a tick box in the MDM stack. Data quality management is a complex problem that is made worse when multiple sources of data are consolidated for MDM.  Data quality should be assessed independetly of MDM to ensure that you have asolution that is appropriate for your needs.

We have delivered a number of MDM projects with varying architectures, depending largely on what could be leveraged within the existing environment.

The common factor in each project was to ensure that the underlying data was able to support the business requirement.

By blending a business and data focus we deliver incremental benefits that justify the exisitng spend and build the business case for additional phases.

Contact us to learn more

Our Privacy Policy

MDM is committed to the protection of personal information.

For our Privacy Policy, click here

Free Joomla! templates by AgeThemes