Master Data Management in Financial Services

Master Data Management (MDM) has a lot of common considerations regardless of the industry where MDM will be blueprinted and implemented and then there are some key aspects to consider specifically for a given industry.

A recent blog post here on the blog examined the specialties of doing Master Data Management (MDM) in the manufacturing sector. The post was called 4 Key Aspects of Master Data Management in Manufacturing.

In this post two specialties of doing MDM in the financial service sector will be examined. These are:

  • The impact of regulations
  • Data domains in focus

The Impact of Regulations

Doing business in the financial service sector is heavily impacted by the various regulations enforced by authorities across the globe. These regulations aim at improving market confidence, financial stability, and consumer protection and stretch across concepts as Know Your Customer (KYC), Anti Money Laundering (AML) and many more. Doing data management in the financial service sector revolves a lot around adhering to these regulations and the embedded concepts.

When implementing a Master Data Management (MDM) solution in the financial sector you will need a broad set of capabilities that both cover the traditional goals of managing master data as for example getting a Single Customer View (SCV) and then also the specifics of what is entailed in and demanded for Knowing Your Customer (KYC).  

Data Domains in Focus

In master data management we often focus on three major data domains: Customer master data, supplier master data and product master data. These domains are also relevant for master data management in financial services however often with some other meaning, naming, and additions.

The customer is king in any business. In financial services a customer is though more often being regarded as one of several different party roles that are involved in business processes. The customer in various roles is one of more counterparties being involved in transactions taking place. Therefore, we for example see the party domain being more naturally accepted by business stakeholders in the financial service sectors than we until now see in other industries.

From Master Data Management to Data Hub Strategy

The requirements for master data management in the financial service sector will quite early in the journey lead to that solutions must be able to encompass Extended Master Data Management. This can also be seen as a data hub strategy where data quality and data governance play a crucial role.

You can learn more about these considerations in a webinar co-hosted by Semarchy with participants from Sumitomo, HSBC and Bloomberg discussing How to establish data quality and data governance for analytics in financial services.

Which Data Management KPIs Should You Measure?

Everyone agrees that the result your data management efforts should be measured and the way to do that should be to define some Key Performance Indicators that can be tracked.

But what should those KPIs be? This has been a key question (so to speak) in almost all data management initiatives I have been involved with. You can with the tools available today easily define some technical indicators close to the raw data such as percentage of duplicate data records and completeness of data attributes. The harder thing to do is to relate data management efforts to business terms and quantify the expected and achieved results in business value.  

A recent Gartner study points out five areas where such KPIs can be defined and measured. The aim is that data / information become a monetizable asset. The KPIs revolves around business impact, time to action, data quality, data literacy and risk.

Get a free copy of the Gartner report on 5 Data and Analytics KPIs Every Executive Should Track from the parsionate site here.

A Guide to Data Quality

While working with some exciting strategic data management projects together with the data management consultancy firm parsionate, the quest of ensuring data quality in large companies is one of the key topics.

Your Success Factors

In their latest whitepaper parsionate has put data quality in context. The idea behind is this is that only when your data quality initiatives are connected with business goals they will be acknowledged and sustained in business operations.

Marketing departments today want to drive more sales through online channels. To do that you will need a bunch of data quality improvements like having convincing product descriptions for all products put on sale online and having consistent and updated prices across all channels.

In operative management you always strive for making better decisions. To be able to do that you need accurate, updated, and well-related information about markets, products, competitors.

In strategic management your aim is to exploit economies of scale. During mergers and acquisitions, managers must pay particular attention to data quality. In the case of mergers, it must be ensured that the data quality of the previously separate systems is impeccable so that weaknesses are not ported to the new overall situation.

For HR key objectives are to find the best candidates and develop potential. These processes are being digitalized with machine decisions involved. This can only work if the undelaying data is complete, updated and consistent.

For logistics the future belongs to the intelligent supply chain. In many cases the data needed to support this is available, however not in the right quality at the right time. Here, the right data quality management can make a huge difference. 

Source: parsionate, data quality in context

The Right Steps to Drive Business Forward

Your roadmap to high data quality that will pave the way to successful business should involve the following 8 steps:

1: Appoint responsible persons for the data

2: Set targets and Key-Performance-Indicators

3: Evaluate data quality of existing data

4: Cleanse and harmonize data inventories

5: Define standards and processes

6: Automate data quality maintenance

7: Regulate data quality across divisions, groups and borders

8: Continuously improve data quality

Learn More

To get more details on the range of success factors for the various business areas and the 8 step roadmap you can download a free copy of the parsionate Data Quality in Context guide here.

Extended MDM Revisited

Master Data Management (MDM) continues to scale as explored in the post about how MDM inflates.

One inflating trend can be named Extended MDM, which is about taking other data domains than the traditional customer, supplier, and product domains under the MDM umbrella and thus creating a governed data hub.

Which entities that will be is industry specific. Examples from retail are warehouses, stores, and the equipment within those. Examples from pharma are own and affiliated plants, hospitals and other served medical facilities. Examples from manufacturing are plants, warehouses as well as the products, equipment and facilities where the produced products are used within.

Extended MDM can be seen as a twin discipline to a data hub strategy with the twist that the MDM approach adds governance to reflecting, integrating, and meshing critical application in a centralized fashion. This trend was touched in the post MDM Terms on the Move in the Gartner Hype Cycle with reference to the latest Hype Cycle for Data and Analytics Governance and Master Data Management.

The digital twin concept is another trend that, so to speak, is a twin of the Extended MDM trend. You can view all the traditional objects (domains) in MDM and the new to come as digital twins as explained in the post 4 Concepts in the Gartner Hype Cycle for Digital Business Capabilities that will Shape MDM.

Data Governance Necessities

When the talk is about data governance necessities, we often jump to the topic of what a data governance framework should encompass.

However, before embarking on this indeed essential agenda or when reviewing the current state of a data governance framework it is useful to take one step back and consider some core fundamentals to have as a prerequisite to implement and mature a data governance framework.

These prerequisites were recently coined in the Gartner report 7 Must-Have Foundations for Modern Data and Analytics Governance.

A reminder of the importance of having these fundamentals in mind is that only one fifth of organizations who in 2022 are investing in information governance according to Gartner will succeed in scaling governance for digital business.

The 7 Foundations

The first and central foundation in the Gartner approach is Value and Outcomes. Having this in the bullseye is probably not new and surprising to anyone. So, assuming the why is in place it is a question of what and how. According to Gartner the answer is to become less data-oriented and more business-oriented. In the end you will have to make a business-oriented data governance framework.

The next foundation is Accountability and Decision Rights. This theme is a common component of data governance frameworks often disguised as data ownership. Here, think of decision ownership as a starting point. 

Then we have Trust. We are going to have less internal data compared to external data. The known data governance frameworks emphasize on internal data. You must mature your data governance framework to provide trust in external data too. And the connection between these two worlds also.

Next one is Transparency and Ethics. Again, this is a well-known topic that is much mentioned probably under the compliance theme, however seldom really infused in the details. Consider this not as a separate course in a data governance framework but as an ingredient in all the courses.

Adjacent to that we have Risk and Security. Business opportunity, risk and security are often handled separately in the organization. A data governance framework is a good place not to handle this in parallel, but to tie these disciplines together.

Don’t forget Education and Training. Make sure that this is defined in the data governance framework but then can be lifted out into the general training and education provided within the organization.

Finally, there is Collaboration and Culture. Data governance goes hand in hand with change management. You must find the best way in your organization to blend policies and standards with storytelling and culture hacks.

Learn More

Would you prefer that your organization will be among the one out of five who will succeed in scaling governance for digital business? Then, as the next step, please find a free link via the parsionate site for the Gartner report on 7 Must-Have Foundations for Modern Data and Analytics Governance here.

4 Key Aspects of Master Data Management in Manufacturing

Master Data Management (MDM) has a lot of common considerations regardless of the industry where MDM will be blueprinted and implemented and then there are some key aspects to consider specifically for a given industry.

For manufacturing I have found these 4 aspects as key areas when making the roadmap and deciding on Master Data Management architecture principles:

● The impact of Internet of Things (IoT) and Industrial Internet of Things (IIoT)
● Balancing global and local
● Mix of implementation styles
● Direct and indirect customers

The impact of Internet of Things (IoT) and Industrial Internet of Things (IIoT)

More and more produced products are smart devices. This goes for household appliances, power tools, cars and much more. Thus, they are part of the Internet of Things (IoT) meaning that each instance of the product (each produced thing) has its own identity, with a specific configuration, with specific ownership and caretaker-ship and each thing is producing streams of data. This will considerably extend the reach of Data Management and will require your Master Data Management to be open towards business partners.

For manufacturing the producing equipment is also smart devices with a lot of data involved and this can only be sustainable maintained and governed by a master data approach. This realm is sometimes called Industrial Internet of Things (IIoT) which is a facet of Industry 4.0.

Balancing global and local

In manufacturing you can only centralize master data management to a certain degree. There are manufacturing and adjacent processes that are best kept localized due to essential variances in product characteristics, geographic differences and other specializations in line of work.

Therefore, finding the right balance between global and local is a crucial point in blueprinting your manufacturing data management solution, reaching the best fit Master Data Management architecture and building the overarching data governance framework.

Mix of implementation styles

For the same reasons you will not be able to follow a full-blown centralized Master Data Management implementation style. You will need to go for a consolidation Master Data Management style but not necessarily for all data domains and subdomains. You can mix these two styles in what can be seen as a co-existence Master Data Management style.

Direct and indirect customers

In manufacturing your direct customers are typically distributors and retailers who have the end-user customers as their direct customers. However, it happens that you have a business scenario where the same end-users also become your direct customer as a manufacturer. Also, you as a manufacturer for many reasons will benefit from loyally share the end-user customer data with your business partners.

Your Master Data Management implementation should cater for providing a true 360-degree view on customers in this complex business setup.

Learn more

One good resource for a deeper dive into the Master Data Management Architecture considerations in manufacturing is a presentation by my long-time data management peer Magnus Wernersson and Pekka Tamminen of Solita. Find the YouTube video here provided by Semarchy: Volvo Cars – Data Centricity & Digital Innovations with MDM Architecture.

The Business Value Behind Top 3 MDM Trends

The title of this post is also the title of a webinar I will present on the 24th March 2022 together with Michael Weiss of parsionate.

The top 3 Master Data Management (MDM) trends in question are:

  • Interenterprise MDM
  • Extended MDM
  • Augmented MDM

Please join me on the webinar for a discussion about what is behind these trends and not at least what will be the business impact.

Register here for The Business Value Behind Top 3 Master Data Management Trends.

4 Concepts in the Gartner Hype Cycle for Digital Business Capabilities that will Shape MDM

Some months ago, Gartner published the latest Hype Cycle for Digital Business Capabilities.

The hype cycle includes 4 concepts that in my mind will shape the future of Master Data Management (MDM) and data management in all. These are:

  • Industrie 4.0
  • Business Ecosystems
  • Digital Twin
  • Machine Customer

Industrie 4.0

You will find Industrie 4.0 near the trough of disillusionment almost ready to climb the slope of enlighten. Several of the recent MDM blue prints I have worked with have Industrie 4.0 as an overarching theme.

Industrie 4.0 is about using intelligent devices in manufacturing and thus closely connected to the term Industrial Internet of Things (IIoT). The impact of industry 4.0 is across the whole supply chain encompassing not only product manufacturing companies but also for example product merchants and product service providers.

With intelligent devices in the supply chain product MDM will evolve from handling data about product models to handle data about each instance of a product.

Business Ecosystems

The concept of business ecosystems has just passed the peak of inflated expectations.

In a modern business environment, no organization can do everything – or even most things – themselves. Therefore, any enterprise needs to partner with other organizations when working on new digital powered business models.

This also calls for increasing sharing of data, including master data, with business partners. This leads to the rise of interenterprise MDM, which by the way is at about the same position in the Hype Cycle for Data Analytics and MDM.

An example of interenterprise data sharing is Product Data Syndication.

Digital Twin

On the climbing side of the peak of inflated expectations we find the concept of a digital twin.

A digital twin is a virtual representation of a real-world entity such as an asset, person, organization, or process. This fits somehow with what MDM is doing which traditionally has been providing virtual descriptions of customers, suppliers, and products.

With the digital twin flavour, you can sharpen and extend MDM in two ways:

  • Have a more real-world on customers and suppliers by looking at those has roles of business partners along with handling many other external and internal organizational entities
  • Putting more asset types than direct products under the MDM umbrella with improved data governance as a result

Machine Customers

A bit further down the climbing side of the peak you will see the concept of the machine customer.

The expectation is that more and more buying tasks will be automated so there will be no human interaction in the bulk of purchasing processes.

This will only be possible if the products involved at those who sell them are digitally described in sufficient details and categorized the same way on the selling and buying side.

This seems like a job for Master Data Management and the adjacent Product Information Management (PIM) discipline where the buying side needs the right capabilities not only for direct trading products but also indirect supplies.

Also, the concept of augmented MDM will play a role here by applying Artificial Intelligence (AI) to the MDM and PIM side of enabling the machine customer.

The Full Report

You can download the full hype cycle report including the complete visual cycle from the parsionate website: Gartner Hype Cycle for Digital Business Capabilities.

A Guide to Master Data Management

Over the recent months, I have been engaged with the boutique Master Data Management (MDM) consultancy parsionate on some visionary projects in the multi-domain MDM area.

The overall approach at parsionate is that MDM is much more than just an IT issue. It is a strategic necessity. This is based on an experience that I share, which is that if you treat MDM as an isolated technological problem, you will inevitably fail!

Multi-domain MDM

MDM implementations today are increasingly becoming enterprise wide and are thus also multi-domain meaning that they cover business partner domains as customer and supplier/vendor, the product domain and a longer tail of other core business entities that matters within the given business model.

The primary goal of a multi-domain MDM implementation is to unify and consolidate heterogeneous data silos across the enterprise. The more source systems are integrated, the more information will be available and the more your enterprise will benefit from a 360° view of its data.

To achieve the desired goal for your multi-domain MDM program, you need to have a clear vision and a long-term strategic roadmap that shows how the various MDM implementation stages fit together with other related initiatives within your enterprise and where the Return of Investment (ROI) is expected and how it can be measured.

Seven Phases of Forming the Roadmap

In the approach at parsionate there are seven phases to go through when forming the roadmap and launching an MDM program.

Phase 1: Identify business needs

Before embarking on an MDM program, consider what data is most important to your business and where you can create the most value by putting this data under the MDM umbrella.

The main rationale is that through MDM organizations can control the way their most important data is viewed and shared in a more efficient, traceable way and thus improve their performance and productivity. An effective MDM implementation helps you streamline your workflows. It breaks down data silos that prevent data from being reused and shared across the enterprise

Phase 2: Set up a data committee

Establishing a data committee (with any equivalent name for a data focussed body) is perhaps the most frequently mentioned aspect of an MDM strategy. This team would usually consist of many different stakeholders who are in a position to enforce the roadmap and the underlaying activities.

This body must be able to convey the importance of data across the enterprise at all organizational levels. The main concern is to make data a top priority in the enterprise.

Phase 3: Set up a data governance program before defining the MDM roadmap

Many organizations shy away from data governance programs that consulting firms suggest because they seem too complex and costly.

The bitter truth is though that if you fail to implement data governance or embed it strategically into the way the organization works, you will inevitably have to address it at a later stage – in a more time-consuming and costly process.

Phase 4: Set clear goals to ingrain the MDM vision in the organization’s culture

It is difficult to promote an MDM program without a clear vision and objectives. At the executive level, the program could be misunderstood as a technological issue. Sometimes decision-makers struggle to understand the value an MDM program will generate. In this case, they will either not fund it or, if it does go ahead, consider it a failure because the result does not meet their expectations.

It is crucial to involve all relevant stakeholders in the roadmap development process at an early stage and engage with them to understand their expectations and requirements. Only then can you ensure that the core elements of a successful MDM program are aligned with the needs of your entire organization.

Phase 5: Choose a step-by-step approach and rapidly implement sub-projects

The most effective way to implement an MDM program is to start with a few key sources and provide meaningful information in a very short time. It is always difficult to implement everything at once (multiple sources, several integration points, and com­plex data) with a „big bang“ or build a data hub without a specific goal in mind.

If a pilot project quickly realizes a series of short-term bene­fits, users and business leaders will appreciate the value of the MDM program. As soon as it becomes clear that the initial project is successful, you can promote a wider roadmap that shows how the next steps will be carried out in line with the strategic goals of your organization. With this iterative approach, the long-term benefits will become clearer.

Phase 6: The mammoth task: Adopt a data-driven mindset

Building a data-driven corporate culture may be considered the supreme challenge of any MDM program. Data culture goes far beyond a simple corporate strategy that uses data for business processes. Rather, it is a mindset that encourages employees to appreciate the tremendous added value of high-quality data.

Many organizations believe they can simply buy new tools to drive digital transformation. That is an illusion. 

Phase 7: Integrate technology

This illusion does however not mean that that MDM technology is not important.

Hardly any other IT system affects as many different departments and data domains in a company and is, implemented the right way, as powerful as an MDM solution. The extreme importance of this type of software within the entire corporate IT infrastructure means that you need to select a system very carefully and strategically.

The Full Guide If you want to read the full guide to MDM mapping out the high road to a successful implementation you can download it from this parsionate site: Master Data Management