Various approaches coexist to address the complexities associated with managing customer information across diverse systems.

One such approach involves the consolidation of data from transactional masters, creating a unified customer view within the customer master. However, the challenge lies in the periodic synchronization and post hoc updates, resulting in potential inconsistencies among the master data from different systems. Conflicts are not uncommon, and the decentralized authoring across systems makes it challenging to establish a definitive authority for the customer master.

Another strategy is the implementation of a registry-based master data management approach, where a central index serves as a linkage to master data concepts. In this model, master records are authored in satellite systems, with the registry providing a skeletal structure holding essential attributes shared across systems. Although the registry facilitates interrogation and reference, its limitations stem from the loose control over the customer master due to its fragmented definition.

Two additional paradigms, namely the consolidated and centralized approaches, offer distinct advantages. The consolidated method, often employed for business intelligence and data warehousing initiatives, operates downstream from the original data creation, creating a self-contained customer master. On the other hand, the centralized MDM hub serves as both a system of reference and entry, allowing comprehensive control over data updates, schema definitions, and permission-based access.

The technological landscape is littered with choices, some vendors support all or just some of these a[[rpaches. Their products and the needs of the market continue to evolve, and exploration through a free trial of innovative solutions like the Pretectum CMDM may open one’s eyes to a myriad of alternative hybridized approaches. A Pretectum trial offers an opportunity to experience firsthand the capabilities and benefits of advanced customer master data management.

Coexistence

Data from transactional masters are consolidated into a single customer view of the customer master.

This is typically updated posthoc and periodically synchronized reflecting all the external keys.

The content of the master from various systems may be inconsistent and more importantly, no single entry is necessarily considered to be more correct and appropriate than any other.

Conflicts between records can and do occur and because the authoring is undertaken in different systems, the end result may only be useful for generalized reference and may not be considered a true or absolute authority.

Registry

A registry master data management approach is employed as a central index linkage to the concept of master data.

Master records are authored across the different systems, but with a linkage that is commonly referenced by the different systems as an external key.

Authoring remains in the satellite systems and at best, the registry serves as a skeleton that contains essential attributes of the master that are common across the systems.

Often the data is simply used for interrogation, lookup, or reference. Because you are working with a skeleton of definition, there is relatively loose control over the customer master because this point of reference only provides a sliver of definition to the customer master.

External keys become useful if held.

Consolidated

Used primarily to support business intelligence (BI) or data warehousing initiatives, this is generally referred to as a downstream MDM style, in that MDM is applied downstream of the operating systems where master data is originally created.

The MDM Hub is the system of reference for all reporting, search and reference purposes and it likely stores all the master data needed with no need to connect to, or be connected with backend systems.

This consolidated customer master can operate in a complete vacuum because it is self-contained, simply taking feeds from the satellite systems – beneficiary applications beyond the CMDM enjoy the benefits of the collated records while sources maintain business as usual. The Pretectum CMDM can be used in this way.

Centralized

The Customer MDM hub is both a system of reference and a system of entry – it can update and receive all necessary data updates from any and all backend systems

From within the centralized MDM, you have access to schema master data definitions, including data domains for reference and lookups, and then whatever subordinate datasets that make full or partial use of those definitions.

You also have the ability to have derivatives of existing data and permission-based access. Forms are available for manual data curation and bulk replacement and appends are also possible.