Boeing has begun discussions with engine manufacturers about joining Dataliner, its new artificial-intelligence platform, in an effort to connect aircraft and engine information that airlines often examine separately. No engine manufacturer has been named, and no participation agreement has been announced.
Chris Raymond, president and chief executive of Boeing Global Services, outlined the idea at MRO Europe in Amsterdam on October 27. Combining the two sets of information could help airlines understand aircraft reliability and anticipate maintenance requirements, he said.
“We have a lot of information on the performance of our aircraft, and so that integrated performance between the engine and the aircraft, I think, is really what operations need to feed on,” Raymond said. “I can see them being partners in Dataliner, and we’ve already had a couple of discussions like that.”
The proposal addresses a practical divide in maintenance. An aircraft’s operating history, maintenance records and technical instructions provide one view of its condition. Engine information adds another. Boeing wants to bring those views closer together so an airline can examine patterns across its fleet rather than respond only to alerts from individual aircraft.
It is the digital equivalent of getting specialists around the same workbench. Each may hold information relevant to the fault, but the value lies in connecting it to the maintenance decision, not simply collecting more readings.
Boeing launched Dataliner on October 20. Built with Microsoft’s Azure AI Foundry, Microsoft data services and other technologies, it is intended to connect aircraft-condition information, maintenance history and operational data with Boeing’s engineering knowledge. Airlines would access the resulting intelligence through applications, analytics, software interfaces and AI-enabled tools.
The architecture does not require an airline to transfer all its records into a single manufacturer-controlled repository. Boeing says operators can retain data in their own environments and decide what information to share. Access controls, encryption and permissions are intended to protect sensitive records.
“Most people want to keep their data; they don’t want to send it all to somebody else,” Raymond said. “They actually want to decide what kind of permissions they grant for this data.”
Those permissions will matter if engine manufacturers participate. Boeing has described airline control over sharing, but has not published prospective engine-partner terms, the engine parameters that would become available or the information airlines would be entitled to access. The discussions do not yet establish a common data agreement across manufacturers.
Dataliner also provides a foundation for Boeing’s existing digital services, including Airplane Health Management, Insight Accelerator and Maintenance Performance Toolbox. Raymond said Boeing had launched a TechOps AI agent and an asset-lifecycle planning tool on the platform. The company intends to connect with airlines’ third-party maintenance applications through software interfaces.
The longer-term ambition reaches beyond diagnosis. Boeing wants to link maintenance information with parts usage and distribution, modifications and safety information. A warning about an emerging technical problem would be more useful if the maintenance team could connect it with the required work, available components and an opportunity to perform the task.
“Our shared mission is to have their fleet flying,” Raymond said. “The real power is going to be when we integrate that data with our parts and distribution data and usage data.”
The promised outcome is greater aircraft availability, but Boeing’s launch announcement and Raymond’s remarks do not provide a measured airline example showing reduced downtime attributable to Dataliner. Neither gives a before-and-after result, a false-alert rate or a quantified reduction in unscheduled maintenance.
The platform has been launched and the engine-maker discussions have begun. The next substantive milestone would be a named operational deployment showing which information was combined, what action followed and whether the aircraft returned to or remained in service more reliably.