A given master data domain as customer, supplier, employee, other/all party, product (beyond PIM), location or asset
A given business unit
You must eat an elephant one bite at a time. Therefore, contextual MDM makes a good concept for getting achievable wins.
However, in an organization with high level of data management maturity the range of contextual MDM use cases, and the solutions for them, will be encompassed by a common enterprise-wide, global, multidomain MDM framework – either as one solution or a well-orchestrated set of solutions.
One example with dependencies is when working with personalization as part of Product Experience Management (PXM). Here you need customer personas. The elephant in the room, so to speak, is that you have to get the actual personas from Customer MDM and/or the Customer Data Platform (CDP).
In having that common MDM solution/framework there are some challenges to be solved in order to cater for all the contextual MDM use cases. One such challenge, being context-aware customer views, was touched upon in the post There is No Single Customer 360 View.
Getting a comprehensive 360-degree view of customers in digital business processes involves the ability to connect customer master data with other master data entities, hierarchies, transactions, big data, and reference data.
As the diagram above shows, a connected and extended master data landscape (aka data hub) will give you the essential capabilities you need in order to understand your customers. Knowing your customers better allows you to develop better products, drive new streams of revenue, and deliver the best customer experience through hyper-personalization.
A consequence of the business benefits in sharing data will be a rise in data management disciplines aiming at business ecosystem wide data sharing, where product data syndication is an obvious opportunity.
During the last years I have been working on such a solution. This one is called Product Data Lake.
In here it is said that: “The integrated network economy could represent a global revenue pool of $60 trillion in 2025 with a potential increase in total economy share from about 1 to 2 percent today to approximately 30 percent by 2025”.
This dramatic shift will in my eyes mean a change of direction in the way we see Master Data Management (MDM) as well as Product Information Management (PIM) and Data Quality Management (DQM) solutions.
360 is a magic number in the master data and data quality world. It is about having a 360-degree view of customers, suppliers, and products. This is an inside-out view. The enterprise is looking at a world revolving around the enterprise just as back then when we thought the universe revolved around the planet Earth.
By 2025 forward looking enterprises must have changed that view and directed master data, product information and data quality management into a state fit for the network economy by having a business ecosystem wide MDM (PIM and DQM) solution landscape.
In the recent Gartner Top 10 Trends in Data and Analytics for 2020 trend number 8 is about data marketplaces and exchanges. As stated by Gartner: “By 2022, 35% of large organizations will be either sellers or buyers of data via formal online data marketplaces, up from 25% in 2020.”
In the 00’s the evolution of Master Data Management (MDM) started with single domain / departmental solutions dominated by Customer Data Integration (CDI) and Product Information Management (PIM) implementations. These solutions were in best cases underpinned by third party data sources as business directories as for example the Dun & Bradstreet (D&B) world base and second party product information sources as for example the GS1 Global Data Syndication Network (GDSN).
In the previous decade multidomain MDM with enterprise wide coverage became the norm. Here the solution typically encompasses customer-, vendor/supplier-, product- and asset master data. Increasingly GDSN is supplemented by other forms of Product Data Syndication (PDS). Third party and second party sources are delivered in the form of Data as a Service that comes with each MDM solution.
In this decade we will see the rise of multienterprise MDM where the solutions to some extend become business ecosystem wide, meaning that you will increasingly share master data and possibly the MDM solutions with your business partners – or else you will fade in the wake of the overwhelming data load you will have to handle yourself.
The data sharing will be facilitated by data marketplaces and exchanges.
On July 23rd I will, as a representative of The Disruptive MDM/PIM/DQM List, present in the webinar How to Sustain Digital Ecosystems with Multi-Enterprise MDM. The webinar is brought to you by Winshuttle / Enterworks. It is a part of their everything MDM & PIM virtual conference. Get the details and make your free registration here.
One challenge here is how to extend the capabilities in MDM / PIM / DQM solutions that are build for Business-to-Business (B2B) and Business-to-Consumer (B2C) use cases. Doing B2B2C requires a Multidomain MDM approach with solid PIM and DQM elements either as one solution, a suite of solutions or as a wisely assembled set of best-of-breed solutions.In the MDM sphere a key challenge with B2B2C is that you probably must encompass more surrounding applications and ensure a 360-degree view of party, location and product entities as they have varying roles with varying purposes at varying times tracked by these applications. You will also need to cover a broader range of data types that goes beyond what is traditionally seen as master data.
In DQM you need data matching capabilities that can identify and compare both real-world persons, organizations and the grey zone of persons in professional roles. You need DQM of a deep hierarchy of location data and you need to profile product data completeness for both professional use cases and consumer use cases.
In PIM the content must be suitable for both the professional audience and the end consumers. The issues in achieving this stretch over having a flexible in-house PIM solution and a comprehensive outbound Product Data Syndication (PDS) setup.
As the middle B in B2B2C supply chains you must have a strategic partnership with your suppliers/vendors with a comprehensive inbound Product Data Syndication (PDS) setup and increasingly also a framework for sharing customer master data taking into account the privacy and confidentiality aspects of this.
A recent Gartner report states that: “Organizations that fail to understand their use cases, desired business outcomes and customer data governance requirements have difficulty choosing between CDPs and MDM solutions, because of overlapping capabilities.”
Gartner compare the two breeds of solutions this way:
CDPs are marketing-managed tools designed for the creation, segmentation and activation of customer profiles. … These platforms have less governance functionality than MDM solutions and tend to focus on delivering a complete view through the amalgamation of data generated by digital customer interactions.
MDM solutions are more mature technology that also enable customer 360 insights by creating and managing a central, persisted system or index of record for master customer records. They enable governance and management of the core data that uniquely identifies one customer as distinct from another. They were built to support enterprisewide sources and applications of customer data.
CDP platforms (via CRM applications) seems to hit from outside in without getting to the core of customer centrecity. MDM solutions are hitting the bullseye and some of the MDM solutions are moving inside out in the direction of extended MDM, where all customer data, not just customer master data, is encompassed under the same data governance umbrella.
The Master Data Management (MDM) discipline is emerging. A certain trend is that MDM solutions will grow beyond handling traditional master data entities and encompass other kinds of data and more capabilities that can be used for other kinds of data as well.
Measuring data quality in conjunction with general key performance indicators in dashboards that besides master data also embraces other internal and external sources as for example aggregated data from data warehouses and data lakes.
Master data and reference data are two types of data that are shared enterprise wide and even in the wider business ecosystem where your company operates.
In your organization and business ecosystem the data that is shared is basically held in applications like ERP and CRM solutions that have come with a data model provided by the solution vendor. These data models are built to facilitate the operations that is supported by each of these applications and is a data model that must suite every kind of organization.
A core reason of being for a Master Data Management (MDM) solution is to provide a data store where master data is represented in a way that reflects the business model of your organization. This data store serves many purposes as for example being a data integration hub and the place where the results of data quality improvements (eg de-duplication) are stored.
Such a data hub can go beyond master data entities and represent reference data and critical application data that is shared across your organization and the wider business ecosystem within a given industry.