Collisions don’t often make the headlines because they usually happen at very low speed when taxiing, therefore no one gets hurt and it’s not very spectacular.
Repairs and the grounding of an airplane for several days or weeks however can be astronomical in terms of cost.
A minor collision, which could simply be ignored if it were someone’s car, can mean significant downtime for repair and checks, which immediately translates into dollars lost. A big airliner can lose tens of thousands of dollars an hour in addition to the cost of repair – around 250,000 euros (331,000 dollars) in the Roissy-CDG case.
Regular maintenance is predictable and documentation is specially designed and optimized for maintenance of this kind, but documentation is not designed to tackle unexpected repairs.
In the case of aircraft, maintenance documentation is organized by topic: a set of books for hydraulics, another one for electricity, another one for mechanics and so on, with no link whatsoever between sets.
But in our collision scenario, it isn’t about checking electricity, then hydraulics, etc. The repair crew needs to start with the damaged area, and from here, to be lead towards the relevant information.
Taking a “product-centric” rather than “document-centric” approach to technical information helps professionals find relevant service information more easily.
With product-centric technical information, accessed digitally, repair crews have the ability to work from product structures originating from product development. This allows service and parts information to remain consistent with current engineering designs, which in turn leads to a reduction in errors and inefficiencies.
Taking a product-centric approach to maintenance is beneficial, not only in aircraft repair, but across all complex products—from nuclear plants to environmentally efficient buildings.
Is your company ready to go product-centric?