Release Maintenance Event

Explanation

This activity is used to release an event on a maintenance order.

When a maintenance order is released, all connected events will be released automatically. However, if an event is added to a maintenance order that is already released, and the event does not have any task cards, the status of the event will be set to Incomplete. To be able to release such an event and start with the work it is necessary to first connect a valid task card and then set the event to the Under Preparation status or directly the the Released status.

When an event with the Simplified Work Order distribution type is released, the event will be processed in Fleet and Asset Management. For events released with the Work Order distribution type, a corresponding work order will be created per event in IFS Work Order Management. If the event being released has the Execution Logic Structure distribution type, all relevant execution logic orders (ELOs) and ELO task cards will receive corresponding work orders and work tasks in IFS Work Order Management.

If the resource and material demands of a non routine event exceed the agreed on free cap values of the connected heavy maintenance contract line, the MRO provider will require commercial approval from the customer in order to proceed with the non routine. In such cases, before the non routine event can be released, one of the following actions should be taken for the non routine event:

• Once the approval from the customer is confirmed, update the non routine commercial approval to the Approved status.
• The MRO provider will decide to proceed with risk by enabling the Proceed At Risk option.

Note: If an integrated non routine quotation flow is used for a non routine that has been released by enabling the Proceed At Risk option, and the non routine quotation is approved as well as the commercial approval is in the Approved status, quoted values will be invoiced. If the quotation is rejected and the commercial approval is in the Rejected status, no work will be invoiced.

If the event being released is connected to a service quotation for which an emergent work percentage is specified, the system will calculate the emerging work amount and raise an information message if the currently used emergent work exceeds 90% of the specified emergent work from the quotation. It is recommended that you evaluate emergent work at this time so as to avoid, for instance a situation where a medium to large event is about to start and the used emergent work percentage is already over 90%. Here, the Allowed emergent work amount is calculated as all emergent work on the quotation where the event is registered and will be equal to the value entered in the Emergent Work field found in the Quotation Totals tab in Service Quotation page. To calculate the currently used emergent work amount the system goes through all maintenance orders that are connected to the quotation and identifies all non routine events in the Work Done status or higher which are not in the quoted scope of the quotation. It will then summarize the prices for transactions belonging to these events and if the result is 90% or higher raise the relevant information message.

Prerequisites

• An event in the Under Preparation status must exist on the maintenance order.

The following prerequisites are only valid if the maintenance events are connected to a heavy maintenance contract:

• Contract line details must be defined on the maintenance event level.
• If the event is a non routine event and commercial approval is needed to proceed with the event, the non routine approval status must be set to Approved or the Procced At Risk option must be enabled.

System Effects

• The event is set to the Released status.
• Additional task cards can be specified for the released event.
• If a heavy maintenance contract is connected to the maintenance event, it is transferred to the generated work tasks, along with the given contract group and contract line.
• The ownership of the material demands connected to the event cannot be changed. This only applies to material included on maintenance orders with the Work Order or Execution Logic Structure distribution type.
• Defined task cards for a released event can be canceled.
• The event will be distributed to a work order if the distribution type is either Work Order or Execution Logic Structure.
• When an event is released on a maintenance order distributed with the Execution Logic Structure distribution type, the event will be added to the ongoing maintenance order and connected task cards will be mapped into correct ELOs on the maintenance order. In addition, the task cards will be mapped into corresponding ELO work orders in IFS Work Order Management.
• If the serial is a vehicle serial, the first event that is released on the serial will lead to an automatic change of the vehicle condition of the serial to the Vehicle Condition Code defined by the auto setting Set when first Mx event is started. For more information, refer to the activity Define Vehicle Condition.
• If post maintenance check information has been predefined for the event type, this information will be fetched onto the event on the maintenance order.

Pages

Manage Maintenance Order

Activity Diagrams

Integrate Emergent Work
Perform Simplified Maintenance Events