Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operational Acceptability”

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 523 records · Page 29

Fully automatic guidance for rotorcraft nap-of-the-earth (NOE) flight following planned profiles

Developing a single-pilot, all-weather nap-of-the-earth (NOE) capability requires fully automatic NOE navigation and flight control. Innovative guidance and control concepts are being investigated in a fourfold research effort that will culminate in the real-time piloted simulation of promising alternatives for automatic guidance and control of rotorcraft in NOE operations, thereby providing a practical demonstration for evaluating pilot acceptance of the automated concepts.

Gorder, Peter J.↗

Space Station Freedom contamination requirements and predictions

Space Station Freedom (SSF) requirements for the induced external gaseous and particulate environment have been defined. They include the Assembly Complete (AC) and the Permanently Manned Capability (PMC) phases which were established since the original configuration was developed. Requirements for both SSF configurations are discussed. Preliminary assessments of the impacts on SSF design and operation indicate that these requirements are both realistic and acceptable to the users with attached payloads.

Ehlers, Horst K. F.↗

Assessment and design of low boom configurations for supersonic transport aircraft

A review is presented of presently utilized sonic boom prediction and minimization techniques. The three-pronged approach - acceptability studies, atmospheric propagation studies, and configuration design and operation, to the sonic boom problem as an element of the High Speed Research Program are discussed. Experimental and theoretical results of concepts designed to validate present minimization methods are given.

Darden, Christine M.↗

International Space Station alpha remote manipulator system workstation controls test report

Previous development testing for the space station remote manipulator system workstation controls determined the need for hardware controls for the emergency stop, brakes on/off, and some camera functions. This report documents the results of an evaluation to further determine control implementation requirements, requested by the Canadian Space Agency (CSA), to close outstanding review item discrepancies. This test was conducted at the Johnson Space Center's Space Station Mockup and Trainer Facility in Houston, Texas, with nine NASA astronauts and one CSA astronaut as operators. This test evaluated camera iris and focus, back-up drive, latching end effector release, and autosequence controls using several types of hardware and software implementations. Recommendations resulting from the testing included providing guarded hardware buttons to prevent accidental actuation, providing autosequence controls and back-up drive controls on a dedicated hardware control panel, and that 'latch on/latch off', or on-screen software, controls not be considered. Generally, the operators preferred hardware controls although other control implementations were acceptable. The results of this evaluation will be used along with further testing to define specific requirements for the workstation design.

Ehrenstrom, William A.↗

Development and status of data quality assurance program at NASA Langley research center: Toward national standards

As part of a continuing effort to re-engineer the wind tunnel testing process, a comprehensive data quality assurance program is being established at NASA Langley Research Center (LaRC). The ultimate goal of the program is routing provision of tunnel-to-tunnel reproducibility with total uncertainty levels acceptable for test and evaluation of civilian transports. The operational elements for reaching such levels of reproducibility are: (1) statistical control, which provides long term measurement uncertainty predictability and a base for continuous improvement, (2) measurement uncertainty prediction, which provides test designs that can meet data quality expectations with the system's predictable variation, and (3) national standards, which provide a means for resolving tunnel-to-tunnel differences. The paper presents the LaRC design for the program and discusses the process of implementation.

Hemsch, Michael J.↗

Post Galileo-Europa-Mission Satellite Tour Design

The Galileo orbiter mission as originally envisioned would orbit Jupiter eleven times, closely encountering either Europa, Ganymede, or Callisto on ten of those orbits. This nominal or prime mission began with Jupiter orbit insertion on December 7, 1995 and ended as designed ten encounters later on December 1, 1997. An extension to this nominal mission was proposed, developed and accepted in 1997 and was designed to continue orbital operations through an additional two years until December 31, 1999. This follow- on mission, labelled the Galileo Europa Mission, visits Europa eight times, Callisto four times, and ends with two visits to Io. It augments the prime mission by offering many attractive additional opportunities for science, especially remote sensing. The opportunities include increased scrutiny of Europa, a world with a possible global ocean hidden beneath the surface ice-cap, and the first high resolution images of Io (the only major satellite not encountered during the nominal tour). In 1998 a new effort was begun to investigate a possible extension to GEM. Remote sensing observations will continue to be important but moreover, valuable unique in situ fields and particles measurements will be a high priority motivation in the design and selection of any post-GEM tour. A significant design feature of a possible post-GEM tour would be the extension of the mission through the December 2000 timeframe. This would permit the possibility of simultaneous fields and particles experiments coordinated with the Cassini spacecraft as it swings by the Jupiter system for the final gravity assist enroute to Saturn.

Wilson, M. G.↗

Glenn-HT Code Validated for Complex Turbine Blade Cooling Passage

This work is motivated by the need to accurately predict heat transfer in turbomachinery. For efficient gas turbine operation, flow temperatures in the hot gas path exceed acceptable metal temperatures in many regions of the engine. So that the integrity of the parts can be maintained for an acceptable engine life, the parts must be cooled. Efficient cooling schemes require accurate heat transfer prediction to minimize regions that are overcooled and, even more importantly, to ensure adequate cooling in high-heat-flux regions.

Rigby, David L.↗

Fault-Tolerant, Multiple-Zone Temperature Control

A computer program has been written as an essential part of an electronic temperature control system for a spaceborne instrument that contains several zones. The system was developed because the temperature and the rate of change of temperature in each zone are required to be maintained to within limits that amount to degrees of precision thought to be unattainable by use of simple bimetallic thermostats. The software collects temperature readings from six platinum resistance thermometers, calculates temperature errors from the readings, and implements a proportional + integral + derivative (PID) control algorithm that adjusts heater power levels. The software accepts, via a serial port, commands to change its operational parameters. The software attempts to detect and mitigate a host of potential faults. It is robust to many kinds of faults in that it can maintain PID control in the presence of those faults.

Granger, James↗

History and Benefits of Engine Level Testing Throughout the Space Shuttle Main Engine Program

Rocket engine testing is important throughout a program s life and is essential to the overall success of the program. Space Shuttle Main Engine (SSME) testing can be divided into three phases: development, certification, and operational. Development tests are conducted on the basic design and are used to develop safe start and shutdown transients and to demonstrate mainstage operation. This phase helps form the foundation of the program, demands navigation of a very steep learning curve, and yields results that shape the final engine design. Certification testing involves multiple engine samples and more aggressive test profiles that explore the boundaries of the engine to vehicle interface requirements. The hardware being tested may have evolved slightly from that in the development phase. Operational testing is conducted with mature hardware and includes acceptance testing of flight assets, resolving anomalies that occur in flight, continuing to expand the performance envelope, and implementing design upgrades. This paper will examine these phases of testing and their importance to the SSME program. Examples of tests conducted in each phase will also be presented.

VanHooser, Katherine↗

Public Risk Assessment Program

The Public Entry Risk Assessment (PERA) program addresses risk to the public from shuttle or other spacecraft re-entry trajectories. Managing public risk to acceptable levels is a major component of safe spacecraft operation. PERA is given scenario inputs of vehicle trajectory, probability of failure along that trajectory, the resulting debris characteristics, and field size and distribution, and returns risk metrics that quantify the individual and collective risk posed by that scenario. Due to the large volume of data required to perform such a risk analysis, PERA was designed to streamline the analysis process by using innovative mathematical analysis of the risk assessment equations. Real-time analysis in the event of a shuttle contingency operation, such as damage to the Orbiter, is possible because PERA allows for a change to the probability of failure models, therefore providing a much quicker estimation of public risk. PERA also provides the ability to generate movie files showing how the entry risk changes as the entry develops. PERA was designed to streamline the computation of the enormous amounts of data needed for this type of risk assessment by using an average distribution of debris on the ground, rather than pinpointing the impact point of every piece of debris. This has reduced the amount of computational time significantly without reducing the accuracy of the results. PERA was written in MATLAB; a compiled version can run from a DOS or UNIX prompt.

Mendeck, Gavin↗

Interval Management with Spacing to Parallel Dependent Runways (IMSPIDR) Experiment and Results

An area in aviation operations that may offer an increase in efficiency is the use of continuous descent arrivals (CDA), especially during dependent parallel runway operations. However, variations in aircraft descent angle and speed can cause inaccuracies in estimated time of arrival calculations, requiring an increase in the size of the buffer between aircraft. This in turn reduces airport throughput and limits the use of CDAs during high-density operations, particularly to dependent parallel runways. The Interval Management with Spacing to Parallel Dependent Runways (IMSPiDR) concept uses a trajectory-based spacing tool onboard the aircraft to achieve by the runway an air traffic control assigned spacing interval behind the previous aircraft. This paper describes the first ever experiment and results of this concept at NASA Langley. Pilots flew CDAs to the Dallas Fort-Worth airport using airspeed calculations from the spacing tool to achieve either a Required Time of Arrival (RTA) or Interval Management (IM) spacing interval at the runway threshold. Results indicate flight crews were able to land aircraft on the runway with a mean of 2 seconds and less than 4 seconds standard deviation of the air traffic control assigned time, even in the presence of forecast wind error and large time delay. Statistically significant differences in delivery precision and number of speed changes as a function of stream position were observed, however, there was no trend to the difference and the error did not increase during the operation. Two areas the flight crew indicated as not acceptable included the additional number of speed changes required during the wind shear event, and issuing an IM clearance via data link while at low altitude. A number of refinements and future spacing algorithm capabilities were also identified.

Baxley, Brian T.↗

Automating the Generation of Heterogeneous Aviation Safety Cases

A safety case is a structured argument, supported by a body of evidence, which provides a convincing and valid justification that a system is acceptably safe for a given application in a given operating environment. This report describes the development of a fragment of a preliminary safety case for the Swift Unmanned Aircraft System. The construction of the safety case fragment consists of two parts: a manually constructed system-level case, and an automatically constructed lower-level case, generated from formal proof of safety-relevant correctness properties. We provide a detailed discussion of the safety considerations for the target system, emphasizing the heterogeneity of sources of safety-relevant information, and use a hazard analysis to derive safety requirements, including formal requirements. We evaluate the safety case using three classes of metrics for measuring degrees of coverage, automation, and understandability. We then present our preliminary conclusions and make suggestions for future work.

Denney, Ewen W.↗

PRA (Probabilistic Risk Assessments) Participation versus Validation

Probabilistic Risk Assessments (PRAs) are performed for projects or programs where the consequences of failure are highly undesirable. PRAs primarily address the level of risk those projects or programs posed during operations. PRAs are often developed after the design has been completed. Design and operational details used to develop models include approved and accepted design information regarding equipment, components, systems and failure data. This methodology basically validates the risk parameters of the project or system design. For high risk or high dollar projects, using PRA methodologies during the design process provides new opportunities to influence the design early in the project life cycle to identify, eliminate or mitigate potential risks. Identifying risk drivers before the design has been set allows the design engineers to understand the inherent risk of their current design and consider potential risk mitigation changes. This can become an iterative process where the PRA model can be used to determine if the mitigation technique is effective in reducing risk. This can result in more efficient and cost effective design changes. PRA methodology can be used to assess the risk of design alternatives and can demonstrate how major design changes or program modifications impact the overall program or project risk. PRA has been used for the last two decades to validate risk predictions and acceptability. Providing risk information which can positively influence final system and equipment design the PRA tool can also participate in design development, providing a safe and cost effective product.

DeMott, Diana↗

Stirling Convertor Controller Development at NASA Glenn Research Center

For nearly two decades, NASA Glenn Research Center (GRC) has been supporting the development of Radioisotope Power Systems (RPS). NASA desires higher conversion efficiency RPS options that are reliable and robust with long life design. Dynamic conversion, such as Stirling and Brayton, offer the potential for higher conversion efficiencies than current RPS but have yet to be demonstrated in a flight application. The RPS program sent out a solicitation to investigate options for dynamic conversion technologies. As a result of this solicitation, four dynamic power convertor (DPC) technologies were selected for design and three are proceeding to the fabrication phase of prototype dynamic convertors. One lesson learned from the Advanced Stirling Radioisotope Generator (ASRG) project is that controller development should be coordinated with the development of a dynamic convertor. As a result of this, NASA GRC has been utilizing hardware from past Stirling convertor projects including that of the ASRG to support controller development for the DPC's. NASA GRC has developed a strong knowledge base on both analog and digital Stirling dynamic power convertor controllers and will continue to expand and apply that knowledge to the DPC's. Over the past 15 years, controllers were developed at GRC, at Lockheed Martin (LM) and by the Johns Hopkins University/Applied Physics Laboratory (JHU/APL). Various generations of the controllers have been developed as lessons were learned through various component and system level tests. Some of the tests performed were fault tolerance, flight acceptance vibration, electromagnetic interference (EMI), spacecraft integration, and extended operation. The fault tolerance test characterized the controller's ability to handle various fault conditions, including high or low bus power consumptions, total open load or short circuit, and replacing a failed controller card while the backup maintains control of the Stirling convertor. The vibration test confirms the controller's ability to control an ASC during launch. The EMI test characterized the AC and DC magnetic and electric fields emitted by the single ASC and if the controller has an impact on the radiated EMI. Spacecraft integration testing in the Radioisotope Power Systems System Integration Laboratory (RSIL) provided insight into the electrical interactions between the representative RPS, its associated control schemes, and realistic electric system loads. The extended operation test allows data to be collected over a period of thousands of hours to obtain long term performance data of the system. This paper describes the history of controller development at NASA GRC, tests performed on these controllers, and lessons learned.

Dugala, Gina M.↗

Orientation Effects in Two-Phase Microgap Flow

The high power density of emerging electronic devices is driving the transition from remote cooling, which relies onconduction and spreading, to embedded cooling, which extracts dissipated heat on-site. Two-phase microgap coolersemploy the forced flow of dielectric fluids undergoing phase change in a heated channel within or between devices. Such coolers must work reliably in all orientations for a variety of applications (e.g., vehicle-based equipment), as well as in microgravity and high-g for other applications (e.g., spacecraft and aircraft). The lack of acceptable models andcorrelations for orientation- and gravity-independent operation has limited the use of two-phase coolers in suchapplications. Previous research has revealed that gravitational acceleration plays a diminishing role in establishing flow regimes and transport rates as the channel size shrinks, but there is considerable variation among the proposed microscale criteria and limited research on two-phase flows in low aspect ratio microgap channels. Reliable criteria for achieving orientation- and gravity-independent flow boiling would enable emerging systems to exploit this thermal management technique and streamline the technology development process.

orientation↗

Stirling Convertor Controller Development at NASA Glenn Research Center

For nearly two decades, NASA Glenn Research Center has been supporting the development of radioisotope power systems (RPS). NASA desires higher conversion efficiency RPS options that are reliable and robust with long-life design. Dynamic conversion, such as Stirling and Brayton, offer the potential for higher conversion efficiencies than current RPS but have yet to be demonstrated in a flight application. The RPS program sent out a solicitation to investigate options for dynamic conversion technologies. As a result of this solicitation, four dynamic power convertor (DPC) technologies were selected for design and three are proceeding to the fabrication phase of prototype dynamic convertors. One lesson learned from the Advanced Stirling Radioisotope Generator (ASRG) project is that controller development should be coordinated with the development of a dynamic convertor. As a result of this, Glenn has been utilizing hardware from past Stirling convertor projects, including that of the ASRG, to support controller development for the DPCs. Glenn has developed a strong knowledge base on both analog and digital Stirling DPC controllers and will continue to expand and apply that knowledge to the DPCs. Over the past 15 years, controllers were developed at Glenn, at Lockheed Martin (LM), and by the Johns Hopkins University Applied Physics Laboratory (APL). Various generations of the controllers have been developed as lessons were learned through various component- and system-level tests. Some of the tests performed were fault tolerance, flight acceptance vibration, electromagnetic interference (EMI), spacecraft integration, and extended operation. The fault tolerance test characterized the controller’s ability to handle various fault conditions, including high or low bus power consumption, total open load or short circuit, and replacing a failed controller card while the backup maintains control of the Stirling convertor. The vibration test confirms the controller’s ability to control an Advanced Stirling Convertor (ASC) during launch. The EMI test characterized the alternating-current (AC) and direct-current (DC) magnetic and electric fields emitted by the single ASC and if the controller has an impact on the radiated EMI. Spacecraft integration testing in the Radioisotope Power Systems (RPS), System Integration Laboratory (RSIL) provided insight into the electrical interactions between the representative RPS, its associated control schemes, and realistic electric system loads. The extended operation test allows data to be collected over a period of thousands of hours to obtain long-term performance data of the system. This paper describes the history of controller development at Glenn, tests performed on these controllers, and lessons learned.

Dugala, Gina M.↗

Benchmark Problem for Autonomous Urban Air Mobility

This paper introduces a Community Benchmark Problem (CBP) for Intelligent Contingency Management (ICM) for Urban Air Mobility (UAM) aircraft. The CBP aims to provide a common framework for measuring and comparing the progress of autonomy solutions for UAM aircraft in handling emergency situations. The paper proposes a methodology for defining and quantifying five measures of complexity that capture the challenges and requirements of ICM for UAM: Mission, Environmental, Autonomy, Decision-Making, and Mission Fault. In addition, it proposes a methodology for defining and quantifying mission risk acceptability with the same goals: Contingency Management, Mission Success, Operational, Mission Redefinition, and Environmental. We describe how to use these measures to track progress of the development of ICM capability, as well as to create scenarios and evaluate the performance of different autonomy solutions.

autonomy↗

Community Benchmark Problem for Intelligent Contingency Management

This paper introduces a Community Benchmark Problem (CBP) for Intelligent Contingency Management (ICM) for Urban Air Mobility (UAM) aircraft. The CBP aims to provide a common framework for measuring and comparing the progress of autonomy solutions for UAM aircraft in handling emergency situations. The paper proposes a methodology for defining and quantifying five measures of complexity that capture the challenges and requirements of ICM for UAM: Mission, Environmental, Autonomy, Decision-Making, and Mission Fault. In addition, it proposes a methodology for defining and quantifying mission risk acceptability with the same goals: Contingency Management, Mission Success, Operational, Mission Redefinition, and Environmental. We describe how to use these measures to track progress of the development of ICM capability, as well as to create scenarios and evaluate the performance of different autonomy solutions.

autonomy↗