Related Topics:
	Tasks

Corrective Tasks

Corrective maintenance consists of the action(s) taken to restore a failed component to operational status. Corrective maintenance is performed at unpredictable intervals because a component's failure time is not known a priori.

Corrective tasks:

• Always bring the block down.

• May bring the system down.

• Require spare parts.

In addition to the common task properties, the following options are used to configure corrective tasks in the Maintenance Task window:

• Task Scheduling allows you to specify when the corrective task will be performed.

• • If you choose Upon item failure, the task will be initiated upon failure of the component.

  • If you choose When found failed during an inspection, the task will be initiated if the component is found to be failed at the next scheduled inspection. This is useful in the case of "hidden failures" (i.e., failures that are not apparent until an inspection is performed) and in cases where the component is not considered mission-critical and repair can wait until the next scheduled maintenance.

  • • If a preventive task takes place before the next inspection, then preventive maintenance (not corrective maintenance) will be performed to restore the component. The downtime, etc. will depend on the preventive task properties.

    • If a corrective task is performed upon inspection and an inspection finds the component failed, then the total downtime includes the full inspection duration followed by the corrective task duration.

If you have selected to perform a corrective task upon inspection and an inspection or preventive task does not occur after the failure, then the component will never be restored. This could happen under either of the following circumstances:

• • • Neither an inspection nor a preventive task is specified for the component.

and/or

• • • The conditions have not been met to perform an inspection or preventive task.

• Basic Repair Properties > Spare Part Pool allows you to choose or create a spare part pool that will be used in performing the task. If a spare part pool is not assigned, it is assumed that unlimited free spares are always immediately available.

For corrective and preventive tasks, a crew is not engaged unless/until the spare part is available. The total time for the task consists of:

• • The time to complete corrective and preventive maintenance (based on the corrective task or preventive task properties).

PLUS

• • The longer of the following times:

  • • The time to obtain the spare part (based on the spare part pool).

OR

• • • The time to obtain an available crew (based on crew availability) and any logistical delay time associated with the crew.

For example, if the component fails at 10 hours (on the system clock), the corrective task will take 5 hours, the time required to obtain the spare will be 48 hours and the logistical delay time associated with the crew is 8 hours, then:

• • The spare will arrive at 58 hours (on the system clock).

  • The crew will be engaged at 50 hours (on the system clock).

  • The maintenance will be completed at 63 hours (on the system clock).

  • The total time for the corrective maintenance will be 53 hours (48 for the spare plus 5 for the task).

  • The crew will be engaged for 13 hours.

If the spare part is available without delay and all other conditions are the same, then:

• • The crew will be engaged at 10 hours (on the system clock).

  • The maintenance will be completed at 23 hours (on the system clock).

  • The total time for the corrective maintenance will be 13 hours (8 for the crew plus 5 for the task).

  • The crew will be engaged for 13 hours.

• Task Consequences

• • Does this task bring the system down?: By default, corrective tasks will not bring the system down unless having the component down brings the system down based on the reliability-wise configuration in the diagram. If you answer Yes, the task will bring the system down even if the task has a zero duration. This forces the task to be included in the count of system downing events, regardless of the task’s duration.

  • Does this task bring the item down?: It is assumed that a component will always be down when a corrective task is performed, even a task with a zero duration; thus, this option cannot be changed.

© 1992-2013. ReliaSoft Corporation. ALL RIGHTS RESERVED.