The systems safety program for a total space launch vehicle general requirements
Requirements and elements of systems safety program for launch vehicle development
COMPONENT RELIABILITY↗
SEARCH · Search NASA
Results for “System Safety”
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.
Spaceflight Ground Support Equipment Reliability & System Safety Data
Presented were Reliability Analysis, consisting primarily of Failure Modes and Effects Analysis (FMEA), and System Safety Analysis, consisting of Preliminary Hazards Analysis (PHA), performed to ensure that the CoNNeCT (Communications, Navigation, and Networking re- Configurable Testbed) Flight System was safely and reliably operated during its Assembly, Integration and Test (AI&T) phase. A tailored approach to the NASA Ground Support Equipment (GSE) standard, NASA-STD-5005C, involving the application of the appropriate Requirements, S&MA discipline expertise, and a Configuration Management system (to retain a record of the analysis and documentation) were presented. Presented were System Block Diagrams of selected GSE and the corresponding FMEA, as well as the PHAs. Also discussed are the specific examples of the FMEAs and PHAs being used during the AI&T phase to drive modifications to the GSE (via "redlining" of test procedures, and the placement of warning stickers to protect the flight hardware) before being interfaced to the Flight System. These modifications were necessary because failure modes and hazards were identified during the analysis that had not been properly mitigated. Strict Configuration Management was applied to changes (whether due to upgrades or expired calibrations) in the GSE by revisiting the FMEAs and PHAs to reflect the latest System Block Diagrams and Bill Of Material. The CoNNeCT flight system has been successfully assembled, integrated, tested, and shipped to the launch site without incident. This demonstrates that the steps taken to safeguard the flight system when it was interfaced to the various GSE were successful.
Fernandez, Rene↗
Reflections on system safety and the law
The application of law to the determination of what constitutes safeness is discussed. The numerous factors are analyzed which enter into the decisions of courts in deciding what is safe and what is unsafe. It is pointed out that as technology changes, legal interpretations of safety also change. Arguements are given for the use of system safety techniques and better engineering analyses as instruments of defense against liability.
Daniel F. Hayes Sr.↗
Autonomous Flight Safety System September 27, 2005, Aircraft Test
This report describes the first aircraft test of the Autonomous Flight Safety System (AFSS). The test was conducted on September 27, 2005, near Kennedy Space Center (KSC) using a privately-owned single-engine plane and evaluated the performance of several basic flight safety rules using real-time data onboard a moving aerial vehicle. This test follows the first road test of AFSS conducted in February 2005 at KSC. AFSS is a joint KSC and Wallops Flight Facility (WEF) project that is in its third phase of development. AFSS is an independent subsystem intended for use with Expendable Launch Vehicles that uses tracking data from redundant onboard sensors to autonomously make flight termination decisions using software-based rules implemented on redundant flight processors. The goals of this project are to increase capabilities by allowing launches from locations that do not have or cannot afford extensive ground-based range safety assets, to decrease range costs, and to decrease reaction time for special situations. The mission rules are configured for each operation by the responsible Range Safety authorities and can be loosely categorized in four major categories: Parameter Threshold Violations, Physical Boundary Violations present position and instantaneous impact point (TIP), Gate Rules static and dynamic, and a Green-Time Rule. Examples of each of these rules were evaluated during this aircraft test.
Simpson, James C.↗
Autonomous Flight Safety System Road Test
On February 3, 2005, Kennedy Space Center (KSC) conducted the first Autonomous Flight Safety System (AFSS) test on a moving vehicle -- a van driven around the KSC industrial area. A subset of the Phase III design was used consisting of a single computer, GPS receiver, and UPS antenna. The description and results of this road test are described in this report.AFSS is a joint KSC and Wallops Flight Facility project that is in its third phase of development. AFSS is an independent subsystem intended for use with Expendable Launch Vehicles that uses tracking data from redundant onboard sensors to autonomously make flight termination decisions using software-based rules implemented on redundant flight processors. The goals of this project are to increase capabilities by allowing launches from locations that do not have or cannot afford extensive ground-based range safety assets, to decrease range costs, and to decrease reaction time for special situations.
Simpson, James C.↗
Probabilistic Causal Analysis for System Safety Risk Assessments in Commercial Air Transport
Aviation is one of the critical modes of our national transportation system. As such, it is essential that new technologies be continually developed to ensure that a safe mode of transportation becomes even safer in the future. The NASA Aviation Safety Program (AvSP) is managing the development of new technologies and interventions aimed at reducing the fatal aviation accident rate by a factor of 5 by year 2007 and by a factor of 10 by year 2022. A portfolio assessment is currently being conducted to determine the projected impact that the new technologies and/or interventions may have on reducing aviation safety system risk. This paper reports on advanced risk analytics that combine the use of a human error taxonomy, probabilistic Bayesian Belief Networks, and case-based scenarios to assess a relative risk intensity metric. A sample case is used for illustrative purposes.
Luxhoj, James T.↗
System safety activities supporting an aero-space plane ground support technology
An overview is presented of the specific system safety activities required to support the ground support technology program associated with the design of an aerospace plane. Safe zones must be assessed to ensure that explosive safety requirements are attained to protect the vehicle, personnel, and support and operational facilities. Attention is given to the specific and unique design requirements connected with the utilization of cryogenic fuels as they apply to the design and development of an aerospace plane.
Mattern, Steven F.↗
Using computer graphics to enhance astronaut and systems safety
Computer graphics is being employed at the NASA Johnson Space Center as a tool to perform rapid, efficient and economical analyses for man-machine integration, flight operations development and systems engineering. The Operator Station Design System (OSDS), a computer-based facility featuring a highly flexible and versatile interactive software package, PLAID, is described. This unique evaluation tool, with its expanding data base of Space Shuttle elements, various payloads, experiments, crew equipment and man models, supports a multitude of technical evaluations, including spacecraft and workstation layout, definition of astronaut visual access, flight techniques development, cargo integration and crew training. As OSDS is being applied to the Space Shuttle, Orbiter payloads (including the European Space Agency's Spacelab) and future space vehicles and stations, astronaut and systems safety are being enhanced. Typical OSDS examples are presented. By performing physical and operational evaluations during early conceptual phases. supporting systems verification for flight readiness, and applying its capabilities to real-time mission support, the OSDS provides the wherewithal to satisfy a growing need of the current and future space programs for efficient, economical analyses.
Computer Simulation↗
Manned space flight nuclear system safety. Volume 7: Literature review. Part 1: Literature search and evaluation
A review of the literature used in conducting the manned space flight nuclear system safety study is presented. The objectives of the presentation are to identify and evaluate for potential application to study the existing related literature and to provide the information required to include the related literature in the NASA Aerospace Safety Research and Data Institute. More than 15,000 documents were evaluated and identification forms were prepared for 850 reports.
Source record↗
Comparative analysis of different configurations of PLC-based safety systems from reliability point of view
The study of a comparative analysis of distinct multiplex and fault-tolerant configurations for a PLC-based safety system from a reliability point of view is presented. It considers simplex, duplex and fault-tolerant triple redundancy configurations. The standby unit in case of a duplex configuration has a failure rate which is k times the failure rate of the standby unit, the value of k varying from 0 to 1. For distinct values of MTTR and MTTF of the main unit, MTBF and availability for these configurations are calculated. The effect of duplexing only the PLC module or only the sensors and the actuators module, on the MTBF of the configuration, is also presented. The results are summarized and merits and demerits of various configurations under distinct environments are discussed.
Tapia, Moiez A.↗
The practical application of mishap data in Army aircraft system safety programs
The means are discussed by which the the United States Army Board for Aviation Accident Research (USABAAR) now utilizes the vast store of historical accident data in the application of the system safety concept for developmental aircraft. USABAAR serves as the central agency for the Army Accident Prevention Program which includes the receipt, processing, and analysis of all data and information related to Army aircraft accident experience. It is pointed out that methods which served the cause of accident prevention so well in the past are no longer adequate and that traditional parameters used to measure mishap experience have become obsolete. USABAAR has developed, and recently put into use, completely revised accident reporting forms which greatly expand the scope and detail of information provided as a result of investigation. This and other factors which have resulted in an improved data system are discussed in detail.
James T. Darrah, Jr↗
System safety in Stirling engine development
The DOE/NASA Stirling Engine Project Office has required that contractors make safety considerations an integral part of all phases of the Stirling engine development program. As an integral part of each engine design subtask, analyses are evolved to determine possible modes of failure. The accepted system safety analysis techniques (Fault Tree, FMEA, Hazards Analysis, etc.) are applied in various degrees of extent at the system, subsystem and component levels. The primary objectives are to identify critical failure areas, to enable removal of susceptibility to such failures or their effects from the system and to minimize risk.
Bankaitis, H.↗
Configuration and Data Management Process and the System Safety Professional
This article presents a discussion of the configuration management (CM) and the Data Management (DM) functions and provides a perspective of the importance of configuration and data management processes to the success of system safety activities. The article addresses the basic requirements of configuration and data management generally based on NASA configuration and data management policies and practices, although the concepts are likely to represent processes of any public or private organization's well-designed configuration and data management program.
Shivers, Charles Herbert↗
Using computer graphics to enhance astronaut and systems safety
The Operator Station Design System (OSDS), a technique of applied computer graphics featuring a flexible interactive software package, is presented in terms of man-machine analyses, flight operations, and systems engineering. In man-machine analyses, the OSDS was used to determine if viewing from the Shuttle Remote Manipulator System was satisfactory and to identify requirements for a pallet-mounted television camera. In another study, extravehicular activity was analyzed using the example of emergency access to latches should they fail in orbit. In terms of flight operations, OSDS can be used to evaluate array monitoring of a solar array power system complex and to provide animated scenarios of mission operations. The most important application of OSDS is in relation to systems engineering, as OSDS can be used to analyze spacecraft and payload design and integration. Payload configurations are included.
Brown, J. W.↗
System safety as applied to Skylab
Procedural and organizational guidelines used in accordance with NASA safety policy for the Skylab missions are outlined. The basic areas examined in the safety program for Skylab were the crew interface, extra-vehicular activity (EVA), energy sources, spacecraft interface, and hardware complexity. Fire prevention was a primary goal, with firefighting as backup. Studies of the vectorcardiogram and sleep monitoring experiments exemplify special efforts to prevent fire and shock. The final fire control study included material review, fire detection capability, and fire extinguishing capability. Contractors had major responsibility for system safety. Failure mode and effects analysis (FMEA) and equipment criticality categories are outlined. Redundancy was provided on systems that were critical to crew survival (category I). The five key checkpoints in Skylab hardware development are explained. Skylab rescue capability was demonstrated by preparations to rescue the Skylab 3 crew after their spacecraft developed attitude control problems.
Kleinknecht, K. S.↗
System Safety and the Unintended Consequence
The analysis and identification of risks often result in design changes or modification of operational steps. This paper identifies the potential of unintended consequences as an over-looked result of these changes. Examples of societal changes such as prohibition, regulatory changes including mandating lifeboats on passenger ships, and engineering proposals or design changes to automobiles and spaceflight hardware are used to demonstrate that the System Safety Engineer must be cognizant of the potential for unintended consequences as a result of an analysis. Conclusions of the report indicate the need for additional foresight and consideration of the potential effects of analysis-driven design, processing changes, and/or operational modifications.
Watson, Clifford↗
Software System Safety and the NASA Aeronautics Blueprint
NASA's Aeronautics Blueprint lays out a research agenda for the Agency s aeronautics program. The word software appears only four times in this Blueprint, but the critical importance of safe and correct software to the fulfillment of the proposed research is evident on almost every page. Most of the technology solutions proposed to address challenges in aviation are software dependent technologies. Of the fifty-two specific technology solutions described in the Blueprint, forty-one depend, at least in part, on software for success. For thirty-five of these forty-one, software is not only critical to success, but also to human safety. That is, implementing the technology solutions will require using software in such a way that it may, if not specified, designed, and implemented properly, lead to fatal accidents. These results have at least two implications for the research based on the Blueprint: (1) knowledge about the current state-of-the-art and state-of-the-practice in software engineering and software system safety is essential, and (2) research into current unsolved problems in these software disciplines is also essential.
Holloway, C. Michael↗
Study report recommendations for the next generation Range Safety System (RSS) Integrated Receiver/Decoder (IRD)
The Integrated Receiver/Decoder (IRD) currently used on the Space Shuttle was designed in the 1980 and prior time frame. Over the past 12 years, several parts have become obsolete or difficult to obtain. As directed by the Marshall Space Flight Center, a primary objective is to investigate updating the IRD design using the latest technology subsystems. To take advantage of experience with the current designs, an analysis of failures and a review of discrepancy reports, material review board actions, scrap, etc. are given. A recommended new design designated as the Advanced Receiver/Decoder (ARD) is presented. This design uses the latest technology components to simplify circuits, improve performance, reduce size and cost, and improve reliability. A self-test command is recommended that can improve and simplify operational procedures. Here, the new design is contrasted with the old. Possible simplification of the total Range Safety System is discussed, as is a single-step crypto technique that can improve and simplify operational procedures.
Crosby, Robert H.↗