Search NASA⌕ Search

SEARCH · Search NASA

Results for “parts program 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 181 records · Page 10

Weight Optimization of Active Thermal Management Using a Novel Heat Pump

Efficient lightweight power generation and thermal management are two important aspects for space applications. Weight is added to the space platforms due to the inherent weight of the onboard power generation equipment and the additional weight of the required thermal management systems. Thermal management of spacecraft relies on rejection of heat via radiation, a process that can result in large radiator mass, depending upon the heat rejection temperature. For some missions, it is advantageous to incorporate an active thermal management system, allowing the heat rejection temperature to be greater than the load temperature. This allows a reduction of radiator mass at the expense of additional system complexity. A particular type of active thermal management system is based on a thermodynamic cycle, developed by the authors, called the Solar Integrated Thermal Management and Power (SITMAP) cycle. This system has been a focus of the authors research program in the recent past (see Fig. 1). One implementation of the system requires no moving parts, which decreases the vibration level and enhances reliability. Compression of the refrigerant working fluid is accomplished in this scheme via an ejector.

Lear, William E.↗

Performance of Airborne Precision Spacing Under Realistic Wind Conditions

With the expected worldwide increase of air traffic during the coming decade, both the Federal Aviation Administration s (FAA s) Next Generation Air Transportation System (NextGen), as well as Eurocontrol s Single European Sky ATM Research (SESAR) program have, as part of their plans, air traffic management solutions that can increase performance without requiring time-consuming and expensive infrastructure changes. One such solution involves the ability of both controllers and flight crews to deliver aircraft to the runway with greater accuracy than is possible today. Previous research has shown that time-based spacing techniques, wherein the controller assigns a time spacing to each pair of arriving aircraft, is one way to achieve this goal by providing greater runway delivery accuracy that produces a concomitant increase in system-wide performance. The research described herein focuses on a specific application of time-based spacing, called Airborne Precision Spacing (APS), which has evolved over the past ten years. This research furthers APS understanding by studying its performance with realistic wind conditions obtained from atmospheric sounding data and with realistic wind forecasts obtained from the Rapid Update Cycle (RUC) short-range weather forecast. In addition, this study investigates APS performance with limited surveillance range, as provided by the Automatic Dependent Surveillance-Broadcast (ADS-B) system, and with an algorithm designed to improve APS performance when an ADS-B signal is unavailable. The results presented herein quantify the runway threshold delivery accuracy of APS un-der these conditions, and also quantify resulting workload metrics such as the number of speed changes required to maintain spacing.

Wieland, Frederick↗

Risk Classification and Risk-based Safety and Mission Assurance

Recent activities to revamp and emphasize the need to streamline processes and activities for Class D missions across the agency have led to various interpretations of Class D, including the lumping of a variety of low-cost projects into Class D. Sometimes terms such as Class D minus are used. In this presentation, mission risk classifications will be traced to official requirements and definitions as a measure to ensure that projects and programs align with the guidance and requirements that are commensurate for their defined risk posture. As part of this, the full suite of risk classifications, formal and informal will be defined, followed by an introduction to the new GPR 8705.4 that is currently under review.GPR 8705.4 lays out guidance for the mission success activities performed at the Classes A-D for NPR 7120.5 projects as well as for projects not under NPR 7120.5. Furthermore, the trends in stepping from Class A into higher risk posture classifications will be discussed. The talk will conclude with a discussion about risk-based safety and mission assuranceat GSFC.

Risk Management↗

AMD Radeon e9173 Low Power PCIE GPU Single Event Effects Test Report

The AMD Radeon Embedded e9170 Graphics Processing Unit (GPU), notably the e9173 Peripheral Component Interconnect Express (PCIE) variant, is of interest to Artemis generation programs with requirements for graphics rendering, compute, artificial intelligence (Ai) with a constraints-requiring piece-part procurement and power consumption of less than 50W. In addition to collecting heavy ion data on this device, a secondary purpose of this test campaign was to validate video capture hardware and software workflows used with GPU, microprocessor and system-on-chip device testing. Five (5) test patterns from the NEPP Processor Enclave (NPE) test suite were used with the e9173. The test patterns covered the operating system’s (OS) idle contribution towards the cross section, matrix math using tensorflow-rocm, two artificial intelligence models developed at NASA GSFC, and an industry standard GPU benchmarking application called Mesa GLXGears.

NASA Technical Memorandum (TM) test report for pos↗

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↗

Concept Development of a Mach 1.6 High-Speed Civil Transport

A high-speed civil transport configuration with a Mach number of 1.6 was developed as part of the NASA High-Speed Research Program to serve as a baseline for assessing advanced technologies required for an aircraft with a service entry date of 2005. This configuration offered more favorable solutions to environmental concerns than configurations with higher Mach numbers. The Mach 1.6 configuration was designed for a 6500 n.mi. mission with a 250-passenger payload. The baseline configuration has a wing area of 8732 square feet a takeoff gross weight of 591570 lb, and four 41000-lb advanced turbine bypass engines defined by NASA. These engines have axisymmetric mixer-ejector nozzles that are assumed to yield 20 dB of noise suppression during takeoff, which is assumed to satisfy, the FAR Stage III noise requirements. Any substantial reduction in this assumed level of suppression would require oversizing the engines to meet community noise regulations and would severly impact the gross weight of the aircraft at takeoff. These engines yield a ratio of takeoff thrust to weight of 0.277 and a takeoff wing loading of 67.8 lb/square feet that results in a rotation speed of 169 knots. The approach velocity of the sized configuration at the end of the mission is 131 knots. The baseline configuration was resized with an engine having a projected life of 9000 hr for hot rotating parts and 18000 hr for the rest of the engine, as required for commercial use on an aircraft with a service entry date of 2005. Results show an increase in vehicle takeoff gross weight of approximately 58700 lb. This report presents the details of the configuration development, mass properties, aerodynamic design, propulsion system and integration, mission performance, and sizing.

Shields, Elwood W.↗

Electron-proton spectrometer quality assurance procedures for equipment and parts

Quality control procedures are established for personnel who are concerned with receiving, storage, transfer, inspection, and use of flight or mission related hardware for the electron/proton spectrometer (EPS) program. While general guidelines, designed to cover all situations, exist, this document provides guidelines and procedures specifically designed to supplement the quality assurance activity on the EPS Program. It is the purpose of this document to insure that all equipment, parts and other hardware received and/or used in the EPS program meet or surpass the standards and requirements established by cognizant authorities.

Gleeson, P.↗

Astronomy sortie missions definition study. Volume 4: Program development requirements

Program development requirements for the selected Astronomy Sortie Missions concept were generated and are presented in four parts as follows: (1)the gross planning requirements that must be considered in subsequent phases of the project; (2)the schedules and logic networks for the design, development, and operation of the overall project; (3)the supporting research and technology required to support the project; and (4)the work breakdown data, from which cost data will be generated. Data reported in each part includes the appropriate rationale with explanations of the guidelines and assumptions that were used in the analyses and estimates.

Source record↗

LACIE performance predictor final operational capability program description, volume 3

The requirements and processing logic for the LACIE Error Model program (LEM) are described. This program is an integral part of the Large Area Crop Inventory Experiment (LACIE) system. LEM is that portion of the LPP (LACIE Performance Predictor) which simulates the sample segment classification, strata yield estimation, and production aggregation. LEM controls repetitive Monte Carlo trials based on input error distributions to obtain statistical estimates of the wheat area, yield, and production at different levels of aggregation. LEM interfaces with the rest of the LPP through a set of data files.

Source record↗

System safety in Stirling engine development

The DOE/NASA Stirling Engine Project Office has required that contractors make safety considerations an integral part of all phases of the Stirling engine development program. As an integral part of each engine design subtask, analyses are evolved to determine possible modes of failure. The accepted system safety analysis techniques (Fault Tree, FMEA, Hazards Analysis, etc.) are applied in various degrees of extent at the system, subsystem and component levels. The primary objectives are to identify critical failure areas, to enable removal of susceptibility to such failures or their effects from the system and to minimize risk.

Bankaitis, H.↗

Satellite power system concept development and evaluation program. Volume 2: System definition

The system level results of the system definition studies performed by NASA as a part of the Department of Energy/NASA satellite power system concept development and evaluation program are summarized. System requirements and guidelines are discussed as well as the major elements that comprise the reference system and its design options. Alternative system approaches including different system sizes, solid state amplifier (microwave) concepts, and laser power transmission system cost summaries are reviewed. An overview of the system analysis and planning efforts is included. The overall study led to the conclusion that the reference satellite power system concept is a feasible baseload source of electrical power and, within the assumed guidelines, the minimum cost per kilowatt is achieved at the maximum output of 5 gigawatts to the utility grid. Major unresolved technical issues include maximum allowable microwave power density in the ionosphere and performance/mass characteristics of laser power transmission systems.

Source record↗

Shuttle on-orbit contamination and environmental effects

Ensuring the compatibility of the space shuttle system with payloads and payload measurements is discussed. An extensive set of quantitative requirements and goals was developed and implemented by the space shuttle program management. The performance of the Shuttle system as measured by these requirements and goals was assessed partly through the use of the induced environment contamination monitor on Shuttle flights 2, 3, and 4. Contamination levels are low and generally within the requirements and goals established. Additional data from near-term payloads and already planned contamination measurements will complete the environment definition and allow for the development of contamination avoidance procedures as necessary for any payload.

Leger, L. J.↗

Report from upper atmospheric science

Most of the understanding of the thermosphere resulted from the analysis of data accrued through the Atmosphere Explorer satellites, the Dynamics Explorer 2 satellite, and observations from rockets, balloons, and ground based instruments. However, new questions were posed by the data that have not yet been answered. The mesosphere and lower thermosphere have been less thoroughly studied because of the difficulty of accessibility on a global scale, and many rather fundamental characteristics of these regions are not well understood. A wide variety of measurement platforms can be used to implement various parts of a measurement strategy, but the major thrusts of the International Solar Terrestrial Physics Program would require Explorer-class missions. A remote sensing mission to explore the mesosphere and lower thermosphere and one and two Explorer-type spacecraft to enable a mission into the thermosphere itself would provide the essential components of a productive program of exploration of this important region of the upper atomsphere. Theoretical mission options are explored.

Carignan, G. R.↗

The HYDROS mission: requirements and baseline system design

The HYDROS mission is under development by NASA as part of its Earth System Science Pathfinder program. HYDROS is designed to provide global maps of the Earth's soil moisture and freeze/thaw state every 2-3 days, for weather and climate prediction, water and carbon cycle studies, natural hazards monitoring, and national security applications.

radar↗

Cooperative Conflict Avoidance Sensor Trade Study Report, Version 2

This study develops evaluation criteria for systems and technologies against the Cooperative Conflict Avoidance (CCA) requirements for unmanned flight at and above FL430 as part of Step 1 of the Access-5 program. These evaluation criteria are then applied to both current and future technologies to identify those which might be used to provide an Equivalent Level of Safety (ELOS) for CCA. This document provides the results of this analysis of various systems and technologies intended for evaluation as part of the CCA work package.

Source record↗

Performance of Airborne Precision Spacing Under Realistic Wind Conditions and Limited Surveillance Range

With the expected worldwide increase of air traffic during the coming decade, both the Federal Aviation Administration's (FAA's) Next Generation Air Transportation System (NextGen), as well as Eurocontrol's Single European Sky ATM Research (SESAR) program have, as part of their plans, air traffic management (ATM) solutions that can increase performance without requiring time-consuming and expensive infrastructure changes. One such solution involves the ability of both controllers and flight crews to deliver aircraft to the runway with greater accuracy than they can today. Previous research has shown that time-based spacing techniques, wherein the controller assigns a time spacing to each pair of arriving aircraft, can achieve this goal by providing greater runway delivery accuracy and producing a concomitant increase in system-wide performance. The research described herein focuses on one specific application of time-based spacing, called Airborne Precision Spacing (APS), which has evolved over the past ten years. This research furthers APS understanding by studying its performance with realistic wind conditions obtained from atmospheric sounding data and with realistic wind forecasts obtained from the Rapid Update Cycle (RUC) short-range weather forecast. In addition, this study investigates APS performance with limited surveillance range, as provided by the Automatic Dependent Surveillance-Broadcast (ADS-B) system, and with an algorithm designed to improve APS performance when ADS-B surveillance data is unavailable. The results presented herein quantify the runway threshold delivery accuracy of APS under these conditions, and also quantify resulting workload metrics such as the number of speed changes required to maintain spacing.

Wieland, Frederick↗

Towards a Standard for Provenance and Context for Preservation of Data for Earth System Science

Long-term data sets with data from many missions are needed to study trends and validate model results that are typical in Earth System Science research. Data and derived products originate from multiple missions (spaceborne, airborne and/or in situ) and from multiple organizations. During the missions as well as well past their termination, it is essential to preserve the data and products to support future studies. Key aspects of preservation are: preserving bits and ensuring data are uncorrupted, preserving understandability with appropriate documentation, and preserving reproducibility of science with appropriate documentation and other artifacts. Computer technology provides adequate standards to ensure that, with proper engineering, bits are preserved as hardware evolves. However, to ensure understandability and reproducibility, it is essential to plan ahead to preserve all the relevant data and information. There are currently no standards to identify the content that needs to be preserved, leading to non-uniformity in content and users not being sure of whether preserved content is comprehensive. Each project, program or agency can specify the items to be preserved as a part of its data management requirements. However, broader community consensus that cuts across organizational or national boundaries would be needed to ensure comprehensiveness, uniformity and long-term utility of archived data. The Federation of Earth Science Information Partners (ESIP), a diverse network of scientists, data stewards and technology developers, has a forum for ESIP members to collaborate on data preservation issues. During early 2011, members discussed the importance of developing a Provenance and Context Content Standard (PCCS) and developed an initial list of content items. This list is based on the outcome of a NASA and NOAA meeting held in 1998 under the auspices of the USGCRP, documentation requirements from NOAA and our experience with some of the NASA Earth science missions. The items are categorized into the following 8 high level categories: Preflight/Pre-Operations, Products (Data), Product Documentation, Mission Calibration, Product Software, Algorithm Input, Validation, Software Tools.

Ramaprian, Hampapuram K.↗