Master data management has become remarkably trendy now, with software vendors lining up to re-badge their offerings as relating to master data in some way. Some of these offerings run best on the overhead projector, and it is relatively hard to find customers who have actually finished an MDM project and been live for some time, rather than those have completed pilot projects or are “investigating” the issue (i.e. attending conferences in nice sunny locations)
Irrespective of your technology choice, if you want to look at MDM at the sharp end then you could do worse than read a Ventana report which documents several KALIDO MDM customer case studies bsed on in-depth interviews of these customers by Ventana analysts. The case studies show a number if important points whatever technology you are using e.g. the sheer breadth of master data that is out there just waiting to be managed. One bank implemented an MDM system to manage the various versions of statutory accounts that are submitted by its numerous subsidiaries, and which have to be carefully consolidated from a compliance viewpoint. As you can imagine, there is a lot of complexity in the master data associated with a chart of accounts for a massive international bank. This is a long way from the customer hub stereotype that many peopel have of MDM projects.
Another customer manages 350 different types of master data, showing that “customer” and “product” are just a small part of the problem. An issue discussed in the report is the need to set the MDM project in the context of a data governance initiative, for example defining roles for data “customers”, “administrators” and “stewards”, each of whom have different responsibilities. Any MDM project will have to address the organizational issues and roles of this type, and the issues encountered will be similar, even if the Kalido-specific elements of the report is not of interest to you.