Search NASA⌕ Search

SEARCH · Search NASA

Results for “Configuration Control”

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 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS1948

Free-Spinning-Tunnel Tests of a 1/29-Scale Model of the Republic XP-91 Airplane with a Vee Tail Installed

A spin investigation has been conducted in the Langley 20 -foot free-spinning tunnel on a 1/29 - scale model of the Republic XP-91 airplane with vee tail installed. The effects cf control settings and movements upon the effect spin and recovery characteristics of the model were determined for the clean condition (wing tanks removed, landing gear and flaps retracted). The tests were made at a loading simulating that following cruise at altitude and at a time when nearly all fuel was expended. The results indicated that the airplane might not spin at normal spinning-control configuration, but if a spin were obtained, recovery therefrom by full rudder reversal would be satisfactory. It was also indicated that aileron-against settings would lead to violent oscillatory motions and should be avoided.

Snyder, Thomas L.↗
NASA NTRS2004

Computer-Aided Systems Engineering for Flight Research Projects Using a Workgroup Database

An online systems engineering tool for flight research projects has been developed through the use of a workgroup database. Capabilities are implemented for typical flight research systems engineering needs in document library, configuration control, hazard analysis, hardware database, requirements management, action item tracking, project team information, and technical performance metrics. Repetitive tasks are automated to reduce workload and errors. Current data and documents are instantly available online and can be worked on collaboratively. Existing forms and conventional processes are used, rather than inventing or changing processes to fit the tool. An integrated tool set offers advantages by automatically cross-referencing data, minimizing redundant data entry, and reducing the number of programs that must be learned. With a simplified approach, significant improvements are attained over existing capabilities for minimal cost. By using a workgroup-level database platform, personnel most directly involved in the project can develop, modify, and maintain the system, thereby saving time and money. As a pilot project, the system has been used to support an in-house flight experiment. Options are proposed for developing and deploying this type of tool on a more extensive basis.

Mizukami, Masahi↗
NASA NTRS1955

Supplementary Investigation in the Langley Free-Spinning Tunnel of a 1/20-Scale Model of the Douglas XF4D-1 Airplane Including Spin-Recovery Parachute Tests of the Model Loaded to Simulate the Douglas F5D-1 Airplane

A supplementary investigation has been conducted in the Langley 20-foot free-spinning tunnel of a l/20-scale model of the Douglas XF4D-1 airplane to determine the effect of only neutralizing the rudder for recovery from an inverted spin, and the effect of partial aileron deflection with the spin for recovery from an erect spin. An estimation of the size parachute required for satisfactory recovery from a spin with the model ballasted to represent the Douglas F5D-1 (formerly the Douglas XF4D-2) airplane was also made. Results of the original investigation on the XF4D-1 design are presented in NACA RM SL50K30a. The results indicated that satisfactory recoveries from inverted spins of the airplane should be obtained by rudder neutralization when the longitudinal stick position is neutral or forward. Recoveries from erect spins from the normal-spin control configuration should be satisfactory by full rudder reversal with simultaneous movement of the ailerons to two-thirds with the spin. For the parachute tests with the model loaded to represent the F5D-1 airplane, the tests indicated that a 16.7-foot-diameter hemispherical-tail parachute (drag coefficient of 1.082 based on the projected area) with a towline 20.0 feet long (full- scale values) should be satisfactory for an emergency spin-recovery device during demonstration spins of the airplane.

Klinar, Walter J.↗
NASA NTRS2009

A Summary of NASA and USAF Hypergolic Propellant Related Spills and Fires

Several unintentional hypergolic fluid related spills, fires, and explosions from the Apollo Program, the Space Shuttle Program, the Titan Program, and a few others have occurred over the past several decades. Spill sites include the following government facilities: Kennedy Space Center (KSC), Johnson Space Center (JSC), White Sands Test Facility (WSTF), Vandenberg Air Force Base (VAFB), Cape Canaveral Air Force Station (CCAFS), Edwards Air Force Base (EAFB), Little Rock AFB, and McConnell AFB. Until now, the only method of capturing the lessons learned from these incidents has been "word of mouth" or by studying each individual incident report. The root causes and consequences of the incidents vary drastically; however, certain "themes" can be deduced and utilized for future hypergolic propellant handling. Some of those common "themes" are summarized below: (1) Improper configuration control and internal or external human performance shaping factors can lead to being falsely comfortable with a system (2) Communication breakdown can escalate an incident to a level where injuries occur and/or hardware is damaged (3) Improper propulsion system and ground support system designs can destine a system for failure (4) Improper training of technicians, engineers, and safety personnel can put lives in danger (5) Improper PPE, spill protection, and staging of fire extinguishing equipment can result in unnecessary injuries or hardware damage if an incident occurs (6) Improper procedural oversight, development, and adherence to the procedure can be detrimental and quickly lead to an undesirable incident (7) Improper materials cleanliness or compatibility and chemical reactivity can result in fires or explosions (8) Improper established "back-out" and/or emergency safing procedures can escalate an event The items listed above are only a short list of the issues that should be recognized prior to handling hypergolic fluids or processing vehicles containing hypergolic propellants. The summary of incidents in this report is intended to cover many more issues than those listed above.

Nufer, Brian M.↗
NASA NTRS2009

Space Systems - Safety and Compatibility of Materials - Method to Determine the Flammability Thresholds of Materials

Spacecraft fire safety emphasizes fire prevention, which is achieved primarily through the use of fire-resistant materials. Materials selection for spacecraft is based on conventional flammability acceptance tests, along with prescribed quantity limitations and configuration control for items that are non-pass or questionable. ISO 14624-1 and -2 are the major methods used to evaluate flammability of polymeric materials intended for use in the habitable environments of spacecraft. The methods are upward flame-propagation tests initiated in static environments and using a well-defined igniter flame at the bottom of the sample. The tests are conducted in the most severe flaming combustion environment expected in the spacecraft. The pass/fail test logic of ISO 14624-1 and -2 does not allow a quantitative comparison with reduced gravity or microgravity test results; therefore their use is limited, and possibilities for in-depth theoretical analyses and realistic estimates of spacecraft fire extinguishment requirements are practically eliminated. To better understand the applicability of laboratory test data to actual spacecraft environments, a modified ISO 14624 protocol has been proposed that, as an alternative to qualifying materials as pass/fail in the worst-expected environments, measures the actual upward flammability limit for the material. A working group established by NASA to provide recommendations for exploration spacecraft internal atmospheres realized the importance of correlating laboratory data with real-life environments and recommended NASA to develop a flammability threshold test method. The working group indicated that for the Constellation Program, the flammability threshold information will allow NASA to identify materials with increased flammability risk from oxygen concentration and total pressure changes, minimize potential impacts, and allow for development of sound requirements for new spacecraft and extravehicular landers and habitats. Furthermore, recent research has shown that current normal gravity materials flammability tests do not correlate with flammability in ventilated, micro- or reduced-gravity conditions. Currently, the materials selection for spacecraft is based on the assumption of commonality between ground flammability test results and spacecraft environments, which does not appear to be valid. Materials flammability threshold data acquired in normal gravity can be correlated with data obtained in microgravity or reduced-gravity experiments, and consequently a more accurate assessment of the margin of safety of the material in the real environment can be made. In addition, the method allows the option of selecting better or best space system materials, as opposed to what would be considered just acceptable from a flammability point of view and realistic assessment of spacecraft fire extinguishment needs, which could result in significant weight savings. The knowledge afforded by this technique allows for limited extrapolations of flammability behavior to conditions not specifically tested and that could potentially result in significant cost and time savings. The intent of this Technical Specification is to bring to the attention of International Aerospace Community the importance of correlating laboratory test data with real-life space systems applications. The method presented is just one of the possibilities that are believed will lead to better understanding the applicability of laboratory aerospace materials flammability test data. International feedback on improving the proposed method, as well as suggestions for correlating other laboratory aerospace test data with real-life applications relevant to space systems are being sought.

Hirsch, David↗
NASA NTRS2010

A Comprehensive Validation Methodology for Sparse Experimental Data

A comprehensive program of verification and validation has been undertaken to assess the applicability of models to space radiation shielding applications and to track progress as models are developed over time. The models are placed under configuration control, and automated validation tests are used so that comparisons can readily be made as models are improved. Though direct comparisons between theoretical results and experimental data are desired for validation purposes, such comparisons are not always possible due to lack of data. In this work, two uncertainty metrics are introduced that are suitable for validating theoretical models against sparse experimental databases. The nuclear physics models, NUCFRG2 and QMSFRG, are compared to an experimental database consisting of over 3600 experimental cross sections to demonstrate the applicability of the metrics. A cumulative uncertainty metric is applied to the question of overall model accuracy, while a metric based on the median uncertainty is used to analyze the models from the perspective of model development by analyzing subsets of the model parameter space.

Norman, Ryan B.↗
NASA NTRS2008

REVEAL: Software Documentation and Platform Migration

The Research Environment for Vehicle Embedded Analysis on Linux (REVEAL) is reconfigurable data acquisition software designed for network-distributed test and measurement applications. In development since 2001, it has been successfully demonstrated in support of a number of actual missions within NASA s Suborbital Science Program. Improvements to software configuration control were needed to properly support both an ongoing transition to operational status and continued evolution of REVEAL capabilities. For this reason the project described in this report targets REVEAL software source documentation and deployment of the software on a small set of hardware platforms different from what is currently used in the baseline system implementation. This report specifically describes the actions taken over a ten week period by two undergraduate student interns and serves as a final report for that internship. The topics discussed include: the documentation of REVEAL source code; the migration of REVEAL to other platforms; and an end-to-end field test that successfully validates the efforts.

Wilson, Michael A.↗
NASA NTRS2011

REVEAL: Software Documentation and Platform Migration

The Research Environment for Vehicle Embedded Analysis on Linux (REVEAL) is reconfigurable data acquisition software designed for network-distributed test and measurement applications. In development since 2001, it has been successfully demonstrated in support of a number of actual missions within NASA's Suborbital Science Program. Improvements to software configuration control were needed to properly support both an ongoing transition to operational status and continued evolution of REVEAL capabilities. For this reason the project described in this report targets REVEAL software source documentation and deployment of the software on a small set of hardware platforms different from what is currently used in the baseline system implementation. This presentation specifically describes the actions taken over a ten week period by two undergraduate student interns and serves as an overview of the content of the final report for that internship.

Wilson, Michael A.↗
NASA NTRS2012

Dual-Doppler Feasibility Study

When two or more Doppler weather radar systems are monitoring the same region, the Doppler velocities can be combined to form a three-dimensional (3-D) wind vector field thus providing for a more intuitive analysis of the wind field. A real-time display of the 3-D winds can assist forecasters in predicting the onset of convection and severe weather. The data can also be used to initialize local numerical weather prediction models. Two operational Doppler Radar systems are in the vicinity of Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS); these systems are operated by the 45th Space Wing (45 SW) and the National Weather Service Melbourne, Fla. (NWS MLB). Dual-Doppler applications were considered by the 45 SW in choosing the site for the new radar. Accordingly, the 45th Weather Squadron (45 WS), NWS MLB and the National Aeronautics and Space Administration tasked the Applied Meteorology Unit (AMU) to investigate the feasibility of establishing dual-Doppler capability using the two existing systems. This study investigated technical, hardware, and software requirements necessary to enable the establishment of a dual-Doppler capability. Review of the available literature pertaining to the dual-Doppler technique and consultation with experts revealed that the physical locations and resulting beam crossing angles of the 45 SW and NWS MLB radars make them ideally suited for a dual-Doppler capability. The dual-Doppler equations were derived to facilitate complete understanding of dual-Doppler synthesis; to determine the technical information requirements; and to determine the components of wind velocity from the equation of continuity and radial velocity data collected by the two Doppler radars. Analysis confirmed the suitability of the existing systems to provide the desired capability. In addition, it is possible that both 45 SW radar data and Terminal Doppler Weather Radar data from Orlando International Airport could be used to alleviate any radar geometry issues at the NWS MLB radar, such as the "cone of silence" or beam blockage. In the event of a radar outage at one of the sites, the multi-radar algorithms would provide continuing coverage of the area through use of the data from the remaining operational radar sites. There are several options to collect, edit, synthesize and display dual-Doppler data sets. These options include commercial packages available for purchase and a variety of freeware packages available from the National Center for Atmospheric Research (NCAR) for processing raw radar data. However, evaluation of the freeware packages revealed that they do not have sufficient documentation and configuration control to be certified for 45 SW use. Additionally, a TI data line must be installed/leased from the NWS MLB office and CCAFS to enable the receipt of NWS MLB raw radar data to use in the dual-Doppler synthesis. Integration of the TI data line into the Eastern Range infrastructure that will meet the security requirements necessary for 45 SW use is time-consuming and costly. Overall evaluation indicates that establishment of the dual-Doppler capability using the existing operational radar systems is desirable and feasible with no technical concerns. Installation of such a system represents a significant enhancement to forecasting capabilities at the 45 WS and at NWS MLB. However, data security and cost considerations must be evaluated in light of current budgetary constraints. In any case, gaining the dual-Doppler capability will provide opportunities for better visualization of the wind field and better forecasting of the onset of convection and severe weather events to support space launch operations at KSC and CCAFS.

Huddleston, Lisa L.↗
NASA NTRS2012

Online Cable Tester and Rerouter

Hardware and algorithms have been developed to transfer electrical power and data connectivity safely, efficiently, and automatically from an identified damaged/defective wire in a cable to an alternate wire path. The combination of online cable testing capabilities, along with intelligent signal rerouting algorithms, allows the user to overcome the inherent difficulty of maintaining system integrity and configuration control, while autonomously rerouting signals and functions without introducing new failure modes. The incorporation of this capability will increase the reliability of systems by ensuring system availability during operations.

Lewis, Mark↗
NASA NTRS2009

Lessons Learned Entry: Hypergolic Propellant Related Spills and Fires

The attached report is a compilation of all credible, unintentional hypergolic fluid related spills, fires, and explosions from the Apollo Program, the Space Shuttle Program, Titan Program, and a few other programs. Spill sites include the following government facilities: KSC, JSC, WSTF, VAFB, CCAFS, EAFB, Little Rock AFB, and McConnell AFB. The root causes and consequences of the incidents contained in this document vary drastically; however, certain "themes" can be deduced and utilized for future hypergolic propellant handling. Some of those common "themes" are summarized below: (1) Improper configuration control and complacency can lead to being falsely comfortable with a system (2) Communication breakdown can escalate an incident to a level where injuries occur and/or hardware is damaged (3) Improper propulsion system and ground support system designs can destine a system for failure (4) Improper training of technicians, engineers, and safety personnel can put lives in danger (5) Improper PPE, spill protection, and staging of fire extinguishing equipment can result in unnecessary injuries or hardware damage if an incident occurs (6) Improper procedural oversight, development, and adherence to the procedure can be detrimental and quickly lead to an undesirable incident (7) Improper local cleanliness or compatibility can result in fires or explosions The items listed above are only a short list of the issues that should be recognized prior to handling of hypergolic fluids or processing of vehicles containing hypergolic propellants. The summary of incidents in this report is intended to cover many more issues than those listed above that have been found during nearly the entire spectrum. of hypergolic propellant and/or vehicle processing.

Nufer, Brian↗
NASA NTRS1942

Supplementary Spin Tests of a 1/20-Scale Model of the Bell XP-39E Airplane

As a result of the loss of the first XP-39E airplane due to an uncontrolled spin, and at the request of the War Department received in their letter to the NACA, March 31, 1942, additional tests have been made of the corresponding 1/20-scale spin-tunnel model. Tests were made for the normal full load condition and also for the loading condition corresponding to that of the airplane at the time of the crash, that Is, with guns, ammunition, and half of the fuel removed from the wings. The model tests were made with the tail arrangement corresponding to that of the airplane at the time of the crash, as well as with numerous modified tail and contour arrangements In an attempt to evolve satisfactory recovery characteristics. The tests were started on April 2, 1942, and completed in approximately two weeks, with the development of several alternate tail arrangements giving reasonably satisfactory recoveries for normal spinning control configuration. The tests were witnessed by Mr. Melvin Shorr, of the Materiel Center at Wright Field, and Mr. Paul C. Emmons, of the Bell Aircraft Corporation, to whom records of the test data were furnished. Colonel H. P. Swofford, of the Materiel Center, Wright Field, also witnessed part of the tests. A preliminary report of the results of the tests has been forwarded to the Materiel Command at Wright Field. A brief check of the parachute installation for the airplane was also made.

A I Neihouse↗
NASA NTRS2015

Core Flight System (cFS) a Low Cost Solution for SmallSats

The cFS is a FSW product line that uses a layered architecture and compile-time configuration parameters which make it portable and scalable for a wide range of platforms. The software layers that defined the application run-time environment are now under a NASA-wide configuration control board with the goal of sustaining an open-source application ecosystem.

flight software↗
NASA NTRS2016

Bumper 3 Update for IADC Protection Manual

The Bumper code has been the standard in use by NASA and contractors to perform meteoroid/debris risk assessments since 1990. It has undergone extensive revisions and updates [NASA JSC HITF website; Christiansen et al., 1992, 1997]. NASA Johnson Space Center (JSC) has applied BUMPER to risk assessments for Space Station, Shuttle, Mir, Extravehicular Mobility Units (EMU) space suits, and other spacecraft (e.g., LDEF, Iridium, TDRS, and Hubble Space Telescope). Bumper continues to be updated with changes in the ballistic limit equations describing failure threshold of various spacecraft components, as well as changes in the meteoroid and debris environment models. Significant efforts are expended to validate Bumper and benchmark it to other meteoroid/debris risk assessment codes. Bumper 3 is a refactored version of Bumper II. The structure of the code was extensively modified to improve maintenance, performance and flexibility. The architecture was changed to separate the frequently updated ballistic limit equations from the relatively stable common core functions of the program. These updates allow NASA to produce specific editions of the Bumper 3 that are tailored for specific customer requirements. The core consists of common code necessary to process the Micrometeoroid and Orbital Debris (MMOD) environment models, assess shadowing and calculate MMOD risk. The library of target response subroutines includes a board range of different types of MMOD shield ballistic limit equations as well as equations describing damage to various spacecraft subsystems or hardware (thermal protection materials, windows, radiators, solar arrays, cables, etc.). The core and library of ballistic response subroutines are maintained under configuration control. A change in the core will affect all editions of the code, whereas a change in one or more of the response subroutines will affect all editions of the code that contain the particular response subroutines which are modified. Note that the Bumper II program is no longer maintained or distributed by NASA.

Christiansen, Eric L.↗
NASA NTRS2016

The Core Flight System (cFS) Community: Providing Low Cost Solutions for Small Spacecraft

In February 2015 the NASA Goddard Space Flight Center (GSFC) completed the open source release of the entire Core Flight Software (cFS) suite. After the open source release a multi-NASA center Configuration Control Board (CCB) was established that has managed multiple cFS product releases. The cFS was developed and is being maintained in compliance with the NASA Class B software development process requirements and the open source release includes all Class B artifacts. The cFS is currently running on three operational science spacecraft and is being used on multiple spacecraft and instrument development efforts. While the cFS itself is a viable flight software (FSW) solution, we have discovered that the cFS community is a continuous source of innovation and growth that provides products and tools that serve the entire FSW lifecycle and future mission needs. This paper summarizes the current state of the cFS community, the key FSW technologies being pursued, the development/verification tools and opportunities for the small satellite community to become engaged. The cFS is a proven high quality and cost-effective solution for small satellites with constrained budgets.

System↗
NASA NTRS2016

Optical Testing and Verification Methods for the James Webb Space Telescope Integrated Science Instrument Module Element

NASA's James Webb Space Telescope (JWST) is a 6.6m diameter, segmented, deployable telescope for cryogenic IR space astronomy (~40K). The JWST Observatory includes the Optical Telescope Element (OTE) and the Integrated Science Instrument Module (ISIM) that contains four science instruments (SI) and the fine guider. The SIs are mounted to a composite metering structure. The SI and guider units were integrated to the ISIM structure and optically tested at the NASA Goddard Space Flight Center as a suite using the Optical Telescope Element SIMulator (OSIM). OSIM is a full field, cryogenic JWST telescope simulator. SI performance, including alignment and wave front error, were evaluated using OSIM. We describe test and analysis methods for optical performance verification of the ISIM Element, with an emphasis on the processes used to plan and execute the test. The complexity of ISIM and OSIM drove us to develop a software tool for test planning that allows for configuration control of observations, associated scripts, and management of hardware and software limits and constraints, as well as tools for rapid data evaluation, and flexible re-planning in response to the unexpected. As examples of our test and analysis approach, we discuss how factors such as the ground test thermal environment are compensated in alignment. We describe how these innovative methods for test planning and execution and post-test analysis were instrumental in the verification program for the ISIM element, with enough information to allow the reader to consider these innovations and lessons learned in this successful effort in their future testing for other programs.

spaceborne telescopes↗
NASA NTRS2017

Micrometeoroid and Orbital Debris Risk Assessment With Bumper 3

The Bumper 3 computer code is the primary tool used by NASA for micrometeoroid and orbital debris (MMOD) risk analysis. Bumper 3 (and its predecessors) have been used to analyze a variety of manned and unmanned spacecraft. The code uses NASA's latest micrometeoroid (MEM-R2) and orbital debris (ORDEM 3.0) environment definition models and is updated frequently with ballistic limit equations that describe the hypervelocity impact performance of spacecraft materials. The Bumper 3 program uses these inputs along with a finite element representation of spacecraft geometry to provide a deterministic calculation of the expected number of failures. The Bumper 3 software is configuration controlled by the NASA/JSC Hypervelocity Impact Technology (HVIT) Group. This paper will demonstrate MMOD risk assessment techniques with Bumper 3 used by NASA's HVIT Group. The Permanent Multipurpose Module (PMM) was added to the International Space Station in 2011. A Bumper 3 MMOD risk assessment of this module will show techniques used to create the input model and assign the property IDs. The methodology used to optimize the MMOD shielding for minimum mass while still meeting structural penetration requirements will also be demonstrated.

Hyde, J.↗
NASA NTRS2019

Bumper: A Tool for Analyzing Spacecraft Micrometeoroid and Orbital Debris Risk

“Bumper” is NASA’s computer program for analyzing spacecraft micrometeoroid and orbital debris (MMOD) risk. Bumper was developed in the late-1980s and has been continuously used and maintained since. The user base has grown from a few government entities to now include numerous commercial entities as well. The NASA Johnson Space Center (JSC) Hypervelocity Impact Technology (HVIT) Team is responsible for all aspects of the Bumper software. Bumper has been used to characterize MMOD risk on hundreds of spacecraft. All of the International Space Station (ISS) modules, visiting vehicles and numerous external components and systems have been analyzed. Bumper was used to analyze each of the Space Shuttle missions since STS-50. The Orion Multi-Purpose Crew Vehicle (MPCV) MMOD shielding is being developed using Bumper as well. Bumper has also been used on numerous telescopes (Hubble, James Webb, and Fermi Gamma-ray Space Telescopes), scientific probes (Stardust, New Horizons, Parker Solar Probe), and Earth observation satellites (Landsat, Joint Polar Satellite System). Bumper is also being used to analyze the micrometeoroid risk and support design of the Deep Space Gateway (DSG) and Mars Sample Return (MSR) missions. The HVIT Bumper Configuration Control Board (CCB) ensures that all changes to the code are approved, reviewed, and documented. Most of the changes are made to add new MMOD damage “ballistic limit equations” (BLEs). BLEs are typically added in response to completion of a hypervelocity impact (HVI) test series and development of an associated BLE. Other less frequent changes include updates of the debris or meteoroid environment models, feature enhancements, and feature retirement. Some BLEs are commercially sensitive and/or proprietary, so the CCB also manages code user-version control and software distribution. The current version – “Bumper 3” – is a FORTRAN executable that utilizes a 64-bit architecture. Bumper 3 has numerous features that make it a powerful tool for analyzing spacecraft MMOD risk. Bumper uses the latest orbital debris and micrometeoroid environment models. Bumper also easily processes large spacecraft geometry models, recognizes hidden surfaces, permits BLE assignment by name or number, and conducts quality checks of the spacecraft geometry model. Bumper 3 can also be used to estimate the effects of particle penetration through thin, high-standoff distance hardware components such as solar arrays and radiators. This is done using a special HVIT-developed technique know as the “3-Part Analysis.” The paper introduces the Bumper 3 MMOD risk analysis code and provides an example MMOD risk assessment showing Bumper’s role in the overall MMOD protection design process.

Lear, Dana M.↗