Pending Maintenance Event

There are several calculation jobs that create pending maintenance events when calculated due dates are reached. These are:

Pending events are created automatically (without any calculation) for modifications defined as Next Visit in Workshop or Next Interval Maintenance, for all on-condition limits, and all registered faults.

Interval Based Maintenance

The due calculation of interval maintenance for serials is based on the registered average operational value per month and the defined maintenance plan. When these limits are reached, a pending event will be created for performing the maintenance.

The Drop Dead Date for the LLP has been Reached

The LLP due calculation creates pending events for life-limited serials when they have reached the forewarning period for the drop dead date.

Modification Inspections and Terminating Actions

Calculates the due dates and values of the modification/inspection for serials that are defined as To be performed. The calculation is only performed for active modifications. The calculation is done for each assigned serial based on the average operational value per month, the effective date and the defined executions (initial inspections, continued inspections and terminating action) for the modification. Note that all modifications defined as Next Visit in Workshop or Next Interval Maintenance, will automatically be created as pending events without any calculation. If post maintenance checks (PMCs) are defined for a modification, the pending events to perform inspections will be created after the modification has been complied with.

Fault Reporting and Inspections

All reported faults will automatically be defined as pending events.

If post maintenance checks (PMCs) are added for a fault, a regular PMC calculation will generate a new pending event based on the information entered on the PMC. A PMC can be specified either as a limit for an operational parameter or as time elapsed since the repair. You also have to supply the number of days forewarning the system should use for this PMC. The limit you enter will determine the number of times a PMC event will be created. The number of days forewarning will determine when it becomes a pending event.

If fault deferrals are defined for a fault, a new due date or value will be calculated when the deferral is recalculated. The deferral must be authorized before calculation can be performed.

An On-Condition Limit has been Reached

You must manually record condition measurements for a serial. If the registered condition limits are superseded by a measurement, you get a warning (yellow card) first, and then a danger signal (red card). A pending event is created. You are reminded until the event is done, the state is set back to normal, and a new cycle of measurement is started.

Manual Maintenance Events

It is possible to manually create maintenance events and add task cards/subtasks, resources, material, and task card sign off requirements to the event. When a manual event is created it will be added to the pool of pending maintenance events. Once the work for the event is planned, it can be connected to an ongoing maintenance order. Manual events are processed in the same way as all other maintenance events. For example, when a manual event that has the Work Order distribution type is released, a work order is created for it and a work task is created per task card/subtask on the event. When the work task is finished, reported time and cost as well as the cost of issued material will be transferred back to the event. 

Maintenance Event Summary (IFS/Complex Assembly MRO is required)

All selected modification events included in the work-scope will be inserted as pending events. LLPs (life limited parts) to be replaced due to the shop visit's requirement for remaining life for the LLPs, will also be added as pending events.