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

QDD 088 Choose Reliability Goals for Modules

Choose Reliability Goals for Modules

We have a reliability target for our system. But we’re not meeting it.

To avoid this scenario, what is something we can do in early development?

When we’re figuring out our concept, we can better learn about our options. We can work with Reliability Engineers to understand what we know, the risk in what we don’t know, and to prioritize reliability of the modules to be able to meet the reliability of our whole system.

We talk about using reliability allocation to help us choose reliability goals for modules of our product design. And we talk about its limitations.

 

View the Episode Transcript

We looked at a product design from a systems point-of-view, where the system is made of modules.

Things Design Engineers can do to help with Reliability Allocation methods:

  • Share the general architecture of the system.
  • Find good reliability data.
    • Find parts to test. This is a great option, but sometimes not realistic at the time we want to make design choices.
    • Find data on related/similar systems or modules. Ask vendors and research baseline design information.
  • Prioritize for test
    • Evaluate the Systems Architecture Diagram – what is new, different, or has been a problem in the past? Highlight them because those are things we want to be curious about.
    • Use our System FMEA (and/or hazards analysis) as a starting point.
      • Is a module leading to many failure events? (Occurrence rating, or number of times it comes up)
      • Does a module failure lead to a whole system failure? (our Severity rating)

Depending on the data and information available, Reliability Engineers may be able to use software tools to look more closely at reliability targets among the system’s modules:

  • create scenarios of varying reliability targets for modules (reliability block diagrams that use reliability functions)
  • compare the modules based on the probability of a module to cause a system failure (using a ratio of reliability functions)
  • meet a system reliability while minimizing cost (aligning module reliability targets and considering costs of improving the reliability of modules)
  • compare options using the cost of increasing the reliability of modules (using a weighted, subjective factor)

From System Analysis Reference Book by ReliaSoft Corporation. Retrieved December 2, 2022, from ReliaWiki.org. Available under a a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

 

There are limitations with reliability predictions.

Calculating reliabilities without test is tempting (relying on physics of failure or mean failure times), but we sacrifice accuracy and can’t report on a reliability with confidence.

Like other things in product development, we start with knowing very little, analyze the information we have to make decisions, and then iterate on those analyses as we learn more about the product. Reliability allocation is like that, too.

Even with information and if we find relevant data, uncertainty is just part of reliability predictions. That doesn’t mean that it’s not worth doing. The team just needs to understand the uncertainty and make decisions with it appropriately.

What’s today’s insight to action?

We can work with Reliability Engineers in early concept phases with reliability allocation to help us:

  • assess where we should be designing for reliability improvements
  • see where we have knowledge gaps and where risks may lie
  • understand how changing probabilities of failure of subsystems or modules can affect our overall system reliability goals
  • plan for reliability tests later in development

Ultimately, Reliability Engineers can help us better understand where we need to focus for great designs.


To learn more about how to do reliability allocation, I recommend this article series authored by Chris Jackson:

3 Ways to do Reliability Allocation #1

3 Ways to do Reliability Allocation #2

3 Ways to do Reliability Allocation #3

3 Ways to do Reliability Allocation #4

3 Ways to do Reliability Allocation #5


Citations:

Other Quality during Design podcast episodes you might like:

How Does Reliability Engineering Affect (Not Just Assess) Design?

5 Options to Manage Risks during Product Engineering

Quality as a Strategic Asset vs. Quality as a Control

Episode Transcript

We’re testing the reliability of our system and it’s not meeting our goals. We may need to revisit how we set up our reliability goals of our modules, the things that we combine together to make up our system. Let’s talk more about reliability allocation after this brief introduction. Hello and welcome to Quality During Design, the place to use quality thinking to create products, others love for less. Each week we talk about ways to use quality during design, engineering, and product development. My name is Dianna Deeney. I’m a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. Listen in and then join us. Visit quality during design.com.

Do you know what 12 things you should have before a design concept makes it to the engineering drawing board where you’re setting specifications. I’ve got a free checklist for you and you can do some assessments of your own. Where do you stack up with the checklist? You can log into a learning portal to access the checklist and an introduction to more information about how to get those 12 things. To get this free information, just sign up@qualityduringdesign.com. On the homepage, there’s a link in the middle of the page. Just click it and say, I want it.

I have heard this kind of a story from multiple reliability engineers about different projects being done in different companies. A reliability target was set for a system to be, let’s say 90%, so we have a system reliability target of 90%. The team decided to design and test their modules to the same level of reliability, a 90% reliability goal. When the whole system got put together, it didn’t meet that goal. It was much less than the 90% goal. What happened? Well, reliability is a probability and probabilities don’t add up that way. If we have a system reliability of 90%, then at least some of our modules need to be designed to a higher level reliability. Not all of them need to be higher than 90%, but at least one, maybe two of them. It depends. What we really wanna look for is to find a combination of liabilities of our modules that fit within what’s capable in terms of our costs, our timeline, and honestly our technical capability.

Sometimes there’s not a whole lot that we can do to improve the reliability of something. Knowing all of this helps us to reach our system reliability goal, we can look at the performance of the module itself, but then also look at how things are assembled as part of the system. Do we need any redundancies to meet our target reliability? Analyzing information and making proposals about certain module requirements in order to meet a system goal is called reliability allocation, so where do we focus our efforts? Which modules do we choose to have a greater reliability and that requires us to know a bit about the reliability of the modules themselves and our reliability. Engineering friends can help us through this. The first thing that comes to mind when trying to understand the reliability of something is through its testing. We design a test specifically for our use case and we develop reliability models from it.

We may not be able to test everything for, for one. We’re likely working at the concept phase of development because we’re setting our reliability requirements and we don’t have units to test. There are other options we have with our reliability engineers. Just by applying our engineering knowledge and looking at our system as a set of different modules, we can start to understand where we have gaps, where we may need to run a few tests or talk with a supplier about any kind of reliability data they may have generated or how they test their product. We can start researching other similar products we have and see if we have reliability data of those products and understand the differences that we’re looking to make with our design and how that affects the relevance of our data to our new use case. We can choose to focus on certain modules to understand the reliability better, what is new, what is different, or what has been a problem in the past.

Another way to help us choose where to focus is based on risk from our failure mode effects analysis. This is a subjective measure, especially in early concept development, but we can consider it as a starting point. If the failure of one module leads to many failure events, then that’s an indication that we want to take a closer look at that module’s reliability. If the failure of one module leads to a system failure, then we’ll want to look at that. Also, all of this sort of research, learning more about our product, how it’s set up in its architecture with modules, finding data and looking at risk information that we may need to help us assess reliability of the system. Like many other aspects of design in the early phases of development, we’re not going to have a lot of data, but we start with what we know and then iterate on it throughout the development process.

Updating things as we learn more about our product and being intentional about what it is we want to test and learn. Any early reliability work isn’t going to be highly accurate. We may not be able to develop it with a high level of confidence. We can use it as a basis for comparing options and highlighting the features of a design that should have a critical level of reliability. Once we do have reliability data, there are some software solutions that reliability engineers can use to help them calculate things like the probability of a module to cause a system failure. They can create a reliability block diagram which assembles the components by its logic order and can assess how different reliability could affect the entire system. Reliability, reliability engineers can also look at the costs associated with increasing the reliability of modules, and a last note is at the lower the level of the individual parts compared to the whole system, the greater the uncertainty we have in being able to predict the reliability of it.

When we are doing reliability allocation, we wanna look at the modules or subsystems. Individual components are generally reliable based on their limited function and also today’s manufacturing and design standards. When we add that component with others to make a system, our system reliability isn’t as high, and that’s because in our greater system there’s a lot of interactions and actions and different components having an effect on the whole system performance. If you’re interested in learning more about how to do reliability allocation in more detail and how it fits into the broader design development process, I recommend an article series authored by Chris Jackson with the titles. Three Ways to Do Reliability Allocation. It’s a five part article series and I’ll include links to it on the podcast blog. What’s today’s insight to action? At the start of this episode, we talked about trying to meet a system reliability goal and what that means for our different modules that are going to be making up our system with what reliability targets do we need to design those modules for.

We can use the help of reliability engineers through reliability allocation to help us better understand this. They can help us assess where we should be designing for reliability improvements. We can work with them to understand where we have knowledge gaps and where risks may be through them. We can also understand how changing probabilities of failure of subsystems or modules can affect our overall system reliability goals. With all of this, we’ll be able to direct our attention to where it needs to be and we’ll be able to plan for a future testing further in the development process. Ultimately, reliability engineers can help us better understand where we need to focus for great designs.

If you like this topic or the content in this episode, there’s much more on our website including information about how to join our signature coaching program. The quality during design journey consistency is important, so subscribe to the weekly newsletter. This has been a production of Deeney Enterprises. Thanks for listening.

 

Filed Under: Quality during Design

About Dianna Deeney

Dianna is a senior-level Quality Professional and an experienced engineer. She has worked over 20 years in product manufacturing and design and is active in learning about the latest techniques in business.

Dianna promotes strategic use of quality tools and techniques throughout the design process.

Leave a Reply Cancel reply

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

Quality during Design podcast logo

Tips for using quality tools and methods to help you design products others love, for less.


by Dianna Deeney
Quality during Design,
Hosted on Buzzsprout.com
Subscribe and enjoy every episode
Google
Apple
Spotify

Recent Episodes

QDD 128 Leveraging Proven Frameworks or Concept Development

QDD 127 Understanding Cross-Functional Collaboration

QDD 126 Exploring the Problem Space: A Key Principle for Robust Product Design and Project Success

QDD 125 Exploring Product Development and AI Through Literature

QDD 124 Design for User Tasks using an Urgent/Important Matrix

QDD 123 Information Development in Design, with Scott Abel – Part 2 (A Chat with Cross-Functional Experts)

QDD 122 Information Development in Design, with Scott Abel – Part 1 (A Chat with Cross-Functional Experts)

QDD 121 Crafting Effective Technical Documents for the Engineering Field

QDD 120 How to use FMEA for Complaint Investigation

QDD 119 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 118 Journey from Production to Consumption: Enhancing Product Reliability

QDD 117 QDD Redux: Choose Reliability Goals for Modules

QDD 116 Reliability Engineering during Design, with Adam Bahret (A Chat with Cross-Functional Experts)

QDD 115 QDD Redux: 5 Options to Manage Risks during Product Engineering

QDD 114 The Instant Glory of Projects

QDD 113 What to do about Virtual Meetings

QDD 112 QDD Redux: How to self-advocate for more customer face time (and why it’s important)

QDD 111 Engineering with Receptivity, with Sol Rosenbaum (A Chat with Cross-Functional Experts)

QDD 110 Don’t Wish for Cross-Functional Buy-in on Product Designs – Plan to Get It!

QDD 109 Before You Start Engineering Solutions, Do This

QDD 108 QDD Redux Ep. 4: Statistical vs. Practical Significance

QDD 107 QDD Redux Ep. 3: When it’s Not Normal: How to Choose from a Library of Distributions

QDD 106 QDD Redux Ep. 2: How to Handle Competing Failure Modes

QDD 105 QDD Redux Ep. 1: How Many Do We Need to Test?

QDD 104 The Fundamental Thing to Know from Statistics for Design Engineering

QDD 103 What to do for Effective and Efficient Working Meetings

QDD 102 Get Design Inputs with Flowcharts

QDD 101 Quality Tools are Legos of Development (and Their 7 Uses)

QDD 100 Lessons Learned from Coffee Pod Stories

QDD 099 Crucial Conversations in Engineering, with Shere Tuckey (A Chat with Cross-Functional Experts)

QDD 098 Challenges Getting Team Input in Concept Development

QDD 097 Brainstorming within Design Sprints

QDD 096 After the ‘Storm: Compare and Prioritize Ideas

QDD 095 After the ‘Storm: Pareto Voting and Screening Methods

QDD 094 After the ‘Storm: Group and Explore Ideas

QDD 093 Product Design with Brainstorming, with Emily Haidemenos (A Chat with Cross Functional Experts)

QDD 092 Ways to Gather Ideas with a Team

QDD 091 The Spirits of Technical Writing Past, Present, and Future

QDD 090 The Gifts Others Bring

QDD 089 Next Steps after Surprising Test Results

QDD 088 Choose Reliability Goals for Modules

QDD 087 Start a System Architecture Diagram Early

QDD 086 Why Yield Quality in the Front-End of Product Development

QDD 085 Book Cast

QDD 084 Engineering in the Color Economy

QDD 083 Getting to Great Designs

QDD 082 Get Clarity on Goals with a Continuum

QDD 081 Variable Relationships: Correlation and Causation

QDD 080 Use Meetings to Add Productivity

QDD 079 Ways to Partner with Test Engineers

QDD 078 What do We do with FMEA Early in Design Concept?

QDD 077 A Severity Scale based on Quality Dimensions

QDD 076 Use Force Field Analysis to Understand Nuances

QDD 075 Getting Use Information without a Prototype

QDD 074 Finite Element Analysis (FEA) Supplements Test

QDD 073 2 Lessons about Remote Work for Design Engineers

QDD 072 Always Plot the Data

QDD 071 Supplier Control Plans and Design Specs

QDD 070 Use FMEA to Design for In-Process Testing

QDD 069 Use FMEA to Choose Critical Design Features

QDD 068 Get Unstuck: Expand and Contract Our Problem

QDD 067 Get Unstuck: Reframe our Problem

QDD 066 5 Options to Manage Risks during Product Engineering

QDD 065 Prioritizing Technical Requirements with a House of Quality

QDD 064 Gemba for Product Design Engineering

QDD 063 Product Design from a Data Professional Viewpoint, with Gabor Szabo (A Chat with Cross Functional Experts)

QDD 062 How Does Reliability Engineering Affect (Not Just Assess) Design?

QDD 061 How to use FMEA for Complaint Investigation

QDD 060 3 Tips for Planning Design Reviews

QDD 059 Product Design from a Marketing Viewpoint, with Laura Krick (A Chat with Cross Functional Experts)

QDD 058 UFMEA vs. DFMEA

QDD 057 Design Input & Specs vs. Test & Measure Capability

QDD 056 ALT vs. HALT

QDD 055 Quality as a Strategic Asset vs. Quality as a Control

QDD 054 Design Specs vs. Process Control, Capability, and SPC

QDD 053 Internal Customers vs. External Customers

QDD 052 Discrete Data vs. Continuous Data

QDD 051 Prevention Controls vs. Detection Controls

QDD 050 Try this Method to Help with Complex Decisions (DMRCS)

QDD 049 Overlapping Ideas: Quality, Reliability, and Safety

QDD 048 Using SIPOC to Get Started

QDD 047 Risk Barriers as Swiss Cheese?

QDD 046 Environmental Stress Testing for Robust Designs

QDD 045 Choosing a Confidence Level for Test using FMEA

QDD 044 Getting Started with FMEA – It All Begins with a Plan

QDD 043 How can 8D help Solve my Recurring Problem?

QDD 042 Mistake-Proofing – The Poka-Yoke of Usability

QDD 041 Getting Comfortable with using Reliability Results

QDD 040 How to Self-Advocate for More Customer Face Time (and why it’s important)

QDD 039 Choosing Quality Tools (Mind Map vs. Flowchart vs. Spaghetti Diagram)

QDD 038 The DFE Part of DFX (Design For Environment and eXcellence)

QDD 037 Results-Driven Decisions, Faster: Accelerated Stress Testing as a Reliability Life Test

QDD 036 When to use DOE (Design of Experiments)?

QDD 035 Design for User Tasks using an Urgent/Important Matrix

QDD 034 Statistical vs. Practical Significance

QDD 033 How Many Do We Need To Test?

QDD 032 Life Cycle Costing for Product Design Choices

QDD 031 5 Aspects of Good Reliability Goals and Requirements

QDD 030 Using Failure Rate Functions to Drive Early Design Decisions

QDD 029 Types of Design Analyses possible with User Process Flowcharts

QDD 028 Design Tolerances Based on Economics (Using the Taguchi Loss Function)

QDD 027 How Many Controls do we Need to Reduce Risk?

QDD 026 Solving Symptoms Instead of Causes?

QDD 025 Do you have SMART ACORN objectives?

QDD 024 Why Look to Standards

QDD 023 Getting the Voice of the Customer

QDD 022 The Way We Test Matters

QDD 021 Designing Specs for QA

QDD 020 Every Failure is a Gift

QDD 019 Understanding the Purposes behind Kaizen

QDD 018 Fishbone Diagram: A Supertool to Understand Problems, Potential Solutions, and Goals

QDD 017 What is ‘Production Equivalent’ and Why Does it Matter?

QDD 016 About Visual Quality Standards

QDD 015 Using the Pareto Principle and Avoiding Common Pitfalls

QDD 014 The Who’s Who of your Quality Team

QDD 013 When it’s Not Normal: How to Choose from a Library of Distributions

QDD 012 What are TQM, QFD, Six Sigma, and Lean?

QDD 011 The Designer’s Important Influence on Monitoring After Launch

QDD 010 How to Handle Competing Failure Modes

QDD 009 About Using Slide Decks for Technical Design Reviews

QDD 008 Remaking Risk-Based Decisions: Allowing Ourselves to Change our Minds.

QDD 007 Need to innovate? Stop brainstorming and try a systematic approach.

QDD 006 HALT! Watch out for that weakest link

QDD 005 The Designer’s Risk Analysis affects Business, Projects, and Suppliers

QDD 004 A big failure and too many causes? Try this analysis.

QDD 003 Why Your Design Inputs Need to Include Quality & Reliability

QDD 002 My product works. Why don’t they want it?

QDD 001 How to Choose the Right Improvement Model

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

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