360° Strategic Asset Management > Common > Failure Register > Failure

This function allows the user to manage actual observation and failure occurrences. “Create new request form” from where a new record can be registered. Certain fields of the form will be defaulted from the registered failure.

It provides the following functionalities:

  • Register an observation or failure
  • Confirm an observation or failure
  • Raise a job-card to investigate or resolve an observation or failure
  • Record defect information against the failure for analysis purposes
  • Record long text failure detail

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

Fields

Field name

Field description

Application

Select the correct classification for the failure record, Internal for observations/ failures within the organisation between different divisions/departments, or External for observations/failures to external customers.

Category

This category indicates that the record created is a failure and observations of potential problems are also registered as failures. This field will be added automatically and cannot be changed.

Classification

The classification describing the severity of the failure or observation that needs to be logged. The user must select the classification from the available lookup.

Type

The type describing the failure or observation and in this instance it always will be of type function loss and cannot be changed by the user. The field value will be automatically added.

Customer

Use the lookup button to select the applicable customer. This is more for billing purposes and set-ups regarding the cost allocation to specific customers. Customer will only be available if the application is of type "External".

Responsible Org

The user may select the organisation responsible for the management of this failure.

Organisation structure

This field defines the structure code of the responsible organisation and the field value will be automatically added from the organisation information.

Observed by

Select the ID of the person who observed the failure/observation. The current logged in user's detail will defaulted into the field. But another user can be selected.

Date observed

Add the date when the failure was observed.

Reported by

Select the ID of the person who reported the failure/observation. The current logged in user's detail will defaulted into the field. But another user can be selected.

Date reported

Add the date when the failure was reported.

Short Description

Add short detailed description of the failure.

Object code

Select the correct object code to register against the failure.

Structure code

This field displays the Position (Structure Code) of the object and defines where on the structure the failure/observation occurred. This field are populated from the object baseline, and may never be added, changed or deleted manually, only by process.

Failure code

The field defines the object where the failure was observed/occurred.

Specific ID

Select the applicable specific id from the lookup. Only objects of the selected object type are available for selection. This field defines a unique identifier for the specific object that this failure was registered for.

Specific description

Description of the specific ID and will automatically be added.

Maintenance register

This button will be activated once the object and specific ID are captured, and IF the specific ID is registered in other execution orders this enables the user to VIEW the execution register for the specific object that was selected in this failure.

Incident register

This button will be activated once the object and specific ID are captured, and IF the specific ID is registered in other failures this enables the user to VIEW the incident register for the specific object that was selected in this failure.