10 Data Management TLAs You Should Know

TLA stands for Three Letter Acronym. The world is full of TLAs. The IT world is full of TLAs. The Data Management world is full of TLAs. Here are 10 TLAs from the data management world that have been mentioned a lot of times on this blog and the sister blog over at The Disruptive MDM / PIM / DQM List:

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?

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 related to each given classification of products. 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.

DAM = Digital Asset Management is about handling rich media files often related to master data and especially product information. The digital assets can be photos of people and places, product images, line drawings, brochures, videos and much more. You can learn more about how these first 3 mentioned TLAs are connected in the post How MDM, PIM and DAM Stick Together.

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.

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. Learn more in the post What is Reference Data Management (RDM)?

10 TLA show

CDI = Customer Data Integration, which is considered as the predecessor to MDM, as the first MDMish solutions focussed on federating customer master data handled in multiple applications across the IT landscape within an enterprise. You may ask: What Happened to CDI?

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. 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?

ADM = Application Data Management, which is about not just master data, but all critical data however limited to a single (suite of) application(s) at the time. ADM is an emerging term and we still do not have a well-defined market as examined in the post Who are the ADM Solution Providers?

PXM = Product eXperience Management is another emerging term that describes a trend to distance some PIM solutions from the MDM flavour and more towards digital experience / customer experience themes. Read more about it in the post What is PxM?

PDS = Product Data Syndication, which connects MDM, PIM (and other) solutions at each trading partner with each other within business ecosystems. As this is an area where we can expect future growth along with the digital transformation theme, you can get the details in the post What is Product Data Syndication (PDS)?

Who is on The Disruptive MDM / PIM List?

The Disruptive Master Data Management Solutions List is a sister site to this blog. This site is aimed to be a list of available:

  • Master Data Management (MDM) solutions
  • Customer Data Integration (CDI) solutions
  • Product Information Management (PIM) solutions
  • Digital Asset Management (DAM) solutions.

You can use this site as an alternative to the likes of Gartner, Forrester, MDM Institute and others when selecting a MDM / CDI / PIM / DAM solution, not at least because this site will include both larger and smaller disruptive MDM solutions.

Vendors can register their solutions here and the crowd, being processional users, can review the solutions.

So far these solutions have been listed:

Reltio thumb

Reltio provides all the benefits of cloud like simplicity, scale, and security. On top of that, Reltio breaks down data silos by providing a unified data set with personalized views of data across departments like sales, marketing and compliance. Learn more about Reltio Cloud here.

thumbnailRiversand is an innovative global pioneer in information management. The powerful MDM, PIM and DAM solution help enterprises to transform their raw data into an engine of growth by making data usable, useful and meaningful. Learn more about Riversand here.

Semarchy IconSemarchy xDM is a platform that enables Intelligent MDM and Collaborative Data Governance. It leverages smart algorithms, an agile design, and scales to meet enterprise complexity with solid ROI. Learn more about Semarchy xDM here.

Contentserv thumbContentserv offers a real-time Product Experience Platform being recognized and recommended by international analysts as one of the top worldwide innovators and strong performers in the PIM & MDM space. Learn more about Contentserv here.

ewEnterWorks, which recently was joint with Winshuttle is a multi-domain master data solution for acquiring, managing and transforming a company’s multi-domain master data into persuasive and personalized content for marketing, sales, digital commerce and new market opportunities. Learn about Enterworks here.

SyncForce-plus-icon

SyncForce helps international consumer & professional packaged goods manufacturers realize Epic Availability. With SyncForce, your product portfolio is digitally available with a click of a button, in every shape and form, both internal and external. Learn about SyncForce here.

Dynamicweb thumb

Dynamicweb PIM brings you fewer applications, integrations and systems. It is fast and inexpensive to implement and maintain, because it is part of an all-in-one platform for omni-channel commerce. Learn more about Dynamicweb PIM here.

Agility thumbAgility® empowers marketers to acquire, enrich and deliver accurate and timely product content through every touchpoint, channel and region along with the analytical support required to maximize effectiveness in the market. Learn more about Agility here.

Magnitude thumbMagnitude Software’s Master Data Management solution offers enterprises the core capabilities to model multiple data entities, harmonize the data sources and manage governance processes for reference data and master data. Learn more about Magnitude MDM here.

AllsightAllSight, which is now a part of Informatica, is using state-of-the-art AI-driven technology in an MDM and Customer 360 solution. AllSight matches and links all customer data and provides multiple views of the customer for different users.

Smallest

Product Data Lake, which is affiliated to this blog, is a cloud service for sharing product master data in the business ecosystems of manufacturers, distributors, merchants, marketplaces and large end users of product information. Learn more about Product Data Lake here.

Disruptive MDM M and A

 

The Three MDM Ages

Master Data Management (MDM) is relatively new discipline. The future will prove what is was, but standing here in mid-2018 I see that we already had 2 ages and are now slowly proceeding into a 3rd age. These ages can be coined as:

  • Pre MDM,
  • Middle MDM and
  • High MDM

Pre MDM

In these dark ages the term Master Data Management may have been used, but there were not any established discipline, methodologies, frameworks and technology solutions around that truly could count as MDM.

We had Customer Data Integration (CDI) around, we had Product Information Management (PIM) in the making and some of us were talking Data Quality Management – and that in practice being namely deduplication / data matching.

Middle MDM

MDM as Three Letter Acronym (TLA) emerged in the mid 00’s as told in the post Happy 10 Years Birthday MDM Solutions.

It was at that time Aaron Zornes changed his stage name from The Customer Data Integration Institute to The MDM Institute.

During this age many MDM solutions slowly but steadily have developed into multi-domain MDM solutions as reported over at the Disruptive MDM List in the blog post called 4 Vendor Paths to Multidomain MDM covering the road travelled by 10 vendors on the MDM market.

Most MDM solutions in the Middle MDM Age have been deployed on-premise

High MDM

We are now cruising into the High MDM Age. First and foremost a lot more organizations are now implementing MDM. Many new deployments are cloud based. New ways are tried out like encompassing more than master data in the same platform.

The jury is of course still out about what will be some main trends of the High MDM Age. My money is placed on what Gartner, the analyst firm, calls Multienterprise MDM as elaborated in the post Ecosystem Wide MDM.

MDM Ages.png

How MDM Solutions are Changing

When Gartner, the analyst firm, today evaluates MDM solutions they measure their strengths within these use cases:

  • MDM of B2C Customer Data, which is about handling master data related to individuals within households acting as buyers (and users) of the products offered by an organisation
  • MDM of B2B Customer Data, which is about handling master data related to other organizations acting as buyers (and users) of the products offered by an organisation.
  • MDM of Buy-Side Product Data, which is about handling product master data as they are received from other organisations.
  • MDM of Sell-Side Product Data, which is about handling product master data as they are provided to other organisations and individuals.
  • Multidomain MDM, where all the above master data are handled in conjunction with other party roles than customer (eg supplier) and further core objects as locations, assets and more.
  • Multivector MDM, where Gartner adds industries, scenarios, structures and styles to the lingo.

QuadrantThe core party and product picture could look like examined in the post An Alternative Multi-Domain MDM Quadrant. Compared to the Gartner Magic Quadrant lingo (and the underlying critical capabilities) this picture is different because:

  • The distinction between B2B and B2C in customer MDM is diminishing and does not today make any significant differentiation between the solutions on the market.
  • Handling customer as one of several party roles will be the norm as told in the post Gravitational Waves in the MDM World.
  • We need (at least) one good MDMish solution to connect the buy-sides and the sell-sides in business ecosystems as pondered in the post Gravitational Collapse in the PIM Space.

Building a MDM Solution Using Best-in-Class Modules

Sometimes keeping it simple is the shortcut to getting it all wrong. While I am a believer in mastering all master data domains under the same vision and strategy, there are still best-in-class options when it comes to orchestrating processes and applying technology in the right chunks.

Customer Data Integration (CDI)

A recent post on this blog was called What Happened to CDI? This post examines the two overlapping disciplines Master Data Management (MDM) and Customer Data Integration (CDI). In a comment Jeff Jones argues that MDM vendors have forgotten about proper CDI workflows. Jeff says: “It seems the industry wants to go from Source to Match/Merge, instead of Source to Match/Identify and finally to Merge.” Please find and jump into the discussion here.

Also, this question was touched some years ago in the post The Place for Data Matching in and around MDM.

Product Information Management (PIM)

The product domain within Multi-Domain MDM also holds some risks of forgetting the proper ways of handling product information. In this domain we must also avoid being blinded by the promise of a single source of master data with surrounding processes and applied technology.

There are many end-to-ends to cover properly as exemplified in the post A Different End-to-End Solution for Product Information Management (PIM).

 

Master Data or

What Happened to CDI?

CDI is a Three Letter Acronym which in the data management world stands for Customer Data Integration.

Today CDI is usually wrapped into Master Data Management (MDM) as examined in the post CDI, PIM, MDM and Beyond. As mentioned in this post, a well-known analyst, Aaron Zornes, runs a business called the MDM Institute, which was originally called the The Customer Data Integration Institute and still has this website: http://www.tcdii.com/.

Many Master Data Management (MDM) vendors today emphasizes on being multidomain, meaning their solutions can manage customer, supplier employee and other party master data as well as product, asset, location and other core business entity types.

However, some vendors still focus on customer master data and the topic of integrating customer data by excelling in the special pain points here, not at least identity resolution and sustainable merge/purge of duplicates. One example is Uniserv Smart Customer MDM.

In my recent little venture called The Disruptive Master Data Management Solution List the aim is to cover all kinds of MDM solutions: Small or big. New (start-up) or old. Multidomain MDM, Customer Data Integration (CDI), Product Information Management (PIM) or even Digital Asset Management (DAM). As a potential buyer, you can browse all these solutions and select your choice of one-stop-shopping candidates or combine best-of-breed solution candidates that matches your requirements in your industry and geography.

First thing that must happen is that vendors register their solutions on the site here.

MDM

The Evolution of MDM

Master Data Management (MDM) is a bit more than 10 years old as told in the post from last year called Happy 10 Years Birthday MDM Solutions. MDM has developed from the two disciplines called Customer Data Integration (CDI) and Product Information Management (PIM). For example, the MDM Institute was originally called the The Customer Data Integration Institute and still have this website:http://www.tcdii.com/.

Today Multi-Domain MDM is about managing customer, or rather party, master data together with product master data and other master data domains as visualized in the post A Master Data Mind Map.

You may argue that PIM (Product Information Management) is not the same as Product MDM. This question was examined in the post PIM, Product MDM and Multi-Domain MDM. In my eyes the benefits of keeping PIM as part of Multi-Domain MDM are bigger than the benefits of separating PIM and MDM. It is about expanding MDM across the sell-side and the buy-side of the business eventually by enabling wide use of customer self-service and supplier self-service.

MDM

The external self-service theme will in my eyes be at the centre of where MDM is going in the future. In going down that path there will be consequences for how we see data governance as discussed in the post Data Governance in the Self-Service Age. Another aspect of how MDM is going to be seen from the outside and in is the increased use of third party reference data and the link between big data and MDM as touched in the post Adding 180 Degrees to MDM.

Besides Multi-Domain MDM and the links between MDM and big data a much mentioned future trend in MDM is doing MDM in the cloud. The latter is in my eyes a natural consequence of the external self-service themes and increased use of third party reference data.

If you happen to be around Copenhagen in the late January I can offer you the full story at a late afternoon event taking place in the trendy meatpacking district and arranged by the local IT frontrunner company ChangeGroup. The event is called Master Data Management: Before, now and in the future.

MDM and SCM: Inside and outside the corporate walls

QuadrantIn my journey through the Master Data Management (MDM) landscape, I am currently working from a Supply Chain Management (SCM) perspective. SCM is very exciting as it connects the buy-side and the sell-side of a company. In that connection we will be able to understand some basic features of multi-domain MDM as touched in a recent post about the MDM ancestors called Customer Data Integration (CDI) and Product Information Management (PIM). The post is called CDI, PIM, MDM and Beyond.

MDM and SCM 1.0: Inside the corporate walls

Traditional Supply Chain Management deals with what goes on from when a product is received from a supplier, or vendor if you like, to it ends up at the customer.

In the distribution and retail world, the product physically usually stays the same, but from a data management perspective we struggle with having buying views and selling views on the data.

In the manufacturing world, we sees the products we are going to sell transforming from raw materials over semi-finished products to finished goods. One challenge here is when companies grow through acquisitions, then a given real world product might be seen as a raw material in one plant but a finished good in another plant.

Regardless of the position of our company in the ecosystem, we also have to deal with the buy side of products as machinery, spare parts, supplies and other goods, which stays in the company.

MDM and SCM 2.0: Outside the corporate walls

SCM 2.0 is often used to describe handling the extended supply chain that is a reality for many businesses today due to business process outsourcing and other ways of collaboration within ecosystems of manufacturers, distributors, retailers, end users and service providers.

From a master data management perspective the ways of handling supplier/vendor master data and customer master data here melts into handling business-partner master data or simply party master data.

For product master data there are huge opportunities in sharing most of these master data within the ecosystems. Usually you will do that in the cloud.

In such environments, we have to rethink our approach to data / information governance. This challenge was, with set out in cloud computing, examined by Andrew White of Gartner (the analyst firm) in a blog post called “Thoughts on The Gathering Storm: Information Governance in the Cloud”.

CDI, PIM, MDM and Beyond

The TLAs (Three Letter Acronyms) in the title of this blog post stands for:

  • Customer Data Integration
  • Product Information Management
  • Master Data Management

CDI and PIM are commonly seen as predecessors to MDM. For example, the MDM Institute was originally called the The Customer Data Integration Institute and still have this website: http://www.tcdii.com/.

Today Multi-Domain MDM is about managing customer, or rather party, master data together with product master data and other master data domains as visualized in the post A Master Data Mind Map. Some of the most frequent other master domains are location master data and asset master data, where the latter one was explored in the post Where is the Asset? A less frequent master data domain is The Calendar MDM Domain.

QuadrantYou may argue that PIM (Product Information Management) is not the same as Product MDM. This question was examined in the post PIM, Product MDM and Multi-Domain MDM. In my eyes the benefits of keeping PIM as part of Multi-Domain MDM are bigger than the benefits of separating PIM and MDM. It is about expanding MDM across the sell-side and the buy-side of the business eventually by enabling wide use of customer self-service and supplier self-service.

The external self-service theme will in my eyes be at the centre of where MDM is going in the future. In going down that path there will be consequences for how we see data governance as discussed in the post Data Governance in the Self-Service Age. Another aspect of how MDM is going to be seen from the outside and in is the increased use of third party reference data and the link between big data and MDM as touched in the post Adding 180 Degrees to MDM.

Besides Multi-Domain MDM and the links between MDM and big data a much mentioned future trend in MDM is doing MDM in the cloud. The latter is in my eyes a natural consequence of the external self-service themes and increased use of third party reference data which all together with the general benefits of the SaaS (Software as a Service) and DaaS (Data as a Service) concepts will make MDM morph into something like MDaaS (Master Data as a Service) – an at least nearly ten year old idea by the way, as seen in this BeyeNetwork article by Dan E Linstedt.

Bookmark and Share

An Alternative Multi-Domain MDM Quadrant

No, this is not an(other) attempt to challenge Gartner, the analyst firm, in making quadrants about vendors in the Master Data Management (MDM) realm.

This an attempt to highlight some capabilities of Multi-Domain MDM solutions here focusing on party and product master data and the sell-side and the buy-side of MDM as discussed some years ago in the post Sell-side vs Buy-side Master Data Quality.

A simple quadrant will look like this:

Quadrant

  • The upper right corner is where MDM started, being with solutions back then called Customer Data Integration (CDI).
  • The Product Information Management (PIM) side is quite diverse and depending on the industry vertical where implemented:
    • Retailers and distributors have their challenges with sometimes high numbers of products that goes in and comes out as the same but with data reflecting different viewing points.
    • Manufacturers have other issues managing raw materials, semi-finished products, finish products and products and services used to facilitate the processes.
    • Everyone have supplies.
  • The supplier master data management has more or less also been part of the PIM space but looks more like customer master data and should be part of a party master data discipline also embracing other party roles as employee.

Also, this quadrant is by the way without other important domains as location (as discussed in the post Bringing the Location to Multi-Domain MDM) and asset (as discussed in the post Where is the Asset?)

Bookmark and Share