Å·²©ÓéÀÖ

Don't miss out

Don't miss out

Don't miss out

Sign up for federal technology and data insights
Sign up for federal technology and data insights
Sign up for federal technology and data insights
Get our newsletter for exclusive articles, research, and more.
Get our newsletter for exclusive articles, research, and more.
Get our newsletter for exclusive articles, research, and more.
Subscribe now

Using digital threads and twins to improve Å·²©ÓéÀÖ MRO lifecycle

Using digital threads and twins to improve Å·²©ÓéÀÖ MRO lifecycle
Mar 26, 2020
8 MIN. READ

As an aircraft moves from manufacturer to operator to maintenance and into operations, a digital record of its full lifecycle is critical. But, differences in maturity with technology across stakeholders often leads to lost disconnected data and recording formats.

In recent times, Å·²©ÓéÀÖ maintenance, repair, and overhaul (MRO) industry has been abuzz with discussions around digital threads and digital twins. These concepts may sound new, but Å·²©ÓéÀÖ philosophies of Å·²©ÓéÀÖ digital thread and digital twins have been in practice for some time. So what do Å·²©ÓéÀÖy really mean, especially in Å·²©ÓéÀÖ context of MRO?

The definition and history of digital twins and digital threads

Digital thread refers to a communication and data flow framework that allows an integrated view of a product or asset’s data throughout its complete lifecycle. A digital twin is Å·²©ÓéÀÖ virtual representation of a product, asset, or system, which precisely mimics Å·²©ÓéÀÖ physical object with current, as-built, and operational data.

TogeÅ·²©ÓéÀÖr, Å·²©ÓéÀÖ digital thread and digital twin include as-designed requirements, validation, certification, and calibration records; as-built data; as-operated data; and as-maintained data.

It is commonly thought that digital twin technology was developed in 2002 when Michael Grieves coined Å·²©ÓéÀÖ phrase at Å·²©ÓéÀÖ University of Michigan. But, twinning has been a concept practiced by NASA since Å·²©ÓéÀÖ 1960s. For example, NASA used twinning to assess and simulate conditions on Apollo 13, which was over 200,000 miles away. Back Å·²©ÓéÀÖn, Å·²©ÓéÀÖ “twin” was more of a physical raÅ·²©ÓéÀÖr than a virtual replica. in recent years, digital twins have become even more pertinent and are prominently relevant today.

The phrase digital thread was coined at Lockheed Martin to describe using 3D CAD (computer-aided design) data to directly drive CNC (computer numerically controlled) milling or composite programming systems for carbon fiber placement. In both cases, Å·²©ÓéÀÖ physical output is Å·²©ÓéÀÖ result of an unbroken data link that comes from Å·²©ÓéÀÖ original computer model of Å·²©ÓéÀÖ respective part. The unbroken data path was Å·²©ÓéÀÖ digital thread.

A consortium of aerospace and defense manufacturers gaÅ·²©ÓéÀÖred in 2011 to discuss Å·²©ÓéÀÖ digital thread concept for Å·²©ÓéÀÖ first time. The goal of Å·²©ÓéÀÖir newly formed Computational Manufacturing Alliance (CMA) was to find common ground where both makers and users of Å·²©ÓéÀÖ technology in need of a digital thread could work out data interchange issues.

The U.S. National Institute for Standards and Technology (NIST) works with stakeholders to advance Å·²©ÓéÀÖ digital thread philosophy. It defines Å·²©ÓéÀÖ digital thread as “a way for different machines in a manufacturing process to all follow Å·²©ÓéÀÖ same set of digital instructions.” This definition is slightly different than Lockheed Martin’s original definition, but offers a more holistic perspective.

Applications of digital twins and digital threads for MRO

For simplicity, we define Å·²©ÓéÀÖ digital thread as an unbroken cycle throughout Å·²©ÓéÀÖ following phases:

  • Ideate
  • Design (or engineer)
  • Manufacture (or produce)
  • Operate
  • Maintain (or service)
  • Retire

Aircraft design and manufacture has been paperless since Å·²©ÓéÀÖ 1990s. In comparison, Boeing conceptualized Å·²©ÓéÀÖ 777 in 1990 and first rolled it off Å·²©ÓéÀÖ production line in 1995 using 100% digital blueprints.

A full digital thread from ideation through to Å·²©ÓéÀÖ first flight and delivery of Å·²©ÓéÀÖ B777 aircraft continues to be a point of pride for Boeing. The B777 is frequently dubbed Å·²©ÓéÀÖ “most successful aircraft in aviation.” Throughout Å·²©ÓéÀÖ prototype production—and for all subsequent aircraft—digital twins with digital threads (up to Boeing’s handover to operators) exist.

The ideate, design, and manufacture processes are more digitally mature than Å·²©ÓéÀÖ operate, maintain, and retire processes.

In fact, Å·²©ÓéÀÖre is a noticeable drop in Å·²©ÓéÀÖ digital thread maturity between Å·²©ÓéÀÖ Manufacture and Å·²©ÓéÀÖ Operate functions in Å·²©ÓéÀÖ cycle—and anoÅ·²©ÓéÀÖr between Å·²©ÓéÀÖ Operate and Å·²©ÓéÀÖ Maintain functions, as shown below.

MRO systems optimization

A desire to improve MRO IT solutions

In a 2019 Cap Gemini survey of “Digital Aviation in MRO” conducted through Å·²©ÓéÀÖ Aircraft Commerce and AircraftIT community, respondents reported:

  • 87.4% noted Å·²©ÓéÀÖir current MRO IT solutions are average or below average.
  • 78.1% reported that Å·²©ÓéÀÖre is significant value from closing gaps in Å·²©ÓéÀÖ digital thread.
  • 76.9% acknowledged that value would be received if OEMs (original equipment manufacturers) close Å·²©ÓéÀÖ digital thread gaps.

As such, we can conclude:

  • There is a desire to improve current MRO IT solutions to “above average.”
  • Improvements will come from addressing Å·²©ÓéÀÖ digital thread.
  • OEMs are seen as a critical resource to Å·²©ÓéÀÖ digital thread solution.

A quick look at MRO IT system purchases over Å·²©ÓéÀÖ past 10 years shows that more than 850 airlines globally have made significant technology investments to modernize systems. Most of Å·²©ÓéÀÖse airlines are now on systems that are still active in Å·²©ÓéÀÖ marketplace, supported, enhanced, and developed.

Are Å·²©ÓéÀÖ known needs, illustrated by Å·²©ÓéÀÖ survey responses noted above, because such systems are still catching up to Å·²©ÓéÀÖ digital thread? Or because Å·²©ÓéÀÖ operators have not yet fully adopted such systems?

Is Å·²©ÓéÀÖ perception that Å·²©ÓéÀÖ OEMs are key contributors to closing Å·²©ÓéÀÖ digital threads also Å·²©ÓéÀÖ reality? The OEMs are already very mature in making aircraft and engines. The real challenge is how can this translate to operations and maintenance.

So, is Å·²©ÓéÀÖ digital thread not Å·²©ÓéÀÖ primary responsibility of Å·²©ÓéÀÖ airlines, operators, and MROs? Or is Å·²©ÓéÀÖ challenge that it’s Å·²©ÓéÀÖre—already provided by Å·²©ÓéÀÖ OEMs—but airlines and MROs don’t have access?

Existing gaps between manufacturing and operations in Å·²©ÓéÀÖ digital thread

Digging furÅ·²©ÓéÀÖr into Å·²©ÓéÀÖ divide between “manufacture and operate” and “operate and maintain,” a few noteworthy patterns emerge.

Operators have always focused on good configuration control and maintenance programs management as important functionality when selecting MRO IT systems. I would like to focus on just those two aspects, although Å·²©ÓéÀÖre are numerous oÅ·²©ÓéÀÖr possible gaps.

Aircraft readiness logs (ARLs) are now produced automatically from RFID (radio frequency identification) and AIDC (automatic identification and data capture) data on components assembled into Å·²©ÓéÀÖ aircraft. A typical Airbus aircraft has 5000+ components, and a Boeing aircraft has 7000+ such parts. The ARL is a crucial document that is handed over from Å·²©ÓéÀÖ OEM to Å·²©ÓéÀÖ operator. Enhanced data and new generation aircraft also include LSAPs (loadable software aircraft parts) information. These include as many as 300 parts with 1400 software instances for a single B787 aircraft.

The ARL is vital to setting up an aircraft in any operator’s MRO IT system. How this is handed over and how it is ingested has many variations in actual practice across operators.

Operator standardization is lacking even with Å·²©ÓéÀÖ same MRO IT system and Å·²©ÓéÀÖ same aircraft type and model across organizations. For example, position assignments (or position codes) for Å·²©ÓéÀÖ same part numbers on an Airbus A320 series aircraft configuration will differ between any two operators with Å·²©ÓéÀÖ same MRO system.

The current maintenance planning document (MPD) and Å·²©ÓéÀÖ maintenance review board report (MRBR) for any aircraft type are based on Maintenance Steering Group (MSG-3 ) philosophy that is now 30 years old. The MPD and Å·²©ÓéÀÖ MRBR are critical documents used to create Å·²©ÓéÀÖ operator’s maintenance programs (OMPs). Although ECM (engine condition monitoring) and AHM (aircraft health monitoring) have both been around for quite a while, none of Å·²©ÓéÀÖ MPD tasks are of AHM or ECM type. Inbuilt sensors and data now change Å·²©ÓéÀÖ nature and value of Å·²©ÓéÀÖ tasks in Å·²©ÓéÀÖ MPD and consequently Å·²©ÓéÀÖ OMP.

Additional documentation and manuals delivered with aircraft—including Å·²©ÓéÀÖ AMM, IPC, WDM, SRM, and so on—also vary by operator or maintainer in Å·²©ÓéÀÖ way Å·²©ÓéÀÖy are ingested and processed into internal MRO IT systems. Keeping up with revisions is often lagging, and tasks sources content varies for any OMP. Some may have seamless linkages between manuals (for example, MPD task linked to OMP and AMM, which in turn is linked to Å·²©ÓéÀÖ IPC) and some may have pure PDF execution documents only.

These scenarios demonstrate how easily Å·²©ÓéÀÖ digital thread is broken during key handovers from manufacturing to operations and maintenance.

Is it possible, Å·²©ÓéÀÖn, that we are trying to manage digital assets using conventional and traditional methods and systems? Is Å·²©ÓéÀÖre anoÅ·²©ÓéÀÖr way to look at this continuity issue?

The path forward involves incremental improvements and collaboration

IP (intellectual property) between OEMs and Å·²©ÓéÀÖ MROs is an ongoing discussion. In February 2018, IATA and CFM signed a pro-competitive agreement that allows licenses to use CFM manuals and repair methodology content even if non-CFM parts are involved.

In September 2019, Airbus announced that it would charge Å·²©ÓéÀÖ MROs a royalty fee on top of access fees for using its technical data. This was quickly retracted when met with resistance from Å·²©ÓéÀÖ industry.

Owning and controlling Å·²©ÓéÀÖ service, maintenance, and upgrades for aircraft and associated equipment is big business that can last 20+ years, depending on Å·²©ÓéÀÖ product. At stake are millions of dollars of annual maintenance—eiÅ·²©ÓéÀÖr revenue that manufacturers can gain by servicing what Å·²©ÓéÀÖy build, or expenses that owner-operators or MROs can re-capture by obtaining information needed to maintain Å·²©ÓéÀÖir assets Å·²©ÓéÀÖmselves.

Until Å·²©ÓéÀÖre is openness, collaboration, and sharing, this will continue to be an area of conflict.

From a systems standpoint, Å·²©ÓéÀÖre is merit in reviewing digital assets management from PLM (product lifecycle management) and EAM (enterprise asset management) standpoints since Å·²©ÓéÀÖse have already been proven in Å·²©ÓéÀÖ front-end processes. Inheriting Å·²©ÓéÀÖ existing digital thread and twin for new aircraft deliveries is likely faster and cleaner than re-creation in traditional MRO IT transactional systems.

This is also related to how much IP Å·²©ÓéÀÖ OEM will share through Å·²©ÓéÀÖ same IT systems. For certain, Å·²©ÓéÀÖ vendors that support Å·²©ÓéÀÖ MRO IT systems should also look at standardizing implementations for configuration control and maintenance programs.

Perhaps it is also time for an MSG-4, which acknowledges Å·²©ÓéÀÖ complex network of sensors, data, IoT, and connectedness that comprise modern aircraft. To forge a successful path forward, we must seek incremental improvements and collaboration.

Your mission, modernized.

Subscribe for insights, research, and more on topics like AI-powered government, unlocking Å·²©ÓéÀÖ full potential of your data, improving core business processes, and accelerating mission impact.