Reltio Connect

• John Doe, 123 Anywhere St., Raleigh NC
• Jonathan Doe, 456 Somewhere Dr., Cary NC

David,

The main reason to assign an Enterprise ID is so that new systems or processes that use master data can reference this ID so that when those systems/processes assign its own ID Reltio does not have to try and match it because it already knows what the entity is based on the Enterprise ID.  If those systems and processes start using records that already have the Enterprise ID they have essentially already identified the entity they are working with and can supplement it with additional data based on survivorship rules within Reltio.

Of course there are other opportunities as well such as using it for reporting purposes so that everyone consuming a given report can understand which entities across the enterprise are being referenced and reported on.

Let me know if that makes sense and if you have a better way of approaching it.

Thanks again for your insights.

Regards,

Brian

David,

The main reason to assign an Enterprise ID is so that new systems or processes that use master data can reference this ID so that when those systems/processes assign its own ID Reltio does not have to try and match it because it already knows what the entity is based on the Enterprise ID.  If those systems and processes start using records that already have the Enterprise ID they have essentially already identified the entity they are working with and can supplement it with additional data based on survivorship rules within Reltio.

Of course there are other opportunities as well such as using it for reporting purposes so that everyone consuming a given report can understand which entities across the enterprise are being referenced and reported on.

Let me know if that makes sense and if you have a better way of approaching it.

Thanks again for your insights.

Regards,

Brian

David,

The main reason to assign an Enterprise ID is so that new systems or processes that use master data can reference this ID so that when those systems/processes assign its own ID Reltio does not have to try and match it because it already knows what the entity is based on the Enterprise ID.  If those systems and processes start using records that already have the Enterprise ID they have essentially already identified the entity they are working with and can supplement it with additional data based on survivorship rules within Reltio.

Of course there are other opportunities as well such as using it for reporting purposes so that everyone consuming a given report can understand which entities across the enterprise are being referenced and reported on.

Let me know if that makes sense and if you have a better way of approaching it.

Thanks again for your insights.

Regards,

Brian

------------------------------
Brian Beil
Senior Manager, Provider MDM Operations
Evernorth

Original Message:
Sent: 06-28-2021 09:48
From: David Starnes
Subject: Enterprise ID Sequence Generator Best Practices

Hi Brian,

Introducing an Enterprise ID has always led to interesting conversations in my opinion. Often times folks (e.g., management) want to establish a "persistent" ID that identifies an individual that never changes - ever. However, that simply isn't possible since 2 individuals assigned an ID who are eventually merged must result in a winner and loser. I know, stating the obvious to a community of MDM practitioners! :-)

When I've introduced an Enterprise ID in the past, I favored using something that isn't easily consumable (e.g., a non-numeric identifier like the entity URI) and wrapped processes around the use of the ID to ensure the latest is used. That being said, I like Angela's use of a numeric value with survivorship being based on the minimum value. Not only does it reduce the frequency of change but it also tends to favor the "older" record.

In either case, you have to expect the value to change and ensure downstream processes leverage the latest and correct value. Another obvious statement right!

As for suspect records and the assignment of an ID, I'd say it depends on the reliability of the data source but typically an ID would be assigned regardless since the data source was worthy enough to be added to the MDM pool.

If you are able to share, I'd love to know the driver behind the need for an Enterprise ID!

------------------------------
David Starnes
Director, Enterprise Information Management & Architecture
RedHill Biopharma, Inc.
Raleigh NC

Original Message:
Sent: 06-24-2021 12:13
From: Brian Beil
Subject: Enterprise ID Sequence Generator Best Practices

Does anyone have best practices and recommendations around the best way to implement a sequence generator that can create an Enterprise ID within Reltio?

For example, do you not assign an Enterprise ID to records that are in the suspect queue?

How do you handle merges and unmerges with respect to this ID assignment within Reltio?

Do you restrict publishing records without an Enterprise ID?

Are there any technical considerations for the format and generation of this ID within Reltio?


Any insights that you have would be appreciated.

Thank you,
Brian

------------------------------
Brian Beil
Senior Manager, Provider MDM Operations
Evernorth
------------------------------