Defer Fault
Explanation
You can defer a fault using deferral information provided by Maintenance Operations Control (MOC) on phoning in
for a deferral and then proceeding to sign for the deferral. You can defer a fault on the Task
Details or My Work pages.
To defer a fault click Defer Fault and then click Record Deferral Details.
When you defer a fault you must record the deferral authorization number, provided by MOC, 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.
Prerequisites
- The fault status must be Open.
- 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.
- The deferral information on the fault is updated and an action is recorded against the fault with the
deferral action provided by you.
- 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:
– When a fault is raised offline and deferred offline: <Tail number>_OFFLINE_<User
ID>_<Timestamp>
– When a fault is raised offline/online and deferred online: <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.