OptiFlight
Staff scheduling and operations for ground handling. OptiFlight runs on our four platform layers and the erdosP-3 solver, and it is in production at Budapest Airport.
Demo data.
Running live at Budapest Airport
OptiFlight plans 120 ground handling staff at Budapest Airport against live flight data. It is in production, with more than 42,000 assignments made so far.
Shifts sized to the flights
Staff follow demand hour by hour, not the peak. 21,000 → 17,000 a month at the same flight volume.
Every flight covered
Every flight covered with the right skills and headcount.
Cover planned, not called in
Reserve sized from delay history per airline.
Admin done by the system
Roster, leave, training expiry and reports come out of one system, not Excel.
Production data, Budapest Airport.
What it solves
Ground handling is the most variable operational environment we work in. These are the conditions a fixed shift plan cannot answer.
-
Demand that swings by the hour
Flight schedules change constantly — static staffing cannot keep pace with a turnaround.
-
Staff aren't interchangeable
Skills, education, and certifications determine who can do what — a plan that ignores this is unsafe, not just inefficient.
-
Service-level pressure
Ground handling operates under tight SLAs — any service gap is immediately visible to a passenger.
-
Reactive decision making
Issues discovered only after they have already affected service — no proactive visibility.
Live decisions, crew and skills, the roster, and proof of what was delivered
Every turnaround and delay on one screen
- Integrations Connected to 15+ airport systems, the AODB among them.
- Delays Arrival and departure changes arrive live, listed per flight.
- Technical times Each flight pair’s ground time and tasks, fitted to the SLA.
- Overlaps Assignments a delay pushes into each other are flagged ahead.
Who can do what, and who is trained for it
- Crew Every person, their contract and their availability.
- Processes Each turnaround split into tasks, in order, per airline.
- Skills Qualifications matched to every task: 35 at Budapest.
- Training Training and expiry dates, so no one is planned on a lapsed skill.
From the card reader to the monthly report
- Attendance Card readers record who arrived and left.
- Schedules The monthly roster and the daily allocation, computed by erdosP-3.
- Leave Leave and absence in the same system as the roster.
- Reports Hours, overtime and utilization, without rebuilding them in Excel.
One sentence in, a re-solved shift out
- Ask in words The supervisor types the change, the way they would say it.
- Constraints The words become rules: unavailable, reassign, nobody over 8 hours.
- What holds Certificates, rest, walk time and the SLA on the stand.
- Re-solved erdosP-3 re-plans what changed; every task stays covered.
What was planned, and what was delivered
At the end of the day OptiFlight compares the plan with what actually happened. The measured durations go into the next plan.
Plan against actual
Per person and per task.
Notifications
Shifts sent out to staff, call-ins for open slots.
Certificate of completion
The services delivered, flight by flight, signed off.
Next plan
Measured durations replace the norm times.
Runs on four layers
Each layer works without the one above it.
Computes the plan, and computes it again when something changes.
Follows the operation against the plan: who did what, when and how.
One picture of the operation, joined from the AODB, Veovo and the task record.
Trackers, card readers and managed devices, with GDPR and US privacy rules built in.
- Flight data from the AODB or Veovo.
- Your rostering or HR system stays the system of record. Changes flow back through an interface.
- Hosted (AWS, Kubernetes) or on-premise.
Optimize your airport operations
Talk to us about how OptiFlight can work for your airport operational environment.