Introduction
An inbound aircraft is late. Its assigned stand is needed by another arrival, the passenger display still shows the original gate, and a ground handler has scheduled equipment at the old position. The operations center can see the conflict. Solving it means getting the right decision to several organizations quickly enough for each to act.
Airport operations management software helps coordinate flight information, resources, turnaround events, and operational communication. The category includes airport operational databases, resource management tools, display systems, and collaborative decision-making capabilities. A procurement team should start with the decisions the airport needs to share and the systems that publish or consume those decisions.
Establish authority for each flight update
An airport operational database, often called an AODB, can provide a common operational flight record. It may collect schedules, estimates, and actual events from multiple sources. Different stakeholders may publish different values at different times. Define which source is authoritative for each field and which users can correct the airport’s working record.
Scheduled, estimated, target, and actual times represent different concepts. A passenger display may need a clear public-facing status, while a resource planner needs the underlying estimates and their history. Ask whether the software retains the source and timestamp of updates, and whether authorized staff can see when a value is stale or disputed. A single displayed time without its context can be difficult to use during a disruption.
SITA describes airport management capabilities covering shared operational data and resource use. Such product descriptions help identify the functions in scope. For procurement, ask the vendor to demonstrate a contested update and show how the operations center decides which value to publish to downstream systems.
Treat gate and stand allocation as a constrained decision
A stand or gate can have limits relating to aircraft compatibility, terminal arrangements, equipment, and local procedures. The airport should validate the rules with its responsible operational teams. Then test how the software presents feasible options and identifies conflicts with nearby or subsequent movements. An apparently empty resource may have a commitment that does not appear in a simple schedule.
Consider a late inbound flight that stays on its stand longer than expected. A planner may need to move a later arrival, confirm that staff and equipment can serve the replacement position, and update passenger information. Ask the platform to show downstream effects before the planner commits. Identify who approves the decision and how each affected stakeholder receives it.
Check whether the tool can represent temporary closures and special constraints with effective times. An airport may need to take a resource out of service for planned work. The impact can extend into the next allocation period. Determine how the operations team records the reason and restores the resource after the relevant handoff. Review what staff see if a closure and a flight assignment overlap.
Use turnaround milestones to support action
A turnaround includes activities carried out by airlines, handlers, and other stakeholders. A milestone is useful when it marks an event that someone can observe or provide and another person can act on. Map each milestone to its owner, source, expected update, and operational consequence. A complete dashboard with unreliable milestone inputs provides a weak basis for decisions.
EUROCONTROL describes Airport Collaborative Decision-Making, or A-CDM, as a way to improve predictability and coordination by sharing operational information and optimizing resources. Airports adopting formal A-CDM processes should align procurement with the applicable specifications and local operating agreements. A software module can exchange data and display milestones. The airport and its partners remain responsible for agreeing who updates them and when.
In a pilot, follow a turnaround with several changes to estimates. Check which updates arrive automatically and which require a stakeholder to intervene. Confirm that downstream users can see the latest accepted value and identify when a required milestone has not arrived. Record how teams resolve differences between their own systems and the airport’s shared record.
Design communication around the recipients
A gate change may affect airline agents, handlers, passenger displays, boarding workflows, and other operational teams. Each recipient needs the appropriate information and may acknowledge it in a different way. Map what is sent to each party and how the operations center verifies delivery. A message marked as sent gives little reassurance if a display has stopped receiving updates.
Test connected systems separately and together. An integration might deliver the updated gate while dropping the effective time or aircraft position. Another might send a duplicate update after a delay. Use controlled scenarios to test the recipient’s behavior when messages arrive out of order or are repeated. Agree on how staff identify and resolve mismatches.
Decide what partners can see and update. An airline or handler may need to maintain certain events for its own flights. An airport coordinator may need a broader view. Review permissions with real operational roles and ensure that sensitive data is distributed only where needed. Retain sufficient history for an authorized review of who changed a record and when.
Rehearse degraded operation and measure recovery
An airport can face a failure in one interface while the rest of the system stays online. The operations team needs a way to identify the affected source, apply approved fallback procedures, and reconcile the resulting updates. Test whether the system displays data age and distinguishes manual changes from restored feeds. Agree on who can declare the shared record current again.
Include integration effort, partner onboarding, training, operational support, and infrastructure in the cost comparison. Define what support covers during critical operating periods and which provider owns each boundary. A smaller airport may benefit from an integrated product with a limited number of interfaces. A larger airport may need more specialized modules and stronger governance around shared data.
Use an approved exercise to finish evaluation. Include a late arrival, a stand conflict, an updated turnaround estimate, and an unavailable downstream feed. Follow the decision through each team that acts on it. A platform is ready for wider deployment when staff can tell which information is current, who owns an unresolved update, and which stakeholders have received the revised plan.