Quick Reporting of Pending Maintenance Event

Explanation

This activity is used to perform quick reporting of a pending maintenance event. This is useful when you want to finish events that have already been performed. The events will be handled similar to how events distributed as Simplified Work Orders are handled. If the event being finished is an inspection event (initial or continued) for a modification:

• You may want to change the inspection to a higher intensiveness, a lower intensiveness, embody the modification or terminate inspections of the modification.
• Enter an appropriate execution type in the New Execution Type field. Do not change the execution type if you want to proceed with the current inspection.
• If you want to terminate inspections of the modification, enable the Terminate Inspections option. Terminating inspections implies that no further initial or continued inspections will be carried out for the particular serial, and the modification will not be complied with. If the Terminate Inspections option is enabled, a value is required to be entered in the Mod Execution Remark field.
• If you finish the last of the current inspection type without specifying a New Execution Type, and with the Terminate Inspections option not enabled, then the system will shift to the next execution type.

If a modification event leading to a part identity change exists and this modification has the Terminating Action execution type, the assigned or affected serial will be renamed to include the new part number and revision once the modification is embodied. In order to perform the automatic renaming of a serial once the event is embodied, the new part number and revision for the serial must have been entered on the modification (i.e., in the Change to Part Number and Change to Part Revision fields). Furthermore, when the modification event is embodied, the system will perform a check to validate the following information before renaming the serial:

• The new part number is a valid alternate of the old part number (i.e., if the serial being renamed is installed in a structure)
• The maintenance program and maintenance group for the old part number is valid for the new part number (i.e., if a new maintenance program and revision is not entered for the serial being renamed)
• The manufacturer and manufacturer part number of the old part number is valid for the new part number (i.e., when a new manufacturer and manufacturer part number is not entered for the serial being renamed)
• A valid maintenance program and maintenance group must exist for the new part number of the serial.
• The template of the old part number is valid for the new part number (i.e., if the serial being renamed has a structure)
• All running events for the serial which are mandatory to cancel have been canceled or finished with.
• The serial being renamed is not included in a work scope that is in any status between Started or Closed (i.e., if the serial is used in an IFS/Complex Assembly MRO flow).

When the part number is changed on a serial, the template information on the serial is often changed as well and will be updated automatically. If the serial has a structure and the old template information for the structure of the serial does not match the new template structure information, the operational condition of the serial will be set to Non Operational when renamed. When the template information is valid for both the old and new part numbers, the operational condition of the new serial will be the same as the operational condition on the old serial. You can choose to update the operational log history, replacement history as well as other history records with the new part number.

Depending on your workflow open one of the following pages to perform this activity:

• Pending Maintenance Events - Select the applicable row and select the option Quick Reporting of Pending Maintenance Event.
• Flight Log - Search for the necessary flight log and then click the Fault tab. Select the applicable fault number and then select the option Quick Reporting of Pending Maintenance Event.
• Serial Maintenance - Search for the necessary serial and then click the Modifications tab. Select the applicable row and then select the option Quick Reporting of Modification Event.

The Quick Reporting of Pending Maintenance Event assistant or the Quick Reporting of Modification assistant opens. Following is a description of the information that can be entered in each assistant step.

• Step 1 - Execution Information
  • Enter appropriate information in the Event Execution section
  • In the Post Maint Check ID field and the Post Maint Check Revision field, enter the identifier and revision of the post maintenance check that is to be carried out after the event has been finished. If a post maintenance check definition has been predefined for the event type, this post maintenance check definition will automatically be defaulted. If applicable, the defaulted value can be changed.
• Step 2 - Fault Information
  • If the selected event is a serial fault event, the Fault Information step opens as the second step of the assistant. Here you need to enter information on the function breakdown for the repair of the fault.
  • If the post maintenance check defined for the repaired fault differs from the post maintenance check originally defined for the fault, the new post maintenance check information can be entered in the Post Maint Check ID field and the Post Maint Check Revision field.
• Step 2 - Modification Information
  • If the event being finished is an inspection event (initial or continued) for a modification, the Modification Information step opens as the second step of the assistant. Here you need to enter information on the preventive checks for the modification. It is recommended that you read the information displayed on the assistant step.
• In thee Part ID Change on Serials in Structure section, you can enter information on any part revision or affected part in the structure that is to be renamed. You can also define if history records are to be updated with the rename information. It is recommended that you read the information displayed on the assistant step.
• Step 3 - Used Material and Operational Value
  • You can enter information on the material consumed on the event and enter operational parameter values in this step.
  • Create a new record in the Material List section and enter appropriate information.
  • Use the Operational Parameter Values section, to register the operational parameter values at the time the running maintenance event is completed. You can also use the Suggest Operational Values option to populate the current operational parameter values for the serial.
  • If operational parameter values are given, these are stored in the history and also used to calculate the next maintenance. If operational parameter values are not given, the historical values nearest in time to the finish date of the event is used.

Prerequisites

• A pending event without sign off requirements must exist. The Sign Off Req. Exist option will be enabled if sign off requirements exist for the event.
• Task cards must not be connected to a pending manual event. The Task Cards Exist option will be enabled if task cards are connected to the event.
• The workshop must be defined.
• Resources with the Person Group resource type must be defined. The resource must be valid for the site of the workshop connected to the event.
• If post maintenance checks should be generated when the event is finished, post maintenance check definitions must exist.

For serial fault events:

• Fault codes must have been defined. If a function number is entered on the fault, fault codes must have been registered for the functional breakdown.
• If a fault cause is to be entered, the cause must have been defined.

For modification events:

• The Allow Quick Reporting option must be enabled for the modification record in the Define Modification or Modification Details pages.
• If the event being finished is a modification event of execution type Terminating Action and leads to a part identity change, the new part number and revision must have been entered for the serial. These values can be entered in the Assign Part Revisions tab in Define Modification page or the Affected Parts tab in Modification Details page.
• If the modification work should lead to an automatic part identity change, the pending modification pending event must have the Terminating Action execution type.
• If the modification work should lead to an automatic part identity change for a serial installed in a structure, the new part number must have been defined as a valid alternative for the old part number.
• If the event being finished is a modification event of execution type Terminating Action and leads to a part identity change, a valid manufacturer and manufacturer part number must exist for the new part number of the serial.
• If the event being finished is a modification event of execution type Terminating Action and leads to a part identity change, a valid maintenance program and maintenance group must exist for the new part number of the serial.
• If the event being finished is a modification event of execution type Terminating Action and leads to a part identity change, the serial cannot exist on a shop order with a status between Started and Closed when using a Complex MRO flow.

System Effects

• The event is finished. Order history and event specific history is updated.
• If the object associated with the event is a vehicle serial and the serial has completed all running events, the vehicle condition of the serial is automatically set to the Vehicle Condition Code defined with auto setting Set when last event is finished.
• Depending on the type of event being completed, the due calculation for interval maintenance, modifications, post maintenance checks, life limited parts or fault deferrals will run automatically for the serial to calculate new due dates and values.
• In the background a work order is created, the status is changed to Started, man-hours used are reported on a single work task, and any consumed material is issued from inventory. The work order and work task is then set to Finished.
• If a modification leading to a part identity change is embodied, the part number of the serial will be changed throughout IFS/Fleet and Asset Management.
• If a modification leading to a part identity change is embodied, the part number of the serial will also be changed in Part Serial Catalog and the history will be generated.
• If the serial is in Inventory (i.e., the current position set to In Inventory) when being renamed through the embodiment of a modification, the correct quantity on hand will be created for the renamed individual.
• If the part number or serial number of the serial is changed through the embodiment of a modification, on a serial that exists in the Returns tab in the Work Task page, the part number or serial number of this serial will be updated as well.
• If a modification leading to a part identity change is embodied, information on the modification that has been complied with is retained in the serial identification history in IFS/Fleet and Asset Management. This modification can be used as a reference for the reason a part identity change was performed on the serial.
• If the serial's configuration becomes invalid as a result of the rename, the operational status of the renamed serial is automatically set to Out Of Operation.
• If the structure template information for the old template structure is not valid for the new template structure, the operational condition of the renamed serial is set to Non Operational.
• If an overhaul event (Overhaul + Cycle) is executed prior executing the scheduled interval maintenance events, the system automatically performs an Interval Maintenance Reset for all the changed events having the calculation rules Inspection, Overhaul (No Cycle) and Replacement that are due prior the overhaul event (Overhaul + Cycle). Note that interval maintenance that has not been changed is aligned automatically subsequent to signing off the overhaul.
• If post maintenance check information has been defined when the event is signed off, post maintenance checks will be generated according to the intervals of the post maintenance check definition.

Pages

Flight Log
Pending Maintenance Events
Serial Maintenance

Activity Diagrams

Manage Flight Logs
Plan Line Maintenance Activities