I've seen it done a number of ways.
Some TPM models have hanging tags in the field then lists and eventually a WO to execute the repair. There are pros and cons to this. Many like the visual nature of hanging tags, etc but eventually if corrective work is to be done to correct the defect then the CMMS will be employed. Maybe tagging is a way to filter some out and communicate to operators.
Personally, I think it is wise to use your CMMS. While not all defects require a WO, most typically will. The CMMS is where we manage WOs so we already have a system hopefully that is mature and able to manage what we call a defect. Those defects that are not maintenance executed could be managed outside a CMMS but could also be managed inside the CMMS as well. A defect handling system will have to be merged at some point with the same resources executing CMMS work so why not use the same system and priority setting?
The other benefit to using the CMMS is the defects can be catagorized as to type or failure mode and some reporting could be done with all other CMMS data related to asset health.
I've never understood why defect elimination was ever presented as a separate process from normal maintenance process flow.
------------------------------
Randy Riddell, CMRP, PSAP, CLS
Reliability Manager
Essity
Cherokee AL
------------------------------
Original Message:
Sent: 09-07-2022 12:42 PM
From: Derek Brown
Subject: Defect Elimination programme
All,
I am keen to get your feedback, I have read and asked other professionals on the subject of defect elimination and where defects should be recorded and managed, some say all defects should be managed from the CMMS, however, other claim they thought it better on another platform, i.e. designated software/spreadsheet etc.
Thoughts?
------------------------------
Derek Brown
Grangemouth
------------------------------