Data quality Profiling and scoring

Measure first, then write the rules that pay.

The profiler reads each source and learns its shape before a single rule exists: fill rates, formats, value lists, distributions, key candidates.

ONE SOURCE, SCORED PER COLUMNtax id96%name92%country74%email61%phone38%bank account88%score = rows passing ÷ rows checked, per column · trend kept per dayTHE SAME FIELD IN TWO SOURCESfieldSAPCRMwinsname92%78%SAPemail61%89%CRMcountry74%91%CRMcredit limit96%94%SAPphone38%62%neitherthe winner per field feeds survivorship; 'neither' becomes a verification taskthe profiler produces both views before a single rule is written, so the first rules target the fields that cost the most
One source scored per column, and the same fields compared across two sources so the better source wins each field. Both views exist before any rule is written.
6
dimensions per column
product
2
sources compared per field, or more
product
1 day
to profile a source of 500,000 rows on the showcase estate
showcase
0
rules needed before the first scorecard
product
Column scores

What the profiler learns on the first run

For each column the profiler records the fill rate, the formats seen and their frequencies, the distinct values and the long tail, the numeric distribution, the dates' range and the relationship to other columns. From these it computes a score per dimension: completeness from the fill rate, validity from the formats against the expected pattern, consistency from the row relationships, uniqueness from the key candidates, timeliness from the dates.

Accuracy needs the world, so the profiler samples: it verifies a sample of tax ids, addresses and bank accounts through the verification services and extrapolates a score with its confidence interval. The full verification runs later as a service agent.

The result is the scorecard: one number per column per dimension, with the failing values listed so the steward can see what a failure looks like before writing the rule for it.

Profile · SAP LFA1 · suppliers · 41,800 rows6 dimensions41,800 rows1 h 40 min
columnfillformatsscoretop issue
STCD1 (tax id)96%396%1,672 blank on active
NAME1100%—92%case and suffix variants
LAND199%474%“United Kingdom”, “UK”, “GB”
SMTP_ADDR70%261%12,540 blank
TELF158%938%nine formats
BANKN88%288%312 unverified > 12 months
Across sources

The same field in two systems, and which one wins

This view feeds survivorship directly: the winning source per field is a starting proposal for the attribute group's rule.

FieldSAPCRMRegistryProposed winnerWhy
Registered name92%78%100%Registry, then SAPThe registry is the world; SAP is closest to it
Email61%89%—CRMFilled and well formed far more often
Country74%91%100%Registry, then CRMSAP holds free text; the registry holds the code
Credit limit96%94%—SAPFinance maintains it in the ERP
Phone38%62%—Verification taskNeither source is reliable; verify or drop from the golden record

Where every source is weak, the profiler proposes a verification task or a decision to leave the field out of the golden record. A golden record with fewer, trustworthy fields beats one with every field and no confidence.

Trend and cost

Scores over time, and what a low score costs

Scores are kept per day, so the effect of a rule is visible as a slope: the country standardisation rule deployed on the showcase estate took the source's consistency from 54% to 81% in three weeks, and the trend shows the day it went live. A rule with no slope is a rule to revisit.

Cost translates a score into money for the owner: the field weight says what one failure costs, the consumer weight says how many processes read it, and the count of failing records multiplies them. Missing carrier codes on 31% of dispatch records cost a consumer-goods company £420,000 a month in misattributed freight in the illustrative estate; the number is what put that field first.

The cost view orders the first week's work: the ten costliest fields get rules on Tuesday. Everything else waits until they are under control.

54% → 81%

consistency after one rule

Country standardisation on the showcase supplier source, three weeks after go-live.

showcase estate
£420K

a month, one missing field

Carrier codes blank on 31% of dispatch records, in the illustrative consumer-goods estate.

illustrative
10

fields under rules on day two

The costliest ten by weight × failures, from the profiler's own numbers.

method
1

verification task per weak field

Fields no source holds well become verification tasks or leave the golden record.

method
Questions

Does profiling copy the data?

It reads in place through the connector and keeps the statistics and the sampled failing values; the rows stay in the source. Where a source is too slow to profile live, the Backbone lands a governed copy and the profiler reads that.

How long does it take?

A source of half a million rows profiles in under two hours on the showcase estate; the cross-source comparison runs once the match keys are set, which is the same afternoon.

Who reads the scorecard?

The steward reads the column view to write rules; the owner reads the cost view to set priorities; the governance lead reads the trend; the consumer reads the contract view on the enforcement page.

See quality run on your own domain

Bring one domain and two systems. In a week the sources are profiled, the ten costliest fields are under rules, the first corrections are written back with their acknowledgements and the publish gate is on.