When IT fails, no one notices—until everyone does.
Whether in hospitals, energy grids, or airports, stable operation of digital systems in safety-critical environments is not an option, but a strict requirement. This is where infrastructure must prove its resilience, scalability, and independence in the face of real-world crises.
A prime example is Fraport AG, operator of one of Europe’s largest aviation hubs. When baggage goes missing or safety-critical information is delayed, it’s not just individual passengers’ vacations that are at risk—the operational stability of the entire airport is on the line. Behind the scenes of such a hub runs an extremely complex digital infrastructure that must operate reliably 24/7, despite increasing demands, ageing legacy systems, and tightening security regulations.
To meet these challenges, Fraport has relied for years on tailor-made software solutions, developed in close collaboration with technology partner XDEV. The goal: independence, rapid response, and full control over mission-critical systems. The technological backbone of this strategy: Java. Together, the two partners develop digital solutions for two particularly demanding areas of airport operations: real-time communication in safety-critical environments and baggage logistics with stringent compliance requirements.
Messenger Instead of Middleware: Java Architecture for Real-Time Communication
Currently under development is the “FRA-Messenger,” a cross-platform communication system designed to distribute operational information—such as weather alerts, security instructions, or service disruptions—in real time. Unlike common cloud-based messengers, Fraport deliberately opted for a custom-built solution—and with good reason: off-the-shelf products often cannot be configured with the required granularity or operated in an audit-proof manner within safety-critical infrastructures.
The architecture of the FRA-Messenger is multi-tenant, compatible with both mobile and desktop environments, and supports location-based message delivery. Additionally, structured chat rooms are automatically created for each flight, where flight-related system data can be augmented by bots. The platform is fully Java-based and deeply integrated with existing systems via robust APIs and interfaces that ensure seamless data exchange.
A key strategic advantage: the custom solution grants Fraport full control over data, design, and further development, free from third-party dependencies. This eliminates vendor lock-in and ensures a future-proof communication infrastructure.
Modernizing Legacy: Baggage System on a New Java Foundation
Another major project focuses on the Baggage Reconciliation System (BRS)—specifically the mission-critical “Final Loading” module. The previous application had been developed for Windows Mobile and was no longer viable from a technological standpoint. In close cooperation with XDEV, the system was completely migrated and modernized.
The new solution is platform-independent, modular, and UX-optimized. Special emphasis was placed on intuitive operation—a must-have in the fast-paced environment of daily airport operations. At the same time, the architecture was designed to allow for future extensions—such as automation or integration with new systems—without friction, ensuring both scalability and long-term viability.
Lessons Learned: Why Custom Development Can Pay Off
These projects demonstrate that eschewing off-the-shelf solutions in complex, safety-critical environments can yield significant benefits when development is agile, user-centric, and technologically sound. The choice of Java as the technological backbone offers an ideal combination of stability, scalability, and a large developer ecosystem. Fraport’s ability to pursue this path is also the result of its close and well-established collaboration with XDEV.
Joachim Schneider, responsible for Technical Systems Support at Fraport, highlights the benefits of this close partnership:
“The short communication channels enable smooth project execution and quick responses to new requirements.”
The technical implementation, system architecture, and ongoing development were the responsibility of XDEV. The collaboration between the two organizations serves as a prime example of how technical autonomy and operational requirements can be successfully aligned in safety-critical domains.
