AWS for Industries

Improve Aircraft parts provenance using Amazon Managed Blockchain

Today’s commercial and defense aircrafts are made up of thousands of parts. The aerospace industry has to function in a tight regulatory environment, which requires the vetting of all parts. These parts can be resold several times throughout the production lifecycle, which makes it challenging to track their history. The traceability of aircraft parts is traditionally a paper-based process. Airlines and other industry participants have to spend a significant amount of time and money to ensure the quality of the aircraft parts supply chain.

In the absence of part-history traceability, the part’s airworthiness must be established through testing and recertification. Sometimes the parts must be replaced because these details aren’t available. The data is spread across and isolated in multiple parties and systems. Intellectual property rights for aircraft parts are owned by multiple parties (for example, customer, OEM, part supplier). Other parties are granted IP use licenses that often do not include data rights. Although those parties might be part of the same ecosystem (manufacturer, suppliers, dismantlers, airline customers, and repair companies), sharing the data can be a challenge because of industry competition. Blockchain’s decentralized, immutable, and consensus-based nature makes it a perfect fit to help overcome these challenges.

Blockchain is a decentralized, transparent, immutable, and auditable data store that keeps a permanent record of all transactions. After a record is written to a blockchain, it cannot be altered. The digital thread will provide real-time status, a chain of custody, and maintenance records of the part over time.

In this blog post, we share industry challenges and an example of how you can use Amazon Managed Blockchain to improve visibility into the history of aircraft parts. The focus of the example we use in this post is on improving the tracking of the part between multiple members during initial repair as part of an operator’s maintenance, repair, and overhaul (MRO) process.

Blockchain benefits

The MRO industry processes 25 billion parts annually, with 20,000 suppliers adding three billion new parts each year. According to information published in in February 2020, there is currently no global parts database. Data sharing is incomplete and only partial digitalized. According to information first published in Data for the life of the aircraft, published by PWC in April 2019, blockchain could cut MRO costs globally by around 5% or $3.5 billion.

For aircraft operators and MRO service providers, a blockchain solution:

  • Reduces time spent on routine inspection and maintenance, thereby improving fleet availability.
  • Increases asset utilization.
  • Reduces inventory threshold.
  • Reduces opportunity for counterfeit parts to be introduced into the supply chain.
  • Ensures that components from banned countries or cyber vulnerabilities do not get introduced into the supply chain.
  • Offers regulatory compliance for issues such as conflict mineral sourcing and human-trafficking laws.

For operators and lessors, a Blockchain solution:

  • Improves the value of the aircraft in the secondary market.

For suppliers and manufacturers, a blockchain solution:

  • Cuts out the middle person for the parts seller and reduces costs.
  • Improves selling opportunities in the parts digital marketplace.

Part Lifecycle 

The following diagram shows how a part goes through the aircraft maintenance lifecycle. The initial component could be acquired through OEMs, parts manufacturer approvals (PMAs), suppliers or traders, or a digital parts marketplace. When the part needs repair and is not serviceable, it ends up in scrap. The operator might have a contractual agreement with an engine OEM or other third parties for the maintenance and overhaul of the parts. Some of these parts require overhaul after a certain number of flying hours. The operator might get the same exact part or a different overhauled part.

Example of Aircraft part Lifecycle Figure 1: Aircraft part Lifecycle

Keeping track of the origin of a part and its maintenance and overhaul history improves airworthiness and reduces the inspection and testing. It also prevents counterfeit parts.

Parts traceability requires a decentralized multi-member network that allows each member (supplier, operator, dismantler, manufacturer) to update information independently. A Hyperledger Fabric network on Amazon Managed Blockchain remains active as long as there is a single member. The network is deleted only when the last member leaves the network. No member or AWS account, even the creator’s AWS account, can delete the network until they are the last member and leave the network.

A blockchain solution could be started by industry alliances, MRO service providers, the parts digital marketplace, OEMs, industry exchange solution providers, and so on. The solution could be built by a smaller group of organizations who collaborate closely and then invite new members to join.

Amazon Managed Blockchain Solution

The following diagram shows the typical aircraft part production lifecycle: initial production (birth), initial delivery, and multiple repair cycles until it’s no longer fit for service and scrapped.

Example of process in repair of a partFigure 2: Part repair process

Let’s walk through how the blockchain solution would work for a single part in a single repair cycle. In this example, the following members work together as part of an alliance:

Manufacturer 1: The original manufacturer for the part. In this example, we include the manufacturer’s repair shop, too. These facilities repair and overhaul aircraft parts. Some facilities provide support for single parts. Some provide support for selected parts, up to complete aircrafts.

Supplier 1: The operator sources components from this supplier.

Logistics (Couriers 1 and 2): The parties responsible for delivering the component to its destination. Sometimes multiple couriers are involved.

Operator 1: The airline that operates aircraft to transport passengers, cargo, and so on. Sometimes the operator also outsources the maintenance activity to third parties (for example, OEMs, MRO service providers).

First cycle of repair process

As part of its initial delivery to the operator, the part is inspected and fitted to the aircraft for service. After some use, a fault occurs and the part needs repair. The blockchain already has part information from the manufacturer and other details from the supplier. Members can use the part usage information in different attributes:

  • Time since new (TSN): The cumulative flying hours of the component since its manufacture.
  • Cycles since new (CSN): For life-limited parts, the cumulative flying cycles of the component since its manufacture.

Step 1: Operator 1 raises a work order (WO) in the MRO system for the defect and removes the part from the aircraft. Courier 2 receives a notification to pick up the part.

Step 2: Courier 2 picks up the part and delivers it to the manufacturer’s repair shop. Manufacturer 1 receives a notification.

Step 3: Manufacturer 1 works on the WO and after the part is repaired, informs the courier to pick it up. Courier 2 receives a notification.

Step 4: Courier 2 delivers the part to operator 1’s base.

Step 5: Operator 1 validates the part and performs a compliance check, if required. The part is fitted on the aircraft, if needed. Otherwise, it might be sent to the warehouse to be used later.

Transaction blocks in blockchain - example stepsFigure 3: Transaction blocks in blockchain

Amazon Managed Blockchain 

Now, let’s look at the architecture. Amazon Managed Blockchain is a fully managed service that allows you to or set up and manage scalable private networks with just a few clicks using the popular open source frameworks, Hyperledger Fabric or Ethereum. Amazon Managed Blockchain eliminates the overhead required to create the network or join a public network. It scales to meet the demands of thousands of applications running millions of transactions. The service removes the burden of provisioning hardware, installing software, managing certificates for access control, and configuring network settings. After your network is up and running, Amazon Managed Blockchain makes it easy to manage and maintain. It manages your certificates and lets you easily invite new members to join the network.

Hyperledger Fabric is designed for applications that require stringent privacy and permission controls with a known set of members. It can be used for aircraft parts provenance.

The following diagram shows the basic components of a Hyperledger Fabric blockchain running on Amazon Managed Blockchain with five members:

High level architecture for end-to-end solutionFigure 4: End-to-end solution architecture

Amazon Managed Blockchain runs all the Fabric components (ordering service, certificate authorities, and peer nodes) in a VPC created in Amazon API Gateway provides API routes to a web application and invokes an AWS Lambda function for each route. The Lambda function obtains users’ blockchain credentials from AWS Secrets Manager and uses those to sign blockchain transactions. Next, the Lambda function sends the signed blockchain transactions for endorsement through the VPC endpoint to the peer node running in an Amazon Managed Blockchain network. Lastly, the Lambda function sends the endorsed transaction proposal to the ordering service where it is committed to the blockchain.

Some business processes like compliance inspection or notifying the courier to pick up parts could be triggered by business events to increase communication and automation between different members. Blockchain events allow applications to respond to activity and updates to the smart contracts that have been deployed to the network, as well as updates to the blockchain network, such as the creation of a new block. These events can enable a diverse set of activities (for example, user notifications through Amazon Simple Notification Service (Amazon SNS) when a business event happens, or streaming data to business intelligence and analytics engines such as Amazon QuickSight or Amazon Redshift). You can also stream to purpose-built databases such as Amazon DynamoDB or Amazon Aurora, or use AWS Lambda for event-triggered applications. For more information, see the Building an event-based application with Amazon Managed Blockchain blog post.

OEMs can enrich this tracking data by linking it to the supply chain process of the parts tracking. For more information, see Blockchain for Supply Chain: Track and Trace and the AerLink is digitally transforming the aircraft leasing and financing industry using Amazon Managed Blockchain blog post.

Considerations for Success

Growing blockchain network membership: When aircraft parts are tracked through the blockchain network, the parts have a verifiable provenance, which provides benefits to the alliance and its members. The key members (manufacturers, suppliers, operators, repair shops) need to join the network. The network should have a working group to define data and API standards, agree on endorsement policies, and costing model for new members. This helps to increase the understanding of the operating model and make it easier for members to join the network. The MRO system could also be fully integrated with the blockchain system using standard APIs. This would allow operators and other MRO service providers to easily adopt the blockchain solution and take advantage of its benefits.

Governance: A private permissions-based blockchain still requires governance and operational oversight. Distributed and decentralized does not mean self-managing. Hyperledger Fabric enables secure interactions among a set of known, identified participants who have a common goal, but do not fully trust each other. It is important to choose a governance model or organization that does not compromise the integrity of the blockchain. By relying on the identities of peers, a permissioned blockchain like Hyperledger Fabric relies on deterministic consensus algorithms. Any block validated by the peer is guaranteed to be final and correct.

Time to build blockchain application: Developing blockchain and ledger applications is simpler, faster, and more efficient with AWS. Amazon Managed Blockchain eliminates the heavy lifting involved in the setup of blockchain networks by reducing the time taken in hosting Hyperledger Fabric frameworks. Amazon Managed Blockchain also makes it easy to operate networks because it supports the AWS CLI, AWS CloudFormation, and Amazon CloudWatch logs.

Simplifying costs for blockchain membership: The cost for membership in a blockchain network should be transparent to members. With Amazon Managed Blockchain, you pay as you go. There are no up-front costs or minimum fees. An Amazon Managed Blockchain network for Hyperledger Fabric consists of one or more members. Each member has peer nodes with local storage. Members can write data to the network. Members are charged for network membership, peer nodes, peer node storage, data written to the network, and data transfer. The costs associated with shared network components are included in your hourly network membership rate, which is billed per second. For more information, see Amazon Managed Blockchain for Hyperledger Fabric pricing.


The travel and aerospace industry needs a one-stop view of aircraft parts provenance. Amazon Managed Blockchain removes the overhead required to create the network. It scales to meet the demands of thousands of applications running millions of transactions for aircrafts parts provenance.

Bib Shukla

Bib Shukla

Bib is EMEA Senior Specialist Solutions Architect for Travel & Hospitality at Amazon Web Services, responsible for guiding the development of reusable IT, blockchain, data and cloud native solutions for the travel & Hospitality. Bib is an industry veteran with 21+ years of leadership experience in digital transformation, enterprise architecture, customer/operation data platform, MRO IT transformation and delivery, and consulting across multiple industries both domestically and internationally.

Sekhar Mallipeddi

Sekhar Mallipeddi

Sekhar is the Worldwide Technical Leader for Travel at AWS with the charter to support and help travel and hospitality customers innovate using AWS cloud to enhance customer experience and improve operational efficiency. Sekhar leads the technical field community for Travel that enables internal AWS teams, ISVs, and GSIs creating technical assets, reference architectures, and solutions. Prior to joining AWS, he spent 20 years in the Travel and Hospitality industry in information technology strategy, cloud strategy, and enterprise architecture roles and built products for aircraft predictive maintenance, revenue management, customer master data management, and analytics. He holds a M.S. in computer science from University of Texas at Arlington, and an MBA from the University of Chicago Booth School of Business. In his spare time, Sekhar loves to cook and experiment with ingredients and cuisines from around the world, and traveling with his family in search of amazing food and wine and has visited over 40 countries.

Tim Murnin

Tim Murnin

Tim Murnin is the worldwide aerospace industry specialist at Amazon Web Services. In this role, he leads the go to market strategy for AWS within the aerospace & defense industry and works closely with customers and partners to define solutions to transform their business. Prior to joining AWS, Tim was the director of manufacturing automation at The Boeing Company, where he led strategies and implementation plans for initiatives such as Smart Factory, blockchain and the Industry Internet of Things at Boeing production sites. Prior to that role, Tim led supply chain strategy for Boeing, Defense, Space & Security. Tim also held leadership roles forming a joint venture with Tata Aerospace and in supply chain management at Boeing Global Services. Tim has a bachelor’s degree from Saint Louis University and an MBA from Harvard Business School.