Skywise Knows: Why the Airbus Innovation Story Is Really a Data Story

SAP’s Airbus story is useful because it shifts attention from aircraft concepts to the enterprise systems underneath them. Airbus runs SAP S/4HANA, SAP Manufacturing Execution on its assembly lines, and SAP Integrated Business Planning across its supply chain. However, for aerospace and defense leaders, the real question is whether their own SAP landscape can carry clean, integrated, near-real-time data across engineering, manufacturing, supply chain, and asset operations the way Airbus’s does.

Standing before an SAP audience in Toulouse, Nicolas Jourdan, a senior strategist at Airbus SAS, framed that innovation as a habit rather than a department. “Without SAP, our systems would not be as efficient as they are,” he said. It is a tidy line, but it carries an operational truth. Airbus builds fuselages, wings, and tails across Europe, ships them on the oversized Beluga to a single assembly site, and it can take up to 12 months to complete a wide-body aircraft. None of that choreography works without integrated data underneath it.

Additionally, in aerospace, quality traceability, export control requirements, long program lifecycles, and engineering change orders make data quality part of the operating model rather than an IT housekeeping item.

The Digital Backbone Is Really a Data Backbone

For SAP ERP environments, integration is the connective tissue between planning, production, inventory, and execution. The weak points show up at system boundaries that matter to aerospace manufacturers. They include PLM-to-ERP, ERP-to-MES, and ERP-to-supplier and MRO systems.

Therefore, a digital thread loses value if it stops at each boundary and demands manual reconciliation, a form of spreadsheet archaeology with better branding. SAPinsider’s data illustrate the issue: respondents call deep integration between planning and operational execution critical, citing the need for cleansed and harmonized operational data and real-time inventory and ATP data.

For a tier-one supplier, reconciling a configuration change against a forward order book can cause integration gaps that ripple straight into delivery, quality, and exception management. While SAP S/4HANA brings MRP, advanced ATP, embedded analytics, and real-time production scheduling, the realized value depends on how integration and master data work are scoped.

Asset Visibility and the Engineering Handoff

Another weak point is the handoff from new product introduction into sustained production and aftermarket operations. SAPinsider’s EAM Report found that 65% of organizations prioritized end-to-end, near-real-time asset visibility. Another 64% were focused on consistent, high-quality asset-management data to gauge production and design risk.

Yet only 16% prioritized digital twin technologies to integrate NPI with asset management. That capability is what translates an engineering revision into tooling changes, maintenance plans, and spares forecasts without manual reconciliation. Airbus offers a proof point: its Skywise platform pulls together aircraft, operations, and maintenance data into a single system and runs AI-supported predictive maintenance to catch failures before they ground an aircraft.

When that loop is not closed inside the SAP ERP estate, predictive maintenance and reliability engineering use cases stall. The same EAM research found that respondents wanted to predict asset downtime and breakdowns that could disrupt production or the supply chain, and needed real-time asset insights to reduce risk. Those use cases depend on telemetry, asset history, and operational data being trusted enough to drive action. And the foundation matters more than the ambition: Airbus did not bolt Skywise onto chaos; it built on a connected SAP core first.

What This Means for SAPinsiders

Map the integration estate before the AI roadmap. The Airbus story is a benchmark for integration, not evidence that most aerospace organizations have reached it. Aerospace organizations should inventory their PLM-to-ERP-to-MES connections against quality and export-control obligations, because in aerospace, the compliance perimeter shapes migration timing and scope. SAPinsiders should, therefore, treat every manual reconciliation point between PLM, ERP, MES, and MRO as a defect to be retired on a schedule rather than a permanent fixture.

Sequence AI behind master data and integration. Predictive maintenance and reliability use cases sit downstream of master data and integration remediation, not ahead of them, and ambition applied to fragmented data produces stalled pilots. CIOs should fund the foundation first, then let digital-twin use cases that are not often prioritized become the differentiator rather than a bottleneck.

Target the NPI-to-asset-management loop, because that is where demand outruns capability. SAPinsider evidence points to the new-product-introduction handoff and supplier data harmonization as the areas with the widest gap between practitioner demand and delivered capability. Organizations must build offerings around closing that loop inside the SAP estate, from configuration change through tooling, maintenance plans, and spares forecasting, and anchor them to a named outcome like Airbus’s Skywise.