Heavy Maintenance Contract

Usage

This page can be used to define and view information about heavy maintenance contracts. Heavy Maintenance Contract (HM Contract) serves as an agreement between the customer and the MRO (Maintenance, Repair, and Overhaul) service provider.

Following details can be defined in the heavy maintenance contract header.

Purpose	Fields
Contract Identity and Status	Contract ID - If a Contract ID is not provided by the user, the system will automatically generate one.  Status – The statuses of a contract can be either Planned, Active, Negotiated or Closed. Contract Name – Name of the contract. Customer - The customer with whom this agreement is made.  Site - The identity of the site for which the heavy maintenance contract is valid. The value cannot be changed once the record is saved.  Currency - The currency code applicable to the heavy maintenance contract. When creating a contract, the customer's preferred currency is retrieved by default. Currency cannot be changed once the record is saved.
Additional Information	Coordinator - Contract coordinator.  Contract Manager - Responsible for overseeing the contract.  Notes - Additional information about the contract.
Contract Valid Period	Valid From -When a new record is created the system date is displayed by default, can change the value if required.   Expiry date - The date until when the heavy maintenance contract is valid. The expiry date on the contract must always be the same or a later date than the expiry dates on the contract lines.
Information for Tracking and Traceability	Created Date   Created By   Modified Date   Modified By

This page contains several tabs,

Contract Groups: Contract groups are specific definitions within a contract, designed to differentiate various categories of maintenance work. These definitions are tailored to the contract's unique requirements, allowing for adjustments based on varying parameters such as customer and MRO relationship, aircraft type, and the nature of the work etc. For more information on how to define a contract group, refer to the activity Enter Contract Groups.

Contract Lines: Contract lines are defined under the contract group and hold the information required to apply the contract for a given Maintenance Event and Task Cards. A single contract line within a contract group can be defined as the primary contract line by enabling the Primary Line option. This primary contract line will be automatically selected when loading the customer work scope, using the Work Scope Loader functionality and, when defining contract details at the maintenance event level while planning the work scope.

Note: To ensure smooth functionality, it is highly recommended to have a single contract line per contract group. 

If a single contract line is created for a contract group, it will be automatically selected when loading the work scope using the Work Scope Loader functionality. Additionally, when adding the contract information at the maintenance event level, this line will be automatically chosen. However, more than one contract line per contract group can be defined for different valid periods or to handle exception scenarios if needed. For more information on how to define a contract line, refer to the activity Enter Heavy Maintenance Contract Lines.

Part Provisioning Rules: Part provisioning rules outline the specifications regarding how parts should be supplied and managed during a maintenance visit, typically established at the part main group level. Any exceptions to these rules can be specified at the part level, known as explicit rules. Each part can have only one designated part provisioning rule, with explicit rules taking precedence over general rules when applying the provisioning guidelines. This rule set comprises two distinct types of provisioning rules: Material Provisioning Rules and Repair Provisioning Rules. For more information on how to define part provisioning rules on a heavy maintenance contract, refer to the activity Enter Part Provisioning Rules on Contract.

Explicit Part Provisioning Rules: Part provisioning rules can be defined on the part main group level, and if there are exceptions to the rule, these can be defined on the part level as explicit part provisioning rules.

Agreements: During the lifecycle of a contract, it is not uncommon to adjust prices from what was agreed at the time of the creation of the contract. Instead of revising the contract, a Customer Agreement can be connected to the contract. For more information on how to connect a customer agreement to a heavy maintenance contract, refer to the activity Enter Customer Agreements.

Customers: Heavy maintenance contracts are normally defined per customer and valid for multiple sites. However, it is possible to extend it to cover multiple customers, by connecting additional customers. This serves multiple purposes:

• Allows multiple customers to utilize one heavy maintenance contract. For example, if different maintenance organizations within a company are defined as separate customers but are permitted to use the same contract, they can be included as additional customers.
• Enables the entry of a different payer. For instance, if one of the aforementioned maintenance organizations needs to be invoiced separately from the parent company, the maintenance organization can be entered as an alternative customer. However, to do so, the maintenance organization has to be connected as an additional customer.

For more information on how to connect additional customers to a heavy maintenance contract, refer to the activity Enter Additional Customer.

Sites: MROs can operate across multiple sites, each serving as a distinct location for carrying out maintenance activities. For more information on how to connect additional sites to a heavy maintenance contract, refer to the activity Enter Valid Sites.

Pages

Heavy Maintenance Contract