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 Fred Schenkelberg 1 Comment

Uncovering Hidden Field Failure Problems

Uncovering Hidden Field Failure Problems

A reliable product does not fail often. Customers expect to a level of reliability performance and failures that occur too early dash their expectation.

The design and development team work to create a robust product. To meet the customer’s reliability expectations. The team may use a range of tools to detect any reliability problem prior to launch.

Yet, customers do uncover problems that surprise us. This may be a problem with how we identify and resolve risks, yet it could also be the development process didn’t look close enough to find the issues. Or, worse, we saw the issue and ignored it.

The Question

Received this question last week asking about ways to improve finding issues (and solving them) before customer find them.

So, here is my question to you, if you wouldn’t mind shedding some light on the subject…is it common place to not be able to predict all that could happen? Or are their truly methods that can prevent this? My experience in micro-electronics is that no one has deep enough pockets or long enough patience to flush out all problems. I’m open to a better way of doing this and a better way of thinking.

My Answer

Thanks for the note and question.

Keep in mind that FMEA is only one way to undercover what you and team do not know — lurking failure mechanisms. There are approaches I’ve seen and they are not perfect, yet can help in most cases, including those brand new inventions.

First — with the FMEA approach include those items that you know you don’t know. If not sure about a particular failure mechanism, if or to what extent, something will fail, then include that and tag it for exploration and future study. The other outcome for FMEA is to improve the monitoring capabilities to detect those elements that may happen and are not currently visible (latent defects, age-related defects, etc.)

Second — for truly novel items without any history extend the bench and environmental testing to find the margins. Cause failures and are they as expected. For expensive items use modeling to estimate the stress levels or accumulated damage required to cause failure and run the experiments to verify. Yes, this can be expensive, yet when the uncertainty or modeling suggests a 1% or higher failure rate, we should invest to know the full story.

Third — supply chain risk analysis and process control. This generally isn’t taken too seriously and adds a great amount of risk of your product failing. Again we do not have the time or resources to cover everything, yet if purchasing is driving cost and not quality/reliability that team needs adjusting. I find that a third or more of field issues come from supply chain related root causes. As you know this root cause can become quite a serious outbreak of failures.

Forth — record all prototype (or simulation) failures. Plot cumulative failures over time and monitor the slope. If it is remaining steep you are not done finding issues, if the plot rolls over to a more horizontal line (meaning it is taking longer and longer to find the next issue) then we’ve found all that we’re capable of finding. Regularly review the testing and evaluation methods to look for ways to expand the coverage and range of stresses to help find issues faster and more of them.

Fifth — keep the team aware of past failures in a systemic way. A checklist or database generally do not work. While at HP I learned about a simple process and wrote about it as an example of a role of the quality and reliability manager within an organization.

Culture Matters

One of the biggest factors I find is the organizations that celebrate failures as a gift tend to find and resolve more issues before shipment. Those that reward the hero that quickly solves a field issue, continue to ship products with field issues. If the culture during development is to blame the engineer or technician for the failure rather than understand the root cause and decision process leading the failure really miss an opportunity to improve their product.

Thanks again for the question. Not sure my answer is of much help. Let me know your thoughts.

Filed Under: Articles, Musings on Reliability and Maintenance Topics, on Product Reliability Tagged With: process

About Fred Schenkelberg

I am the reliability expert at FMS Reliability, a reliability engineering and management consulting firm I founded in 2004. I left Hewlett Packard (HP)’s Reliability Team, where I helped create a culture of reliability across the corporation, to assist other organizations.

« 5 Steps to Create a Reliability Plan
Preventive Maintenance Goals and Activities »

Comments

  1. Hilaire Perera says

    August 28, 2019 at 2:28 PM

    Have not seen a person or any organization indicating ” a quantitative measure for quality in FMEA ”

    Failure Modes, Mechanisms and Effects Analysis (FMMEA) enhances the value of FMEA and FMECA by identifying high priority failure mechanisms and failure models. High priority failure mechanisms determine the operational stresses, and the environmental and operational parameters that need to be controlled. Models for the failure mechanisms help in the design and development of a reliable product

    Center for Advanced Life Cycle Engineering CALCE ( http://www.calce.umd.edu/ ) has developed the FMMEA process and helped several organizations implement the tool in their product development process.

    Reply

Leave a Reply Cancel reply

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

Article by Fred Schenkelberg
in the Musings series

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 Articles

  • 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