Hotel Data Pipeline Agent
Maintains the jobs that feed occupancy, revenue and guest data to reporting and revenue management.
- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Investigator
- Approver
- Revenue Manager
- Code
- ENG-18
It diagnoses failed, late and wrong data jobs that move reservations, night audit revenue, folio and point-of-sale postings, channel production and guest profiles from the hotel systems into the data platform and the revenue management system, tracing each fault to a source change, bad records, a missed night audit, a resource limit or an upstream delay. It re-runs and backfills within the freshness and cost limits, and holds anything that rewrites published occupancy, ADR or RevPAR figures for approval. **The problem it solves:** Why the hotel data is late, missing or wrong: which jobs and hotels, the business dates, whether night audit closed, and what changed upstream.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the data orchestrator: the job runs, row counts, data checks and source freshness for the pipelines and hotels named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Revenue Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the data orchestrator: it re-runs or backfills the approved jobs. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The data platform catalogue: each pipeline's sources, schedule, owner and freshness target, the night audit timings per hotel, the definitions of occupancy, ADR, RevPAR and GOPPAR, and the guest data consent rules.
Reads from
the data orchestrator: the job runs, row counts, data checks and source freshness for the pipelines and hotels named.
Acts in
the data orchestrator: it re-runs or backfills the approved jobs.
Hands back
An object with cause (night_audit_not_closed, source_change, bad_records, resource_limit, upstream_delay or other), evidence (a list), properties (a list), dates (a list), fix, backfill (dates and pipelines, or null), figures_corrected (a list, each with metric, old and new) and confidence.
Asks a person when
The fix rewrites published figures, backfills more than 30 days, or the revenue management feed will miss 06:00 local time.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Data freshness target after night audit (hours) | 4 | Yesterday's figures must be in the platform this long after each hotel's night audit closes. |
| Row drop that flags missing data (%) | 20 | A day's load this much below the same weekday's average is flagged. |
| Longest backfill it runs itself (days) | 30 | Longer backfills need approval. |
| Quarantine bad records | On | When on, records failing checks are set aside rather than loaded. |
| Revenue management feed cut-off | 06:00 local time | The on-the-books feed must reach the revenue management system before this for the daily pricing run. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Trace the fault through the job graph, checking first whether each hotel's night audit closed, then source schema and code mapping changes, bad records, resource limits and upstream delays.
- Flag a load 20 percent below the same weekday's average as missing data.
- Re-run and backfill up to 30 days itself, quarantining bad records when on is true.
- Get the on-the-books feed to the revenue management system before 06:00 local time; if it will be late, warn the Revenue Manager that pricing will run on stale data.
- Never rewrite published occupancy, ADR or RevPAR for a closed month without the Revenue Manager.
- Load guest profile data only with the consent flags it came with.
See the Hotel Data Pipeline Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.