How do you know if a given repair is required too often? In the typical maintenance organization, this determination occurs only when someone happens to connect the dots; it’s not actively looked for. When someone does connect the dots, there may be acknowledgement that, “Yeah, it seems like we’re doing this a lot,” but considerable time will pass before the cause is addressed.
First, you must actively search for the problem. From your CMMS, generate a report listing the last 100 repairs. Sort them by type and then by asset number. Now you can easily see any patterns if they exist. If you don’t see any, then go with a larger data sample.
Next, identify the three most common repairs and the 10 assets with the most repairs.
- For each of these repairs, what is the failure cause? Can a change in design, PdM, or PM eliminate that cause?
- If any asset is similar to other assets not on the list, then that asset needs attention. Maybe it’s an operator issue. If you see repeats on the list, then there is likely a root cause to determine.
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.