Stuart recommends: Most of the successful cost-tracking systems use VMRS coding. I personally have been using VMRS for 35-plus years. I also have stepped out of the box by adding a Reason for Repair Code (14) to track the costs after the PM inspection. Also, I want to see average inspection times per employee (because that’s what the boss wants to see—productivity).
Then, I want to see what was found and track those repair costs separately without digging deep into the system and shooting the technician for taking too much time on the PM. Here is an easy way to retrieve the data: Report not on the PM time, but what repairs required the PM inspection…too much data can be buried in the PM inspection code. The tech will do as requested, will make it fit and manipulate the time to fit.
Performing the PM within the standard repair times (SRT) may not be the most efficient PM. Be careful what you ask for, because you just may get it—a 1-1/2 hour PM—and you may find out later from a PM audit that it was a “paper PM” with all the boxes checked, but without substance. It is best to measure the quality, manage the time and motivate the players.
For more information, visit www.darrystuart.com or e-mail comments or questions to Darry at: [email protected].