In this “summer series” of posts dedicated to Master Data Management for Product Data, we’ve gone across what we identified as the five most frequent use cases of MDM for product data. Now we are looking at the key capabilities that are needed in MDM platform to address each of these use cases. In this post, we address the MDM for lean managed services , which is about creating and orchestrating a standardized and unified infrastructure from a heterogeneous landscape of legacy assets.
This use case is about creating a uniform and actionable view of a network of equipment. It generally starts with a very heterogeneous set of legacy systems. It may even happen that source systems are nothing more than spreadsheets and that the resulting system will replace them rather than coexist with them, requesting strong and rapid to implement data migration capabilities. The data quality component from your MDM solution would then be of great help, not only to assess and profile your data, but also to help you standardize it. After all, your key objective is to drive efficiency while managing your equipment from the uniform and quality proofed view that your MDM provides. This should be an ongoing effort, requesting strong usability capabilities from your data quality component together with reporting and monitoring capabilities.
Once populated, the MDM may become the place where the master data is authored, requesting this capability together with workflow in case of collaborative authoring.
Even more importantly your MDM should become a hub that can remotely triggers actions to the objects that it references. Strong ESB capabilities, including with advanced security, fault tolerance and audit trail management, are then mandated.
Conitinued on part 9.