Queue length, crowd density, and passenger flow from existing terminal cameras — on-premise, no faces stored.
Terminal 2 — Departures
--:--
In hall
412
Flow
38/min
Avg wait
6 min
Security A1
14 in queue · 6 min
Security A2
27 in queue · 12 min
Security A3
9 in queue · 4 min
Fast track
3 in queue · 1 min
open lane · A2 over threshold
pax/min
Airport Analytics turns the cameras already in your terminal into live operational data: how long the queue at security or check-in is, how dense a gate area has become, and how passengers move between zones.
It gives terminal operations teams a single live view of pressure points — so staff, lanes, and announcements can be adjusted before a queue spills into a corridor.
Processing runs on-premise on a server inside the airport network. Counts, densities, and wait estimates leave as numbers; video stays where it was recorded.Zones, thresholds, and alerts are configured per camera, and every reading is logged so you can replay a shift and see what happened and when.
Per-lane queue length and estimated wait at check-in, security, immigration, and boarding — updated continuously from the camera feed.
Draw zones on any camera and get live occupancy and density, with alerts when a gate area, corridor, or hall crosses the level you set.
Directional counts between zones show where people actually move, so layout, signage, and staffing decisions rest on data rather than guesswork.
Airport Analytics questions
Usually not. The system reads standard RTSP/ONVIF streams from existing CCTV, including Dahua, Hikvision, Axis, and Uniview, as long as the view covers the queue or zone you care about. We review camera placement during scoping and only recommend additions where a view is genuinely missing.
No. Airport Analytics counts people and measures density and movement; it does not identify individuals and stores no faces or biometric data. Only aggregate numbers and events leave the processing server, which sits inside your own network.
Through a live dashboard, threshold alerts by email or webhook, and exports for shift reports. Counts and wait estimates can also be pushed to your existing operations tools or passenger information displays through an API.
An on-premise server inside the airport network connects to the camera streams. Zones and thresholds are configured per camera during a pilot on a limited set of cameras, then extended terminal by terminal. Engineering and support run from our Amman office.
Last updated:
