Search NASA⌕ Search

SEARCH · Search NASA

Results for “fail operational”

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 253 records · Page 14

Impact of an Exhaust Throat on Semi-Idealized Rotating Detonation Engine Performance

A computational fluid dynamic (CFD) model of a rotating detonation engine (RDE) is used to examine the impact of an exhaust throat (i.e., a constriction) on performance. The model simulates an RDE which is premixed, adiabatic, inviscid, and which contains an inlet valve that prevents backflow from the high pressure region directly behind the rotating detonation. Performance is assessed in terms of ideal net specific impulse which is computed on the assumption of lossless expansion of the working fluid to the ambient pressure through a notional diverging nozzle section downstream of the throat. Such a semi-idealized analysis, while not real-world, allows the effect of the throat to be examined in isolation from, rather than coupled to (as it actually is) various loss mechanisms. For the single Mach 1.4 flight condition considered, it is found that the addition of a throat can yield a 9.4 percent increase in specific impulse. However, it is also found that when the exit throat restriction gets too small, an unstable type of operation ensues which eventually leads to the detonation failing. This behavior is found to be somewhat mitigated by the addition of an RDE inlet restriction across which there is an aerodynamic loss. Remarkably, this loss is overcome by the benefits of the further exhaust restrictions allowed. The end result is a configuration with a 10.3 percent improvement in ideal net specific thrust.

combustion↗

Impact of an Exhaust Throat on Semi-Idealized Rotating Detonation Engine Performance

A computational fluid dynamic (CFD) model of a rotating detonation engine (RDE) is used to examine the impact of an exhaust throat (i.e. a constriction) on performance. The model simulates an RDE which is premixed, adiabatic, inviscid, and which contains an inlet valve that prevents backflow from the high pressure region directly behind the rotating detonation. Performance is assessed in terms of ideal net specific impulse which is computed on the assumption of lossless expansion of the working fluid to the ambient pressure through a notional diverging nozzle section downstream of the throat. Such a semi-idealized analysis, while not real-world, allows the effect of the throat to be examined in isolation from, rather than coupled to (as it actually is) various loss mechanisms. For the single Mach 1.4 flight condition considered, it is found that the addition of a throat can yield a 9.4 percent increase in specific impulse. However, it is also found that when the exit throat restriction gets too small, an unstable type of operation ensues which eventually leads to the detonation failing. This behavior is found to be somewhat mitigated by the addition of an RDE inlet restriction across which there is an aerodynamic loss. Remarkably, this loss is overcome by the benefits of the further exhaust restrictions allowed. The end result is a configuration with a 10.3 percent improvement in ideal net specific thrust.

propulsion↗

CloudSat Anomaly Recovery and Operational Lessons Learned

In April 2011, NASA's pioneering cloud profiling radar satellite, CloudSat, experienced a battery anomaly that placed it into emergency mode and rendered it operations incapable. All initial attempts to recover the spacecraft failed as the resultant power limitations could not support even the lowest power mode. Originally part of a six-satellite constellation known as the "A-Train", CloudSat was unable to stay within its assigned control box, posing a threat to other A-Train satellites. CloudSat needed to exit the constellation, but with the tenuous power profile, conducting maneuvers was very risky. The team was able to execute a complex sequence of operations which recovered control, conducted an orbit lower maneuver, and returned the satellite to safe mode, within one 65 minute sunlit period. During the course of the anomaly recovery, the team developed several bold, innovative operational strategies. Details of the investigation into the root-cause and the multiple approaches to revive CloudSat are examined. Satellite communication and commanding during the anomaly are presented. A radical new system of "Daylight Only Operations" (DO-OP) was developed, which cycles the payload and subsystem components off in tune with earth eclipse entry and exit in order to maintain positive power and thermal profiles. The scientific methodology and operational results behind the graduated testing and ramp-up to DO-OP are analyzed. In November 2011, the CloudSat team successfully restored the vehicle to consistent operational collection of cloud radar data during sunlit portions of the orbit. Lessons learned throughout the six-month return-to-operations recovery effort are discussed and offered for application to other R&D satellites, in the context of on-orbit anomaly resolution efforts.

cloud profiling radar satellite↗

Use of the quartz crystal microbalance to determine the monomeric friction coefficient of polyimides

When a thin film of polymer is coated on to a quartz crystal microbalance (QCM), the QCM can be used to detect the rate of increase in weight of the polymer film as the volatile penetrant diffuses into the polymer. From this rate information the diffusion coefficient of the penetrant into the polymer can be computed. Calculations requiring this diffusion coefficient lead to values which approximate the monomeric friction coefficient of the polymer. This project has been concerned with the trial of crystal oscillating circuits suitable for driving polymer coated crystals in an atmosphere of penetrant. For these studies done at room temperature, natural rubber was used as an easily applied polymer that is readily penetrated by toluene vapors, qualities anticipated with polyimides when they are tested at T(g) in the presence of toluene. Three quartz crystal oscillator circuits were tested. The simplest circuit used +/- 5 volt dc and had a transistor to transistor logic (TTL) inverter chip that provides a 180 deg phase shift via a feed back loop. This oscillator circuit was stable but would not drive the crystal when the crystal was coated with polymer and subjected to toluene vapors. Removal of a variable resistor from this circuit increased stability but did not otherwise increase performance. Another driver circuit tested contained a two stage differential input, differential output, wide band video amplifier and also contain a feed back loop. The circuit voltage could not be varied and operated at +/- 5 volts dc; this circuit was also stable but failed to oscillate the polymer coated crystal in an atmosphere saturated with toluene vapors. The third oscillator circuit was of similar construction and relied on the same video amplifier but allowed operation with variable voltage. This circuit would drive the crystal when the crystal was submerged in liquid toluene and when the crystal was coated with polymer and immersed in toluene vapors. The frequency readings obtained when using this oscillating circuit are highly variable. This circuit requires further modification to stabilize frequency readings before its use in studies to determine the diffusion coefficient of penetrant molecules into a polymer film coated on a QCM.

Bechtold, Mary M.↗

Galileo System Design for Orbital Operations

In April 1991, Galileo's X-band high gain antenna failed to deploy. An alternate approach which utilizes the spacecraft's S-band low gain antenna was conceived and is in development.

Galileo↗

Certification of tactics and strategies in aviation

The paper suggests that the 'tactics and strategies' notion is a highly suitable paradigm to describe the cognitive involvement of human operators in advanced aviation systems (far more suitable than classical functional analysis), and that the workload and situational awareness of operators are intimately associated with the planning and execution of their tactics and strategies. If system designers have muddled views about the collective tactics and strategies to be used during operation, they will produce sub-optimum designs. If operators use unproven and/or inappropriate tactics and strategies, the system may fail. The author wants to make a point that, beyond certification of people or system designs, there may be a need to go into more detail and examine (certify?) the set of tactics and strategies (i.e., the Operational Concept) which makes the people and systems perform as expected. The collective tactics and strategies determine the information flows and situational awareness which exists in organizations and composite human-machine systems. The available infrastructure and equipment (automation) enable these information flows and situational awareness, but are at the same time the constraining factor. Frequently, the tactics and strategies are driven by technology, whereas we would rather like to see a system designed to support an optimized Operational Concept, i.e., to support a sufficiently coherent, cooperative and modular set of anticipation and planning mechanisms. Again, in line with the view of MacLeod and Taylor (1993), this technology driven situation may be caused by the system designer's and operator job designer's over-emphasis on functional analysis (a mechanistic engineering concept), at the expense of a subject which does not seem to be well understood today: the role of the (human cognitive and/or automated) tactics and strategies which are embedded in composite human-machine systems. Research would be needed to arrive at a generally accepted 'planning theory' which can elevate the analysis, description and design of tactics and strategies from today's cottage industry methods to an engineering discipline. The available infrastructure and equipment (automation) enable these information flows and situational awareness, but are at the same time the constraining factor. Frequently, the tactics and strategies are driven by technology, whereas we would rather like to see a system designed to support an optimized Operational Concept, i.e., to support a sufficiently coherent, cooperative and modular set of anticipation and planning mechanisms. Again, in line with the view of MacLeod and Taylor (1993), this technology driven situation may be caused by the system designer's and operator job designer's over-emphasis on functional analysis (a mechanistic engineering concept), at the expense of a subject which does not seem to be well understood today: the role of the (human cognitive and/or automated) tactics and strategies which are embedded in composite human-machine systems. Research would be needed to arrive at a generally accepted 'planning theory' which can evaluate the analysis, description and design of tactics and strategies from today's cottage industry methods to an engineering discipline.

Koelman, Hartmut↗

Human factors in aviation operations: The hearback problem

This report covers a study of ASRS reports wherein ATC controllers failed to monitor adequately (hearback) incorrect readbacks of ATC clearances. A total of 417 reports received over a period of 29 months from April 1981 through July 1983 comprised the study data set. Factors examined were: the reasons for a flight crew's getting clearances incorrectly, the operating factors that caused controllers to mishear or not hear the correct readbacks, and consequences of the various types of hearback misses. The principle conclusion of the study takes the form of a precaution to flight crews that a controller's not challenging a readback does not necessariliy mean the readback is correct and that flight crews must explicitly question any doubtful or unusual aspects of clearances rather than depending on controllers to detect readback errors.

Monan, William P.↗

Development of Human System Integration at NASA

Human Systems Integration seeks to design systems around the capabilities and limitations of the humans which use and interact with the system, ensuring greater efficiency of use, reduced error rates, and less rework in the design, manufacturing and operational deployment of hardware and software. One of the primary goals of HSI is to get the human factors practitioner involved early in the design process. In doing so, the aim is to reduce future budget costs and resources in redesign and training. By the preliminary design phase of a project nearly 80% of the total cost of the project is locked in. Potential design changes recommended by evaluations past this point will have little effect due to lack of funding or a huge cost in terms of resources to make changes. Three key concepts define an effective HSI program. First, systems are comprised of hardware, software, and the human, all of which operate within an environment. Too often, engineers and developers fail to consider the human capacity or requirements as part of the system. This leads to poor task allocation within the system. To promote ideal task allocation, it is critical that the human element be considered early in system development. Poor design, or designs that do not adequately consider the human component, could negatively affect physical or mental performance, as well as, social behavior. Second, successful HSI depends upon integration and collaboration of all the domains that represent acquisition efforts. Too often, these domains exist as independent disciplines due to the location of expertise within the service structure. Proper implementation of HSI through participation would help to integrate these domains and disciplines to leverage and apply their interdependencies to attain an optimal design. Via this process domain interests can be integrated to perform effective HSI through trade-offs and collaboration. This provides a common basis upon which to make knowledgeable decisions. Finally, HSI must be considered early in the requirements development phase of system design and acquisition. This will provide the best opportunity to maximize return on investment (ROI) and system performance. HSI requirements must be developed in conjunction with capability ]based requirements generation through functional. HSI requirements will drive HSI metrics and embed HSI issues within the system design. After a system is designed, implementation of HSI oversights can be very expensive. An HSI program should be included as an integral part of a total system approach to vehicle and habitat development. This would include, but not limited to, workstation design, D&C development, volumetric analysis, training, operations, and human -robotic interaction. HSI is a necessary process for Human Space Flight programs to meet the Agency Human ]System standards and thus mitigate human risks to acceptable levels. NASA has been involved in HSI planning, procedures development, process, and implementation for many years, and has been building several internal and publicly accessible products to facilitate HSI fs inclusion in the NASA Systems Engineering Lifecycle. Some of these products include: NASA STD 3001 Volumes 1 and 2, Human Integration Design Handbook, NASA HSI Implementation Plan, NASA HSI Implementation Plan Templates, NASA HSI Implementation Handbook, and a 2 ]hour short course on HSI delivered as part of the NASA Space and Life Sciences Directorate Academy. These products have been created leveraging industry best practices and lessons learned from other Federal Government agencies.

Whitmore, Mihriban↗

Recommended techniques for effective maintainability. A continuous improvement initiative of the NASA Reliability and Maintainability Steering Committee

This manual presents a series of recommended techniques that can increase overall operational effectiveness of both flight and ground based NASA systems. It provides a set of tools that minimizes risk associated with: (1) restoring failed functions (both ground and flight based); (2) conducting complex and highly visible maintenance operations; and (3) sustaining a technical capability to support the NASA mission using aging equipment or facilities. It considers (1) program management - key elements of an effective maintainability effort; (2) design and development - techniques that have benefited previous programs; (3) analysis and test - quantitative and qualitative analysis processes and testing techniques; and (4) operations and operational design techniques that address NASA field experience. This document is a valuable resource for continuous improvement ideas in executing the systems development process in accordance with the NASA 'better, faster, smaller, and cheaper' goal without compromising safety.

Source record↗

Remotely Accessible Testbed for Software Defined Radio Development

Previous development testbeds have assumed that the developer was physically present in front of the hardware being used. No provision for remote operation of basic functions (power on/off or reset) was made, because the developer/operator was sitting in front of the hardware, and could just push the button manually. In this innovation, a completely remotely accessible testbed has been created, with all diagnostic equipment and tools set up for remote access, and using standardized interfaces so that failed equipment can be quickly replaced. In this testbed, over 95% of the operating hours were used for testing without the developer being physically present. The testbed includes a pair of personal computers, one running Linux and one running Windows. A variety of peripherals is connected via Ethernet and USB (universal serial bus) interfaces. A private internal Ethernet is used to connect to test instruments and other devices, so that the sole connection to the outside world is via the two PCs. An important design consideration was that all of the instruments and interfaces used stable, long-lived industry standards, such as Ethernet, USB, and GPIB (general purpose interface bus). There are no plug-in cards for the two PCs, so there are no problems with finding replacement computers with matching interfaces, device drivers, and installation. The only thing unique to the two PCs is the locally developed software, which is not specific to computer or operating system version. If a device (including one of the computers) were to fail or become unavailable (e.g., a test instrument needed to be recalibrated), replacing it is a straightforward process with a standard, off-the-shelf device.

Lux, James P.↗

Status of the STIS Instrument After Repair During Sm4

The Space Telescope Imaging Spectrograph (STIS) was installed in the Hubble Space Telescope (HST) in February of 1997, and operated until August of 2004, when an electrical malfunction in a power supply forced cessation of operations. On May 17,2009, during the fourth EVA of SM4, astronauts Michael Good and Mike Massimino undertook an eight-hour spacewalk, during which they replaced the STIS LVPS-2 circuit board containing the failed component, successfully repairing STIS. We will review the scientific capabilities and operational status of STIS after this repair. In most respects, STIS after the 2009 repair operates in much the same way as it did prior to the 2004 failure. Most changes in performance are close to what had been expected. The degradation of the STIS CCD due to radiation damage and the modest changes in optical throughput are consistent with extrapolation of previously-observed trends. Internal and external alignments of the instrument are also similar to what they were in 2004. The biggest surprise is that the dark current for the NUV MAMA detector is several times larger than had been expected and is only slowly decreasing towards its expected range. We discuss how these changes will affect science with STIS now and in the future.

Proffitt, Charles R.↗

Modeling distributed energy resource aggregations in security constrained unit commitment and economic dispatch

The Federal Energy Regulatory Commission (FERC) recently issued Order 2222, which requires all wholesale electricity markets in the US to allow distributed energy resources (DERs) to participate in the market as aggregated resources. These DER aggregations may be composed of many individual resources that are offered and dispatched by the market as a single entity. We present here a model of a distributed energy resource aggregator (DERA) that is scheduled by a market operator’s security constrained unit commitment (SCUC) and security constrained economic dispatch (SCED). The DERA model includes constraints for battery energy storage systems (BESSs), demand response resources (DRRs), and a simple distributed energy resource (DER). This paper describes a model for each resource type and presents two methods for the DERA to generate market offer curves: a profit-maximizing optimization to compute cost curves and a direct cost algorithm to determine dispatch costs for each resource and combine into cost curves. Once all participating DERAs are scheduled in SCUC/SCED, the model is then modified to dispatch individual DERs to maximize profit or minimize schedule deviation of the DERAs. A simulation of a representative day illustrates the DERA offers, the scheduled generation, and the DERA dispatch. Findings show the potential for unavoidable schedule deviations due to internal DER constraints and due to economic incentives to deviate from the SCUC/SCED schedules. This highlights the importance of DERA offer construction on market efficiency and system reliability. Novel aspects of our approach include: (1) We consider the asymmetry of price incentives impacting DERAs from the wholesale market compared to those impacting consumers from the retail market, as imposed by current regulations and laws. (2) We model aggregate consumer response through statistically parameterizable utility functions rather than a potentially impractical approach of modeling each individual consumer. (3) We show how to use the DERA operational dispatch model to create offers into the wholesale electricity market. (4) We show how DERAs may fail to meet their scheduled dispatch because the market offer format may not permit them to fully express their operational features such as intertemporal costs and constraints to the market.

aggregations↗

Addressing Challenges to the Design & Test of Operational Lighting Environments for the International Space Station

In our day to day lives, the availability of light, with which to see our environment, is often taken for granted. The designers of land based lighting systems use sunlight and artificial light as their toolset. The availability of power, quantity of light sources, and variety of design options are often unlimited. The accessibility of most land based lighting systems makes it easy for the architect and engineer to verify and validate their design ideas. Failures with an implementation, while sometimes costly, can easily be addressed by renovation. Consider now, an architectural facility orbiting in space, 260 miles above the surface of the earth. This human rated architectural facility, the International Space Station (ISS) must maintain operations every day, including life support and appropriate human comforts without fail. The facility must also handle logistics of regular shipments of cargo, including new passengers. The ISS requires accommodations necessary for human control of machine systems. Additionally, the ISS is a research facility and supports investigations performed inside and outside its livable volume. Finally, the facility must support remote operations and observations by ground controllers. All of these architectural needs require a functional, safe, and even an aesthetic lighting environment. At Johnson Space Center, our Habitability and Human Factors team assists our diverse customers with their lighting environment challenges, via physical test and computer based analysis. Because of the complexity of ISS operational environment, our team has learned and developed processes that help ISS operate safely. Because of the dynamic exterior lighting environment, uses computational modeling to predict the lighting environment. The ISS' orbit exposes it to a sunrise every 90 minutes, causing work surfaces to quickly change from direct sunlight to earthshine to total darkness. Proper planning of vehicle approaches, robotics operations, and crewed Extra Vehicular Activities are mandatory to ensure safety to the crew and all others involved. Innovation in testing techniques is important as well. The advent of Solid State Lighting technology and the lack of stable national and international standards for its implementation pose new challenges on how to design, test and verify individual light fixtures and the environment that uses them. The ISS will soon be replacing its internal fluorescent lighting system to a solid state LED system. The Solid State Lighting Assembly will be used not only for general lighting, but also as a medical countermeasure to control the circadian rhythm of the crew. The new light source has performance criteria very specific to its spectral fingerprint, creating new challenges that were originally not as significant during the original design of the ISS. This presentation will showcase findings and toolsets our team is using to assist in the planning of tasks, and design of operational lighting environments on the International Space Station.

Clark, Toni A.↗

Situation Management in the Link Monitor and Control Operator Assistant (LMCOA)

This paper describes a knowledge-based system called the Situation Manager that was developed for the Link Monitor and Control Operator Assistant (LMCOA) at the Jet Propulsion Laboratory. This system was developed in response to a number of deficiencies that were identified in an earlier version of the LMCOA: (1) the need to close the control loop between sending a directive and knowing when its execution is complete (versus just closing the communications loop), (2) the need to recognize an anomaly and alert the operator when a directive is rejected or a link device fails, and (3) the need to suggest ways to work around an anomaly, provided that it is recognizable. In response to these needs, the Situation Manager has been designed to provide the LMCOA with three basic capabilities: situation assessment, anomaly diagnosis, and recovery from commonly

Monitor↗

Smart Planning for Radioactive Source Transport Advanced Tools for Increased Safety and Efficiency

End-of-life (EOL) management of high-activity radioactive sources is made uniquely challenging by the inherent risks associated with storage and transportation of these sources, the complex logistics involved, and the strict requirements for regulatory compliance. Traditional methods lack comprehensive tools for accurate site assessments and precision planning for the transportation of radioactive sources. They also frequently fail to provide the adaptability required to consider diverse operational environments, resulting in inefficiencies and potential safety concerns. This paper introduces a novel software solution developed to address these issues by integrating advanced technologies such as light detection and ranging (LiDAR)-based 3D environment modeling, smart dynamic route planning, and customizable measurement functionalities. This software enables detailed terrain visualizations, facilitating thorough environmental assessments and enabling users to virtually navigate, analyze, and plan site-specific operations. Among the key features are a user-centric interface for virtual navigation, precise site measurement tools for site evaluations, interactive visualizations that highlight potential operational hazards, dynamic route planning capabilities, and real-time collision detection to promote safe workflows. By demonstrating the effectiveness of this tool through real-world application, the present work underscores the tool’s potential to revolutionize radioactive source EOL management by improving operational efficiencies, minimizing risk, and advancing the state of practice to achieve suitable and secure radioactive material handling.

99 - GENERAL AND MISCELLANEOUS↗

Design of thermal protection system for 8 foot HTST combustor

The combustor in the 8-foot high temperature structures tunnel at the NASA-Langley Research Center has encountered cracking over a period of 50-250 tunnel tests within a limited range of the required operating envelope. A program was conducted which analyzed the failed combustor liner hardware and determined that the mechanism of failure was vibratory fatigue. A vibration damper system using wave springs located axially between the liner T-bar and the liner support was designed as an intermediate solution to extend the life of the current two-pass regenerative air-cooled liner. The effects of liner wall thickness, cooling air passage height, stiffener ring geometry, reflective coatings, and liner material selection were investigated for these designs. Preliminary layout design arrangements including the external water-cooling system requirements, weight estimates, installation requirements and preliminary estimates of manufacturing costs were prepared for the most promissing configurations. A state-of-the-art review of thermal barrier coatings and an evaluation of reflective coatings for the gasside surface of air-cooled liners are included.

Moskowitz, S.↗

Space Telescope design for maintenance

The Space Telescope is the first free-flying spacecraft designed to be serviced and repaired by EVA astronauts performing in-orbit maintenance tasks necessary to replace failed or worn-out components. The Telescope's operational profile anticipates in-orbit maintenance approximately two and one half years after initial launch, spacecraft return to ground after five years, and relaunch about one year later. Component design for in-orbit maintenance is being verified by 1-G and neutral buoyancy simulation techniques. Skylab experience led to the implementation of this approach which has significant economic benefits compared to 'one-time-use' space hardware.

Field, E. L.↗

Simultaneous real-time data collection methods

This paper describes the development of electronic test equipment which executes, supervises, and reports on various tests. This validation process uses computers to analyze test results and report conclusions. The test equipment consists of an electronics component and the data collection and reporting unit. The PC software, display screens, and real-time data-base are described. Pass-fail procedures and data replay are discussed. The OS2 operating system and Presentation Manager user interface system were used to create a highly interactive automated system. The system outputs are hardcopy printouts and MS DOS format files which may be used as input for other PC programs.

Klincsek, Thomas↗