Search NASA⌕ Search

SEARCH · Search NASA

Results for “hardware 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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Reliability and Qualification of Hardware to Enhance the Mission Assurance of JPL/NASA Projects

Packaging Qualification and Verification (PQV) and life testing of advanced electronic packaging, mechanical assemblies (motors/actuators), and interconnect technologies (flip-chip), platinum temperature thermometer attachment processes, and various other types of hardware for Mars Exploration Rover (MER)/Mars Science Laboratory (MSL), and JUNO flight projects was performed to enhance the mission assurance. The qualification of hardware under extreme cold to hot temperatures was performed with reference to various project requirements. The flight like packages, assemblies, test coupons, and subassemblies were selected for the study to survive three times the total number of expected temperature cycles resulting from all environmental and operational exposures occurring over the life of the flight hardware including all relevant manufacturing, ground operations, and mission phases. Qualification/life testing was performed by subjecting flight-like qualification hardware to the environmental temperature extremes and assessing any structural failures, mechanical failures or degradation in electrical performance due to either overstress or thermal cycle fatigue. Experimental flight qualification test results will be described in this presentation.

PRTs↗
NASA NTRS2015

Data Applicability of Heritage and New Hardware For Launch Vehicle Reliability Models

Bayesian reliability requires the development of a prior distribution to represent degree of belief about the value of a parameter (such as a component's failure rate) before system specific data become available from testing or operations. Generic failure data are often provided in reliability databases as point estimates (mean or median). A component's failure rate is considered a random variable where all possible values are represented by a probability distribution. The applicability of the generic data source is a significant source of uncertainty that affects the spread of the distribution. This presentation discusses heuristic guidelines for quantifying uncertainty due to generic data applicability when developing prior distributions mainly from reliability predictions.

Al Hassan, Mohammad↗
NASA NTRS2003

System and Software Reliability (C103)

Within the last decade better reliability models (hardware. software, system) than those currently used have been theorized and developed but not implemented in practice. Previous research on software reliability has shown that while some existing software reliability models are practical, they are no accurate enough. New paradigms of development (e.g. OO) have appeared and associated reliability models have been proposed posed but not investigated. Hardware models have been extensively investigated but not integrated into a system framework. System reliability modeling is the weakest of the three. NASA engineers need better methods and tools to demonstrate that the products meet NASA requirements for reliability measurement. For the new models for the software component of the last decade, there is a great need to bring them into a form that they can be used on software intensive systems. The Statistical Modeling and Estimation of Reliability Functions for Systems (SMERFS'3) tool is an existing vehicle that may be used to incorporate these new modeling advances. Adapting some existing software reliability modeling changes to accommodate major changes in software development technology may also show substantial improvement in prediction accuracy. With some additional research, the next step is to identify and investigate system reliability. System reliability models could then be incorporated in a tool such as SMERFS'3. This tool with better models would greatly add value in assess in GSFC projects.

Wallace, Dolores↗
NASA NTRSDate not supplied

Signal and Power Integrity Design Methodology for High-Performance Flight Computing Systems

Computing capabilities of space systems have in-creased onboard performance by orders of magnitude with the use of radiation-tolerant field-programmable gate arrays (FPGA)and processors. The incorporation of signal and power integrity analysis with printed circuit board (PCB) design in reliable computing architectures for space systems has become critical to enable future mission capabilities. Developers launch high-performance processors into a breadth of orbits and missions, running varying applications that create challenges for designing reliable computing hardware. Specifically, for these designs, academic and industry research has focused on component radiation performance, fault mitigation, and reliable architectures. How-ever, other design parameters including electromagnetic interference (EMI), PCB stackup, signal integrity (SI), voltage regulator module (VRM) design, and power distribution network (PDN)are often deprioritized or disregarded as the design matures. Since these characteristics are becoming more significant in high-performance processor designs, this research presents a hardware design and analysis methodology for high-performance, space-computing systems that focuses on a holistic design approach and PDN reliability. While these challenges exist across all space hardware, the reduced PCB dimensions imposed by SmallSats and CubeSats introduce additional hurdles, specifically to VRM and decoupling design. By examining the relationship between the PDN and radiation performance, an analytical relationship is developed that incorporates Total Ionizing Dose and Single-Event Transients to ensure reliability throughout the mission duration. The presented design methodology is applied to the SpaceCube v3.0 Mini, an FPGA-based on-board science data processing system developed at NASA Goddard Space Flight Center.

Advanced avionics↗
NASA NTRS1990

Thermal management of advanced fuel cell power systems

It is shown that fuel cell devices are particularly attractive for the high-efficiency, high-reliability space hardware necessary to support upcoming space missions. These low-temperature hydrogen-oxygen systems necessarily operate with two-phase water. In either PEMFCs (proton exchange membrane fuel cells) or AFCs (alkaline fuel cells), engineering design must be critically focused on both stack temperature control and on the relative humidity control necessary to sustain appropriate conductivity within the ionic conductor. Water must also be removed promptly from the hardware. Present designs for AFC space hardware accomplish thermal management through two coupled cooling loops, both driven by a heat transfer fluid, and involve a recirculation fan to remove water and heat from the stack. There appears to be a certain advantage in using product water for these purposes within PEM hardware, because in that case a single fluid can serve both to control stack temperature, operating simultaneously as a heat transfer medium and through evaporation, and to provide the gas-phase moisture levels necessary to set the ionic conductor at appropriate performance levels. Moreover, the humidification cooling process automatically follows current loads. This design may remove the necessity for recirculation gas fans, thus demonstrating the long-term reliability essential for future space power hardware.

Vanderborgh, N. E.↗
NASA NTRS1972

Long life assurance study for manned spacecraft long life hardware. Volume 1: Summary of long life assurance guidelines

A long life assurance program for the development of design, process, test, and application guidelines for achieving reliable spacecraft hardware was conducted. The study approach consisted of a review of technical data performed concurrently with a survey of the aerospace industry. The data reviewed included design and operating characteristics, failure histories and solutions, and similar documents. The topics covered by the guidelines are reported. It is concluded that long life hardware is achieved through meticulous attention to many details and no simple set of rules can suffice.

Source record↗
NASA NTRS1972

Fabrication and test of eight sets of STRAP 3 flight hardware

The development and characteristics of the Stellar Tracking Rocket Attitude Positioning (STRAP) system are discussed. The objective of the program was to produce eight sets of reliable flight hardware at a cost that was compatible with the typical sounding rocket mission. The flight system consists of: (1) the attitude control system, (2) the pneumatics systems components, and a fine guidance error sensors star tracker. The performance of the system and the areas where improvements are needed are examined. Line drawings and circuit diagrams are presented to amplify the accomplishments of the project.

Greeb, M. E.↗
NASA NTRS2008

Reusability Studies for Ares I and Ares V Propulsion

With a mission to continue to support the goals of the International Space Station (ISS) and explore beyond Earth orbit, the United States National Aeronautics and Space Administration (NASA) is in the process of launching an entirely new space exploration initiative, the Constellation Program. Even as the Space Shuttle moves toward its final voyage, Constellation is building from nearly half a century of NASA spaceflight experience, and technological advances, including the legacy of Shuttle and earlier programs such as Apollo and the Saturn V rocket. Out of Constellation will come two new launch vehicles: the Ares I crew launch vehicle and the Ares V cargo launch vehicle. With the initial goal to seamlessly continue where the Space Shuttle leaves off, Ares will firstly service the Space Station. Ultimately, however, the intent is to push further: to establish an outpost on the Moon, and then to explore other destinations. With significant experience and a strong foundation in aerospace, NASA is now progressing toward the final design of the First Stage propulsion system for the Ares I. The new launch vehicle design will considerably increase safety and reliability, reduce the cost of accessing space, and provide a viable growth path for human space exploration. To achieve these goals, NASA is taking advantage of Space Shuttle hardware, safety, reliability, and experience. With efforts to minimize technical risk and life-cycle costs, the First Stage office is again pulling from NASA s strong legacy in aerospace exploration and development, most specifically the Space Shuttle Program. Trade studies have been conducted to evaluate life-cycle costs, expendability, and risk reduction. While many first stage features have already been determined, these trade studies are helping to resolve the operational requisites and configuration of the first stage element. This paper first presents an overview of the Ares missions and the genesis of the Ares vehicle design. It then looks at one of the most important trade studies to date, the "Ares I First Stage Expendability Trade Study." The purpose of this study was to determine the utility of flying the first stage as an expendable booster rather than making it reusable. To lower the study complexity, four operational scenarios (or cases) were defined. This assessment then included an evaluation of the development, reliability, performance, and transition impacts associated with an expendable solution. This paper looks at these scenarios from the perspectives of cost, reliability, and performance.

Williams, Thomas J.↗
NASA NTRS2008

Reusability Studies for Ares I and Ares V Propulsion

With a mission to continue to support the goals of the International Space Station (ISS) and explore beyond Earth orbit, the United States National Aeronautics and Space Administration (NASA) is in the process of launching an entirely new space exploration initiative, the Constellation Program. Even as the Space Shuttle moves toward its final voyage, Constellation is building from nearly half a century of NASA spaceflight experience, and technological advances, including the legacy of Shuttle and earlier programs such as Apollo and the Saturn V rocket. Out of Constellation will come two new launch vehicles: the Ares I crew launch vehicle and the Ares V cargo launch vehicle. With the initial goal to seamlessly continue where the Space Shuttle leaves off, Ares will firstly service the Space Station. Ultimately, however, the intent is to push further: to establish an outpost on the Moon, and then to explore other destinations. With significant experience and a strong foundation in aerospace, NASA is now progressing toward the final design of the First Stage propulsion system for the Ares I. The new launch vehicle design will considerably increase safety and reliability, reduce the cost of accessing space, and provide a viable growth path for human space exploration. To achieve these goals, NASA is taking advantage of Space Shuttle hardware, safety, reliability, and experience. With efforts to minimize technical risk and life-cycle costs, the First Stage office is again pulling from NASA's strong legacy in aerospace exploration and development, most specifically the Space Shuttle Program. Trade studies have been conducted to evaluate lifecycle costs, expendability, and risk reduction. While many first stage features have already been determined, these trade studies are helping to resolve the operational requisites and configuration of the first stage element. This paper first presents an overview of the Ares missions and the genesis of the Ares vehicle design. It then looks at one of the most important trade studies to date, the "Ares I First Stage Expendability Trade Study." The purpose of this study was to determine the utility of flying the first stage as an expendable booster rather than making it reusable. To lower the study complexity, four operational scenarios (or cases) were defined. This assessment then included an evaluation of the development, reliability, performance, and transition impacts associated with an expendable solution. The paper looks at these scenarios from the perspectives of cost, reliability, and performance. The presentation provides an overview of the paper.

Williams, Thomas J.↗
NASA NTRS1994

Space Hardware Design for Long Life with High Reliability

In 1991, the Cassini Project at JPL funded a study to identify rules for design and test of hardware required to function reliably in space for very long lifetimes. The widest possible range of hardware issues were considered consistent with three constraints: (1) Software and mission rules were addressed only to the extent they affected hardware performance; (2) the rules developed were applicable to a single spacecraft, and multiple spacecraft to achieve mission success were not considered; and (3) high reliability rules were considered only in their relationship to long life. The study was subsequently published as a JPL document. One major conclusion of the workshop was that unattended space missions extending out to 25 years or more are feasible.

hardware↗
NASA NTRSDate not supplied

Green Propulsion : A NASA GSFC Assessment

In the ever-changing paradigm of efficient and capable spacecraft design, scientific missions continue pushing spacecraft subsystems to deliver effective solutions to meet challenging new mission/spacecraft applications. From an in-space storable liquid chemical propulsion perspective, monopropellant hydrazine is a dependable propellant. Bi-propellant architectures offer even superior performance, but add the complexity of a hypergolic fuel (hydrazine/ mono-methyl hydrazine) and oxidizer (Nitrogen Tetroxide/ mixed oxides of nitrogen) dual tank combination. These propulsion system designs (mono-propellant and bi-propellant) have high heritage, high propellant throughput qualified engines, widely tested material compatibility, qualified fluid delivery commercial-off-the-shelf components, known handling practices, and repeatable performance in successfully delivering on mission requirements. NASA and the broader propulsion community have historically selected hypergolic propellants for most mission applications. The space propulsion community has learned to successfully handle these highly toxic and hazardous materials, navigate the regulated use and the associated safety protocols, personnel protective equipment, and unique training standards – all requisite for loading spacecraft propulsion systems with hypergolic propellants. The question now arises as to what is next for in-space chemical propulsion? Is there an alternative, or even replacement, to the reliable hypergolic fluids, or propellant alternatives that promise increased mission benefits? With the evolution and proven advancements in innovative in-space green propellant technologies capable of delivering benefits to scientific missions, concern over the reliability and infusibility of this higher performing and safer to handle class of propellants is waning. As NASA science missions move forward with the potential flight infusion of green propulsion, NASA and the broader propulsion community are working to address remaining gaps in hardware development, reliability, performance, unique operational considerations, and risk mitigations for high value scientific assets.

Henry W. Mulkey↗
NASA NTRS2011

NASA Applications and Lessons Learned in Reliability Engineering

Since the Shuttle Challenger accident in 1986, communities across NASA have been developing and extensively using quantitative reliability and risk assessment methods in their decision making process. This paper discusses several reliability engineering applications that NASA has used over the year to support the design, development, and operation of critical space flight hardware. Specifically, the paper discusses several reliability engineering applications used by NASA in areas such as risk management, inspection policies, components upgrades, reliability growth, integrated failure analysis, and physics based probabilistic engineering analysis. In each of these areas, the paper provides a brief discussion of a case study to demonstrate the value added and the criticality of reliability engineering in supporting NASA project and program decisions to fly safely. Examples of these case studies discussed are reliability based life limit extension of Shuttle Space Main Engine (SSME) hardware, Reliability based inspection policies for Auxiliary Power Unit (APU) turbine disc, probabilistic structural engineering analysis for reliability prediction of the SSME alternate turbo-pump development, impact of ET foam reliability on the Space Shuttle System risk, and reliability based Space Shuttle upgrade for safety. Special attention is given in this paper to the physics based probabilistic engineering analysis applications and their critical role in evaluating the reliability of NASA development hardware including their potential use in a research and technology development environment.

Safie, Fayssal M.↗
NASA NTRS1986

Management of SSME hardware life utilization

Statistical and probabilistic reliability methodologies were developed for the determination of hardware life limits for the Space Shuttle Main Engine (SSME). Both methodologies require that a mathematical reliability model of the engine (system) performance be developed as a function of the reliabilities of the components and parts. The system reliability model should be developed from the Failute Modes and Effects Analysis/Critical Items List. The statistical reliability methodology establishes hardware life limits directly from the failure distributions of the components and parts obtained from statistically-designed testing. The probabilistic reliability methodology establishes hardware life limits from a decision analysis methodology which incorporates the component/part reliabilities obtained from a probabilistic structural analysis, a calibrated maintenance program, inspection techniques, and fabrication procedures. Probilistic structural analysis is recommended as a tool to prioritize upgrading of the components and parts. The Weibull probability distribution is presently being investigated by NASA/MSFC to characterize the failure distribution of the SSME hardware from a limited data base of failures.

Pauschke, J. M.↗
DOE OSTI2016

Verifying quantitative reliability for programs that execute on unreliable hardware

Emerging high-performance architectures are expected to contain unreliable components that may exhibit soft errors, which silently corrupt the results of computations. Full detection and masking of soft errors is challenging, expensive, and, for some applications, unnecessary. For example, approximate computing applications (such as multimedia processing, machine learning, and big data analytics) can often naturally tolerate soft errors. We introduce Rely, a programming language that enables developers to reason about the quantitative reliability of an application—namely, the probability that it produces the correct result when executed on unreliable hardware. Rely allows developers to specify the reliability requirements for each value that a function produces. We perform a static quantitative reliability analysis that verifies quantitative requirements on the reliability of an application, enabling a developer to perform sound and verified reliability engineering. The analysis takes a Rely program with a reliability specification and a hardware specification that characterizes the reliability of the underlying hardware components and verifies that the program satisfies its reliability specification when executed on the underlying unreliable hardware platform. We demonstrate the application of quantitative reliability analysis on six computations implemented in Rely.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS2008

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

It is essential that management and engineering understand the need for an availability requirement for the customer's space transportation system as it enables the meeting of his needs, goal, and objectives. There are three types of availability, e.g., operational availability, achieved availability, or inherent availability. The basic definition of availability is equal to the mean uptime divided by the sum of the mean uptime plus the mean downtime. The major difference is the inclusiveness of the functions within the mean downtime and the mean uptime. This paper will address tIe inherent availability which only addresses the mean downtime as that mean time to repair or the time to determine the failed article, remove it, install a replacement article and verify the functionality of the repaired system. The definitions of operational availability include the replacement hardware supply or maintenance delays and other non-design factors in the mean downtime. Also with inherent availability the mean uptime will only consider the mean time between failures (other availability definitions consider this as mean time between maintenance - preventive and corrective maintenance) that requires the repair of the system to be functional. It is also essential that management and engineering understand all influencing attributes relationships to each other and to the resultant inherent availability requirement. This visibility will provide the decision makers with the understanding necessary to place constraints on the design definition for the major drivers that will determine the inherent availability, safety, reliability, maintainability, and the life cycle cost of the fielded system provided the customer. This inherent availability requirement may be driven by the need to use a multiple launch approach to placing humans on the moon or the desire to control the number of spare parts required to support long stays in either orbit or on the surface of the moon or mars. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability, but also provide the capability to bound the variables providing engineering the insight required to control the system's engineering solution. An example of this visibility will be the need to provide integration of similar discipline functions to allow control of the total parts count of the space transportation system. Also the relationship visibility of selecting a reliability requirement will place a constraint on parts count to achieve a given inherent availability requirement or accepting a larger parts count with the resulting higher reliability requirement. This paper will provide an understanding for the relationship of mean repair time (mean downtime) to maintainability, e.g., accessibility for repair, and both mean time between failure, e.g., reliability of hardware and the system inherent availability. Having an understanding of these relationships and resulting requirements before starting the architectural design concept definition will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Rhodes, Russel E.↗
NASA NTRS2008

Space Transportation System Availability Requirement and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

reliability↗