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 Leave a Comment

Generic Lists of Failure Information – Good Idea or Not?

Generic Lists of Failure Information – Good Idea or Not?

Are generic lists of failure information useful to FMEA teams? Are they a good idea or not?

There is a lot of discussion amongst FMEA practitioners on automating and standardizing FMEAs. In this article, I will discuss the pros and cons of using generic lists of failure modes, effects and causes.

The Oxford English dictionary defines “generic” as “characteristic of or relating to a class or group of things; not specific.”

Referencing Effective FMEAs, chapter 5:

FMEA practitioners should be aware of the benefits and limitations of using generic listings of failure modes, effects, causes, etc. Generic lists of failure information can be good thought-starters for FMEA teams, provide standardized descriptions, and ensure completeness of analysis. Controlling the description of individual failure modes enables analysis and dissemination of failure information between project teams and the entire organization.

The limitations of using generic failure information include the suitability of generic descriptions to the current project, potential for inclusion of information in current FMEA that is not of concern to FMEA team, and the possibility of stifling the creativity of the FMEA team to “think outside the box” and identify issues not previously seen. This last issue can be addressed by the proper use of brainstorming before exposing the FMEA team to generic failure information. In addition, generic failure data may come from significantly different operating environments and usages than current application.

How can “generic” words or phrases be useful in FMEA?

The FMEA team can consider past lists of actual failures, or published lists of generic failures to begin discussions within the FMEA team. It should be thought-starters, for opening up discussion, not “canned.” The team should end up with failure mode, effect, cause descriptions after listening, discussing and arriving at consensus, based on the specific circumstances of the item being analyzed. There is nothing wrong with working in the direction of standardized descriptions, as long as it aids in the identification of the most important failures, effects and causes. The key is staying faithful to the fundamentals of FMEA.

How can use of “generic” words or phrases be detrimental in FMEAs?

The FMEA team should consider the suitability of generic descriptions to the current project. What is the same, or different between the current project and the generic list?

The FMEA team should avoid inclusion of information in the current FMEA that is not of concern to anyone on the team. As covered in the “Tips” section of the article “Application Tip – Begin with Concerns”

It is a good practice to limit the discussion of failure modes to those of concern to at least one member of a properly constituted FMEA team.

Above all, the FMEA team should work in the direction of enhancing the creativity of the team to identify issues not previously seen. Yes, it is important to ensure past problems are not repeated. But it is equally important to ensure unseen problems do not manifest. Too much emphasis on “canned” lists of failures can make it more difficult to think outside the box, see what is potentially not yet visible, and will stifle creativity.

When integrating model-based engineering with FMEA, it is essential to use the power of the team to focus on the most important issues and get to viable root causes and risk prioritization.

See the article “Why FMEA Needs to be Team-Based,” which includes what elements of the FMEA can be prepopulated or automated, and what elements must be considered by the team.

Next Article

In the next Inside FMEA article, I will share an fascinating reader question about the use of a company-defined policy to identify Special Characteristics in FMEAs.

 

Filed Under: Articles, Inside FMEA Tagged With: Generic phrases

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.

« Age Related Degradation Variables – Which is the Dominant One?
Driver Safety Video »

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