How Symbios/Beontra Gave Airport Operators Data-Driven Planning Across Three Time Horizons

Airports are among the most complex operational environments on earth. A mid-sized airport handles 50,000+ passengers daily, with hundreds of flights, thousands of staff shifts, and dozens of gates that need allocation in real time. Every delay cascades - a late arrival at Gate 12 affects departures at Gate 14, ground crew schedules, baggage handling, and retail revenue.

Symbios AG / Beontra AG provided airport management software, but their existing tools had grown organically over years. The short-term planning module - the one operators used for day-to-day decisions - was outdated, slow, and difficult to use. Planners spent more time fighting the interface than analyzing data. Reports that should take seconds required manual exports and spreadsheet manipulation.

The medium-term and long-term modules existed in separate systems with different data formats. Airport managers who needed to compare this week's gate utilization against next quarter's capacity forecast had to manually reconcile data across three disconnected tools. The result: planning decisions based on incomplete information and institutional memory rather than unified analytics.

Beontra needed a complete rebuild of their short-term planning module and a coherent suite that connected all three planning horizons - without disrupting the airports already using the existing system.

Beontra's requirements were unusual. They needed developers who could work with legacy PHP/Symfony codebases, understand relational database systems spanning MySQL, Oracle, and MS-SQL simultaneously, and build modern ExtJS frontends that airport planners - not software engineers - would actually use. Finding that combination in one team is rare.

easy.bi brought exactly that mix. The team had deep experience with Symfony-based enterprise applications, multi-database architectures, and building data-intensive interfaces for non-technical users. Equally important, easy.bi introduced professional software development practices - CI/CD pipelines with Jenkins, structured quality measures, and a development process that Beontra could sustain after the engagement ended.

The engagement started with the highest-priority pain point: the short-term planning module. Rather than patching the existing system, easy.bi proposed and executed a complete redevelopment - new architecture, new interface, new performance profile.

Short-term planning rebuild. The new module was built on PHP/Symfony with Propel ORM, connecting to the existing MySQL database while supporting Oracle and MS-SQL for airports using different backends. The ExtJS frontend replaced the old interface with a responsive, filterable dashboard where planners can view gate assignments, staff schedules, and flight data in real time. Query performance that previously took 30+ seconds now returns in under 2 seconds.

Multi-horizon analytics. The suite was designed so short-term operational data feeds into medium-term trend analysis and long-term capacity planning. Airport managers can start with today's gate utilization, zoom out to quarterly patterns, and project forward to annual capacity needs - all from one interface. No more reconciling spreadsheets across disconnected systems.

Professional development process. Beyond the code, easy.bi introduced structured quality practices: Jenkins-based CI/CD pipelines, automated testing, Maven build management, and documented development workflows in Jira and Confluence. These practices ensured that Beontra's internal team could maintain and extend the system confidently after the engagement.

Multi-database architecture. Airports use different database systems. The planning suite was built to connect to MySQL, Oracle, or MS-SQL depending on the deployment - without code changes. A database abstraction layer handles the differences, allowing Beontra to deploy the same product across their entire client base regardless of infrastructure.