Search NASA⌕ Search

SEARCH · Search NASA

Results for “design requirements”

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRS1989

Space station wardroom habitability and equipment study

Experimental designs in life-size mock-up form for the wardroom facility for the Space Station Habitability Module are explored and developed. In Phase 1, three preliminary concepts for the wardroom configuration are fabricated and evaluated. In Phase 2, the results of Phase 1 are combined with a specific range of program design requirements to provide the design criteria for the fabrication of an innovative medium-fidelity mock-up of a wardrobe configuration. The study also focuses on the design and preliminary prototyping of selected equipment items including crew exercise compartments, a meal/meeting table and a portable workstation. Design criteria and requirements are discussed and documented. Preliminary and final mock-ups and equipment prototypes are described and illustrated.

Nixon, David↗
NASA NTRS1989

Electronically Variable Pressure Regulator (EVPR)

A new programmable electronically variable pressure regulator (EVPR) concept accurately controls the local outlet or remote system pressure. It uses an integral pulse width modulated rare earth permanent magnet motor operating in response to redundant pressure transducer feedback signals. The EVPR is a simple single stage device that does not use dynamic seals or pilot valving. Conversion of partial revolution motor torque to poppet lifting force is accomplished by pure flexure action to avoid using bearings. The flexure drive (called the ROTAX) has a variable lead to minimize motor weight and power consumption. Breadboard tests were completed successfully on two critical design elements of the EVPR: the ROTAX and the motor. The ROTAX cable system was tested for 250,000 cycles without failure. The breadboard motor met the basic design requirements including the design torque and power consumption. Prototype parts were fabricated, and testing of the prototype EVPR has started. It is PC computer controlled to facilitate programming, data acquisition and analysis. A lightweight dedicated microprocessor is planned for the flightweight EVPR.

Reinicke, R. H.↗
NASA NTRS1992

Nickel-hydrogen battery design for the Transporter Energy Storage Subsystem (TESS)

Information is given in viewgraph form on nickel hydrogen battery design for the transporter energy storage subsystem (TESS). Information is given on use in the Space Station Freedom, the launch configuration, use in the Mobile Servicing Center, battery design requirements, TESS subassembley design, proof of principle testing of a 6-cell battery, possible downsizing of TESS to support the Mobile Rocket Servicer Base System (MBS) redesign, TESS output capacity, and cell testing.

Lapinski, John R.↗
NASA NTRS1992

Space Station external thermal control system design and operational overview

The driving design requirements and resulting design characteristics for a two-phase ammonia system of the Space Shuttle are reviewed with particular attention given to operational and station assembly issues related to system activation and steady-state operation. Design is described at an overall system level and an orbit replaceable unit level. It is concluded that a system flow network must be designed and ammonia pressures must be controlled to acquire waste heat efficiently from all contributing heat sources at a controlled temperature.

Raetz, John↗
NASA NTRS1995

Program For Analyzing Designs Of Liquid-Propellant Rockets

Rocket Combustor Interactive Design Computer Methodology (ROCCID) computer program provides standardized methodology, using state-of-art codes and procedures, for analysis of combustion performance and stability of liquid-propellant rocket engine. Provides combustion analyst with software tool to analyze existing combustor design (point-analysis option), or design high-performance, stable combustor, given set of input design requirements (point-design option). Written in ANSI FORTRAN 77 and VAX FORTRAN.

Klem, Mark D.↗
NASA NTRS1996

Mars pathfinder Rover egress deployable ramp assembly

The Mars Pathfinder Program is a NASA Discovery Mission, led by the Jet Propulsion Laboratory, to launch and place a small planetary Rover for exploration on the Martian surface. To enable safe and successful egress of the Rover vehicle from the spacecraft, a pair of flight-qualified, deployable ramp assemblies have been developed. This paper focuses on the unique, lightweight deployable ramp assemblies. A brief mission overview and key design requirements are discussed. Design and development activities leading to qualification and flight systems are presented.

Spence, Brian R.↗
NASA NTRS2003

How to Do Science From an Engineering Organization

MSFC's Space Environments Team performs engineering support for a number of NASA spaceflight projects by defining the space environment, developing design requirements, supporting the design process, and supporting operations. Examples of this type of support are given including meteoroid environment work for the Jovian Icy Moon Orbiter mission, ionizing radiation support for the Chandra X-Ray Observatory, and astronomicaVgeophysica1 observation planning for International Space Station.

Suggs, Robert M.↗
NASA NTRS2005

NASA Tech Briefs, November 2005

Topics covered include: Laser System for Precise, Unambiguous Range Measurements; Flexible Cryogenic Temperature and Liquid-Level Probes; Precision Cryogenic Dilatometer; Stroboscopic Interferometer for Measuring Mirror Vibrations; Some Improvements in H-PDLCs; Multiple-Bit Differential Detection of OQPSK; Absolute Position Encoders With Vertical Image Binning; Flexible, Carbon-Based Ohmic Contacts for Organic Transistors; GaAs QWIP Array Containing More Than a Million Pixels; AutoChem; Virtual Machine Language; Two-Dimensional Ffowcs Williams/Hawkings Equation Solver; Full Multigrid Flow Solver; Doclet To Synthesize UML; Computing Thermal Effects of Cavitation in Cryogenic Liquids; GUI for Computational Simulation of a Propellant Mixer; Control Program for an Optical-Calibration Robot; SQL-RAMS; Distributing Data from Desktop to Hand-Held Computers; Best-Fit Conic Approximation of Spacecraft Trajectory; Improved Charge-Transfer Fluorescent Dyes; Stability-Augmentation Devices for Miniature Aircraft; Tool Measures Depths of Defects on a Case Tang Joint; Two Heat-Transfer Improvements for Gas Liquefiers; Controlling Force and Depth in Friction Stir Welding; Spill-Resistant Alkali-Metal-Vapor Dispenser; A Methodology for Quantifying Certain Design Requirements During the Design Phase; Measuring Two Key Parameters of H3 Color Centers in Diamond; Improved Compression of Wavelet-Transformed Images; NASA Interactive Forms Type Interface - NIFTI; Predicting Numbers of Problems in Development of Software; Hot-Electron Photon Counters for Detecting Terahertz Photons; Magnetic Variations Associated With Solar Flares; and Artificial Intelligence for Controlling Robotic Aircraft.

Source record↗
NASA NTRS2007

Lessons Learned in the Specification, Purchase, Validation and Final Installation Process of a Replacement PCM Bit Synchronizer

This paper intends to describe the lessons learned while specifying validating and installing a bit sync to replace the 30 year old Aydin Model 335a PCM bit sync used in the Space Shuttle Launch Control Center. The engineer had to analyze the original requirements and specifications and then create new requirements documentation that more correctly described our needs. One issue to consider was the removal of unnecessary requirements such as various data formats when only one format is used. The conversion to a system that no longer has an assortment of analog rotary switches required retraining of the operators. Finally, post-procurement corrections for undisclosed user requirements and missed design requirements required close contact with a manufacturer who was willing to accommodate the changes.

Price, Richard N.↗
NASA NTRS2017

Technology Considerations for Inclusion of Survivability in MDAO

Rising traffic density, along with autonomy and diversity of vehicles in the air, will fundamentally change the safety environment of the future air transportation system. The change in risk is two-fold: increasing chances of mid-air collisions with non-cooperative objects and increasing chances of crashes over highly populated areas. The changing nature of the vehicles populating the airspace means that civilian aircraft design must now explicitly include considerations of survivability in the event of collision with other vehicles, as well as prevention of damage to people, animals and property on the ground, to a much greater extent than today. This paper offers a preliminary perspective on how MDAO could contribute toward these goals. One of the conclusions is that, in contrast to traditional vehicle design, to accommodate the complexity of the future airspace safely and efficiently, vehicle design requirements, modeling, and design optimization must be closely connected to the properties of the airspace, including those of other vehicles in the air. Thus, the total measure of a vehicle's survivability should include the traditional survivability in malfunction scenarios, combined with new considerations of survivability in collisions and survivability of the public on the ground.

Alexandrov, Natalia M.↗
NASA NTRSDate not supplied

Early Systems Integration Strengthens Orion Medical Capabilities

The Orion spacecraft has significant mass and volume constraints, which limits resources that can be provided for medical use. Sharing of resources between vehicle systems is therefore required to meet design requirements. This presentation will illustrate resource sharing within the Orion vehicle using oxygen as a case study.

C Haas↗
NASA NTRS1984

Natural laminar flow airfoil design considerations for winglets on low-speed airplanes

Winglet airfoil section characteristics which significantly influence cruise performance and handling qualities of an airplane are discussed. A good winglet design requires an airfoil section with a low cruise drag coefficient, a high maximum lift coefficient, and a gradual and steady movement of the boundary layer transition location with angle of attack. The first design requirement provides a low crossover lift coefficient of airplane drag polars with winglets off and on. The other requirements prevent nonlinear changes in airplane lateral/directional stability and control characteristics. These requirements are considered in the design of a natural laminar flow airfoil section for winglet applications and chord Reynolds number of 1 to 4 million.

Vandam, C. P.↗
NASA NTRS1972

Space Shuttle orbiter power system requirements and design.

This paper is the third in a series discussing space station-shuttle power systems. The power requirements of the orbiter and a tradeoff study of several possible power system concepts are presented. The power sources considered are fuel cells, solar array/battery, radioisotope Brayton, and cryogenic fueled turboalternators. A fuel cell power source is chosen as the best candidate for the orbiter power system. A baseline power system is defined using four fuel cells, secondary batteries, primary emergency batteries, and constant speed drive-alternator units for ferrying power. A weight and cost summary is included.

Lombard, J. W.↗
NASA NTRS2018

The IFS for WFIRST CGI: Science Requirements to Design

Direct Imaging of exoplanets using a coronagraph has become a major field of research both on the ground and in space. Key to the science of direct imaging is the spectroscopic capabilities of the instrument, our ability to extract spectra, and measure the abundance of molecular species such as Methane. To take these spectra, the WFIRST coronagraph instrument (CGI) uses an integral field spectrograph (IFS), which encodes the spectrum into a two-dimensional image on the detector. This results in more efficient detection and characterization of targets, and the spectral information is critical to achieving detection limits below the speckle floor of the imager. The CGI IFS operates in two18% bands spanning 600nm to 840nm at a nominal spectral resolution of R50. We present the current science and engineering requirements for the IFS design, the instrument design, anticipated performance, and how the calibration is integrated into the focal plane wavefront control algorithms. We also highlight the role of the Prototype Imaging Spectrograph for Coronagraphic Exoplanet Studies (PISCES) at the JPL High Contrast Imaging Testbed to demonstrate performance and validate calibration methodologies for the flight instrument.

Groff, Tyler D.↗
NASA NTRS2010

Functional Mobility Testing: Quantification of Functionally Utilized Mobility Among Unsuited and Suited Subjects

A novel approach was used in this test for the creation of mobility requirements to be fed into the Human-Systems Integration Requirements and Engineering Requirements Documents. Existing suits may not provide adequate mobility to perform all functional tasks required in future missions. Looking solely at maximum unsuited mobility could be unrealistic and unnecessary to design into a suit. The new approach focused instead on functional range of motion. Setting design requirements based on the mobility necessary to perform a broad spectrum of functional tasks should save resources while still providing a suit capable of performing all tasks that a suited crewmember is likely to encounter. Unsuited functional mobility testing revealed some interesting nuances of human movement including variances in mobility utilized when completing functional tasks as well as the impact of compound joint motions and the influence of joint loading on range of motion. Suited requirements must reflect the fact that altered movement strategies are utilized while wearing a space suit. Improved methods for the creation of space suit design requirements should lead to improved suit performance while maintaining crewmember safety and reducing overall costs.

Scott A. England↗
NASA NTRS2011

Launch Pad Escape System Design (Human Spaceflight)

A launch pad escape system for human spaceflight is one of those things that everyone hopes they will never need but is critical for every manned space program. Since men were first put into space in the early 1960s, the need for such an Emergency Escape System (EES) has become apparent. The National Aeronautics and Space Administration (NASA) has made use of various types of these EESs over the past 50 years. Early programs, like Mercury and Gemini, did not have an official launch pad escape system. Rather, they relied on a Launch Escape System (LES) of a separate solid rocket motor attached to the manned capsule that could pull the astronauts to safety in the event of an emergency. This could only occur after hatch closure at the launch pad or during the first stage of flight. A version of a LES, now called a Launch Abort System (LAS) is still used today for all manned capsule type launch vehicles. However, this system is very limited in that it can only be used after hatch closure and it is for flight crew only. In addition, the forces necessary for the LES/LAS to get the capsule away from a rocket during the first stage of flight are quite high and can cause injury to the crew. These shortcomings led to the development of a ground based EES for the flight crew and ground support personnel as well. This way, a much less dangerous mode of egress is available for any flight or ground personnel up to a few seconds before launch. The early EESs were fairly simple, gravity-powered systems to use when thing's go bad. And things can go bad very quickly and catastrophically when dealing with a flight vehicle fueled with millions of pounds of hazardous propellant. With this in mind, early EES designers saw such a passive/unpowered system as a must for last minute escapes. This and other design requirements had to be derived for an EES, and this section will take a look at the safety design requirements had to be derived for an EES, and this section will take a look at the safety design aspects for a launch pad escape system.

Maloney, Kelli↗
NASA NTRS2004

Requirements to Design to Code: Towards a Fully Formal Approach to Automatic Code Generation

A general-purpose method to mechanically transform system requirements into a provably equivalent model has yet to appear. Such a method represents a necessary step toward high-dependability system engineering for numerous possible application domains, including sensor networks and autonomous systems. Currently available tools and methods that start with a formal model of a system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The gap that current tools and methods leave unfilled is that their formal models cannot be proven to be equivalent to the system requirements as originated by the customer. For the classes of systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or in other appropriate graphical notations) into a provably equivalent formal model that can be used as the basis for code generation and other transformations.

Hinchey, Michael G.↗
NASA NTRS2005

Requirements to Design to Code: Towards a Fully Formal Approach to Automatic Code Generation

A general-purpose method to mechanically transform system requirements into a provably equivalent model has yet to appear. Such a method represents a necessary step toward high-dependability system engineering for numerous possible application domains, including distributed software systems, sensor networks, robot operation, complex scripts for spacecraft integration and testing, and autonomous systems. Currently available tools and methods that start with a formal model of a system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The gap that current tools and methods leave unfilled is that their formal models cannot be proven to be equivalent to the system requirements as originated by the customer. For the classes of systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or in other appropriate graphical notations) into a provably equivalent formal model that can be used as the basis for code generation and other transformations.

Hinchey, Michael G.↗