Open capacity before a queue peaks
Trigger operations when queue length, wait time or inflow rate predicts a service breach.
Airport & rail flow
See pressure build before passengers feel it.
Measure entry rates, queue growth, directional movement and zone occupancy across checkpoints, gates and concourses.
60/minentrance validation traffic rate
Livezone occupancy and queue status
Edgelocal video processing option
Decisions this package supports
Measure what changes the operation.
Find the actual bottleneck
Compare movement between entrances, checkpoints, gates and transfer zones.
Plan peaks with evidence
Use historical flow patterns for staffing, signage and facility planning.
Where the cameras look
From the entrance doors to the gate.
Ayonix runs on the terminal's or station's existing cameras — standard RTSP and ONVIF streams — with processing that can stay inside the facility network. It follows bodies across the lines and zones you configure; it does not identify travellers.
Entrances and arrival doors
Inflow by direction at the doors passengers arrive through, so a rising arrival rate shows before the queue it will become.
Security checkpoints
Queue length, queue growth and estimated wait per checkpoint, with thresholds that tell operations when to open capacity.
Gates and waiting areas
Live occupancy by zone where passengers wait, compared against the limits you configure.
Corridors, escalators and platforms
Directional movement between zones — transfer corridors, escalators and station platforms — to find where flow actually slows.
Fixed-scope start
Validate one checkpoint or gate before network rollout.
One checkpoint, two weeks, agreed ground truth and a written scale recommendation.
- Scene and camera review
- Site calibration
- Acceptance report
Airport & rail FAQ
What operators ask first.
Does passenger counting identify travellers?
No. Counting follows body movement across configured lines and zones; identity matching is not required, and counting does not switch it on. Identity checks at border control are a separate Ayonix system, with its own deployment and policies.
Can processing stay inside the airport or station network?
Yes. Processing can run at the edge or on premises, or in a hybrid design where video stays local and only approved aggregate data goes to reporting systems.
Can it feed our operations systems?
Counts, occupancy and threshold events are available through the API and webhooks, and as CSV exports, for operations dashboards, signage and staffing tools.
Do we need new cameras?
Often not. Ayonix accepts standard RTSP streams and can integrate with common VMS environments. Camera angle, resolution, frame rate and scene density are checked before the pilot.
How is a pilot run?
At one checkpoint or gate for two weeks: a scene and camera review, site calibration, manual ground truth agreed in advance, and an acceptance report with a written recommendation before any network rollout.