Reltio Connect

Match & Merge – We have a broad mix of systems getting customer master data. How those systems will deal with match & merge ID's and the OV values of the attributes is a challenge. Reltio OV logic is also limited but we don't want to customize logic for this. What are others doing in this area? I would like to know best practices and how other big organizations are tackling this challenge. 

------------------------------
Chad McCord
Senior IT Manager, Master Data Management
HP
TX
------------------------------

Reltio Platform will do consolidation of data coming from different sources - match and then merge data together, but will always preserve all data coming from every system. There is no risk of data loss. Operational value calculation is done for every attribute separately and on the fly - each time record is read, OV are re-calculating, so you can always experiment with rules and outcome you get without risk of data loss.

The most important part to keep in mind here - Reltio Platform gives you a lot of flexibility and the way how data would be consolidated strongly depends on match rules configuration. Different use cases assume different precisions of data comparison to consider two records as a match - sometimes fuzzy comparison is enough, sometimes you may need a very strict match to consider two pieces of data came from different systems to be the same.

In section https://docs.reltio.com/datamodeler/managingentitytypes.html you can find useful sections about how to build match rules using match rules editor and to do match rules analysis to make sure rules would be efficient. 

We always recommend experimenting with match rules before rolling them out to production to evaluate precision of results and performance impact. Evaluation would have better quality by using significant data volumes.

Please refer to OV documentation during experimenting with your OV rules - https://docs.reltio.com/matchmerge/survivorshiprules.html 

------------------------------
Alexey Sidelnikov
------------------------------

Original Message:
Sent: 06-01-2021 09:17
From: Chad McCord
Subject: How are others dealing with Match and Merge ID's and OV values of attributes?

Match & Merge – We have a broad mix of systems getting customer master data. How those systems will deal with match & merge ID's and the OV values of the attributes is a challenge. Reltio OV logic is also limited but we don't want to customize logic for this. What are others doing in this area? I would like to know best practices and how other big organizations are tackling this challenge. 

------------------------------
Chad McCord
Senior IT Manager, Master Data Management
HP
TX
------------------------------

Hi @Chad McCord, thanks for your question. Maybe @Walt Feldman has some views on this?

Chris ​​

------------------------------
Chris Detzel
Community Program Manager
Reltio
------------------------------

Original Message:
Sent: 06-01-2021 09:17
From: Chad McCord
Subject: How are others dealing with Match and Merge ID's and OV values of attributes?

Match & Merge – We have a broad mix of systems getting customer master data. How those systems will deal with match & merge ID's and the OV values of the attributes is a challenge. Reltio OV logic is also limited but we don't want to customize logic for this. What are others doing in this area? I would like to know best practices and how other big organizations are tackling this challenge. 

------------------------------
Chad McCord
Senior IT Manager, Master Data Management
HP
TX
------------------------------

Hi Chad,

We master over 40MIL customer profiles in Reltio. Could you be more specific relative to the challenges you are facing with match & merge ID's and the OV values?

In our setup, we use the email address as the surrogate crosswalk value, which essentially eliminates the issues with customer IDs being assigned to a "winner" and also the "loser". This allows us to maintain a "durable" customer ID that we can feed downstream into a variety of systems for a variety of use cases.

In our setup, we migrated data from 2 legacy platforms. Each platform was relatively strong on the data quality of some attributes and weak on others. We used survivorship rules to create an OV containing the best data from each platform. This did not require any custom logic, purely OOB functionality. Now that we are running "steady state", our customer data comes in via our mobile app and web site, so we trust this data to become OV.

Hope this helps,
Walt 

------------------------------
Walt Feldman
Digital Data Lead
Subway
------------------------------

Original Message:
Sent: 06-02-2021 08:12
From: Chris Detzel
Subject: How are others dealing with Match and Merge ID's and OV values of attributes?

Hi @Chad McCord, thanks for your question. Maybe @Walt Feldman has some views on this?

Chris ​​

------------------------------
Chris Detzel
Community Program Manager
Reltio

Original Message:
Sent: 06-01-2021 09:17
From: Chad McCord
Subject: How are others dealing with Match and Merge ID's and OV values of attributes?

Match & Merge – We have a broad mix of systems getting customer master data. How those systems will deal with match & merge ID's and the OV values of the attributes is a challenge. Reltio OV logic is also limited but we don't want to customize logic for this. What are others doing in this area? I would like to know best practices and how other big organizations are tackling this challenge. 

------------------------------
Chad McCord
Senior IT Manager, Master Data Management
HP
TX
------------------------------