Issue
The creation of a cross-functional person repository is a project in its own right, requiring both the identification of duplicates and the implementation of synchronization mechanisms between the various applications connected to the repository.
Key points for creating a people repository
- You have duplicates, and you’ll still have duplicates. In a well-managed system, it is estimated that there are 5% of duplicates. We have encountered up to 70% duplication in the same IS.
- Before deduplicating, put in place processes to prevent the creation of new duplicates, at the risk of having to repeat the operation regularly.
- Sometimes, there are legitimate duplicates created to compensate for functional limitations of the IS. The new repository should take this into account.
- The elimination of certain duplicates can have significant business impacts. Example: bank customers with several PELs (Yes, yes, this does exist)…
- Deduplication is fine, but what descriptive information is considered correct? Freshness date, but not only. Need to take customer preferences into account. Be careful with financial information (RIB)
- It’s complicated to cancel a dedupe in the event of an error. Prefer logical deduplication (Meta-referential) and provide deduplication cancellation procedures.
- Don’t focus on special cases (Example: Same names, dates of birth, addresses, … or almost). These cases do exist, but are very uncommon. Don’t base your strategy on marginal cases.
Our offer
We support you in implementing your person repository and deduplication operations.
Our software tools enable you to detect duplicate individuals and companies using algorithms based on phonemization and fuzzy logic matching of all available descriptive data.
Use cases
Background The SNCF’s purchasing department managed its operations on an MVS, COBOL, DB2 platform with an outdated client-server Easel front. The
…
The Project was based on the development of a suite of tools dedicated to migrate the SiPo application from a
…
Archiving of data and documents from AG2R Group’s Information System Applications intended to be decommissioned Background For many years, the AG2R La
…
