Prepare to decomply a performed modification

Explanation

This activity is used to create a pending maintenance event for the decompliance of a modification.

When a modification is complied with, all defined actions are performed as specified. However, occasions can arise where previously performed actions need to be reversed (in other words, you need to decomply a modification). This can be performed using the New Event for Decompliance option. With this option, a new modification event containing the modification execution type decomply, is used to reverse the action of the modification that was previously performed.

When a modification of execution type Terminating Action leading to a part identity change is complied with, the serials assigned to and/or affected by the modification is automatically renamed to the new part number and revision. The New Event for Decompliance option can be used to create a pending event for the modification to reverse the performed serial rename. Once the decomplied modification event is finished, the renamed serial will be reversed back to its origin defined on the modification. This means that the renamed serial will be changed automatically and will include the old part number used before the serial was renamed. If history records were updated with the new part number of the renamed serial, these records will be updated once more to include the old part number of the serial.

Note: If post maintenance checks (PMCs) exist after the modification has been complied with, you can choose to remove these PMCs immediately, or after the decomply event for this modification is completed.

To create a pending event for the decompliance of a modification, select the option New Event for Decompliance from one of the following pages.

• Modifications that can be decomplied
• Serial Modification History
• Serial Modification History List
• History per Serial/Modification

For a modification that is related to a complex MRO flow, select the option New Event for Decompliance from the Manage Work Scope Events/PCW Modifications tab.

Prerequisites

• A historical modification (i.e., the modification is completed) with either an Active or an Obsolete status, must exist for the serial. Both pending and running decomply events can be defined for obsolete modifications.
• The Decompliance Allowed option must be enabled for the part assigned to the modification. For more information on connecting parts to a modification, refer to the activity Assign Parts to Modification.
• If the modification has been complied with, the compliance status for the modification must be Complied. (Initial or continued inspections cannot be decomplied at this stage.)
• The modification that will be decomplied must have the execution type Terminating Action. Furthermore, the Decompliance Allowed option must be enabled for the modification.
• If a part identity change performed on a serial through the embodiment of a modification is to be reversed, a pending event for the decompliance of the modification must exist.

System Effects

• A pending event for the decompliance of the modification is created, and the event is available for normal maintenance event distribution.
• When a referenced modification with a reference type of Mandatory is decomplied for a serial, the pending event created for the referencing modification is removed.
• When a decomplied modification event leading to a part identity change is finished, the serial is reversed back to its origin defined on the modification.
• When a decomplied modification event leading to a part identity change is finished, and history for the serial has been updated with the new part number, these history records will be updated once more with the old part number and revision.

Pages

History per Serial
Manage Work Scope Events
Modifications that can be decomplied
Serial Modification History
Serial Modification History List

Activity Diagrams

Plan Maintenance Events, variant MRO
Plan Maintenance Visit