There are always people who are out to push their view of CMMS software coding, and then enforce it on an unsuspecting corporation whether they want it or not, and regardless of the flaws that are obvious.
The key issue with work order type codes are that they should not be repetitive, nor should their be any confusion about them.
For example, overhaul and service are both used interchangeably. If your system uses both of these then you are already in trouble. Another classic example is pretty much anything else plus "service".
The result? You dilute the worth of your work order coding - something that is essential to have well planned out if you are ever going to get a handle on your whole-of-life situation.
I would recommend using a code that represents one of the 7 maintenance types, plus one for reactive. This is something that comes from my own RCM background and needs to be used in conjunction with other similar thinking approaches. (like the "right level" to apply work order history)
Types of planned maintenance tasks
- PTIVE - Predictive Maintenance Tasks
- PTED - Predicted Tasks
- PRES - Preventive Restoration Tasks
- PREP - Preventive Replacement Tasks
- DTIVE - Detective Maitnenance Tasks
- DTED - Detected Tasks (Corrective)
- RTF - Run to failure
Over the next few weeks I am going to be visiting this theme a lot. Adopting a structure something like this does wonders for your maintenance history - but also puts you into a great position for zero based budgeting, Whole-of-Life management, and Risk-Distributed-Budgeting. (The Holy Grail)
No comments:
Post a Comment