Speaking Of Reliability: Friends Discussing Reliab 5i293l

A Good Reliability Engineer Abstract Kirk and Fred discuss a simple question of what being a practical and sound reliability engineer means. Key Points Kirk and Fred as they discuss the different aspects of reliability engineering and what they need to be a good reliability engineer Topics include: The results of effective reliability development for a new product may take years to emerge from field data. Few will what contributed to its success if it is proven reliable. A skilled reliability engineer will ask many questions about why a product failed, tracing back through the manufacturing processes and use conditions to determine the root cause. Understanding material science and the history of past products is also crucial for identifying the cause of failure. Companies do not design products solely for marginal or exceptional use cases; instead, by creating a product that meets the fundamental strength limit with standard materials and processes, they achieve a robust design that is more tolerant of marginal use conditions. A proficient reliability engineer can effectively communicate the reliability risks, potential solutions, and cost savings associated with modifying a product to enhance its robustness. Gaining insight into the product, its usage, the manufacturing process, customer expectations, past failure mechanisms, and stress testing results is essential to becoming a competent reliability engineer. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes Please click on this link to access a relatively new analysis of traditional reliability prediction methods article from the US ARMY and CALCE titled  “Reliability Prediction – Continued Reliance on a Misleading Approach”. It is in the public domain, so please distribute freely. Attempting to predict reliability  is a misleading and costly approach to use for developing a reliable system. You can now purchase the most recent recording of Kirk Gray’s Hobbs Engineering 8 (two 4 hour sessions) hour Webinar “Rapid and Robust Reliability Development 2022 HALT & HASS Methodologies Online Seminar” from this link. For more information on the newest discovery testing methodology here is a link to the book “Next Generation HALT and HASS: Robust design of Electronics and Systems” written by Kirk Gray and John Paschkewitz. The post SOR 1053 A Good Reliability Engineer appeared first on Accendo Reliability.

Confidence Reliability Abstract Kirk and Fred discuss the term confidence and its use in reliability engineering Key Points Kirk and Fred as they discuss confidence in predicted failure distributions and the use of reliability engineering. Topics include: Knowing how and why a system fails, such as a modem, and the variations in the environmental stresses is critical to understanding and knowledge of intrinsic wear out of components. When you have only one sample for evaluation from three separate vendors, and when we accelerate the physics driving the wear out, and they all exceed by orders of magnitude the required field use life, we can be confident that any of them will meet the life requirements. Some major considerations for determining whether a component or system will work as intended for the required time can be the quality of the manufacturing, installation, and maintenance over time. Here is a link to Chris Jackson’s webinar titled “Confidence is a measure of you”. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes Please click on this link to access a relatively new analysis of traditional reliability prediction methods article from the US ARMY and CALCE titled  “Reliability Prediction – Continued Reliance on a Misleading Approach”. It is in the public domain, so please distribute freely. Attempting to predict reliability  is a misleading and costly approach to use for developing a reliable system. You can now purchase the most recent recording of Kirk Gray’s Hobbs Engineering 8 (two 4 hour sessions) hour Webinar “Rapid and Robust Reliability Development 2022 HALT & HASS Methodologies Online Seminar” from this link. For more information on the newest discovery testing methodology here is a link to the book “Next Generation HALT and HASS: Robust design of Electronics and Systems” written by Kirk Gray and John Paschkewitz. The post SOR 1052 Confidence Reliability appeared first on Accendo Reliability.

Reliability and Safety Abstract Carl and Fred discuss the difference between the body of knowledge of reliability and safety, and how they work together. Key Points Carl and Fred as they discuss the different roles and responsibilities of reliability and safety activities. Topics include: What is anticipated misuse of a product, and how is that incorporated into reliability applications? What is role of regulatory requirements in reliability versus safety? Difference between performance and safety requirements. How do the four elements in the definition of reliability relate to this discussion? Fail safe: We don’t want product to fail; but if it does we want it to fail safely. Risk analysis includes both severity and probability of occurrence. Severity assessment includes potential safety impacts. Fault tolerance and degraded performance Role of tradeoff studies in decisions about safety and reliability. In an FMEA, is it a failure if the product is used slightly outside the operating envelope? What if the failure is very severe? Discussion of concerns, and how they can be used as input to failure modes. Using AI as input to discussions, to be sure nothing is missed. Both Safety and reliability are essential in products. If product fails, ask what happens (the consequence). Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1051 Reliability and Safety appeared first on Accendo Reliability.

A Curse of Reliability Engineers Abstract Carl and Fred discuss the importance of reliability engineering and customer service working together to increase reliability and safety from the customer point of view. It is very important to understand how customers actually use your product, and customer service staff are uniquely positioned to provide that insight. Key Points Carl and Fred as they discuss how reliability engineers can improve customer service, and how customer service can provide critical reliability information. Topics include: Deg customer service activities to satisfy both experienced s and inexperienced s. How should reliability engineers interact with customer service? What is the value? Reliability engineers should sit and listen to customer service calls. Reliability engineers can teach customer service staff what questions to ask customers to decipher valid reliability issues. What about “anticipated misuse”? Should reliability consider anticipated misuse? The answer is “yes.” Customer service can quickly escalate issues from people who already understand have used the first-level diagnostics. Excellent customer service creates word-of-mouth advocacy. AI is an opportunity to improve customer service, with faster diagnostics. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1050 A Curse of Reliability Engineers appeared first on Accendo Reliability.

The Testing Strategy Abstract Enrico and Fred discuss a couple of ways to approach planning reliability testing. Key Points Enrico and Fred as they discuss a question about testing everything or not. Topics include: Testing is expensive and must create a meaningful result. One approach is to test everything – difficult, time-consuming, etc. Another is to identify key decisions and test to create information necessary to make correct decisions. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1049 The Testing Strategy appeared first on Accendo Reliability.

Why Set a Reliability Goal Abstract Chris and Fred discuss the importance of (trying to) set a reliability goal. Simple … right? Key Points Chris and Fred as they discuss reliability goal setting. How do we do them? What makes good ones? How do we not set bad ones? Topics include: Intents and catchphrases are not goals. ‘We have a five-year warranty!’ Great … what is the five-year reliability goal to this warranty period? ‘It should last 20 years!’ Cool … not all will, so how many can fail over twenty years if this is indeed cool. ‘It should not fail for our customer in the first two years of operations.’ Magnificent … but which customer? … are they on a boat? … is the product being delivered by a third-party courier who has no idea what is in the box? … don’t even know why this is a problem? The ‘quality’ or ‘validation and verification’ team is not in charge. We have come across plenty of organizations where the ‘testing team’ has said that if you can’t test it, it can’t be a requirement. Wrong. Testing is not the only way to measure something. Real example … a ‘quality control team’ in a company successfully had the requirement ‘device must be easy to use’ removed from the specifications because it could not be tested. Effort is often mistaken as outcomes. Sometimes writing down things feels good. Having reliability goals and objectives in some document somewhere might make a board of directors feel good. But what happens when no one in the organization is aware of these goals? … or if they are aware – care about those goals. Goals need to matter, challenge designers, be feasible, and have personal ramifications when they aren’t met. So this means you need to really focus on getting this right. Some organizations say ‘we are success-orientated’ as a shield against looking for and focusing on how their products fail. Every product will fail. There are ‘failure-orientated’ organizations and ‘success-DISorientated organizations.’ Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes The post SOR 1048 Why Set a Reliability Goal appeared first on Accendo Reliability.

Why Set a Reliability Goal Abstract Chris and Fred discuss the importance of (trying to) set a reliability goal. Simple … right? Key Points Chris and Fred as they discuss reliability goal setting. How do we do them? What makes good ones? How do we not set bad ones? Topics include: Intents and catchphrases are not goals. ‘We have a five-year warranty!’ Great … what is the five-year reliability goal to this warranty period? ‘It should last 20 years!’ Cool … not all will, so how many can fail over twenty years if this is indeed cool. ‘It should not fail for our customer in the first two years of operations.’ Magnificent … but which customer? … are they on a boat? … is the product being delivered by a third-party courier who has no idea what is in the box? … don’t even know why this is a problem? The ‘quality’ or ‘validation and verification’ team is not in charge. We have come across plenty of organizations where the ‘testing team’ has said that if you can’t test it, it can’t be a requirement. Wrong. Testing is not the only way to measure something. Real example … a ‘quality control team’ in a company successfully had the requirement ‘device must be easy to use’ removed from the specifications because it could not be tested. Effort is often mistaken as outcomes. Sometimes writing down things feels good. Having reliability goals and objectives in some document somewhere might make a board of directors feel good. But what happens when no one in the organization is aware of these goals? … or if they are aware – care about those goals. Goals need to matter, challenge designers, be feasible, and have personal ramifications when they aren’t met. So this means you need to really focus on getting this right. Some organizations say ‘we are success-orientated’ as a shield against looking for and focusing on how their products fail. Every product will fail. There are ‘failure-orientated’ organizations and ‘success-DISorientated organizations.’ Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes The post SOR 1048 Why Set a Reliability Goal appeared first on Accendo Reliability.

Review of RAMS 2025 Abstract Chris and Fred discuss the success or otherwise of the Reliability and Maintainability Symposium (RAMS) 2025 … with a focus on AI. What are your thoughts? Key Points Chris and Fred as they discuss the success of RAMS 2025 and its focus on AI. This year, RAMS 2025 was held in Florida. Topics include: How did its focus on AI go? RAMS historically has ‘themes’ that rarely reflect what it is all about. This year’s theme was about ‘AI.’ While there was a fair bit of AI content, it didn’t feel like this was any more than what was included last year. And unfortunately, AI appeared to be touted as a universal panacea to reliability issues. It isn’t. You come up with a crumby design for a new product, AI won’t all of a sudden make it reliable. Conference ‘academic’ writing standards remain a challenge. Technically, to get accepted into a journal or conference proceedings, a paper needs to reflect something that is ‘new’ or adds to the ‘state of the art.’ However, some of the best stories are people talking about mistakes they made on their journey to making something amazing and reliable. These stories often get rejected by the paper selection committee as they are not ‘technical enough.’ But then the papers that are ‘technical enough’ tend to address a very small fraction of real world problems. So it is hard to understand what is ‘acceptable’ or ‘not’ … meaning we get a wide range of papers in of quality and relevance. Location, Location, Location! The RAMS hotel selections remain inexplicable. The nearest ‘main’ airport is almost two hours away! The hotel, while nice, is so isolated that it charges like wounded bulls for food, amenities, and so on. This matters! When people are choosing which conference to attend, conferences held in expensive, hard-to-reach places are not a selling point. The RAMS committee can only pretend to openly complain and worry about how to attract future attendees while travelling to the dumbest places to hold conferences so many times … Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes The post SOR 1047 Review of RAMS 2025 appeared first on Accendo Reliability.

Building a Reliability Team Abstract Dianna and Fred discuss building a reliability team. Key Points Dianna and Fred as they discuss building a reliability team. Topics include: the difference between being a manager and building/leading a team. why a reliability program should not rely on one person. the importance of business risk and how to quantify it with input from a team. how ad hoc teams can solve problems and create opportunities for continuous improvement. Plus, find out how a reliability engineer saved a company millions of dollars by building a team to solve a problem. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes Fred and Dianna discuss the differences between being a manager and building a team, noting that simply managing a department is very different from creating a team to solve a specific problem. They emphasize that a reliability program should not be built around one person, as that program will disappear when that person leaves the organization. Building a team requires influence, explaining the benefits, and getting people to understand what’s in it for them. A key element of a team is understanding business risk. The team can assist with putting a dollar amount on the risk to get a project going. Ad hoc teams can be useful to solve problems, like a customer complaint, or for continuous improvement. The team should include people from different parts of the organization. In one case, a reliability engineer built a team that saved a company millions of dollars by identifying bottlenecks in the prototype process. There can be reliability lessons in business systems and processes as well. The post SOR 1046 Building a Reliability Team appeared first on Accendo Reliability.

Complex AI Reliability Abstract Dianna and Fred discuss complex AI reliability. Key Points Dianna and Fred as they discuss complex AI reliability: using AI for complex systems. Topics include: the pitfalls of trusting AI without proper validation and monitoring. how small errors in AI decision-making can compound and lead to unreliable outcomes. why good data and established practices are essential before implementing AI in maintenance and planning. day trading, comedies, and quality scorecards Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes In this episode of Speaking of Reliability, Fred and Dianna discuss complex AI reliability, in using AI for complex systems. They share their experiences with AI, noting that while it can be a helpful start, it’s not always a finished product. They also talk about a use study of using AI for stock trading. The goal was to use AI as an agent for decision making. It’s an example of compounding probabilities, with risk and uncertainty in those decisions. The discussion highlights the risk of relying on AI without proper validation, as small errors in AI decision-making can compound and lead to unreliable outcomes. They emphasize that AI is only as good as the data it’s trained on, and that good data and established practices are essential before implementing AI. They conclude that AI is a tool that needs to be evaluated and monitored. The post SOR 1045 Complex AI Reliability appeared first on Accendo Reliability.

Reliability Engineer or No Abstract Enrico and Fred discuss about the role of the reliability engineer in modern organizations. Key Points Fred and Enrico in an engaging conversation about the evolving role of the reliability engineer in organizations and the broader question: Should reliability engineering be a dedicated function, or should it be integrated across teams? This episode covers: Centralized vs. Distributed Reliability Expertise Discussing the pros and cons of having a dedicated reliability engineer versus embedding reliability knowledge across teams. Insights into how organizations with a strong reliability culture achieve product excellence, even without dedicated reliability roles. The Importance of Collaboration and Culture Why embedding reliability into simultaneous engineering teams fosters better outcomes than working in silos. Examples of how a reliability mindset can be effectively distributed across functions like design, marketing, and manufacturing. Teaching and Coaching: The True Role of a Reliability Engineer Transitioning from running tests to empowering teams with reliability knowledge. How training and mentorship help build a culture of reliability excellence within organizations. Challenges in Creating a Reliability Mindset Overcoming outdated practices and checklist-based reliability programs. Strategies for moving beyond test-focused approaches to prevent issues before they arise. Success Stories and Lessons Learned Anecdotes from organizations that shifted their approach to reliability. Exploring how training, collaboration, and management buy-in lead to lasting improvements. This episode offers practical advice for reliability professionals and decision-makers striving to elevate their organization's approach to reliability engineering. Whether you’re a seasoned engineer or new to the field, you’ll find valuable perspectives to enhance your impact. Audio RSS Show Notes   The post SOR 1044 Reliability Engineer or No appeared first on Accendo Reliability.

Value of Failures Abstract Kirk and Fred discuss how many companies discard or never get back failed parts or subsystems even though they are high-value gold in the quest to make a more reliable product. Key Points Kirk and Fred as they discuss why so few companies realize the value of field failure returns, testing to limits, and the distribution of stress limits in testing several samples of a new product during development. Topics include: Semantics and the reliability engineers use are critical in selling a new reliability evaluation process. For instance, the term destruct limit used in HALT (Highly Accelerated LIMIT tests) may sound to non-engineers as if you were going to smash it to pieces and then analyze the pieces. Many companies test-to- and then scrap the used samples when a better use would be to take those samples and find and compare the operational and sometimes destruct limits, what Kirk has termed comparative limits analysis, The potential costs of a weak link during product development testing will be exponentially more expensive to a manufacturer when it fails in the field, so it is a good bet that companies should err on the side of making it more robust. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes Please click on this link to access a relatively new analysis of traditional reliability prediction methods article from the US ARMY and CALCE titled  “Reliability Prediction – Continued Reliance on a Misleading Approach”. It is in the public domain, so please distribute freely. Attempting to predict reliability  is a misleading and costly approach to use for developing a reliable system. You can now purchase the most recent recording of Kirk Gray’s Hobbs Engineering 8 (two 4 hour sessions) hour Webinar “Rapid and Robust Reliability Development 2022 HALT & HASS Methodologies Online Seminar” from this link. For more information on the newest discovery testing methodology here is a link to the book “Next Generation HALT and HASS: Robust design of Electronics and Systems” written by Kirk Gray and John Paschkewitz. The post SOR 1043 Value of Failures appeared first on Accendo Reliability.

Reliability Tradeoffs Abstract Kirk and Fred discuss the tradeoffs involved in developing a reliable product. Key Points Kirk and Fred as they discuss how, during product development, we have to limit the amount of robustness we can achieve so that it is on schedule and cost-competitive. Topics include: HALT is to find weaknesses in new products using standard materials and processes for most common electronics up to the technology’s fundamental limit. Some products, such as oil exploration tools as Measurement While Drilling (MWD) electronics and interplanetary robots, have unique extreme conditions that are the exceptions. Experience conducting and analyzing HALT processes results in understanding the capabilities of electronic material’s stress limits and their relevance to past failures. HALT is not just breaking and fixing products during development. Engineers should use multiple samples for any HALT process to confirm a low limit. Reliability engineers must justify every limit cause and proposed improvement by tying the potential reliability risk of not improving to known field failure issues. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. SOR 1042 Reliability TradeoffsKirk Grayshare Social: Link: Embed: https://episodes.reliability.fm/sor/sor-1042-reliability-tradeoffs.mp3 Audio RSS Show Notes Please click on this link to access a relatively new analysis of traditional reliability prediction methods article from the US ARMY and CALCE titled “Reliability Prediction Continued Reliance on a Misleading Approach.” It is in the public domain, so please distribute freely. Attempting to predict reliability is a misleading and costly approach to ecording of Kirk Gray’s Hobbs Engineering 8 (two 4 hour sessions) hour Webinar “Rapid and Robust Reliability Development 2022 HALT & HASS Methodologies Online Seminar” from this link. For more information on the newest discovery testing methodology here is a link to the book “Next Generation HALT and HASS: Robust design of Electronics and Systems” written by Kirk Gray and John Paschkewitz.

Service Life Requirements Abstract Enrico and Fred discuss one of the most critical questions in reliability engineering. Play Episode

Getting it Right Abstract Philip and Fred discuss the value of precision maintenance. Key Points Philip and Fred as they discuss the need to purchase, install, and maintain equipment with precision. Topics include: A mindset to get it right and enjoy the benefits Alignment as an example Rotating equipment benefits significantly with ‘getting it right’ attention to detail. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1040 Getting it Right appeared first on Accendo Reliability.

Competing Risk or Not Abstract Philip and Fred discuss the considerations when the dataset does not have competing risks. Key Points Philip and Fred as they discuss the difference in data analysis and results when the dataset does or does not have competing risks of failure. Topics include: What are competing risks? The extreme value family of distributions. Does your software just assume competing risks? Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1039 Competing Risk or Not appeared first on Accendo Reliability.

FMEA and AI Abstract Carl and Fred discuss Failure Mode and Effects Analysis and Artificial Intelligence. There are emerging integration opportunities and challenges, which will be discussed in this podcast. Key Points Carl and Fred as they discuss the opportunities and pitfalls to incorporating AI techniques with FMEA. Topics include: Discussion of Automated FMEA versus team-based FMEA. Use of ChatGPT with FMEA Discussion of example of capacitor failures and the use of historical data, augmented by an understanding of new technology. What is role of AI in ing FMEA? How do models integrate with FMEA? What portion of FMEA can be prepared before team meetings? Functions, some failure modes and other information can be prepared. However, be cautious of pre-filling a form, as people don’t see what isn’t there. FMEA preparation is input for consideration and should be team reviewed. FMEA Cause usually needs subject matter expertise to get to root cause, especially for new technology, new applications and new environments. A good role for AI interface is with thought-starter questions and things to consider. FMEA is not done when form is filled out. 3 reasons for human team involvement: overcoming blind spots, exposing different backgrounds and experiences, and team synergy comes up with new viewpoints. FMEA is organized brainstorm; it’s a thinking exercise. FMEA is not done until risk is reduced to acceptable level. It is not fill-out-the-form activity. Past FMEAs are not necessarily good FMEAs. Use FMEA quality objectives to evaluate how good FMEA are. Understand the limitations of AI, and be open to its uses in FMEA. Don’t be bashful to ask question. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1038 FMEA and AI appeared first on Accendo Reliability.

NUDD Abstract Carl and Fred discuss an interesting question from an Accendo listener. The question has to do with what is called NUDD: New, Unique, Difficult, Different. Specifically the listener’s management wanted to know if their NUDD process could replace FMEA. Key Points Carl and Fred as they deep dive into NUDD and FMEA. They examine both methods to see how they relate to each other. Topics include: What is NUDD, and how does it work? What is the relationship between NUDD and FMEA? Can NUDD replace FMEA, and if not, why not? NUDD helps to identify higher risk issues, and can track follow up. FMEA is a deeper analysis that gets to root cause, risk analysis to prioritize issues, and recommendations to reduce risk. NUDD and FMEA can work together. NUDD does not replace FMEA. NUDD can be front end to FMEA to help identify focus areas. Don’t forget interfaces; more than half problems occur at interfaces. Discussion about following standards versus analytical thinking Reliability is a way of thinking, not merely a set of topics and methods. FMEA is not a “fill out the form” exercise. Don’t forget field history, as input to selecting projects. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes   The post SOR 1037 NUDD appeared first on Accendo Reliability.

Defined Environment Abstract Kirk and Fred discuss Key Points Kirk and Fred as they discuss Topics include: point 1 point 2 point 3 Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes Please click on this link to access a relatively new analysis of traditional reliability prediction methods article from the US ARMY and CALCE titled  “Reliability Prediction – Continued Reliance on a Misleading Approach”. It is in the public domain, so please distribute freely. Trying to predict reliability for development is a misleading a costly approach. You can now purchase the most recent recording of Kirk Gray’s Hobbs Engineering 8 (two 4 hour sessions) hour Webinar “Rapid and Robust Reliability Development 2022 HALT & HASS Methodologies Online Seminar” from this link. For more information on the newest discovery testing methodology here is a link to the book “Next Generation HALT and HASS: Robust design of Electronics and Systems” written by Kirk Gray and John Paschkewitz. The post SOR 1036 Defined Environment appeared first on Accendo Reliability.

Make it Less Robust Abstract Dianna and Fred discuss requests to engineers to make it less robust. Key Points Dianna and Fred as they discuss the situation where engineers are asked to make something less robust. Topics include: Planned obsolescence and its impact on product design. Deg products to last a specific time, not too long, not too short. Why some products are designed to break, and how it affects the consumer. The business and marketing reasons behind planned obsolescence. Why some companies are moving towards design for repairability and sustainable materials. Enjoy an episode of Speaking of Reliability. Where you can friends as they discuss reliability topics. us as we discuss topics ranging from design for reliability techniques to field data analysis approaches. Audio RSS Show Notes In this episode, Fred and Dianna discuss why we may make it less robust. This includes the concept of planned obsolescence and how it impacts product design. They explore the idea of why some products are made to fail and the business reasons behind this practice. One story involves a company that designs products with a specific lifespan, aiming for a 10-year warranty, while another story discusses how a contract incentivized a company to make products that would fail. They also consider how the market drives the business and how product reliability can affect sales. The conversation also touches upon the movement towards design for repairability and the use of sustainable materials. The discussion highlights the trade-offs that businesses make between product longevity, cost, and market demand. They conclude by emphasizing that while perfect reliability is an ideal goal, it may not always align with business objectives. The post SOR 1034 Make it Less Robust appeared first on Accendo Reliability.