The number of people traveling by air continues to climb, but with per-seat margins under pressure, airlines are looking for new ways to grow profitably. That includes offering unique passenger experiences that build loyalty and generate revenue while optimizing operations both on the ground and in the air.
In my conversations with airlines across the globe, I see three critical factors:
IT systems within an airline evolve at a varying pace and in silos. On one side you have digital boarding passes, and on the other loyalty points take 72 hours to show up in your flyer’s account. This incongruence arises due to the difficulty these systems have in sharing information in general – much less in real-time.
Information held by System A needs to be requested by System B. Picture the Baggage application querying the Air Operations application every few minutes to check if a specific flight has landed. This exact information is also crucial for the ground crew. Unsurprisingly, the Ground Operations systems will also need to periodically query the Air Operations system for the exact same information – has that flight landed yet?
This kind of bespoke information sharing architecture is inflexible, cannot scale, and is very expensive to maintain. The resulting silos inhibit the scale at which systems can discover and respond to key events in the airline ecosystem.
If key events are available to multiple systems, across teams, right when they occur, the opportunity to respond to them is much higher and can unlock immense value. Think of this as a ripple that is triggered by an important business event.
Let’s take the example of a boarding pass scanned at the boarding gate. This event – boarding pass scanned – is not tied to any one system. It occurs and is now available to all systems at the same time. Applications that need to respond to it can make use of it, and others don’t consume it.
This creates new possibilities for customer experience and operational efficiencies. Let’s look at one series of actions more closely:
The occurrence of one event – “Updated BOARDING COMPLETED time” – triggers three systems to respond and help the airline:
Over the years, airlines have gathered an immense amount of data on customer needs and preferences, as well as on air and ground operations. Kudos to the airlines for building out procedures and infrastructure to collect and store all this information. However, what we most commonly hear from airlines is “I can tell you in detail what happened yesterday, but I don’t know what is happening right now. Even if I know what’s happening now, I can’t respond to it in real-time.” Sound familiar?
Let’s go back to the “Updated BOARDING COMPLETED time” event. As Customer Service works on alternative itineraries, how do they know which customers to prioritize? Is there a 1 Million Mile passenger on-board? Is there a family of four that booked their rental car and hotel through your airline? Can you notify these passengers – directly or through the flight crew – that you are on it and delight them in the process?
It’s evident here that this request will touch a multitude of systems – Customer Service, Ticketing, Loyalty, mobile apps. Some events like “high-value client” could be generated months before the event “Updated BOARDING COMPLETED time”, but by being able to get that information in motion and liberated from a specific system, the overall responsiveness of the system is enhanced and silos are broken down.
Let’s look at some common interactions between an airline’s systems:
The data flow here is tightly-coupled, point-to-point, and systems are not able to share key information more broadly or in real-time without changing the source systems or polling more systems. Point to point integrations are inflexible and just don’t scale for real-time responsiveness.
What’s needed is a method to bring all events to a common plane and – in a governed way – let systems choose which events and information streams are essential for them. This is embodied in what Gartner calls an event mesh.
An event mesh makes it possible to dynamically stream the same event in real-time to multiple systems in different locations – on prem, in a public or private cloud, or in a hybrid scenario. The event mesh can filter the stream so each system only receives what’s useful to them, e.g., “boarding pass scanned” is essential to Air Ops for predictive analytics but is likely not a valuable event for Marketing.
That common refrain from airlines about knowing what happened yesterday or even a decade ago, but not about what’s happening right now, sums up the challenges with systems that live in silos.
An event mesh powered and governed by Solace PubSub+ Platform not only guarantees the delivery of data to the interested consumer apps, but lets you integrate legacy and “bursty” batch-based systems with modern event-driven systems. You can put static data into motion and share it with your entire ecosystem, unlocking its value and letting you leverage it to launch innovative new services that enhance customer experience and improve operational efficiency, all without the risk of impacting existing systems.
PubSub+ is extensively deployed in mission-critical use cases in the aviation industry, specifically serving as the data distribution backbone for some of the world’s biggest air navigation service providers. In addition to supporting a variety of message/data sharing patterns like pub/sub, streaming, etc., it now comes with an event portal that helps you govern, discover and manage events across your ecosystem. You can view, design, manage and govern all your event data and integrate with enterprise data lineage and search tools.
Imagine the innovation and positive impact to your business that could be enabled by having real-time access to the key business events processed anywhere in your IT landscape. The possibilities are endless! All this is possible by event enabling your systems on an event mesh.
Shawn McAllister is responsible for the strategy and delivery of the Solace PubSub+ Event Streaming and Management Platform. He leads a team of incredibly talented engineers and architects in this endeavor.
McAllister has worked with many of our clients to help them adopt an event-driven architecture and to learn first-hand their needs as input to the innovation built into the PubSub+ Platform. He has participated in the definition of various OASIS messaging protocol standards, including MQTT 3.1.1, MQTT 5.0, and AMQP1.0.
Before joining Solace, McAllister led software, hardware, and test engineering teams at Newbridge Networks (later Alcatel Canada), where he was responsible for developing features on ATM and Ethernet switches as well as the 7750 Multiservice IP Router.
McAllister holds a Bachelor of Mathematics from the University of Waterloo, with majors in both Computer Science and Combinatorics/Optimization.[position] => Chief Technology Officer & Chief Product Officer [url] => https://solace.com/blog/author/shawnmcallister/ ) )