Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • 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 Maintenance Management
      • 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
      • RCM Blitz®
      • ReliabilityXperience
      • 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
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • 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
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Podcasts
  • Courses
    • Your Courses
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
  • Barringer Process Reliability Introduction Course Landing Page
  • Upcoming Live Events
You are here: Home / Articles / Preliminary Risk Assessment

by Carl S. Carlson Leave a Comment

Preliminary Risk Assessment

Preliminary Risk Assessment

Selecting Which FMEAs to Do

FMEAs take time and cost money. They should be done when a certain level of risk can be effectively addressed by the FMEA procedure. Preliminary Risk Assessment is a procedure that uses company-determined criteria to select which FMEAs to do.

“The key is to schedule your priorities.” ― Steven Covey

Why is Preliminary Risk Assessment Important?

Short of doing FMEAs on all subsystems and components, which can be very expensive and time consuming, there needs to be a way to prioritize potential FMEA projects, to help identify which FMEAs to do. One way to do this prioritization is called Preliminary Risk Assessment.

What is Preliminary Risk Assessment

Preliminary Risk Assessment is a procedure to prioritize which FMEAs will be done as part of a new project. It assess the risk associated with subsystems or components (when performing Design FMEAs) or process steps (when performing Process FMEAs) against company-defined risk criteria.

How is Preliminary Risk Assessment Performed?

The following is a simple procedure for performing a Preliminary Risk Assessment:

1. Open up a spreadsheet. In the first column, for Design FMEAs, list the system hierarchy (subsystems and components). For Process FMEAs, list the process steps.

2. Across the top of the spreadsheet enter the company-specific risk criteria used to prioritize the risk of the subsystems and components. The company-specific risk criteria can be identified by the project team. Example below.

3. The next step is to rank each risk criteria for each row in the system hierarchy on a scale, such as high, medium, or low, or 1 to 3. In other words, assess the risk for each item in the system hierarchy (or the process hierarchy), according to the risk criteria.

4. The final step uses simple arithmetic to multiply the cells in each row to obtain a risk index number for each of the subsystems or components in the system hierarchy. This index can then be used as input to the FMEA selection decision.

What are examples of risk criteria

The following are examples of risk criteria for selecting FMEAs. Companies can and should use their own criteria.

1. Potential for safety issues (What is the degree of safety risk associated with the item?)
2. New technology (What is the degree of new technology being introduced with the item?)
3. New applications of existing technology (What is the degree of change being introduced with the item?)
4. History of significant field problems (What level of field problems has been associated with the item or similar items?)
5. Potential for important regulation issues (What level of government regulation is associated with the item?)
6. Supplier capability (What is the risk associated with the supplier of the item?)

Note: These risk criteria can and should be tailored to the circumstances of an individual company or organization and applied to each item in the Bill of Materials.

Example of Preliminary Risk Assessment

The following is a fictitious example of a Preliminary Risk Assessment for an all-terrain bicycle system.

In this example, only the subsystems are assessed; however, the same procedure can be used for selection of components. The results of the Preliminary Risk Assessment in this example point towards two subsystems: frame and hand brake.

FMEA Tip # 1

In many cases, specific changes to a design or manufacturing process are being considered. The nature of the proposed changes can be documented and becomes input to the preliminary risk assessment. This includes changes in design, material, manufacturer, supplier, supplier design or process, usage environment, interfaces, specifications, performance requirements, or any other changes.

FMEA Tip # 2

Preliminary risk assessment can be applied to Process FMEAs. Each of the steps in the process hierarchy (as documented in the process flow diagram) can be analyzed by the preliminary risk assessment procedure, the same as with Design FMEA.

FMEA Tip # 3

The company-specific risk criteria can include a weighting factor, if the company wishes to weight certain criteria more than others. Example is safety concerns.

Problem

You are asked to perform a Design FMEA on a new Bicycle Hand Brake subsystem. In addition to the Hand Brake subsystem DFMEA, you are considering which components may need FMEAs. In this example, the bicycle hand brake is made up of 4 components: brake lever, brake cable, brake pad and brake caliper.

The Preliminary Risk Assessment for the components of the Hand Brake Subsystem DFMEA follows:

How might you use this Preliminary Risk Assessment to select which FMEAs will be done?

Solution

The Preliminary Risk Assessment rating provides input to the project team to help select which FMEAs to perform. Based on this analysis, the highest rating for components of the hand brake subsystem is for the brake cable, followed by brake pads, brake lever and brake caliper. The All-Terrain project team can use this analysis as input to the decision on which FMEAs to do for the hand brake components. Other factors to consider include project budget, project timing, and whether the component is designed in-house or by a supplier. In this fictitious example, the All-Terrain team decided to do Design FMEAs on the hand brake subsystem (based on earlier Preliminary Risk Assessment for bicycle subsystems) and the brake cable (based on this analysis). Given time and resources, they may also add a Design FMEA on the brake pads.

FMEA Question

Reader

Is it recommended to get the design engineers themselves to perform an FMEA or should this job stay with specialists like reliability and safety engineers? For the design engineers it would cost time and keep them away from their normally time-critical design tasks, as they have to be trained first in FMEA tasks. On the other side, it would increase their insight in quality parameters like reliability and safety of their products and systems engineering.

I normally try to perform the FMEA myself applying interview techniques, but in smaller companies (subcontractors), FMEA work is performed by the design engineers themselves.

What is your recommendation?

Reply

Thanks for your question. I have three comments for your consideration.

First, in my experience, FMEAs should be performed by a team, not by an individual. Below is an excerpt from my book on the subject of FMEA teams:

One of the most important steps in preparing for an FMEA is selecting the right team because FMEA is a cross-functional team activity. Doing an FMEA by one person, or with an inadequate or incomplete team, is unacceptable and inevitably results in poor quality. There are three primary reasons for the necessity to have the correct team when doing an FMEA.

1. People have “blind spots.” A well-defined cross-functional team minimizes the errors inherent with “blind spots.”
2. The FMEA analysis requires subject-matter experts from a variety of disciplines to ensure incorporation of all necessary inputs into the exercise, and that the proper expertise is applied to the design or process being analyzed.
3. One of the indispensable values of an FMEA is the cross talk and synergy between subject-matter experts that occurs during the meetings. Well-defined groups can discover things that individuals often miss.

A typical core team for a System or Design FMEA might include representatives from system engineering, design engineering, manufacturing engineering, test engineering, field service, and quality or reliability. Large systems or subsystems may require more than one design representative. Supplier partners may be included for critical parts on a need to know basis.

A typical core team for a Process FMEA might include representatives from manufacturing engineering, plant assembly, product engineering, supplier quality, end-of-line test, maintenance, and quality or reliability.

In addition, the FMEA core team can invite other experts for specific topics during FMEA meetings, when their topic is being discussed.

Second, it is important to identify the roles and responsibilities for FMEA. Turning, again, to my book:

Companies vary widely in how they organize the functions of systems engineering, design engineering, quality, reliability, manufacturing, service and other departments that will provide representation to FMEA teams. There is no template defining the specific roles and responsibilities for carrying out the FMEA tasks, however, there are certain guidelines. FMEA needs the support of a reliability or quality “homeroom”, where the body of knowledge of FMEA is supported with standards, procedures, training, and facilitation. It is usually a good practice to make the design engineer responsible for accomplishing Design FMEAs and the process engineer responsible for accomplishing Process FMEAs, with the support of the skilled resources from the reliability or quality “homeroom.”

My preference is for a trained representative from the quality or reliability department to facilitate the FMEA, with design engineering owning the document. However, I’ve seen companies successfully implement FMEA with design engineering doing the facilitation, as long as the correct team is formed and trained, and the facilitator is trained in the skills of facilitation.

Third, FMEA teams should be trained based on the following guidelines:

FMEA team members need training in the basics of FMEAs before the FMEA team meetings begin. This can either be full team training by an expert in FMEA methods, or at minimum, the team needs a good overview of FMEA fundamentals. If the FMEA team is not familiar with the basics of FMEAs, such as procedure, definitions, examples, and lessons learned, then the meetings will be much longer than necessary and the results will be unsatisfactory.

At minimum, I recommend at least one person being well trained in the fundamentals of FMEA, and leading the effort. The FMEA team can then be trained in an overview of the fundamentals.

Next Article

FMEA procedure includes assessing three types of risk: severity, occurrence, and detection. In the next article, action strategies to reduce severity risk are discussed. Yes, it is possible to reduce the risk related to severity.

 

[display_form id=415]

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.

« Conundrum: Global Warming – Electric Demand
Sunil Part 2 »

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

  • Gremlins today
  • The Power of Vision in Leadership and Organizational Success
  • 3 Types of MTBF Stories
  • ALT: An in Depth Description
  • Project Email Economics

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