Follow the steps in this workflow to record a non-routine or a shop
finding—both called a fault in
Maintenix—while working on another task, be it an
inspection task or other type of work.
- The initiating task is either active, in work, or
completed.
When you record the fault from a task,
Maintenix
associates the fault to that task, which is referred to as the initiating task.
If the fault was addressed before you had time to record it in
Maintenix, you record the fault and close it immediately. For faults that are not
addressed—because the work must be done later during the visit, or the fault must be
evaluated by the maintenance controller—you record the fault and leave it open.
When raising a fault, you can choose to reuse an existing fault definitions, or create an ad hoc task.
- Do one of the following:
- In the Barcode Search field, scan or
enter the barcode of the task, and press Enter.
- On the Task Search page, enter your
search criteria, and click Search.
- On your to-do list, My Tasks tab, select the check
box of the task.
Depending on whether the fault is addressed
or not, follow the correct procedure from one of the following:
Use these instructions when you found a fault as you were working on a task, and
fixed the fault immediately.
- On the Task Details page, click Found Faults.
- On the Raise Logbook Fault page, select Log fault and close or Log fault and leave open.
- To use a reusable fault definition, in the Fault Registration area, do the
following:
- Click Select Fault Definition
.
- On the Select Fault Definition page,
search for relevant fault definitions by entering the fault definition name, or by
selecting the failed system, and click Search.
- In the list of fault definitions found,
select the fault definition.
- To raise an ad hoc fault, in the Fault Registration area, provide the required information. Note the following:
- Logbook Reference: If the fault was first recorded in a logbook,
enter the logbook reference number.
- Failed System: Click
.
Click
next to the aircraft until you see the failed system.
Select the radio button beside the ATA chapter where the fault occurred.
- Resolution Config Slot: If the
fault was resolved on a different ATA chapter (resolved system) than the initially
reported ATA chapter (failed system), start typing the name or ATA code of the
config slot on which the issue was resolved, and then click the result from the
list.
- Fault Description: Enter the description of the fault, exactly as
it is written in the logbook.
- For faults you are raising and
closing immediately, in the Corrective Action area, provide the required information. Note the following:
- Corrective Action: Enter what you did to resolve the
fault; if this information is in the logbook, enter it exactly as it
is written in the logbook.
- Repair Location: Update the location where the fault
was fixed, if necessary.
- Labor Skill: Select the skill that was used to resolve
the fault.
- Hours Spent: Enter the number of hours spent to
address the fault.
- For faults you are raising and
leaving open, in the Suggested Corrective Action area, provide the required information. Note the following:
- Independent Inspection Required: Select if the work
that will be done to fix the fault must be inspected.
- Request Engineering: Select if you want this fault to
be sent to your organization's engineering department for assistance.
- In the Fault Details area, provide the required information. Note the following:
- Recurrence Of: If this fault is possibly a recurrence of a fault
that occurred in the past on this aircraft, the name of the previous fault is
shown; if it is not the correct fault, click Select Recurring Task
to select the correct fault.
Tip: You can record measurement values that provide
relevant details for the fault by clicking

above the table.
- Click OK.
- If this is potentially a recurring fault, but the
Recurrence Of field was
empty when you clicked OK, the Find
Recurring Fault page opens. Select a fault that the current fault is a
recurrence of, or select N/A if not applicable, and click OK.