Recently while doing a demo to one of the customer, one of the question that kept on hovering around most part of the discussion is "I have this attribute. Can I keep it in the Master Data Management Solution". The attributes that were chosen were price of a product, points earned by the customer and so forth.
The price of the product for that customer is something that would change multiple times in a single day and a similar thing could happen with the Point system. This definitely does not contribute to the Master data.
A lot of times it has been observed that customer does not clearly understand what Master Data is and often confuses it with a repository which can hold all their data like a Data Warehouse vis-à-vis a solution which could give them that single view of the customer or any entity. So it is very important to make the customer understand what Master Data is. The attributes that form a part of Master Data should not be highly transactional as then the objective of the MDM is lost.
The price of the product for that customer is something that would change multiple times in a single day and a similar thing could happen with the Point system. This definitely does not contribute to the Master data.
A lot of times it has been observed that customer does not clearly understand what Master Data is and often confuses it with a repository which can hold all their data like a Data Warehouse vis-à-vis a solution which could give them that single view of the customer or any entity. So it is very important to make the customer understand what Master Data is. The attributes that form a part of Master Data should not be highly transactional as then the objective of the MDM is lost.
Looking for views from other MDM Specialists.
