data governance hub

Bring Flexibility Back to Your MDM Deployment
Simplify the role of the MDM Hub and provide additional capabilities without compromising performance or system availability.



Data Governance Hub


Over the past decade, Master Data Management (MDM) technology has evolved from its experimental beginnings into a formal component of enterprise architecture. Whereas early MDM deployments played a supporting role to BI or CRM, more mature MDM deployments have become mission-critical operational systems in their own right.

The integrated role of MDM restricts the ability to extend the system because the downstream impacts are so complex. Mature MDM customers are finding that common MDM applications such as adding external marketing databases or adding data validation rules have become too expensive or too risky to deploy into the operational environment. Furthermore, as companies extend the concepts of data governance they find that the processing overhead of data validations and workflows creates performance issues with the overall MDM processing.

Gaine clients have solved this issue by recognizing the differences between an Operational MDM Hub (Op-Hub) and a Data Governance Hub (DG-Hub). The introduction of a DG-Hub enables clients to recapture the flexibility that has been sacrificed in many MDM deployments.


The DG-Hub is typically loosely coupled to other enterprise applications through a pub / sub architecture. Typically the operational MDM hub will not contain all of the data required for data governance processing and it is common that the DG-Hub will require additional source information to apply a broader scope of data validations.

The DG-Hub is able to apply extensive validations and policy checks on the master data because it operates as a background process and no downstream systems are reliant upon a real-time response or subscription file from the DG-Hub. Outputs from the DG-Hub are data governance workflows and inputs gathered from these workflows. Because the DG-Hub is not providing operation systems with enterprise keys or a golden record, it is more suitable for loading new data files without the same concerns for performance impacts or changes to the master files.

The flexibility of the DG-Hub is a natural extension of an enterprise MDM strategy. The DG-Hub simplifies the role of the MDM Hub and provides additional capabilities without compromising performance or system availability.

data governance hub DG-hub


Key Features

Compare DG-Hub and Op-Hub

DG-Hub MDM Operational Hub Benefits of the DG-Hub

Contains very rich source data with more attribution than a typical MDM Hub.

Contains a limited set of “enterprise” attributes.

Allows more extensive and complex validations on the master data.

Extensive workflows for multiple data governance processes..

Simple workflows for the most common data steward activities such as resolve suspect match or conflicting attribution.

A single record loaded into the DG-Hub may generate multiple independent workflows. As no system is waiting for a response, these workflows can be long-running and inter-dependent.

Manages an organizational structure for the entire data governance organization.

Manages only the data steward roles and data access roles.

Data governance involves multiple stakeholders not just data stewards and councils. The DG-Hub allows the extended organization to be modeled and used in workflow processing.

Manages data policy and specifications.

Manages rules for the MDM attributes under management.

Data policies typically extend beyond the attributes within an MDM Hub. The DG Hub provides an extended data specification repository to manage more extensive data policies.

Provides a central repository to monitor the efficacy of the data governance organization.

Provides a central place to manage the master data content.

Improving master data over time requires that the data governance processes and policies are subject to continuous improvement. The DG-Hub provides a view of these processes and outcomes.

Focus is on integration with the desktop of the business users.

Focus is on integration with enterprise systems architecture.

DG stakeholders span the entire organization and may have a role to play in the management of this enterprise data. A familiar desktop experience is critical to successful data governance adoption.



A Data Governance Hub provides a new level of flexibility to a mature MDM deployment. The DG Hub relieves many of the major restrictions inherent in an Operational MDM Hub deployment and restores the advantages of a disconnected system without compromising the benefits of MDM to operational processes.

A Data Governance Hub is simpler to deploy and support because it isolates validations and workflows from operational processes.

New data can be loaded into the DG Hub without concerns for impacting the operational environment.
Manage data policy and specifications for a broader scope of master data.
Manage a data governance organizational structure for use in workflow processing.
Provides a central repository of data governance processes and user interactions.