What is MDM? – and the Adjacent Disciplines?

This site is list of solutions for MDM and the disciplines adjacent to MDM. As always, it is good to have a definition of what we are talking about. So, here are some definitions of MDM and an Introduction to 9 adjacent disciplines:

Def MDM

MDM: Master Data Management can be defined as a comprehensive method of enabling an enterprise to link all of its critical data to a common point of reference. When properly done, MDM improves data quality, while streamlining data sharing across personnel and departments. In addition, MDM can facilitate computing in multiple system architectures, platforms and applications. You can find the source of this definition and 3 other – somewhat similar – definitions in the post 4 MDM Definitions: Which One is the Best?

The most addressed master data domains are parties encompassing customer, supplier and employee roles, things as products and assets as well as location.

Def PIM

PIM: Product Information Management is a discipline that overlaps MDM. In PIM you focus on product master data and a long tail of specific product information – often called attributes – that is needed for a given classification of products.

Furthermore, PIM deals with how products are related as for example accessories, replacements and spare parts as well as the cross-sell and up-sell opportunities there are between products.

PIM also handles how products have digital assets attached.

This data is used in omni-channel scenarios to ensure that the products you sell are presented with consistent, complete and accurate data. Learn more in the post Five Product Information Management Core Aspects.

Def DAM

DAM: Digital Asset Management is about handling extended features of digital assets often related to master data and especially product information. The digital assets can be photos of people and places, product images, line drawings, certificates, brochures, videos and much more.

Within DAM you are able to apply tags to digital assets, you can convert between the various file formats and you can keep track of the different format variants – like sizes – of a digital asset.

You can learn more about how these first 3 mentioned TLAs are connected in the post How MDM, PIM and DAM Stick Together.

Def DQM

DQM: Data Quality Management is dealing with assessing and improving the quality of data in order to make your business more competitive. It is about making data fit for the intended (multiple) purpose(s) of use which most often is best to achieved by real-world alignment. It is about people, processes and technology. When it comes to technology there are different implementations as told in the post DQM Tools In and Around MDM Tools.

The most used technologies in data quality management are data profiling, that measures what the data stored looks like, and data matching, that links data records that do not have the same values, but describes the same real world entity.

Def RDM

RDM: Reference Data Management encompass those typically smaller lists of data records that are referenced by master data and transaction data. These lists do not change often. They tend to be externally defined but can also be internally defined within each organization.

Examples of reference data are hierarchies of location references as countries, states/provinces and postal codes, different industry code systems and how they map and the many product classification systems to choose from.

Learn more in the post What is Reference Data Management (RDM)?

Def CDI

CDI: Customer Data Integration is considered as the predecessor to MDM, as the first MDMish solutions focused on federating customer master data handled in multiple applications across the IT landscape within an enterprise.

The most addressed sources with customer master data are CRM applications and ERP applications, however most enterprises have several of other applications where customer master data are captured.

You may ask: What Happened to CDI?

Def CDP

CDP: Customer Data Platform is an emerging kind of solution that provides a centralized registry of all data related to parties regarded as (prospective) customers at an enterprise.

In that way CDP goes far beyond customer master data by encompassing traditional transaction data related to customers and the emerging big data sources too.

Right now, we see such solutions coming both from MDM solution vendors and CRM vendors as reported in the post CDP: Is that part of CRM or MDM?

Def ADM

ADM: Application Data Management is about not just master data, but all critical data that is somehow shared between personel and departments. In that sense MDM covers all master within an organization and ADM covers all (critical) data in a given application and the intersection is looking at master data in a given application.

ADM is an emerging term and we still do not have a well-defined market – if there ever will be one – as examined in the post Who are the ADM Solution Providers?

Def PXM

PXM: Product eXperience Management is another emerging term that describes a trend to positioning PIM solutions away from the MDM flavour and more towards digital experience / customer experience themes.

In PXM the focus is on personalization of product information, Search Engine Optimization and exploiting Artificial Intelligence (AI) in those quests.

Read more about it in the post What is PxM?

Def PDS

PDS: Product Data Syndication connects MDM, PIM (and other) solutions at each trading partner with each other within business ecosystems. Product data syndication is often the first wave of encompassing interenterprise data sharing. You can get the details in the post What is Product Data Syndication (PDS)?

An MDM / PIM / DQM Easter Egg

It is high season for painting Easter eggs now.MDM PIM DQM Easter EggThis egg is featuring:

  • Master Data Management (MDM),
  • Product Information Management (PIM) and/or
  • Data Quality Management (DQM)

as well as:

  • Application Data Management (ADM),
  • Customer Data Integration (CDI),
  • Customer Data Platform (CDP),
  • Digital Asset Management (DAM),
  • Product Data Syndication (PDS),
  • Product experience Management (PXM) and
  • Reference Data Management (RDM)

Check out the 10 data management TLAs on this list here.

What ERP Applications Do and Don’t Do

The functionality of Master Data Management (MDM) and Product Information Management (PIM) solutions are in many organizations (yet) being taken care of by ERP applications.

However, there are some serious shortcomings in this approach.

If we look at party master data (customer roles and supplier roles) a classic system landscape can besides the ERP application also have a CRM application and a separate SRM (Supplier Relationship Management / Supplier Onboarding) application. The master data entities covered by these applications are not the same.

ERP do dont party

Party master data

On the sell side the CRM application will typically also hold a crowd of prospective customers that are not (yet) onboarded into the ERP application. In many cases the CRM application will also have records describing indirect customers that will never be in the ERP application. Only the existing direct customers are shared between the CRM and ERP application. Besides that, the ERP application may have accounts receivable records that have never been onboarded through the CRM application.

On the buy side a functionality of an SRM application is to track the onboarding process and thereby be the system of record for prospective suppliers. Only existing suppliers will be shared between the ERP application and the SRM application. Besides that, the ERP application will have accounts payable records that have never been onboarded through the SRM application.

A main reason of being for a Master Data Management (MDM) solution is to provide a shared registry of every real-world party entity now matter in what application they are described and thereby ensuring consistency, uniqueness and other data quality dimensions.

When looking at product data, ERP applications must often be supplemented by other applications in order to handle detailed and specific topics.

ERP do dont product

Product data

Product Lifecycle Management (PLM) applications are becoming popular when enterprise units as R&D, product management and others have to be supported in handling the series of detailed events that takes place from when a new product is thought of for the first time all through that it is retired and even after that in the period where complaints and other events may occur. ERP applications can only properly handle the main status events as when the product is ready for sale for the first time, when sale is blocked and when the last piece is taken away from the inventory.

Product Information Management (PIM) applications are becoming popular when enterprise units as sales and marketing need to provide specific product data that varies between different product groups. Not at least the rise of ecommerce has driven a demand for providing very detailed and specific product information to support self-service selling. ERP applications are not built to cater for this complexity and the surrounding functionality.

The information demand in this scenario does also encompass handling a variety of digital assets going from product images in many angles, line drawings, videos and more. Depending on the range of requirements this may be handled in a PIM application or separately in a DAM (Digital Asset Management) application.

Where there is no PIM and/or PLM solution in place, the fallback solution to cover the requirements not fulfilled by ERP is a bunch of spreadsheets.

The reason of being for multidomain MDM solutions is to cover the full spectrum of party entities, product entities together with other master data domains as locations and assets.

Check out the range of solutions to cover this space on this list.

MDM, PIM, DAM within Data Management

Master Data Management (MDM), Product Information Management (PIM) and Digital Asset Management (DAM) are some interrelated disciplines that again is interrelated with other disciplines in the data management space.

MDM PIM DAM and Data Management

The core disciplines are:

  • MDM has some sub disciplines, most notable:
    • Multidomain MDM which is when the MDM effort encompasses not only a single master data domain as for example customer, supplier, employee (all being party master data) or product master data but all master data domains relevant for a given organization.
    • Multienterprise MDM which is an emerging discipline where the scope of sharing master data goes from doing that within a given organization to embracing the business ecosystem(s) where the organization operates.
  • PIM can be seen as an extension to product master data management which takes care of the product information in marketing and sales scenarios. In addition:
    • PIM has some overlapping acronyms as PCM, PDM, PLM and PxM as discussed in the post Product Something Management.
    • Product Data Syndication is the multienterprise (business ecosystem wide) scenario related to PIM, where product information is shared between trading partners (or between disconnected entities belonging to the same organization).
  • DAM is most commonly related to PIM and the requirement for handling digital assets as images, textual documents, videos and more related to products, but the digital assets can also relate to other master data entities.

Reference Data Management (RDM) is closely related to these disciplines as told in the post RDM: A Small but Important Extension to MDM.

Data Governance can be seen as an overarching discipline for data management and should also go hand in hand with MDM, PIM and DAM. A core result from MDM, PIM and DAM activities is to provide sustainable data quality so that data cleansing and data matching does not have to be done over and again.

MDM and RDM underpins data reporting activities, Test Data Management (TDM) and data security and MDM, PIM and DAM is an essential aspect of data architecture, data modelling and data integration.

If you are considering solutions for MDM, PIM and DAM, our list features some of the best solutions from the most forward-looking vendors on the market. Check it out here.

Master Data Management Definitions: The A-Z of MDM. Part 1

img_A-Z_post1

This guest blog post is written by Justine Aa. Rodian of Stibo Systems. The post is part 1 in a series of 3. Please stay tuned for part 2 and 3.

Master Data Management can seem complicated to understand and talk about. There are so many abbreviations, so much puzzling lingo. This blog post breaks down the most commonly used MDM terms and define them so that even your mum understands. Get your MDM definitions straight in this A-Z of Master Data Management.

A

Analytics. The discovery of meaningful patterns in data. For businesses, data analytics are used to gain insight and thereby optimize processes and business strategies. Master Data Management can support analytics by providing organized master data as the basis of the analysis or link trusted master data to new types of information output from analytics.

Application Data Management (ADM). The management and governance of the application data required to operate a specific business application. ADM performs a similar role to MDM, but on a much smaller scale as it only enables the management of data used by a single application.

Application Programming Interface (API). An integrated part of most software, such as applications and operating systems, that allows one piece of software to interact with other types of software. In Master Data Management, not all functions can necessarily be handled in the software platform itself. For instance, you want to be able to deliver or receive data to or from external systems and applications. By using APIs built into the software, you can do that and thereby expand the functionality of your MDM solution.

Assets. In the MDM lingo, an asset can be understood in slightly different ways. There’s the term “data as an asset,” where asset is defined as something that can be “owned” or “controlled” to produce value. Here we talk about a way of perceiving something as an asset. But, when you hear about asset management and enterprise assets in conjunction with MDM, an asset is a more tangible thing of which the management can be optimized. Assets can be physical (people, buildings, parts, computers) and digital (data, images).

Architecture. An MDM solution is not just something you buy, then start to use. It needs to be fitted into your specific enterprise setup and integrated with the overall enterprise architecture and infrastructure, which is why MDM architecture is required as one of the first steps in an MDM process.

Attributes. In MDM, an attribute is a specification or characteristic that helps define an entity. For instance, a product can have several attributes, such as color, material, size and components. MDM supports the management of product data, including related attribute data.

B

Business Intelligence (BI). Business Intelligence is a type of analytics. It entails strategies and technologies that help organizations understand their operations, customers, financials, product performance and a number of other key business measurements. MDM supports BI efforts by feeding the BI solution with trusted master data.

Big Data. Large or complex data sets that make traditional data processing tools inadequate. Big data is characterized by the three Vs: Volume (a lot of data), Velocity (data created with high speed) and Variety (data comes in many forms and ranges). The purpose of using Big Data technologies is to capture the data and turn it into actionable insights. The information gathered from Big Data analytics can be linked to your master data and thereby provide new levels of insights.

Bill Of Materials (BOM). A list of the parts or components that are required to build a product.

B2B, B2C, B2B2C. Whether you operate as a Business-to-Business company, Business-to-Consumer company or any combination, Master Data Management can be applicable if you deal with large amounts of master data about, for instance, products, customers, assets, locations or employees.

Business rules. Business rules are conditions or actions set up in your MDM solution that allow for the modification of your data. According to your business rules, you can determine how your data is organized, categorized, enriched and managed. Business rules are typically used in workflows.

C

Customer Data Integration (CDI). The process of combining customer information acquired from internal and external sources to generate a consolidated customer view. CDI is often considered a subset of MDM for customer data.

Customer Data Platform (CDP). A marketing system that unifies a company’s customer data from marketing and other channels to optimize the timing and targeting of messages and offers. An MDM platform supports a CDP by linking the CDP data to other master data, such as product and supplier data, maximizing the potential of the data.

Change Management. The preparation and support of individuals, teams and organizations in making organizational change. A necessity in any MDM implementation if you want to maximize the ROI, as it is very much about changing processes and mindsets.

Cleansing. As in data cleansing. The process of identifying, removing and/or correcting inaccurate data records (e.g., by deduplicating data). Data cleansing eliminates the problems of useless data to ensure quality and consistency throughout the enterprise, and is an integral process of any decent Master Data Management process.

Cloud. MDM solutions come in many variations, and a central question of today is whether to host it on-premises or in the cloud (or a mix, called a hybrid). Cloud MDM is slowly on the rise, and many vendors offer the possibility to host in the cloud, but still the majority of companies choose an on-premise solution due to security concerns. With a hosted cloud solution, typically run on Amazon’s Web Services, Microsoft’s Azure or Google Cloud, organizations don’t have to install, configure, maintain and host the hardware and software. It is outsourced to a third party and typically offered as a subscription service.

Communication. Is something you don’t want to forget in the implementation of an MDM solution. It’s important that the whole company is made aware of what MDM is, what value it brings, and what it means for everyone on a daily basis. That’s the only way people will commit to it.

Contextual. As in contextual Master Data Management. Sometimes known under the name situational MDM (ref. Gartner Hype Cycle). It refers to the management of changeable master data as opposed to traditional, more static, master data. As products and services get more complex and personalized, so does the data, making the management of it equally complex. The dynamic and contextual Master Data Management is forecast to be one of the next big hypes in the MDM world.

Learn more here.

Customer Relationship Management (CRM). A system that can help businesses manage business relationships and the data and information associated with them. For smaller businesses a CRM system can be enough to manage the complexity of customer data, but in most cases organizations have several CRM systems used to various degrees and with various purposes. For instance, the sales and marketing organization will often use one system, the financial department another, and perhaps procurement a third. MDM can provide the critical link between these systems. It does not replace CRM systems but supports and optimizes the use of them.

Customer Master Data Management. Also sometimes referred to as MDM of customer data. The aim is to get one single and accurate set of data on each of your business customers—the so-called 360-degree customer view—across systems, locations and more, in order to create the best possible customer experience and optimize processes.

Learn more here.

D

Digital Asset Management (DAM). The business management of digital assets, most often images, videos, digital files and their metadata. Many businesses have a standalone or home-grown DAM solution, inhibiting the efficiency of the data flow and thereby delaying processes, such as on-boarding new products into an e-commerce site. MDM lets you handle your digital assets more efficiently and connects it to other data. DAM can be a prebuilt function in some MDM solutions.

Data. Data is a computing term to describe the characters, symbols, numbers and media that a computer system is storing. Data is unprocessed information.

Deduplication. The process of eliminating redundant data in a data set, by identifying and removing extra copies of the same data, leaving only one high-quality data set to be stored. Data duplicates are a common business problem, causing wasted resources and leading to bad customer experiences. When implementing a Master Data Management solution, thorough deduplication is a crucial part of the process.

Domain. In the MDM world a domain is understood as one of several areas in which your business can benefit from data management, for example within the product data domain, customer data domain, supplier data domain, etc.

Digital Transformation. (or Digital Disruption). Refers to the changes associated with the use of digital technology in all aspects of human society. For businesses, a central aspect of Digital Transformation is the “always-online” consumer, forcing organizations to change their business strategy and thinking in order to deliver excellent customer experiences. Digital Transformation also has major impact on efficiency and workflows (e.g., the so-called Fourth Industrial Revolution driven by automation and data, also known as Industry 4.0). MDM can play a crucial role in driving digital transformations, as the backbone of these are data.

D-U-N-S. Data Universal Numbering System. A D-U-N-S number is a unique nine-digit identifier for each single business entity, provided by Dun & Bradstreet. The system is widely used as a standard business identifier. A decent MDM solution will be able to support the use of D-U-N-S by providing an integration between the two systems.

If you’d like the whole A-Z e-book in a downloadable format, please find it here.

Justine Aagaard Rodian is a marketing specialist at Stibo Systems with a background as a journalist. Five years in the data management industry has armed Justine with unique insights and she is now using her storytelling and digital skills to spread valuable business knowledge about Master Data Management and related topics.