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

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

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.     

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

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

地震平衡技术及其在地震反演中的应用

地震平衡技术是一种在地震反演中改善井震关系的新技术。它通过单井对比、空间分形建模以及平衡处理的手段 ,克服地震反演中子波空变的影响 ,使得经过地震平衡技术处理的地震剖面井震关系得到较好改善 ,从而可以用统一的子波对研究区的地震资料进行反演     

岩石物理横波速度曲线计算技术

横波速度是地震勘探中的重要参数。针对实际生产中缺乏横波速度测井曲线资料，利用经验公式计算精确度不高的问题，通过对横波速度计算理论模型的研究分析，选择Blot-Gassman模型法，利用岩石矿物成分、流体成分、孔隙度及密度等测井曲线进行横波速度测井曲线的计算，并对横波速度计算技术和流程进行研究。在实际工区进行了横波速度曲线计算，计算结果与实测横波吻合程度较高，误差小于10％，该技术在储层和流体识别预测的应用中取得了较好效果。     

世界地震勘探仪器装备技术发展综述--记新千年首届物探装备技术研讨会

2001年4月，石油物探装备学会在北京召开了新千年首届技术研讨会，本文根据与会外国公司发布的信息，围绕当前地震勘探仪器的技术现状和发展进行了综合评述，并提出了一些看法和观点。     

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

在分析常用可靠性指标及其应用现状的基础上，根据可靠性理论及石油测井仪器的特点。提出了石油测井仪器的可靠性模型。在探讨常用可靠性指标对石油测井仪器适用性的同时，提出将平衡稳定工作时间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.