SEARCH · Search NASA
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.
The Skylab medical experiments altitude test plan is outlined. Described are the scope and objectives of the program, the management system under which it would be conducted, requirements for configuration of the test facility, test control documentation, data processing, and detailed test objectives.
The design factors being considered in the NASA space-station development program are summarized. The currently envisioned mission requirements are listed, and the system architecture is defined as a core station, mission-dedicated elements, and supporting equipment such as an orbit maneuvering vehicle. System design factors discussed include orbit selection, contamination control, autonomy, system safety, technology implementation, long life, reliability and maintainability, and cost; subsystem design factors include structural considerations, electrical power, environmental control and life support, data management, communications and tracking, onboard propulsion, habitability, and crew support. Configurational design is seen as driven by a number of factors, primarily the need to fit all components into the Shuttle payload bay for assembly in LEO by the Shuttle crew.
Water recovery subsystems are being tested at the NASA Lyndon B. Johnson Space Center for Space Station use to process waste water generated from urine and wash water collection facilities. These subsystems are being integrated into a water management system that will incorporate wash water and urine processing through the use of hyperfiltration and vapor compression distillation subsystems. Other hardware in the water management system includes a whole body shower, a clothes washing facility, a urine collection and pretreatment unit, a recovered water post-treatment system, and a water quality monitor. This paper describes the integrated test configuration, pertinent performance data, and feasibility and design compatibility conclusions of the integrated water management system.
GEOM manipulates and displays any geometry data expressed in Hess format. Provides user with capability to manipulate, modify, and view such geometric configurations interactively. GEOM program and the PAGMS data-base management system written in FORTRAN IV.
Conceptual spacecraft design considerations for using 30-kW class arcjet engines as an active load for a 100-kWe SP-100 space nuclear reactor power system flight experiment are discussed. These design considerations involve configuration trades; interfaces with power, attitude and velocity control, thermal management, orbit insertion and reaction control propulsion systems; imposed environments concerned with electromagnetic noise, survivability, and ammonia exhaust plumes; and associated diagnostic instrumentation.
Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system (a collection of tools for constructing distributed application management software) is described. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real-time reactive program. The underlying application is instrumented with a variety of built-in and user-defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when preexisting, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.
This viewgraph presentation reviews Structural Health Monitoring Analysis for the Orbiter Wing Leading Edge. The Wing Leading Edge Impact Detection System (WLE IDS) and the Impact Analysis Process are also described to monitor WLE debris threats. The contents include: 1) Risk Management via SHM; 2) Hardware Overview; 3) Instrumentation; 4) Sensor Configuration; 5) Debris Hazard Monitoring; 6) Ascent Response Summary; 7) Response Signal; 8) Distribution of Flight Indications; 9) Probabilistic Risk Analysis (PRA); 10) Model Correlation; 11) Impact Tests; 12) Wing Leading Edge Modeling; 13) Ascent Debris PRA Results; and 14) MM/OD PRA Results.
While significant and substantial progress continues to be accomplished toward readying the Space Launch System (SLS) rocket for its first test flight, work is already also underway on preparations for the second flight - using an upgraded version of the vehicle - and beyond. Designed to support human missions into deep space, Space Launch System (SLS), is the most powerful human-rated launch vehicle the United States has ever undertaken, and is one of three programs being managed by the National Aeronautics and Space Administration's (NASA's) Exploration Systems Development division. The Orion spacecraft program is developing a new crew vehicle that will support human missions beyond low Earth orbit (LEO), and the Ground Systems Development and Operations program is transforming Kennedy Space Center into a next-generation spaceport capable of supporting not only SLS but also multiple commercial users. Together, these systems will support human exploration missions into the proving ground of cislunar space and ultimately to Mars. For its first flight, SLS will deliver a near-term heavy-lift capability for the nation with its 70-metric-ton (t) Block 1 configuration. Each element of the vehicle now has flight hardware in production in support of the initial flight of the SLS, which will propel Orion around the moon and back. Encompassing hardware qualification, structural testing to validate hardware compliance and analytical modeling, progress in on track to meet the initial targeted launch date. In Utah and Mississippi, booster and engine testing are verifying upgrades made to proven shuttle hardware. At Michoud Assembly Facility in Louisiana, the world's largest spacecraft welding tool is producing tanks for the SLS core stage. Providing the Orion crew capsule/launch vehicle interface and in-space propulsion via a cryogenic upper stage, the Spacecraft/Payload Integration and Evolution (SPIE) element serves a key role in achieving SLS goals and objectives. The SPIE element marked a major milestone in 2014 with the first flight of original SLS hardware, the Orion Stage Adapter (OSA) which was used on Exploration Flight Test-1 with a design that will be used again on the first flight of SLS. The element has overseen production of the Interim Cryogenic Propulsion Stage (ICPS), an in-space stage derived from the Delta Cryogenic Second Stage, which was manufactured at United Launch Alliance in Decatur, Alabama, prior to being shipped to Florida for flight preparations. Manufacture of the Orion Stage Adapter and the Launch Vehicle Stage Adapter (LVSA) took place at the Friction Stir Facility located at Marshall Space Flight Center in Huntsville, Alabama. Marshall is also home to the Integrated Structural Test of the ICPS, LVSA, and OSA, subjecting the stacked components to simulated stresses of launch. The SPIE Element is also overseeing integration of 13 "CubeSat" secondary payloads that will fly on the first flight of SLS, providing access to deep space regions in a way currently not available to the science community. At the same time as this preparation work is taking place toward the first launch of SLS, however, the Space Launch System Program is actively working toward its second launch. For its second flight, SLS will be upgraded to the more-capable Block 1B configuration. While the Block 1 configuration is capable of delivering more than 70 metric tons to low Earth orbit, the Block 1B vehicle will increase that capability to 105 t. For that flight, the new configuration introduces two major new elements to the vehicle - an Exploration Upper Stage (EUS) that will be used for both ascent and in-space propulsion, and a Universal Stage Adapter (USA) that serves as a "payload bay" for the rocket, allowing the launch of large exploration systems along with the Orion spacecraft. Already, flight hardware is being prepared for the Block 1B vehicle. Welding is taking place on the second rocket's core stage. Flight hardware production has begun on booster components. An RS-25 engine slated for that flight has been tested. Development work is taking place on the Exploration Upper Stage, with contracts in place for both the stage and the RL10 engines which will power it. (The EUS will use four RL10 engines, an increase from one on the ICPS.) For the crew configuration of the Block 1B vehicle, the SLS SPIE element is managing the USA and accompanying Payload Adapter, which will accommodate both large payloads co-manifested with Orion and small-satellite secondary payloads. This co-manifested payload capacity will be instrumental for missions into the Proving Ground around the moon, where NASA will test new systems and demonstrate new capabilities needed for human exploration farther into deep space.
While significant and substantial progress continues to be accomplished toward readying the Space Launch System (SLS) rocket for its first test flight, work is already underway on preparations for the second flight - using an upgraded version of the vehicle - and beyond. Designed to support human missions into deep space, SLS is the most powerful human-rated launch vehicle the United States has ever undertaken, and is one of three programs being managed by the National Aeronautics and Space Administration's (NASA's) Exploration Systems Development division. The Orion spacecraft program is developing a new crew vehicle that will support human missions beyond low Earth orbit (LEO), and the Ground Systems Development and Operations (GSDO) program is transforming Kennedy Space Center (KSC) into a next-generation spaceport capable of supporting not only SLS but also multiple commercial users. Together, these systems will support human exploration missions into the proving ground of cislunar space and ultimately to Mars. For its first flight, SLS will deliver a near-term heavy-lift capability for the nation with its 70-metric-ton (t) Block 1 configuration. Each element of the vehicle now has flight hardware in production in support of the initial flight of the SLS, which will propel Orion around the moon and back. Encompassing hardware qualification, structural testing to validate hardware compliance and analytical modeling, progress is on track to meet the initial targeted launch date. In Utah and Mississippi, booster and engine testing are verifying upgrades made to proven shuttle hardware. At Michoud Assembly Facility (MAF) in Louisiana, the world's largest spacecraft welding tool is producing tanks for the SLS core stage. Providing the Orion crew capsule/launch vehicle interface and in-space propulsion via a cryogenic upper stage, the Spacecraft/Payload Integration and Evolution (SPIE) element serves a key role in achieving SLS goals and objectives. The SPIE element marked a major milestone in 2014 with the first flight of original SLS hardware, the Orion Stage Adapter (OSA) which was used on Exploration Flight Test-1 with a design that will be used again on the first flight of SLS. The element has overseen production of the Interim Cryogenic Propulsion Stage (ICPS), an in-space stage derived from the Delta Cryogenic Second Stage, which was manufactured at United Launch Alliance (ULA) in Decatur, Alabama, prior to being shipped to Florida for flight preparations. Manufacture of the OSA and the Launch Vehicle Stage Adapter (LVSA) took place at the Friction Stir Facility located at Marshall Space Flight Center (MSFC) in Huntsville, Alabama. Marshall is also home to the Integrated Structural Test of the ICPS, LVSA, and OSA, subjecting the stacked components to simulated stresses of launch. The SPIE Element is also overseeing integration of 13 "CubeSat" secondary payloads that will fly on the first flight of SLS, providing access to deep space regions in a way currently not available to the science community. At the same time as this preparation work is taking place toward the first launch of SLS, however, the Space Launch System Program is actively working toward its second launch. For its second flight, SLS will be upgraded to the more-capable Block 1B configuration. While the Block 1 configuration is capable of delivering more than 70 t to LEO, the Block 1B vehicle will increase that capability to 105 t. For that flight, the new configuration introduces two major new elements to the vehicle - an Exploration Upper Stage (EUS) that will be used for both ascent and in-space propulsion, and a Universal Stage Adapter (USA) that serves as a "payload bay" for the rocket, allowing the launch of large exploration systems along with the Orion spacecraft. Already, flight hardware is being prepared for the Block 1B vehicle. Welding is taking place on the second rocket's core stage. Flight hardware production has begun on booster components. An RS-25 engine slated for that flight has been tested. Development work is taking place on the EUS, with contracts in place for both the stage and the RL10 engines which will power it. (The EUS will use four RL10 engines, an increase from one on the ICPS.) For the crew configuration of the Block 1B vehicle, the SLS SPIE element is managing the USA and accompanying Payload Adapter, which will accommodate both large payloads co-manifested with Orion and small-satellite secondary payloads. This co-manifested payload capacity will be instrumental for missions into the proving ground around the moon, where NASA will test new systems and demonstrate new capabilities needed for human exploration farther into deep space.
The Configuration Aerodynamics (CA) element of the High Speed Research (HSR) program is managed by a joint NASA and Industry team, referred to as the Technology Integration Development (ITD) team. This team is responsible for the development of a broad range of technologies for improved aerodynamic performance and stability and control characteristics at subsonic to supersonic flight conditions. These objectives are pursued through the aggressive use of advanced experimental test techniques and state of the art computational methods. As the HSR program matures and transitions into the next phase the objectives of the Configuration Aerodynamics ITD are being refined to address the drag reduction needs and stability and control requirements of High Speed Civil Transport (HSCT) aircraft. In addition, the experimental and computational tools are being refined and improved to meet these challenges. The presentation will review the work performed within the Configuration Aerodynamics element in 1994 and 1995 and then discuss the plans for the 1996-1998 time period. The final portion of the presentation will review several observations of the HSR program and the design activity within Configuration Aerodynamics.
In optimizing a helicopter configuration, Hughes Helicopters uses a program called Computer Aided Sizing of Helicopters (CASH), written and updated over the past ten years, and used as an important part of the preliminary design process of the AH-64. First, measures of effectiveness must be supplied to define the mission characteristics of the helicopter to be designed. Then CASH allows the designer to rapidly and automatically develop the basic size of the helicopter (or other rotorcraft) for the given mission. This enables the designer and management to assess the various tradeoffs and to quickly determine the optimum configuration.
Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system is described: a collection of tools for constructing distributed application management software. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real time reactive program. The underlying application is instrumented with a variety of built-in and user defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when pre-existing, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.
In this presentation, the presenter will review what was done at Kennedy Space Center to deploy and implement PTC MathCAD and PTC Workgroup Manager in a multi-org system. During the presentation the presenter will explain how they configured PTC Windchill to create custom soft-types and object initialization rules for their custom numbering scheme and why they choose these methods. This presentation will also include how to modify the EPM default soft-type file in the PTC Windchill server codebase folder. The presenter will also go over the code used in a start up script to initiate PTC MathCAD and PTC Workgroup Manager in the proper order, and also set up the environment variables when running both PTC Workgroup Manager and PTC Creo. The configuration.ini file the presenter used will also be reviewed to show you how to set up the PTC Workgroup Manager and customized it to their user community. This presentation will be of interest to administrators trying to create a similar set-up in either a single org or multiple org system deployment. The big take away will be ideas and best practices learned through implementing this system, and the lessons learned what to do and not to do when setting up this configuration. Attendees will be exposed to several different sets of code used and that worked well and will hear some limitations on what the software can accomplish when configured this way.
Next generation concentrating solar thermal power (CSP) and novel solar thermochemical systems using concentrating solar thermal (CST) energy require high operating temperatures exceeding those of traditional nitrate-salt CSP systems. Particle-based systems are attractive for next-generation CSP and CST applications owing to high-temperature stability of inert silica- or alumina-based particulate materials, the lack of low-temperature freezing concerns that limit molten salt and/or molten metal heat transfer media, and cost-effective thermal storage using low-cost particulate and containment materials. Open-cavity falling particle receivers have many potential advantages, but face challenges pertaining to scalability, thermal loss, and particle loss through the open aperture, and are infeasible for chemical processes that require a low-oxygen ambient environment. Enclosed receiver configurations can be scalable, avoid particle loss when heating particles, and have potential for future chemical processes; however, particle-based heat transfer media provide substantially lower heat transfer rates than liquid media, and thus enclosed particle receiver designs require novel configurations to limit surface temperatures under the high incident solar flux concentrations necessary for high receiver thermal efficiency at high temperature. This paper introduces the novel planar-cavity enclosed particle receiver configuration in which arrays of planar surfaces are arranged into sub-vertical cavities. Large angles between the panel surface normal vectors and the aperture surface normal allow the incoming solar beam to distribute along the panel walls. Correspondingly, a high incident solar flux concentration at the cavity aperture produces substantially lower absorbed solar flux concentration on any panel wall. Sets of individual vertical cavities can be arranged to form a scalable receiver configuration.
Embedded computer systems and supporting operating systems have recently enabled the automation of many time-critical flight functions. This automation requires the integration of computer hardware and software, aircraft hardware, and the flight application. To properly integrate and control these critical functions requires a real-time environment that is provided by the onboard flight computer, a real-time operating system, and a real-time flight application that supplies the input commands to the aircraft and responds to the resulting actions. The increased complexity of developing and testing such real-time applications can best be supported by a separate test facility that provides the processing visibility and control which is virtually impossible in the actual real-time operating environment. Such a flight software validation facility has been developed at the NASA Langley Research Center to support applications using the Shuttle real-time language HAL/S. The development and control of this facility are described. Some of the management techniques used were project schedules, status monitoring, code walk-throughs, configuration control, phased releases, validation suites, and modern programming techniques.
The purpose of this document is to define the process for validation and verification (V&V) of software used to test the thermal data acquisition equipment in the Oak Ridge National Laboratory (ORNL) Package Testing Program (PTP) as part of the testing configuration(s). This process adheres to all applicable ORNL Standards Based Management System requirements and correlates with the PTP Quality Management System and the Software Quality Assurance Plan.
The stowage list and hardware tracking system, a computer based information management system, used in support of the space shuttle orbiter stowage configuration and the Johnson Space Center hardware tracking is described. The input, processing, and output requirements that serve as a baseline for system development are defined.
A three stage process of ground testing of the Space Telescope Pointing Control System is used for verification prior to on-orbit operation. First, development tests are conducted in a laboratory environment using flight/engineering model control sensor and actuators configured with an engineering model of the flight computer and data management system breadboards. These development tests validate the results of computer simulations predicting control system performance. Integration tests bring together flight system elements and software interfaced to a software simulation of vehicle dynamics to confirm closed loop performance. The final ground test phase, flight systems testing, is conducted on the fully assembled Space Telescope, verifies interfaces with the Fine Guidance Sensors and includes a thermal vacuum testing period. During the final test phase, the Point Control System is exercised with the dynamics simulator running in real time.