动力环境集中监控系统可靠性的提高

为实现电源设备乃至通信机房的少人或无人值守和集中维护,必须建立一套完善的电信局动力环境集中监控系统。文中结合番禺区电信局的实际,讨论了提高系统运行可靠性的几点措施,包括硬件方面与软件方面的手段,关键在于加强系统的运行管理。     

Using an integrated process of data and modeling in HRA

The paper describes an approach taken to estimate the probabilities of failure associated with various railroad tasks to prevent accidents (principally collisions and derailments). These probabilities were estimated using an expert elicitation process that used partially relevant data available from a variety of databases and that were filtered and scaled to make them more directly relevant to the analyses being performed. Extensive qualitative studies were performed prior to the elicitation process to identify relevant contexts under which the tasks can be performed.     

基于可靠性评价的含缺陷核压力管道疲劳寿命预测方法

含缺陷压力管道经缺陷评定合乎使用后,其疲劳寿命的估计具有重要的工程意义。将整个含缺陷压力管道作为一个整体,分析了含缺陷压力管道的疲劳裂纹扩展特点,提出了相应的含缺陷压力管道疲劳寿命的计算过程,并在基于可靠性评价的基础上,给出了核压力管道的可接受失效概率,最终得到了含缺陷核压力管道疲劳寿命预测方法。     

基于模糊数的发射装置模糊可靠性分析

鱼雷发射装置的可靠性直接关系到潜艇武器系统的整体作战效能。考虑到可靠性分析中影响因素的模糊性,本文引入模糊数的概念,对潜艇鱼雷发射装置的可靠性进行分析,并基于模糊数的运算法则,给出了串联系统模糊可靠度的计算方法。     

地地战术导弹飞行可靠性指标评定方法

在小子样情况下 ,利用系统和分系统试验数据对导弹的飞行可靠性指标进行评定 ,从数学上说是系统可靠性综合问题 .运用MML SR方法对新型号地地战术导弹的飞行可靠性指标进行评定 ,避免了MML方法在遇到无失败单元时不适用的缺陷 ,在利用地面试验信息方面有其明显优势 ;运用Bayes方法对改进型导弹的飞行可靠性指标进行评定 ,将不同试验阶段的多源试验信息作为验前信息 ,扩大了信息量 .最后 ,对两种方法在工程应用上遇到的问题进行了讨论 ,并给出了解决方法 .     

液压系统广义可靠性设计

介绍了广义可靠性和有效度的基本概念，简要论述了对液压系统进行广义可靠性设计的重要性，并从可靠性设计和维修性设计两方面提出了提高液压系统有效度的具体措施。／     

石油测井仪器可靠性指标探讨

在分析常用可靠性指标及其应用现状的基础上，根据可靠性理论及石油测井仪器的特点。提出了石油测井仪器的可靠性模型。在探讨常用可靠性指标对石油测井仪器适用性的同时，提出将平衡稳定工作时间NWTURE和免维修测井井次NOLWNM作为石油测井仪器可靠性指标的思想；探讨了获取可靠性指标的途径。给出了推荐使用的石油测井仪器可靠性指标。     

用快切装置替代备自投装置提高厂用电安全可靠性

指出目前厂用电切换装置存在的不足，分析了快切装置的基本原理以及厂用电事故下的成功快切对电厂安全生产的意义，说明了在厂用电切换中尽快应用快切装置的必要性。     

电子产品可靠性设计与成本控制

介绍了可靠性设计过程涉及的质量控制成本的解决方法，通过对最有可能影响可靠性的电路设计、元器件选用等方面的分析，介绍了在降低可靠性设计成本的基础下更好地解决可靠性问题的一些方法。     

Quantitative demonstration and cost considerations of a software fault removal methodology

This paper presents a demonstration of a methodology for fault removal during software development. The methodology encompasses the entire development history, from system and software requirements generation to system test. Thus it considers not only the faults during software testing after formal configuration controls have been invoked, but also the faults discovered prior to that phase: during system and software requirements generation, preliminary design, detailed design and code and unit testing. The agents for fault discovery used in verification and validation are called activities, techniques and tools (AT & Ts) in this paper, each having a certain maximum potential or capability for fault discovery. The AT & Ts considered include the usual specification review activities, and also certain tools not normally applied in ‘standard’ software development, such as automated requirements aids. Application of the methodology yields numbers of residual faults as of each phase of development, including those remaining to be discovered during operations and maintenance. Some previous experience and data on residual faults correspond to these results, indicating that the methodology and choice of parameters are reasonable. The methodology also allows one to calculate a relative loss due to delay in fault discovery, which, as is well known, rises rapidly when faults are not discovered during the phase in which they are generated.