This page can be used to define pricing rules and conditions applied during the invoicing process for the maintenance work performed by the MRO on behalf of the customer.
Following details can be viewed and edited in the heavy maintenance contract line header.
Purpose | Fields |
Contract Identity and Status |
|
Identification |
|
Validity Period |
|
Additional Information |
|
Primary Line |
|
This page contains two tabs,
Contract Rules: Contract rules define how a customer is billed for planned and/or completed maintenance work associated with a heavy maintenance contract line. Multiple contract rule lines can be defined for a heavy maintenance contract line to cover various types of maintenance work, such as Routine, Non-Routine, or Both. They can also be defined for different sales groups and cost types, as well as a default, mandatory contract rule line covering all other types that haven't been explicitly defined. If any transaction on the generated work tasks is not covered by a contract rule, the price logic used for work tasks will be applied during invoicing. For more information on how to define a contract rule, refer to the activity Define Contract Rules.
Exclusions: If certain ATA chapters are to be excluded from the heavy maintenance contract when handling reported non-routine events, these specific ATA chapters can be defined in the Heavy Maintenance Contract Line/Executions tab. These exclusions apply only to non routines which are reported from a work task connected to the heavy maintenance contract line. When reporting a non routine using the Report Fault option in the Report Non Routine assistant from the work task level, the heavy maintenance contract line connected to the originating task is automatically inherited to the created non routine event. If the lowest function level of the reported non routine belongs to the excluded list of functions or if it is a child function or a function in the excluded list, the non routine will be excluded from the contract. In other words, contract details will not be applied to the non routine event. For more information on how to define non routine exclusions, refer to the activity Define Exclusions for Non Routines.