DAT-100 · Run data quality and duplicate check

Travel & housing · master data

Status: Concept – not built yet

Keeps the person records free of duplicate entries and formal errors, because every duplicate in housing and travel immediately creates double costs, and every format error causes an automated booking to fail.

Trigger: Nightly batch run across the entire person database; also immediately upon new entry (DAT-010, step 6) and upon change (DAT-090).

Rule (automatable) Judgment (human decides)

Decision rules

• R1 IF similarity score ≥ {{DUBLETTEN_SCHWELLE_SCORE}} THEN present candidate for manual decision; automatic merging never happens, because name matches occur across trades.
• R2 IF a person is on the staffing list but not in the person records THEN trigger DAT-010 and inform GWL.
• R3 IF a person is in the person records but no longer on the staffing list THEN check for reassignment and if applicable DAT-130; pass existing bookings to CHG-030 for cancellation review.
• R4 IF a format error affects a booking-relevant field THEN mark the person in DAT-120 as “not booking-ready”.
• R5 IF two records are merged AND both already carry bookings THEN no automatic cancellation, instead handoff to CHG-020, because the surplus booking is a cost decision.

Common pitfalls

1. Duplicate arises from entry as “Anna Müller” and “Anna Mueller” → two rooms across the entire work block, discovered only at hotel billing. 2. Replacement is created while the replaced person stays active → demand for one position planned twice. 3. Automatic merge without review for two actually different people with the same name → one person loses room, ticket, and billing. 4. Quality report is sent to all trades collectively → every trade lead sees the data gaps of all others.

Impact H × Effort S → Do-first · VOLL · RACI **R** THK · **A** PK · **C** GWL, 1RA · **I** PL, PBH · Manual effort: Estimate: 15–30 min per day reviewing the report for series productions; 10–20 min per merge decision

Request this workflow