You are on page 1of 7

November 15, 2009

11.0 FAILURE ANALYSIS

1.0 PURPOSE
This standard defines the process for performing Failure Analysis on assets at the Water Authority.

2.0 SCOPE
This standard applies to the Water Authority facilities and divisions involved in recording failure classes and failure hierarchies on assets and workorders.

3.0 DEFINITIONS
3.1 Cause Code - Defines the CAUSE of the failure and/or Problem. 3.2 Failure Analysis - Failure analysis is the process by which you examine asset or location failure history, reported over a significant period of time. Use any 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 equipment failures in the future. For example, you might want to review your preventive maintenance schedule, or you might be able to identify a branch of faulty inventory items. 3.3 Failure Reporting - Failure reporting is a long-term process where you gather data about failures so that you can analyze trends and take steps to avoid problems in the future. For example, in looking back over the failure reports for a pump, you might notice that the pump often breaks down about one week before its monthly preventative maintenance check is scheduled. You might decide to change the frequency of the PM checks to every other week, rather than every four weeks. You conduct failure analyses to review histories of asset and location failures over time. Look for issues such as breakdown trends or mean time between failures on printed reports. You can correlate this failure information with other data such as preventive maintenance (PM) schedules to develop ways to reduce or limit asset failures in the future. 3.4 Failure Hierarchy - A failure hierarchy is an organized set of Problems, Causes, and Remedies related to Asset and Location failures. The failure hierarchy is identified by its top-level component, called a Failure Class. There must be an associated failure class for each Asset or Location that you want to report failures for. Groups of data called failure codes are linked in parent-child relationships to form a failure hierarchy. 3.5 Failed System – Defines the system where the failure occurred. This is tied to the type of system (i.e. - Sewage, Gravity). 3.6 Failure Class - Defines where in the system the failure occurred. This is tied to the type of Asset (i.e. - Meter, Pipe, Fire Hydrant). 3.6 Problem Code - Defines the PROBLEM of the failure. I.E. Leaks, Knocked Out, Blocked, Backed Up, etc. 3.7 Remedy Code -Defines the REMEDY to fix the failure/problem. Page 1

should designate responsibilities. 2009 11. the person creating the workorder will identify the Failure Class and Problem. as appropriate. including the Failure Hierarchy. If the work being completed is not applicable to a failure hierarchy. the workorder will automatically have this completed once the workorder is assigned an asset. or lack thereof. If the asset itself has already been identified with a failure class.0 RESPONSIBILITIES The following provides typical descriptions of responsibilities and accountabilities for implementing the failure analysis process. As the workorder progresses. Cause and Remedy codes may be left blank.November 15.4 Unless it is not required. Cause and Remedy will be noted on the workorder log.3 Levels of the hierarchy can be added at anytime. 5. the Problem.0 FAILURE ANALYSIS 4.1 Unless required.3 Maintenance Technician – Responsible for performing the initial steps in completing the Failure Analysis.7 The Planner/Scheduler has final approval on the Failure Hierarchy. Additional notes related to the Problem.Responsible for the review and approval of workorder documentation.6 Failure Hierarchy Completion: If possible. 5. including the Failure Hierarchy. Completion of the Failed System field is optional. the Failure Hierarchy need only be completed at the Parent level of the working being performed.Responsible for completing all workorders and ensuring that the workorder is documented with the appropriate Failure Hierarchy. 4. Page 2 . 5. which includes the proper recording of the Failure Class. Supervisor and Superintendent to perform a review of the Failure Hierarchy prior to submitting the workorder for final completion. Problem. This will represent what asset class failed. it is responsibility of the Maintenance Technician. 4. Cause and Remedy of the workorder will be documented.2 Supervisor .4 Planner/Scheduler . 4.2 Any person authorized to create or modify workorders can document the Failure Hierarchy as work progresses through the completion of a workorder and its tasks. 5. 5. Each Superintendent or Supervisor. These requests must conform to the definitions identified in this standard.0 INSTRUCTIONS 5. No workorder will be marked with a status of COMPLETED until the Failure Hierarchy is final. These items may change during the course of workorder completion as more information is obtained during the work process. 5.5 During the completion of the workorder. all workorders will be documented with a Failure Class as defined in this standard. 4.1 Superintendent . Cause and Remedy. and the Problem.Responsible for the review and approval of workorder documentation. then the Failure Class will be noted as NA (Not Applicable). Changes to the failure hierarchy codes must be requested through the Maximo Support team and will be immediately completed. 5.

0.0 APPENDICES APPENDIX 11.A – Building a Failure Hierarchy – Maximo Example Page 3 . 2009 11.November 15.0 FAILURE ANALYSIS 6.

Maximo will attempt to match the value you entered with an existing failure code value. You can use existing failure codes and/or create new ones to build the hierarchy. You use the Failure Reporting subtab of the Quick Reporting application. causes. reported over a significant period of time. Failure Class and Problem Code data on work orders provides data that can be used for failure analysis. you might want to review your preventive maintenance schedule.0 FAILURE ANALYSIS Appendix 11.November 15. their labels reflect the selected row in the table above. you can develop ways to reduce or limit future failures. If one already exists. Failure hierarchies are built from the top down. and the Failure Reporting tab of the Work Order Tracking application to record failure data. Cause. Failure analysis is how you examine your failure history data. and remedies for asset and operating location failures. You can create new failure codes by typing a value into the field. Maximo displays the Select Value dialog box. Page 4 . CAUTION: Before entering Causes or Remedies. or completed partially and added to later as necessary. The procedures for adding Problem. and Remedy level failure codes are the same with one exception: selecting the parent for Causes and Remedies. click the appropriate row in the parent table window. for instance. A failure hierarchy can be created all at once.A . If one does not exist. 2009 11. It is not a required field. To change the table label. Groups of data called failure codes are linked in parent-child relationships to form a failure hierarchy. A failure hierarchy is a set of data on problems.Building a Failure Hierarchy – Maximo Example Failure reporting lets you identify and track asset and location failures. You navigate the failure hierarchy from top to bottom. Each hierarchy is identified by its failure class. For example. By correlating this failure information with other data available to you. For example. Click Continue to accept the value. but provides means to track failures at a “system” level rather than the Failure Class level. You use asset or location failure reports to look for breakdown trends. Maximo and Failure Hierarchies You can select existing failure codes by clicking the Select Value icon next to the field used in Maximo for recording Failure Hierarchies. All Problem failure codes are children of the Failure Class.0. or you might be able to identify a branch of faulty inventory items. and so on. NOTE: Failure codes can be used at any level of the hierarchy. which indicate the parent levels for the records in each table window. jammed" could be both a Problem and a Cause. check that the table window label reflects the correct parent for the failure code you are about to enter. but note the labels for the Cause and Remedy tables. Maximo copies it into the field. The Cause and Remedy table windows are both paired table windows. Entering Failed System. NOTE: Failed System is a Water Authority custom field and has been added to the Failure Analysis Program procedures. average time between failures. preventive maintenance schedules for an asset or location.

Maximo displays a message if a work order with the same Problem Code already exists for the asset or location! Failure Hierarchy Example This example demonstrates the steps you could use to build a three-level failure code hierarchy named PUMPS in the Failure Codes application. Click the links below to see how you build each level. you can enter a description.. Failure Class and Failure Codes To create the failure class and first level failure code of the PUMPS failure hierarchy in the Failure Codes application: 1. 2009 11. Page 5 .0 FAILURE ANALYSIS TIP: Using failure codes on work orders can help reduce the number of duplicate work orders that are entered in the system. click New Failure Code . In the Description field. enter PUMPS. The following figure shows a failure hierarchy for a pump: Failed System To create a Failed System selection. In the Failure Class field.g. This information will be configured in the system and made available via a drop down list. Pump failures. e. 2. On the Failure Codes tab of the Failure Codes application. a request must be submitted to the Maximo Support team with the Failed System Code and Description.November 15.

In the Description field. Problems The Problems table contains the top level failure codes in the hierarchy. You have now identified three main problems that could put the pump out of service. 5. enter LOW PRES. click LOW PRES to select it as the problem to which you want to add a cause. Next. 2009 11. or second level failure code that you create. You must save each level of the hierarchy before you can create or add to another level of the hierarchy.0 FAILURE ANALYSIS You have just created the top level of the failure hierarchy. Seal Leaking. you must first select its parent from the first level of failure codes. Housing Leaking. In the Description field. Causes You are now ready to start building the second level of the PUMPS failure hierarchy in the Failure Codes application. 2. and then click Save Failure Code . In the Cause field. Next. 8. Repeat steps 2-4 to insert the following additional causes for the problem of low pressure: HOUSING. For every cause. 3. Low Pressure. 1. 4. Stopped. click New Row. 3. Cause SEAL. enter Low Pressure. 1. Repeat steps 3-5 to enter the following additional problems: LOW VOL. 7. Problem Click Done.November 15. You have just created three causes for the problem of low pressure in this failure hierarchy. for these causes. In the Problem field. 2. 5. Problem STOPPED. Under the Problems table. you will create three failure codes in the top failure code type within this hierarchy. enter FITTING. enter Fitting Leaking. click New Row. 6. or children. 4. Under the Causes table. These problems are the first level of the failure hierarchy. In the Problems table. Page 6 . you can enter remedies. Cause Click Done. 6. and then click Save Failure Code.

Tighten Fitting. 7. 5. causes. You can add and delete problems. enter Replace Fitting.November 15. You have completed building a failure hierarchy. Repeat steps 2-4 to insert the following additional remedy for the cause Fitting: TIGHT FIT. Under the Remedies table. Page 7 . click New Row. In the Remedy field. 3.0 FAILURE ANALYSIS Remedies Take these steps to build the third and final level of the PUMPS failure hierarchy in the Failure Codes application: 1. and remedies to the failure hierarchy. Remedy Click Done. click Fitting to select it as the cause to which you want to add a remedy. In the Causes table. enter REPFIT. In the Description field. 4. 6. 2009 11. and then click Save Failure Code. 2.