Version: 0.1 (Draft)
Date: 7 January 2026
Status: For review and comment

1. Purpose

The purpose of the AODB Data Exchange Working Group is to support and accelerate the ACI Data Dictionary initiative by:

• Identifying, prioritising, and sequencing AODB‑related attributes, terms, and concepts that are most critical for real‑world data exchange; and
• Providing airport‑led guidance to help ACI move more quickly from attribute definition to usable interface and message models.

The group exists to ensure that ACI Data Dictionary outputs are driven by actual airport integration needs, particularly in the context of AODB replacement, modularisation, and modern integration architectures.

1. Background and Rationale

Airports across the group are:

• Actively procuring or planning AODB replacements;
• Moving towards event‑driven, API‑first, and modular system architectures;
• Managing complex, legacy integration estates; and
• Seeking to reduce risk through phased migration rather than “big bang” cutovers.

While the ACI Data Dictionary provides a critical foundation for common terminology and semantics, airports currently experience a gap between:

• Comprehensive attribute catalogues, and
• Prioritised, interface‑ready definitions that vendors and integrators can implement quickly.

This working group is intended to:

• Bring practical urgency and focus into the Data Dictionary roadmap; and
• Help ACI concentrate effort on the attributes and terms that matter first for AODB data exchange.

1. Objectives

The working group will:

3.1 Support ACI Data Dictionary Prioritisation

• Identify high‑value AODB attributes and terms required for common operational use cases.
• Recommend prioritisation and sequencing of dictionary content based on integration impact rather than theoretical completeness.

3.2 Link Data Definitions to Interface Use

• Articulate which attributes are required for specific AODB data exchanges (e.g. flight lifecycle events, resource allocation, de‑icing, billing).
• Help translate attribute lists into coherent interface and message concepts, without defining vendor‑specific solutions.

3.3 Reflect Real Airport Architecture Needs

• Provide input grounded in:
• Event‑driven architectures
• Best‑of‑breed vs platform approaches
• Phased migration and parallel‑run scenarios
• Ensure definitions consider coexistence of multiple AODBs and consumers.

3.4 Embed “Secure by Design” Considerations

• Ensure that prioritised attributes and interfaces are shaped with security, data ownership, and resilience in mind from the outset.

3.5 Accelerate Industry Adoption

• Help ACI Data Dictionary outputs become:
• Easier for vendors to implement
• Easier for airports to mandate
• Easier for partners (airlines, handlers) to consume

1. Scope

In Scope

• AODB‑related attributes, terms, and concepts within the ACI Data Dictionary
• Prioritisation guidance based on airport integration needs
• Mapping of attributes to typical AODB data exchanges
• Architectural and migration considerations relevant to definition order

Out of Scope

• Formal ownership or governance of the ACI Data Dictionary
• Detailed interface specifications or schemas
• Vendor or product‑specific designs
• Commercial or procurement activity

1. Key Focus Areas

Indicative areas the group may address include:

• Flight lifecycle and event data
• Resource management (stands, gates, baggage, de‑icing)
• AODB as a data publisher vs data consumer
• Canonical operational events
• “Minimum viable” attribute sets for common integrations
• Migration patterns requiring dual‑running AODBs

Focus areas may evolve over time.

1. Deliverables

The group may produce:

• Attribute prioritisation recommendations for ACI
• Use‑case‑driven groupings of AODB data terms
• Guidance notes linking attributes to interface needs
• Input papers or position statements for ACI working groups

Outputs are expected to be advisory, lightweight, and iterative.

1. Ways of Working

• The group will collaborate via a shared workspace (e.g. Confluence).
• Meetings will focus on specific use cases or integration scenarios.
• Discussion will be grounded in real airport examples.
• Outputs will be fed back to ACI Data Dictionary and related forums.

1. Membership

Membership consists primarily of:

• Airport architects and integration leads
• Practitioners actively involved in AODB operation or replacement
• Participants willing to contribute experience‑based input

1. Relationship to ACI

• The group acts as an informal advisory body.
• Its role is to influence and inform, not replace, ACI governance.
• Success is measured by increased pace, relevance, and usability of Data Dictionary outputs.

1. Success Criteria

The group is successful if:

• ACI Data Dictionary work becomes more clearly prioritised
• Airports and vendors can more quickly define interoperable interfaces
• AODB replacements become lower‑risk and more repeatable across the industry

1. Review and Evolution

This Terms of Reference is a living document and will be reviewed periodically as the group’s scope and maturity evolve.

1. Next Steps

• Circulate this draft for comment
• Agree initial focus areas (e.g. flight event model, RMS interface, migration patterns)
• Confirm alignment with ACI DD Working Group priorities