See how the Airbus A380 wiring delays show why a product designed across several sites needs a single controlled definition of its interfaces and design data, and control over how they change.
In hardware development, teams often split work across sites, partners, suppliers, and tools. Each team owns its part of the design, while the interfaces between those parts are often assumed rather than defined.
The Airbus A380 case shows why a product designed across several sites needs a single, controlled definition of its interfaces and design data, along with change control that reaches every team. On the A380, the electrical harnesses for the forward and aft fuselage did not match the actual aircraft.
The first delivery was planned for 2006, but Airbus announced delays in June 2005, June 2006, and October 2006, and the actual delivery slipped to October 15, 2007.
In this article, we take a closer look at the origins of this delay and the transferable lessons engineers can learn that apply to their projects.
The A380's design was spread across 16 sites in 4 countries, and Airbus became a single integrated company only in 2001. Each aircraft carries more than 100,000 wires and 40,300 connectors, performing 1,150 wiring functions, according to a Calleam case study.
The root cause was the wiring. In Airbus's own account, harness design for the forward and aft fuselage could not keep pace with the rest of the aircraft, and the designed harness routing did not match the actual aircraft configuration.
Airbus cited incompatible concurrent engineering tools across sites and a late implementation of a 3D digital mock-up (DMU) for harness installation. At the time, reports indicated that the German and Spanish sites used CATIA V4, while the French and British sites used CATIA V5, and data did not transfer faithfully between them.
Every decision likely seemed reasonable at the time. The sites had proven their tools in their own work, had long histories as semi-independent partners, and migrating a toolchain mid-program carries its own cost and schedule risk.
Viewed from a requirements engineering lens, the harness-to-structure interface lacked a controlled definition used by every site, and changes didn't reliably reach every affected design. Contributing factors included production starting before the design was finalized, cabin customization for each airline that multiplied harness variants, and an organization still integrating its national sites.
Most hardware teams don't build aircraft, but many split a design among a partner, a supplier, a second site, or two CAD versions. A harness defined in a spreadsheet, a connector pinout sent by email, or a board outline exported to another tool creates the same interface problem at a smaller scale.
Best practice: Treat each interface that crosses a boundary as a requirement.
For a harness, that means the elements that cross the harness-to-structure boundary: routing zones, attachment points, connector positions, and mounting envelopes. Keep it in a shared environment that every team member can access, and assign an owner to approve changes. This way, every site designs against the same interface data, so mismatches surface during review.
Best practice: Treat tool and format compatibility as a requirement of the project.
At kickoff, send a pilot model or a part from an earlier project from each team to the other team and open it in their tool. Verify that geometry, lengths, and attributes survive the round trip, then repeat the test with the first real design data.
Best practice: When an interface changes, run a change impact analysis.
List the designs that depend on the change and notify their owners. Verify that each design is updated before you close the change order. Small changes are often skipped because each seems too minor for a formal review. On the A380, hundreds of small wiring changes added up to a redesign.
The A380 had more than 100,000 wires, but the same pattern appears when two engineers use different CAD versions or a supplier uses another tool. Ask these questions about your own project:
Every interface that crosses a boundary needs one controlled definition, and every change to it needs to reach the teams that depend on it.
A connected workflow keeps interface requirements, their owners, and linked designs in a single shared place, so changes show which designs they affect across teams, sites, and suppliers.
With Requirements Portal, teams can write interface requirements in a shared workspace and assign an owner to each. They can then link each requirement to designs and V&V activities. When a requirement changes, the links show which designs and V&V activities are affected, so the owner knows who needs to update.
For teams that work across ECAD tools today, the Altium 365 Workspace can accept and interpret designs from popular tools, including Altium Designer, OrCAD, KiCad, and EAGLE.
With MCAD CoDesigner, ECAD and MCAD changes flow through the Workspace, and it supports harness projects, enabling electrical and mechanical teams using different tools to exchange design changes.
If you want more lessons from real hardware cases, these articles cover other requirements management failures and what you can learn from them:
The electrical harnesses designed for the forward and aft fuselage did not match the actual aircraft. Airbus said its concurrent engineering tools were incompatible across sites and that the 3D digital mock-up for harness installation arrived late. At the time, reports indicated that sites used different CATIA versions.
An interface requirement defines what crosses the boundary between two parts of a design, such as routing zones, attachment points, connector positions and pinouts, or a mounting envelope. Each side builds to that requirement, often without seeing the other side's design.
Teams can keep requirements and designs in a shared workspace with change history. At kickoff, verify that design files convert correctly between tools, and again when the first real design data is available. Linking interface requirements to the designs that depend on them ensures every change reaches the design owners it affects.