Maintenance, Repair & Operations

Reduce Repeat Repairs with This Method

Aug. 19, 2019

if you suspect you've got repeat repair jobs, implement this method.

Consider implementing this method if you suspect you've got repeat repair jobs.

For it to work, you need a computerized maintenance management system (CMMS) and precise failure (cause) codes. Be sure to have an “other” code so people aren't forced to pick a wrong one to complete the form.

Each time a repair is performed on a given asset, your CMMS will be updated with relevant information, including failure code, asset number, tech ID, date, and start/stop times.

If you've set up your asset information correctly, your CMMS can generate a report by asset type because that information is recorded under the asset number.

Let's say it seems you've replaced far too many fan belt motors over the past year. Have the CMMS generate a report by asset type fan belt and show asset number, date, duration, and tech.

Export the report to a spreadsheet. Sort by some significant variable from low to high. If you sort by asset number, do you see assets that stand out?

Perhaps a tech or two does the repair incorrectly (improper tightening, wrong belt dressing). Sorting by tech will tell you only which techs did the most repairs. If you sort again by duration and then by date, you may see a correlation between repair speed and failure rates.

About the Author

Mark Lamendola

Mark is an expert in maintenance management, having racked up an impressive track record during his time working in the field. He also has extensive knowledge of, and practical expertise with, the National Electrical Code (NEC). Through his consulting business, he provides articles and training materials on electrical topics, specializing in making difficult subjects easy to understand and focusing on the practical aspects of electrical work.

Prior to starting his own business, Mark served as the Technical Editor on EC&M for six years, worked three years in nuclear maintenance, six years as a contract project engineer/project manager, three years as a systems engineer, and three years in plant maintenance management.

Mark earned an AAS degree from Rock Valley College, a BSEET from Columbia Pacific University, and an MBA from Lake Erie College. He’s also completed several related certifications over the years and even was formerly licensed as a Master Electrician. He is a Senior Member of the IEEE and past Chairman of the Kansas City Chapters of both the IEEE and the IEEE Computer Society. Mark also served as the program director for, a board member of, and webmaster of, the Midwest Chapter of the 7x24 Exchange. He has also held memberships with the following organizations: NETA, NFPA, International Association of Webmasters, and Institute of Certified Professional Managers.