Nice article by Marty Moseley of Initiate Systems on Multidomain MDM. The article provides real world examples and explains how multi-domain MDM adds value. I am pleased we are seeing more emphasis on multi-domain by the product vendors (Initiate has been a leader in the CDI space for a while now).
One comment on the following statement from the article:
"All data that flows through an enterprise can be categorized into six different types: who, what, when, where, how and why. Master data is about who, what, when and where. ...."
I would extend the definition of master data to include "how" and maybe "why". And to be clear I am still talking about entity and not transactional data. I view relations (intersections) across MDM domains which define the "how" as master data as well. Here are a few examples:
- Hierarchies, define how like master data relates
- Entitlements, define how customers and products relate
- Pricing, defines how customers, products, and locations relate
I need to chew a little more on the classification of "why" as master data since not many real world examples of such master data does jumps out at me right away. Strategic business planning and metrics come to mind though, where information is very important from the executive and management levels through to the individual contributors, which I would make the case for inclusion as master data as well.
No comments:
Post a Comment