Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Common-Cause Failure”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

41 records · Page 3

Finite-Test-Case Development to Demonstrate Logical Integrity of Software in DRPS

Reactor protection system (RPS) in nuclear power plant (NPP) is in the process of digitalization in response to advanced features of digital systems. In this context, software integrity in the RPS becomes an important issue since it may cause common-cause failure. Therefore, to guarantee the safety of NPPs, the integrity of the software need to be properly demonstrated or assessed. There are three typical approaches for software reliability quantification: software reliability growth model (SRGM), Bayesian belief network (BBN), and test-based method. Basically, SRGM is difficult to apply to the safety-critical software because not only sufficient failure sets are unavailable but consequence of system failure is also unacceptable. Then the result obtained through the BBN model may have large uncertainty, so it produces difficulties in integrity demonstration of safety-critical software. Thus, the BBN result need to be complemented or verified by test-based method. Currently, for the integrity demonstration of safety-critical software, black-box test which feeds inputs and examines just outputs whether they succeeded or failed is considered based on trajectory-form-of-input (a series of successive values for the input variables that occur during the operation of the software over time). Usually these trajectory-inputs are randomly sampled from operational profile. In this approach, however, there are some practical difficulties. Therefore, we proposed a new test method for safety-critical software in digitalized reactor protection system (DRPS). The main contents described in this paper are about basic concepts under development of finite-test-cases by which the integrity of the software logic can be verified. It should be noted that the influence of the environments, such as operating system and other hardware, are not considered since the method focuses on software logic only. (authors)

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Sensitivity and Importance Measure Analyses for Various Design Architectures for High Safety-Significant Safety-Related Digital Instrumentation and Control Systems of Nuclear Power Plants

A transition from analog instrumentation and control (I&C) technologies to digital I&C technologies is taking place for license renewals of existing nuclear power plants and for operating licenses of new advanced reactors. This transition necessitates research on risk and economic assessments of digital I&C technologies to ensure the long-term safety and reliability of vital systems, reduce uncertainty in licensing costs in addition to timeline, support integration of digital I&C systems in the plant, and find the most efficient technology upgrades. Adding redundancy within systems or components is a common means of improving design safety; however, it can also make designs more prone to common-cause failures (CCFs). Introducing diversity into redundant systems or components is a way to mitigate and possibly eliminate CCFs, but it also increases plant complexity and may be costly. The balance between redundancy and diversity remains a challenge for digital I&C systems. This study performs sensitivity and importance analyses for four design architectures of two digital I&C systems—the reactor-trip system and the engineered safety features actuation system. For each system, two architectures are examined, including a redundant, non-diverse configuration and a redundant, diverse configuration. The sensitivity analysis will provide insights on the impact of introducing diversity to system reliability. The importance results will help identify risk-significant and risk-sensitive components and failure modes, which may be good candidates for future design improvement.

99 GENERAL AND MISCELLANEOUS↗

Common-Cause Component Group Modeling Issues in Probabilistic Risk Assess

Common cause failures (CCFs) have been recognized as significant risk contributors in probabilistic risk assessments (PRAs) for commercial nuclear power plants (NPPs) since 1980s. A series of reports including those of United States Nuclear Regulatory Commission (NRC) regulations (NUREGs) have been published from late 1980s to early 2000s to provide guidelines for performing CCF event data analysis and modeling CCF in PRA. However, there are still some issues existed in CCF modeling and CCF parameter estimations. One of such issues is the modeling of multiple common-cause component group (CCCG) for the same component in a PRA model. This paper exams the CCCG definition and the requirements from the PRA standard, investigates the CCCG modeling practices and issues existing in PRAs, and presents systematic approaches and guidelines to model CCCG in PRA properly and consistently.

99 GENERAL AND MISCELLANEOUS↗

Developing Generic Prior Distributions for Common Cause Failure Alpha Factors and Causal Alpha Factors

This report is a revision of the original report, INL/LTD-17-43723. Distribution of the original report was to the Nuclear Regulatory Commission (NRC) only, and the report was not made available to the public. The original report was revised as this report for public distribution. This report presents the latest update of generic prior distributions for common cause failure (CCF) alpha factors, as well as the development of new generic prior distributions for CCF causal alpha factors. The history of CCF treatment and parameter estimations is reviewed. The existing process for developing generic prior distributions is reviewed and used to develop new priors for CCF alpha factors and causal alpha factors. For causal alpha factors, different priors are developed for the five different CCF cause groups: Component (GC), Design (GD), Environment (GE), Human (GH), and Other (GO). These generic prior distributions could be used in the Standardized Plant Analysis Risk (SPAR) models for CCF parameter estimation. The issues and preliminary thoughts regarding prior distribution development are documented. Potential future work is then proposed for improving the process of developing priors.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Multiversion software reliability through fault-avoidance and fault-tolerance

In this project we have proposed to investigate a number of experimental and theoretical issues associated with the practical use of multi-version software in providing dependable software through fault-avoidance and fault-elimination, as well as run-time tolerance of software faults. In the period reported here we have working on the following: We have continued collection of data on the relationships between software faults and reliability, and the coverage provided by the testing process as measured by different metrics (including data flow metrics). We continued work on software reliability estimation methods based on non-random sampling, and the relationship between software reliability and code coverage provided through testing. We have continued studying back-to-back testing as an efficient mechanism for removal of uncorrelated faults, and common-cause faults of variable span. We have also been studying back-to-back testing as a tool for improvement of the software change process, including regression testing. We continued investigating existing, and worked on formulation of new fault-tolerance models. In particular, we have partly finished evaluation of Consensus Voting in the presence of correlated failures, and are in the process of finishing evaluation of Consensus Recovery Block (CRB) under failure correlation. We find both approaches far superior to commonly employed fixed agreement number voting (usually majority voting). We have also finished a cost analysis of the CRB approach.

Vouk, Mladen A.↗