Why do so many people directly link master data management with customer data? Maybe because we have been dealing with customer data so long, that when a new buzz word appears, we immediately try to link what we are doing to the "latest craze" to ensure our mindshare among the stakeholders.
However, the more I think about MDM and product data, the more intrigued I am. I have said this in a number of metings: product names are curious because they often describe what they are. For example, a PHILLIPS SCREWDRIVER 6-3/4" is a phillips screwdriver that is 6 and 3/4 inches long. What is more, product descriptions carry a lot of information that can be relatively easily parsed out using standard text analysis and text mining techniques. So I would very much be interested in hearing more about some product information MDM projects - email me or post your success stories!
Posted January 29, 2008 7:46 AM
Permalink | 1 Comment |
Twitter 
LinkedIn 
YouTube
David,
It's an interesting question why do people link master data management with customer data.
I think you have to take in account that most people who make use of the MDM already have another set references. For example most people, when think of product, think of a commercial product or a end-product. When we introduce MDM to people the productnames already exist which uniquely discribe a product. so why make new ones up?
Your second point is about information included in a productname. I rarely encountered situations where the added information is not also included as information on it's own. So the same information can be found in different entities.
The added information in the productname is rarely used. (at least in my experience)
Maybe you have other experiences. But I prefer not to combine multiple information in one entity. I simply don't see the need.
Guido