Ground handling

A turnaround is thirty-five minutes and a dozen dependent tasks.

Optimum plans staff and equipment against every one of them, watches the apron in real time, and rebuilds the plan the moment something slips. Live at Budapest Airport.

Turnaround · A4 · 11:40 inbound
RESOLVING
chocks · gpu
deboard
unload
clean
fuel
cater
load
board
pushback
fuel truck 6 min late — plan rebuilt
off-block held
Why it is hard

Nothing on the apron holds still long enough to plan once.

Ground handling is the most variable environment in aviation operations. Aircraft arrive late, equipment breaks, people call in sick, and every task waits on the one before it. A roster written the night before is wrong by the first wave.

01

Tasks depend on each other

Boarding waits on cleaning, cleaning waits on deboarding. One slip moves everything downstream.

02

People are not interchangeable

Certifications, rest rules and shift ends decide who can actually take the task, not just who is free.

03

The margin is minutes

SLAs are contractual and tight. The difference between meeting one and missing it is a decision taken in the next five minutes.

What we run

A closed loop, not a nightly roster

Four stages, running continuously through the shift. Each one feeds the next.

01

Plan

Staff, skills and equipment allocated against the day's turnaround pattern.

02

Sense

IoT devices on the apron report position, equipment status and task timing as it happens.

03

Intervene

When a turnaround drifts toward an SLA breach, the supervisor is told while there is still time to act.

04

Learn

Every completed shift sharpens the estimates the next plan is built on.

erdosP-3 in the tower

A supervisor handling a delay doesn't want a settings screen

They say what happened and get an updated plan back. erdosP-3 turns the sentence into constraints, re-solves the shift against the full rule set, and shows the trade-off before anything is committed.

“Move the two people off gate B12 to the delayed turnaround on A4.”

the plan updates, and the SLA impact is shown.

“The 11:40 is delayed forty minutes — what does that do to the rest of the shift?”

the knock-on effects across later turnarounds are shown before you commit.

“Who's currently free and qualified for pushback?”

a real answer, grounded in live skills and availability data.

Proof, not a promise

Running live at Budapest Airport

BUD is where this approach has been proven in a real, high-variability ground-handling environment. The systems described on this page are the ones running there.

Full case study coming soon.

Budapest Airport
Data handling
EU-only residency Sealed, isolated tenant Never used for training GDPR compliant
Security & Compliance

See it applied to your operation

We'll walk through your turnaround pattern and show you where the loop catches what a static plan would miss.

Book a demo