In this section we will learn that failures and defects are common phenomena in the work place. The result of a failure can be disruptive, catastrophic, inconvenient and expensive.

Operators using the Equipment to produce goods or deliver a service are usually the first to observe a failure. Important information that should accompany the registration of the failure includes the conditions that prevailed when the observation was made. Together with this the failure type and other observation detail needs to be supplied before an inspection Work Order is raised to verify the failure. Depending on the severity of the failure, the inspection Execution Order may trigger more Work Orders. The particulars of the failure (in some industries referred to as a notification) can be updated with new data as and when it becomes available. Changes can be made to the Execution Order progress status, failure status, codes and conditions.

An observation will typically be an incident on the factory floor where an employee observes a potential problem such as a water leak, oil leak, broken window, lights that are not working, an electrical motor that works but is making a louder than normal noise etc. A failure can be regarded as an incident that occurred and has an effect on its surroundings. Examples include a conveyor belt that stopped working, car radio that is not working etc.

A failure describes the inability of a piece of Equipment to achieve a desired standard of performance. A failure is expressed in terms of a total function loss or degradation of a system function. Defects are normally associated with specific vendor item numbers. Defects are registered as a result of a failure whereby it has been established that a specific vendor item number caused the failure. Defects are used as part of failure analysis to identify specific vendor item numbers which is the cause of specific problems.

The process for registering a Failure as well as defect is illustrated in the following process. Once a Failure has been raised the user can register a Execution Order for investigating the fixing of the Failure. It is also important to realise that a Failure can be registered from an Execution Order. While doing a specific Execution Order (e.g. wash the vehicle) an observation was made (e.g. that the vehicle is leaking oil). Depending on how the maintenance environment is managed this might in certain environments immediately become a Execution Order. In most instances it will be logged as an observation and the maintenance planner will decide how important or critical the observation is and when it must be corrected.

Failure Register Features

Failure Register has the following main features:

Note

This Failures list view is a display of all the registered failures. Failures can be created from various sources. These include:

  • From an Execution Order
  • From a Contract Specific line
  • From an Incident
  • From the Specific register

Task

Description

Failure Register

Create a new failure record with the create form.

Participants

This tab displays the participants registered against the selected failure record.

Setup

Use this button to define characteristics and detail for failure, and on the Participant the set up of defect codes, ageing and load of related images.

Create

Create new maintenance execution order from the participant.

Status History

This function is used to view the status history of the failures.

Status

The function is used to change current status of the Failure and the Record Status.