Use this activity to review fault thresholds so recurring faults on a system are not missed when you plan the next maintenance window. This is a general process in 7.46.1.1 Review all Upcoming Maintenance Requirements. It is not in the main sequence of open-task, open-fault, and opportunistic-task review. See Line Maintenance Planning.
A fault threshold sends an alert when a specified number of faults occur against a system within a specified number of days. For example, five faults in three days against system 28-00. Each time a fault is raised, CAMO checks whether a fault threshold exists for that configuration slot or any parent configuration slot. If a threshold exists, CAMO increments the fault total.
Faults designated as no fault found, raised in error, or possible faults are not added to the total. You can also limit a threshold to specific tail numbers by specifying an applicability range.
Threshold mode is either of the following:
When the threshold is exceeded for the specified period, an alert is sent to all roles assigned to the alert.
This activity is not available on IFS Cloud Web. Review existing thresholds in CAMO. Do not use due date, extended due date, usage due, or overdue on the Open and Deferred Fault page as the definition of a fault threshold. Those fields belong to the due-before-next-window check. See Review Aircraft Open Faults.
This activity is a review. It does not create a fault threshold.
To see how to create a fault threshold, refer to Line Maintenance and MOC / managing faults and shop findings / Create fault thresholds in the IFS CAMO user guide. Creating a threshold is not part of this review.
Use this procedure after a threshold alert, to see the related open and deferred faults. These pages are not the fault threshold list.