Search NASA⌕ Search

SEARCH · Search NASA

Results for “Failure Rate”

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 73 records · Page 4

Development of KSC program for investigating and generating field failure rates. Volume 1: Summary and overview

A summary of the KSC program for investigating the reliability aspects of the ground support activities is presented. An analysis of unsatisfactory condition reports (RC), and the generation of reliability assessment of components based on the URC are discussed along with the design considerations for attaining reliable real time hardware/software configurations.

Bean, E. E.↗

Lognormal Uncertainty Estimation for Failure Rates

"Uncertainty analysis itself is uncertain, therefore, you cannot evaluate it exactly," Source Uncertain. Quantitative results for aerospace engineering problems are influenced by many sources of uncertainty. Uncertainty analysis aims to make a technical contribution to decision-making through the quantification of uncertainties in the relevant variables as well as through the propagation of these uncertainties up to the result. Uncertainty can be thought of as a measure of the 'goodness' of a result and is typically represented as statistical dispersion. This presentation will explain common measures of centrality and dispersion; and-with examples-will provide guidelines for how they may be estimated to ensure effective technical contributions to decision-making.

Britton, Paul T.↗

A PROPOSED METHOD FOR ESTIMATING FAILURE RATES OF DEGRADED PASSIVE COMPONENTS IN THE NRC SIGNIFICANCE DETERMINATION PROCESS

This paper outlines a methodology for estimation of the incremental core damage frequency associated with the degradation of passive components with a view to its application in the US Nuclear Regulatory Commission's significance determination process. The method involves use of simplified physics-based models of materials degradation and the probabilistic comparison of transient loads with deteriorating system capacities.

passives↗

JANTX1N5554 switching diode

Micro Semiconductor and Semtech diodes were tested. In group 1 tests Micro Semiconductor and Semtech lot testing was stopped because of excess failure rate. Failure analysis was performed on group 1 and 3 because of apparent failure mode.

Source record↗

Reliability Research for Photovoltaic Modules

Report describes research approach used to improve reliability of photovoltaic modules. Aimed at raising useful module lifetime to 20 to 30 years. Development of cost-effective solutions to module-lifetime problem requires compromises between degradation rates, failure rates, and lifetimes, on one hand, and costs of initial manufacture, maintenance, and lost energy, on other hand. Life-cycle costing integrates disparate economic terms, allowing cost effectiveness to be quantified, allowing comparison of different design alternatives.

Ross, Ronald J., Jr.↗

Analysis and Optimization of Test Plans for Advanced Exploration Systems Reliability and Supportability

Future crewed exploration missions beyond Low Earth Orbit (LEO) will operate farther from Earth and be logistically isolated for longer than any previous human spaceflight mission. Under these conditions, supportability and reliability willbestronger drivers of mission mass and risk than they have been in the past. Items with high failure rates, or uncertain failure rates, can result in high spares mass requirements and/or high risk on deep space missions. Testing is a critical element of system development which provides the opportunity to identify and resolve design issues, defects, or other failure modes before they cause problems during a mission. Reliability growth programs can reduce failure rates by identifying and remove failure modes via design changes, and long-duration life testing can provide valuable data to reduce failure rate estimate uncertainty and verify (to some level of confidence) that components are as reliable as expected. Testing activities take time and resources, however, and must be incorporated into program plans in order to be fully effective. This paper presents an integrated reliability test plan analysis and optimization methodology, which has been used to inform Advanced Exploration Systems (AES) Life Support Systems (LSS) ground test planning for future missions. The methodology determines the optimal number of test units to purchase and allocation of test time –split between reliability growth and uncertainty reduction testing –across a given set of items in order to minimize spares mass for a given mission under constraints on total test cost and schedule. Model outputs also include expected spares mass after testing and the expected number of modifications or refurbishments during testing, both of which can inform program planning. Discussion of the model, conclusions, and future work are also presented.

Testing↗

Analysis and Optimization of Test Plans for Advanced Exploration Systems Reliability and Supportability

Future crewed exploration missions beyond Low Earth Orbit (LEO) will operate farther from Earth and be logistically isolated for longer than any previous human spaceflight mission. Under these conditions, supportability and reliability willbestronger drivers of mission mass and risk than they have been in the past. Items with high failure rates, or uncertain failure rates, can result in high spares mass requirements and/or high risk on deep space missions. Testing is a critical element of system development which provides the opportunity to identify and resolve design issues, defects, or other failure modes before they cause problems during a mission. Reliability growth programs can reduce failure rates by identifying and remove failure modes via design changes, and long-duration life testing can provide valuable data to reduce failure rate estimate uncertainty and verify (to some level of confidence) that components are as reliable as expected. Testing activities take time and resources, however, and must be incorporated into program plans in order to be fully effective. This paper presents an integrated reliability test plan analysis and optimization methodology, which has been used to inform Advanced Exploration Systems (AES) Life Support Systems (LSS) ground test planning for future missions. The methodology determines the optimal number of test units to purchase and allocation of test time –split between reliability growth and uncertainty reduction testing –across a given set of items in order to minimize spares mass for a given mission under constraints on total test cost and schedule. Model outputs also include expected spares mass after testing and the expected number of modifications or refurbishments during testing, both of which can inform program planning. Discussion of the model, conclusions, and future work are also presented.

Testing↗

Tutorial: Performance and reliability in redundant disk arrays

A disk array is a collection of physically small magnetic disks that is packaged as a single unit but operates in parallel. Disk arrays capitalize on the availability of small-diameter disks from a price-competitive market to provide the cost, volume, and capacity of current disk systems but many times their performance. Unfortunately, relative to current disk systems, the larger number of components in disk arrays leads to higher rates of failure. To tolerate failures, redundant disk arrays devote a fraction of their capacity to an encoding of their information. This redundant information enables the contents of a failed disk to be recovered from the contents of non-failed disks. The simplest and least expensive encoding for this redundancy, known as N+1 parity is highlighted. In addition to compensating for the higher failure rates of disk arrays, redundancy allows highly reliable secondary storage systems to be built much more cost-effectively than is now achieved in conventional duplicated disks. Disk arrays that combine redundancy with the parallelism of many small-diameter disks are often called Redundant Arrays of Inexpensive Disks (RAID). This combination promises improvements to both the performance and the reliability of secondary storage. For example, IBM's premier disk product, the IBM 3390, is compared to a redundant disk array constructed of 84 IBM 0661 3 1/2-inch disks. The redundant disk array has comparable or superior values for each of the metrics given and appears likely to cost less. In the first section of this tutorial, I explain how disk arrays exploit the emergence of high performance, small magnetic disks to provide cost-effective disk parallelism that combats the access and transfer gap problems. The flexibility of disk-array configurations benefits manufacturer and consumer alike. In contrast, I describe in this tutorial's second half how parallelism, achieved through increasing numbers of components, causes overall failure rates to rise. Redundant disk arrays overcome this threat to data reliability by ensuring that data remains available during and after component failures.

Gibson, Garth A.↗

The optimum cost-effective test time for redundant systems with specified reliability and confidence

This paper investigates the optimum test time to determine the number of redundant units needed to achieve high reliability with high confidence. Newly designed systems often have high initial failure rates which can be reduced by testing to find failure modes and remove them by redesign. To accurately estimate the required number of redundant units, the test time must be extended to accurately determine the failure rate. If the measured failure rate is used, there is a 50% chance that the actual hardware failure rate is higher. Using the measured failure rate gives only a 50% confidence that the failure rate and number of spares are not too low. After the test, given the measured failure rate and the desired reliability, the number of spares can be determined and the confidence in the reliability computed. Instead of accepting the reliability results of a fixed duration test, it is possible to set the requirements for both the redundant reliability and the confidence level and then compute the test time needed to minimize the total cost required to achieve these requirements. The confidence that the redundant reliability is not too low is increased by using a higher than measured failure rate to increase the number of spares. The higher number of spares increases cost. Longer test time reduces the variance in the failure rate and the increase in the number of spares, so that test cost increases and spares cost decreases. The total cost is the sum of the cost of the test time and the spares. The optimum test time produces the minimum total cost for the system failure rate, mission length, and required reliability and confidence level. Longer testing is justified by reduced cost. Some examples are given.

Harry W Jones↗

Reliability Growth Modeling and Testing

Reliability growth has been modelled as an exponential decline in the cumulative failure rate that continues indefinitely as long as testing continues. Contrary to this, most reliability growth data show a brief high initial failure rate due to infant mortality followed by a long period of constant low failure rate. A two part failure rate model with an initial exponential decline followed by a constant failure rate usually fits the data and provides a more realistic description of reliability growth. The reliability growth process consists of testing, experiencing failures, finding the failure causes, and redesigning the system to remove them. The cost of reliability growth increases with the number of inherent failure modes and the time needed for them to occur and be removed. The failure modes with the lower failure rates will tend to occur later, as their Mean Time Before Failure (MTBF) is the inverse of the failure rate. Reliability growth testing has diminishing returns, since it takes longer to find and remove the less probable failures.This paper first discusses the reliability bathtub curve and then explains that reliability growth is produced by testing, identifying failure causes, and designing to remove them. A simple model of reliability growth is introduced, with a brief group of early failures followed by a constant failure rate. The cumulative failure rate n(t)/t can decline as rapidly as1/t or t-1butdeclines more slowly if additiona lfailures occur. The 56-failure Crow data seti s used to demonstrate the two-phase model of reliability growth followed by a constant failure rate. 13 additional data sets are modeled, with 9 of the 14 data sets showing reliability growth approximately as n(t)/t =1/t or t-1and substantial final failure rates. The model fits most of the data sets, but 4of the 14 show no reliability growth. The reliability growth period typically includes six failures and extends one-quarter or half the total test time. As reliability growth testing continues, the cumulative failure rate should be tracked to estimate the reliability growth exponent and the final failure rate.

reliability growth modeling↗

Modeling Reliability Growth

Reliability growth has been modelled as an exponential decline in the cumulative failure rate that continues indefinitely as long as testing continues. Contrary to this, most reliability growth data show a brief high initial failure rate due to infant mortality followed by a long period of constant low failure rate. A two part failure rate model with an initial exponential decline followed by a constant failure rate usually fits the data and provides a more realistic description of reliability growth. The reliability growth process consists of testing, experiencing failures, finding the failure causes, and redesigning the system to remove them. The cost of reliability growth increases with the number of inherent failure modes and the time needed for them to occur and be removed. The failure modes with the lower failure rates will tend to occur later, as their Mean Time Before Failure (MTBF) is the inverse of the failure rate. Reliability growth testing has diminishing returns, since it takes longer to find and remove the less probable failures.This paper first discusses the reliability bathtub curve and then explains that reliability growth is produced by testing, identifying failure causes, and designing to remove them. A simple model of reliability growth is introduced, with a brief group of early failures followed by a constant failure rate. The cumulative failure rate n(t)/t can decline as rapidly as1/t or t-1butdeclines more slowly if additiona lfailures occur. The 56-failure Crow data seti s used to demonstrate the two-phase model of reliability growth followed by a constant failure rate. 13 additional data sets are modeled, with 9 of the 14 data sets showing reliability growth approximately as n(t)/t =1/t or t-1and substantial final failure rates. The model fits most of the data sets, but 4of the 14 show no reliability growth. The reliability growth period typically includes six failures and extends one-quarter or half the total test time. As reliability growth testing continues, the cumulative failure rate should be tracked to estimate the reliability growth exponent and the final failure rate.

reliability growth modeling↗

Heroic Reliability Improvement in Manned Space Systems

System reliability can be significantly improved by a strong continued effort to identify and remove all the causes of actual failures. Newly designed systems often have unexpected high failure rates which can be reduced by successive design improvements until the final operational system has an acceptable failure rate. There are many causes of failures and many ways to remove them. New systems may have poor specifications, design errors, or mistaken operations concepts. Correcting unexpected problems as they occur can produce large early gains in reliability. Improved technology in materials, components, and design approaches can increase reliability. The reliability growth is achieved by repeatedly operating the system until it fails, identifying the failure cause, and fixing the problem. The failure rate reduction that can be obtained depends on the number and the failure rates of the correctable failures. Under the strong assumption that the failure causes can be removed, the decline in overall failure rate can be predicted. If a failure occurs at the rate of lambda per unit time, the expected time before the failure occurs and can be corrected is 1/lambda, the Mean Time Before Failure (MTBF). Finding and fixing a less frequent failure with the rate of lambda/2 per unit time requires twice as long, time of 1/(2 lambda). Cutting the failure rate in half requires doubling the test and redesign time and finding and eliminating the failure causes.Reducing the failure rate significantly requires a heroic reliability improvement effort.

life support↗