Traceability and Transparency

How might we improve the traceability and transparency of critical information on the engines, parts and activities during the maintenance process, so verification of the information can be made easier?

Integrated and Coherent

How might we design a shared platform that is integrated into existing workflows of different stakeholders and also allows for new data inputs, such as IoT, and analytics?

Seamless and Self-executing

How might we improve the speed of information flow and task execution, while having the right protocols in place to prevent errors and maintain data protection?

Maintenance Workflow


An engine is scheduled to have a soft life proactive replacement of a major component, Line-Replaceable Unit (LRU). In hopes of improving a developing engine health monitoring issue the LRU was replaced. Subsequent flights revealed that the troubleshooting issue is still deteriorating. Eventually the technical team plans an engine removal to schedule it for a shop visit for rectification. As this engine is on a lease, removal of the engine for shop visit warrants a lease return check before it is released it back to the lessor.

Asset 12q.png

Maintenance Planning Data Download


Asset 12q.png

Line Maintenance Tracking Chart Updates


Asset 12q.png

Work Request Input


Asset 12q.png

Issuance of Work Instructions and Purchase Orders




BFE : Buyer Furnished Equipment 
EHM  :  Equipment Health Monitoring
ERP : Enterprise Resource Planning

LAE : Licensed Aircraft Engineer
LMTC : Line Maintenance Tracking Chart

LRU : Line-Replaceable Unit

MPC : Maintenance Planning and Control
PDD  : Planning Data Department

PPS : PowerPlant Shop
QAT : Quick-Action-Team
RR : Rolls-Royce
SIAEC : SIA Engineering Company
TCAv : TotalCare Availability

WRI : Work Request Input

Problem Statement


This is a Blockchain assignment, where you are expected to create a Blockchain solution for solving the above problem, based on the maintenance process.


You need to create a consortium blockchain solution using any of the technologies wherein the members of the consortium will be - 

  • Airline

  • RR (Rolls-Royce)

  • SIAEC (SIA Engineering Company)

  • MRO

Submission Guidelines


1. You are expected to submit a prototype for this challenge which covers at least 3-4 steps mentioned in the workflow. You can choose any of the steps as long as they make sense as a coherent workflow. Essentially, you need to make logical sub-sections in the workflow and attempt to make it more efficient using your solution

2. You need to submit your solution as a private Github repository - shared only with the evaluators and stakeholders

3. You also need to provide a Powerpoint/Keynote/Google Slides deck with the solution. This can be uploaded to a private Google Drive or Dropbox, and the link to the deck needs to be in the README of the Github repo. This deck will talk more about the solution you have built, your idea/concept and why you chose to solve this part of the process specifically. Required points to be included in the deck as follows;

  • Introduction - An introduction to your company & team

  • Challenge of choice - Explain the challenge of choice

  • Solution - Articulate the idea and your strategy in solving the problem.

  • Tech - What makes your blockchain technology special? Elaborate on tools and approach used.

  • Beyond challenge - How can your solution be implemented into an existing business? Elaborate on compatibility.


4. The instructions to submit will be emailed to you once you complete the application form


5. This challenge is agnostic towards the blockchain platform. You can use any technology (Ethereum, Hyperledger, Corda, Quorum, etc) in order to build your solution


6. It is important to note though, that your solution needs to cater towards a PRIVATE blockchain platform since the data being shared amongst the parties is sensitive


7. ONLY specific members in this consortium will be able to read and write data from the blockchain, and these controls need to be built in your solution. For example, within the RR organization, you might have multiple nodes and also different levels of access controls based on the job function of the person

Sample Documents Provided


All the document samples are available for download at the Resources page. You can choose to use one or more of the sample documents provided here for creating your solution. 

Qualification Criteria

1. Submit the correct link to your repository


2. Make sure your repository includes the complete codebase (all the commits are done, documentation, complete, etc)


3. Focus on one of the themes mentioned above. Your solution should try to solve the maintenance process and make it more efficient from the perspective of one of the themes mentioned above. There might be some overlap, which is ok, but one of the themes must be clearly visible in your solution. 


4. Do not plagiarise the code. That will be grounds for instant disqualification

Submission Deadline


Please submit the final repository including documentation by or before 23rd September, 23.59pm (SGT)

Judging Criteria

Your solution will be judged on the following criteria


Code quality 

Code Quality, also known as Software Quality, is generally defined in two ways:

  • How well does the code conform to the functional specifications and requirements of a project.

  • Structural quality, which relates to the maintainability and robustness of the code.



For code readability,  the evaluator will study the way in which you write the code. A readable code is easy to understand, follows standard naming conventions, is consistent and can be grasped by anyone reading it, right from a novice programmer to an expert. 



Code extensibility generally means that the code is easily extensible, has few and clean dependencies, reduced coupling and more cohesive abstractions. 

In the context of this problem statement though, you need to make sure that your codebase and solution can be extended from a small prototype to a product that can be readily  deployed on the shopfloor. It should scale across verticals and also across different stakeholders. 



In the context of this problem statement, you need to ensure that the code you are writing is applicable to a particular use case of engine maintenance and also solves the given problem statement. Your solution cannot be too generic, it needs to conform to the requirements given above and have a near future application. 

Security and Reliability

In the case of a blockchain application, and due to the fact that multiple stakeholders are involved, and that you are dealing with information which is sensitive and important, you need to make sure that the solution you are proposing and the code you are writing is extremely secure and reliable. Lapses in standard security protocols will be penalized during scoring.

Powered by

In Collaboration with

Prize Sponsor