Consolidation & Coexistence MDM Configuration

The system setup of the Consolidated and Coexistence styles is rather similar. Hence, only a single configuration file is required for either implementation style. The primary difference between the two styles is with regards to data synchronization.

For more information on the various implementation styles, refer to the MDM Solution Overview topic.

Data synchronization requirements must be carefully vetted during the analysis phase of an implementation.

Data Model

Individual Customer

For B2C implementations, the Accelerator files provide attributes, references, a match algorithm, a find similar algorithm, and a clerical review workflow for Individual Customer entity type.

Household

The Household entity type is relevant to the Individual Customer use case for B2C implementations. The Accelerator files provide a match algorithm and clerical review workflow for Household.

Workflows

Clerical review workflows for each entity type are provided:

  • Individual Customer Clerical Review
  • Organization Customer Clerical Review
  • Contact Person Clerical Review
  • Household Clerical Review
  • Supplier Clerical Review

Clerical review workflows provide the data steward with an interface to view and resolve potential duplicate findings by the respective algorithms of each entity type.

For more information on configuring Match Algorithms and Clerical Review Workflows, refer to the Matching, Linking, and Merging topic in the Matching, Linking, and Merging documentation.

User Privileges

The Consolidated and Coexistence configurations provide a generic user group for Data Stewards. No special privileges are configured for this group and all users have system super user privileges.

Event processor

A preconfigured match event processor collects events for Individual Customer, Organization Customer, Supplier, Contact Person, and Household entities to evaluate their respective match algorithms.

Web UI

A Data Steward Web UI configuration is provided for the purpose of meeting the operational needs of the data steward persona. The Web UI affords the data steward the ability to carry out their daily tasks such as clerical review remediation, ad hoc stewardship responsibilities, maintaining internal hierarchies, monitoring data governance, and running data profiles.

For more information on configuring a Web UI, refer to the Creating a New Web UI topic in the Web User Interfaces documentation. For more information on Data Stewardship, refer to the Data Stewardship topic in the Solution Enablement: Customer & Supplier MDM documentation.

Inbound Integration Endpoint

An inbound integration endpoint (IIEP) is provided and used in conjunction with the Match and Merge Importer. For more information, refer to the Inbound Integration Endpoints topic and the IIEP - Configure Match and Merge Importer Processing Engine topic in the Data Exchange documentation.

Although the Coexistence style MDM dictates that master data is synchronized to upstream and downstream systems, no outbound integration endpoint configuration is provided due to such requirements being specific to each solution implementation. For more information on STEP's capabilities, refer to the Outbound Integration Endpoints topic in the Data Exchange documentation.

Component Models

The following component models are included in the Consolidated and Coexistence Configuration file.

  • Matching:

    • Individual Customer

    • Household

    • Organization Customer

    • Contact Person

    • Supplier

  • Matching – Merge Golden Record:

    • Individual Customer

    • Organization Customer

    • Contact Person

    • Supplier

  • Matching – Link Golden Record:

    • Household

For more information, refer to the Component Models topic in the System Setup documentation.

Workflows

Clerical review workflows allow Data Stewards to adjudicate potential duplicate customer and/or supplier records. The clerical review task list in the Web UI displays all potential duplicate groupings. Users are then able to visually compare the groupings and make an informed decision to merge or reject the groupings.

Further tools provided in the clerical review screen to aid the Data Steward's decision making include the Golden Record Advanced Merge Dialog and the machine learning match recommendations. For more information, refer to the Golden Record Advanced Merge Dialog topic and the Machine Learning Match Recommendations topic in the Matching, Linking, and Merging documentation.

The accelerator files provide the following dedicated clerical review workflows for each entity type:

    • Organization Customer Clerical Review workflow

    • Contact Clerical Review workflow

    • Household Clerical Review workflow

    • Supplier Clerical Review workflow

    • Individual Customer Clerical Review workflow