OpenDQ-Matrix360 / learning companion

Data Remediation Approaches

Module 04 Lesson 5 · 7 lessons in this module

Data Remediation Approaches

In brief: Survivorship rules are the logic that determines which field value from which source system populates the golden record when multiple records for the same entity are merged. They are one of the most consequential configuration decisions in MDM — and one of the least discussed outside of technical teams.

Reading lesson

No matching watermarked video was found for this lesson. The complete written lesson is available below.

Watch: How survivorship rules shape the golden record, why enrichment source trust matters for AI training data, and how to sequence MDM remediation milestones as formal gates in the AI development timeline.

Module support notes

Survivorship Rules — The Logic Behind the Golden Record

Survivorship rules are the logic that determines which field value from which source system populates the golden record when multiple records for the same entity are merged. They are one of the most consequential configuration decisions in MDM — and one of the least discussed outside of technical teams.

Getting survivorship rules right requires business input: which source system is most reliable for each field type, how recently updated values should be weighted against historically accurate sources, and whether completeness should override recency when values conflict. For AI programs, field values that become AI features should be sourced from the most accurate system for that feature type — not simply the most recently updated system, which may reflect a data entry error rather than a real-world change.

Note

Survivorship rules encode the organization's knowledge about which sources are most trustworthy for each field. Examples: legal name — most recently updated source wins; email address — source with highest historical accuracy wins; primary address — value verified against postal authority reference data wins. Each rule reflects a deliberate business decision, not a default setting.

A survivorship rule configuration panel for a customer domain showing five fields — legal name, email address, primary address, industry classification, and annual revenue — each with a different configured survivorship logic reflecting which source system is most trustworthy for that specific field type.
Survivorship rules encode the organization's knowledge about which sources are most trustworthy for each field.

Enrichment Sources and Trust Hierarchies

Not all enrichment sources deliver the same quality, and organizations that treat all enrichment as equivalent introduce a new source of data quality risk. Internal authoritative systems — records confirmed and maintained by the business teams responsible for them — are the most reliable enrichment source. Commercial data enrichment providers vary significantly in accuracy, coverage, and update frequency, and their fitness for AI training data should be assessed against the same quality dimensions applied to internal data.

Inferred or derived values carry the highest risk for AI training data, because they introduce model assumptions into the data layer before the AI model has been trained — potentially creating circular reasoning if the model is later used to validate the derived values it was trained on.

Warning

Enrichment source trust determines whether enriched data improves or degrades AI model quality. Using inferred or derived values as AI training features without flagging them as such risks training a model on assumptions — and then using that model to validate the assumptions it was built on. Always track enrichment source provenance alongside the enriched values themselves.

A trust hierarchy pyramid for customer data enrichment with three tiers: Internal Authoritative Systems at the top, Trusted Third-Party Providers in the middle, and Inferred or Derived Values at the bottom. Each tier is labeled with its appropriate use case and its risk profile for AI training data.
Enrichment source trust determines whether enriched data improves or degrades AI model quality.

The Remediation and AI Development Timeline

One of the most valuable governance practices organizations can adopt is the establishment of formal dependency gates between MDM remediation milestones and AI development phases. Model training should not begin until the golden records for all required domains have been created and certified. Model deployment should not proceed until the pipelines delivering master data to the production model have been assessed and governed.

These gates prevent the most common and costly AI data quality failure — a model that reaches deployment with training data quality problems that were known but not resolved because the AI development timeline was not coordinated with the MDM remediation schedule.

Tip

Make MDM remediation milestones explicit gates in your AI project plan — not background work running in parallel. Golden record creation should be a named prerequisite for model training sign-off. Pipeline certification should be a named prerequisite for deployment approval. When these dependencies are invisible to the AI development team, they get skipped under schedule pressure.

A dual-track timeline showing AI Development milestones on top and MDM Remediation milestones below, with dependency arrows connecting MDM outputs to AI development gates. Golden record creation must precede model training; pipeline certification must precede model deployment.
AI development gates should not open until the required MDM remediation milestones are complete.

Remediation is only complete when the fixed data has been certified against the quality thresholds the organization defined before assessment began.

A four-stage horizontal flow showing the data remediation journey: Prioritize — rank issues by business value, AI impact, and remediation effort; Remediate — apply the right method for each problem type; Prevent — embed prevention controls at data entry and integration points; Certify — confirm remediated data meets quality thresholds for operational use and AI readiness.
Remediation without certification is effort without evidence. Confirm the outcome before declaring the work done.

Lesson progress

0% watched
← Previous Next lesson →