Failure Analysis enables maintenance users to track an asset failure from the time it is reported until its resolution. Statistics from their collected failure data provide them with information on why an event occurs and causes asset failure. They can then take the necessary steps to eliminate that event. Additionally, they can use the failure statistics, among others, to help them formulate their Reliability-Centered Maintenance (RCM) program.
Failure hierarchies that support multiple-level failure reporting provide effective root cause and reliability analysis. For specific Asset Groups, each failure (problem) has a defined number of root causes, with each root cause having a defined number of resolutions (remedies).
1. First step is to define Failure Codes. There are three main Failure Code Types:
- Failure Code
- Cause Code and
- Resolution Code
3. If the Failure Set that maintenance users are creating is similar to an existing Failure Set, they can copy failure codes from an existing Failure Set.
4. Failure sets are then assigned to Asset Groups. Each set provides Asset Group-specific information on the possible failures of an Asset Group, the possible causes of each failure, and the possible resolutions for each cause. Assets within an asset group inherit the assigned Failure Code Set.
5. Failure data collection for an asset is performed by entering failure tracking codes, when creating the failure work order or when completing it.
Maintenance users or supervisor can analyze failures that are reported against assets with the Failure History and Failure Analysis pages.
The Failure History page displays detailed failure data, reported at the work order level. The Failure Analysis page aggregates failure data, based on the user-selected View By and displayed measures, such as Mean Time Between Failures (MTBF), and Mean Time To Repair (MTTR).