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.
Health
What the rules are catching
Active and monitoring rules, and everything they have held, released or rejected.
What the gates test for
Six dimensions. A check that has never fired is shown as never having fired, not as evidence of a clean estate.
What happens on failure
The action is stated on the gate, not decided later.
Gates that have never fired
Reported as a zero, not as a pass.
The gates
Each names the dimension it tests, the expression it evaluates, what happens when it fails, and who owns the failures.
| Gate | Dimension | Applies to | Expression | On failure | Run | Failed | Pass | Held | Owner |
|---|---|---|---|---|---|---|---|---|---|
| DQ-03 Invoice not already presented Critical | Duplication | Invoice capture intake function Invoice Capture and AP Automation | supplier plus invoice number plus gross amount has not been seen in the trailing 400 days | Block threshold 100% | 6,924 | 44 | 99.4% | 13 | M. Okonjo |
| DQ-09 No conflicting open unit for the same subject Medium | Duplication | Every line all-lines | no other open unit on the same line carries the same subject identifier | Warn threshold 98% | 10,482 | 43 | 99.6% | 8 | N. Ferreira |
Quarantine queue
4 items match the current filter. Every held item has an owner and an age.
| Item | Function · line | Gate | Field | Observed | Expected | Source | Age | Status | Owner | Outcome |
|---|---|---|---|---|---|---|---|---|---|---|
| PR7A-1014 Supplier review at detect deterioration DQ-03-Q-019 | Procurement & Source-to-Pay PR7A | DQ-03 | supplier plus invoice number | already seen | supplier plus invoice number plus gross amount has not been seen in the trailing 400 days | Invoice Capture and AP Automation | 9.0 days | Rejected at intake | M. Okonjo | Rejected at intake. The unit never entered the line and the requester was told why. |
| PR8C-1037 Requisition at approve above threshold DQ-03-Q-001 | Procurement & Source-to-Pay PR8C | DQ-03 | supplier plus invoice number | already seen | supplier plus invoice number plus gross amount has not been seen in the trailing 400 days | Invoice Capture and AP Automation | 8.0 days | Rejected at intake | M. Okonjo | Rejected at intake. The unit never entered the line and the requester was told why. |
| GB8C-1048 Master record at approve DQ-09-Q-011 | AI GBS & Global Business Services GB8C | DQ-09 | no other open unit | already seen | no other open unit on the same line carries the same subject identifier | Enterprise Data Warehouse | 7.8 days | Rejected at intake | N. Ferreira | Rejected at intake. The unit never entered the line and the requester was told why. |
| GB1C-1031 Payroll transaction at feed payroll DQ-09-Q-009 | AI GBS & Global Business Services GB1C | DQ-09 | no other open unit | already seen | no other open unit on the same line carries the same subject identifier | Enterprise Data Warehouse | 3.7 days | Rejected at intake | N. Ferreira | Rejected 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.
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.
Judge a quarantined item
Held by a rule. Nobody has looked at it yet.
Fix the source behind a rejection
Rejected items keep arriving until the upstream cause changes.
Finish a review already open
Picked up, not concluded.
Promote a monitoring rule to active
The rule watches and reports but does not hold anything.
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
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.
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.