Skip to main content Skip to complementary content

Best Practices: MDM Modelling

Availability-noteDeprecated
Information noteDeprecation: Talend Master Data Management (MDM) is deprecated and will reach end of life on December 31, 2024. For more information on migrating from Talend MDM, contact Talend Professional Services.

This article defines the best practices to adopt when creating a physical MDM model with Talend.

Overview

This article serves as a guide to the techniques, standards and best practices that should be employed when creating a physical MDM model with Talend.

The following best practices have been compiled from many years of experience in implementing Talend MDM by the Talend Professional Services team. For further assistance, please contact your Talend Account Manager.

This article does not attempt to outline how a given domain (for example, Customer) should be modelled. The physical MDM model design is driven by :

  • An organization-wide consensus of the definition of each master data entity – this is usually not just the model as defined by an individual source system. The driving force for obtaining this consensus should be the data governance group, with representation from all stakeholders (business and IT). The result of this initiative is a set of conceptual and logical models which are used to help design the MDM physical model.
  • Data profiling and analysis.
  • The business processes that the organization requires to be enacted upon the MDM model. This most likely includes business processes that do not exist in the organization before the MDM project. Thus, business process analysis (current and desired) is a critical pre-requisite to the implementation of the right MDM physical model design.

Once the organization is ready to begin creation of an MDM physical model, this guide should be employed to ensure a consistent and robust implementation.

Prerequisites

  • You have completed the Talend MDM Modelling Training class.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!