Defer Fault

Explanation

Once the Maintenance Operations Controller (MOC) approves the deferral reference from the Pending Reference Approvals page in CAMO, the line technician can defer the fault.

If the DEFER_ON_APPROVAL configuration parameter is set to TRUE in CAMO, the fault will be automatically deferred upon MOC's approval of the deferral reference.

You can defer a fault on the Task Details or My Work pages.

To defer a fault click Defer Fault from the task or fault details page and then click Record Deferral Details. When you defer a fault, select a deferral reason and enter the deferral action taken. You can also record a deferral note and proceed to sign off.

Depending on the Signature Service User Permissions for your user, you can sign off using a digital signature or via an alternative sign-off process. You can use an assigned YubiKey to sign off on the deferral creating an immutable digital signature. To do so click Sign, proceed with the sign off process, and click Finish. The digital signature is stored against the task or fault and can be viewed at any time.

Alternatively, if you are signing off without YubiKey authentication, simply click Finish to complete the task.

Note: If you are deferring a fault and signing off using a digital signature, follow through with recording the digital signature or cancel the procedure before the final step to avoid canceling at the final step and losing all task actions performed. 

Note: When you defer a fault, the system warns you if any issued materials for the task have not been signed. The message lists the unsigned materials. You can continue with the deferral or cancel it to sign the materials first.

Note: You can open Defer Fault and select a deferral reference even if assignments on the fault or its subtasks are in Work Started status. However, completing the deferral is blocked until those assignments are completed or job-stopped.

Note: A deferral reference that requires MOC approval cannot be selected while assignments on the fault or its subtasks are in Work Started status. The same rule applies when using Request to Defer Fault.

Note: If other work packages are in progress at different maintenance locations, the system displays an alert. You must complete those work packages before you can defer the fault.

Note: When you defer a fault, which has one or more panels connected to it, the corresponding corrective maintenance task of it gets removed from the nested MAINTENANCE TASKS tab of all the MPC open/close tasks of the connected panels.

Prerequisites

• The fault status must be Open.
• Any work that has started on the fault or its subtasks must be completed or job‑stopped before you can defer the fault. If work is in progress, the system displays a message. You must complete or job‑stop those assignments before proceeding with the deferral.
• If there are other work packages in progress at a different maintenance location, you must complete or close those work packages before deferring the fault.
• The aircraft must not be locked.
• Deferral reasons must be set up in Aviation Maintenance/Basic Data/Fault.
• If you are using digital signature to sign off on the deferral, the application user should be registered with a valid public certificate to use IFS signature service in Solution Manager/Signature Service.
• If you are not using a digital signature to sign off, the E-Sign option must have been disabled from the Signature Service User Permissions page.

System Effects

• The fault status changes to Deferred and the fault is displayed with the list of deferred faults for the aircraft turn.
• If the fault has linked subtasks, those subtasks are unassigned from the work package and removed from the Workscope tab. In hangar maintenance, they are also removed from the Tasks page. The fault–subtask link is maintained after deferral.
• In line maintenance, the fault moves to the Deferred Faults tab. The Task Details page for each deferred subtask becomes read-only.
• In hangar maintenance, a deferred non-routine with subtasks is visible on the Unassigned Faults tab of the Hangar Maintenance Work Package Execution page.
• If the fault has work assignments that were assigned but not yet started, those assignments are automatically unassigned when the fault is deferred.
• If materials were reserved for the task but not yet issued, those material reservations are automatically released when the fault is deferred.
• When the fault is deferred, the fault can be packaged into another work package from CAMO. Once published to MEX, any pending work items (such as parts, labor requirements, tools, and measurements) are available in the new task created for the deferred fault. All task steps are listed as pending in the new task, allowing you to start fresh. Completed steps are synchronized to CAMO for record-keeping.
• After you defer the fault, an execution summary becomes available on the Fault Details page. This execution summary shows the history of work attempts, including when the work was performed, which steps were completed, what parts and materials were used, and the deferral reasons. This information is displayed in read-only mode for reference.
• The deferral information on the fault is updated and an action is recorded against the fault with the deferral action provided by you.
•  The DEFER_ON_APPROVAL configuration parameter in CAMO must be set to FALSE.
• The task is unassigned from the work package and no longer displayed as a work task.
• If the sign-off was handled using a digital signature, you can download a .zip file containing digital signature information from the Attachments/Digital Signatures tab at the bottom of the Task Details and Fault Details pages. Alternatively, if configured, you can view the digital signature files at the external file storage location.
  
  This .zip file contains .json, .xml, and .pdf files. The metadata is stored in the .json and .xml files, while the .pdf file includes the signed document containing the content reviewed by the line technician.
  
  The file name of the .zip file follows the GUID.zip format, where GUID stands for globally unique identifier.
  
  The files within the ZIP file are named in the following format: <Tail number>_<Record ID>_<User ID>_<Timestamp>
• When deferring a fault that has a signed removal of a mandatory component and there is no corresponding installation or signed installation of a part for the same mandatory config slot and position in the work package, you will see a warning indicating that the fault removed a mandatory component and there is no matching part installation in the work package.
• When deferring a fault, if the number of mandatory component installations does not tally with the number of mandatory component removals in the work package for the same config slot and position, you will see a warning.
• If the fault you are deferring has part installation or removal records, the information related to part changes are sent to CMS for validation upon deferring the fault.
  
  CMS warnings are displayed on the following pages:
  
  Web application
  
  - Fault Details page (banner) - If the part changes are pending CMS validation, a yellow banner is displayed to indicate that the CMS validation is pending. If a configuration issue has been identified during the CMS validation, a red banner is displayed.
  - Fault Details page/PART REMOVALS and PART INSTALLATIONS tabs (Configuration Warning field) - You can expand the row with the configuration warning to see more information about the warning.
  - Aircraft Turn Details page (banner) - If a configuration issue has been identified during the CMS validation, a red banner is displayed.
  - Aircraft Turn Details page/DEFERRED FAULTS tab (Configuration Warning field)
  
  Mobile application
  
  - Aircraft Turn Details page (banner) - If a configuration issue has been identified during the CMS validation, a red banner is displayed.
  - Aircraft Turn Details page/Deferred Faults tab (Configuration Warning field)
  - Fault Details page/Part Changes tab (Configuration Warning field). You can select View Warning to see more information about the warning.
  
  For more information, see About CMS Validations.

Note: When a fault is deferred, only tools with recorded usage hours that have been signed are synchronized to CAMO. Unsigned tools are not included in the synchronization.

Pages

Task Details

Activity Diagrams

Defer Faults or Non-Routines