LensReading which lens this session carries.

Connect · item 15

Data quality gates at intake

Bad data does not become less expensive further down the line. Sixteen checks sit at the first station of every line, covering completeness, validity, duplication, referential integrity, timeliness and consistency. A unit that fails is blocked outright or held in a quarantine queue with a named owner — never quietly waved through with a flag nobody reads.

Connector registry

Health

What the rules are catching

Active and monitoring rules, and everything they have held, released or rejected.

Gates at intake
16
14 enforcing · 2 monitoring only
Checks run
203,658
Across the whole estate at first station
Pass rate
99.6%
767 checks failed
Held right now
95
of 171 items ever quarantined
Held over 72 hours
62
Oldest is 9.1 days old
Rejected at intake
29
47 released after review

What happens on failure

The action is stated on the gate, not decided later.

Block4 gates
The unit never enters the line.
Quarantine8 gates
Held at intake for a named owner to clear.
Warn4 gates
Enters the line carrying a flag that travels with it.

Gates that have never fired

Reported as a zero, not as a pass.

1 of 16 gates have run without a single failure. That is either a genuinely clean condition or a check that is not reaching the data it was written for. It is listed here so somebody has to decide which.

The gates

Each names the dimension it tests, the expression it evaluates, what happens when it fails, and who owns the failures.

GateDimensionApplies toExpressionOn failureRunFailedPassHeldOwner
DQ-04
Amount is a parseable figure in a known currency
High
Validity
Any unit carrying a value
all-lines
Group ERP — Financials
value parses to a positive decimal and the currency code appears in the group currency table
Quarantine
threshold 99.9%
22,08966
99.7%
6D. Halvorsen
DQ-07
Tax code valid for the jurisdiction pair
High
Validity
Cross-border invoice and order intake
all-lines
Indirect Tax Engine
tax code returned by the engine is valid for the ship-from and ship-to jurisdiction pair on the date of supply
Quarantine
threshold 99%
3,1239
99.7%
5F. Aubert
DQ-13
Bank detail change carries out-of-band confirmation
Critical
Validity
Supplier master change intake
function
Source-to-Pay Suite
any change to supplier bank detail is accompanied by an out-of-band confirmation reference
Block
threshold 100%
17,59833
99.8%
1L. Duarte

Quarantine queue

1 item match the current filter. Every held item has an owner and an age.

ItemFunction · lineGateFieldObservedExpectedSourceAgeStatusOwnerOutcome
LG1A-1022
Contract at draft
DQ-07-Q-005
Legal
LG1A
DQ-07tax code returned byout of rangetax code returned by the engine is valid for the ship-from and ship-to jurisdiction pair on the date of supplyIndirect Tax Engine4.5 daysRejected at intakeF. AubertRejected at intake. The unit never entered the line and the requester was told why.

Which lines carry the intake burden

Quarantine volume by function, all time.

Procurement & Source-to-Pay57
Information Technology26
Human Resources22
Supply Chain13
Marketing8
AI GBS & Global Business Services8
Finance7
Administration7
Legal5
Revenue Operations4
Sales4
Customer Service4
Engineering3
Research & Development3

Actions

What is waiting on a person

Quarantine is a holding pen, not a decision. Every item below is work that stopped and is waiting for somebody to say what happens to it.

Operations

What this desk is allowed to start

A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.

Trigger and bound

This desk can start a rule run across a named batch, and it can move an item into quarantine. It cannot release an item, reject one, or change a threshold — releasing bad data is the whole risk this layer exists to manage, so it stays with a person.

Live observability

What the record shows right now

What happened to everything the rules have held.

Current distribution

171 items

Released4727%
In review2816%
Quarantined6739%
Rejected2917%

Is policy and strategy coming to fruition

Whether the written intent is holding here

14 of 16 rules are enforcing. 95 items are held and undecided.

Not holding on the record

The written intent is that no unchecked record reaches a downstream figure. 14 rules enforce that today and 2 only watch. The queue is the real test: 67 items are held with nobody assigned and 28 are open with somebody assigned, against 47 released and 29 rejected historically. A held item is not a failure of the rule — it is the rule working — but a held item nobody judges is a figure quietly missing its input.

What this page is, and what it is not

The gates, the expressions, the thresholds and the quarantine queue are real mechanisms. They run at the first station of every line and they hold work that fails. What they run against is the modeled feed described on the connector registry — connect a customer instance and the same gates run unchanged against real intake.

2 of the 16 gates are set to monitor rather than enforce. They are counted in the check totals but they stop nothing. That is a deliberate state for a gate whose false-positive rate has not yet been characterized, and it is shown rather than hidden behind an overall pass rate.

62 items have been held for more than seventy-two hours, the oldest for 9.1 days. A quarantine queue that ages without clearing is a queue that people have learned to route around, so the age is shown on every row and never averaged away.