Use cases · Airports
A typical day, with agents.
From the 04:50 runway inspection to the 23:15 daily log: what the agents do, what a person signs, and where they stop.
24 hours
Fifteen moments of an operational day.
An illustration, not client data. Every line exists as such in the ledger: the time, the area, what was done, and what was left to a person.
Two lighting findings on a taxiway edge: two work orders drafted in the CMMS, position and photo attached.
Runway condition code per third proposed from the observations entered; to validate by the duty officer before transmission.
A ten-minute deviation at loading, documented with the timestamps; the service report is ready for the airline.
One test missing on lane 4: checkpoint supervisor notified before opening, log excerpt attached.
Incident report drafted from the system log, maintenance ticket prepared, affected flights listed.
Two without a pick-up slot: provider alerted, cases opened with their deadline.
Taxonomy proposed, 72-hour deadline computed, shift log and wildlife log attached. Awaiting the safety manager’s signature.
Loading scan absent after transfer; file ready for the handler, cause proposed.
Track and noise measurement reconciled; draft reply prepared, for the environment desk to approve.
Result logged, cause proposed, corrective action opened with a named owner and a due date.
Not executed: issuing or extending a pass is not in the warrant. ID office notified, request logged.
Declaration drafted in the taxonomy, photos and GSE data attached, 72-hour deadline computed. Awaiting the station manager’s signature.
Three overdue corrective actions: reminders drafted for their owners, deadlines recomputed.
No finding. Reconciliation for the day: four inspections due, four logged.
From the day’s records, not from memory: exceptions, open tickets, reports awaiting signature.
Times, flights and figures belong to a day composed for illustration. The pilot project is judged on yours.
What changes
Three moments where your teams receive the work already done.
In the morning
An exceptions list, not a pile of logs
What was due against what was logged — inspections, tests, pick-ups — with the work orders and tickets already drafted. Your teams decide; they no longer compile.
At each occurrence
A report ready to sign, on time
The deadline is computed the moment the occurrence is read; the draft exists before anyone has to think about it. What arrives late today arrives on time by construction.
Every month
Reports compiled from the register
Wildlife, security, baggage, PRM, complaints: every figure traceable to the cases behind it. For management, the users’ committee, the authority.
The pilot project
Six weeks from the day access opens. One process. A measure agreed before day one.
The clock starts the day access is open, not at signature: that is the only part of the calendar we control, and it is the only part we commit to. Fixed price for a defined scope, quoted before we start, billed per site or per station — a change of scope is re-quoted, never added to the invoice without written agreement. If the measure is not met at week six, we stop, and you keep the ledger, the documents and the warrant.
Before you sign — five working days
You send us one month of history as an export: inspections, incidents, tests, in whatever format you have. No access to your systems, no security review to open, no commitment.
What comes back
Real deliverables, drafted on your own records: the reports the agent would have prepared, the gaps it would have raised, the sources attached to every line. You judge on evidence before committing to anything. And if the export is not usable as it stands, we tell you — that is already a finding about your data.
Week 1 — scope
One process, its sources and outputs, the warrant, the named humans, the success measure and the stop rule. Written and signed.
Weeks 2–3 — build
Built in your environment, on your records, with the access you grant. Read-only first; write access only where the warrant says so.
Weeks 4–5 — run supervised
The agent works; your people validate. Every run in the ledger, every exception reviewed together each week.
Week 6 — decide
The measure, the ledger and the exceptions on the table. Continue, extend to a second process, or stop.
What you get, whatever the decision
The warrant text, the full ledger export in open formats, every deliverable produced, and a written account of where the agent was wrong. No lock-in: the outputs live in your systems and your formats, not in a platform you would have to keep renting from us.