Avoid Duplicates by Avoiding Peer-to-Peer Integrations

When working in Master Data Management (MDM) programs some of the main pain points always on the list are duplicates. As explained in the post Golden Records in Multi-Domain MDM this may be duplicates in party master data (customer, supplier and other roles) as well as duplicates in product master data, assets, locations and more.

Most of the data quality technology available to solve these problems revolves around identifying duplicates.  This is a very intriguing discipline where I have spent some of my best years. However, this is only a remedy to the symptoms of the problem and not a mean to eliminate the root cause as touched in the post The Good, Better and Best Way of Avoiding Duplicates.

The root causes are plentiful and as all challenges they involve technology, processes and people.

Having an IT landscape with multiple applications where master data are a created, updated and consumed is a basic problem and a remedy to that is the main reason of being for Master Data Management (MDM) solutions. The challenge is to implement MDM technology in a way that the MDM solution will not just become another silo of master data but instead be solution for sharing master data within the enterprise – and ultimately in the digital ecosystem around the enterprise.

blind-spot-take-careThe main enemy from a technology perspective is in my experience peer-to-peer system integration solutions. If you have chosen application X to support a business objective and application Y to support another business objective and you learn that there is an integration solution between X and Y available, this is very bad news. Because short term cost and timing considerations will make that option obvious. But in the long run it will cost you dearly if the master data involved are handled in other applications as well. Because then you will have blind spots all over the place where through duplicates will enter.

The only sustainable solution is to build a master data hub where through master data are integrated and thus shared with all applications inside the enterprise and around the enterprise. This hub must encompass a shared master data model and related metadata.

 

Learn from MDM Vendors

The Disruptive List of Master Data Management Solutions has a blog. On this blog some of the leading MDM vendors provides guest blog posts with their perspective on both emerging trends and good old fundamental prerequisites within the MDM discipline.

Earlier this year David Corrigan of AllSight wrote a thought provoking post about 3 Reasons MDM No Longer Delivers a Customer 360.    

Yesterday Shamanth Shankar of Riversand contributed with a timely post on Why next generation MDM and PIM solutions must be in the Cloud.

Today we have a well-founded post by Nils Erik Pedersen of Stibo Systems on the Five Steps to Guarantee a Successful Master Data Management Implementation.

Learn from MDM Vendors

Good to have Agility Multichannel on the Disruptive MDM / PIM List

The latest entry on The Disruptive List of Master Data Management Solutions is Agility Multichannel, who provides a well proven Product Information Management (PIM) solution for 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.

Recently Agility Multichannel was acquired by Magnitude Software and is thus a part of a broader software offering alongside with the Magnitude MDM solution which was previously known as Kalido.

Agility is close to me as Agility was one of the first forward looking MDM and PIM market players to join as ambassador at Product Data Lake.

You can learn more about the Agility Multichannel solution here.

banner

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

Three Remarkable Observations about Reltio

The latest entry on The Disruptive Master Data Management Solutions List is Reltio. I have been following Reltio for more than 5 years and have had the chance to do some hands on lately.

In doing that, I think there are three observations that makes the Reltio Cloud solution a remarkable MDM offering.

More than Master Data

While the Reltio solution emphasizes on master data the platform can include the data that revolves around master data as well. That means you can bring transactions and big data streams to the platform and apply analytics, machine learning, artificial intelligence and those shiny new things in order to go from a purely analytical world for these disciplines to exploit these data and capabilities in the operational world.

The thinking behind this approach is that you can not get a 360-degree on customer, vendor and other party roles as well as 360-degree on products by only having a snapshot compound description of the entity in question. You also need the raw history, the relationships between entities and access to details for various use cases.

In fact, Reltio provides not just operational MDM, but through a module called Reltio IQ also brings continuously mastered data, correlated transactions into an Apache Spark environment for analytics and Machine Learning. This eliminates the traditional friction of synchronizing data models between MDM and analytical environments. It also allows for aggregated results to be synchronized back into the MDM profiles, by storing them as analytical attributes. These attributes are now available for use in operational context, such as marketing segmentation, sales recommendations, GDPR exposure and more.

Multiple Storing Capabilities

There is an ongoing debate in the MDM community these days about if you should use relational database technology or NoSQL technology or graph technology? Reltio utilizes all three of them for the purposes where each approach makes the most sense.

Reference data are handled as relational data. The entities are kept using a wide column store, which is a technique encompassing scalability known from pure column stores but with some of the structure known from relational databases. Finally, the relationships are handled using graph techniques, which has been a recurring subject on this blog.

Reltio calls this multi-model polyglot persistence, and they embrace the latest technologies from multiple clouds such as AWS and Google Cloud Platform (GCP) under the covers.

Survival of the Fit Enough

One thing that MDM solutions do is making a golden record from different systems of records where the same real-world entity is described in many ways and therefore are considered duplicate records. Identifying those records is hard enough. But then comes the task of merging the conflicting values together, so the most accurate values survive in the golden record.

Reltio does that very elegantly by actually not doing it. Survivorship rules can be set up based on all the needed parameters as recency, provenance and more and you may also allow more than one value to survive as touched in the post about the principle of Survival of the Fit Enough.

In Reltio there is no purge of the immediately not surviving values. The golden record is not stored physically. Instead Reltio keeps one (or even more than one) virtual golden record(s) by letting the original source records stay. Therefore, you can easily rollback or update the single view of the truth.

The Reltio platform allows survivorship rules to be customized in rulesets for an unlimited number of roles and personas. In effect supporting multiple personalized versions of the truth. In an operational MDM context this allows sales, marketing, compliance, and other teams to see the data values that they care about most, while collaborating continuously in what Reltio calls the Self-Learning Enterprise.

Going beyond operational MDM

 

There is no PIM quadrant, but there is a PIM wave

2018-Forrester-PIM-WaveWith the, in my eyes well justified, merge of the two Master Data Management (MDM) quadrants Gartner, the analyst firm, is somehow missing some ranking of specialised Product Information Management (PIM) vendors.

However, Forrester, the other analyst firm, still have their wave with the fresh new Forrester Wave™: Product Information Management Solutions, Q2 2018.

Two of the leaders have already announced their position as you can see here with Enterworks and Contentserv.

If you want to know more about the best PIM solutions on the market, you can also read about Enterworks, Contentserv, Stibo Systems, Riversand and Agility Multichannel on the disruptive list of MDM, PIM and DAM solutions.

 

Achieving Business Benefits from Multi-Domain MDM

Multi-Side MDMThe title of this blog post is also the title of my presentation at a Master Data Management (MDM) event that will take place in Berlin the 18th and 19th October 2018.

Here, I will give my perspectives on:

Read more about this MDM event from ThinkLinkers here. Hope to see you in Berlin.

PS: You can watch a YouTube video with testimonials from a previous event here.

Ecosystem Wide Product Information Management

The concept of doing Master Data Management (MDM) not only enterprise wide but ecosystem wide was examined in the post Ecosystem Wide MDM.

As mentioned, product master data is an obvious domain where business outcomes may occur first when stretching your digital transformation to encompass business ecosystems.

The figure below shows the core delegates in the ecosystem wide Product Information Management (PIM) landscape we support at Product Data Lake:

Ecosystem Wide PIM.png

Your enterprise is in the centre. You may have or need an in-house PIM solution where you manipulate and make product information more competitive as elaborated in the post Using Internal and External Product Information to Win.

At Product Data Lake we collaborate with providers of Artificial Intelligence (AI) capabilities and similar technologies in order to improve data quality and analyse product information.

As shown in the top, there may be a relevant data pool with a consensus structure for your industry available, where you exchange some of product information with trading partners. At Product Data Lake we embrace that scenario with our reservoir concept.

Else, you will need to make partnerships with individual trading partners. At Product Data Lake we make that happen with a win-win approach. This means, that providers can push their product information in a uniform way with the structure and with the taxonomy they have. Receivers can pull the product information in a uniform way with the structure and with the taxonomy they have. This product data syndication concept is outlined in the post Sell more. Reduce costs.

MDM in The Cloud, On-Premise or Both

One of the forms of Master Data Management (MDM) is the rising cloud deployment model as touched in the Disruptive MDM List blog post about 8 Forms of Master Data Management.

If we look at the MDM solution vendors, they may in that sense be divided into three kinds:

  • Cloud only, which are vendors born in the cloud age and who are delivering their service in the cloud only. Reltio is an example of that kind of MDM vendor.
  • Cloud or on-premise, which are vendors that can deliver both in the cloud and on premise, but where it makes most sense that you as a customer chooses the one that fits you the best. An example is Semarchy.
  • Cloud and on-premise. Informatica is the example of an MDM vendor that embraces both deployment models (together with other data management disciplines) at the same time (called hybrid) as told in an article by Kristin Nicole of SiliconANGLE. The title goes like this: Balancing act: Informatica straddles on-prem needs with cloud data at Informatica World 2018

Cloud MDM

Even With 20 Entities MDM Can be Hard

This week I attended the Master Data Management Summit Europe 2018 and Data Governance Conference Europe 2018 in London.

Among the recurring sessions year by year on this conference and the sister conferences around the world will be Aaron Zornes presenting the top MDM Vendors as he (that is the MDM Institute) sees it and the top System Integrators as well.

Managing an ongoing list of such entities can be hard and doing it in PowerPoint does not make the task easier as visualized in two different shots captured via Twitter as seen below around the Top 19 to 22 European MDM / DG System Integrators:

20 entities

Bigger picture available here.

Now, the variations between these two versions of the truth and the real world are (at least):

  • Red circles: Is number 17 (in alphabetical order) Deloitte – in Denmark – who bought Platon 5 years ago or is it KPMG.
  • Blue arrow and circles: Is SAP Professional Services in there or not – and if they are, there must be 21 Top 20 players with two number 11: Edifixio and Entity Group
  • Green arrow: Number 1 (in alphabetical order) Affecto has been bought by number 8 CGI during this year.

PS: Recently I started a disruptive list of MDM vendors maintained by the vendors themselves. Perhaps the analysts can be helped by a similar list for System Integrators?