Failure Reporting, Analysis, and Corrective Action System (FRACAS)

FRACAS is an acronym that stands for Failure Reporting, Analysis, and Corrective Action System. The term originates from the Department of Defense and was first recorded in the military standard MIL-STD-2155 published in 1985.

FRACAS is a three-step process originally used to achieve the reliability and maintainability potential of military equipment systems. Its initial scope focused on defense, aerospace, automotive, telecommunications, and the like. Today, FRACAS has evolved into a tool that can benefit any industry.

This three-step approach forms a closed-loop system, and each step is methodically carried out before moving onto the next one. The following steps are described in more detail below.

Failure Reporting

As with any problem-solving process, FRACAS starts with stating the problem. Failure reporting is the process of gathering everything you need to know about a failure or an issue.

The level of detail in these reports is expected to vary across different organizations and industries. FRACAS is usually customized to suit the unique requirements of each company. Typical information included in a failure report are:

• Date and time of the incident
• The person who found the issue or failure
• The person who is conducting the report
• Details about the incident, including events prior to the incident
• Corrective action performed, if any, to fix the issue
• Solutions that can prevent future occurrences

With a computerized maintenance management system in place, data required for failure and incident reporting should be more readily available. All you would need to do is ensure your assets are set up and properly accounted for in the system. You would also want to align your team on the procedures to perform and update maintenance tasks in your CMMS. This way, you can maximize your software to do the work for you.

Analysis

After gathering all the available information, the next step is to investigate the failure and its origins. The primary goal of the analysis phase is to identify the root cause of the issue. Learning the reason behind a failure paves the way for future solutions.

Technical people, engineers, or team leaders are usually the ones performing the analysis. Their knowledge and experiences help inform the root cause analysis and endorse corrective action.

Corrective Action

After identifying the steps to resolve the issue, the last thing to do is implement the corrective action. In this step, specific tasks to resolve the issue are developed, documented, and implemented. Applicable tests should also be performed to verify the resolutions are adequate.

Remember that FRACAS is a closed-loop process. It's only until after the implementation of the corrective action that a case can be considered “closed out."

How Is FRACAS Implemented?

At this point, you can see that FRACAS is pretty straightforward. It gives you a basic framework for how to ensure your facility’s concerns are addressed. The next sensible question then is how to start implementing it.

The key to effectively implementing FRACAS is making sure your data is maximized. It's not enough to have an abundance of data. Additionally, it's equally important to ensure your data is organized. This allows you to more clearly identify associations between your observations and your conclusions. To ensure you’re not missing any crucial points, it helps to follow the following phases of implementation.

1. Discovery Phase

The first phase requires you to identify each task needing to be performed. This includes the accountable person or unit, specific procedures involved, and the approval processes, if any. Definitions and standards should also be set at this phase.

There are a few steps that need to be determined at this phase. To name a few, you should identify definitions of failure, descriptions of failure, verification procedures, failure modes, and RCA procedures. At the end of this phase, ensure all processes are well-documented.

2. Design Phase

The next phase aims to streamline your requirements. After identifying all the prerequisites in the discovery phase, you would want to create a system that sustainably provides for your needs.

Each activity should be planned out in the design phase. Tasks can be classified as either human work or document-based tasks. Human work requires manual intervention and should be assigned to a point person or an execution team. Document-based tasks, on the other hand, can be thought of as analysis tasks usually in the form of reports.

3. Enactment Phase

The enactment phase is the process everyone has been waiting for. Enactment involves putting your planned activities into practice. Team members should be aware of their tasks, schedules, and updating methods. To ensure the progress is accurately tracked, members should also notify the team of their status in real-time by using a CMMS. This prevents inefficiencies, such as redundant tasks and unnecessary standstills.

What Are Some Problem-Solving Methods Commonly Used With FRACAS?

As technology and communications expand, so do the innovations in the approach to solving problems. What used to be offline strategies have been incorporated into widespread industry standards. For example, workflows tailored to fit a company’s FRACAS process might be based on other existing problem-solving methods, such as the Eight Disciplines (8D) or DMAIC methods.

The 8D Approach

The 8D Approach is a methodology for solving problems, focused on improving products and processes. This method was developed by the Ford Motor Company, initially used by professionals working in the automotive industry. The following steps summarize the eight disciplines.

D0: Plan and prepare

Before anything else, 8D starts with a plan. In this step, you identify any steps you would need to take to solve a problem.

D1: Build a team

The next step involves forming a team. The idea behind this step is each member provides various vantage points to the same problem. Each person’s knowledge and experience is utilized to have a broader view of the situation.

D2: Define and describe the problem

The problem is then defined and described in detail. Basic questions to ask in this stage are: Who? What? Where? When? Why? How? And How Many?

D3: Contain the problem

After a problem is identified, it's important to isolate the problem from the customer and usual operations. In this stage, actions are taken to keep the problem contained and under control.

D4: Identify, describe, and verify root causes

The root cause is then identified using root cause analysis techniques. Examples of RCA techniques are 5 Whys, Ishikawa Diagram, and Fault Tree Analysis. Each situation may require one or a combination of these techniques.

D5: Choose corrective actions

Identifying the root cause puts you in a better position to identify corrective actions that will address the actual source of the problem. This next step aims to choose the most appropriate corrective action that's verified to provide a permanent solution.

D6: Implement and validate corrective actions

The chosen corrective action is then put into practice. The specific steps of the implementation process are identified and then carried out. This step also includes, through observed evidence, the validation that corrective actions are effective.

D7: Take preventive measures

Aside from identifying a solution to the problem, it's also important to take preventive measures against possibly recurring failures. This step includes changes to existing systems and procedures to improve organizational readiness for future events.

D8: Congratulate your team

To wrap up the 8D approach is the recognition of the whole team's efforts. This highlights the achievement of everyone in the company to improve processes.

What Is DMAIC?

DMAIC is an acronym that stands for define, measure, analyze, improve, and control. DMAIC is a problem-solving approach and an important tool used in the Six Sigma method. 

1. Define

Here the problem, improvement opportunity, objectives, and actions are defined and identified. Aside from the initial problem statement, the resources, benefits, and even timelines should also be specified in this stage.

2. Measure

This next step is done to establish a quantitative baseline to be used as the basis for the effectiveness of any further action. A huge portion of this step is allotted to data gathering and collection. Having a CMMS or EAM software in place should relieve you of a lot of the manual tasks related to this step.

3. Analyze

As with the previous problem-solving methods, this step ensures the root cause is identified. This step aims to identify the primary cause of failure and to assess the effects of the identified root cause. In this step, investigations are performed to spot the true origin of an identified breakdown event.

4. Improve

The next step aims to implement a solution to the problem. A detailed outline of the steps should be developed in this phase. This will act as the outline of procedures that need to take place.

5. Control

The last step emphasizes that DMAIC is an ever-evolving process. It's geared toward continuous improvement and promotes the same culture to the team. Through this stage, activities are tracked to gauge the stability and sustainability of the problem-solving processes.

What Are the Benefits of FRACAS?

There are huge advantages to incorporating FRACAS into the everyday operations of a company. Knowing FRACAs is a closed-loop process should give you the confidence that issues are being addressed for the long term. Some key benefits of FRACAS include:

1. Reduced Costs

A systematic approach to correcting failures reduces the need for rework. This directly translates to a reduction in material costs and labor costs for any needed repair. Surplus stock and leftover materials are also avoided if corrective actions are well planned out.

2. Increased Reliability

FRACAS promotes a culture of continuous improvement with a data-driven mindset. The discipline of checking the status of an asset and performing required actions gives you lower chances of failure. This, in turn, contributes to increased equipment reliability and overall performance.

3. Decreased Inefficiencies

In relation to reliability, FRACAS can lead to metrics that could reveal potential inefficiencies. Mean time between failure (MTBF) and mean time to repair (MTTR), for example, are metrics that would typically be the focus of equipment failure reports. Having a comprehensive view of the inefficiencies within the plant can lead you to form concrete actions to address the problem.

What Are Some Common Concerns When Implementing FRACAS?

To maximize the benefits of FRACAS, a company should be aware of some of the common mistakes and misconceptions associated with it. The following points are some of the common issues organizations will potentially struggle with down the road.

1. Complex Organizational Structures

FRACAS is used by multiple teams within the organization. At the same time, multiple people are also accountable for putting in data. This makes the process vulnerable to inefficiencies such as double-handling and unnecessary work.

To improve on this issue, it helps to identify the scope of work each team is required to complete. The capability to provide input can be limited to certain responsible groups to ensure every step is assigned to the proper person.

2. Lack of Prioritized Goals

Another challenge in implementing FRACAS is the differences in perception when it comes to the prioritization of goals. Each functional group might focus on different aspects of a certain project.

A relatable example is when implementing FRACAS under a constrained budget. Under such conditions, corrective actions may be performed with insufficient data and limited analysis. This would have been handled more effectively if goals were clearly listed and prioritized. That way, the resources would have been more focused on resolving the most pressing concerns.

3. Inefficient Data Tracking

Data is the foundation on which FRACAS procedures are built upon. Without confidence in your data, the following steps in FRACAS won’t work to your advantage. The tricky thing with data is it needs to be consistently tracked to provide usable information. One good data point can easily be put to waste if the next data point is inaccurate.

With multiple assets running, it can be a daunting task to keep track of each piece of equipment at all times. This is where your software can come and save you loads of work. Modern software systems can keep track of your asset data in real-time. Manual activities that would have taken you valuable man-hours can be automated and set up with the right information.

Conclusion

Increasing preventive maintenance tasks is surely one way to reduce failure events. However, this isn't necessarily the best option out there. Instead, you'd want to be as efficient as you are effective.

There are other smarter ways to optimize PM activities without breaking the bank. FRACAS is one of the first steps to streamlining your PM strategy. By systematically identifying the problem and coming up with solutions, processes become more sustainable in the long-term.