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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Statistical Evaluation of Utilization of the ISS

PayLoad Utilization Modeler (PLUM) is a statistical-modeling computer program used to evaluate the effectiveness of utilization of the International Space Station (ISS) in terms of the number of research facilities that can be operated within a specified interval of time. PLUM is designed to balance the requirements of research facilities aboard the ISS against the resources available on the ISS. PLUM comprises three parts: an interface for the entry of data on constraints and on required and available resources, a database that stores these data as well as the program output, and a modeler. The modeler comprises two subparts: one that generates tens of thousands of random combinations of research facilities and another that calculates the usage of resources for each of those combinations. The results of these calculations are used to generate graphical and tabular reports to determine which facilities are most likely to be operable on the ISS, to identify which ISS resources are inadequate to satisfy the demands upon them, and to generate other data useful in allocation of and planning of resources.

Andrews, Ross↗
NASA NTRS2008

Performance of a Borehole X-ray Fluorescence Spectrometer for Planetary Exploration

We have designed and constructed a borehole X-ray Fluorescence Spectrometer (XRFS) as part of the Mars Subsurface Access program [1]. It can be used to determine the composition of the Mars regolith at various depths by insertion into a pre-drilled borehole. The primary requirements and performance metrics for the instrument are to obtain parts-per-million (ppm) lower limits of detection over a wide range of elements in the periodic table (Magnesium to Lead). Power consumption during data collection was also measured. The prototype instrument is complete and preliminary testing has been performed. Terrestrial soil Standard Reference Materials were used as the test samples. Detection limits were about 10 weight ppm for most elements, with light elements being higher, up to 1.4 weight percent for magnesium. Power consumption (excluding ground support components) was 12 watts.

Kelliher, Warren C.↗
NASA NTRS2007

Visual Navigation - SARE Mission

The SARE Earth Observing and Technological Mission is part of the Argentinean Space Agency (CONAE - Comision Nacional de Actividades Espaciales) Small and Technological Payloads Program. The Argentinean National Space Program requires from the SARE program mission to test in a real environment of several units, assemblies and components to reduce the risk of using these equipments in more expensive Space Missions. The objective is to make use those components with an acceptable maturity in design or development, but without any heritage at space. From the application point of view, this mission offers new products in the Earth Observation data market which are listed in the present paper. One of the technological payload on board of the SARE satellite is the sensor Ground Tracker. It computes the satellite attitude and orbit in real time (goal) and/or by ground processing. For the first operating mode a dedicated computer and mass memory are necessary to be part of the mentioned sensor. For the second operational mode the hardware and software are much simpler.

Alonso, Roberto↗
NASA NTRS1979

The 25 kW power module evolution study. Part 3: Conceptual designs for power module evolution. Volume 2: Program plans

A plan is presented for the evolutionary development and deployment of the power module system with performance capabilities required to support the 1983 to 1990 user requirements. Aspects summarized include program functional, operational, and hardware elements; program work breakdown and specification items; development plans and schedules for developmental and technology milestones; test concepts and timeliness; and ground and orbit operations concepts.

Source record↗
NASA NTRS1983

Cardiovascular examinations and observations of deconditioning during the Space Shuttle orbital flight test program

During the first four flights of the Space Shuttle, cardiovascular data were obtained on each crewmember as part of the operational medicine requirements for crew health and safety. From monitoring blood pressure and electrocardiographic data, it was possible to estimate the degree of deconditioning imposed by exposure to the microgravity environment. For this purpose, a quantitative cardiovascular index of deconditioning (CID) was derived to aid the clinician in his assessment. Isotonic saline was then investigated as a countermeasure against orthostatic intolerance and found to be effective in partially reversing the hemodynamic consequences. It was observed that the space flight environment of reentry might potentially be arrhythmogenic in at least one individual.

Bungo, M. W.↗
NASA NTRS2020

Lunar Flashlight Propulsion System Fracture Control Plan

This document is intended to replace a previously approved Fracture Control Plan (VACCO X16029-10-FCP1) for the Lunar Flashlight Propulsion System (LFPS). The current LFPS is a new design and therefore requires a new plan; however, the spacecraft interfaces have remained the same. This document describes the elements of the Marshall Space Flight Center (MSFC)Fracture Control Program and the responsibilities for managing these elements for the LFPS for the Lunar Flashlight CubeSat mission that will launch as a secondary payload on the Space Launch System (SLS). The purpose of this document is to establish a plan for the fracture control activities for MSFC’s LFPS that will be used on the Lunar Flashlight CubeSat. This plan lists all the specific activities that will be performed to satisfy fracture control for this program. The provisions of this plan shall be met to demonstrate that the parts are in compliance with NASA’s fracture control requirements for space flight hardware.

Cubesat↗
NASA NTRS2002

Radiation Hardness Assurance for Space Systems

The space radiation environment can lead to extremely harsh operating conditions for on-board electronic box and systems. The characteristics of the radiation environment are highly dependent on the type of mission (date, duration and orbit). Radiation accelerates the aging of the electronic parts and material and can lead to a degradation of electrical performance; it can also create transient phenomena on parts. Such damage at the part level can induce damage or functional failure at electronic box, subsystem, and system levels. A rigorous methodology is needed to ensure that the radiation environment does not compromise the functionality and performance of the electronics during the system life. This methodology is called hardness assurance. It consists of those activities undertaken to ensure that the electronic piece parts placed in the space system perform to their design specifications after exposure to the space environment. It deals with system requirements, environmental definitions, part selection, part testing, shielding and radiation tolerant design. All these elements should play together in order to produce a system tolerant to.the radiation environment. An overview of the different steps of a space system hardness assurance program is given in section 2. In order to define the mission radiation specifications and compare these requirements to radiation test data, a detailed knowledge of the space environment and the corresponding electronic device failure mechanisms is required. The presentation by J. Mazur deals with the Earth space radiation environment as well as the internal environment of a spacecraft. The presentation by J. Schwank deals with ionization effects, and the presentation by T. Weatherford deals with Single particle Event Phenomena (SEP) in semiconductor devices and microcircuits. These three presentations provide more detailed background to complement the sections 3 and 4. Part selection and categorization are discussed in section 5. Section 6 presents the organization of the hardness assurance within a project. Section 7 discusses emerging radiation hardness assurance issues.

Poivey, Christian↗
NASA NTRS2019

"Making Safety Happen" Through Probabilistic Risk Assessment at NASA

NASA is using Probabilistic Risk Assessment (PRA) as one of the tools in its Safety & Mission Assurance (S&MA) tool belt to identify and quantify risks associated with human spaceflight. This paper discusses some of the challenges and benefits associated with developing and using PRA for NASA human space programs. Some programs have entered operation prior to developing a PRA, while some have implemented PRA from the start of the program. It has been observed that the earlier a design change is made in the concept or design phase, the less impact it has on cost and schedule. Not finding risks until the operation phase yields much costlier design changes and major delays, which can result in discussions of just accepting the risk. Risk contributors identified by PRA are not just associated with hardware failures. They include but are not limited to crew fatality due to medical causes, the environment the vehicle and crew are exposed to, the software being used, and the reliability of the crew performing required actions. Some programs have entered operation prior to developing a PRA, and while PRA can still provide a benefit for operations and future design trades, the benefit of implementing PRA from the start of the program provides the added benefit of informing design and reducing risk early in program development. Currently, NASA’s International Space Station (ISS) program is in its 20th year of on-orbit operations around the Earth and has several new programs in the design phase preparing to enter the operation phase all of which have active (or living) PRAs. These programs incorporate PRA as part of their Risk-Informed, Decision-Making (RIDM) process. For new NASA human spaceflight programs discussion begins with mission concept, establishing requirements, forming the PRA team, and continues through the design cycles into the operational phase. Several examples of PRA related applications and observed lessons are included.

Applications↗
NASA NTRS2008

Use of Probabilistic Engineering Methods in the Detailed Design and Development Phases of the NASA Ares Launch Vehicle

The United States National Aeronautics and Space Administration (NASA) is in the midst of a space exploration program called Constellation to send crew and cargo to the international Space Station, to the moon, and beyond. As part of the Constellation program, a new launch vehicle, Ares I, is being developed by NASA Marshall Space Flight Center. Designing a launch vehicle with high reliability and increased safety requires a significant effort in understanding design variability and design uncertainty at the various levels of the design (system, element, subsystem, component, etc.) and throughout the various design phases (conceptual, preliminary design, etc.). In a previous paper [1] we discussed a probabilistic functional failure analysis approach intended mainly to support system requirements definition, system design, and element design during the early design phases. This paper provides an overview of the application of probabilistic engineering methods to support the detailed subsystem/component design and development as part of the "Design for Reliability and Safety" approach for the new Ares I Launch Vehicle. Specifically, the paper discusses probabilistic engineering design analysis cases that had major impact on the design and manufacturing of the Space Shuttle hardware. The cases represent important lessons learned from the Space Shuttle Program and clearly demonstrate the significance of probabilistic engineering analysis in better understanding design deficiencies and identifying potential design improvement for Ares I. The paper also discusses the probabilistic functional failure analysis approach applied during the early design phases of Ares I and the forward plans for probabilistic design analysis in the detailed design and development phases.

Fayssal, Safie↗
NASA NTRS1991

Solar Pumped Lasers and Their Applications

Since 1980, NASA has been pursuing high power solar lasers as part of the space power beaming program. Materials in liquid, solid, and gas phases have been evaluated against the requirements for solar pumping. Two basic characteristics of solar insolation, namely its diffuse irradiance and 5800 K blackbody-like spectrum, impose rather stringent requirements for laser excitation. However, meeting these requirements is not insurmountable as solar thermal energy technology has progressed today, and taking advantage of solar pumping lasers is becoming increasingly attractive. The high density photons of concentrated solar energy have been used for mainly electric power generation and thermal processing of materials by the DOE Solar Thermal Technologies Program. However, the photons can interact with materials through many other direct kinetic paths, and applications of the concentrated photons could be extended to processes requiring photolysis, photosynthesis, and photoexcitation. The use of solar pumped lasers on Earth seems constrained by economics and sociopolitics. Therefore, prospective applications may be limited to those that require use of quantum effects and coherency of the laser in order to generate extremely high value products and services when conventional and inexpensive means are ineffective or impossible. The new applications already proposed for concentrated solar photons, such as destruction of hazardous waste, production of renewable fuel, production of fertilizer, and air/water pollution controls, may benefit from the use of inexpensive solar pumped laser matched with the photochemical kinetics of these processes.

Lee, Ja H.↗
NASA NTRS2008

A Data Type for Efficient Representation of Other Data Types

A self-organizing, monomorphic data type denoted a sequence has been conceived to address certain concerns that arise in programming parallel computers. A sequence in the present sense can be regarded abstractly as a vector, set, bag, queue, or other construct. Heretofore, in programming a parallel computer, it has been necessary for the programmer to state explicitly, at the outset, what parts of the program and the underlying data structures must be represented in parallel form. Not only is this requirement not optimal from the perspective of implementation; it entails an additional requirement that the programmer have intimate understanding of the underlying parallel structure. The present sequence data type overcomes both the implementation and parallel structure obstacles. In so doing, the sequence data type provides unified means by which the programmer can represent a data structure for natural and automatic decomposition to a parallel computing architecture. Sequences exhibit the behavioral and structural characteristics of vectors, but the underlying representations are automatically synthesized from combinations of programmers advice and execution use metrics. Sequences can vary bidirectionally between sparseness and density, making them excellent choices for many kinds of algorithms. The novelty and benefit of this behavior lies in the fact that it can relieve programmers of the details of implementations. The creation of a sequence enables decoupling of a conceptual representation from an implementation. The underlying representation of a sequence is a hybrid of representations composed of vectors, linked lists, connected blocks, and hash tables. The internal structure of a sequence can automatically change from time to time on the basis of how it is being used. Those portions of a sequence where elements have not been added or removed can be as efficient as vectors. As elements are inserted and removed in a given portion, then different methods are utilized to provide both an access and memory strategy that is optimized for that portion and the use to which it is put.

James, Mark↗
NASA NTRS2009

Ares I Avionics Introduction

The Ares I is the next generation human-rated launcher for the United States Constellation program. This system is required to provide single fault tolerance within defined crew safety and mission reliability limits. As part of the effort to achieve those safety goals, Ares I includes an avionics subsystem built as a multistring, voting architecture. The avionics design draws upon experience gained from building fly-by-wire systems for Shuttle, X- 38, and Seawolf. Architectural drivers for the avionics design include using proven technologies with existing suppliers of space rated parts for critical functions (to reduce overall development risk), easing the software development effort by using an off-theshelf, DO-178B certifiable, ARINC-653 operating system in the main flight computers, minimizing mutual data and power connections that might lead to a common-mode hardware failure of the redundant avionics strings, and centralizing overall Ares I command & control within the Upper Stage.

Marchant, Christopher C.↗
NASA NTRS2012

EVA Skills Training

Dr. Parazynski and a colleague from Extravehicular Activity (EVA), Robotics, & Crew Systems Operations (DX) worked closely to build the EVA Skills Training Program, and for the first time, defined the gold standards of EVA performance, allowing crewmembers to increase their performance significantly. As part of the program, individuals had the opportunity to learn at their own rate, taking additional water time as required, to achieve that level of performance. This focus on training to one's strengths and weaknesses to bolster them enabled the Crew Office and DX to field a much larger group of spacewalkers for the daunting "wall of EVA" required for the building and maintenance of the ISS. Parazynski also stressed the need for designers to understand the capabilities and the limitations of a human in a spacesuit, as well as opportunities to improve future generations of space. He shared lessons learned (how the Crew Office engaged in these endeavors) and illustrated the need to work as a team to develop these complex systems.

Parazynski, Scott↗
NASA NTRS1988

Energy Efficient Engine: High-pressure compressor test hardware detailed design report

The objective of the NASA Energy Efficient Engine program is to identify and verify the technology required to achieve significant reductions in fuel consumption and operating cost for future commercial gas turbine engines. The design and analysis is documented of the high pressure compressor which was tested as part of the Pratt and Whitney effort under the Energy Efficient Engine program. This compressor was designed to produce a 14:1 pressure ratio in ten stages with an adiabatic efficiency of 88.2 percent in the flight propulsion system. The corresponding expected efficiency for the compressor component test rig is 86.5 percent. Other performance goals are a surge margin of 20 percent, a corrected flow rate of 35.2 kg/sec (77.5 lb/sec), and a life of 20,000 missions and 30,000 hours. Low loss, highly loaded airfoils are used to increase efficiency while reducing the parts count. Active clearance control and case trenches in abradable strips over the blade tips are included in the compressor component design to further increase the efficiency potential. The test rig incorporates variable geometry stator vanes in all stages to permit maximum flexibility in developing stage-to-stage matching. This provision precluded active clearance control on the rear case of the test rig. Both the component and rig designs meet or exceed design requirements with the exception of life goals, which will be achievable with planned advances in materials technology.

Howe, David C.↗
NASA NTRS2008

Human Rating Requirements for NASA's Constellation Program

NASA s Constellation Program (CxP) will conduct a series of human space expeditions of increasing scope, starting with missions supporting the International Space Station and expanding to encompass the Moon and Mars. Although human-rating is an integral part of all CxP activities throughout their life cycle, NASA Procedural Requirements document NPR 8705.2B, Human-Rating Requirements (HRR) for Space Flight Systems, defines the additional processes, procedures, and requirements necessary to produce human-rated space systems that protect the safety of crew members and passengers on these NASA missions. In order to be in compliance with 8705.2B the CxP must show appropriate implementation or progression toward the HRR, or justification for an exception. Compliance includes an explanation of how the CxP intends to meet the HRR, analyses to be performed to determine implementation; and a matrix to trace the HRR to CxP requirements. The HRR requires the CxP to establish a human system integration team (HSIT), consisting of astronauts, mission operations personnel, training personnel, ground processing personnel, human factors personnel, and human engineering experts, with clearly defined authority, responsibility, and accountability to lead the human-system integration. For example, per the HRR the HSIT is involved in the evaluation of crew workload, human-in-the-loop usability evaluations, determining associated criteria, and in assessment of how these activities influenced system design. In essence, the HSIT is invaluable in CxP s ability to meet the three fundamental tenets of human rating: the process of designing, evaluating, and assuring that the total system can safely conduct the required human missions; the incorporation of design features and capabilities that accommodate human interaction with the system to enhance overall safety and mission success; and the incorporation of design features and capabilities to enable safe recovery of the crew from hazardous situations.

Berdich, Debbie↗
NASA NTRS2011

Digital Interface Board to Control Phase and Amplitude of Four Channels

An increasing number of parts are designed with digital control interfaces, including phase shifters and variable attenuators. When designing an antenna array in which each antenna has independent amplitude and phase control, the number of digital control lines that must be set simultaneously can grow very large. Use of a parallel interface would require separate line drivers, more parts, and thus additional failure points. A convenient form of control where single-phase shifters or attenuators could be set or the whole set could be programmed with an update rate of 100 Hz is needed to solve this problem. A digital interface board with a field-programmable gate array (FPGA) can simultaneously control an essentially arbitrary number of digital control lines with a serial command interface requiring only three wires. A small set of short, high-level commands provides a simple programming interface for an external controller. Parity bits are used to validate the control commands. Output timing is controlled within the FPGA to allow for rapid update rates of the phase shifters and attenuators. This technology has been used to set and monitor eight 5-bit control signals via a serial UART (universal asynchronous receiver/transmitter) interface. The digital interface board controls the phase and amplitude of the signals for each element in the array. A host computer running Agilent VEE sends commands via serial UART connection to a Xilinx VirtexII FPGA. The commands are decoded, and either outputs are set or telemetry data is sent back to the host computer describing the status and the current phase and amplitude settings. This technology is an integral part of a closed-loop system in which the angle of arrival of an X-band uplink signal is detected and the appropriate phase shifts are applied to the Ka-band downlink signal to electronically steer the array back in the direction of the uplink signal. It will also be used in the non-beam-steering case to compensate for phase shift variations through power amplifiers. The digital interface board can be used to set four 5-bit phase shifters and four 5-bit attenuators and monitor their current settings. Additionally, it is useful outside of the closed-loop system for beamsteering alone. When the VEE program is started, it prompts the user to initialize variables (to zero) or skip initialization. After that, the program enters into a continuous loop waiting for the telemetry period to elapse or a button to be pushed. A telemetry request is sent when the telemetry period is elapsed (every five seconds). Pushing one of the set or reset buttons will send the appropriate command. When a command is sent, the interface status is returned, and the user will be notified by a pop-up window if any error has occurred. The program runs until the End Program button is depressed.

Smith, Amy E.↗
NASA NTRSDate not supplied

Implementation of Human Systems Integration Technical and Management Process for the Lunar Gateway Program

NASA recognizes Human Systems Integration (HSI) as part of the overall systems engineering and acquisition strategy for space systems. The Lunar Gateway Program is implementing HSI technical and management process across the lifecycle of the mission, as required by NPR 7123.1C NASA Systems Engineering Processes and Requirements, and led by the Gateway HSI team as required by NPR 8705.2C Human-Rating Requirements for Space Systems, now HEOMD-003 Crewed Deep Space Systems Human Rating Certification Requirements and Standards for NASA Missions. NASA has been using HSI principles for many years and has applied them to many of its previous human spaceflight Programs. As NASA returns to the Moon in a more sustainable manner, the Gateway Program is maturing the application of HSI by implementing it more visibly as part of Artemis, with guidance from the NASA/SP-20210010952 NASA HSI Handbook. This paper discusses how HSI is being implemented in the Gateway Program, challenges faced with its implementation during the development phase, and strategies/approaches used to overcome those. The paper also covers HSI implementation for flight systems, vehicle processing, and interfaces across the six identified NASA HSI Domains: human factors engineering, operations, safety, training, maintainability and supportability, habitability and environment. The goal is to provide an overview of the implementation process of HSI in the Gateway Program as an example for other Programs/Projects/Missionsthat are looking to implement HSI.

Jackelynne Silva-Martinez↗
NASA NTRS1995

Flight test evaluation of the E-systems Differential GPS category 3 automatic landing system

Test flights were conducted to evaluate the capability of Differential Global Positioning System (DGPS) to provide the accuracy and integrity required for International Civil Aviation Organization (ICAO) Category (CAT) III precision approach and landings. These test flights were part of a Federal Aviation Administration (FAA) program to evaluate the technical feasibility of using DGPS based technology for CAT III precision approach and landing applications. An IAI Westwind 1124 aircraft (N24RH) was equipped with DGPS receiving equipment and additional computing capability provided by E-Systems. The test flights were conducted at NASA Ames Research Center's Crows Landing Flight Facility, Crows Landing, California. The flight test evaluation was based on completing 100 approaches and landings. The navigation sensor error accuracy requirements were based on ICAO requirements for the Microwave Landing System (MLS). All of the approaches and landings were evaluated against ground truth reference data provided by a laser tracker. Analysis of these approaches and landings shows that the E-Systems DGPS system met the navigation sensor error requirements for a successful approach and landing 98 out of 100 approaches and landings, based on the requirements specified in the FAA CAT III Level 2 Flight Test Plan. In addition, the E-Systems DGPS system met the integrity requirements for a successful approach and landing or stationary trial for all 100 approaches and landings and all ten stationary trials, based on the requirements specified in the FAA CAT III Level 2 Flight Test Plan.

Kaufmann, David N.↗