| Operational KPI analytics | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX AODB explicitly provides KPIs customizable by user and available throughout the application. |
| Structured data export | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | RESA CLEVER DATA, a related INFOPAX analytics component, exposes aggregated airport data for integration into customer statistics channels and provides a native Excel/OLAP interface for traffic and financial statistics. This establishes structured analytical-data extraction from INFOPAX-related data, but it does not establish unrestricted export of every operational or reference dataset from the core AODB. |
| What-if / scenario analysis | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX RMS explicitly provides What if? and What else? simulation functions and can test allocation consistency before implementation. |
| Airport operational reference data | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | Reference data is explicitly one of the three functional AODB modules and is consolidated/shared with other RESA applications. |
| Central AODB flight record | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX AODB is explicitly RESA's Airport Operational Data Base and the core flight-management information source within the INFOPAX suite. |
| Linked arrival / departure turns | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX A-CDM explicitly relies on aircraft rotations as part of its collaborative airport-operations model. |
| Multi-source flight consolidation | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX AODB consolidates operational data and receives automatic updates from airlines, handlers and other external systems. The public material does not document a source-priority hierarchy. |
| Operational flight timestamps | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | RESA INFOPAX explicitly manages seasonal, daily and real-time flight records and applies day-of-operation updates for time-related data including estimated arrival, on/off-block and runway times. Its IATA MVT module also integrates estimated arrival/departure changes. The source establishes operational timestamps but does not enumerate every planned, estimated and actual timestamp field used by every airport implementation. |
| Real-time flight updates | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX AODB automatically updates flight data from airlines, handlers and external systems and includes a real-time program. |
| Schedule versioning / change control | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | RESA INFOPAX documents validity-dated data to preserve history, creation of the day-of-operation schedule from the seasonal schedule, and application of updates to future days when the seasonal schedule changes. This establishes schedule-change traceability and controlled propagation, but the reviewed source does not document named schedule versions, approval workflow or rollback between versions. |
| Seasonal flight schedules | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX AODB explicitly constructs seasonal schedules and derives the daily program from the seasonal program. |
| Drag-and-drop / manual override | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the airport operations model? | INFOPAX RMS explicitly provides a Drag & Drop function for graphical resource management. |