Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Way of the Quality Warrior
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • Quality Engineering Statistics
    • An Introduction to Reliability Engineering
    • Reliability Engineering for Heavy Industry
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Carl S. Carlson 5 Comments

Understanding FMEA Recommended Actions – Part 1

Understanding FMEA Recommended Actions – Part 1

Actions Speak Louder than Words

Consider these questions: How many recommendations are needed to address the root cause of a high-risk problem? If the FMEA team is addressing an issue with high-severity and high-occurrence ratings, is it usual to have a single recommended action to reduce risk? Why not? Read on, to learn the essential elements of FMEA recommended actions, and answers to this questions.

“I have been impressed with the urgency of doing. Knowing is not enough; we must apply. Being willing is not enough; we must do.”
Leonardo da Vinci

Definition of “action”

The Oxford English dictionary defines “action” as “the fact or process of doing something, typically to achieve an aim.”

What is the definition of “Recommended Action” in an FMEA?

“Recommended Actions” are the tasks recommended by the FMEA team that can be performed to reduce or eliminate the risk associated with potential cause of failure. Recommended Actions should consider the existing controls, the relative importance (prioritization) of the issue, and the cost and effectiveness of the corrective action. There can be many recommended actions for each cause.

How are Recommended Actions identified in FMEAs?

The FMEA team reviews each of the high severities (regardless of RPN value), followed by each of the high RPNs, and develops the recommended actions that, when executed, will reduce risk to an acceptable level. There is often more than one action needed to address risk associated with each of the failure modes and causes. The FMEA team should take care to recommend feasible and effective actions that will fully address the risk associated with each failure mode/cause. Whatever action the FMEA team believes needs to be done to address risk must show up in the recommended action column.

In identifying recommended actions, the FMEA team should consider existing controls, the relative importance (prioritization) of the issues, as well as the cost and effectiveness of corrective actions.

For each recommended action, the FMEA team should assign the person responsible, the due date, and other typical project management type of information in order to be able to execute the actions efficiently.

Why is it usually necessary to use multiple recommendations to address high risk? Because, some actions can reduce severity risk, other actions can reduce occurrence risk, and even other actions can reduce detection risk.

What is an example of a Design FMEA recommended action?

Item: Power steering pump

Function: Delivers hydraulic power for steering by transforming oil pressure at inlet ([xx] psi) into higher oil pressure at outlet [yy] psi during engine idle speed

Failure Mode: Inadequate outlet pressure (less than [yy] psi)

Effect (Local: Pump): Low pressure fluid goes to steering gear
Effect (Next level: Steering Subsystem): Increased friction at steering gear
Effect (End user): Increased steering effort with potential accident during steering maneuvers

Cause: Fluid incorrectly specified (viscosity too low)

Prevention Control: Design guidelines for hydraulic fluid selection
Detection Control: Vehicle durability testing #123

Recommended Action: Increase fluid viscosity to standard #xyz

Poorly worded example of Recommended Action: Change fluid viscosity

What is an example of a Process FMEA recommended action?

Process Step: Induction harden shafts using induction hardening machine

Function: Induction harden shafts using induction-hardening machine ABC, with minimum hardness Brinell Hardness Number (BHN) “X”, according to specification #123.

Failure Mode: Shaft hardness less than BHN “X”

Effect (In plant): 100% scrap
Effect (End user): Shaft fractures with complete loss of performance
Effect (Assembly): Not noticeable during assembly

Cause: Induction machine electrical voltage/current settings incorrect for part number

Prevention Control: Shaft hardening setup instructions
Detection Control: audit of shaft hardness

Recommended Action: Install machine alert light (red) to let operator know when voltage or current is set too high
Recommended Action: Implement Statistical Process Control (SPC) charts on machine voltage and current

Poorly worded example of Recommended Action: Implement Statistical Process Control

Application Tips

  1. In addition to identifying recommended actions to improve designs and reduce risk, the team should review the corresponding engineering or manufacturing requirements. The question needs to be asked, “Do the engineering or manufacturing requirements need to be changed to reflect the design or process improvement?” If the answer to this question is “yes,” the team needs to add recommended actions to improve the requirements. This is important because it is ultimately the engineering or manufacturing requirements that drive product designs, product testing, manufacturing processes and process control plans.
  2. For high-risk issues, the FMEA team should consider three approaches. First, try to reduce severity risk, if possible. Second, recommend actions to reduce occurrence risk and ensure the actions “fix” the cause. Recall the cause in an FMEA is a design or manufacturing deficiency, as covered in “Understanding FMEA Causes – Part 1.” Third, the team can consider actions to reduce detection risk. Future “Inside FMEA” articles will focus on strategies to reduce severity, occurrence and detection risk.

Next Article

Consider the recommended action “Review results of XYZ test to confirm requirements are  achieved.” Is this a good FMEA recommended action to address a high-risk issue? Is it sufficient? Challenge your FMEA knowledge by solving this problem and other problems in the next article.

Filed Under: Articles, Inside FMEA, on Tools & Techniques

About Carl S. Carlson

Carl S. Carlson is a consultant and instructor in the areas of FMEA, reliability program planning and other reliability engineering disciplines, supporting over one hundred clients from a wide cross-section of industries. He has 35 years of experience in reliability testing, engineering, and management positions, including senior consultant with ReliaSoft Corporation, and senior manager for the Advanced Reliability Group at General Motors.

« Where Does Maintenance Fit Into Reliability?
Design of Experiments Process — A Decision Making Focus »

Comments

  1. Sandy says

    May 25, 2018 at 5:28 AM

    when Action to be taken in FMEA.

    Reply
    • Carl Carlson says

      May 31, 2018 at 8:01 AM

      Hi Sandy,

      Thanks for your question about when to take action in an FMEA. That is an important question. Let’s take a look at the paragraph titled “How are Recommended Actions identified in FMEAs?”, in the article “Understanding FMEA Recommended Actions.” Here’s what it says.

      “The FMEA team reviews each of the high severities (regardless of RPN value), followed by each of the high RPNs, and develops the recommended actions that, when executed, will reduce risk to an acceptable level. There is often more than one action needed to address risk associated with each of the failure modes and causes. The FMEA team should take care to recommend feasible and effective actions that will fully address the risk associated with each failure mode/cause. Whatever action the FMEA team believes needs to be done to address risk must show up in the recommended action column.
      “In identifying recommended actions, the FMEA team should consider existing controls, the relative importance (prioritization) of the issues, as well as the cost and effectiveness of corrective actions.
      “For each recommended action, the FMEA team should assign the person responsible, the due date, and other typical project management type of information in order to be able to execute the actions efficiently.”

      Please let me know if the verbiage in this paragraph answers your question. And do not hesitate to ask further questions.

      Carl

      Reply
  2. Bill VanNiejenhuis says

    July 21, 2020 at 12:15 PM

    IN the PFMEA, once the recommened action has been completed, do you go back and redo the portion of the FMEA with the new RPN? and remove it from the “Recommended action column?

    Reply
    • Carl Carlson says

      July 21, 2020 at 9:23 PM

      Good question!
      In most FMEA standards and company applications, the FMEA Recommendations are executed and the final SOD are assessed. If the SOD risk is not acceptable, the FMEA team can recommend further actions until the risk is reduced to an acceptable level. It is not usually the practice to modify the original FMEA to reflect the design or process modifications or RPNs, during the product development process. Once the FMEA is completed with risk reduced to an acceptable level, the new information can be entered into a generic FMEA, so that future FMEAs will benefit from the updated information. One of the reasons for this practice as described is that FMEAs are legal records showing the due diligence to address risk. I would suggest maintaining the FMEA by version control. If the company wants to initiate a new version of the FMEA, which builds on the previous version, that can be done.

      Reply
  3. shiv prajapati says

    October 4, 2020 at 10:27 AM

    High RPN? When a RPN should be consider as high?

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Articles by Carl Carlson
in the Inside FMEA series

[popup type="" link_text="Logo Info" ]

Information about FMEA Icon

Inside FMEA can be visually represented by a large tree, with roots, a solid trunk, branches, and leaves.

- The roots of the tree represent the philosophy and guiding principles for effective FMEAs.
- The solid trunk of the tree represents the fundamentals for all FMEAs.
- The branches represent the various FMEA applications.
- The leaves represent the valuable outcomes of FMEAs.
- This is intended to convey that each of the various FMEA applications have the same fundamentals and philosophical roots.

 

For example, the roots of the tree can represent following philosophy and guiding principles for effective FMEAs, such as:

1. Correct procedure         2. Lessons learned
3. Trained team                 4. Focus on prevention
5. Integrated with DFR    6. Skilled facilitation
7. Management support

The tree trunk represents the fundamentals of FMEA. All types of FMEA share common fundamentals, and these are essential to successful FMEA applications.

The tree branches can include the different types of FMEAs, including:

1. System FMEA         2. Design FMEA
3. Process FMEA        4. DRBFM
5. Hazard Analysis     6. RCM or Maintenance FMEA
7. Software FMEA      8. Other types of FMEA

The leaves of the tree branches represent individual FMEA projects, with a wide variety of FMEA scopes and results. [/popup]

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Posts

  • test
  • test
  • test
  • Your Most Important Business Equation
  • Your Suppliers Can Be a Risk to Your Project

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy