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 retrieval command subsystem reference manual for the NASA Aerospace Safety Information System (NASIS) is presented. The command subsystem may be operated conversationally or in the batch mode. Retrieval commands are categorized into search-oriented and output-oriented commands. The characteristics of ancillary commands and their application are reported.
The message file for the NASA Aerospace Safety Information System (NASIS) is discussed. The message file contains all the message and term explanations for the system. The data contained in the file can be broken down into three separate sections: (1) global terms, (2) local terms, and (3) system messages. The various terms are defined and their use within the system is explained.
The operation specifications for the NASA Aerospace Safety Information System are presented. The environment which leads to the design, implementation, and installation of the system is described. The manner in which the various components of the system inter-relate is explained. The manner in which the system was installed and subsequently modified is reported.
The Data Base Administrator User's Guide for the NASA Aerospace Safety Information System is presented. The subjects discussed are: (1) multi-terminal tasking, (2) data base executive, (3) utilities, (4) maintenance, (5) terminal support, and (6) retrieval subsystem.
The installation standards for the NASA Aerospace Safety Information System (NASIS) data base management system are presented. The standard approach to preparing systems documentation and the program design and coding rules and conventions are outlined. Included are instructions for preparing all major specifications and suggestions for improving the quality and efficiency of the programming task.
The systems overviews of the NASA Aerospace Safety Information System (NASIS) are presented. The overviews are directed toward informing management of a system's capabilities and requirements. The intent of the overviews is to introduce the system features to interested individuals. Each overview contains a description of the component's activities and roles in the overall system. The description includes charts and diagrams and a discussion of the performance requirements and growth potential of the module.
The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular set is prepared in a standard form and centralized in a single document. The format for the data set is provided.
The design specifications for the programs and modules within the NASA Aerospace Safety Information System (NASIS) are presented. The purpose of the design specifications is to standardize the preparation of the specifications and to guide the program design. Each major functional module within the system is a separate entity for documentation purposes. The design specifications contain a description of, and specifications for, all detail processing which occurs in the module. Sub-modules, reference tables, and data sets which are common to several modules are documented separately.
The retrieval command subsystem reference manual for the NASA Aerospace Safety Information System (NASIS) is presented. The output oriented classification of retrieval commands provides the user with the ability to review a set of data items for verification or inspection as a typewriter or CRT terminal and to print a set of data on a remote printer. Predefined and user-definable data formatting are available for both output media.
The message file for the NASA Aerospace Safety Information System (NASIS) is discussed. The message file contains all the message and term explanations for the system. The data contained in the file can be broken down into three separate sections: (1) global terms, (2) local terms, and (3) system messages. The various terms are defined and their use within the system is explained.
The Data Base Administrator User's Guide for the NASA Aerospace Safety information system is presented. The subjects discussed are: (1) multi-terminal tasking, (2) data base executive, (3) utilities, (4) maintenance, and (5) update mode functions.
The work on ignition and combustion research in oxygen systems under the sponsorship of NASA's Aerospace Safety Research and Data Institute (ASRDI) is described. Preliminary results of ignition of nonmetallic materials by electric arc and mechanical impact are presented. Ignition by a resonant process involving repeated shock waves has been demonstrated and some of the results included. In addition, results of studies concerned with ignition due to the rapid rupture of metal films and diaphragms are reviewed. Burning rate studies of three nommetallic materials in oxygen enriched environments were completed and the results are presented.
Reports on the research projects performed under the NASA/ASEE Summer Faculty Fellowship Program are presented. The program was conducted by The University of Alabama and MSFC during the period from June 4, 1990 through August 10, 1990. Some of the topics covered include: (1) Space Shuttles; (2) Space Station Freedom; (3) information systems; (4) materials and processes; (4) Space Shuttle main engine; (5) aerospace sciences; (6) mathematical models; (7) mission operations; (8) systems analysis and integration; (9) systems control; (10) structures and dynamics; (11) aerospace safety; and (12) remote sensing
In response to a request from the House of Representatives Committee on Science, Space, and Technology in its Report No. 102-500 of April 22, 1992, the Aerospace Safety Advisory Panel (ASAP) created an ad hoc task force to conduct a thorough assessment of the Space Shuttle Main Engine (SSME). The membership was drawn mostly from organizations other than ASAP, and this report represents the views of that task force. Its task was to assess the risk that the SSME poses to the safe operation of the Space Shuttle, to identify and evaluate improvements to the engine that would reduce the risk, and to recommend a set of priorities for the implementation of these improvements. The SSME Assessment Team, as it opted to call itself, convened in mid-1992 and, subsequently, met with and gathered information from all the principal organizations involved in the SSME program. These included the Rocketdyne Division of Rockwell International, the Marshall Space Flight Center of NASA, and the Pratt & Whitney Division of United Technologies Corporation. The information in this report reflects the program status as of October 1992. From the information received, the Team formed its conclusions and recommendations. Changes in the program status have, of course, occurred since that time; however, they did not affect the Team's conclusions and recommendations.
At the request of the President of the United States through the Office of Science and Technology Policy (OSTP), the NASA Administrator tasked the Aerospace Safety Advisory Panel with the responsibility to identify and review issues associated with the safe operation and management of the Space Shuttle program arising from ongoing efforts to improve and streamline operations. These efforts include the consolidation of operations under a single Space Flight Operations Contract (SFOC), downsizing the Space Shuttle workforce and reducing costs of operations and management. The Panel formed five teams to address the potentially significant safety impacts of the seven specific topic areas listed in the study Terms of Reference. These areas were (in the order in which they are presented in this report): Maintenance of independent safety oversight; implementation plan for the transition of Shuttle program management to the Lead Center; communications among NASA Centers and Headquarters; transition plan for downsizing to anticipated workforce levels; implementation of a phased transition to a prime contractor for operations; Shuttle flight rate for Space Station assembly; and planned safety and performance upgrades for Space Station assembly. The study teams collected information through briefings, interviews, telephone conversations and from reviewing applicable documentation. These inputs were distilled by each team into observations and recommendations which were then reviewed by the entire Panel.
The projected radiation levels within the International Space Station (ISS) have been criticized by the Aerospace Safety Advisory Panel in their report to the NASA Administrator. Methods for optimal reconfiguration and augmentation of the ISS shielding are now being developed. The initial steps are to develop reconfigurable and realistic radiation shield models of the ISS modules, develop computational procedures for the highly anisotropic radiation environment, and implement parametric and organizational optimization procedures. The targets of the redesign process are the crew quarters where the astronauts sleep and determining the effects of ISS shadow shielding of an astronaut in a spacesuit. The ISS model as developed will be reconfigurable to follow the ISS. Swapping internal equipment rack assemblies via location mapping tables will be one option for shield optimization. Lightweight shield augmentation materials will be optimally fit to crew quarter areas using parametric optimization procedures to minimize the augmentation shield mass. The optimization process is being integrated into the Intelligence Synthesis Environment s (ISE s) immersive simulation facility at the Langley Research Center and will rely on High Performance Computing and Communication (HPCC) for rapid evaluation of shield parameter gradients.
Text analysis is important for effective information retrieval from databases where the critical information is embedded in text fields. Aerospace safety depends on effective retrieval of relevant and related problem reports for the purpose of trend analysis. The complex text syntax in problem descriptions has limited statistical text mining of problem reports. The presentation describes an intelligent tagging approach that applies syntactic and then semantic analysis to overcome this problem. The tags identify types of problems and equipment that are embedded in the text descriptions. The power of these tags is illustrated in a faceted searching and browsing interface for problem report trending that combines automatically generated tags with database code fields and temporal information.
Catastrophic accidents are usually preceded by precursory events that, although observable, are not recognized as harbingers of a tragedy until after the fact. In the nuclear industry, the Three Mile Island accident was preceded by at least two events portending the potential for severe consequences from an underappreciated causal mechanism. Anomalies whose failure mechanisms were integral to the losses of Space Transportation Systems (STS) Challenger and Columbia had been occurring within the STS fleet prior to those accidents. Both the Rogers Commission Report and the Columbia Accident Investigation Board report found that processes in place at the time did not respond to the prior anomalies in a way that shed light on their true risk implications. This includes the concern that, in the words of the NASA Aerospace Safety Advisory Panel (ASAP), "no process addresses the need to update a hazard analysis when anomalies occur" At a broader level, the ASAP noted in 2007 that NASA "could better gauge the likelihood of losses by developing leading indicators, rather than continue to depend on lagging indicators". These observations suggest a need to revalidate prior assumptions and conclusions of existing safety (and reliability) analyses, as well as to consider the potential for previously unrecognized accident scenarios, when unexpected or otherwise undesired behaviors of the system are observed. This need is also discussed in NASA's system safety handbook, which advocates a view of safety assurance as driving a program to take steps that are necessary to establish and maintain a valid and credible argument for the safety of its missions. It is the premise of this handbook that making cases for safety more experience-based allows NASA to be better informed about the safety performance of its systems, and will ultimately help it to manage safety in a more effective manner. The APA process described in this handbook provides a systematic means of analyzing candidate accident precursors by evaluating anomaly occurrences for their system safety implications and, through both analytical and deliberative methods used to project to other circumstances, identifying those that portend more serious consequences to come if effective corrective action is not taken. APA builds upon existing safety analysis processes currently in practice within NASA, leveraging their results to provide an improved understanding of overall system risk. As such, APA represents an important dimension of safety evaluation; as operational experience is acquired, precursor information is generated such that it can be fed back into system safety analyses to risk-inform safety improvements. Importantly, APA utilizes anomaly data to predict risk whereas standard reliability and PRA approaches utilize failure data which often is limited and rare.