This activity is used to define non-requirement based events, referred to as convenience tasks. A convenience task is identified by its nature to occur unpredictably but execute through a fixed setup. Examples of such events are bird-strike inspection, heavy landing inspection, and cabin version changes.
To define a convenience task you need to enter a valid maintenance code for the combination of maintenance program, serial part, and maintenance group. When the maintenance code is connected to a task card, it is possible to define any work, resources, and material required to complete the convenience task.
Note: It is not possible to define convenience tasks using maintenance codes already defined in the Maintenance Plan/Intervals tab. In the same way, it will not be possible to define maintenance intervals by using the maintenance codes already defined for convenience tasks.
Additional information on the convenience task can be entered as a maintenance event remark. When a maintenance event is created for the convenience task, this information will be transferred to the event.
A post maintenance check definition can be connected to the maintenance code defined for the convenience task. When the corresponding maintenance event is finished, post maintenance checks will be generated to perform post maintenance activities for the convenience task.
As a result of this activity, the convenience task is defined and you can specify the actions that need to be performed to resolve the event.