The IT Architecture of Passenger Flow Management
I was reflecting on this recently while thinking about the great strides Xovis has made in simplifying the IT architecture of its passenger flow management system.
The boundaries of IT simplicity
Airports are inherently complex. They are sites of intense movement—physically and digitally—and junction points of many different emotions and interests. Operators’ efforts to simplify and optimize systems are ultimately shaped by the reality of mission-critical processes and the purpose they serve. Put simply, a system cannot be simplified to the point where it reduces a process’s effectiveness.
That there are boundaries to optimization that airport operators must respect is a given. Too often, however, operators overlook the high levels of architectural complexity—and cost—they assume in pursuit of operational efficiency. If, in 2026, you are still obligated to invest heavily in physical servers to improve passenger flow at your airport’s curbside areas, it may be time to rethink your approach.
The allure of the quick fix
The importance of IT architecture in managing passenger flow at airports has grown in recent years, as more companies promising quick fixes enter a market that often rewards innovation and novelty in equal measure. This phenomenon is not limited to passenger flow management, but airports are among the environments where mistakes can create major headaches for many stakeholders.
For newcomers to the market, the learning curve—especially in regard to IT architecture—can be steep. Initial inefficiencies in design may be reduced over time, as experience catches up with ambition. The gap between the two may only be a costly mistake for a few years, or (and this is the big risk) it could be a budgetary weight for years to come.
Sometimes, an airport’s decision to deploy a system with a highly complex IT architecture reflects a disconnect between stakeholders. Operational teams and passenger experience specialists may focus primarily on promised outcomes without fully considering what an on-premises setup entails. This is unfortunate—and entirely avoidable.
The benefits of experience
I’d like to be able to say that the IT architecture supporting Xovis’ Passenger Flow Management System (PFMS) has been perfect since our first airport project. The reality is that there have been many sub-optimal setups and more than a few mistakes in our 16-year history. Fortunately, we have learned from those missteps, gaining valuable experience along the way. Unlike some passenger flow technology, that’s experience you can’t buy on the internet.
Our journey has been one of constant learning and innovation. This is true for our 3D stereovision sensor technology—the recently launched large-area PF sensor being a great example—as well as for our infrastructure, which moved in 2023 to a fully managed system called AERO.
The simple answer behind the move to AERO is, you guessed it, simplicity. AERO is not only the pipeline for the powerful machine-learning-based features Xovis is developing; it also enables a truly global support structure.
AERO’s global deployment structure, combined with enhanced monitoring and alerting, enables proactive system oversight—allowing Xovis to detect potential issues early and inform customers before they are impacted. AERO’s global reach—including Azure datacenters in Japan, India, the US, and Europe—reflects Xovis’ global operations, and it is the result of years spent refining our solution so that airports don’t have to spend years regretting theirs.
Tags: | airports | passenger flow | data-driven operations | optimization | IT architecture |
