Deferral references

Deferral references are used by technicians to justify deferring faults. When you create deferral references, you must consider applicability rules, follow-on requirements, related deferral references, and impacts on operations, performance, and maintenance actions.

The following list describes the deferral reference fields in detail:

Assembly Type: The assembly type to which the deferral reference applies.
Failed System: The failed system to which the deferral reference applies. You can search by system name and ATA chapter.; This field only populates the System slots for the chosen assembly. Root, Tracked, and Sub-assembly configuration slots or positions are not searched.; This field uses auto-complete functionality. For example, if you type "72-" in the Failed System field, the system configuration slot with "72-" anywhere in its name is displayed.
Number Installed: For the particular component, the total number installed or that can be installed on the aircraft. You can enter dashes (-), zeros, and positive numbers in this field.
Required for Dispatch: For the particular component, the number that must be installed and operational on the aircraft when the aircraft is dispatched. You can enter dashes (-), zeros, and positive numbers in this field.
Name: The deferral reference ID. This is typically the MEL or CDL code and name.
Description: You can enter a detailed description of when the deferral reference is used.
Status: When you create a deferral reference, the default value is Inactive. Set this value to Active when the deferral reference is ready for use.
Requires Maintenance Operations Control (MOC) Authorization: Turn this switch on if the deferral reference requires MOC authorization before the fault can be deferred. Typically, MEL faults require MOC approval of deferral references, so you'd turn this switch on for these types of references. If MOC authorization is required, technicians are prevented from job stopping and deferring faults until the deferral reference request is approved.; Turn this switch off to allow technicians to defer faults without the involvement of MOC. For example, you might want to turn this switch off for long-term deferral references that do not require MOC authorization.
Severity: This customizable list displays the different types of severities such as MEL or CDL. To see a severity type in the list, it must have at least one class associated with it in the database.
Class: The class associated with the severity type. For example, a MEL severity type might be class A, B, C, or D. (In the database, each class must have a default deadline defined).
Default Deadline: Displays the default deadline (in days) for the severity and class. For example, MEL C is 10 days.
Use Custom Deadline: Use this switch to indicate that you want to use a custom deadline for the fault deferred under the deferral reference, and then complete the associated custom deadline.
Custom Deadline: After you indicate that you want to use a custom deadline for the fault deferred under this deferral reference, you can enter the custom deadline in Days, Flight Hours, and/or Cycles. You must specify at least one deadline type.; You can use a zero (0) or a positive integer for days or cycles. For flight hours, you can use a zero (0) or a fractional value up to two decimal places.
Conflicting Deferral References: List all the deferral references configured that are in conflict if this deferral reference is selected.
Associated Deferral References: List of all the deferral references configured that are associated with this deferral reference.
Operators: The operators to which the deferral reference applies.
Applicability Range: The applicability range to which the deferral reference applies. The same fault on different aircraft might require different references. When technicians select deferral references, they only see references in the selection list that are applicable to the aircraft that has the fault they want to defer.
Recurring Inspections: List the recurring inspections that must take place after a fault is deferred using the deferral reference. Recurring inspections are requirement definitions that should have the FOLLOW class. This class ensures that Maintenix automatically initializes the follow-on requirements when the fault is deferred, even if the requirement must be initialized for more than one fault on the aircraft at the same time. If you choose another class of requirement (such as REQ), only one instance of the requirement can be initialized against an aircraft at a time.; While editing a deferral reference, a dashed red line surrounding a recurring task definition indicates that the task definition is obsolete. While viewing a deferral reference, obsolete task definitions are identified with red text.; Note: The applicability of the Recurring Task definition must match the applicability of the deferral reference.
Subtasks: List the subtasks that need to be tracked for the deferral reference. These could be pieces of work listed in the AMM, or reviews and approvals by different groups.
Operational Restrictions: List the operational restrictions that result from this deferral reference.
Maintenance Actions: List all the maintenance actions that must take place in order to assign this deferral reference.
Performance Penalties: List the performance penalties on the aircraft when this deferral reference is selected.
Capabilities: Identify downgrades to aircraft capabilities due to invoking the deferral reference. For example, invoking the deferral reference could reduce ETOPS 120 to 90 or it could downgrade the Wi-Fi capabilities of the aircraft.