Business Intelligence Network business intelligence resources

Blog: Colin White

« New CIO Spending Survey | Main | After Acquiring Sunopsis Where Will Oracle Go Next? »

Is a Data Warehouse the Place to Start an MDM Project?

A lot has been written about master data management (MDM) over the last few months on the Business Intelligence Network. Although there are some differences of opinion about how to implement MDM, I think everyone agrees that MDM is associated with both business transaction and BI application processing. Given that many companies have master data managed by both types of application where is the best place to start an MDM project?

In the business transaction processing area most attempts at integrating master data have been based on custom built IT applications. The application package vendors are beginning to offer packaged solutions for MDM, but many of them are focused primarily on integrating master data from their various business transaction application packages. To be successful these packaged MDM solutions must also provide support for master data from legacy and third-party application packages.

The data warehousing area of IT has often done the best job in many companies in understanding, documenting, cleansing and integrating operational data. When discussing MDM and data warehousing, however, it is important to separate operational processing from BI processing. I would argue that using an operational data store or a data hub to consolidate and propagate business transaction data and master data is operational processing, not BI processing. Of course, the integrated master data system of record created by this processing is an ideal data source for BI processing applications and their underling data warehouses and data marts.

Some analysts and vendors are arguing that data from operational data stores, data warehouses and master data stores should be integrated into a single data warehousing environment. To me this is backward thinking and will cause even more operational processing to be brought into the BI environment. We should be looking for ways of reducing the operational work being done in the BI environment, not increasing it.

Master data processing needs to be separated from both the business transaction and BI environments and integrated into a single MDM system. This MDM system should be used to supply data to business transaction and BI applications, not the reverse. It will take time to move such an MDM environment, and meanwhile there are tactical MDM approaches that can leverage existing master data in both business transaction and BI applications. It not be forgotten, however, that in the longer term the objective is to separate and integrate master data into its own environment.

I will discuss this topic in more detail in my October newsletter article on the BI Network.

  Posted by Colin White on September 26, 2006 12:53 PM |

Comments

Colin,

I think the master data flow can start either at a single point of entry for the master data or, more likely, especially in the short-term, at the operational systems where the data is generated. It would flow to operational systems and the DW/BI environment. So, I agree with you - it's PRE data warehouse operations.

As for the perspective of "Are the Data Warehouse architects the PEOPLE to start an MDM Project?" I would say yes.

Colin,

If master data management is done tool/technology that is separate from the DW, my experience has always shown that MDM precedes the DW. But interestingly, there have been some recent developments from data warehousing vendors where the notion of MDM within a DW has been revived. It would be interesting to see how this approach compares with the traditional approach.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)