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 objective of the project is to develop an acoustic modeling capability, based on commercial off-the-shelf software, to be used as a tool for oversight of the future manned Constellation vehicles to ensure compliance with acoustic requirements and thus provide a safe and habitable acoustic environment for the crews, and to validate developed models via building physical mockups and conducting acoustic measurements.
The International Space Station (ISS) presents a significant acoustics challenge considering all of the Modules and equipment that make it an on-orbit laboratory workshop and home with long-term crew occupation. This challenge is further complicated by the fact there are numerous and a wide variety suppliers of Station hardware, including International Partners. This paper addresses how ISS acoustics are managed to ensure a safe and habitable environment by establishing requirements, providing oversight and design support, sharing lessons learned and information, testing for hardware compliance, predicting future acoustic levels, and performing on-orbit measurement and monitoring of actual acoustic levels. ISS acoustic requirements are classified by the type of hardware involved, in three categories: Modules; payloads; and Government Furnished Equipment (GFE). Current status of overall ISS acoustics for each of these hardware categories will be discussed. In addition, the following items will be discussed: examples where NASA design support has been used to aid in obtaining compliance; difficulties encountered; and areas of concern.
The objective of the project is to develop an acoustic modeling capability, based on commercial off-the-shelf software, to be used as a tool for oversight of the future manned Constellation vehicles. The use of such a model will help ensure compliance with acoustic requirements. Also, this project includes modeling validation and development feedback via building physical mockups and conducting acoustic measurements to compare with the predictions.
Once deployed, all intricate systems that operate for a long time (such as an airplane or chemical processing plant) experience degraded performance during operational lifetime. These can result from losses of integrity in subsystems and parts that generally do not materially impact the operation of the vehicle (e.g., the light behind the button that opens the sliding door of the minivan). Or it can result from loss of more critical parts or subsystems. Such losses need to be handled quickly in order to avoid loss of personnel, mission, or part of the system itself. In order to manage degraded systems, knowledge of its potential problem areas and the means by which these problems are detected should be developed during the initial development of the system. Once determined, a web of sensors is employed and their outputs are monitored with other system parameters while the system is in preparation or operation. Just gathering the data is only part of the story. The interpretation of the data itself and the response of the system must be carefully developed as well to avoid a mishap. Typically, systems use a test-threshold-response paradigm to process potential system faults. However, such processing sub-systems can suffer from errors and oversights of a consistent type, causing system aberrant behavior instead of expected system and recovery operations. In our study, we developed a complete checklist for determining the completeness of a fault system and its robustness to common processing and response difficulties.
I. Design: a) S/C designed to be largely single fault tolerant; b) Operate in flight demonstrated envelope, with margin; and c) Strict compliance with requirements & flight rules. II. Test: a) Baseline, fault & stress testing using flight system testbeds (H/W & S/W); b) In-flight checkout & demos to remove first time events. III. Failure Analysis: a) Critical event driven fault tree analysis; b) Risk mitigation & development of contingencies. IV) Residual Risks: a) Accepted pre-launch waivers to Single Point Failures; b) Unavoidable risks (e.g. natural disaster). V) Mission Assurance: a) Strict process for characterization of variances (ISAs, PFRs & Waivers; b) Full time Mission Assurance Manager reports to Program Manager: 1) Independent assessment of compliance with institutional standards; 2) Oversight & risk assessment of ISAs, PFRs & Waivers etc.; and 3) Risk Management Process facilitator.
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.
There have been a number of studies done in the past drawn on lessons learned with regard to human loss-of-life events. Generally, the systemic causes and proximate causes for fatal events have both been examined in considerable detail. However, an examination of near-fatal accidents and failures that narrowly missed being fatal could be equally useful, not only in detecting causes, both proximate and systemic, but also for determining what factors averted disaster, what design decisions and/or operator actions prevented catastrophe. Additionally, review of risk factors for upcoming or future programs will often look at trending statistics, generally focusing on failure/success statistics. Unfortunately, doing so can give a skewed or misleading view of past reliability or a reliability that cannot be presumed to apply to a new program. One reason for this might be that failure/success criteria aren't the same across programs, but also that apparent success can hide systemic faults that, under other circumstances, can be fatal to a program with different parameters. A program with a number of near misses can look more reliable than a consistently healthy program with a single out-of-family failure and provide very misleading data if it is not examined in detail. This is particularly true for a manned space program where failure/success includes more than making a particular orbit. Augmenting reliability evaluations with this near miss data can provide insight and expand on the limitations of a strictly pass/fail evaluation. Even more importantly, a thorough understanding of these near miss events can identify conditions that prevented fatalities. Those conditions may be key to a programs reliability, but, without insight to the repercussions if such conditions were not in place, their importance may not be readily clear. As programs mature and political and fiscal responsibilities come to the fore, often there is considerable incentive to eliminate unnecessary conservatism, design margin, redundancy, operational support, testing, training, or safety oversight. An evaluation that demonstrates how these features and capabilities averted disaster can ensure processes that saved lives or missions are not discarded without appropriate review and understanding. Close examination of accidents that almost were can also highlight differences in design from one program to another, either justifying reliability comparisons or negating them. It can also provide considerable insight into how those saving factors were developed and implemented so that similar methods can be used to ensure appropriate life-saving and mission saving factors can be developed, even for a dissimilar space program. The lessons are appropriate for seasoned manned space programs and agencies, but crucial for untried agencies and organizations that are interested in sending man into space. The large body of publicly available near miss and accident data available provide invaluable insight into programmatic, technical, and even political issues that can be addressed before they impact safety. In this paper, we examine a number of these near misses and accidents and steps a program, agency, or potential spacefaring company might take to improve their chances of success and avoid mission or safety disasters using this data.
Acoustic limits in habitable space enclosures are required to ensure crew safety, comfort, and habitability. Noise control is implemented to ensure compliance with the acoustic requirements. The purpose of this paper is to describe problems with establishing acoustic requirements and noise control efforts, and present examples of noise control treatments and design applications used in the Space Shuttle Orbiter. Included is the need to implement the design discipline of acoustics early in the design process, and noise control throughout a program to ensure that limits are met. The use of dedicated personnel to provide expertise and oversight of acoustic requirements and noise control implementation has shown to be of value in the Space Shuttle Orbiter program. It is concluded that to achieve acceptable and safe noise levels in the crew habitable space, early resolution of acoustic requirements and implementation of effective noise control efforts are needed. Management support of established acoustic requirements and noise control efforts is essential.
The Simple, Scalable, Script-based Science Processing (S4P) Archive (S4PA) is a disk-based archival system for remote sensing data. It is based on the data-driven framework of S4P and is used for data transfer, data preprocessing, metadata generation, data archive, and data distribution. New data are automatically detected by the system. S4P provides services such as data access control, data subscription, metadata publication, data replication, and data recovery. It comprises scripts that control the data flow. The system detects the availability of data on an FTP (file transfer protocol) server, initiates data transfer, preprocesses data if necessary, and archives it on readily available disk drives with FTP and HTTP (Hypertext Transfer Protocol) access, allowing instantaneous data access. There are options for plug-ins for data preprocessing before storage. Publication of metadata to external applications such as the Earth Observing System Clearinghouse (ECHO) is also supported. S4PA includes a graphical user interface for monitoring the system operation and a tool for deploying the system. To ensure reliability, S4P continuously checks stored data for integrity, Further reliability is provided by tape backups of disks made once a disk partition is full and closed. The system is designed for low maintenance, requiring minimal operator oversight.
Within the Department of Defense, multiple architectures are created to serve and fulfill one or several specific service or mission related LVC training goals. Multiple Object Models exist across and within those architectures and it is there that those disparate object models are a major source of interoperability problems when developing and constructing the training scenarios. The two most commonly used architectures are; HLA and TENA, with DIS and CTIA following close behind in terms of the number of users. Although these multiple architectures can share and exchange data the underlying meta-models for runtime data exchange are quite different, requiring gateways/translators to bridge between the different object model representations; while the Department of Defense's use of gateways are generally effective in performing these functions, as the LVC environment increases so too does the cost and complexity of these gateways. Coupled with the wide range of different object models across the various user communities we increase the propensity for run time errors, increased programmer stop gap measures during coordinated exercises, or failure of the system as a whole due to unknown or unforeseen incompatibilities. The Joint Composable Object Model (JCOM) project was established under an M&S Steering Committee (MSSC)-sponsored effort with oversight and control placed under the Joint Forces Command J7 Advanced Concepts Program Directorate. The purpose of this paper is to address the initial and the current progress that has been made in the following areas; the Conceptual Model Development Format, the Common Object Model, the Architecture Neutral Data Exchange Model (ANDEM), and the association methodology to allow the re-use of multiple architecture object models and the development of the prototype persistent reusable library.
In August 2006, NASA awarded Space Act Agreements (SAAs) for Commercial Orbital Transportation Services (COTS) under the Commercial Crew and Cargo Project Office at Johnson Space Center. One of the goals of the SAAs is to facilitate U.S. private industry demonstration of cargo transportation capabilities, ultimately achieving reliable, cost effective access to low-Earth orbit (LEO). Each COTS provider is required to complete International Space Stations (ISS) Integration activities, which includes meeting the physical and functional interfaces and interface requirements between the ISS and COTS vehicles. These requirements focus on the areas of risk to the ISS during rendezvous and proximity operations, as well as the integration operations while the COTS vehicle is berthed to the ISS. On December 23, 2008, NASA awarded Commercial Resupply Service (CRS) contracts to provide resupply services to the ISS, following the Shuttle retirement. In addition to performing any ISS Integration activities, NASA will be performing independent assessments of the launch vehicle and orbital vehicle to evaluate the readiness of the contractor to deliver NASA cargo safely to the ISS. This paper will address the activities NASA Centers, both JSC and KSC, in the oversight and insight function over commercial visiting vehicles to the ISS.
The goal of this collaborative project between FC-MD, APL, and GSFC and supported by NASA IV&V Software Assurance Research Program (SARP), was to develop a tool, Dynamic SAVE, or Dyn-SAVE for short, for analyzing architectures of systems of systems. The project team was comprised of the principal investigator (PI) from FC-MD and four other FC-MD scientists (part time) and several FC-MD students (full time), as well as, two APL software architects (part time), and one NASA POC (part time). The PI and FC-MD scientists together with APL architects were responsible for requirements analysis, and for applying and evaluating the Dyn-SAVE tool and method. The PI and a group of FC-MD scientists were responsible for improving the method and conducting outreach activities, while another group of FC-MD scientists were responsible for development and improvement of the tool. Oversight and reporting was conducted by the PI and NASA POC. The project team produced many results including several prototypes of the Dyn-SAVE tool and method, several case studies documenting how the tool and method was applied to APL s software systems, and several published papers in highly respected conferences and journals. Dyn-SAVE as developed and enhanced throughout this research period, is a software tool intended for software developers and architects, software integration testers, and persons who need to analyze software systems from the point of view of how it communicates with other systems. Using the tool, the user specifies the planned communication behavior of the system modeled as a sequence diagram. The user then captures and imports the actual communication behavior of the system, which is then converted and visualized as a sequence diagram by Dyn-SAVE. After mapping the planned to the actual and specifying parameter and timing constraints, Dyn-SAVE detects and highlights deviations between the planned and the actual behavior. Requirements based on the need to analyze two inter-system communication protocols that are representative of protocols used in the Aerospace industry have been specified. The protocols are related: APL s Common Ground System (CGS) as used in the MErcury Surface, Space ENvironment, GEochemistry, and Ranging (MESSENGER) and the Radiation Belt Space Probes (RBSP) missions. The analyzed communications were implementations of the Telemetry protocol and the CCSDS File Delivery Protocol (CFDP) protocol. Based on these requirements, three prototypes of Dyn-SAVE were developed and applied to these protocols. The application of Dyn-SAVE to these protocols resulted in the detection of several issues. Dyn-SAVE was also applied to several Testbeds that have previously been used for experimentation earlier on this project, as well as, to other protocols and logs for testing its broader applicability. For example, Dyn-SAVE was used to analyze 1) the communication pattern between a web browser and a web server, 2) the system log of a computer in order to detect offnominal computer shut-down behavior, and 3) the actual test cases of NASA Goddard s Core Flight System (CFS) and automatically generated test cases in order to determine the overlap between the two sets of test cases. In all cases, Dyn-SAVE assisted in providing insightful conclusions about each of the cases identified above.
In 2004, NASA awarded the Research, Operations, Maintenance, and Engineering (ROME) contract at NASA Langley Research Center to a team led by Jacobs Technology, Inc. A key component of the contract was the transitioning of the five large wind tunnel facilities from NASA managed and NASA or NASA/contractor workforces to fully contractor operated. The contractor would manage daily operations while NASA would continue to develop long-term strategies, make decisions regarding commitment of funds and commitment of facilities, and provide oversight of the contractor's performance. A major challenge would be the transition of knowledge of facility operations and maintenance from the incumbent civil servant workforce to the contractor workforce. While the contract has since been modified multiple times, resulting in a blended NASA/ROME workforce across the facilities, the processes developed and implemented to capture and document facility knowledge from the incumbent subject matter experts, build training and certification programs, and grow individual skills across subject areas and across facilities, are worthy of documentation. This is the purpose of this paper.
The NASA Exploration Systems Mission Directorate (ESMD) and Penn State technology commercialization project was designed to assist in the maturation of a NASA SBIR Phase III technology. The project was funded by NASA's ESMD Education group with oversight from the Surface Systems Office at NASA Kennedy Space Center in the Engineering Directorate. Two Penn State engineering student interns managed the project with support from Honeybee Robotics and NASA Kennedy Space Center. The objective was to find an opportunity to integrate SBIR-developed Regolith Extractor and Sampling Technology as the payload for the future Lunar Lander or Rover missions. The team was able to identify two potential Google Lunar X Prize organizations with considerable interest in utilizing regolith acquisition and transfer technology.
Airsickness is the most significant medical condition affecting naval aviation training. A 2001 study showed that airsickness was reported in 81% of naval aviation students and was associated with 82% of below average flight scores. The cost to a single training air-wing was over $150,000 annually for fuel and maintenance costs alone. Resistent cases are sent to the Naval Aerospace Medical Institute (NAMI) for evaluation and desensitization in the self-paced airsickness desensitization (SPAD) program. This approach is 75% successful, but can take up to 8 weeks at a significant travel cost. NASA Ames Research Center's Autogenic Feedback Training Exercises (AFTE) uses physiological and biofeedback training for motion sickness prevention. It has a remote capability that has been used from Moffett Field, CA to Atlanta, GA . AFTE is administered in twelve (30-minute) training sessions. The success rate for the NASA AFTE program has been over 85%. Methods: Implementation Phases: Phase I: Transfer NASA AFTE to NAMI; NASA will remotely train aviation students at NAMI. Phase II: NAMI-centered AFTE application with NASA oversight. Phase III: NAMI-centered AFTE to remotely train at various Navy sites. Phase IV: NAMI to offer Tri-service application and examine research opportunities. Results: 1. Use available telemedicine connectivity between NAMI and NASA. 2. Save over $2,000 per student trained. 3. Reduce aviation training attrition. 4. Provide standardization of multi-location motion sickness training. 5. Future tri-service initiatives. 6. Data to NASA and Navy for QA and research opportunities.
Presentation topics include: standards in a changing business model, the new National Space Policy is driving change, a new paradigm for human spaceflight, consistency across standards, the purpose of standards, danger of over-prescriptive standards, a balance is needed (between prescriptive and general standards), enabling versus inhibiting, characteristics of success-oriented standards, characteristics of success-oriented standards, and conclusions. Additional slides include NASA Procedural Requirements 8705.2B identifies human rating standards and requirements, draft health and medical standards for human rating, what's been done, government oversight models, examples of consistency from anthropometry, examples of inconsistency from air quality and appendices of government and non-governmental human factors standards.
To date six long duration astronauts have experienced in flight visual changes and post flight signs of optic disc edema, globe flattening, choroidal folds, hyperoptic shifts and or raised intracranial pressure. In some cases the changes were transient while in others they are persistent with varying degrees of visual impairment. Given that all astronauts exposed to microgravity experience a cephalad fluid shift, and that both symptomatic and asymptomatic patients have exhibited optic nerve sheath edema on MRI, there is a high probability that all astronauts develop in-flight idiopathic intracranial hypertension to some degree. Those who are susceptible, have an increased likelihood of developing treatment resistant papilledema resulting in visual impairment and possible long-term vision loss. Such an acquired disability would have a profound mission impact and would be detrimental to the long term health of the astronaut. The visual impairment and increased intracranial pressure phenomenon appears to have multiple contributing factors. Consequently, the working "physiological fault bush" with elevated intracranial pressure at its center, is divided into ocular effects, and CNS and other effects. Some of these variables have been documented and or measured through operational data gathering, while others are unknown, undocumented and or hypothetical. Both the complexity of the problem and the urgency to find a solution require that a unique, non-traditional research model be employed such as the Accelerated Research Collaboration(TM) (ARC) model that has been pioneered by the Myelin Repair Foundation. In the ARC model a single entity facilitates and manages all aspects of the basic, translational, and clinical research, providing expert oversight for both scientific and managerial efforts. The result is a comprehensive research plan executed by a multidisciplinary team and the elimination of stove-piped research. The ARC model emphasizes efficient and effective communication between management and investigators; and real-time sharing of scientific discoveries in an effort to solve complex problems.
With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better understanding of the mission assurance that MOD brings to commercial ventures to the ISS