I wrote, “The Perils and Pitfalls of Managing Master Data “inside” ERP Systems” April 24th. Unfortunately I did not get to see the comment, or get to replay, until after our self enforced time limit for comments expired. So I apologize for getting so long to back to this topic and comments.
Here is my response to Sowmindra.
Thanks for leaving a comment.
You ask a good question. We tend to call the set of questions related to “where the master data resides” as “implementation styles” type questions. That is, the degree to which the data is instantiated. We have seen a wide array of requirements that favor a centralized approach (push out), a registry approach (point to), as well as a consolidated approach (collect and harmonize). All three styles have, to varying degrees, worked for operational/transactional MDM situations. There are also some industry specific “favorites” such as registry for patient data in healthcare. So there does not seem to be one answer to your question. We distilled the more notable characteristics that end user organizations consider in this discussion in a note we updated in 2011: The Important Characteristics of the MDM Implementation Style – Update. My colleague, Lyn Robison, also tackled the same question and drilled down on the decision drivers in more detail with A Comparison of Master Data Management Implementation Styles in October 2012.
IBM’s book, Enterprise Master Data Management (2008), is a pretty good resources for some of this dialog, but even it has a few gaps and the models in the book do not align quite with ours (which makes using the rest of the research harder than it needs to be). Most other so-called MDM books really don’t cover all the basis at all; mostly because the authors only have limited exposure or experience with one type of master data (i.e. Customer), or one industry (i.e. banking). One needs a wide array of experiences to spot the real patterns in this topic.
Again, sorry for lateness.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.