Failure Codes - Maximo

The Failure Codes application is to build and display failure hierarchies, which help you construct accurate histories of the failures that affect your assets and operating locations. After reporting and analyzing failure trends, you can take preventive measures. The identifier of a failure hierarchy is the failure class. You can enter this code on Asset and Location records when you want to report work done on them, and then analyze failure trends for them.

A failure hierarchy is a set of data on problems, causes, and remedies for asset and operating location failures. Groups of data called failure codes are linked in parent-child relationships to form a failure hierarchy. Its failure class identifies each hierarchy.

A failure hierarchy resembles other Maximo hierarchies. There is a top-level category, or failure class, that has one or more levels of failure codes below it. Examples of failure codes are: PROBLEM, CAUSE, and REMEDY. Each failure code can have one or more child failure codes. See the sample failure hierarchy below.

sample failure hierarchy
Fig 5.1 Sample maximo failure hierarchy

Partial Failure Hierarchy for a Packaging Line:
In this example, the failure class PKG has three child failure codes, HYDRAUL, ELECTRIC, and VALVES, which can each be a PROBLEM. The children of the codes HYDRAUL and VALVES are also shown. These can be CAUSES. There could be an additional level (or levels) below CAUSE that is assigned the type REMEDY.

Understanding the Failure Code Hierarchy:
A Failure Class is the name used to identify a failure hierarchy. By default Maximo uses a three level hierarchy that is built on a Problem, Cause and Remedy framework.

1. The PROBLEM is the symptom. What looks or feels broken? Problem failure codes are added, viewed, modified, and deleted in the Problems table window on the Failure Codes tab.
2. The CAUSE creates the problem. Why did the problem occur? Cause failure codes are added, viewed, modified, and deleted in the Causes for table window on the Failure Codes tab. Note that the Causes for table window is paired with the Problems table window.
3. The REMEDY is the correction. What will fix the problem? Remedy failure codes are added, viewed, modified, and deleted in the Remedies for table window on the Failure Codes tab. Note that the Remedies for table window is paired with the Causes for table window.


Each level in the failure hierarchy beneath the failure class can contain one or more failure codes, which "belong to" the failure code in the next higher level. An individual failure code can have multiple children; each child in turn can have one or more child failure codes.

Screen Shot displaying the Failure codes
Fig 5.2 Sample maximo failure hierarchy

Creating Failure Codes:
You use the Failure Codes application to create and view failure hierarchies. These hierarchies represent the identified causes of asset and location failures, and the identified solutions to these failures.

Building a Failure Hierarchy:
Failure hierarchies are built from the top down. You navigate the failure hierarchy from top to bottom. A Failure Hierarchy can be created all at once, or completed partially and added to later as necessary. You can use existing failure codes and/or create new ones to build the hierarchy.

- You can select existing failure codes by clicking the Select Value icon next to the field.
- You can create new failure codes by typing a value into the field. Maximo will attempt to match the value you entered with an existing failure code value. If one already exists, Maximo copies it into the field. If one does not exist, Maximo displays the Select Value dialog box. Click Continue to accept the value.


The procedures for adding Problem, Cause, and Remedy level failure codes are the same with one exception: selecting the parent for Causes and Remedies. All Problem failure codes are children of the Failure Class, but note the labels for the Cause and Remedy tables, which indicate the parent levels for the records in each table window. The Cause and Remedy table windows are both paired table windows, their labels reflect the selected row in the table above.

Managing Failure Codes:
Failure reporting lets you identify and track asset and location failures. Entering Failure Class and Problem Code data on work orders provides data that can be used for failure analysis. You use the Failure Reporting Sub tab of the Quick Reporting application, and the Failure Reporting tab of the Work Order Tracking application to record failure data.
Failure analysis is how you examine your failure history data, reported over a significant period of time. You use asset or location failure reports to look for breakdown trends, average time between failures, and so on.
By correlating this failure information with other data available to you, for instance, preventive maintenance schedules for an asset or location, you can develop ways to reduce or limit future failures. For example, you might want to review your preventive maintenance schedule, or you might be able to identify a branch of faulty inventory items

You build failure hierarchies in the Failure Codes application. A failure hierarchy is a tree-type structure that shows relationships between identified problems, causes and remedies for asset and operating location failures. Failure hierarchies are built from the top level, the failure class, down.

To build a failure hierarchy, complete the following procedures:
To create the first level of the hierarchy:

1. On the Failure Codes tab of the Failure Codes application, click New Failure Code and, if necessary, enter a value in the Failure Class field.
2. In the Failure Class Description field, enter a description. Click Long Descriptionif you need more space.
3. Under the Problems table, click New Row.
4. In the Problem field, enter a value or click Select Valueto select a problem.
5. In the Description field, enter a description. Click Long Descriptionif you need more space.
6. Repeat steps 3-5 for each problem in the hierarchy.
7. Click Done, and then click Save Failure Code .


To create the second level of the hierarchy:

1. In the Problem table, select the failure code to which you want to add a cause, or child.
2. Under the Causes table, click New Row.
3. In the Cause field, enter a value or click Select Value to select a cause.
4. In the Description field, enter a description.
5. Repeat steps 2-4 for each cause you want to add to the selected problem in the hierarchy.
6. Click Done.
7. Click Save Failure Code .


To create the third level of the hierarchy:

1. In the Causes table, select the failure code to which you want to add a remedy, or child.
2. Under the Remedies table, click New Row.
3. In he Remedy field, enter a value or click Select Valueto select a remedy.
4. In the Description field, enter a description.
5. Repeat steps 2-4 for each remedy you want to add to the selected cause in the hierarchy.
6. Click Done.
7. Click Save Failure Code .


To copy a failure hierarchy:

1. On the Failure Codes tab, display the record to which you want to copy a failure hierarchy, or click New Record , and in the Failure Class field, enter a value.
2. From the Select Action menu, select Copy Failure Hierarchy.
3. From the Copy Failure Hierarchy page, select the check box for the failure class and problem that you want to copy.
4. Click OK.
5. Click Save Failure Code .
Add Comments :

Login

Register