Skip to content
gfourrAirfield notes veovo.com ↗
Advertisement Paid promotional article by Veovo. Not affiliated with any airport, airline or regulator. Disclosure
Airport control tower under a crescent moon at night
Veovo · Airport operations platform

Flights, gates, queues and billing on one data layer

Veovo is the system airports use to run the day. The live flight record, the turnaround plan, the lane that opens before the queue forms, and the invoice that follows the landing — all drawn from the same operational picture.

See the platform on veovo.com How it works ↓
Strip bay / today
VVO 0442 Boarding
STD14:30
ETD14:42
Gate26
Bay114
VVO 0448 Gate change
STD14:55
ETD15:06
Gate31→8
Bay122
VVO 0451 Pushback
STD15:20
TOBT15:14
Gate17
Bay118
Sponsored article This page is paid promotional content created by Veovo. All product claims are the sponsor's own statements. This is not an independent news article.
Bay 01 / One day on the strip bay

The strip changes. The plan changes with it.

On a flight progress strip, every event — a boarding call, a gate move, a pushback — is one notation. In the Veovo layer, each notation also triggers the work behind it, so the desk, the ramp and the bill all read the same minute.

VVO 0442 Boarding
STD14:30
ETD14:42
Gate26
Bay114
What the layer does Boarding started: the count updates on FIDS, the gate staff see predicted finish, and the queue model re-runs for security.
VVO 0448 Gate change
STD14:55
ETD15:06
Gate31→8
Bay122
What the layer does Gate 31 closes for a late inbound: the change publishes to displays and apps, the stand plan is re-checked, and the transfer desk gets the new walk time.
VVO 0451 Pushback
STD15:20
TOBT15:14
Gate17
Bay118
What the layer does Off-block predicted at 15:14: handlers see the target time, the stand frees for the next rotation, and the billing record opens on the actual movement.
VVO 0457 Airborne
STD15:45
ATD15:41
Gate12
Bay110
What the layer does Wheels up four minutes early: on-time performance is scored, the charges run, and tomorrow's stand rotation already carries today's actuals.
Bay 02 / The data layer

Schedule, movement, decision.

The platform joins the flight schedule to how people actually move through the terminal, then turns the difference between the two into the next instruction for staff.

01 / Schedule

The plan

Flights, gates, baggage belts, check-in desks and staffing — the seasonal plan and the on-the-day plan, held in the airport operational database.

02 / Movement

What is actually happening

Sensors, LiDAR, 3D cameras and Wi-Fi read how people move kerb to gate, while the flight record logs every change to the schedule in real time.

03 / Decision

What to do next

Open a lane, move a gate, push a turnaround, bill the movement. The instruction goes to the desk that owns it, before the queue or the leak appears.

Bay 03 / Systems

Eight modules, one record.

The platform ships as a family of modules that all read and write the same operational picture.

SYS 01

Flight management & AODB

The live record of scheduled and actual flights. Sydney modernised its operations on this, together with flight-information displays.

SYS 02

Resource management

Gate, baggage-belt and check-in desk plans — seasonal and on the day — aimed at higher utilisation and fewer delays.

SYS 03

A-CDM

Turnaround coordination with airlines and handlers: predicted off-block times, on-time performance, lower emissions.

SYS 04

FIDS

Flight screens with dynamic content — the board becomes a channel, not a static list of times.

SYS 05

Queue management & capacity optimiser

Wait times, occupancy and lane-opening plans for check-in, security and border control.

SYS 06

Flow management

Kerb-to-gate movement tied to individual flights, read from LiDAR, 3D cameras and Wi-Fi. Manchester Airports Group uses it to place retail and signage where people actually pass.

SYS 07

Passenger forecasting

When travellers and bags will hit each touchpoint, so staffing is set before the queue forms rather than after it has.

SYS 08

Revenue management

Airline and aeronautical billing: landing, parking and passenger charges, with leakage control. This is not concession point-of-sale reporting.

Bay 04 / The ops clock

A day on the layer.

One operating day, compressed into the five moments where the platform changes what staff do next.

05:40 Forecast

Passenger forecasting sets staffing for the 11:00 bank before the queue has a chance to form.

11:20 Queue

A lane opens on the capacity optimiser's call; wait time and occupancy update from the sensors behind the line.

14:35 Turnaround

A-CDM syncs target off-block times with airline and handlers; the predicted time becomes the shared one.

19:10 Revenue

The billing engine prices landing, parking and passenger charges from the actual movement — and flags what was missed.

22:45 Flow

Kerb-to-gate movement closes out, and tomorrow's plan is seeded with today's actuals instead of yesterday's guess.

140+ Airports
25 Countries
4.5M Flight movements / year
1B+ Passengers
$5B Revenue billed (US$)
Bay 05 / The record

The airport behind the departure board

Passengers see one screen. The airport runs on a far larger one. Behind every departure board sits the airport operational database — the AODB — the live record of what is scheduled and what is actually happening, minute by minute, across gates, belts, desks and stands.

Veovo is the platform built around that record. One data layer joins the flight schedule to how people actually move through the terminal, then turns the difference into an instruction: open a lane, move a gate, push a turnaround, chase a billing leak. The desk that owns the problem gets the message while there is still time to act on it.

The schedule says what should happen. The layer says what is happening. The gap between the two is where an airport's day is won or lost.

The layer starts with flight management. Sydney Airport modernised its operations on the AODB and flight-information displays. Manchester Airports Group reads kerb-to-gate movement from LiDAR, 3D cameras and Wi-Fi to decide where retail and signage should sit. Passenger forecasting sets staffing before the queue forms.

At the end of the chain sits the revenue engine: landing, parking and passenger charges billed from the actual movement, with leakage control built in. Across the customer base that engine bills roughly five billion dollars of aeronautical charges a year. It is not a shop till — this is the money airports live on, not what the duty-free counter takes.

Veovo is London-based and owned by Gentrack, the New Zealand-listed software group. In September 2026, Montréal–Trudeau (YUL) went live on the operations platform. Delivery is cloud, on-premise or managed service, and sales cycles are long — because this software sits under the systems of record an airport cannot afford to get wrong.

A passenger walks past the flight information wall in a terminal corridor at night
What travellers watch is the last link: the board is fed by the same record the tower, the ramp and the revenue desk work from.

The scale of the record is what makes it valuable. Across roughly 140 to 150 airports in about 25 countries, the platform touches more than a billion passengers and 4.5 million flight movements a year. Each one is a row that had to be planned, staffed, moved and billed. The layer exists so those rows never disagree with each other.

No payment details on this page · This page is sponsored content · Platform details are on veovo.com

Bay 06 / The platform

The full picture lives on veovo.com

Product modules, deployments, case studies and procurement contacts are published by Veovo itself. This page introduces the platform; the vendor's site carries the detail.

Open veovo.com
An aircraft at its stand on a wet apron at night with ground vehicles in front
Bay 07 / Questions

Asked at the desk.

Q01 What does Veovo actually run?

Flight management and the airport operational database, gate and belt resource planning, A-CDM turnaround coordination, flight information displays, queue and capacity optimisation, kerb-to-gate flow management, passenger forecasting, and the aeronautical revenue engine. Eight modules that share one record.

Q02 Is this a passenger shopping app?

No. Veovo is the back-of-house platform airport staff use to run flights, gates, queues and airline billing. It is not a consumer app and not a retail point-of-sale system; the revenue module prices aeronautical charges, not shop sales.

Q03 Where is it in use?

Roughly 140 to 150 airports in about 25 countries. Named deployments include Sydney Airport, Manchester Airports Group and Montréal–Trudeau (YUL), which went live in September 2026.

Q04 How is it delivered?

Cloud, on-premise or as a managed service. Implementation cycles are long by design: the platform replaces or sits under an airport's systems of record, so the work is done in staged rollouts rather than overnight.

Q05 Does this page take orders or payments?

No. This page collects nothing, sells nothing and has no forms. Procurement, demos and sales enquiries run through veovo.com.

Q06 Who publishes this page?

This sponsored page is published by gfourr on behalf of Veovo, 203 Eversholt Street, Kings Cross, London NW1 1BU, United Kingdom. Phone +44 (0) 203 9061 000, email [email protected].