Achieving Global Interoperability in Aviation: The Crucial Role of Data Exchange Standards

Achieving Global Interoperability in Aviation: The Crucial Role of Data Exchange Standards

Transforming Airline Distribution and Passenger Services

Introduction

Global interoperability, eXchange of data/Information, is a must for the aviation community. Standards enable interoperability in the aviation supply chain making globally inter-connected aviation system possible.

In today's rapidly evolving technological landscape, industries across the board face unprecedented pressure to modernize. The need for technological change is no longer a matter of convenience but a critical factor for survival and competitiveness. This applies to all sectors, including the airline industry, where emerging technologies, shifting customer expectations, and new operational challenges demand innovative solutions.

As customers grow increasingly accustomed to personalized, seamless, and efficient experiences in their day-to-day lives, these expectations inevitably extend to their interactions with airlines. To remain competitive, it is essential to not only meet but anticipate these evolving behaviors. From improving operational efficiency to enhancing customer experiences, embracing technological innovation allows airlines to adapt to the demands of a dynamic market.

This document delves into the importance of continuous technological adaptation, particularly in the fast-evolving airline industry. In today's competitive environment, customer behaviors and expectations are rapidly changing, driven by digital transformation and innovations in other sectors. For airlines to remain competitive, it's essential to adopt technologies that are aligned with customer-centric solutions—enhancing personalization, convenience, and the overall travel experience.

Technological adaptation also plays a critical role in operational excellence. Airlines face increasing pressures to optimize operations, reduce costs, and maintain high safety and service standards. By embracing emerging technologies such as artificial intelligence, machine learning, automation, and cloud computing, airlines can streamline processes, improve decision-making, and create more efficient and scalable solutions. These technologies enable real-time data-driven insights, predictive maintenance, and better resource management, reducing operational disruptions and improving punctuality.

Furthermore, technological innovation empowers airlines to be agile in response to external disruptions, such as economic downturns, changes in regulations, or unexpected events like pandemics. Agility ensures that organizations can quickly pivot and adapt to new challenges while maintaining a competitive edge. This adaptability, paired with a customer-centric approach, supports the airline's long-term growth, relevance, and ability to deliver superior travel experiences.

In conclusion, continuous technological adaptation is not just about helping airlines to remain competitive but a necessity for airlines. It fuels innovation, enhances customer satisfaction, drives operational efficiency, and ensures that airlines remain resilient in a rapidly changing world.

IATA Industry Standards

IATA’s Message Standards

IATA provides data exchange standards that foster interoperability and efficiency across the airline industry. Among these are key frameworks such as messaging protocols, data models, and emerging areas like digital identity. IATA’s messaging standards, for example, allow airlines, airports, ground handlers, and other stakeholders to communicate seamlessly, ensuring that vital information flows are uninterrupted across global systems. Similarly, data models provide a unified structure for storing, processing, and exchanging airline data, reducing complexity and fostering technical consistency across platforms and operations.


The Role of Digital Identity

As travelers’ demand more seamless, secure, and personalized experiences, digital identity solutions are emerging as a cornerstone of modern aviation. IATA's One ID initiative, for instance, envisions a future where a single biometric token can streamline the entire passenger journey, from check-in to boarding, while enhancing security and privacy.

Modern Airline Retailing Architecture

At the heart of these developments is the Modern Airline Retailing (MAR) architecture, a forward-looking framework that aims to revolutionize the way airlines engage with their customers. By standardizing technologies and processes, the MAR architecture supports a more dynamic, retail-driven approach to airline services. This architecture provides the foundation for future standards and innovations, ensuring that the airline industry responds quickly to changing market conditions and customer preferences.

While current IATA standards cover areas like messaging and data models, the industry is only beginning to explore future technologies. From enhanced digital identity systems to more sophisticated data exchange protocols, IATA will continue to lead the way in defining and refining the technology standards that power the future of air transport.

Airline Industry And Data Sharing Patterns

Modern data exchange standards are being designed as a series of highly granular conversations which allow parties to hone in on the very specific piece of data needed in the context of a specific business transaction and share just that.

This shift will drive increased use of API technology where every actor in the ecosystem from a customer, seller to airline, airport or a government needs to connect seamlessly to any other actor and request the specific information needed at that time and context.

Organization and Role of ATSB in Standards Building

ATSB enables strategic data formats governance and change management oversight across all IATA distribution and passenger services projects and standards development.

The group provides standards & guidance that exploit standards and encourage support for formats and communication.

Strategic Governance

Interoperability

The ATSB plays a pivotal role in ensuring the interoperability of Data Exchange Standards within the airline industry. Interoperability refers to the ability of different systems, technologies, or organizations to communicate, exchange, and utilize information seamlessly, without barriers or compatibility issues. In the context of the airline industry, this involves ensuring that diverse systems—ranging from flight management systems and passenger booking platforms to baggage handling and air traffic control systems—can work together efficiently.

By promoting the adoption of standardized data exchange protocols, the ATSB enables airlines, airports, service providers, and regulatory bodies to share critical information in real time. This ensures smooth operations, from flight scheduling and passenger check-in to real-time aircraft tracking and safety monitoring. Interoperability fosters operational efficiency, reduces the risk of errors or delays due to miscommunication, and enhances overall safety by ensuring that all stakeholders are working from the same accurate and up-to-date data sets.

This seamless integration across systems is vital for an industry as complex and interconnected as aviation. With various systems needing to operate in harmony globally, ATSB’s commitment to interoperability allows for innovation while maintaining consistency and reliability in operations.

Advisory

In addition to its role in promoting interoperability, the ATSB serves as an advisor on architecture and technology strategy to other management standards boards and the Steering Group. This advisory function is critical, as it provides specialized expertise and strategic guidance on emerging technologies, system architectures, and industry best practices.

By offering its technical knowledge, the ATSB supports the strategic direction of technological adoption across the airline industry. It advises on best practices to integrate new technologies into existing frameworks, ensures compliance with industry regulations, and facilitates the alignment of various systems with long-term business objectives. The advisory role also includes guiding the implementation of innovations that enhance both operational efficiency and the customer experience, such as automation, artificial intelligence, and data analytics.

Through its advisory capacity, the ATSB provides guidance so that airline technology strategies are future-proof, scalable, and aligned with global best practices, helping to ensure the sustainable growth of the industry while meeting evolving customer demands.

Operational

Quality Assurance

The ATSB is tasked with upholding the highest standards of quality when it comes to Data Exchange Standards in the airline industry. Quality assurance in this context is crucial because it ensures that all data exchanged between various systems, airlines, airports, and stakeholders is accurate, reliable, and consistent. The ATSB plays a critical role in developing rigorous testing and validation processes to verify that data flows are correct, secure, and meet the required specifications.

Maintaining this level of quality is essential for the smooth operation of complex airline ecosystems, where the accuracy and integrity of data can directly impact safety, operations, and the customer experience. For example, accurate passenger information, flight schedules, baggage tracking, and maintenance records are all vital to ensuring smooth operations, minimizing disruptions, and optimizing efficiency. Any discrepancy in the data could lead to delays, miscommunication, or even safety risks. The ATSB ensures that all Data Exchange Standards undergo continuous monitoring, testing, and improvement, so that any potential issues are addressed before they affect operational systems.

Methodology Management

The ATSB also manages the methodology used for documenting business requirements and developing Data Exchange Standards. This responsibility is critical because it ensures that the processes behind standardization are not only systematic but also transparent and comprehensive. A well-structured methodology allows for a clear definition of business requirements, ensuring that the Data Exchange Standards are developed to meet the specific needs of the airline industry.

Methodology management involves creating detailed documentation, and ensuring that all relevant business use cases are considered. By doing so, the ATSB ensures that the standards are aligned with real-world operational requirements, facilitating seamless integration across diverse systems. A structured approach also means that the development of standards is repeatable, scalable, and adaptable, allowing for future updates or new technologies to be incorporated with minimal disruption.

In addition to the initial development, the ATSB’s methodology management ensures continuous refinement and evolution of Data Exchange Standards, keeping them relevant and responsive to emerging trends and challenges in the airline industry.

Oversight of AIDM

The ATSB is also responsible for overseeing the Airline Industry Data Model (AIDM), a comprehensive framework that standardizes data definitions and structures across the airline industry. AIDM is a key enabler for interoperability and consistency in data exchanges, ensuring that all stakeholders, whether airlines, airports, or service providers, are using the same data models and terminologies. This standardization minimizes discrepancies and inconsistencies, allowing for more efficient collaboration and data sharing across the industry.

The ATSB’s oversight of AIDM involves ensuring that the data model remains up-to-date, relevant, and comprehensive. This includes aligning AIDM with new business needs, regulatory changes, and technological advancements. The ATSB also ensures that the AIDM framework continues to reflect best practices in data modeling, promoting clarity and reducing complexity when integrating systems or exchanging data.

A single point of access to store structured information including:

  • Industry-agreed vocabulary

  • Data definitions and their relationships

  • Related business requirements

 

image-20250303-074856.png

 

image-20250303-074926.png

Standardization

The ATSB maintains standards and best practices for consistent and interoperable implementation of Data Exchange Standards and related formats, promoting efficiency and reliability in business operations.

Overall, the ATSB demonstrates strengths in ensuring interoperability, quality assurance, strategic advisory, methodology management, oversight of the AIDM, and standardization, contributing to the effectiveness and efficiency of data exchange processes within the airline industry.

How ATSB is organized?

The board is primarily composed of representatives from IATA member airlines, particularly those in leadership positions related to IT, architecture, and technology strategy.

Leadership

Senior leadership from IATA and airlines including technology strategists, architecture experts, and other relevant staff, also participate to provide industry-level coordination.

Subject Matter Experts (SMEs)

Technology experts from various fields such as cloud computing, cybersecurity, data modelers, digital transformation are often included in discussions.

Vendors and Partners

In some cases, technology vendors or solution providers may participate as observers or advisors, especially if the technology they provide is critical to industry operations.

Working Groups

Change Management & AIDM

Aviation is a truly interconnected industry and AIDM provides a common point of reference to store industry-agreed vocabulary. It is a central repository to store vocabulary, business requirements, data, and message models, and to build and generate all data exchange specifications.

Defines the structure, semantics, and relationships of data elements relevant to various aspects of airline operations, including passenger services, flight operations, cargo handling, and revenue management.

The Identity Management Working Group

Develops and improves identity management technology standards in identification and identity space.

Identity Management Working Group plays a vital role in shaping the future of identity management standards by addressing identity management challenges and opportunities in the airline industry.

The group brings together industry stakeholders to develop standards, guidelines, and best practices related to identity management in air travel.

Establish industry standards and specifications for identity management processes and technologies, such as biometrics, digital identity verification, and passenger data sharing.

Identity management plays a crucial role in ensuring the security and integrity of air travel operations.

  • Sellers/travel agents in the context of distribution standard.

  • Airlines/airports and service providers in the context of operations standards.

The Open API Working Group

In 2021, the Digital Transformation Advisory Council (DTAC) set a strategy to achieve an Open Data Ecosystem. This working group develops industry standards and best practices for the use of RESTful API technology in the airline industry. Open Data Ecosystem concepts associated with openness and interoperability in technology through the adoption of Open APIs, open standards, and open architecture.

Open APIs facilitate interoperability and collaboration between different software systems, enabling them to exchange data and functionality seamlessly.

IATA’s Open API Hub

IATA’s Open API Hub is a repository for any Airline Industry organization to discover and collaborate with APIs from other trusted industry providers. The Open API Hub allows you to connect to APIs to quickly build partnerships, promote competition and to efficiently bring new products to the market creating a dynamic and interoperable API Ecosystem across the value chain.

Architecture Principles

The overarching purpose of industry-wide standards is to facilitate communication among many business partners and streamline integration of complex systems.

ATSB guidance to IATA standards groups and industry organizations provide a set of principles to follow when working on data exchange or technology-enabled standards. This further outlines the role of ATSB in technology selection.

When designing industry standards. maximize the use of a common data model, process model and look for the opportunities to re-use existing frameworks and patterns.

A series of components with clearly defined functions and using exchange formats is often better than a large and unwieldy all-purpose industry standard.

Alignment with Business Capabilities

When developing new standards, business requirements should always articulate what business capability will be improved or created by implementing the new standard. It is the responsibility of the business standards group to formulate business requirements. Airline Value Chain serves as an anchor model to pinpoint the area of business capability being improved.

The development of messaging schemas should begin with a comprehensive understanding of the business capabilities and processes they are intended to support. This top-to-bottom approach ensures that the data model is not only technically sound but also closely aligned with the strategic objectives and operational realities of the aviation industry.

Business-Centric Design

A business-centric design for a data model means that the structure and elements of the model are built with a clear understanding of the business processes, goals, and requirements of the stakeholders who will be using it. In the airline industry, this includes airlines, airports, service providers, regulatory bodies, and customers. The model must reflect these real-world processes, ensuring that the data it captures and the relationships it represents align closely with how business is conducted.

By embedding the business needs into the data model, the design ensures that the schema not only supports current operations but also remains adaptable to future changes. As the airline industry evolves with new technologies, customer behaviors, and regulatory requirements, the data model must be flexible enough to accommodate these changes without needing a complete overhaul. This alignment with business processes allows the data model to scale, handle complexities, and support innovation, ensuring that it continues to add value as operations grow and diversify..

Interoperability

Interoperability is a critical aspect of any data model, particularly in the highly interconnected airline industry. A well-defined data model facilitates seamless communication and data exchange between different systems, organizations, and stakeholders. Whether it’s flight information being shared between airlines and airports, or passenger data moving between booking systems and security, interoperability ensures that these systems can interact without friction.

In aviation, where multiple systems are constantly exchanging data in real time, smooth interoperability is essential for maintaining efficiency and delivering a high level of service to customers. A consistent and interoperable data model reduces the need for complex integrations, decreases the likelihood of miscommunication, and ensures that systems from different vendors can work together effortlessly. This is crucial for avoiding disruptions, optimizing operations, and enhancing the overall travel experience.

Consistency and Accuracy

A strong data model is the foundation for achieving consistency and accuracy in how data is represented and used across various systems. In the airline industry, this is particularly important given the wide range of operations and the multitude of systems involved in areas such as booking, flight management, baggage handling, and customer service.

A robust data model ensures that data remains consistent as it moves between different platforms, preventing discrepancies that could lead to operational inefficiencies or customer dissatisfaction. For example, if passenger information is incorrect or flight schedules are not synchronized across systems, it could lead to missed flights, delays, or errors in baggage handling. By ensuring consistency and accuracy at the data modeling stage, airlines can reduce the risk of such issues, improving both reliability and decision-making across the organization.

Open Standards

Open standards play a crucial role in defining how various technologies and systems communicate with each other. In the context of a data model, open standards like HTTP, HTML, XML, JSON, and TCP/IP provide common protocols and formats that ensure compatibility, interoperability, and vendor neutrality.

These standards are essential because they enable different technologies, systems, and vendors to integrate seamlessly without being locked into proprietary solutions. This fosters flexibility, allowing airlines and their partners to adopt best-of-breed technologies while still ensuring that they can communicate with existing systems. Open standards also promote innovation, as developers and technology providers can build new solutions that work within a widely accepted framework, speeding up adoption and minimizing integration challenges.

In the airline industry, where diverse systems from booking engines to air traffic control need to work together efficiently, open standards ensure that all parties can exchange data and collaborate effectively, leading to smoother operations and better service delivery.

Cost of Backward Compatibility

Backward compatibility is a critical business requirement for any organization dealing with complex technology systems, especially in industries like aviation, where numerous legacy systems are still in use. However, maintaining backward compatibility comes with significant costs. While it ensures that older systems and technologies can still function alongside newer ones, the ongoing effort to retain and evolve standards for every historical data format can lead to escalating complexities and operational challenges.

Backward compatibility requires continued support for outdated technologies, interfaces, and data formats, which may no longer be efficient or aligned with current industry best practices. This creates a burden on resources, as development teams must dedicate time and effort to ensuring that older systems are supported, often leading to intricate workarounds or temporary fixes. As newer technologies are introduced, the need to bridge the gap between old and new systems increases, adding layers of complexity to the overall infrastructure.

This complexity becomes unmanageable over time as the system architecture grows more convoluted, making it harder to maintain, troubleshoot, or innovate. The costs can manifest in various ways:

  1. Increased Development Efforts: Supporting backward compatibility requires additional coding, testing, and debugging efforts, as developers must ensure that new updates or systems don’t break existing integrations. This prolongs the development cycle and diverts resources away from innovation and new features.

  2. Higher Maintenance Costs: Over time, maintaining backward compatibility adds to the operational costs of maintaining legacy systems and ensuring that they continue to work alongside modern technologies. This includes the need for specialized knowledge of outdated technologies that may no longer be widely used, leading to higher labor costs.

  3. Performance and Efficiency Trade-offs: Supporting old standards can mean compromising the performance, efficiency, and scalability of newer systems. Often, legacy formats and technologies are less optimized for today’s operational needs, resulting in slower processes or reduced system capabilities when compared to fully modernized environments.

  4. Increased Risk of System Failures: As the system becomes more complex with layers of backward compatibility, the risk of errors, failures, or security vulnerabilities increases. These systems can become harder to test comprehensively, as the interplay between old and new components introduces more potential points of failure.

  5. Delays in Adopting New Technologies: Clinging to backward compatibility may delay the adoption of new, more efficient technologies and standards. Organizations may hesitate to implement cutting-edge solutions because of the burden of ensuring compatibility with legacy systems, thereby falling behind competitors who are more agile in adapting to technological advancements.

While backward compatibility may be a necessary business requirement, the cost of supporting it can become prohibitively high if not managed properly. Persisting in maintaining compatibility for every legacy standard and data format introduces unmanageable complexity that stifles innovation, increases maintenance burdens, and creates inefficiencies. To mitigate these issues, organizations need to strike a balance—ensuring backward compatibility where truly necessary, while gradually phasing out outdated systems and adopting forward-thinking standards that enable growth, scalability, and modernization.

Data as an asset

Data exchange standards of the future must respect the need of parties to control the data they generate.

Standards should enable sharing the necessary information in the right context and for an agreed business purpose, and in line with legal requirements, rather than expect sharing of all possible information about a subject just because it may be useful for the recipient one day for a business reason that cannot be yet specified.

Development of standards should consider usability, so that application and implementation of standards becomes easy and is possible in short time frames.

Data Governance

A framework of policies, processes, roles, and standards that ensures data is properly managed, secured, and used effectively within an organization. It focuses on data quality, consistency, compliance, security, and accessibility to support business objectives.

Why Airlines and Suppliers Must Adhere to Data Governance

Airlines and their suppliers manage vast amounts of sensitive and operational data, making data governance critical for compliance, security, and efficiency.

Regulatory Compliance
  • Airlines handle passenger data, payment details, and flight information, requiring strict adherence to legal regulations and standards like GDPR, PCI DSS, and IATA Resolution 787.

Data Security & Privacy
  • Protecting Personally Identifiable Information (PII) such as passport details and payment data is crucial to prevent data breaches.

  • Prevents unauthorized access to sensitive operational data, reducing risks of cyber threats and fraud.

Operational Efficiency & Cost Savings
  • Ensures data consistency and accuracy, reducing errors in flight operations, crew scheduling, and ticketing systems.

  • Enhances supply chain efficiency by ensuring real-time data sharing between airlines and suppliers.

Passenger Experience & Trust
  • Ensures seamless data flow for personalized offers, loyalty programs, and efficient check-in processes.

  • Builds trust by demonstrating a commitment to data privacy and ethical use of passenger information.

Systems Thinking

Systems thinking is a holistic approach that focuses on the way that a system's constituent parts interrelate and how systems work overtime and within the context of larger systems. This method involves understanding the broader context, recognizing patterns, and anticipating the effects of interactions within the system.

Rather than focusing on individual parts in isolation. This approach recognizes that systems are composed of interconnected and interdependent elements, and changes or issues in one part of the system can affect other parts.

Industry Common Language

The airline industry requires a common language to serve as a shared reference point for describing key concepts and business processes across organizations. This is crucial for fostering collaboration, consistency, and efficiency. To achieve this, the industry leverages enterprise architecture and model-driven techniques that create a structured approach to managing and exchanging information.

The introduction of the Airline Industry Data Model (AIDM) represents a major step toward this goal. The AIDM allows the airline industry to systematically document and model its shared knowledge in the form of business and data models, separating this documentation from the process of creating new data exchange standards. By documenting business processes and data models independently and before generating specific standards (such as XML or JSON), the industry ensures a clear and consistent understanding of information across technologies. These models are also computer-readable, meaning they can be applied and adapted to emerging technologies in the future.

Under the governance of the Passenger Standards Conference (PSC), all new data exchange standards being developed today are required to use the AIDM and its associated methodology. This requirement is designed to accelerate the development process of standards and reduce the cost associated with adopting new standards. By ensuring all data exchange is built upon the same foundational model, it eliminates redundancy, streamlines communication, and simplifies integration across different platforms.

Furthermore, as the airline industry begins to embrace advanced data analytics and machine learning, having a common understanding of data is critical. The AIDM facilitates data exchange and processing at scale, allowing for smoother integration of large data sets and making it easier to apply advanced technologies. With this common language in place, the industry can unlock the full potential of data-driven innovations, improving decision-making, operational efficiency, and customer experiences.

Data Model Design Principles

When designing a data model, it is crucial to ensure that the model is robust, efficient, and adaptable to future needs. The following key principles - modularity, scalability, flexibility, and standardization are fundamental to achieving these goals. These principles ensure that the data model is not only effective in the present but also capable of adapting to future changes and growth.

The chart highlights Modularity, Scalability, Flexibility, and Standardization principles.

Modularity

Modularity refers to the practice of breaking down the data model into smaller, manageable components or modules that are independent yet interrelated. Each module focuses on a specific aspect of the system, making it easier to design, maintain, and update individual elements of the model without affecting the entire structure.

  • Benefits:

    • Easier Maintenance: Changes can be made to specific modules without disrupting the entire data model.

    • Improved Reusability: Modules can be reused across different parts of the system or even in different projects.

    • Simplified Debugging: Identifying and resolving issues within a specific module is easier than dealing with a monolithic, interdependent model.

By applying modularity, a data model is easier to extend and maintain, allowing teams to focus on individual components while ensuring the system remains cohesive.

Scalability

Scalability ensures that the data model can handle increasing amounts of data or users over time without significant performance degradation. This is critical in environments like the airline industry, where data volumes grow rapidly as businesses expand and technology evolves. A scalable data model is designed with the understanding that future demands will likely be larger, more complex, or more dynamic than the current requirements.

  • Benefits:

    • Handles Growth: As data volumes increase, the model can expand to accommodate this growth without requiring a complete redesign.

    • Ensures Efficiency: A well-scaled model ensures that operations remain efficient even with high transaction volumes or a larger user base.

    • Prepares for Future Needs: Scalability ensures that the system can support new technologies, such as big data analytics or machine learning, without major overhauls.

Designing with scalability in mind helps to future-proof the data model, ensuring it can grow as the business evolves.

Flexibility

Flexibility refers to the ability of the data model to adapt to changes in business needs, technologies, and data formats over time. It acknowledges that the industry is dynamic, and new data types, technologies, or regulations may emerge that require adjustments. A flexible data model can easily accommodate these changes without requiring a complete redesign or significant disruptions to ongoing operations.

  • Benefits:

    • Adaptability: The model can easily incorporate new data sources, processes, or technology without major disruption.

    • Minimizes Overhaul Needs: By designing flexibility into the system, it reduces the need for complete overhauls as business or technology requirements change.

    • Supports Innovation: A flexible model supports the integration of new innovations, such as AI, IoT, or blockchain, allowing organizations to quickly capitalize on new opportunities.

Flexibility ensures that the data model can evolve with the organization, keeping pace with new challenges and opportunities in a fast-changing environment.

Standardization

Standardization involves the use of consistent formats, protocols, and definitions across the data model. It is essential for ensuring interoperability, efficiency, and ease of integration with other systems or organizations. By adhering to industry standards for data exchange, structure, and communication, a data model promotes a unified approach that reduces the risk of errors and confusion.

  • Benefits:

    • Interoperability: Standardization ensures that systems using the model can communicate seamlessly, even if they come from different vendors or technologies.

    • Consistency: A standardized model ensures that data is consistently represented across various systems, improving the reliability and accuracy of information.

    • Simplified Integration: Standardization facilitates easier integration of third-party applications, new technologies, or external systems, allowing for quicker deployment and fewer complications.

Standardizing the data model fosters consistency and ensures that data exchange is smooth, reducing potential issues in communication and operational efficiency.

Data representation formats - Key focus area in ATSB

In this section, we discuss the various data exchange formats that are being actively worked on and documented by the Architecture Technology Strategy Board (ATSB), which significantly impact the development of industry standards and interoperability. These formats are expected to play a crucial role in enhancing the efficiency and effectiveness of data exchange processes across the airline industry value chain in the coming years. The formats discussed here are either mature or rapidly growing and are already proving to be effective, whether through use by individual airlines or in other industries that face similar challenges to those in aviation.

1. Mature or Rapidly Growing Data Formats

The ATSB is focused on documenting and refining data formats that have either reached maturity or show strong potential for rapid adoption across the airline industry. These formats address current industry-wide problems and present significant opportunities for streamlining data exchange, improving operational efficiency, and enhancing customer experience.

These modern data exchange formats have been proven in various ways:

  • Proven in use by airlines: Some formats have been widely adopted by airlines due to their ability to simplify and standardize processes, making data exchange easier and more reliable.

  • Proven in other industries: Formats originally developed or popularized in other industries—such as financial services, logistics, and telecommunications—are being leveraged by the airline industry. These formats have demonstrated their ability to address similar issues in areas such as data consistency, integration, and scalability.

The growing adoption of these formats indicates that the airline industry is moving towards a more standardized, efficient approach to data exchange. For example, formats such as XML, JSON, and JSON-LD are being increasingly used for their flexibility, human readability, and compatibility with a wide range of technologies. These formats provide the foundation for data exchange between different systems and stakeholders in the industry, ensuring that information is transmitted smoothly and efficiently.

2. Major Format Switches and Business Model Changes

It is important to note that major format switches are often tied to changes in business models within the airline industry. As airlines and their partners shift toward more modern technologies, data formats that were previously suitable for specific use cases may no longer be adequate to support new business requirements.

For instance:

  • Cloud migration: Airlines transitioning to cloud-based infrastructure may need to adopt new data formats that are better suited for distributed systems and scalable cloud environments. This could involve moving away from proprietary formats in favor of more open, standardized options that are optimized for cloud applications.

  • Data-driven business models: The increasing importance of big data, machine learning, and advanced analytics in the airline industry often requires the use of modern data formats that can easily accommodate complex, large-scale data sets. Older formats may be insufficient for handling the volume and variety of data needed for these advanced applications.

  • Industry collaboration and partnerships: As airlines collaborate more with partners in travel, hospitality, and logistics, the need for interoperable data formats becomes even more pressing. The switch to standardized formats facilitates smoother data exchange across organizational boundaries and different technologies.

These business model shifts are catalysts for the adoption of new data formats that are more agile, scalable, and compatible with emerging technologies. They also highlight the broader trend of digital transformation in the airline industry, where technology plays an essential role in driving operational improvements, innovation, and customer satisfaction.

Business Continuity

Business continuity is a critical concern for any organization, especially in industries like aviation where downtime or disruptions can have severe operational, financial, and reputational consequences. When it comes to data exchange formats, maintaining continuity becomes even more important when legacy formats are still in use, even though they are gradually being replaced by newer standards.

In the context of the airline industry, legacy/classic data exchange formats have historically been the backbone of communication between systems, stakeholders, and partners. However, as the industry evolves, organizations are increasingly adopting more modern and efficient standards. Despite this shift, legacy / classic data exchange formats may still be in heavy use across various systems and processes. Therefore, ensuring business continuity requires a careful balancing act between transitioning to new formats and maintaining operational stability.

The Need for Legacy Formats in Business Continuity

Legacy data exchange formats, while outdated, may still be integral to business operations, especially in large-scale, complex systems that have been built around these formats over many years. This is particularly true when the legacy systems are deeply embedded in day-to-day operations and there are critical processes that depend on them. Some reasons why legacy formats must be maintained for continuity include:

  • Ongoing Use of Legacy Systems: Many legacy systems continue to handle crucial operations, such as flight scheduling, reservations, check-in processes, and more. These systems may rely on legacy formats for data exchange, meaning a complete overhaul is not always feasible due to the complexity and cost of upgrading or replacing these systems.

  • Long Transition Period: Transitioning from legacy systems to modern technologies (eg: Modern Airline Retailing) is often a long and resource-intensive process. During this period, businesses must ensure that legacy systems continue to work seamlessly with newer systems. Data format compatibility is critical to prevent disruptions, maintain operational integrity, and protect the customer experience.

  • Regulatory and Compliance Requirements: Some legacy formats may still be necessary for compliance with industry regulations or contractual obligations with partners. For example, certain data formats might have been mandated in earlier agreements or regulatory frameworks, which means they must be maintained for continuity until the terms of those agreements can be updated.

Managing the Transition to New Formats for Business Continuity

To ensure business continuity during the transition from legacy data exchange formats to more modern ones, organizations must take a strategic approach. Here are some key steps to manage this transition effectively:

  • Gradual Transition: Instead of making a sudden switch to new formats, the transition should be phased in gradually. This allows legacy systems to coexist with newer systems, enabling businesses to test new data exchange formats while ensuring that legacy systems continue to function without disruption.

  • Parallel Systems: During the transition period, many organizations choose to run parallel systems, where both legacy and new systems operate side by side. This provides a safety net in case there are issues with the new formats, while also allowing time for employees to become familiar with new technologies and workflows.

  • Backward Compatibility: New data exchange standards should be designed with backward compatibility in mind. This means that the new systems should be able to support legacy formats for a period of time, ensuring that business continuity is not compromised. Ensuring compatibility allows for smooth integration between older and newer systems, reducing the likelihood of disruptions during the transition.

  • Comprehensive Testing and Validation: Before fully migrating to new formats, it’s essential to conduct thorough testing and validation. This includes testing the interaction between legacy and new systems, as well as validating that the new formats can handle the same data flows and processes without introducing errors.

  • Stakeholder Communication: Communication is key when transitioning from legacy to modern data exchange formats. Clear communication with internal stakeholders, partners, and customers ensures everyone is aware of the changes and can make the necessary adjustments. Regular updates help mitigate any potential risks associated with misunderstandings or delays in the transition.

Contained formats - Moving Away from Legacy Standards

ATSB discourages further development of data exchange standards based on legacy/classic formats, specifically TELETYPE messaging over Type B protocol, and EDIFACT messaging typically transferred via Type A protocol or IBM MQ. These legacy formats, though once essential to the airline industry, are increasingly becoming obsolete due to their technical limitations and the evolving needs of modern aviation systems.

TELETYPE and EDIFACT

While there may be exceptional situations justifying minor adjustments of TELETYPE or EDIFACT based messaging standards for business continuity reasons, business standards groups should assess each such case with great care. Whenever possible, a request to amend such standards should be considered as a business driver for modernization and priority should be given to developing a modern technology solution over upgrading TELETYPE or EDIFACT message.

Extensible Markup Language / XML

Most IATA data exchange standards are currently published in the form of XML schema. Older schemas were handcrafted and require manual changes. More recent schemas such as the ones developed by NDC and ONE Order are generated from a common Airline Industry Data Model (AIDM) and they are semantically interoperable.

XML format is being gradually taken over by a more lightweight approach described at the beginning of this section. More importantly, traditional XML schemas were typically designed to facilitate sharing of large sets of data for “any” use rather than the currently preferred approach of selective data sharing data for specific business purposes. This is where the traditional XML schemas represent legacy approach.

When planning development of new messaging standards or major upgrades of existing XML schemas, particularly those developed prior to the introduction of the AIDM, standards groups should consider the benefits of upgrading from large XML schemas to a family of API specifications which may represent more appropriately the business process and better support the modern paradigm of selective data sharing.

Lightweight integration and use of APIs

Recently, we have seen an acceleration in adoption of lightweight integration protocols for direct sharing of information.

Typically, this would represent sharing content in JSON over HTTP applying software architecture style called Representational State Transfer (REST). This is a mature method suitable for direct sharing of information between two parties and readily available for use in mobile devices.

When designing API specifications, great care should be taken to understand the expected interactions and data flows and use those to guide the design. Mechanical translation from existing XSD schemas traditionally focusing only on data content over process is discouraged.

Phasing Out Legacy Formats: A Strategic Approach

Open Data Ecosystem

Open Data Ecosystem concepts associated with openness and interoperability in technology through the adoption of Open APIs, open standards, and open architecture.

Open Standards

Defines how various elements of a technology or system should behave or communicate, ensuring compatibility, interoperability, and vendor neutrality.

Open Standards promote innovation, competition, and transparency by allowing multiple vendors and developers to implement and support them without restrictions.

Open Architecture Design Approach

Open Architecture emphasizes interoperability, flexibility, and modularity in the development of systems or solutions. It involves using open standards and promotes vendor neutrality, avoids vendor lock-in, and enables organizations to easily adapt and extend their systems as technology evolves.

To develop industry standards and best practices for the use of RESTful API technology in the airline industry.

Open technology, including but not limited to REST API, GraphQL, AsyncAPI standards and best practices.

As the industry moves towards more modern data exchange formats, it is important to ensure that the transition away from legacy formats is handled strategically. Here are some key considerations:

  • Gradual Transition: Phasing out legacy formats cannot be done abruptly without causing disruptions in daily operations. Many airlines and service providers still rely on these formats, so a gradual shift to more modern solutions is necessary. This transition could involve dual systems where both legacy formats and new formats coexist during a period of parallel operation.

  • Backward Compatibility: New standards and technologies must be backward compatible to ensure that airlines and stakeholders using legacy formats can still communicate effectively. During the transition, it is critical that systems are designed to support both old and new formats, ensuring smooth data exchange without interruption.

  • Standardization and Modernization: The ATSB’s approach encourages the development of modern, standardized formats that are compatible with current and emerging technologies. By standardizing data exchange across the airline industry, the ATSB ensures that all stakeholders can work within a common framework that is scalable and adaptable for future advancements.

JSON Preferred Over XML

When it comes to choosing between JSON and XML for data exchange, JSON has emerged as the preferred option for a variety of reasons. In particular, simplicity, readability, performance, and efficiency make JSON a superior choice in modern applications, especially in the fast-paced and high-demand environments like the airline industry. Here’s a breakdown of why JSON is increasingly favored over XML.

1. Simplicity and Readability

Ease of Use

One of the primary reasons JSON is preferred over XML is its simplicity and ease of use. JSON is much simpler in structure, making it easier for both developers and systems to handle. Its format is compact and doesn’t require complex tags or attributes like XML. Here's why:

Human-Readable:

JSON has a format that is easy for humans to read and understand. Its key-value pairs and simple structure make it far more intuitive compared to XML’s verbose tag-based format.

Learning Curve:

The learning curve for JSON is significantly lower than XML due to its simpler structure. Developers familiar with JavaScript or other modern programming languages find JSON natural to use, as it mirrors common data structures such as objects and arrays. This is in contrast to XML, which involves more abstract concepts, such as nested tags and attributes.

Data Structure

The data structure in JSON is based on key-value pairs (or sometimes arrays), making it more intuitive than XML’s hierarchical tree structure. In XML, data is typically nested under multiple tags, which can become cumbersome and difficult to navigate, especially in large datasets.

  • JSON: Data is organized into key-value pairs, which are easy to map to objects or properties in most programming languages. This makes it easy to access and manipulate data programmatically.

  • XML: Data is organized in nested elements (tags) with attributes, which can introduce complexity, particularly in large datasets with multiple layers of nesting.

This straightforward approach to representing data makes JSON particularly attractive for developers looking for a simple yet effective format for structured data.

Smaller Payloads

One of the most significant advantages of JSON over XML is its compactness. JSON typically results in smaller message sizes compared to XML, and this has several benefits in terms of performance and efficiency.

Interoperability and Ease of Integration

As the airline industry, like many other industries, continues to evolve, interoperability is key. Systems need to communicate effectively across different platforms and applications, many of which may use different technologies or programming languages. Here’s how JSON benefits this aspect:

  • Cross-Language Compatibility: JSON is language-independent and can be easily integrated into various programming languages, including JavaScript, Python, Java, Ruby, and many others. Most modern programming languages offer native support for JSON parsing, making it an easy choice for developers.

  • Widely Adopted: JSON has become the de facto standard for data exchange in web services (APIs), cloud-based systems, and mobile apps. Its popularity in the tech industry has led to widespread support and tools to manage and process it efficiently.

The Role of JSON in the Airline Industry

In the airline industry, where real-time data exchange is essential, JSON has proven itself to be the preferred choice for data exchange. Its lightweight nature makes it well-suited to handle the enormous amounts of data generated by various airline systems, from reservations to flight schedules, baggage handling, and more. JSON enables these systems to communicate efficiently with each other and other stakeholders, including:

  • Airlines and Airports: Real-time data exchange for flight status, ticketing, and baggage tracking.

  • Air Traffic Control Systems: Data transmission for flight paths, schedules, and weather updates.

  • Mobile and Web Apps: JSON is commonly used in the development of apps that provide passengers with live updates, check-in, boarding, and tracking information.

Best Practices and Methodology for Transitioning from SOAP-based XML to RESTful JSON Services and APIs

The transition from SOAP-based XML services to RESTful JSON APIs is a significant step for organizations seeking to modernize their systems. SOAP (Simple Object Access Protocol) and REST (Representational State Transfer) are both web service protocols used to enable communication between client and server, but they differ considerably in design, complexity, and scalability. SOAP relies heavily on XML and is typically more rigid and verbose, while REST is lightweight, flexible, and uses JSON, which is easier to work with in modern web applications.

Adoption of RESTful JSON Service Standards in the Airline Industry

The airline industry, like many other sectors, is undergoing a digital transformation to meet the rising demand for more efficient, cost-effective, and customer-centric services. One of the key technological advancements in this transformation is the shift from traditional service-based architecture, such as SOAP with XML, to modern RESTful APIs that use JSON .

RESTful JSON services are quickly becoming the preferred standard in the airline industry due to their simplicity, scalability, and performance benefits. This shift is particularly critical for improving interoperability across various systems and enhancing customer service. Below is an in-depth exploration of why and how the adoption of RESTful JSON service standards is occurring in the airline industry.

How RESTful JSON is Being Implemented

Adoption of Industry Standards

The adoption of the Airline Industry Data Model (AIDM) is a key factor driving the shift toward RESTful JSON services. The AIDM provides a common language for data representation across the airline industry, ensuring consistency and interoperability.

  • AIDM and JSON Integration: Airlines that are part of industry groups like the ATSB are encouraged to use the AIDM along with RESTful APIs to standardize how data is exchanged between systems. This ensures that the data exchanged is consistent, reducing errors and improving overall system performance.

Industry Trends and Future Outlook

Semantic Interoperability

Current messaging (like EDIFACT, XML, NDC) is syntactic: systems know the structure but not the meaning.

Syntactic and semantic interoperability are two key layers of system integration. Syntactic interoperability ensures that systems can exchange data using a common structure or format, such as XML or JSON, but it does not guarantee that both systems understand the data the same way. In contrast, semantic interoperability goes a step further by enabling systems to interpret the meaning of the data consistently, using shared vocabularies or ontologies like RDF or OWL. While syntactic alignment enables communication, semantic interoperability is essential for intelligent automation, AI reasoning, and meaningful collaboration between systems—especially in complex domains like healthcare, aviation, or finance.

Aspect

Syntactic Interoperability

Semantic Interoperability

Aspect

Syntactic Interoperability

Semantic Interoperability

Definition

The ability of systems to exchange data using a common format

The ability of systems to interpret the meaning of exchanged data

Focus

Structure, format, protocols

Meaning, context, and shared understanding

Examples

XML, JSON, CSV, SOAP, REST, EDIFACT

RDF, OWL, JSON-LD, FHIR, http://schema.org , knowledge graphs

What it solves

Can the systems read each other’s data?

Can the systems understand what the data means?

Dependency

Requires agreed data structure/schema

Requires agreed ontology or vocabulary

Limitation

Misunderstandings possible if field meanings differ

More complex setup, but enables deeper automation and AI reasoning

Analogy

Speaking the same language (syntax)

Speaking the same language and meaning (context and intent)

Shift from Rigid Schemas to More Flexible Models

  • JSON > XML: JSON has become dominant for web and API communication due to its lightweight nature and ease of use.

  • Schema-less or Adaptive Models: With NoSQL and semi-structured data, schema-less databases allow for greater flexibility. Schema is often inferred or enforced at the application layer.

AI-Driven Schema Evolution and Mapping

  • LLMs (Large Language Models) can auto-generate or translate schemas.

  • Schema alignment and data transformation are becoming more intelligent, reducing the need for strict pre-alignment between systems.

  • Tools like Microsoft Synapse, Google Dataflow, or AI-based ETL platforms now do smart schema inference and automated mapping.

Blockchain and Smart Contracts

  • In decentralized systems, schemas are embedded in smart contracts or token standards (e.g., ERC-721 for NFTs).

  • These schemas are immutable and must be precise, making standards (e.g., OpenZeppelin libraries) essential.

  • JSON continues to dominate as the data format for blockchain APIs and wallets.

API-First and Event-Driven Architectures

  • OpenAPI/Swagger and AsyncAPI specs are now the norm for describing REST and event-based interactions.

  • These API specifications act like schemas, but with more behavioral metadata (e.g., endpoints, verbs, payloads).

  • They support automatic documentation, client generation, and mock servers.

Industry-Specific Schema Standardization

  • In aviation (IATA NDC/ONE Order), finance (ISO 20022), and healthcare (HL7/FHIR), standardized schemas still drive interoperability.

  • Future: These may be extended with machine-readable semantics and AI-ready tagging.

How OWL (Web Ontology Language) Can Shape Airline Messaging Standards

Emergence of Self-Describing Data & Semantic Interoperability

OWL (Web Ontology Language) enables the creation of ontologies. It can play a transformative role in modernizing airline messaging in several impactful ways. OWL helps computers understand the meaning of data, not just its structure. Technologies like RDF, OWL, and JSON-LD enable machines to understand not just structure but meaning (semantics). This is crucial for AI agents, smart contracts, and digital twins which require contextual understanding.

Dynamic, AI-Driven Interactions

OWL-defined ontologies empower AI systems to reason about passenger data and behavior. For example, recognizing a SpecialMealRequest as a dietary preference can drive personalized service recommendations and automation in customer interactions. When messages are semantically tagged, AI and automation tools can understand and act on them without custom logic.

Future-Proofing Messaging Standards

As airlines shift to event-driven, API-first, and AI-enabled ecosystems, traditional rigid schemas fall short. OWL-based ontologies can integrate with modern formats like JSON-LD and GraphQL, ensuring scalable, intelligent, and globally aligned messaging. When systems use OWL-based ontologies, the structure and semantics of messages are both understood. This leads to smarter message exchange, especially in complex workflows involving multiple systems.

Adoption of modern messaging standards

Significance of New Industry Messaging Standards Built in JSON for Modern Airline Retailing

The airline industry is currently undergoing a digital transformation, and modern airline retailing is at the heart of this change. Retailing in the airline context refers to the end-to-end process of selling and delivering travel-related services, including flight bookings, ancillary products, loyalty programs, and personalized offers. As airlines move towards more agile, data-driven, and customer-focused business models, the messaging standards used to exchange information play a critical role in ensuring efficiency, scalability, and adaptability.

In this context, the development of new industry messaging standards in JSON represents a significant step forward, enabling airlines to cater to the demands of modern travelers, streamline operations, and create a more flexible ecosystem for both suppliers and customers. Below, we delve into the reasons why building new industry messaging standards in JSON is essential for modern airline retailing.

Alignment with Modern Technology Stack

  • Digital-First Approach: In the current retailing landscape, airlines are increasingly having regards to digital channels for customer engagement, such as mobile apps, websites, and third-party platforms. JSON is the preferred data format in web technologies, as it is lightweight and well-supported by virtually all modern web development frameworks. By adopting JSON for industry messaging standards, airlines align their backend systems with a digital-first approach that customers expect.

  • Compatibility with Web APIs: RESTful APIs, which use JSON for data exchange, are at the core of modern application architectures. Airlines are shifting from legacy SOAP-based web services to RESTful APIs, which are more agile, scalable, and compatible with cloud-based technologies. JSON facilitates seamless communication between distributed services and applications, making it easier for airlines to integrate new retailing technologies like booking engines, pricing engines, and customer management systems.

Enhanced Interoperability Across Platforms

  • Cross-System Communication: The airline industry is comprised of numerous interconnected systems, from Global Distribution Systems (GDS) to Passenger Service Systems (PSS), ancillary services, and third-party partners. JSON provides a universal format for data exchange across these systems, ensuring that disparate technologies (whether old or new) can communicate effectively and consistently. This is particularly important in airline retailing, where airlines need to interact with multiple partners, including OTAs (Online Travel Agencies), suppliers, and airports.

  • Standardization Across the Industry: As airlines consider the adoption of new retailing models, which may include dynamic pricing, personalized offers, and cross-sell/up-sell strategies, they require standardized data formats to exchange offers, prices, and services efficiently. By adopting a universal messaging standard based on JSON, the industry can create consistent data models that enhance interoperability between the various players in the airline ecosystem. This can lead to faster product distribution, fewer errors, and a smoother customer experience.

Scalability and Performance

  • Faster Communication: One of the primary advantages of JSON is its lightweight structure compared to XML, which reduces the payload size for messages. This is especially critical in airline retailing, where time-sensitive operations and large volumes of transactions need to be processed quickly. Faster communication reduces latency, ensures real-time pricing and availability updates, and improves the overall performance of retailing systems.

  • Adaptable for High-Volume Transactions: Airline retailing platforms need to process millions of transactions per day, including flight bookings, baggage fees, seat upgrades, and loyalty rewards. JSON’s efficient data structure enables these high-volume operations to scale easily without overburdening systems or affecting performance. This is crucial for modern retailing, where airlines must handle peak traffic periods, such as holiday seasons or special promotions.

Improved Flexibility for Innovation

  • Easier Adaptation to Emerging Technologies: The airline industry is continuously innovating, with new technologies like artificial intelligence (AI), machine learning (ML), and blockchain becoming increasingly important. JSON, as a flexible and human-readable format, integrates seamlessly with these technologies, enabling airlines to leverage advanced analytics and provide personalized offerings to customers. Whether it’s using AI for dynamic pricing or blockchain for secure ticketing, a JSON-based messaging standard will ensure that these technologies can be integrated smoothly into airline retailing operations.

  • Enabling Real-Time Customization: In modern airline retailing, customers expect personalized offers and services that cater to their unique needs. JSON allows airlines to exchange data in real time, enabling the option of customized pricing, upselling opportunities, and tailored promotions based on customer data. For example, an airline can offer a personalized discount on baggage fees based on a customer’s previous travel behavior, loyalty program status, or even weather conditions. The flexibility of JSON-based messaging enables airlines to stay agile and adapt quickly to customer demands and market conditions.

Simplified Data Management and Maintenance

  • Easier Schema Evolution: As the airline industry evolves, new data models, business processes, and regulations will emerge. With JSON, changes to data structures (such as adding new fields or updating service offerings) are much easier to implement compared to XML. This is especially important in airline retailing, where new product offerings, pricing models, and partnerships frequently need to be integrated into the system. The flexibility of JSON enables airlines to evolve their data models in response to changing market dynamics without the risk of breaking the system or requiring complex schema changes.

  • Cost-Effective Development: Since JSON is simple, well-documented, and widely used across the tech industry, it reduces the time and cost associated with development, testing, and maintenance. Airlines can leverage existing tools and libraries, and developers can quickly onboard with little training. This makes it more cost-effective to build and maintain messaging standards for modern airline retailing, allowing airlines to allocate resources to other innovation areas, such as customer experience and operational efficiency.

Real-Time Data Exchange and Customer Experience

  • Real-Time Personalization: One of the major advantages of modern airline retailing is the ability to provide real-time personalized experiences. JSON supports this by enabling the quick exchange of data between various touchpoints, such as booking platforms, mobile apps, and check-in systems. For example, airlines can offer personalized promotions during the booking process based on a customer’s previous travel history or search behavior. The JSON-based messaging format allows these promotions to be delivered in real time, improving the customer experience and increasing conversion rates.

  • Simplified User Experience: Modern airline retailing often involves a complex set of services, including flight bookings, seat selections, baggage management, and loyalty programs. With JSON-based messaging standards, airlines can ensure that customers have a seamless experience across platforms. Whether a customer is using a mobile app, website, or interacting with an airline via voice assistants, JSON ensures the backend systems can work together smoothly to provide an intuitive, fast, and responsive user experience.

Integration with Emerging Trends

  • Artificial Intelligence and Predictive Analytics: With the increasing use of AI and ML, airlines are considering leveraging predictive analytics to manage inventories, and forecast demand. JSON, as a lightweight and easily consumable format, allows AI systems to quickly access and process large datasets to make real-time decisions. For instance, airlines can use predictive models to offer personalized discounts based on a customer’s likelihood to purchase.

  • Blockchain for Secure Transactions: Airlines are exploring blockchain to improve transparency, reduce fraud, and enhance the security of ticketing and loyalty programs. By adopting JSON as a messaging standard, airlines can ensure that blockchain-based transactions integrate smoothly with other systems, making it easier to manage secure, decentralized ticketing and payments.

Agentic AI and Airline Messaging Standards

Agentic AI refers to AI systems that act autonomously, not just generating text or predictions, but taking multi-step actions toward a goal

Current Limitations:

  • Each system speaks a different protocol (NDC, EDIFACT, internal APIs).

  • Context is lost between processes e.g., a passenger’s intent or disruption state isn’t carried seamlessly.

  • Orchestration is manual or rule-based, not adaptive.

  • Hard to make systems collaborate dynamically , everything is pre-coded.

Future Reality:

Airlines are moving toward:

  • API ecosystems (NDC)

  • Continuous offer management (real-time pricing)

  • Disruption automation

  • Personalized servicing

All of which require contextual, adaptive, multi-agent coordination exactly what Agentic AI enables.

Where Messaging Standards Fit In

IATA standards will remain the backbone, but they’ll shift from static message formats to semantic and contextual exchanges.

Current Standard Role

Future Role with Agentic AI

Current Standard Role

Future Role with Agentic AI

Define XML/JSON schemas