31 October 2012 by Andrew Shanks

Key Considerations When Selecting Your Next AODB

ChromaAODB - Airport Operational Database/AODB

Gone are the days when airports had to rely on custom developed solutions to run each individual aspect of their operation in silo from one and another. Now, airports should view their IT estate as a tightly integrated set of core operational systems that can act as a catalyst to rationalise infrastructure requirements and deliver real operational cost savings across the life of the project.

Most airports will only tackle a refresh of their AODB, RMS, FIDS and related systems once every 5 to 10 years. As highlighted in my last blog, Taking an Integrated, Collaborative Approach to Airport Operational Data, “completely integrated and interactive business intelligence platforms are not yet recognised as viable solutions, due to perceived constraints and cost of implementation.” according to Frost & Sullivan.

Taking AODB as a building block towards joined up airside and passenger processes and a catalyst for greater community engagement, how do operators begin to build a business case for a system refresh and what are the key considerations when going through the process?

AODB as the central source of truth: The concept and design of an effective AODB system should be one based on a central operational database that gathers and collects all data relating to the operation of an airport.

AODB to reduce operational costs: An AODB should run as a Commercial-off-the-Shelf (COTS) product that serves to consolidate and centralise the central IT estate required for its operation.

AODB as a collaborative tool: Leading AODB systems should incorporate all CDM milestones, and respective data, within the core data set, providing a single view in to all key flight data

Joining airside & passenger operations: Airport operators should be taking a proactive approach that transcends airside and terminal operations to ensure critical passenger processes and related data are the central focus.

AODB as a community system: The modern AODB should be equally applicable to airports with competitive ground handling, and airports with total operational responsibility.

AODB for automation & reporting: As a single source of the truth, any system should be one that distributes real-time information to all critical systems such as FIDS and RMS.

Tags: Airside Terminal CDM Next Generation Technology Integrated Operations AODB