Survivorship Tables
Survivorship tables have the following characteristics:
They contain customer data that originates in multiple systems.
Different sources might contain conflicting data for the same attribute. For example, two subscribing systems might have the same customer name, but each might have a different address for the customer. Oracle Customer Hub (UCM) resolves these conflicts, ensuring the survival of the best-version record.
The surviving record is that with the best available value for each attribute.
Survivorship rules are an automated mechanism for consolidating customer data to produce a best-version record.
Oracle Customer Hub (UCM) Survivorship Engine evaluates updates from each registered system, and applies rules to determine which value is best for each attribute.
Survivorship rules can be created by a system integrator or a data steward.
Oracle Customer Hub (UCM) allows two thresholds to be set depending on the scores from the matching process:
Records with high-match scores can be automerged by applying survivorship rules.
Records with match scores in the middle will be sent to the data steward for review and resolution.
Records with low-match scores will be left as separate records.