Read demand against capacity
A useful terminal view shows arrivals, queue length, wait time, completed processing, and active lanes in the same interval. That makes it easier to tell a flight-wave surge from a lane closure, slow processing, or a blocked route.
01 · Map the journey
Start where a team can change the flow
Check-in and bag drop
- Passenger arrivals and queue growth
- Active desks, kiosks, and service points
- Wait and processing intervals
Security and border queues
- Queue length, spillover, and throughput
- Active lanes during each demand wave
- Operational timing only—not security-risk decisions
Gates and public areas
- Boarding queues and gate-area occupancy
- Concourse, lounge, and retail-zone dwell
- Congestion near circulation routes
Start with one zone where the operating team can change lane coverage, staffing, routing, or opening time. Do not combine unrelated terminal areas into one average.
02 · Define the metrics
Keep queues, throughput, and capacity together
| Question | Measure | Required context |
|---|---|---|
| Is the queue growing? | Arrivals, queue length, wait distribution, and spillover by interval. | Zone boundary, service endpoint, and observation completeness. |
| Is capacity available? | Active lane-minutes, processed passengers, and throughput per active lane. | Lane status and separately authorized operating records. |
| Did the response work? | Threshold-to-operating-change time and the queue after the change. | Comparable flight wave, staffing action, and supporting footage. |
| Is flow blocked elsewhere? | Zone occupancy, dwell, movement path, and repeated congestion intervals. | Camera coverage, occlusion, closures, and terminal layout. |
03 · Connect cameras and records
Connect approved views with operating records
Existing cameras can be evaluated when approved views show the measurement zone, queue boundary, service point, and movement path clearly enough for the agreed task. Validate angle, crowding, occlusion, lighting, frame rate, timestamp alignment, access, and retention before operational use.
Camera observations can be combined with separately authorized flight schedules, desk or lane status, staffing changes, boarding records, and other operational systems. Keep each source identified. Video should not be used to infer passenger identity, nationality, security risk, or travel purpose for this measurement.
04 · Pilot one decision
Test one terminal decision
- Choose one zone and decision. For example, when to review opening another check-in lane.
- Define the events. Agree on arrivals, queue entry, service start, service end, active capacity, and missing observations.
- Compare matched flight waves. Keep time of day, airline or service pattern, lane configuration, and disruptions visible.
- Review the change. Report the wait distribution, throughput, response time, incomplete events, and supporting footage.
References
Sources
- ACI EUROPE passenger-flow guidanceOperational approaches to monitoring airport passenger flows, queues, and crowding.
- NIST Privacy FrameworkA voluntary framework for identifying and managing privacy risk.