Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Hackathon Exercise Planes and Parts
Hyperledger Composer Hackathon: Planes and Parts
Divide into small teams. I recommend the team have some web development skills, as well as Hyperledger Composer skills. You should have completed the Composer Playground Tutorial and Composer Developer Tutorial prior to the hackathon.
The airline industry is highly regulated, however despite all the regulations accidents still occur due to counterfeit parts entering the supply chain, or due to parts being fitted by unqualified mechanics.
You will create a solution for tracking the provenance of airline parts as well as the accreditation of mechanics.
A mechanic should be able to log the work that they are performing on an aeroplane part (using web/mobile/IoT), while the regulator should be able to use a web application to see the overall condition of the aircraft fleet.
Do your best to tackle as many of the situations of interest listed below. Feel free to make assumptions, but be prepared to explain them!
A mechanic (identified by
faaMechanicId) fits parts to an aeroplane. The mechanic has a set of certifications that authorise him to perform different types of maintenance on a plane.
The types of part (and certifications) are:
Everyone that works for the the regulator (FAA) needs to be able to see the full service history of every plane. They should receive notifications/alerts for critical situations.
A plane (identified by FAA
nNumber) is composed of a set of Parts, with every part being tracked in the supply chain.
A part (identified by
serialNumber) has a description, partNumber, type, creation date, condition (0-10, with 10 being excellent, 0 being failed) and an associated required maintenance certification. Each part has an associated service history.
See http://proaviation.com/inventory/ for an example parts catalog.
- Inspect part (update the condition)
- Replace part (swap one part for another)
- Destroy part (an old part is certified as destroyed)
- Create part (a new part enters the supply chain)
Regulatory Situations of Interest
- Destroyed parts still used by planes
- Parts serviced by unqualified mechanics
- Parts used by multiple planes
- Parts in POOR (<3) condition that are > 5 years old
- Ad-hoc query to find parts that are subject to recall
- Parts in GOOD condition (>8) that are less than 1 year old that are replaced (may indicate fraud)
- Parts whose condition IMPROVES
- A part that is replaced for another that is in worse condition
...and the results
Here's a link to the git-repo for one of the teams.