Report a Fault
Explanation
This activity is used to report a failure or fault for a vehicle or serial.
Failures and faults can occur during an operation or during the maintenance
of a vehicle or serial.
If the fault is to be created as a pending maintenance event, create
the fault from the Manage
Fault Information page, Faults page,
Flight Log/Faults tab or select the Report
Fault option in the Report Fault assistant.
It is also possible to register faults that have already been repaired and for
which you only want to generate a fault history record. To do this, select the
Report Already Repaired Fault option in the Report
Fault assistant. If the fault is already created (as a pending
event), you can use the Quick Reporting of Pending Event
option to finish the event.
Following are some of the information that can be entered when reporting
a fault:
- A description of the fault and the serial for which the fault is registered.
- The date and time the fault was discovered. The default value is the
same as the date in the Last To Date for the latest operation
logging on the serial or the current date/time. This is dependent of what has
been set up as the value to be defaulted in object property DEFAULT_FAULT_DATE.
The defaulted date can be changed provided that the fault, if it is to be deferred,
has not been approved.
- The person category of the person reporting the fault. If a default
category exists for the current user, this value appears automatically.
The default information can be changed, if needed.
- The product model. The product model connected to the template structure
of the serial appears by default. If a serial is not connected to a product
model (e.g., serials that are not on the topmost level of a structure),
a product model should be entered manually.
- The function breakdown of the fault. Depending on the value entered,
the system attempts to populate the parent functions. For instance, if a
bottom function is entered, the sub function and function are populated
if the function breakdown has been defined.
- The fault code, which must be valid for the given function breakdown.
- Additional information on the fault. This information will be transferred
to the Mx Event Remark field for the corresponding maintenance
event.
- For faults reported on a flight log, a flight operational plan ID (flight
number) may be entered. This is the flight on which the fault was discovered.
- Additional information if the fault is to be deferred. To defer a fault,
enable the Enable Fault Deferral option and enter required
deferral information, e.g., the deferral list/item code, the number of days
the fault is to be deferred or the operational add on value, the reason
for deferring a fault. The deferral item definition contains standard settings
for the deferral such as number of days, operational parameter settings
or a combination of both. Note: If the number of days or
add on value is automatically suggested based on the deferral definition,
it is possible to change the value to a lower value.
- Report actions taken to fix a fault.
- Post maintenance check information for the fault. If a post maintenance
check definition has been defined for the fault function entered on the
fault, the post maintenance check definition will automatically be defaulted.
If applicable, the defaulted value can be changed.
- Connect one or more documents and media items to the fault record via
the available options in Attachments. When
the fault is deleted the connection to the attached document(s) and media
items will also be deleted.
If sign off requirements exist for the function breakdown of the already
repaired fault, no sign off will be performed for the fault. To register faults
that have already been repaired, select the Already Repaired
fault execution when reporting the fault.
Prerequisites
- Persons must have been registered in the
Person page.
- Products and models must have been defined and valid functions registered
per product and model.
- Fault codes must have been defined.
- The number of levels required for the function
breakdown must have been defined. For more information, refer the
activity Verify or Adjust Default Object Properties.
- If functions are to be reported on the fault, fault codes must be connected
to the functions. For more information on registering fault codes for a
function breakdown, refer to the activity Define Fault Function.
- If reporting an already repaired fault and sign off requirements are
connected to the function breakdown, these sign off requirements will not
be considered.
- If the fault is to be reported on a flight log, the flight log should
be in the Open status.
System Effects
- A pending maintenance event is created when the fault is registered
with the Pending Fault fault action.
- A serial fault history record is generated when the fault is registered
with the Already Repaired fault action.