Choosing a passenger-flow monitoring system starts with the decisions an airport needs to make. Where are queues built? How long are passengers waiting? Is an apparent bottleneck caused by rising arrivals, slower processing, or a change in the queue layout?
When evaluating LiDAR for airport queue monitoring, assess the complete solution: sensor coverage, perception software, measurement methods, analytics, integrations, and ongoing support. Ask suppliers to demonstrate performance in your operating environment and agree on acceptance criteria before rollout.
1. Define the operational problem first
Start with a specific process, such as a security checkpoint, border-control queue, or boarding area. Identify who will use the information and what action it should support. Monitoring a single queue and understanding passenger movement across several terminal areas are different project scopes.
For example, a checkpoint supervisor may need alerts about a growing queue, while an operations planner needs historical demand and throughput patterns. Define these requirements together so the project delivers information that teams can use.
Ask the supplier: Which operational questions will the proposed deployment answer, and which are outside its scope?
2. Agree on what each measurement means
Labels such as “waiting time” and “queue length” can conceal different definitions. Establish the boundaries, units, calculation methods, and reporting intervals for every metric.
| Metric | Definition to agree |
| Queue length | Number of people waiting, physical queue extent, or both; include the queue boundary. |
| Waiting time | Time between specified points; clarify whether service time is included. |
| Throughput | People crossing a defined point per reporting interval. |
| Occupancy | People present within a defined area at a given time. |
| Dwell time | Time spent within a zone, which may include activities other than waiting. |
Distinguish observed waiting times from estimates and forecasts. A completed journey describes what a passenger experienced. A current estimate or forecast addresses what someone joining the queue may experience. Ask how each value is calculated, updated, and labeled.
Ask the supplier: Can you explain a displayed waiting-time value using its measurement boundaries, calculation method, and timestamp?
3. Assess coverage in your actual terminal layout
Request a coverage plan based on the monitored area, mounting options, queue entry and exit points, and nearby structures. Have the supplier identified potential obstructions and show how the design addresses them.
Include busy conditions in the assessment. Test dense groups, luggage, passengers moving alongside the queue, and queues extending beyond their usual footprint. Where multiple sensors are proposed, ask how their observations are combined and how duplicate counts are avoided.
ACI EUROPE’s passenger-flow guidance emphasizes that tracking and queue-measurement quality depends strongly on the perception software. Sensor specifications alone therefore provide an incomplete basis for comparing solutions. Read the ACI EUROPE guidance.
Ask the supplier: What can be measured across the planned coverage area, and where could visibility or tracking become incomplete?
4. Test changing queue layouts
Airport teams move barriers, open lanes, merge queues, and redirect passengers. Include these changes in the evaluation rather than testing only one fixed arrangement.
Ask whether zone and queue changes require manual configuration, happen automatically, or use a combination of both. Establish who can make changes, how long they take, and whether earlier reports remain comparable.
Also test passengers leaving a queue, switching lines, or briefly stepping aside. Ask how these events affect counting and waiting-time calculations.
Ask the supplier: Can you demonstrate a queue-layout change and explain its effect on live measurements and historical reporting?
5. Validate the measurements before acceptance
Agree on a validation plan before the pilot begins. Compare system outputs with independently collected reference, such as synchronized manual counts and timed observations, using the same measurement boundaries.
Cover quiet and busy periods, different queue lengths, and layout changes. Define separate acceptance criteria for passenger counts, queue length, and waiting time. A single headline accuracy percentage does not explain how each metric performs.
For waiting time, request errors expressed in minutes or seconds, alongside the test conditions and sample size. Ask to see missing observations and difficult periods as well as overall averages.
Ask the supplier: What evidence will show that each required metric meets our agreed criteria under representative conditions?
6. Clarify the roles of sensors, software, and integrations
Ask for a simple architecture showing how sensor observations become operational information. Identify which component handles perception and tracking, which calculates queue metrics, and which provides dashboards, alerts, or forecasts.
AMORPH’s collaboration with Veovo illustrates this distinction: AMORPH provides LiDAR perception technology that is integrated with Veovo’s airport platform. The functions delivered to the airport depend on the selected solution and integration. Explore the AMORPH and Veovo collaboration.
For your project, confirm data interfaces, timestamps, update frequency, system ownership, and behavior when a connection is interrupted. If flight-specific analysis is required, ask what additional data and matching logic are needed.
Ask the supplier: Which capabilities are included, which require another platform, and who supports the complete workflow?
7. Review data handling and operational resilience
Include your airport’s privacy, IT, and security teams in the evaluation. Request a clear inventory of the data captured, processed, exported, and retained. Ask whether raw point clouds, movement tracks, or aggregated metrics are stored, and who can access them.
Review retention settings, hosting arrangements, access controls, and any links to other datasets. A description such as “anonymous tracking” should be supported by an explanation of the actual data lifecycle.
Operational reliability also needs attention. Ask how the system reports a sensor outage, network interruption, or incomplete coverage. Agree on how unavailable or stale measurements will be shown so users can distinguish them from valid readings.
Ask the supplier: How will our teams know when the data is unavailable, incomplete, or out of date?
8. Compare installation and ongoing costs
Request an itemized scope covering sensors, mounting, power, connectivity, processing infrastructure, software licenses, integration, commissioning, and training.
Include the cost of support, replacement equipment, configuration changes, and expansion. A pilot should also establish who maintains the installation and who updates measurement zones when the terminal changes.
Ask the supplier: What will it take to operate, maintain, and extend this deployment after the initial installation?
A practical example from Bucharest Airports
At Bucharest Airports, AMORPH implemented a LiDAR-based passenger-flow solution in the Departures Terminal. The published case study describes two LiDAR sensors, passenger counting, queue and waiting-time measurement, dashboards, historical reporting, and automated alerts.
The deployment operated without AODB or e-gate integration to meet the project’s requirements. This is a useful example of why integration needs should follow the intended application rather than be assumed to be identical at every airport.
Read the Bucharest passenger-flow case study.
Your airport queue-monitoring evaluation checklist
Before selecting a solution, request:
- A defined operational scope and agreed metric definitions.
- A coverage plan identifying monitored areas and potential blind spots.
- A demonstration under busy conditions and changing queue layouts.
- A validation plan with metric-specific acceptance criteria.
- A clear division of responsibilities across software and integrations.
- Documented data handling and outage behavior.
- A complete installation, support, and expansion cost breakdown.
Discuss your airport queue-monitoring requirements
Evaluating LiDAR for a checkpoint, border-control area, or boarding zone? Share your terminal layout, monitoring priorities, and reporting needs with AMORPH SYSTEMS to discuss an appropriate approach.
Frequently asked questions
The best fit depends on the terminal layout, required measurements, integration needs, and operational goals. Compare suppliers against the same scenarios and acceptance criteria and ask for evidence from a representative pilot.
A sensor’s distance measurements do not by themselves constitute a queue waiting-time metric. The software deployed must interpret the observations and apply a defined measurement or estimation method. Ask the supplier to explain that method.
The quantity should follow a site-specific coverage design. Ask the supplier to account for mounting positions, obstructions, passenger density, and the area needed for the intended measurements. The two-sensor Bucharest deployment is a project example, not a sizing rule.
Yes, as the Bucharest project demonstrates. Confirm whether your own requirements need additional connections, especially when combining passenger-flow information with flight data or wider operational workflows.
Compare system values with independently timed observations using matching entry and exit points. Agree on test conditions, sample sizes, reporting intervals, and acceptable errors before testing, and review results across different operating conditions.