The Warranty Module has been designed to ensure an operator maximizes the amount of warranty that is claimed on both the aircraft and parts in the inventory.

By setting up warranty contract terms in the OASES system any potential claim can be identified and a claim made for the part as soon as it is booked into stores in an un-serviceable condition.


Warranty Workbench

Warranty Controllers use the integrated Warranty Workbench to monitor the warranty situation and to make decisions on claims where this is required. All the actions necessary to administer warranty can be carried out in this single screen. A Warranty Controller can tailor his workbench through a series of filters to customise It to their particular requirements which may be a set of vendor accounts or perhaps an aircraft fleet for which they has responsibility. Use of the Workbench speeds up the administration and ensures all the data necessary to carry out the function is all available in one place. This allows the controllers to spend more time analyzing and improving performance rather than carrying out basic administration.

Warranty Agreements

The Vendor Management team can define in OASES the exact warranty agreements that are in place covering an aircraft, a vendor, a repair station, or a part / serial number. This allows a great deal of flexibility in defining the exact warranty terms for each aircraft or component, as well as allowing for contract agreements where groups of parts are overhauled by a particular contractor. Manufacturer warranties can also be handled for new aircraft which can be calendar, hours or cycles based. Once defined in OASES, these rules will then be used to decide if a warranty claim can be made for any part coming from an aircraft in an un-serviceable condition.

Warranty Tracking

At the time of booking in the component in an un-serviceable state the component records are checked to see if any potential warranty claim can be made. This can be based on time since new, time since fit, a calendar time, or a time since overhaul or repair. It can check the number of cycles or hours since new or last overhauled or last repaired. The potential claims are identified by comparing the component information held in the system against a set of criteria which have been defined for that part by the Vendor Management team. When a claim is identified the system automatically marks the repair order in the system as a warranty claim and advises the stores person of the warranty claim. If the stores person does not want to claim warranty they must enter a reason for not doing so. When a warranty is claimed, the warranty order for that component is identified with a watermark as a ‘warranty claim’. The order paperwork will also have printed on it, details of the reason for the warranty claim.


Once the system is setup it will identify each warranty claim that can be made and then either automatically raise a warranty order or refer the case to the warranty team for a decision. In the event more than one warranty term is a potential source of a warranty claim the system identifies these items, and refers them to the warranty controller through the Warranty Workbench. The controller can then decide which claim to make based on the value or likelihood of the claim being successful. The warranty controllers can also enter data relating to their warranty claims as it becomes available, such as whether the warranty is granted or denied. They can also enter strip reports and other information to build a full history for a particular part.


By continuously gathering data on the warranty claims and their outcome, the system has the ability to generate a variety of useful reports which help the operator monitor its performance in successfully claiming warranty. These reports can then be used to target vendors or repair stations which have a poor record of performance with regards to warranty claims and drive up the number of successful claims.
Share with

Our website uses cookies. To learn more, including how to manage cookies. click here