Month: April 2022

FTMaintenance Select v.2.5.0.2 Release Notes

FasTrak SoftWorks, Inc. is pleased to announce the release FTMaintenance Select v.2.5.0.2, which incorporates the following:

Features

  • Asset Management
    • Access asset management functionality from a mobile web browser, including the ability to view asset details, log meter readings, and create service requests.
    • Identify the owner of an asset.
  • Inventory Management
    • Browse inventory items by storage location within a specific inventory.
    • Track an inventory item’s reorder point to easily identify when stock of an inventory item needs to be replenished.
  • Reporting
    • Generate a report that displays the response time to service requests and work orders.
    • Generate a report that displays the turnaround time of service requests and work orders.
  • Work Order Management
    • Improved usability of preventive maintenance work order scheduling functionality.

Solutions

  • Asset Management
    • Minor defect fixes and improvements to Asset functionality.
  • Inventory Management
    • Minor defect fixes and improvements to Inventory functionality.
  • Notifications
    • Minor defect fixes and improvements to Notification functionality.
  • Purchasing
    • Minor defect fixes and improvements to Purchasing functionality.
  • Service Request Management
    • Corrected an issue that prevented requesters from selecting an Asset on the Service Request.
    • Minor defect fixes and improvements to Service Request functionality.
  • Work Order Management
    • Minor defect fixes and improvements to Work Order functionality.
  • Work Order Scheduling
    • Minor defect fixes and improvements to Work Order Scheduling functionality.

What is Mean Time to Repair?

Maintenance technician using an asset that cuts sheet metal, one of the machines that will be included in Mean Time to Repair calculations.

Maintenance teams are commonly judged on how quickly they respond to asset failures. Mean Time to Repair (MTTR) is an important asset management metric used to help maintenance teams improve recovery times. This blog post shows you how to you calculate MTTR and how you can use it to improve your maintenance process.

What is Mean Time to Repair?

Defining mean time to repair (MTTR) is the first step in knowing how to use it. Mean Time to Repair is a maintenance metric that measures the average time required to repair an asset, from the moment an incident occurs until it is returned to service. It refers to the amount of wrench time that it takes to fix a problem. MTTR also demonstrates how quickly an organization responds when an unexpected breakdown occurs. This metric can bring visibility to problems with the maintenance process as it relates to making repairs.

The Benefits and Importance of Mean Time to Repair

There are several reasons that determining Mean Time to Repair is important, as well as benefits of doing so.

Discover Areas that Impact Downtime

Over time, comparing MTTR values helps maintenance teams assess whether there are issues with the asset, maintenance tasks, parts, staffing, scheduling, and/or employees. By making improvements in these areas, downtime can then be reduced. Responding to and resolving issues with assets quickly leads to more efficient production, which helps to retain customers and gain new ones.

Helps Evaluate Asset Performance

Mean Time to Repair provides a benchmark for maintenance managers to evaluate asset performance. It can also be used to identify assets that are candidates for replacement. Reports that display MTTR and related information can show how an asset is performing compared to similar assets. If one is performing significantly worse than others, the maintenance team can show there is cause for replacement.

Identifies Asset Outliers

One of the most important benefits is that Mean Time to Repair identifies asset repair outliers, assets that are significantly underperforming and the MTTR for them is high. Keep in mind that any number near the average of MTTR is not very helpful. It may be easier to determine outliers when more assets are being compared. If a few machines out of each similar group have a high MTTR, there is likely an underlying reason for it.

If an organization has many of the same kinds of assets, all assets of that type can be compared to see which of them have a high MTTR. Location and use of the machines matter as well, so the maintenance team needs to conduct a thorough analysis to find out why each of these machines’ MTTR is different.

Some questions to ask include, do these machines get misused by inexperienced technicians? Are some machines running beyond their rated capacity? It serves as a starting point to ask other subsequent questions, dig into the history of each asset, and examine what the causes of each asset failure were. If trying other ways to lower MTTR were unsuccessful, maintenance departments can question whether or not the assets need to be replaced.

Helps Shape Future Asset Buying Decisions

The results of calculating MTTR helps shape future asset buying decisions. They may get feedback from technicians as well since they are the ones doing the maintenance work. It’s worthwhile to ask if it is a make and model issue. If so, they can choose not to buy that same machine again. When an asset is brand new, it is will have an MTTR outlier, but it will usually be low, not high, so that number is not especially useful. But over the course of the asset’s lifecycle, looking for trends from a make and model perspective will help to identify outliers on the high end.

Who Uses Mean Time to Repair Information?

The information gathered from calculating mean time to repair is valuable to many people in an organization. It is especially relevant for maintenance managers, maintenance technicians, and production supervisors.

Maintenance Managers

Maintenance managers use MTTR to examine the maintenance jobs on certain machines that are taking the longest to complete and if there are ways to shorten the timeframe of these jobs. This can include a variety of assets and wrench times, but the key is finding outliers. If it’s determined that the MTTR is longer than desirable because of assets that are in poor condition, they may use that information to show upper management that the asset should be replaced.

Maintenance Technicians

Maintenance technicians may use MTTR to (informally) evaluate their own performance. It will help them reflect on what to improve that is in their control and what is out of their control. It allows them to see patterns in repairs that take longer or shorter periods of time. In some cases, it may help them to present a case for hiring more technicians. As a team, maintenance technicians can use MTTR information to set maintenance goals.

Production Supervisor

While the production manager or supervisor is not directly involved in the factors MTTR covers, they may be impacted by its results. If they are aware of the current state of MTTR on multiple types of repairs on specific assets, it can help them to understand that while there is an average downtime number on each type of machine, downtime overall will vary greatly depending on which asset is down, how major the repair is, and what it will take to fix the problem.

How to Calculate Mean Time to Repair

The Mean Time to Repair formula is shown below. Take the sum of all repair time (for similar repairs on an asset or group of assets) in hours and divide by the number of repairs that occurred within the specified time period.

 

It’s important to note that repair time can be defined as the time from the report of the problem to repair completion, or from the start of the actual repair work to completion. Most of the time, the latent period between when a problem occurs and when it is discovered is also included. Organizations will use one method or the other based on their needs.

The number of repairs is the total number of similar repairs done on the asset that MTTR is being calculated on within the specified time period. This formula gives the average time it takes to complete the repair process.

It’s worth noting that the MTTR calculation assumes that the tasks are performed sequentially (that is, in a standardized way and in the same order every time) and by appropriately trained personnel. Finding an ideal Mean Time to Repair heavily depends on the type of asset and the time required for each repair, which may vary greatly.  Desired timeframes for repairs to be completed must be adjusted for the asset’s complexity and age.

If you are just starting to calculate MTTR and don’t have multiple years worth of data to look back on, you can come up with a number by calculating MTTR for a group of similar assets and apply that number to a specific machine in that group. It may take two or three years to get a true benchmark, whereas initially, only educated guesses can be made. Getting a good number for each repair type on each particular asset or group of similar assets is the goal.

How to Interpret Mean Time to Repair

In order to benefit from the results of calculating mean time to repair, maintenance teams need to know how to interpret them. MTTR can serve as a benchmark for future comparison. Remember that the number will rise and fall over time based on the types of repairs that were done during the time period calculated. The number should be determined for each type of repair in an asset class or individual asset as they will be different. There is no one ideal MTTR number because it depends on the type of asset and type of repair.

Another thing to remember is that initial calculations are a benchmark. MTTR values in subsequent calculations may be higher or lower. A lower number may reflect that an asset is new, since less severe problems occur with newer assets. A lower MTTR number might also mean frequent, short repairs are being made, so it’s not necessarily an indicator of how well repairs are being performed.

If MTTR numbers are higher, that could mean more major repairs were completed during the last calculation period, or it could indicate other issues. It’s important to look into what might be causing an increase in those numbers to determine if those factors can be changed or not.

Calculating Mean Time to Repair should be done at longer intervals rather than shorter ones. For example, if MTTR was calculated for a year’s worth of repairs the first time, the maintenance team should wait at least another full year before calculating MTTR again. However, after the first two years, a smaller timeframe may be appropriate to use to get quicker feedback. Comparing MTTR numbers that are too close together will not give an accurate mean time, or average number when establishing a baseline, but after that point, a long time frame is not as crucial.

An MTTR report can show how an asset is performing relative to similar assets and help to build a case for asset replacement or reflect on maintenance efforts for that asset. Many underlying issues can impact MTTR, so it needs to be determined whether changes are needed to staffing, scheduling, or inventory management.

Ways to Improve Mean Time to Repair

The MTTR metric may also help to improve maintenance scheduling, which in turn will improve MTTR values. Maintenance managers may change the frequency of some preventive maintenance, allow more or less time to complete certain jobs, or make adjustments to which technicians complete which jobs. Other ways to improve Mean Time to Repair include:

  • Provide more in-depth training on asset function and repair techniques for new employees or as a refresher for existing employees.
  • Implement predictive maintenance sensors to alert maintenance departments of problems before they become emergencies, which will result in faster, easier maintenance jobs.
  • Continually update repair procedures and instructions to ensure they are performed in a standardized way.

What are the Limitations of Mean Time to Repair?

As with all maintenance metrics, there are limitations to MTTR. It doesn’t tell you where in the process an error or failure occurred. If MTTR is calculated over too short of a time period, the results will not be accurate. For some assets and types of failure, it takes several months or a year to gather enough data and determine an accurate number. For others assets and failure types, there may be enough data to calculate MTTR after a much shorter time frame.

In many cases, an increase in MTTR can reveal issues and a decrease can indicate improvements. However, it depends on the types of repairs being made. Major repairs take more time and increase MTTR while quick repairs can lower MTTR. Only repairs that are comparable to each other (apples to apples) can be included in the same MTTR calculation. Therefore, multiple MTTR numbers can be calculated for different types of repairs for the same asset. Either way, keeping track of MTTR over time helps maintenance personnel know how they’re performing.

Steps Included in Calculating Repair Time

Now that we’ve covered what Mean Time to Repair is, why it’s important, who uses it, and how to interpret it, next is to learn what tasks are included in the repair time calculation.

Diagnosing the Issue

Once the technician has been notified of the problem, the timeframe for calculating MTTR begins. The technician will come over to the machine and attempt to determine the issue. They may do an inspection, speak to the machine operator to learn more about the problem, and perform diagnostics.

Fixing the Issue

After the cause of the problem has been found, it’s time to fix the issue. Depending on what the repair is, this may be the longest part of the process. The machine is has already broken down, so production downtime has already been occurring. However, the technician will have to shut down the machine fully to begin the maintenance work. The time it takes to actually do the repair is measured closely. Any form of a lockout tagout procedure would also be included here.

Reassembling and Calibrating the Asset

After the machine is repaired, if needed, the machine is reassembled, aligned, and calibrated. If the maintenance work requires any disassembly of the machine, the parts need to be replaced.

Setting Up, Testing, and Starting the Asset Back Up

Lastly, repair time includes setting up the asset for production, testing its operation to ensure the repair fixed the problem, and starting the machine again. When the machine is fully up and running again, the period of Mean Time to Repair ends.

Calculate MTTR with FTMaintenance Select

Computerized maintenance management system (CMMS) software helps maintenance teams easily calculate Mean Time to Repair because all work order information including labor time records and individual repair records are recorded. This creates maintenance history, which stores and displays information about how long repairs took. It also holds data on how many and what type of repairs were done on each asset, what solved each maintenance problem, and information on the condition of each asset.

CMMS software also allows maintenance managers to make adjustments in the maintenance schedule to accommodate unexpected corrective maintenance work. The maintenance reports available in CMMS software help maintenance teams to calculate MTTR accurately.

FTMaintenance Select is a complete maintenance management software solution that can be used to track asset maintenance and repair time, including MTTR, build a maintenance history, track labor hours, and run asset reports. Request a demo today to learn more.

 

 

Asset Management Best Practices

A maintenance technician performing maintenance on a large piece of equipment as part of asset management best practices.

Managing assets efficiently has always been a significant challenge; however, asset management is a necessity for maximizing manufacturing profits. It serves as a cost saving measure to maintain and extend equipment life. Manufacturers rely on these machine assets to produce the products they sell and facility assets to support their manufacturing environments.

There comes a point when the cost of maintaining an asset exceeds the cost of replacing it, which is when a new asset should be purchased as part of asset management. Successful asset management is made easier by implementing best practices and with the help of CMMS software.

This article is part of a series of articles related to maintenance management best practices. Read our other best practice articles:

Importance of Asset Management

Asset management is an important part of maintenance because it keeps assets running smoothly, which leads to efficient production. When assets are adequately tracked and monitored, this ensures equipment is not continually breaking down. Maintenance managers have a lot to juggle and being able to manage assets effectively makes their job easier.

Assets have a finite useful life. The cost of the asset is spread out over the asset’s lifespan and, with maintenance costs, accumulates as the asset depreciates. However, proper asset maintenance ensures the asset’s life is maximized while minimizing maintenance costs. Once an asset is “paid off” through the revenue it generates, revenue brought in by the asset doing its job in production goes towards the organization’s profits.

Managing assets well is also important because it extends the lifespan of expensive, critical assets. It makes the maintenance team’s job easier in the long run because they can more easily predict when major repairs will be needed while emergency maintenance is lessened at the same time.

Maintenance is only one aspect of asset management. While it is the maintenance team’s job to repair assets, perform preventive maintenance (PM), and create a system where maintenance is more planned and predictable, some assets are meant to be run to failure without PM being done on them. Using assets that have already been paid off allows organizations to use money for other capital improvements.

Asset Management Best Practices

Invest in Asset Management Software

One of the best practices that should be applied to asset management is investing in computerized maintenance management system (CMMS) software that will support the most critical asset management requirements. A robust CMMS system will provide a central database for supplier information, warranties, site leases and more. It will also have tools to optimize the maintenance workflow.

Automate and Improve Data Collection

One asset management best practice is automating and improving asset data collection. Data collection and access can be improved by integrating a computerized maintenance management system (CMMS) software use into facility, vehicle, and manufacturing asset management. The asset management feature in the software ensures maintenance teams can quickly identify what equipment they have, where assets are located, and view service history to assist in troubleshooting.

In addition to manual methods, data is collected through equipment sensors, which are put in place to conduct predictive maintenance (PdM). These sensors are able to detect internal wear that can’t be directly observed. Advanced analysis of data for predictive maintenance may be achieved through machine learning and artificial intelligence. The Internet of Things (IoT) is where data used for PdM is collected by the sensors and stored in a database. In CMMS software, there may be triggers set to generate work orders based off of specific asset conditions.

Be Aware of all Assets Owned

Having an accurate census of all assets is helpful for knowing how many of them require maintenance and when. Being aware of all the assets an organization utilizes ensures maintenance can be tracked on each machine, vehicle, or facility. This knowledge can help to schedule maintenance with the least interruption for production and assign work orders based on which technicians are most knowledgeable and experienced with each asset.

Uniquely Identify Assets

It’s also an important asset management best practice to uniquely identify all assets using a standard naming convention. There are nearly endless ways to create abbreviations for assets that make sense for an organization. The key is to make them consistent and able to be universally understood by anyone in the organization who needs to use them.

Use GPS Technology to Track Mobile Assets Locations

Keeping track of mobile assets is important, especially for organizations in industries that have a lot of vehicles. GPS technology can pinpoint exactly where a vehicle is when it is out on a job. This is useful for determining how long certain jobs take (including travel time) and can be used to determine where to send assistance faster if a vehicle breaks down.

Create Asset Tags

For stationary assets, the use of asset tags can pinpoint a machine’s location within a facility. This ensures maintenance technicians get to the right asset at the right time to perform maintenance. Asset tags can also be scanned so that information about the asset can be viewed from a mobile phone or tablet.

Use an Asset Hierarchy

Another asset management best practice to implement is using an asset hierarchy. This allows maintenance teams to see how assets and their related sub-components relate to one another. These relationships help to determine where maintenance issues are occurring most.

Have a Robust Failure Tracking Program

A robust failure tracking program should always be part of asset management. This includes asset history found in CMMS software, using failure codes where applicable, and implementing sensors to collect data for predictive maintenance (PdM) when possible.

Prioritize Safety

Prioritizing safety is another best practice when it comes to manufacturing asset management. Maintaining assets well requires attention to detail, which can make the difference between a machine operating safely or not. A system should be set up so that asset management procedures can be accessed easily. Adjustments to these procedures should be made to improve safety when necessary.

Maintain Adequate Documentation

Another best practice for asset management is to maintain adequate documentation on assets. User manuals and equipment schematics are two primary types of documentation that need to be readily available and should be stored in the CMMS.

Maintenance teams should find paper documentation and scan or enter the information into the software. If necessary, they need to look for digital files on various network drives or in email threads. They can also go to the source to get documentation, which is the vendor or manufacturer. Another way to get the documentation needed is to search the manufacturer’s website, call a representative, or send them an email.

Beyond documentation about the assets themselves, maintenance teams should document repairs and preventive maintenance tasks in the maintenance management software. Some information, such as asset history, is updated automatically, depending on how well the maintenance team is using their CMMS. This can help make decisions about whether to repair or replace assets when they break down.

When organizations purchase new CMMS software or when new assets are purchased, there may be a period of “catch up” time to get all necessary data in the system. This might seem like a tedious process, but it’s important to take the time to gather and import as much data as possible because it will be helpful for asset management down the road.

Set Quality and Usage Guidelines

The asset management process also includes setting asset usage guidelines for production staff. When these guidelines are followed, it helps maintenance staff to streamline the maintenance schedule. When assets are operated correctly, there is less chance of downtime due to misuse of machines.

Using assets properly also includes being aware of when assets need to be available for maintenance. Open communication between the maintenance and production departments before repairs or preventive maintenance tasks take place is important to avoid misunderstandings and scheduling conflicts.

Follow Warranty Guidelines

From the day an asset is purchased and throughout its early lifecycle, following warranty guidelines is imperative. Maintenance needs to be consistent with their inspections of each asset. It’s also essential to keep up with all of the manufacturer’s recommended maintenance. Equipment manufacturers have guidance for recommended maintenance schedules which outline which service tasks need to be done, the intervals at which to perform maintenance, and what replacement parts will be needed.

Failure to do one or all of these things can void the manufacturer warranty. For example, if the maintenance team fails to do regular furnace inspections and change the filter, the manufacturer will decline to replace a part that failed or the entire furnace as a result. Other things that will void a warranty include making modifications to a machine, changing a component without an authorized technician, or modifying control software on equipment without authorization.

Identify Critical Spares for Each Asset

Identifying and stocking critical spares for each asset should be a best practice for every organization that is managing assets. This can be done using a bill of materials or recorded elsewhere in the CMMS. CMMS software can also make sure critical spares are available in inventory by keeping track of the amounts of each part in stock. If regular inspections are being conducted, having spare parts on hand ensures they can be replaced whenever needed. Otherwise, the machine may be out of service while maintenance waits for a delivery.. These parts are stored in Maintenance, Repair, and Operations (MRO) inventory, which also includes supplies and tools for completing maintenance work.

How CMMS Software Supports Asset Management

This article has already mentioned CMMS software, which is a type of asset management software. There are many ways that CMMS software can provide support for successful asset management.

Provides a Centralized Database

CMMS software provides a centralized database where all information about maintenance operations can be stored and viewed in an organized fashion. Instead of looking through file cabinets and printed manuals, the cloud-based platform makes asset information available from any internet-connected device. Technicians in the field and managers working offsite don’t have to go back to a desktop computer or printed resource—they can view essential asset data directly on their mobile phone or tablet.

Visualizes Asset Relationships

It’s important for maintenance teams to be able to visualize asset relationships so the information about them can be utilized. The CMMS database includes asset hierarchies, in which parent-child relationships for equipment, subassemblies, and components are created. Knowing how assets relate to each other is a central part of asset management.

Keeps Detailed Maintenance Records

CMMS software helps maintenance teams keep detailed records. The information found in user manuals can be entered directly into asset records. Digital versions of manuals can be attached directly. CMMS software automatically creates maintenance history based on those records that can be reviewed quickly.

Meticulous asset record keeping is part of a comprehensive maintenance strategy which increases the maintenance team’s chances of scheduling maintenance early before there is serious damage to the machines. It’s valuable for maintenance managers to have data on equipment health available in CMMS software. Asset data such as the manufacturer ID, make and model, specification, and location can be stored and easily updated in CMMS software.

Offers Asset Tags

Having CMMS software in place ensures maintenance teams can utilize asset tags to easily look up asset information. These tags are barcode labels which are affixed to the asset and scanned with a barcode scanner. The scanner reads the code and pulls up information in the software, which is tied to the asset the barcode represents. This allows information about assets to be viewed in seconds and easily updated from a mobile device.

Provides a Robust Failure Tracking System

Using a CMMS for asset management will provide maintenance teams with a robust failure tracking system. This proves to be helpful when an asset needs to be repaired frequently. Technicians can look back at failures recorded in the software and see which assets are failing most often, helping to shape future maintenance decisions regarding those assets. Asset failure information can also be used for Failure Modes and Effects Analysis (FMEA).

Creates Bills of Materials and Identifying Critical Spares

CMMS software also facilitates asset management by having the ability to create equipment bills of materials (EBOM). Not every asset needs a bill of materials, but the most critical assets likely do. A maintenance planner (or in smaller organizations, a maintenance manager) will establish the EBOM. Maintenance planners help determine which parts to buy and which parts will be needed in the future.

While it may be excessive to include every screw and bolt, items that are needed for preventive work and critical spares should be included. If an item isn’t in stock and the supplier has long lead times, that should be indicated on the EBOM. EBOMs stored in a CMMS have a format that is easy to edit, use, and view.

Technicians can refer to the BOM and quickly identify the parts needed to complete repairs. A well written BOM can also ensure optimized maintenance scheduling, ensuring the correct parts are available for upcoming work. BOMs also reduce downtime because technicians can quickly determine which parts they need for the current maintenance job.

Identifying critical spares, which is necessary for creating equipment bills of materials and asset management in general, can also be done more easily with CMMS software.

Uniquely Identifies Assets

CMMS software is also one of the best ways to incorporate asset naming conventions. Having a naming convention in place makes it easier to search and query related data.

Read More: What is an Asset Naming Convention?

Improves Asset Performance through Reporting

CMMS asset management software allows you to report on your maintenance data and calculate metrics such as the Meant Time between Failure (MTBF), Mean Time to Repair (MTTR), and Overall Equipment Effectiveness (OEE). Through reporting, valuable insights can be gained which can direct maintenance activities in the right direction while tackling challenges that arise.

Read More: 3 Important Asset Management KPIs and How to Use Them

Schedules Recurring Maintenance

Finally, asset management with CMMS software includes the ability to schedule reoccurring maintenance. This ensures maintenance is performed on time according to manufacturer specific guidelines and warranty. It also allows maintenance managers to schedule preventive maintenance when it will interrupt production as little as possible.

Improve Asset Management with FTMaintenance Select

FTMaintenance Select offers modern asset management capabilities to support the best practices you need to carry out machine maintenance. To learn more about how FTMaintenance Select is a complete asset management software solution, schedule a demo today.

What is a Remedy Code?

Young male technician repairing a printing machine, which will later by documented by a CMMS remedy code.

This article is part of a series of articles on the topic of equipment failure tracking. Read our other articles on this topic:

What are Remedy Codes?

The first two articles in this series, focusing on failure codes and cause codes, established the following:

  • Failure codes are used to track a problem or type of failure.
  • Cause codes are used to track the reason why a failure occurred.

Together, these codes help tell the story of what failure occurred and why it happened. A third piece of information that is of interest to the maintenance team is how to fix the problem. That’s where remedy codes come in.

A remedy code, sometimes called an action code, is a value used to uniquely identify a type of maintenance action taken in response to a failure, and is often found in a computerized maintenance management system (CMMS). Like failure codes and cause codes, remedy codes are a combination of an alphanumeric code and a description. Remedy codes represent the action a maintenance technician took to correct the issue identified by the failure and cause codes.

Where are Remedy Codes Used?

Remedy codes are used in CMMS software on work orders to identify what type of work was performed to return an asset to working order. Over the course of a repair, technicians may take multiple actions to repair an asset that has failed, some of which may not solve the problem. Technicians test their handiwork to ensure that the asset’s condition has returned to normal. Only then can technicians apply remedy codes – after they implement an acceptable fix and work is considered complete.

Why Use Remedy Codes?

There are many reasons organizations use CMMS remedy codes. Note that, while remedy codes can be useful for any organization, they are most commonly used in organizations or industries that have rigorous failure tracking requirements, such as oil and gas.

Improved Repair Time

The details of maintenance work are contained in many places on a work order or in a CMMS. When it comes time to perform maintenance, technicians must sift through many historical work order records to find previous solutions.

Remedy codes sharpen troubleshooting and issue resolution skills by providing technicians with a well-defined list of maintenance tasks that solved the problem in the past. Ultimately, this allows technicians to return assets to service more quickly. Over time, technicians will become better at thinking about which remedies are most appropriate for a given failure cause.

Implementation of a Proactive Maintenance Strategy

Tracking asset failures through failure codes, cause codes, and remedy codes sets the stage for implementing proactive maintenance strategies, such as reliability-centered maintenance (RCM). Upon completion of corrective maintenance work, the failure, its cause, and its solution are known. This allows maintenance management to plan for future occurrences of the failure and schedule maintenance tasks to prevent them.

Further Reading: How to Implement a Proactive Maintenance Strategy

Labor Resource Productivity Tracking

Remedy codes can be used as a way to estimate and track how long it takes technicians to perform maintenance tasks. As each remedy becomes known, maintenance managers can assign labor time estimates to each maintenance task, improving maintenance planning.

Remedy codes with associated time estimates also help maintenance managers track labor performance. For example, a CMMS report that compares the estimated labor time to actual labor time spent on a remedy may reveal who performs tasks well and who might need additional training.

Identification of Training Needs

Maintenance managers are responsible for making sure their team has the correct skills required to perform maintenance work. Tracking maintenance work through remedy codes helps identify what types of tasks are performed most often and helps prioritize training, especially for new hires.

As mentioned previously, CMMS reports filtered by remedy code can also reveal underperforming employees who might require refresher training. At the same time, reports may reveal high performers who can help train others on certain tasks or repairs on specific assets.

CMMS Remedy Code Construction

The information needed to create meaningful remedy codes comes from team experience and asset maintenance history. As technicians document their work in the CMMS over time, maintenance managers can identify trends in the types of tasks being performed – and how long they take.

Remedy Code Design

Like failure codes and cause codes, remedy codes are typically unique to each organization and their assets. Because remedy codes are used for rigorous asset failure tracking, they are more comprehensive and asset-specific. Even though the maintenance task may be the same, it will take a different amount of time to complete depending on the asset, easy of performing maintenance, etc.

Remedy Code List Example

Below is an example of a remedy code list for a CNC machine. Note that this list is not exhaustive of all maintenance actions.

Remedy Code Remedy Code Description
BLOCK-NOZZ Remove blockage from coolant nozzle
CHIP Empty chip box
CLEAN-CHK Clean chuck
CLEAN-CF Clean cooling fan
CHECK-HO Check flow of hydraulic oil
CHECK-COOL Check flow of coolant; fill coolant tank
PRES-HU Check pressure of hydraulic unit
REPLACE-FLT Replace filter
REPPLACE-MTR-BRNG Replace motor bearing

CMMS Remedy Code Best Practices

The goal of developing remedy codes is for CMMS users to be able to track maintenance actions in response to failures. Keep the following best practices in mind when constructing remedy codes:

  • Make Remedy Codes Clear and Specific: As discussed, remedy codes will differ by asset. However, the list of remedy codes for a given asset should be easy to understand and memorize. Codes and their meanings should not overlap with one another – each should be tied to a specific maintenance action.
  • Include a Catch-All Remedy Code: When getting started with remedy codes, all possible failure remedies will not be known – they will be discovered over time. Therefore, it is acceptable to use a catch-all “other” code that can be later analyzed and broken down to generate additional remedy codes.
  • Hold Team Accountable for Use: Rigorous maintenance tracking requires that maintenance teams use remedy codes consistently. A CMMS makes maintenance documentation more transparent, providing a shared reference point for holding employees accountable for entering required data.
  • Review and Update the Remedy Code List: Because failures and their causes are unpredictable, it is unlikely that the original remedy code list will be inclusive of all maintenance tasks. The need for additional remedy codes will arise as technicians perform maintenance work and more asset data is collected. Periodically review work orders and consult with your team to expand the remedy code library.

Document and Track Asset Maintenance with FTMaintenance Select

Remedy codes make it easy for maintenance workers to identify corrective maintenance actions. When failures occur, technicians are able to drill in to historical CMMS data to quickly find solutions and return assets back to service faster. FTMaintenance Select is a centralized platform that provides maintenance organizations with a single source for documenting and tracking asset maintenance. Request a demo today to learn more about FTMaintenance Select.

This article is part of a series of articles on the topic of equipment failure tracking. Read our other articles on this topic:

What is a Cause Code?

Young male technician testing a printing machine to determine the cause of failure, to be documented by a CMMS cause code.

This article is part of a series of articles on the topic of equipment failure tracking. Read our other articles on this topic:

What are Cause Codes?

The first article of this series, What is a Failure Code?, establishes that failures codes are a way to document the state of a failed asset, as determined by an observer. Because they only capture the problem with an asset, failure codes alone do not paint the whole picture of a failure event. Cause codes help to fill in this missing information.

A cause code, sometimes called a reason code, is a value used to uniquely identify a type of failure cause and is often found in a computerized maintenance management system (CMMS) or other asset management system. Like failure codes, cause codes are a combination of an alphanumeric code and a description. Cause codes are used to record the underlying reason for the problem identified by the failure code.

Where are Cause Codes Used?

Cause codes are used in maintenance management software along with failure codes for asset failure tracking. They are applied to work orders to identify why a problem occurred. In most cases, technicians cannot identify the reason for asset failure without investigating the issue and testing solutions to see if a repair corrected the issue. Therefore, cause codes are commonly entered after work has been completed, though they are sometimes entered during troubleshooting.

Why Use Cause Codes?

There are many reasons organizations use CMMS cause codes.

Improved Maintenance Effectiveness

A description of a failure is often too simplistic to be useful. Without understanding the root cause of an asset failure, technicians are only treating the symptoms of failure and not preventing it from occurring in the future. Cause tracking provides a starting point for failure analysis and the creation of maintenance tasks that reduce the likelihood of failure.

Improved Downtime Tracking

Rather than simply documenting that downtime occurred without explanation, cause codes connect downtime events with a reason for failure. As this information is gathered over time, organizations can drill into the data to identify patterns in downtime and develop plans to reduce it. Recurring issues may warrant more frequent preventive maintenance or identify additional training needs for certain maintenance tasks. Without identifying the true cause of the downtime, it is likely to happen again.

Improved Troubleshooting

When troubleshooting, a technician may first use a CMMS to find historical work orders whose failure code matches what they have observed or what has been reported. Next, the technician may look at the paired cause code to understand what has caused the failure in the past. This failure code-cause code pair provides better direction for troubleshooting, allowing technicians to start investigating the most likely causes first.

Additionally, the use of cause codes refocuses the efforts of the maintenance team to investigate reasons for failure. Otherwise, technicians might simply make repairs and move on, thereby increasing the likelihood the failure will reoccur.

Implementation of Asset Lifecycle Management Practices

Both basic and advanced methods of asset life cycle management rely on collecting information about failures and their causes in order to reduce downtime, extend asset life, and optimize lifetime asset maintenance expenses. As asset lifecycle management strategies become more advanced, cause tracking becomes more important.

For example, to reduce downtime, organizations perform root cause analysis (RCA) to help maintenance staffs backtrack through the steps leading up to failure in order to understand the conditions that prompted it. Building off RCA, failure modes and effects analysis (FMEA) identifies an asset’s failure modes and their associated risks in order to extend asset life. Going a step further, organizations that practice reliability-centered maintenance (RCM) develop maintenance plans to prevent failures, based on their cause, in the most cost effective manner.

CMMS Cause Code Construction

The information required to construct cause codes comes from high-level maintenance employees and tradesmen, maintenance history, and practical experience with an asset. Employees who have expertise in electrical, mechanical, and pneumatic systems have an in-depth understanding of probable issues that can occur. Maintenance history, stored in a CMMS, provides a database of failure and repair data from which to generate cause codes. In some organizations, the maintenance and engineering teams work together to devise the cause code library.

Cause Code Design

Like failure codes, cause codes are typically unique to each organization. First-time users may favor broad, high-level cause codes that represent the general system causing issues. Not only are broader cause codes easier to construct, but they make it easier to start process improvement as well.

Granular, asset-specific cause codes are better suited for experienced maintenance teams who operate under an established cause tracking system. If making cause codes too specific, maintenance managers may also have trouble identifying cause trends. Also, inexperienced technicians are likely to erroneously assign failure causes and compromise failure data. However, if the CMMS supports it, specific cause codes might be nested under more general cause codes, providing both novice and veteran workers with the ability to document causes.

Regardless of which approach is taken, it is important to keep in mind that tracking causes is not an ending point – it is a starting point for deeper failure analysis. Therefore, the simplicity or complexity of the cause code library should match the organization’s requirements.

Cause Code List Example

Below is an example of a generic cause code list. Note that this list is not exhaustive of all causes of equipment failures.

Cause Code Cause Code Description
AF Pneumatic failure
EF Electrical failure
HF Hydraulic failure
MF Mechanical failure
PM Inconsistent preventive maintenance
SF Start-up failure

CMMS Cause Code Best Practices

The goal of developing cause codes is for CMMS users to be able to track why asset failures occurred on work orders. Keep the following best practices in mind when constructing cause codes:

  • Consider Team Experience: Technicians experienced in a particular trade or craft will be able to more easily identify the probable cause of an asset failure. Making cause codes too complex will result in less-experienced technicians picking the wrong codes. Start with a simple cause code library – the list can become more granular as the team grows into the use of the system.
  • Keep the Cause Code List Size Manageable: There is a delicate balance between too many and too few cause codes. List size will partially depend on team experience. However, also consider the ease of analyzing the data. Starting with broad cause codes allows organizations to dig deeper into issues. Starting with too many cause codes that are too specific can make it difficult to “see the forest through the trees” and understand the larger issues at hand.
  • Make Cause Codes Foolproof: Cause codes should be constructed in such a way that they are easy to memorize, hard to misunderstand, not easily confused with one another, and have specific meanings that do not overlap with one another. Doing so will maximize the value of failure cause tracking while limiting mistakes or faulty data.
  • Hold Team Accountable for Use: Cause codes will only be effective if used consistently and correctly. A CMMS allows you to verify that cause codes are used properly, and becomes a reference point for identifying and correcting mistakes.
  • Review and Update the Cause Code List: Cause code lists are not set in stone. During analysis, it is possible that causes are being miscategorized or that additional cause codes are needed. Periodically review the cause code library and update when appropriate.

Conclusion

Cause tracking makes maintenance more effective by tracking the reasons why assets fail. Based on the root causes of failure, organizations can implement highly targeted maintenance tasks that treat causes, not symptoms. FTMaintenance Select is a CMMS that allows you to easily plan, schedule, and document maintenance activities on critical equipment and facility assets. Request a demo today to learn more about FTMaintenance Select.

This article is part of a series of articles on the topic of equipment failure tracking. Read our other articles on this topic: