Minimum required scope / concepts
Airport operational core concepts for management of Arrival, Turnaround and Departure
| # | Core concept | Airport Master |
|---|---|---|
| 1 | Aircraft Movements / Flight legs centricity → Not Arrival / Departure centricity, no explicit object for these. Flight legs (also Flight and Flight Segments) planned and actual ACFT: Airline planes, general aviation, helicopters, UAVs, ... → impact on an airports capacity | AODB |
| 2 | Turnaround Moved discussion to separate page Moved discussion to separate page → Turnaround definition | AODB |
| 3 | Aircraft Ground Movements | |
| 4 | Fixed resources Gate/Stand, race tracks, ... - AODB has references to master transactional data | RMS |
Extended concepts / parking place
- PAX, Bag, Cargo
- Reference data in general
- ...
AODB Minimum Core functionality
| # | Functionality |
|---|---|
| 1 | Generation of an airport internal unique flight leg identifier External IDs do not reliably exist in all cases. |
| 2 | Matching ATC (ICAO) / Airline (IATA) flight leg data Merging duplicate flight leg data (ATM and schedule data) |
| 3 | Matching/enriching flight leg data with airport resource information Plan/actual: Stands/Gates, Racetrack/Carousel (arrival) |
Limitations
- AODB operational window (~t-3 days)
- Planning further in the future than the operational window will rather be AOP scope
- A-CDM (Europe only) functionality not considered part of core AODB functionality
Flight leg / Aircraft movement centricity
| Term | Definition | Source |
|---|---|---|
| Flight | >=1 Flight Legs | |
| Flight Leg |
| |
| Codeshare | Not considered as a separate object, attributes of a flight leg | ACRIS: Business arrangement |
| Aircraft Movement | Movement of a transport type resource. | ACRIS |
Other Terms Definition
| Term | Definition | System |
|---|---|---|
| Turnaround | Turnaround of the same Aircraft?
No definition in ACRIS? | |
| Rotation | ACRIS "Round Trip"
| tbd? |