Once upon a time, long ago (2005), Dave Gasdia had published an article describing how to expand the Failure Hierarchy. Unfortunately, my Google skills are failing me, and I can't find a link to it this morning (but I do have a printed copy!). I loved the idea. Here's an example we encountered, much like you have:
OOTB, the 2nd level -- the "Problem" level -- would be used by Work Order Tracking, in combination with the Location and/or Asset, to warn that you might be creating a duplicate Work Order. So suppose we had a dorm room A612. A student in room A612 reports a sink leak in his room. That is, FAILURE = sink, PROBLEM = leak. Suppose he or a roommate also report a shower leak; that is, FAILURE = shower, PROBLEM = leak.
Here, Maximo would pop up a warning that there's an existing Work Order for this room for a 'leak'. Well, yes, but it would be more useful to know that there was already a Work Order for a shower problem. In this example, it's obviously not a duplicate, both Work Orders are necessary.
The article described how to add a new top level and shift everything down. So, basically I could create a new top level as the Failure "Object" -- in this example, dorm room. (And, while at it, set that as the default Failure on the Location or Asset record.) Then next level down would now be the Failure Class, e.g. sink or shower. Then each of those would have their Problems, Causes, and Remedies.
Referring back to Darren's screenshots above, with this 5-level setup, the top level might still be AIR, but the second level could contain things like MOTOR and FAN (and several others). The 3rd level could contain BEARING as a child of MOTOR and another entry for BEARING as a child of FAN.
Much more data to build out then/the hierarchy becomes more complicated, but it increases accuracy IMO.
------------------------------
Travis Herron
------------------------------
Original Message:
Sent: Wed January 17, 2024 04:11 AM
From: Andrew Jeffery
Subject: Maximo Failure History Code
Hi Tee,
There are two possibilities. Maximo HSE - Work Order Tracking (HSE) application allows reporting against component level.
For clients who only have base Maximo then you can still create a Task at COMP status and you can report failure on the task which can reference a different asset, then by navigating to the Activities and Tasks application, Failure Reporting will be found right at the bottom of the main page of that application.
Hope that helps - Andrew
------------------------------
Andrew Jeffery
Maximo SME
ZNAPZ b.v
Barnstaple
0777 1847873
Original Message:
Sent: Tue January 16, 2024 04:57 AM
From: Tee Yeow Hum
Subject: Maximo Failure History Code
Hi Darren,
Thanks for your reply.
Almost, but your reply is still useful. Using your example AIR, say we have problem code "bearing" and cause code "wear". However, how would you know if the bearing was on the motor or fan?
------------------------------
Tee Yeow Hum
Original Message:
Sent: Tue January 16, 2024 04:22 AM
From: Darren Hornidge
Subject: Maximo Failure History Code
Hello Tee,
Hopefully I am understanding your question. Within the Failure Codes application, you can create a failure class. In the Screenshot below, it is called AIR
The AIR class can have multiple PROBLEM codes such as MOTOR, FAN, COILS, FILTERS and each of these can have their own set of CAUSES and each cause can have its own SET of REMEDY codes.
As you mentioned, they are not very detailed however the analysis of these codes over time would be more than enough for a reliability engineer to zone in on the issues and make recommendations.
Thanks to Andrew Jefferey, you can see a lot of great detail on this topic at Maximo Secrets. Failure Codes and Failure Reporting – Maximo Secrets
Apologies if this was not your point but hopefully it is useful for you.
Daz
------------------------------
Darren Hornidge
Asset Care Systems Manager
Coca Cola Europacific Partners
0437215275
Original Message:
Sent: Mon January 15, 2024 03:23 AM
From: Tee Yeow Hum
Subject: Maximo Failure History Code
In Maximo, to report history, the problem code and the activity code is used. Organization will have to configure the codes to make it meaningful. As there's only 1 problem code, you will have to code with a string of statement that describes the component and how it fails, like a description of failure mode.
If the work order is tagged to the asset of say an Air Handling Unit (AHU) which is a package unit containing components of motor, fan, cooling coils, filters and variouis sensors, each of the problem code will need to describe the failure mode in a lengthy statement, I assume.
Examples: Motor bearing seized due to lack of lubrication, Motor winding burnt due to insulation failure, etc.
If the work order is tagged to the asset of motor as a child of the AHU, then the problem code can be "bearing seized due to lack of lubrication".
Is there a best practice?
Have anyone configure an additional fields such as component like bearings for capturing the object of the failure and causes?
------------------------------
Tee Yeow Hum
------------------------------