Airbus PLM: data archeology & death by obsolescence

Airbus PLM: data archeology & death by obsolescence


Almost 10 years ago, Gartner defined IT obsolescence management as major emerging issue. Here is a passage from old the old article about that:

By year-end 2010, more than one-third of all application projects will be driven by the need to deal with technology or skills obsolescence.  “Our research with thousands of clients across multiple geographic locations and industries shows that most CIOs are struggling to cope with a set of portfolios in which an overwhelming percentage of the artifacts need to be retired and replaced within a comparatively short period of time — between 2008 and 2015,” said Dale Vecchio, research vice president at Gartner.  “The scale of obsolescence in the set of portfolios is a major problem in its own right, but it is compounded by the lack of integrated planning capability within many IT management teams.

And if you think about main contributing factors, such as lack of agility of IT systems and services in responding to business requests, increasing demand for integration and aging of deployed assets you can see why obsolescence is a huge issue for manufacturing companies. The amount of old enterprise PLM software assets is increasing. Think about all major PLM software providers – all PLM platforms were originally developed more than 10 years ago.

The problem of obsolescence in PLM software is hitting large companies – those companies invested large amount of resources in PLM development for the last 1-2 decades. article Boeing, Airbus and the Hardship of Dealing with PLM Obsolescence –TV Report gives you an interesting perspective on the level of complexity in PLM obsolescence in major commercial aircraft OEMs – Airbus and Boeing. Large manufacturing organization are actively looking for a formula how to maintain existing environment and at the same time get access to new development, technologies and projects. And this is a place with lot of conflicts and very costly mistakes for the future development.

The dream situation is explained by CIMdata’s Peter Bilello: “A key question is how these industrial organizations can cost-effectively move to newer technological capabilities. Have they installed and developed a PLM environment that can be upgraded reasonably quickly, at a reasonable cost and ensure that the data can come forward as well?”

As much as it sounds simple the problem is crazy complex. Participants of Verdi Ogewell’s TV report highlighted some of the elements that in their view can solve the problem – standards, data-driven approach and layers. The last one seems like a strategy for Airbus. Here is an interesting quote by Airbus’ Anders Romare:

So interoperability and openness are key, and Airbus’ Anders Romare is clear about the strategy they have to meet the harmonization requirements on the one hand, and the need to integrate new technologies on the other. “We try to work on two dimensions,” he said, adding that, “For the core PLM backbone, yes, we need still to harmonize across the company. It’s important to have one single backbone harmonized across the company. Then we try to build on top of those backbones, more agile layers where we can have faster development, faster cycles.” Basically, Airbus uses PTC’s Windchill as its PDM backbone, Aras PLM for supplier collaboration and Dassault Systèmes’ CATIA for CAD. SAP is the solution on the ERP side (MES, Manufacturing Execution Systems).

I found both passages very much conflicting. If the desire of IT organization to find an architecture to support an easy upgrade and data migration, then to build horizontal layers is probably a mistake. As much as it seems like a way to unblock Airbus IT organization to develop new agile solutions, the architecture is fundamentally wrong and will lock Airbus product data even more in the future. Both layers are build on existing PLM backbones – PTC Windchill and Aras Innovator.  Aras was developed a decade later after Windchill and has some interesting technological elements such as open XML driven data model schema. But from fundamental architecture perspective both systems are perfect examples of monolithic PLM backbones that will have similar trajectory of development and obsolescence. While standards like PLCS and JT are very promising to make point-to-point integration easier, they will be helpless to solve a problem of two aging product layers in the future. In the future, so called “stable layer” will become a dead layer. And PLM architects will have to take lessons in data archeology to learn how to get product data and reuse it for new applications.

What is my conclusion? Obsolescence is a big problem in PLM. While all PLM systems are old, to solve a problem by combination of older and newer application can be a dead end. Agile product development layer on top of existing “stable” model is a temporary patch that will solve a problem for few years or maybe a decade. Airbus and Boeing are talking about 50-100 years of data lifecycle, so 10 years is a very short period of time. By creating layers of relational data models and application Airbus, Boeing and other manufacturing companies potentially can create even a bigger problem in the future. A new agile facade of data layers will not solve a problem of old data spaghetti called “stable data”. To solve a problem there is a need to change data architecture. There is no silver bullet solution. However, to move away from traditional horizontal layers to micro-service architecture and vertical components can be one of the first steps in the future. Just my thoughts…

Best, Oleg

Want to learn more about PLM? Check out my new PLM Book website.

Disclaimer: I’m co-founder and CEO of openBoM developing cloud based bill of materials and inventory management tool for manufacturing companies, hardware startups and supply chain. My opinion can be unintentionally biased.

Image credit – USB Typewriter Computer Keyboard Underwood Model F c. 1930s


Share This Post

  • Pingback: GHZ Partners | IT Services, Software()

  • marclind

    Oleg, thanks for covering this. Seems like a little fact check needed on musings.

    “Monolithic” describes a major problem we’ve set out to solve at Aras.

    Whole point of ‘interesting technological elements such as open XML driven data model schema’ combined with our loosely coupled, federated services is to enable fast customization and integration while retaining continuous upgradability… not sure how that could get lost / forgotten after all these years?!?

    Agile PLM layer (i.e. Aras) over “stable” legacy PDM is for speed today. That way can gain rapid benefits now… and retire legacy whenever ready… rip & replace doesn’t have to be prerequisite for strategic benefit… it can happen anytime.

    Implement a single service, like workflow – just one process, like enterprise change – or whole end-to-end application suite… just what you need, when needed; that’s our approach.

    And w/ Aras you upgrade all the time – even when continuing to customize as constantly improving processes – which eliminates Obsolescence.

    Agree w/ all your points… right up until we/Aras was misrepresented and lumped in w/ monolithic Wc!

    Just thought some clarification was in order 🙂


  • beyondplm


    Thanks for your comment!

    gradual replacement is probably the only possible strategy for project scale like Airbus. And I agree Aras has advantages as newer system comparing to Windchill and some other “mature” PLM systems. However, Airbus didn’t presented it in that way, in my view. It was presented as a strategy to have 2 levels – mode1 and mode2 according to Gartner definition of Bi-modal IT. And it doesn’t say anything about replacement. But I see your point and interest of Aras eventually to replace Windchill.

    Monolithic is funny word :). Especially if we take a marketing spin on what is monolithic and what is not. I will try to stick with technical terms. Let me thing about it. I’m sure will come with another blog, so we will have an opportunity to debate and find what is “true monolithic” vs “true agile”… right?

    Thanks, Oleg

  • marclind

    Yes, for sure. Think we can have fun debating with monolithic and agile, especially since seems most people are still trying to figure out implications

  • Pingback: Beyond PLM (Product Lifecycle Management) Blog Next PLM marketing battle - monolithic system - Beyond PLM (Product Lifecycle Management) Blog()

  • beyondplm

    Here you go Marc, look forward for your comments!

    Next PLM marketing battle will be about “monolithic” systems.

  • Loic M

    Hi Oleg,
    )I disagree that PLCS is promising for point to point integration. To my opinion, this norm is far too abstract to be easily/widely implemented.
    Indeed, I participated few years ago to the implementation a Proof-of concept for data exchange between companies of the european aerospace industrie. It was initially specified to used this STEP AP239 (PLCS) for the description of Technical Data Package (exchange data), but it is oversize for “simple” exchanges. No user is able to read the file without the help of relative complex. As a result, you cannot really improve simple use cases per iteration. The implementation need to be done by specialists (of this norm). How many are they in the world? => the use of this norm was abandon for a simpler XML structure.

    Standard like JT is really interesting for storing and exchanging scenario. Daimler choosed to use it few years ago.

    I’m quite surprise you do not mention the LOTAR initiative about this thematic. (see

  • beyondplm

    Loic, thanks for your comments! I agree PLCS is not an idea, but could be a starting point for future improvements.

    Also thank you for mentioning LOTAR. I think it is important piece of technology, but it is slightly outside of the topic which was mostly focused on bi-modal PLM concept.

  • Pingback: Beyond PLM (Product Lifecycle Management) Blog Aras PLM Platform - All or Nothing? - Beyond PLM (Product Lifecycle Management) Blog()