Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “hardware 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.

At least 361 records · Page 20
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Reliability Improvements in Liquid Rocket Engine Instrumentation

Instrumentation hardware is often the weak link in advanced liquid fueled propulsion systems. The development of the Space Shuttle Main Engine (SSME) was no exception. By sheer necessity, a reusable, high energy, low weight engine system often relegates the instrumentation hardware to the backseat in the critical hardware development process. This produces less than optimum hardware constraints; including size, location, mounting, redundancy, and signal conditioning. This can negatively affect the development effort and ultimately the system reliability. The challenge was clear, however, the outcome was less certain. Unfortunately, the SSME hardware development culminated in series of measurement failures, most significant of which was the premature engine shutdown during the launch of STS-51F on July 29, 1985. The Return to Flight activities following the Challenger disaster redoubled our efforts to eliminate, once and for all, sensor malfunctions as the determining factor in overall engine reliability. This paper describes each phase of this effort in detail and includes discussion of the tasks related to improving measurement reliability.

Hill, A.↗
NASA NTRS2010

Project Interface Requirements Process Including Shuttle Lessons Learned

Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings

Bauch, Garland T.↗
NASA NTRS2013

Implementing a Microcontroller Watchdog with a Field-Programmable Gate Array (FPGA)

Reliability is crucial to safety. Redundancy of important system components greatly enhances reliability and hence safety. Field-Programmable Gate Arrays (FPGAs) are useful for monitoring systems and handling the logic necessary to keep them running with minimal interruption when individual components fail. A complete microcontroller watchdog with logic for failure handling can be implemented in a hardware description language (HDL.). HDL-based designs are vendor-independent and can be used on many FPGAs with low overhead.

Straka, Bartholomew↗
NASA NTRS2015

Contamination Control for Thermal Engineers

The presentation will be given at the 26th Annual Thermal Fluids Analysis Workshop (TFAWS 2015) hosted by the Goddard Spaceflight Center (GSFC) Thermal Engineering Branch (Code 545). This course will cover the basics of Contamination Control, including contamination control related failures, the effects of contamination on Flight Hardware, what contamination requirements translate to, design methodology, and implementing contamination control into Integration, Testing and Launch.

Design↗
NASA NTRS2002

Analysis and Design of Crew Sleep Station for ISS

This paper details the analysis and design of the Temporary Sleep Station (TeSS) environmental control system for International Space Station (ISS). The TeSS will provide crewmembers with a private and personal space, to accommodate sleeping, donning and doffing of clothing, personal communication and performance of recreational activities. The need for privacy to accommodate these activities requires adequate ventilation inside the TeSS. This study considers whether temperature, carbon dioxide, and humidity within the TeSS remain within crew comfort and safety levels for various expected operating scenarios. Evaluation of these scenarios required the use and integration of various simulation codes. An approach was adapted for this study, whereby results from a particular code were integrated with other codes when necessary. Computational Fluid Dynamics (CFD) methods were used to evaluate the flow field inside the TeSS, from which local gradients for temperature, velocity, and species concentration such as CO (sub 2) could be determined. A model of the TeSS, containing a human, as well as equipment such as a laptop computer, was developed in FLUENT, a finite-volume code. Other factors, such as detailed analysis of the heat transfer through the structure, radiation, and air circulation from the TeSS to the US Laboratory Aisle, where the TeSS is housed, were considered in the model. A complementary model was developed in G189A, a code which has been used by NASA/JSC for environmental control systems analyses since the Apollo program. Boundary conditions were exchanged between the FLUENT and G189A TeSS models. G189A provides human respiration rates to the FLUENT model, while the FLUENT model provides local convective heat transfer coefficients to G189A model. An additional benefit from using an approach with both a systems simulation and CFD model, is the capability to verify the results of each model by comparison to the results of the other model. The G189A and FLUENT models were used to evaluate various ventilation designs for the TeSS over a range of operating conditions with varying crew metabolic load, equipment operating modes, ventilation flow rates, and with the TeSS doors open and closed. Results from the study were instrumental in the optimization of a design for the TeSS ventilation hardware. A special case was considered where failure of the TeSS ventilation system occurred. In this case, a study was conducted in order to determine the time required for the CO (sub 2) concentration inside the TeSS to increase to ISS limit values under transient conditions. A lumped-capacitance code, SINDA-FLUINT was used in this case to provide accurate predictions of the human reaction to the TeSS cabin conditions including core and skin temperatures and body heat storage. A simple two-dimensional CFD model of a crewmember inside the TeSS was developed in FLUENT in order to determine the volume envelope of the respired air from the human, which maintained a minimum velocity profile. This volume was then used in the SINDA-FLUINT model to facilitate the calculations of CO (sub 2) concentrations, dry bulb temperatures and humidity levels inside the TeSS.

Keener, John F.↗
NASA NTRS2017

Mass and Reliability Source (MaRS) Database

The Mass and Reliability Source (MaRS) Database consolidates components mass and reliability data for all Oribital Replacement Units (ORU) on the International Space Station (ISS) into a single database. It was created to help engineers develop a parametric model that relates hardware mass and reliability. MaRS supplies relevant failure data at the lowest possible component level while providing support for risk, reliability, and logistics analysis. Random-failure data is usually linked to the ORU assembly. MaRS uses this data to identify and display the lowest possible component failure level. As seen in Figure 1, the failure point is identified to the lowest level: Component 2.1. This is useful for efficient planning of spare supplies, supporting long duration crewed missions, allowing quicker trade studies, and streamlining diagnostic processes. MaRS is composed of information from various databases: MADS (operating hours), VMDB (indentured part lists), and ISS PART (failure data). This information is organized in Microsoft Excel and accessed through a program made in Microsoft Access (Figure 2). The focus of the Fall 2017 internship tour was to identify the components that were the root cause of failure from the given random-failure data, develop a taxonomy for the database, and attach material headings to the component list. Secondary objectives included verifying the integrity of the data in MaRS, eliminating any part discrepancies, and generating documentation for future reference. Due to the nature of the random-failure data, data mining had to be done manually without the assistance of an automated program to ensure positive identification.

Valdenegro, Wladimir↗
NASA NTRS2006

Fracture - An Unforgiving Failure Mode

During the 2005 Conference for the Advancement for Space Safety, after a typical presentation of safety tools, a Russian in the audience simply asked, "How does that affect the hardware?" Having participated in several International System Safety Conferences, I recalled that most attention is dedicated to safety tools and little, if any, to hardware. The intent of this paper on the hazard of fracture and failure modes associated with fracture is my attempt to draw attention to the grass roots of system safety - improving hardware robustness and resilience.

Goodin, James Ronald↗
NASA NTRS2006

NASA Taxonomies for Searching Problem Reports and FMEAs

Many types of hazard and risk analyses are used during the life cycle of complex systems, including Failure Modes and Effects Analysis (FMEA), Hazard Analysis, Fault Tree and Event Tree Analysis, Probabilistic Risk Assessment, Reliability Analysis and analysis of Problem Reporting and Corrective Action (PRACA) databases. The success of these methods depends on the availability of input data and the analysts knowledge. Standard nomenclature can increase the reusability of hazard, risk and problem data. When nomenclature in the source texts is not standard, taxonomies with mapping words (sets of rough synonyms) can be combined with semantic search to identify items and tag them with metadata based on a rich standard nomenclature. Semantic search uses word meanings in the context of parsed phrases to find matches. The NASA taxonomies provide the word meanings. Spacecraft taxonomies and ontologies (generalization hierarchies with attributes and relationships, based on terms meanings) are being developed for types of subsystems, functions, entities, hazards and failures. The ontologies are broad and general, covering hardware, software and human systems. Semantic search of Space Station texts was used to validate and extend the taxonomies. The taxonomies have also been used to extract system connectivity (interaction) models and functions from requirements text. Now the Reconciler semantic search tool and the taxonomies are being applied to improve search in the Space Shuttle PRACA database, to discover recurring patterns of failure. Usual methods of string search and keyword search fall short because the entries are terse and have numerous shortcuts (irregular abbreviations, nonstandard acronyms, cryptic codes) and modifier words cannot be used in sentence context to refine the search. The limited and fixed FMEA categories associated with the entries do not make the fine distinctions needed in the search. The approach assigns PRACA report titles to problem classes in the taxonomy. Each ontology class includes mapping words - near-synonyms naming different manifestations of that problem class. The mapping words for Problems, Entities and Functions are converted to a canonical form plus any of a small set of modifier words (e.g. non-uniformity NOT + UNIFORM.) The report titles are parsed as sentences if possible, or treated as a flat sequence of word tokens if parsing fails. When canonical forms in the title match mapping words, the PRACA entry is associated with the corresponding Problem, Entity or Function in the ontology. The user can search for types of failures associated with types of equipment, clustering by type of problem (e.g., all bearings found with problems of being uneven: rough, irregular, gritty ). The results could also be used for tagging PRACA report entries with rich metadata. This approach could also be applied to searching and tagging failure modes, failure effects and mitigations in FMEAs. In the pilot work, parsing 52K+ truncated titles (the test cases that were available), has resulted in identification of both a type of equipment and type of problem in about 75% of the cases. The results are displayed in a manner analogous to Google search results. The effort has also led to the enrichment of the taxonomy, adding some new categories and many new mapping words. Further work would make enhancements that have been identified for improving the clustering and further reducing the false alarm rate. (In searching for recurring problems, good clustering is more important than reducing false alarms). Searching complete PRACA reports should lead to immediate improvement.

Malin, Jane T.↗
NASA NTRS1982

The P-POD Project

The programmable pilot oriented display (P-POD), a multiprocessor based flight information processing and display unit, is discussed. Communication protocols between the three Z-80 processors inside P-POD are reviewed. The interface between the video processor, P2, and the main processor, P1, was tested. Hardware and software were revised. Data flow between P1 and P2 is illustrated. While running diagnostic routines to exercise the P1/P2 interface at maximum speed an intermittent failure was observed. A check of possible noise sources or race conditions in the hardware did not reveal the source of this failure. Possible software timing problems were also fully investigated. To eliminate the effects of this type of failure a performance monitor routine was used to detect these occasional failures and correct them. The data transmission cycle between P1/P2 is either allowed to continue normal operation or is re-initialized and restarted when an error is detected.

Littlefield, J. A.↗
NASA NTRS2019

Model Based Engineering for Software Assurance

NASA's successful development of next generation space vehicles, habitats, and robotic systems will require reliable hardware and software systems. The aim of this initiative is to develop modeling methodology and tools to support Model-Based Systems Engineering (MBSE) for software assurance and reliability analysis. This effort expands the Unified Modeling Language (UML) software design models to include fault data for the extraction of Failure Modes and Effects Criticality Analysis (FMECA) and Fault Tree Analysis (FTA) for software. We explored different modeling approaches to integrate the UML software design models with the Systems Modeling Language (SysML) system models to generate an integrated model and reliability tools that take into account software and hardware interfaces.The benefits of this concept directly affect the safety community with quick turnarounds to produce software assurance and reliability analysis artifacts and the ability to visualize failure effects, both hardware and software. The result is enhanced system design integrity and early identification of system risks. This initiative will enable software assurance activities early in the system design lifecycle, facilitating the discovery of design weaknesses and enhancing the capability to produce safe, hazard-free systems

Wang, Lui↗
NASA NTRSDate not supplied

In-Space Inspection Needs: Opportunities for advanced NDE tools such as x-ray CT for additively manufactured parts, in-situ resource utilization, geological applications, and more

It is now 50 years since the first human presence on the surface of the Moon and as we strive to return with women and men in the next few years, we embrace new technical challenges, goals, and innovative solutions to address 21st century objectives. These new ambitions carry fresh challenges and risks, with the field of NDE playing an increasingly more relevant role towards meeting these essential goals. In recent years, more advanced NDE tools have triggered a rapid expansion of applications for the space industry. In particular, x-ray Computed Tomography (CT) has proven to be a trusted and powerful asset for spaceflight hardware inspection, as well as applied geotechnical analysis for natural materials (e.g., rocks, soils) for NASA and across industry. However, such methods have yet to be extended to “deep space” applications such as those that are now part of the US National Space Policy Directive (SPD-1) and the accelerated push to return humans to the Moon (i.e., Artemis). For this reason, advancing these powerful Earth-based laboratory methods via new technologies, integrated computational solutions, and creative engineering approaches is directly aligned with national space policies, as well as with multiple NASA Strategic Plan priorities. The use of x-ray CT at scales as fine as a few microns or smaller can identify spacecraft part failure modes relevant to quality assurance for flight hardware and AM parts such as those recently developed for ISS. This technology could also identify valuable metallic phases within geological materials (i.e., rocks or drill cores), enabling resource-relevant triage of samples for In-Situ Resource Utilization (ISRU) and high science value sample return to Earth laboratories. There is also significant application for 3D imaging tools for medical use such as inspecting protective gear as well as bone density degradation studies which are critical in establishing a sustained presence in space. Timing for development of these tools for space use is advantageous as we prepare for new opportunities in the next few years and recognize recent commercial technology advancements which make it feasible. Moreover, as NASA strives to take full advantage of developments in AM technologies, including In-Space Manufacturing (ISM), it is widely recognized that NDE tools such as CT will play an essential role in acceptance of these parts for widespread use. New in-space 3D inspection tools with complimentary technology such as AI-based automated feature recognition (accelerated by machine learning), rapid compositional analysis, and advanced sample manipulation, would be a game-changing step toward a new class of crew-based laboratory sensors once human outposts on the Moon are established.

In-Space Non-Destructive Evaluation↗
NASA NTRS2000

Reliability and Maintainability (RAM) Training

The theme of this manual is failure physics-the study of how products, hardware, software, and systems fail and what can be done about it. The intent is to impart useful information, to extend the limits of production capability, and to assist in achieving low-cost reliable products. In a broader sense the manual should do more. It should underscore the urgent need CI for mature attitudes toward reliability. Five of the chapters were originally presented as a classroom course to over 1000 Martin Marietta engineers and technicians. Another four chapters and three appendixes have been added, We begin with a view of reliability from the years 1940 to 2000. Chapter 2 starts the training material with a review of mathematics and a description of what elements contribute to product failures. The remaining chapters elucidate basic reliability theory and the disciplines that allow us to control and eliminate failures.

Lalli, Vincent R.↗
NASA NTRS1994

Hardware and software reliability estimation using simulations

The simulation technique is used to explore the validation of both hardware and software. It was concluded that simulation is a viable means for validating both hardware and software and associating a reliability number with each. This is useful in determining the overall probability of system failure of an embedded processor unit, and improving both the code and the hardware where necessary to meet reliability requirements. The methodologies were proved using some simple programs, and simple hardware models.

Swern, Frederic L.↗
NASA NTRS1988

Independent Orbiter Assessment (IOA): Assessment of the orbital maneuvering subsystem, volume 2

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the Orbital Maneuvering System (OMS) hardware and electrical power distribution and control (EPD and C), generating draft failure modes and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The IOA results were then compared to the proposed Post 51-L NASA FMEA/CIL baseline. This report documents the results of that comparison for the Orbiter OMS hardware and EPD and C systems. Volume 2 continues the presentation of IOA worksheets and contains the critical items list and the NASA FMEA to IOA worksheet cross reference and recommendations.

Haufler, W. A.↗
NASA NTRS1988

Independent Orbiter Assessment (IOA): Assessment of the reaction control system, volume 2

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the aft and forward Reaction Control System (RCS) hardware and Electrical Power Distribution and Control (EPD and C), generating draft failure modes and potential critical items. The IOA results were then compared to the proposed Post 51-L NASA FMEA/CIL baseline. This report documents the results of that comparison for the Orbiter RCS hardware and EPD and C systems. Volume 2 continues the presentation of IOA worksheets.

Prust, Chet D.↗
NASA NTRS1988

Independent Orbiter Assessment (IOA): Assessment of the reaction control system, volume 3

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the aft and forward Reaction Control System (RCS) hardware and Electrical Power Distribution and Control (EPD and C), generating draft failure modes and potential critical items. The IOA results were then compared to the proposed Post 51-L NASA FMEA/CIL baseline. This report documents the results of that comparison for the Orbiter RCS hardware and EPD and C systems. Volume 3 continues the presentation of IOA worksheets.

Prust, Chet D.↗
NASA NTRS1988

Independent Orbiter Assessment (IOA): Assessment of the reaction control system, volume 4

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the aft and forward Reaction Control System (RCS) hardware and Electrical Power Distribution and Control (EPD and C), generating draft failure modes and potential critical items. The IOA results were then compared to the proposed Post 51-L NASA FMEA/CIL baseline. This report documents the results of that comparison for the Orbiter RCS hardware and EPD and C systems. Volume 4 continues the presentation of IOA worksheets and contains the potential critical items list.

Prust, Chet D.↗
NASA NTRS1988

Independent Orbiter Assessment (IOA): Assessment of the reaction control system, volume 5

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA effort first completed an analysis of the aft and forward Reaction Control System (RCS) hardware and Electrical Power Distribution and Control (EPD and C), generating draft failure modes and potential critical items. The IOA results were then compared to the proposed Post 51-L NASA FMEA/CIL baseline. This report documents the results of that comparison for the Orbiter RCS hardware and EPD and C systems. Volume 5 contains detailed analysis and superseded analysis worksheets and the NASA FMEA to IOA worksheet cross reference and recommendations.

Prust, Chet D.↗