Master data management

Companies adopt Master data management (MDM) strategies to ensure that a system becomes ‘the system of record' to manage the master data. It is meant to avoid duplication of data as well as to ensure that master data is managed under change control and the change is managed in only one system.
Traditional MDM approach is derived from data warehousing approach where the master data is collected in a central repository with ETL process for each source application. Central repository then manages changes and propagates them to the relevant upstream and downstream applications.
For the Industrial domain, such an approach may not be practical as the ETL logic, data cleansing logic, conflict resolution logic, and central repository design tend to be complex, laborious, and costly to develop and maintain. Furthermore, access control / security logic and change control / workflow engine need to be developed on top of such central repository.

Instead, many Industrial organizations have adopted the following eQube-MI based approach: For each type of critical data, ‘a system of record' is identified (e.g.; for EBOM – a PLM system is selected as the system of record, MBOM – an ERP system is selected as the system of record, Mfg. plan and BOP – a process planning system , etc.). All changes are managed with security rules in that system of record and once changes are ‘released', those changes are propagated to the upstream and downstream systems. No other system is then allowed to change the master data, they are only allowed to consume that data. Thus, achieving the core purpose of MDM and ensuring no copies of copies are created that can be changed in multiple systems. Since no central repository is required, substantial overhead of designing, creating, and maintaining it is eliminated.
Some of the use cases for eQube-MI based MDM solution are:

1)Implementation of a common parts library

2)Propagation of EBOM to Planning system and ERP system

3)Vendor part management


 Learn More