Browse Prior Art Database

Un-Collpase with Source In-Synch

IP.com Disclosure Number: IPCOM000238015D
Publication Date: 2014-Jul-25
Document File: 7 page(s) / 280K

Publishing Venue

The IP.com Prior Art Database

Abstract

This solution will ensure the MDM parties will be in synch with source applications after undo collapse/merge operation. Current approach creates two instances of the same golden record in MDM with different party IDs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 38% of the total text.

Page 01 of 7

Un-Collpase with Source In-Synch


De-duplication process of customer data is one of the most critical components of Master Data Management. A suspect duplicate processing is a three step process:

Potential Duplicate Search


Match and Identification of duplicate customers and
Survivorship of master record

Developing a matching rule is typically driven by the data and business needs. If a conservative approach is taken to develop a matching rule, there are chances of missing few duplicate entries resulting into under-matching (Also known as False Negative). Whereas relaxing the matching rules might result into over-matching i.e wrong identification of duplicates (Also known as False Positive). Therefore organizations need to keep a balance between False Positives and False Negatives in order to get the optimum matching results.

Survivorship of master record is last step of suspect duplicate processing where master record survives and the duplicate record gets eliminated based on the defined survivorship rules.

Based on the survivorship rules, duplicate records are merged/collapsed to create the single golden master record. Wrong merging of records happens due to over-matching (False Positive).

Problem Statement:

Data keeps changing during the lifecycle of a party resulting into change in the identification of the party. As a result, existing matching rule might produce false positive or false negative results.

Such false positive cases create undesirable collapsed parties.

In these scenarios it is critical to revert back the wrong collapsed information to reflect the current state of the source parties.

Today most of the undo collapse solutions create two identical party records from one record. However these records don't contain the latest image of the source records and thus provides a wrong picture of the parties.

Remediation effort for rectifying incorrectly collapsed information requires significant amount of manual intervention to fix the problem.

Business Impacts:

In financial services industry incorrect collapsed customer records can cause an account statement or other confidential information to be sent to a wrong person.

In healthcare, even worse, a life threatening scenario can arise when a person receives a wrong medicine prescribed for another person, gets a blood transformation incompatible with his/her blood type and so on.

Profiles of two commercial organizations operating from same building might get merged due to similar business address and similarity in names .

Because of similar Name, Address, DOB; profile of father and son can be identified as same and subsequently collapsed.

These are few of the incidents which are embarrassing for the organizations. Sometime organizations have to pay financial penalty and subsequently loss of reputation in the market resulting into loss in business.

1


Page 02 of 7

Current Approach:

In MDM product, OOTB (out of the box) 2 different ways of doing merge:

Merge where an add transa...