Reliability predictions — more than the sum of the parts

J. McLinn
{"title":"Reliability predictions — more than the sum of the parts","authors":"J. McLinn","doi":"10.1109/RAMS.2008.4925837","DOIUrl":null,"url":null,"abstract":"Reliability predictions have been the subject of much discussion over the prior 20 years. Some articles have proclaimed them to be valueless while other articles suggest importance. Spending a great amount of time calculating numbers does not present value directly. Using the numbers as the basis for additional positive activities would seem to be one reason for predictions. Any reliability prediction should be considered as a single tool in a larger reliability improvement tool box that often feeds other more important activities. This role of predictions in a larger reliability world will be explored here. Examples of follow-on improvement activities include, lessons learned about components, identification of critical components, identification of critical design features, estimation of high-stress conditions, approaches for derating, design for reliability, design for manufacture, input to an FMEA, input to a verification test plan, and warranty and repair estimates. The prediction is not an end of the process, but rather the beginning of the larger reliability improvement and design review process. Here, the value of predictions will be tied to lessons learned and outcomes. Predictions have fundamentally changed over the last 20 years for several reasons. As Failure-in-Time (FIT) numbers have declined in most handbooks, the MTBF prediction didn't always match subsequent field data on an absolute scale. It is possible to be a factor of three different or more. Each successive issue of Telcordia or the Mil Handbook 217 (now 217Plus), appears rather similar to the prior ones. This simplicity masks some of the evolution in numerical content and models. There is much to be learned from a short review of the prediction process itself. Failure rate estimates from tables are not trustworthy for they depend upon experience, customer applications, models and other unknown items. At some point it is time to wrap up the prediction phase and move onto improvement and feed other reliability tools. The ldquoLessons Learnedrdquo based upon knowledge of the design, manufacture, customer environment or are valuable. Items in lessons learned might cover a variety of situations that can enhance or detract from estimated reliability. Other lessons learned are contained in design guidelines, derating standards. All of these should be addressed early in any project, once a Bill of Materials (BOM) has been generated. Each has an impact on the prediction estimate but are not overtly included in the process.","PeriodicalId":143940,"journal":{"name":"2008 Annual Reliability and Maintainability Symposium","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2008-01-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2008 Annual Reliability and Maintainability Symposium","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RAMS.2008.4925837","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 3

Abstract

Reliability predictions have been the subject of much discussion over the prior 20 years. Some articles have proclaimed them to be valueless while other articles suggest importance. Spending a great amount of time calculating numbers does not present value directly. Using the numbers as the basis for additional positive activities would seem to be one reason for predictions. Any reliability prediction should be considered as a single tool in a larger reliability improvement tool box that often feeds other more important activities. This role of predictions in a larger reliability world will be explored here. Examples of follow-on improvement activities include, lessons learned about components, identification of critical components, identification of critical design features, estimation of high-stress conditions, approaches for derating, design for reliability, design for manufacture, input to an FMEA, input to a verification test plan, and warranty and repair estimates. The prediction is not an end of the process, but rather the beginning of the larger reliability improvement and design review process. Here, the value of predictions will be tied to lessons learned and outcomes. Predictions have fundamentally changed over the last 20 years for several reasons. As Failure-in-Time (FIT) numbers have declined in most handbooks, the MTBF prediction didn't always match subsequent field data on an absolute scale. It is possible to be a factor of three different or more. Each successive issue of Telcordia or the Mil Handbook 217 (now 217Plus), appears rather similar to the prior ones. This simplicity masks some of the evolution in numerical content and models. There is much to be learned from a short review of the prediction process itself. Failure rate estimates from tables are not trustworthy for they depend upon experience, customer applications, models and other unknown items. At some point it is time to wrap up the prediction phase and move onto improvement and feed other reliability tools. The ldquoLessons Learnedrdquo based upon knowledge of the design, manufacture, customer environment or are valuable. Items in lessons learned might cover a variety of situations that can enhance or detract from estimated reliability. Other lessons learned are contained in design guidelines, derating standards. All of these should be addressed early in any project, once a Bill of Materials (BOM) has been generated. Each has an impact on the prediction estimate but are not overtly included in the process.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
可靠性预测-超过部分的总和
在过去的20年中,可靠性预测一直是许多讨论的主题。一些文章宣称它们毫无价值,而另一些文章则认为它们很重要。花费大量时间计算数字并不能直接显示价值。利用这些数字作为额外积极活动的基础,似乎是做出预测的原因之一。任何可靠性预测都应该被看作是一个更大的可靠性改进工具箱中的一个工具,这个工具箱经常为其他更重要的活动提供支持。本文将探讨预测在更大的可靠性世界中的作用。后续改进活动的例子包括:关于组件的经验教训、关键组件的识别、关键设计特征的识别、高应力条件的估计、降额方法、可靠性设计、制造设计、FMEA的输入、验证测试计划的输入,以及保证和维修估计。预测不是过程的结束,而是更大的可靠性改进和设计评审过程的开始。在这里,预测的价值将与经验教训和结果联系在一起。在过去的20年里,由于几个原因,预测发生了根本性的变化。由于大多数手册中的FIT数据都在下降,因此MTBF预测在绝对尺度上并不总是与后续的现场数据相匹配。它可能是三个不同或更多的因素。Telcordia或《军事手册217》(现为《217 plus》)的每一期都与前几期相当相似。这种简单性掩盖了数值内容和模型的一些演变。从对预测过程本身的简短回顾中可以学到很多东西。表中的故障率估计是不可信的,因为它们依赖于经验、客户应用程序、模型和其他未知项目。在某种程度上,是时候结束预测阶段,转向改进和提供其他可靠性工具了。所学到的问题和经验是基于对设计、制造、客户环境的了解,或者是有价值的。经验教训中的项目可能涵盖各种情况,可以提高或降低估计的可靠性。其他经验教训包含在设计指南、降额标准中。在任何项目的早期,一旦生成了物料清单(BOM),就应该处理所有这些问题。每一个都对预测估计有影响,但没有公开地包括在过程中。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
What's wrong with bent pin analysis, and what to do about it A systems reliability approach to decision making in autonomous multi-platform systems operating a phased mission Software tools for PRA Optimal highway maintenance policies under uncertainty Reliability analysis of phased-mission systems using Bayesian networks
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1