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 307 records · Page 17

JANTX1N3893 diode

Diodes manufactured by Siemens and Motorola were tested. Testing of Motorola diodes was stopped in all 3 groups because 50% failure-rate limit was reached. Siemens lot endured more testing in groups 1 and 2 and completed testing on group 3. Failure analysis was performed for group 2 testing.

Source record↗

LSA field test

After almost four years of endurance testing of photovoltaic modules, no fundamental life-limiting mechanisms were identified that could prevent the twenty-year life goal from being met. The endure data show a continual decline in the failure rate with each new large-scale procurement. Cracked cells and broken interconnects continue to be the principal causes of failure. Although the modules are more adversely affected physically by hot, humid environments than by cool or dry environments there are insufficient data to correlate failure with environment. There is little connection between the outward physical condition of a module and changes in its electrical performance.

Jaffe, P.↗

Is it possible to identify a trend in problem/failure data

One of the major obstacles in identifying and interpreting a trend is the small number of data points. Future trending reports will begin with 1983 data. As the problem/failure data are aggregated by year, there are just seven observations (1983 to 1989) for the 1990 reports. Any statistical inferences with a small amount of data will have a large degree of uncertainty. Consequently, a regression technique approach to identify a trend is limited. Though trend determination by failure mode may be unrealistic, the data may be explored for consistency or stability and the failure rate investigated. Various alternative data analysis procedures are briefly discussed. Techniques that could be used to explore problem/failure data by failure mode are addressed. The data used are taken from Section One, Space Shuttle Main Engine, of the Calspan Quarterly Report dated April 2, 1990.

Church, Curtis K.↗

Stereotactic Radiosurgery for Poor Performance Status Patients

Purpose: Patients with poor performance status (PS), usually defined as a Karnofsky Performance Status of 60 or less, were not eligible for randomized stereotactic radiosurgery (SRS) studies, and many guidelines suggest that whole-brain radiation therapy (WBRT) is the most appropriate treatment for poor PS patients. Methods and Materials: In this retrospective review of our SRS database, we identified 36 patients with PS of 60 or less treated with SRS for central nervous system (CNS) metastatic disease. PS, as defined by the Karnofsky Performance Status, was 60 (27 patients), 50 (8 patients), or 40 (1 patient). The median number of CNS lesions treated was 3. Results: Median overall survival (OS) was 7.2 months (range, 0.73-25.6 months). Fifteen patients (41%) were alive at 6 months, and 6 patients (16.6%) were alive at 1 year. There was no difference in OS in patients who underwent previous WBRT. There were no local failures or cases of radiation toxicity. Distant CNS failures were seen in 9 patients (25%). Conclusions: Our patients with poor PS had reasonable median OS and relatively low distant CNS failure rates. Patients in this patient population may be ideal candidates for SRS compared with WBRT given the low incidence of distant failure over their remaining lives and the favorable logistics of single-fraction treatment for these patients with debility and their caregivers.

62 RADIOLOGY AND NUCLEAR MEDICINE↗

Failure Mode and Effects Analysis for a Photovoltaic Inverter

While PV panel reliability continues to increase, PV inverters become the limiting factor for PV system reliability. Consequently, it is critical to have a generic tool from a third party for PV inverter reliability assessment to help 1) utilities/PV farm operators schedule maintenance in advance, and 2) inverter developers improve the next-generation design. However, these two things cannot be accomplished without first understanding the reasons behind inverter failure. Following this idea, as the first step, it is essential to identify and investigate the most failure-prone components within a PV inverter system. After all, any system is only as reliable as the components that are contained within it. This motivates the failure mode and effects analysis (FMEA) work presented for this workshop. The FMEA is conducted as follows: first, the overview of the methodology on the development of the FMEA is presented; then, based on a top-down approach starting from the PV inverter system, critical inverter components with high failure rates are identified and summarized; afterward, a thorough FMEA study at a component-level is performed and its results, including failure modes, failure mechanisms, and critical stressors, are tabulated; finally, according to three rankings (chance of occurrence, severity of occurrence, and ease of detection prior to failure) for each failure mechanism provided by the FMEA, risk priority numbers are calculated and the failure mechanisms along with the critical stressors are ranked in terms of their potentially detrimental effect on the PV inverter.

Brown, Buck↗

On-orbit spacecraft reliability

Operational and historic data for 350 spacecraft from 52 U.S. space programs were analyzed for on-orbit reliability. Failure rates estimates are made for on-orbit operation of spacecraft subsystems, components, and piece parts, as well as estimates of failure probability for the same elements during launch. Confidence intervals for both parameters are also given. The results indicate that: (1) the success of spacecraft operation is only slightly affected by most reported incidents of anomalous behavior; (2) the occurrence of the majority of anomalous incidents could have been prevented piror to launch; (3) no detrimental effect of spacecraft dormancy is evident; (4) cycled components in general are not demonstrably less reliable than uncycled components; and (5) application of product assurance elements is conductive to spacecraft success.

Bloomquist, C.↗

Report of the Odyssey FPGA Independent Assessment Team

An independent assessment team (IAT) was formed and met on April 2, 2001, at Lockheed Martin in Denver, Colorado, to aid in understanding a technical issue for the Mars Odyssey spacecraft scheduled for launch on April 7, 2001. An RP1280A field-programmable gate array (FPGA) from a lot of parts common to the SIRTF, Odyssey, and Genesis missions had failed on a SIRTF printed circuit board. A second FPGA from an earlier Odyssey circuit board was also known to have failed and was also included in the analysis by the IAT. Observations indicated an abnormally high failure rate for flight RP1280A devices (the first flight lot produced using this flow) at Lockheed Martin and the causes of these failures were not determined. Standard failure analysis techniques were applied to these parts, however, additional diagnostic techniques unique for devices of this class were not used, and the parts were prematurely submitted to a destructive physical analysis, making a determination of the root cause of failure difficult. Any of several potential failure scenarios may have caused these failures, including electrostatic discharge, electrical overstress, manufacturing defects, board design errors, board manufacturing errors, FPGA design errors, or programmer errors. Several of these mechanisms would have relatively benign consequences for disposition of the parts currently installed on boards in the Odyssey spacecraft if established as the root cause of failure. However, other potential failure mechanisms could have more dire consequences. As there is no simple way to determine the likely failure mechanisms with reasonable confidence before Odyssey launch, it is not possible for the IAT to recommend a disposition for the other parts on boards in the Odyssey spacecraft based on sound engineering principles.

Mayer, Donald C.↗

Probability and Confidence Trade-space (PACT) Evaluation: Accounting for Uncertainty in Sparing Assessments

There are two general shortcomings to the current annual sparing assessment: 1. The vehicle functions are currently assessed according to confidence targets, which can be misleading- overly conservative or optimistic. 2. The current confidence levels are arbitrarily determined and do not account for epistemic uncertainty (lack of knowledge) in the ORU failure rate. There are two major categories of uncertainty that impact Sparing Assessment: (a) Aleatory Uncertainty: Natural variability in distribution of actual failures around an Mean Time Between Failure (MTBF) (b) Epistemic Uncertainty : Lack of knowledge about the true value of an Orbital Replacement Unit's (ORU) MTBF We propose an approach to revise confidence targets and account for both categories of uncertainty, an approach we call Probability and Confidence Trade-space (PACT) evaluation.

Anderson, Leif↗

Redundant integrated flight control/navigation inertial sensor complex

A redundant strapdown inertial navigation system for integrated flight control/navigation use is described. Design of the system, which consists of four tuned-gimbal gyros, eight accelerometers, and four processors, is discussed, with emphasis on its compact configuration (13 by 13 by 14 in.), based on symmetry properties of an octahedron. A matrix operator for least-squares combination of data from an arbitrary number of two-degree-of-freedom gyros is derived, and general parity equations for error analysis are given. Self-contained detection and isolation of a two-axis gyro failure is considered; system failure probability, which depends on component failure rates and self-correction capacities, is analyzed. Test data, including typical parity equation responses during motion and simulated gyro and accelerometer failures, are also presented.

Ebner, R. E.↗

Independent Review of Mitigating System Performance Indicator Reporting in the EPIX Database

This report summarizes work done to verify the component, failure mode, and method of detection information provided in the Equipment Performance Information Exchange (EPIX) to support implementation of Mitigating Systems Performance Indices. This task is to select reports from EPIX and determine if their categorization as MSPI or non-MSPI failures is consistent with the development of unreliability baseline failure rates, and whether this significantly affects estimates of plant risk. This review is of all MSPI devices in EPIX that were reported as failures. The components include emergency generators; motor-driven, turbine-driven, and enginedriven pumps; and air and motor-operated valves. The date range for this report includes all MSPI device reported failures from 2003 to the most current EPIX data at the INL (up to the 3rd quarter 2008).

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Predicting Computer System Failures Using Support Vector Machines

Mitigating the impact of computer failure is possible if accurate failure predictions are provided. Resources, applications, and services can be scheduled around predicted failure and limit the impact. Such strategies are especially important for multi-computer systems, such as compute clusters, that experience a higher rate failure due to the large number of components. However providing accurate predictions with sufficient lead time remains a challenging problem. This paper describes a new spectrum-kernel Support Vector Machine (SVM) approach to predict failure events based on system log files. These files contain messages that represent a change of system state. While a single message in the file may not be sufficient for predicting failure, a sequence or pattern of messages may be. The approach described in this paper will use a sliding window (sub-sequence) of messages to predict the likelihood of failure. The frequency representation of the message sub-sequences observed are then used as input to the SVM that associates the messages to a class of failed or non-failed system. Experimental results using actual system log files from a Linux-based compute cluster indicate the proposed SVM approach can predict hard disk failure with an accuracy of 76% one day in advance.

99 GENERAL AND MISCELLANEOUS↗

Reliability Effects of Surge Current Testing of Solid Tantalum Capacitors

Solid tantalum capacitors are widely used in space applications to filter low-frequency ripple currents in power supply circuits and stabilize DC voltages in the system. Tantalum capacitors manufactured per military specifications (MIL-PRF-55365) are established reliability components and have less than 0.001% of failures per 1000 hours (the failure rate is less than 10 FIT) for grades D or S, thus positioning these parts among electronic components with the highest reliability characteristics. Still, failures of tantalum capacitors do happen and when it occurs it might have catastrophic consequences for the system. This is due to a short-circuit failure mode, which might be damaging to a power supply, and also to the capability of tantalum capacitors with manganese cathodes to self-ignite when a failure occurs in low-impedance applications. During such a failure, a substantial amount of energy is released by exothermic reaction of the tantalum pellet with oxygen generated by the overheated manganese oxide cathode, resulting not only in destruction of the part, but also in damage of the board and surrounding components. A specific feature of tantalum capacitors, compared to ceramic parts, is a relatively large value of capacitance, which in contemporary low-size chip capacitors reaches dozens and hundreds of microfarads. This might result in so-called surge current or turn-on failures in the parts when the board is first powered up. Such a failure, which is considered as the most prevalent type of failures in tantalum capacitors [I], is due to fast changes of the voltage in the circuit, dV/dt, producing high surge current spikes, I(sub sp) = Cx(dV/dt), when current in the circuit is unrestricted. These spikes can reach hundreds of amperes and cause catastrophic failures in the system. The mechanism of surge current failures has not been understood completely yet, and different hypotheses were discussed in relevant literature. These include a sustained scintillation breakdown model [1-3]; electrical oscillations in circuits with a relatively high inductance [4-6]; local overheating of the cathode [5,7, 8]; mechanical damage to tantalum pentoxide dielectric caused by the impact of MnO2 crystals [2,9, 10]; or stress-induced-generation of electron traps caused by electromagnetic forces developed during current spikes [11]. A commonly accepted explanation of the surge current failures is that at unlimited current supply during surge current conditions, the self-healing mechanism in tantalum capacitors does not work, and what would be a minor scintillation spike if the current were limited, becomes a catastrophic failure of the part [l, 12]. However, our data show that the scintillation breakdown voltages are significantly greater that the surge current breakdown voltages, so it is still not clear why the part, which has no scintillations, would fail at the same voltage during surge current testing (SCT).

Teverovsky, Alexander↗

Hydrogen Equipment Enclosure Risk Reduction through Earlier Detection of Component Failures

Hydrogen component reliability and the hazard associated with failure rates is a critical area of research for the successful implementation and growth of hydrogen technology across the globe. The research team has partnered to quantify system risk reduction through earlier detection of hydrogen component failures. A model of hydrogen dispersion in a hydrogen equipment enclosure has been developed utilizing experimentally quantified hydrogen component leak rates as inputs. This model provides insight into the impact of hydrogen safety sensors and ventilation on the flammable mass within a hydrogen equipment enclosure. This model also demonstrates the change in safety sensor response time due to detector placement under various leak scenarios. The team looks to improve overall hydrogen system safety through an improved understanding of hydrogen component reliability and risk mitigation methods. This collaboration fits under the work program of IEA Hydrogen Task 43 Subtask E Hydrogen System Safety.

CFD↗

DIVA/DeviceEditor (DIVA) v6.0.0

The DIVA software interfaces a process in which researchers design their DNA with a web-based graphical user interface (DeviceEditor), submit their designs to a central queue, and a few weeks later receive their sequence-verified clonal constructs. Each researcher independently designs the DNA to be constructed with a web-based BioCAD tool, and presses a button to submit their designs to a central queue. Researchers have web-based access to their DNA design queues, and can track the progress of their submitted designs as they progress from "evaluation", to "waiting for reagents", to "in progress", to "complete". Researchers access their completed constructs through the central DNA repository. Along the way, all DNA construction success/failure rates are captured in a central database. Once a design has been submitted to the queue, a small number of dedicated staff evaluate the design for feasibility and provide feedback to the responsible researcher if the design is either unreasonable (e.g., encompasses a combinatorial library of a billion constructs) or small design changes could significantly facilitate the downstream implementation process. The dedicated staff then use DNA assembly design automation software to optimize the DNA construction process for the design, leveraging existing parts from the DNA repository where possible and ordering synthetic DNA where necessary. Once all requisite process inputs are available, the design progresses from "waiting for reagents" to "in progress" in the design queue. Human-readable and machine-parseable DNA construction protocols output by the DNA assembly design automation software are then executed by the dedicated staff exploiting lab automation devices wherever possible. Since the all employed DNA construction methods are sequence-agnostic, standardized (utilize the same enzymatic master mixes and reaction conditions), completely independent DNA construction tasks can be aggregated into the same multi-well plates and pursued in parallel. The resulting sets of cloned constructs can then be screened by high-throughput next-gen sequencing platforms for sequence correctness. A combination of long read-length (e.g., PacBio) and paired-end read platforms (e.g., Illumina) would be exploited depending the particular task at hand (e.g., PacBio might be sufficient to screen a set of pooled constructs with significant gene divergence). Post sequence verification, designs for which at least one correct clone was identified will progress to a "complete" status, while designs for which no correct clones were identified will progress to a "failure" status. Depending on the failure mode (e.g., no transformants), and how many prior attempts/variations of assembly protocol have been already made for a given design, subsequent attempts may be made or the design can progress to a "permanent failure" state. All success and failure rate information will be captured during the process, including at which stage a given clonal construction procedure failed (e.g., no PCR product) and what the exact failure was (e.g. assembly piece 2 missing). This success/failure rate data can be leveraged to refine the DNA assembly design process.

Plahar, Hector↗

DIVA V1.0

The DIVA software interfaces a process in which researchers design their DNA with a web-based graphical user interface, submit their designs to a central queue, and a few weeks later receive their sequence-verified clonal constructs. Each researcher independently designs the DNA to be constructed with a web-based BioCAD tool, and presses a button to submit their designs to a central queue. Researchers have web-based access to their DNA design queues, and can track the progress of their submitted designs as they progress from "evaluation", to "waiting for reagents", to "in progress", to "complete". Researchers access their completed constructs through the central DNA repository. Along the way, all DNA construction success/failure rates are captured in a central database. Once a design has been submitted to the queue, a small number of dedicated staff evaluate the design for feasibility and provide feedback to the responsible researcher if the design is either unreasonable (e.g., encompasses a combinatorial library of a billion constructs) or small design changes could significantly facilitate the downstream implementation process. The dedicated staff then use DNA assembly design automation software to optimize the DNA construction process for the design, leveraging existing parts from the DNA repository where possible and ordering synthetic DNA where necessary. SynTrack software manages the physical locations and availability of the various requisite reagents and process inputs (e.g., DNA templates). Once all requisite process inputs are available, the design progresses from "waiting for reagents" to "in progress" in the design queue. Human-readable and machine-parseable DNA construction protocols output by the DNA assembly design automation software are then executed by the dedicated staff exploiting lab automation devices wherever possible. Since the all employed DNA construction methods are sequence-agnostic, standardized (utilize the same enzymatic master mixes and reaction conditions), completely independent DNA construction tasks can be aggregated into the same multi-well plates and pursued in parallel. The resulting sets of cloned constructs can then be screened by high-throughput next-gen sequencing platforms for sequence correctness. A combination of long read-length (e.g., PacBio) and paired-end read platforms (e.g., Illumina) would be exploited depending the particular task at hand (e.g., PacBio might be sufficient to screen a set of pooled constructs with significant gene divergence). Post sequence verification, designs for which at least one correct clone was identified will progress to a "complete" status, while designs for which no correct clones wereidentified will progress to a "failure" status. Depending on the failure mode (e.g., no transformants), and how many prior attempts/variations of assembly protocol have been already made for a given design, subsequent attempts may be made or the design can progress to a "permanent failure" state. All success and failure rate information will be captured during the process, including at which stage a given clonal construction procedure failed (e.g., no PCR product) and what the exact failure was (e.g. assembly piece 2 missing). This success/failure rate data can be leveraged to refine the DNA assembly design process.

Source record↗

DIVA V2.0

The DIVA software interfaces a process in which researchers design their DNA with a web-based graphical user interface, submit their designs to a central queue, and a few weeks later receive their sequence-verified clonal constructs. Each researcher independently designs the DNA to be constructed with a web-based BioCAD tool, and presses a button to submit their designs to a central queue. Researchers have web-based access to their DNA design queues, and can track the progress of their submitted designs as they progress from "evaluation", to "waiting for reagents", to "in progress", to "complete". Researchers access their completed constructs through the central DNA repository. Along the way, all DNA construction success/failure rates are captured in a central database. Once a design has been submitted to the queue, a small number of dedicated staff evaluate the design for feasibility and provide feedback to the responsible researcher if the design is either unreasonable (e.g., encompasses a combinatorial library of a billion constructs) or small design changes could significantly facilitate the downstream implementation process. The dedicated staff then use DNA assembly design automation software to optimize the DNA construction process for the design, leveraging existing parts from the DNA repository where possible and ordering synthetic DNA where necessary. SynTrack software manages the physical locations and availability of the various requisite reagents and process inputs (e.g., DNA templates). Once all requisite process inputs are available, the design progresses from "waiting for reagents" to "in progress" in the design queue. Human-readable and machine-parseable DNA construction protocols output by the DNA assembly design automation software are then executed by the dedicated staff exploiting lab automation devices wherever possible. Since the all employed DNA construction methods are sequence-agnostic, standardized (utilize the same enzymatic master mixes and reaction conditions), completely independent DNA construction tasks can be aggregated into the same multi-well plates and pursued in parallel. The resulting sets of cloned constructs can then be screened by high-throughput next-gen sequencing platforms for sequence correctness. A combination of long read-length (e.g., PacBio) and paired-end read platforms (e.g., Illumina) would be exploited depending the particular task at hand (e.g., PacBio might be sufficient to screen a set of pooled constructs with significant gene divergence). Post sequence verification, designs for which at least one correct clone was identified will progress to a "complete" status, while designs for which no correct clones wereidentified will progress to a "failure" status. Depending on the failure mode (e.g., no transformants), and how many prior attempts/variations of assembly protocol have been already made for a given design, subsequent attempts may be made or the design can progress to a "permanent failure" state. All success and failure rate information will be captured during the process, including at which stage a given clonal construction procedure failed (e.g., no PCR product) and what the exact failure was (e.g. assembly piece 2 missing). This success/failure rate data can be leveraged to refine the DNA assembly design process.

CHEN, JOANNA↗

Reliability analysis of Skylab ATM solar cell modules

A detailed reliability analysis was performed on both types of Skylab Apollo telescope mount solar cell modules. Failure rates used were based on testing of several modules of each type for over 4000 thermal cycles. The analysis delineated several important differences between the failure modes of the two differently designed solar cell modules, and, more importantly, showed that the modules can be expected to meet all mission requirements.

Jones, G. M.↗

Reliability analysis of structures under periodic proof tests in service

A reliability analysis of structures subjected to random service loads and periodic proof tests treats gust loads and maneuver loads as random processes. Crack initiation, crack propagation, and strength degradation are treated as the fatigue process. The time to fatigue crack initiation and ultimate strength are random variables. Residual strength decreases during crack propagation, so that failure rate increases with time. When a structure fails under periodic proof testing, a new structure is built and proof-tested. The probability of structural failure in service is derived from treatment of all the random variables, strength degradations, service loads, proof tests, and the renewal of failed structures. Some numerical examples are worked out.

Yang, J.-N.↗