Lufthansa Technik Tackles MRO Systems Interoperability

Lufthansa Technik is doubling down on its digital strategy with a suite of software acquisitions aimed at solving one of the industry’s most persistent challenges: interoperability. Across the industry, several maintenance operations, job cards and repair orders are still recorded manually or in hybrid digital formats—a clear sign that the sector’s digital transformation is far from complete.

The company’s recent acquisitions of Swiss-AS AMOS and flydocs software, alongside its existing Aviatar platform, form the backbone of what it calls a “Digital Tech Ops Ecosystem.” The goal is to unify technical operations under a connected, data-driven framework.

“Our recent acquisitions … were driven by a clear strategic objective: to build a truly integrated and future-ready Digital Tech Ops Ecosystem,” a team of specialists at Lufthansa Technik (LHT) tell Aviation Week Network.

However, while consolidation is accelerating, many systems across the supply chain still operate in silos. Technicians often toggle between stand-alone digital tools and paper-based records, revealing a fragmented landscape where systems “don’t talk to each other.”

LHT says it is tackling this head-on with open interfaces and API-driven integration. “AMOS … features a robust interface architecture that supports real-time data exchange with third-party systems, including Aviatar and flydocs,” the team explains. “This ensures that the Digital Tech Ops Ecosystem is not just a collection of tools, but a connected network that delivers operational efficiency and data consistency.”

The suite is designed to be modular, allowing customers to adopt individual tools or the full stack. “Customers can adopt the complete suite for a fully integrated experience or select individual modules to address specific needs,” the team says. This flexibility is intended to accommodate varying levels of digital maturity across airlines, MROs and operators.

Concerns about vendor lock-in—where operators become dependent on a single provider—are addressed through what LHT calls a neutral architecture. “The Digital Tech Ops Ecosystem is built to avoid vendor lock-in. Its open, modular and neutral architecture ensures that customers remain in control of their choices,” the team adds.

The company also emphasizes compatibility with legacy systems. “All Digital Tech Ops Ecosystem solutions offer multiple interface options, supporting both standard industry protocols and custom integrations,” the team says. “This openness is designed to enable connections beyond the ecosystem itself—linking with customer and partner systems to unlock new efficiencies.”

One example LHT cites involves data from Aviatar’s Condition Monitoring or Technical Logbook applications being linked with AMOS maintenance records or flydocs’ asset documentation to “deliver faster decision-making and optimized maintenance planning.”

Still, the broader industry continues to wrestle with a digital divide. While LHT’s digital architecture offers a promising blueprint, many operators remain constrained by legacy infrastructure and disconnected systems. The path to seamless interoperability, even with consolidation, appears to be still under construction.