SEARCH · Engineering Papers
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.
Methodology is described for determining potential safety hazards involved in the construction and operation of photovoltaic power systems and provides guidelines for the implementation of safety considerations in the specification, design and operation of photovoltaic systems. Safety verification procedures for use in solar photovoltaic systems are established.
The System-Wide Safety project at NASA is developing the concept and a subset of supporting technologies for evolving safety management from a post-accident iterative improvement on safety performed by large commercial operators only to predictive and increasingly autonomous safety functions that are performed during operations across vehicles, airports, and services. The system of interest is the In-time Aviation Safety Management System (IASMS), recommended by the National Academies for NASA to develop the concept in coordination with the broad and diverse community of stakeholders in aviation safety. Because the system context is the airspace and aviation industry, it is important to create and maintain traceability from the research work and system architecture elements developed at NASA to community-created roadmaps and aviation agency guidance.
The integration of unmanned aerial vehicles in the national airspace will introduce new vehicle types, technologies, and operational paradigms for which safety must be maintained and hazards mitigated. One approach is to attempt to design for possible hazards and unsafe incidents that can occur at different phases of flight (pre-flight, in-flight, and post-flight) and during ground operations. Another is to mitigate safety incidents by implementing changes to policies, procedures, regulations, and design to cover personnel, equipment, and aircraft during operations. These and other techniques, not described herein, are typically conservative or adhoc in that they reduce the likelihood of risk after safety incidents have occurred. In this work, the goal is to develop a more predictive capability to monitor and mitigate risk and hazards to safety “in-time” enough for decisions to be made. In line with NASA’s Aeronautics Mission Directorate Strategic Thrust 5 [1] (In-Time System-Wide Safety Assurance), the System-Wide Safety (SWS) project under which this work falls, is developing and demonstrating innovative and safety-oriented solutions that enable modernization and aviation transformation. To that effect, this work will detail data-driven efforts on the SWS project to develop a number of safety-critical services for in-time monitoring and mitigation of hazards to low-altitude flight operations. First, hazards to these operations are identified based on previous work by NASA [2,3] and others in the aerospace industry. These hazards include (i) unsafe proximity to other vehicles, property, and people on the ground, (ii) critical system failures such as communication signal/GPS loss, unexpected propulsion system degradation, engine/power failure, and (iii) operational/environmental issues such as severe weather and gusty winds. For these hazards, safety metrics, which can be quantified and assessed are defined, models to monitor and predict them are developed, and flight test data is generated to develop, validate, and test these models, considering the complex interplay of the different hazards that define them [4-6]. In addition, the uncertainty in the non-deterministic effects that cannot be modeled nor predicted and unknown unknowns that arise after design/testing and during operations must be handled in rigorous manner. As a result, for each of the developed safety metrics, their dependencies on one another are characterized and a framework for handling the uncertainties inherent in the modeling, algorithms, and measurements required for prediction is also developed [7]. To that effect, this presentation will describe the safety metrics and services already developed and underway under the System-Wide Safety project that utilize data-driven techniques for the identification of anomalies, precursors, and trends (APTs) to monitor and mitigate hazards to safety, in-time, for urban flight operations in low-altitude airspace.
Risk analysis and integrated verification and validation are two important elements in a plan for ensuring the safety of critical software systems. We describe an approach we are currently developing for integrating risk analysis, and metrics analysis, and propose a fault predictor that would integrate the results of these activities. Practical difficulties associated with our approach are also discussed, as are limitations of the proposed predictor. We conclude with a discussion of what as been learned to date, and with suggestions for future work.
Adoption of commercial off-the-shelf (COTS) products in safety critical systems has been seen as a promising acquisition strategy to improve mission affordability and, yet, has come with significant barriers and challenges. Attempts to integrate COTS software components into NASA human rated flight systems have been, for the most part, complicated by verification and validation (V&V) requirements necessary for flight certification per NASA s own standards. For software that is from COTS sources, and, in general from 3rd party sources, either commercial, government, modified or open source, the expectation is that it meets the same certification criteria as those used for in-house and that it does so as if it were built in-house. The latter is a critical and hidden issue. This paper examines the longstanding barriers and challenges in the use of 3rd party software in safety critical systems and cover recent efforts to use COTS software in NASA s Multi-Purpose Crew Vehicle (MPCV) project. It identifies some core artifacts that without them, the use of COTS and 3rd party software is, for all practical purposes, a nonstarter for affordable and timely insertion into flight critical systems. The paper covers the first use in a flight critical system by NASA of COTS software that has prior FAA certification heritage, which was shown to meet the RTCA-DO-178B standard, and how this certification may, in some cases, be leveraged to allow the use of analysis in lieu of testing. Finally, the paper proposes the establishment of an open source forum for development of safety critical 3rd party software.
An In-time Aviation Safety Management System (IASMS) [1,2] is a set of services, functions, and capabilities (SFCs) necessary for monitoring known hazards and emergent risks, assessing safety data for anomalies, precursors, and trends, mitigating hazards that reach safety thresholds, and assuring efficacy of controls in mitigating hazards. An IASMS will continually monitor the NAS to collect data on the status of aircraft, air traffic management systems, weather, and airports. Within the NASA Aeronautics Research Mission Directorate (ARMD) System-Wide Safety (SWS) project’s technical challenge called In-time Aviation Safety Management Systems (IASMS) for Commercial Aviation Operations, which we often refer to as Technical Challenge 6 (TC-6), we have performed an assessment of several aviation data sources we have found that are relevant to assessing the safety of the National Airspace System (NAS) in the context of an IASMS. This assessment includes understanding the nature of the data themselves and using some data analytics tools on these data to show how they can be used to identify potential safety issues. We also describe how the data and analytics are part of a system that can allow for other data and analytics to be performed and for the results to be visualized for use by appropriate operators to identify potential safety issues and develop mitigations. This report is a step toward the ultimate goal of TC-6, which is to develop a prototype IASMS system that demonstrates the potential of an IASMS and inspire operators to build analogous systems to make the best possible use of the significant investments that they make in collecting, storing, and managingdata related to their operations.
The Runway Safety Monitor (RSM) designed by Lockheed Martin is part of NASA's effort to reduce aviation accidents. We developed a Petri net model of the RSM protocol and used the model checking functions of our tool SMART to investigate a number of safety properties in RSM. To mitigate the impact of state-space explosion, we built a highly discretized model of the system, obtained by partitioning the monitored runway zone into a grid of smaller volumes and by considering scenarios involving only two aircraft. The model also assumes that there are no communication failures, such as bad input from radar or lack of incoming data, thus it relies on a consistent view of reality by all participants. In spite of these simplifications, we were able to expose potential problems in the RSM conceptual design. Our findings were forwarded to the design engineers, who undertook corrective action. Additionally, the results stress the efficiency attained by the new model checking algorithms implemented in SMART, and demonstrate their applicability to real-world systems. Attempts to verify RSM with NuSMV and SPIN have failed due to excessive memory consumption.
Demonstration of required safety margins on critical electrical/electronic circuits in large complex systems has become an implementation and cost problem. These margins are the difference between the activation level of the circuit and the electrical noise on the circuit in the actual operating environment. This document discusses the origin of the requirement and gives a detailed process flow for the identification of the system electromagnetic compatibility (EMC) critical circuit list. The process flow discusses the roles of engineering disciplines such as systems engineering, safety, and EMC. Design and analysis guidelines are provided to assist the designer in assuring the system design has a high probability of meeting the margin requirements. Examples of approaches used on actual programs (Skylab and Space Shuttle Solid Rocket Booster) are provided to show how variations of the approach can be used successfully.
Topics dealing with nuclear safety are addressed which include the following: general safety requirements; safety design requirements; terrestrial safety; SP-100 Flight System key safety requirements; potential mission accidents and hazards; key safety features; ground operations; launch operations; flight operations; disposal; safety concerns; licensing; the nuclear engine for rocket vehicle application (NERVA) design philosophy; the NERVA flight safety program; and the NERVA safety plan.
Explore the source record for details and available documents.
Decades of systems engineering practice have demonstrated that the earlier the identification of requirements occurs, the lower the chance that costly redesigns will needed later in the project life cycle. A better understanding of all requirements can also improve the likelihood of a design's success. Significant effort has been put into developing tools and practices that facilitate requirements determination, including those that are part of the model-based systems engineering (MBSE) paradigm. These efforts have yielded improvements in requirements definition, but have thus far focused on a design's performance needs. The identification of safety & mission assurance (S&MA) related requirements, in comparison, can occur after preliminary designs are already established, yielding forced redesigns. Engaging S&MA expertise at an earlier stage, facilitated by the use of MBSE tools, and focused on actual project risk, can yield the same type of design life cycle improvements that have been realized in technical and performance requirements.
This presentation provides an overview of NASA's Aviation Safety Reporting System (ASRS) for Unmanned Aviation Systems / drones
This paper describes the concepts and features of a fault-tolerant intelligent robotic control system being developed for applications that require high dependability (reliability, availability, and safety). The system consists of two major elements: a fault-tolerant controller and an operator workstation. The fault-tolerant controller uses a strategy which allows for detection and recovery of hardware, operating system, and application software failures.The fault-tolerant controller can be used by itself in a wide variety of applications in industry, process control, and communications. The controller in combination with the operator workstation can be applied to robotic applications such as spaceborne extravehicular activities, hazardous materials handling, inspection and maintenance of high value items (e.g., space vehicles, reactor internals, or aircraft), medicine, and other tasks where a robot system failure poses a significant risk to life or property.
This report presents an example of the application of multi-criteria decision analysis to the selection of an architecture for a safety-critical distributed computer system. The design problem includes constraints on minimum system availability and integrity, and the decision is based on the optimal balance of power, weight and cost. The analysis process includes the generation of alternative architectures, evaluation of individual decision criteria, and the selection of an alternative based on overall value. In this example presented here, iterative application of the quantitative evaluation process made it possible to deliberately generate an alternative architecture that is superior to all others regardless of the relative importance of cost.
There is broad recognition that the high tempo and density of Urban Air Mobility (UAM) operations will require identifying new Air Traffic Management (ATM) concepts to safely integrate UAM air traffic into the airspace alongside existing air traffic. However, the simulation models used to compare ATM concepts today are difficult to apply during the early stages of concept development and do not offer enough support in identifying potential new concepts. In addition, they have limited ability to evaluate ATM concepts in terms of safety, security, and other key emergent properties. Instead of using simulation to evaluate ATM concepts, this paper demonstrates how a safety-driven systems engineering approach based on Systems-Theoretic Accident Model and Processes (STAMP) can be used to design properties such as safety into an ATM system from the earliest stages of development. Using a hazard analysis technique called Systems-Theoretic Process Analysis (STPA), system requirements and the desired ATM behavior are derived. As an example, two possible ATM concepts to implement that behavior are compared to identify their safety-related benefits and tradeoffs. This new approach enables (1) systematic exploration of alternative ATM concepts and (2) identification of the safety-related tradeoffs between concepts as early as possible in the development process.
The inability to establish appropriate assurance methods for AI/ML components in safety critical systems leaves us unable to effectively manage the risks and benefits of such systems. It drives cost of development for systems with AI/ML components uneconomically high, it delays the adoption of systems with AI/ML components at scale, and it can result in catastrophic consequences in terms of the safety of systems with AI/ML components. In this presentation we will explore what constitutes sufficient scientific-based evidence to substantiate a safety claim related to an AI/ML component performing a safety-critical function.
This report presents a high-level overview of a general strategy to mitigate the risks from threats to safety-critical computer-based systems. In this context, a safety threat is a process or phenomenon that can cause operational safety hazards in the form of computational system failures. This report is intended to provide insight into the safety-risk mitigation problem and the characteristics of potential solutions. The limitations of the general risk mitigation strategy are discussed and some options to overcome these limitations are provided. This work is part of an ongoing effort to enable well-founded assurance of safety-related properties of complex safety-critical computer-based aircraft systems by developing an effective capability to model and reason about the safety implications of system requirements and design.
The basic ability of STARS to maintain a satellite communications link with TDRSS satellites during dynamic aircraft flights was successfully demonstrated during FD 1. The Range Safety and Range User systems' link margins were measured. The ability to acquire/reacquire and maintain lock between a high-dynamic vehicle and a satellite-based system was demonstrated. The Range Safety system simultaneously received and processed command links from space and ground transmitters and provided near real-time Range Safety telemetry to DFRC, which then sent it in near real time to KSC, GSFC, and WFF for monitoring. The GPS receiver maintained track except during extremely dynamic maneuvers. The Range User system sent data at three different data rates. There were excellent cooperation and support from the different Centers, contractors, and Ranges. A large amount of data was recorded and extensive post-flight analysis was performed. The Range User TDRSS link margin met or exceeded the predicted performance at three different data rates. The Range Safety launch-head link margins generally agreed with the predicted performance. The UPS positions and velocities agreed with those from tracking radar to within about 20 m and a few rn/s. The link margins for the Range Safety TDRSS telemetry link were less than expected. The link margin for one TDRSS command link LPT channel was occasionally much less than the other. Additional post-flight testing has yet to identify the root causes of these results. There were many lessons learned from this first set of test flights. The most important one is that more time and testing are needed for each step to deal with the inevitable problems. It is vital that these lessons be among the primary areas of study that will carry over from FD#1 to FD#2, which is currently scheduled for early FY05 at DFRC and will use a specially designed Ku-band phased array antenna for the Range User system. The next series of flight demonstrations scheduled for late 2004 at DFRC will incorporate many lessons learned from FD#1. A specially designed Ku-band phased array antenna will be used with the Range User system. A test flight on a hypersonic vehicle is planned by the end of 2006.