Before we start building model and loading data into MDS, you may have questions: How do you design the model? How to decide which attributes should be included? How other applications talk with MDS? Should entity data in applications be over-written? These design related questions should be answered by picking right MDM hub style for your corporation.
There are three MDM hub styles: Repository or transnational,Registry and hybrid.
Repository requires that master data is maintained in MDM hub only. And all systems should be modified to use the master data from the master data hub repository. This style seems a best option but in real world, It's just impossible for any established companies unless they are startups. but if it's startup, it requires a MDM? This style requires all existing applications to be modified to use the new master data databases. And it also requires a common data model for all applications. In many cases, It's just too difficult or too expensive.
Registry is opposite way. The hub doesn't contain actual master data. It just contains links to where the master data exists in source applications.The links typically are source system IDS and the key data values. The hub does the cleansing and assign unique identifiers to the matched records to remove the duplication. The hub has to provide an attribute locator service to fetch authorized values of each data element from reference systems. Performance can be an issue because we have to make call to various systems and consolidate them together. And because we need to assign unique identifiers to matched records, high quality of matching engine is critical. The benefits are also attractive. First, it avoids political issues about over writing data into source system. And the implementation cost is low.
Hybrid style resembles registry style but store more attributes than just removing duplication. The hybrid one addresses the performance issue.
We will discuss how to implement hybrid style using MDS in next article
Comments
Post a Comment