Search NASASearch

SEARCH · Search NASA

Results for “System reliability”

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.

At least 109 records · Page 6

Application of Analytical Hierarchy Process for Narrowing Down Nep Candidate Reactor Designs

Nuclear electric propulsion (NEP)-powered vehicles have been contemplated for human Mars missions. The nuclear power system contemplates using a high temperature light-weight nuclear reactor for the production of electrical power in the range of 2-5 MWe with a 3-10 year service life. A myriad of technology options exist for achieving these mission objectives. The analytic hierarchy process (AHP), a multi-attribute decision method, is being used to narrow down the candidate designs. The AHP is a structured decision process that fuses model-supplied quantitative data with subjective assessments to facilitate decisions that involve multiple competing criteria. Proven end-to-end nuclear design and systems analysis tools will be used to provide quantitative performance data such as end-to-end system reliability, system robustness to recover from off-normal conditions, system specific weight (α in kg/kWe), and the ability to meet the service life-time and power level requirements. Three high assay low enriched uranium (HALEU) reactor concepts, namely, gas-, heat pipe- and pumped liquid-cooled nuclear cores coupled to a He/Xe gas or supercritical CO2- Brayton power conversion system are being modeled using the AHP to understand the trade-offs associated with these design combinations. In addition to the reactor and power conversion options, there are a myriad of additional components and subsystems – e.g., radiators, heat exchangers, and recuperators – that also figure into the evaluation process. The choice of the right overall system is a multidimensional problem that has to include not only quantitative data, but also the so called “external factors”, examples of which include the component and subsystem Technology Readiness Levels (TRLs), the associated Advancement Degrees of Difficulty (AD2), the cost and schedule required to achieve a technical maturity consistent with mission infusion, alignment with the priorities of NASA’s Space Nuclear Propulsion program, and alignment with other ongoing government and commercial investments in micro reactors. Focused expert elicitations form the basis for qualitative data set. As a final step, decision-makers individually express their opinions regarding the relative importance of the criteria and preferences among the alternatives through pairwise comparisons. The paper will describe the AHP approach, progress to-date applying it to the NEP human Mars mission problem, and preliminary results. Use of AHP provides sufficient flexibility for incorporating industry input at different stages as the technologies evolve through additional research and development. It is expected that the decision process will be ongoing and expanded to examine additional options and technology choices, culminating in a defensible set of candidate reactor concepts that will form the basis for developing a multi-year NEP technology maturation strategy. .

Dasari V Rao

Trends in reliability modeling technology for fault tolerant systems

Reliability modeling for fault tolerant avionic computing systems was developed. The modeling of large systems involving issues of state size and complexity, fault coverage, and practical computation was discussed. A novel technique which provides the tool for studying the reliability of systems with nonconstant failure rates is presented. The fault latency which may provide a method of obtaining vital latent fault data is measured.

Bavuso, S. J.

User's guide to the Reliability Estimation System Testbed (REST)

The Reliability Estimation System Testbed is an X-window based reliability modeling tool that was created to explore the use of the Reliability Modeling Language (RML). RML was defined to support several reliability analysis techniques including modularization, graphical representation, Failure Mode Effects Simulation (FMES), and parallel processing. These techniques are most useful in modeling large systems. Using modularization, an analyst can create reliability models for individual system components. The modules can be tested separately and then combined to compute the total system reliability. Because a one-to-one relationship can be established between system components and the reliability modules, a graphical user interface may be used to describe the system model. RML was designed to permit message passing between modules. This feature enables reliability modeling based on a run time simulation of the system wide effects of a component's failure modes. The use of failure modes effects simulation enhances the analyst's ability to correctly express system behavior when using the modularization approach to reliability modeling. To alleviate the computation bottleneck often found in large reliability models, REST was designed to take advantage of parallel processing on hypercube processors.

Nicol, David M.

On reliable control system designs

A research effort is summarized which addresses some of the current problems in interfacing systems theory and reliability. Reliability is roughly the probability that a system will perform according to specifications for a given amount of time. The reliability of a system depends on the structure of its components. Systems theory and control theory deal with the response characteristics of a system, which depend on the system dynamics. The concepts necessary to unify the structural and the dynamic properties of a system are defined. The result is a definition of what constitutes a reliable systems, from the viewpoint of systems theory, and a methodology which can be used to determine if a given design allows a reliable control system design.

Birdwell, J. Douglas

An Approach to Automate tools for the Risk Assessment of Digital Instrumentation and Control Systems

Reliable digital instrumentation and control systems (DI&C) are integral for sustaining the continued operation of nuclear power plants. These systems ensure that nuclear reactors operate safely, efficiently, and within regulatory requirements. Yet, the cost of designing and licensing new nuclear DI&C can be prohibitively expensive. Under the U.S. Department of Energy Light Water Reactor Sustainability Program, Idaho National Laboratory has developed a framework for supporting the risk-informed design of DI&C systems by offering methods to support the identification, quantification, and evaluation of risks for various DI&C design architectures. The framework indicates potential software failure modes and provides pathways for quantifying the potential for these software failures, including common cause failures. Using the framework’s systematic approach, challenges for assessing risks within new and existing nuclear DI&C systems can be reduced. Nevertheless, the current framework can be further improved using the convenience of automation. This paper introduces the development of Software for the Hazard Identification and Evaluation of Digital Systems (SHIELDS). SHIELDS is an engineering software package that enables the identification, elimination, and mitigation of potential risks and reduces the burden of deploying reliable DI&C systems. This work introduces plans and techniques to digitize and improve the manual risk assessment modules of the framework. These improvements will save time and increase the repeatability and usability of the framework, making it more accessible to a wider range of users. Ultimately, this introduces SHIELDS and how its modules support efficient development of safe and reliable DI&C systems.

46 - INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AN

Diverse Redundant Systems for Reliable Space Life Support

Reliable life support systems are required for deep space missions. The probability of a fatal life support failure should be less than one in a thousand in a multi-year mission. It is far too expensive to develop a single system with such high reliability. Using three redundant units would require only that each have a failure probability of one in ten over the mission. Since the system development cost is inverse to the failure probability, this would cut cost by a factor of one hundred. Using replaceable subsystems instead of full systems would further cut cost. Using full sets of replaceable components improves reliability more than using complete systems as spares, since a set of components could repair many different failures instead of just one. Replaceable components would require more tools, space, and planning than full systems or replaceable subsystems. However, identical system redundancy cannot be relied on in practice. Common cause failures can disable all the identical redundant systems. Typical levels of common cause failures will defeat redundancy greater than two. Diverse redundant systems are required for reliable space life support. Three, four, or five diverse redundant systems could be needed for sufficient reliability. One system with lower level repair could be substituted for two diverse systems to save cost.

life support

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, in a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation; testing results, and other information. Where appropriate, actual performance history was used for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to verify compliance with requirements and to highlight design or performance shortcomings for further decision-making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability and maintainability analysis, and present findings and observation based on analysis leading to the Ground Systems Preliminary Design Review milestone.

Gernand, Jeffrey L.

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, within a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability, and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation, testing results, and other information. Where appropriate, actual performance history was used to calculate failure rates for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to assess compliance with requirements and to highlight design or performance shortcomings for further decision making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability, and maintainability analysis, and present findings and observation based on analysis leading to the Ground Operations Project Preliminary Design Review milestone.

Gernand, Jeffrey L.