Search NASA⌕ Search

SEARCH · Search NASA

Results for “safety requirements”

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 91 records · Page 5

High Flux Isotope Reactor Low-Enriched Uranium Low Density Silicide Fuel Design Parameters

High Flux Isotope Reactor (HFIR) highly enriched uranium (HEU) to low-enriched uranium (LEU) conversion activities are ongoing as part of the Department of Energy (DOE) National Nuclear Security Administration (NNSA)’s nuclear nonproliferation mission. Design activities studying the conversion of HFIR from HEU to LEU fuel explored different fuel design features and shapes with a low density uranium-silicide dispersion (U 3 Si 2 -Al) fuel, which has a uranium density of 4.8 gU/cm 3 . The goal of these studies is to generate several HFIR LEU fuel designs of varying fuel fabrication complexity that meet the current HEU performance metrics and safety requirements. The documented designs will serve as references for fuel fabrication and qualification activities. Recent advancements in modeling and simulation tools enable quick prototyping of fuel designs. Shift, a Monte Carlo neutron transport and depletion tool optimized for high-performance computing (HPC) architectures, is used for efficient fuel cycle and performance metrics calculations. The HFIR Steady State Heat Transfer Code (HSSHTC) is used to vet the thermal safety margin. Also, a new automation tool that connects all fuel design analysis steps, named Python HFIR Analysis and Measurement Engine (PHAME), has been developed to expedite the design study in an efficient and reproducible manner. Leveraging these tools, several candidate fuel designs were selected for varying fabrication complexity. This report provides design feature details for four selected HFIR LEU low density U 3 Si 2 -Al fuel designs and their corresponding performance and safety metrics. Nominal, best-estimate design parameters and irradiation conditions, including fission rate densities, power densities, heat fluxes, and cumulative fission densities are provided for candidate fuel designs relevant to framing irradiation experiments to support fuel qualification efforts. Simulations show that the low density U 3 Si 2 -Al, with design features to enhance safety, can meet HEU core performance metrics and safety requirements if the reactor power is increased from 85 MW (HEU) to 95 MW (LEU) and if the active fuel length is increased from 50.80 cm (HEU) to 55.88 cm (LEU).

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

MODULARITY-AT-SCALE FOR COST COMPETITIVE DEPLOYMENT OF NUCLEAR ENERGY

Modularity options have been limited for traditional nuclear energy deployment due to the conventional light water reactor (LWR) safety requirements, such as high pressure retaining heavy and robust containment structures. However, a relatively new regulatory approach called ‘Functional Containment’ has potential to allow less expensive and more flexible designs for non LWRs. Functional containment provides flexibility in design and deployment based on risk informed and performance-based criteria, so that reactors are not over-designed. Non-nuclear industry has successfully used modular design approaches in automotive, aerospace, chemical processing, building construction, and ship building. These industries have shown that modular construction reduces construction time by around 30% - 50% compared to the conventional stick built approach. The nuclear industry can use similar approaches to reduce construction time and costs, balanced with safety requirements, using the functional containment approach. This paper discussing the background of modularity in nuclear energy, examples of less learned, modularity approaches in non-nuclear industries and the potential of cost and schedule savings through the emerging regulatory design flexibilities potentially enabling combination of modular deployment at different scales.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Modularity-at-scale for advanced reactors presentation

Modularity options have been limited for traditional nuclear energy deployment due to the conventional light water reactor (LWR) safety requirements, such as high pressure retaining heavy and robust containment structures. However, a relatively new regulatory approach called ‘Functional Containment’ has potential to allow less expensive and more flexible designs for non-LWRs. Functional containment provides flexibility in design and deployment based on risk-informed and performance-based criteria, so that reactors are not over-designed. Non-nuclear industry has successfully used modular design approaches in automotive, aerospace, chemical processing, building construction, and ship building. These industries have shown that modular construction reduces construction time by around 30% - 50% compared to the conventional stick-built approach. The nuclear industry can use similar approaches to reduce construction time and costs, balanced with safety requirements, using the functional containment approach. This paper discussing the background of modularity in nuclear energy, examples of less learned, modularity approaches in non-nuclear industries and the potential of cost and schedule savings through the emerging regulatory design flexibilities potentially enabling combination of modular deployment at different scales.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

High Flux Isotope Reactor Low Enriched Uranium U-10Mo Fuel Design Parameters

Activities to convert the HFIR from HEU to LEU are ongoing as part of the US Department of Energy (DOE) National Nuclear Security Administration (NNSA) nuclear nonproliferation mission. Design activities to study the conversion of HFIR from HEU to LEU fuel explored different fuel design features and shapes with a uranium-molybdenum (U-10Mo) monolithic alloy fuel. This high-density alloy contains 90 wt % uranium and 10 wt % molybdenum and has a uranium density of 15.318gU/cm 3 . The goal of these studies is to generate several candidate HFIR LEU fuel designs of varying fuel fabrication complexity that meet the current HEU performance metrics and safety requirements. Recent advancements in modeling and simulation tools and design methods enabled a thorough analysis of the available design space with U-10Mo fuel. A surrogate model used this analysis as training data to quickly determine the performance of a design given specific design parameters. An optimization module used this surrogate model to quickly search this multidimensional search space given specific desired performance characteristics. This approach was made possible by the large available design space with U-10Mo fuel. Shift, a Monte Carlo tool optimized for high-performance computing (HPC) architectures, was used for faster calculation and better data management for reactor physics simulations. Once most of these design studies were complete, a new suite called the Python HFIR Analysis and Measurement Engine (PHAME) was developed to connect all fuel design analysis steps, making design studies more efficient and reproducible. The post-processing capabilities of these new tools are leveraged for the information provided herein. Leveraging these tools, several candidate fuel designs were selected with varying levels of feature complexity and reactor performance. This report provides design feature details for four selected HFIR LEU U-10Mo fuel designs and their corresponding performance and safety metrics. Nominal best-estimate design parameters and irradiation conditions, including fission rate densities, power densities, heat fluxes, and cumulative fission densities, are provided. Simulations show that the high uranium density of U-10Mo fuel provides a large potential design space that enables various LEU designs to meet HEU core performance metrics and safety requirements with a power increase from 85 MW (HEU) to 95 MW or 100 MW (LEU).

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Design for an integrated discipline operations control center for Space Station Freedom

This paper presents selected features of a human factors oriented plan for a Space Station Freedom (SSF) ground Discipline Operations Center (DOC) that is integrated with other work areas used by multidisciplinary life scientists. This combined facility is referred to as an integrated DOC or IDOC. This plan is based upon the assumption that there will be a constantly changing array of specialized equipment and procedures used by life sciences principal investigators (PI) on the ground which must be linked to SSF through various DOC systems. Other sites will also be able to communicate with SSF (Anon., 1992). It is also assumed that cost reduction will be a major design consideration and that one integrated structure will be less expensive to build and operate than two separate ones. Since both the DOC personnel and PIs will need to communicate with the flight crew aboard SSF, the general interconnect architecture of the PIs' communication linkage is considered here. Key human factor design elements of this plan include: a candidate facility layout which accommodates three (3), multipurpose, rapidly reconfigurable work areas (suites) and consequent user traffic flow considerations, a multimedia telecommunications support capability, functional (human) traffic flow, optimized internal illumination and acoustics requirements, selected volumetric and safety requirements, and other architectural design parameters.

Haines, Richard F.↗

From Informal Safety-Critical Requirements to Property-Driven Formal Validation

Most of the efforts in formal methods have historically been devoted to comparing a design against a set of requirements. The validation of the requirements themselves, however, has often been disregarded, and it can be considered a largely open problem, which poses several challenges. The first challenge is given by the fact that requirements are often written in natural language, and may thus contain a high degree of ambiguity. Despite the progresses in Natural Language Processing techniques, the task of understanding a set of requirements cannot be automatized, and must be carried out by domain experts, who are typically not familiar with formal languages. Furthermore, in order to retain a direct connection with the informal requirements, the formalization cannot follow standard model-based approaches. The second challenge lies in the formal validation of requirements. On one hand, it is not even clear which are the correctness criteria or the high-level properties that the requirements must fulfill. On the other hand, the expressivity of the language used in the formalization may go beyond the theoretical and/or practical capacity of state-of-the-art formal verification. In order to solve these issues, we propose a new methodology that comprises of a chain of steps, each supported by a specific tool. The main steps are the following. First, the informal requirements are split into basic fragments, which are classified into categories, and dependency and generalization relationships among them are identified. Second, the fragments are modeled using a visual language such as UML. The UML diagrams are both syntactically restricted (in order to guarantee a formal semantics), and enriched with a highly controlled natural language (to allow for modeling static and temporal constraints). Third, an automatic formal analysis phase iterates over the modeled requirements, by combining several, complementary techniques: checking consistency; verifying whether the requirements entail some desirable properties; verify whether the requirements are consistent with selected scenarios; diagnosing inconsistencies by identifying inconsistent cores; identifying vacuous requirements; constructing multiple explanations by enabling the fault-tree analysis related to particular fault models; verifying whether the specification is realizable.

Cimatti, Alessandro↗

Automating the Generation of Heterogeneous Aviation Safety Cases

A safety case is a structured argument, supported by a body of evidence, which provides a convincing and valid justification that a system is acceptably safe for a given application in a given operating environment. This report describes the development of a fragment of a preliminary safety case for the Swift Unmanned Aircraft System. The construction of the safety case fragment consists of two parts: a manually constructed system-level case, and an automatically constructed lower-level case, generated from formal proof of safety-relevant correctness properties. We provide a detailed discussion of the safety considerations for the target system, emphasizing the heterogeneity of sources of safety-relevant information, and use a hazard analysis to derive safety requirements, including formal requirements. We evaluate the safety case using three classes of metrics for measuring degrees of coverage, automation, and understandability. We then present our preliminary conclusions and make suggestions for future work.

Denney, Ewen W.↗

Bayesian Inference for NASA Probabilistic Risk and Reliability Analysis

This document, Bayesian Inference for NASA Probabilistic Risk and Reliability Analysis, is intended to provide guidelines for the collection and evaluation of risk and reliability-related data. It is aimed at scientists and engineers familiar with risk and reliability methods and provides a hands-on approach to the investigation and application of a variety of risk and reliability data assessment methods, tools, and techniques. This document provides both: A broad perspective on data analysis collection and evaluation issues. A narrow focus on the methods to implement a comprehensive information repository. The topics addressed herein cover the fundamentals of how data and information are to be used in risk and reliability analysis models and their potential role in decision making. Understanding these topics is essential to attaining a risk informed decision making environment that is being sought by NASA requirements and procedures such as 8000.4 (Agency Risk Management Procedural Requirements), NPR 8705.05 (Probabilistic Risk Assessment Procedures for NASA Programs and Projects), and the System Safety requirements of NPR 8715.3 (NASA General Safety Program Requirements).

Dezfuli, Homayoon↗

Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems

When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEJ Software Development Risk Taxonomy [4] focuses on general software development issues. It does not, however, cover all the safety risks. The Software Safety Risk Taxonomy [8] was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a Software Safety Risk Taxonomy Based Questionnaire (TBQ) is generated containing questions addressing each safety attribute in the Software Safety Risk Taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized Product Engineering Class within the Software Safety Risk Taxonomy. At the end of the paper, we present the tool known as the 'Legacy Systems Risk Database Tool' that is used to collect and analyze the data required to show traceability to a particular safety standard

Hill, Janice↗

The NASA Commercial Crew Program (CCP) Mission Assurance Process

In 2010, NASA established the Commercial Crew Program in order to provide human access to the International Space Station and low earth orbit via the commercial (non-governmental) sector. A particular challenge to NASA has been how to determine the commercial providers transportation system complies with Programmatic safety requirements. The process used in this determination is the Safety Technical Review Board which reviews and approves provider submitted Hazard Reports. One significant product of the review is a set of hazard control verifications. In past NASA programs, 100 percent of these safety critical verifications were typically confirmed by NASA. The traditional Safety and Mission Assurance (SMA) model does not support the nature of the Commercial Crew Program. To that end, NASA SMA is implementing a Risk Based Assurance (RBA) process to determine which hazard control verifications require NASA authentication. Additionally, a Shared Assurance Model is also being developed to efficiently use the available resources to execute the verifications. This paper will describe the evolution of the CCP Mission Assurance process from the beginning of the Program to its current incarnation. Topics to be covered include a short history of the CCP; the development of the Programmatic mission assurance requirements; the current safety review process; a description of the RBA process and its products and ending with a description of the Shared Assurance Model.

Commercial Crew Program↗

Safety in earth orbit study

Safety aspects are studied of the space shuttle orbiter, the shuttle payloads, and space stations in earth orbital operations. The tasks generated safety requirements, guidelines, recommendations, and conceptual safety devices. The tasks studied were: hazardous payloads, docking, onboard survivability tumbling spacecraft, and escape and rescue operations.

Source record↗

Development of CO2 laser Doppler instrumentation for detection of clear air turbulence, volume 2: Appendices

Analyses of the mounting and mount support systems of the clear air turbulence transmitters verify that satisfactory shock and vibration isolation are attained. The mount support structure conforms to flight crash safety requirements with high margins of safety. Restraint cables reinforce the mounts in the critical loaded forward direction limiting maximum forward system deflection to 1 1/4 inches.

Harris, C. E.↗

Hybrid propulsion technology program: Phase 1, volume 2

The program objectives of developing hybrid propulsion technology (HPT) to enable its application for manned and unmanned high thrust, high performance space launch vehicles are examined. The studies indicate that the hybrid propulsion (HP) is very attractive, especially when applied to large boosters for programs such as the Advanced Launch System (ALS) and the second generation Space Shuttle. Some of the advantages of HP are identified. Space launch vehicles using HP are less costly than those flying today because their propellant and insulation costs are much less and there are fewer operational restraints due to reduced safety requirements. Boosters using HP have safety features that are highly desirable, particularly for manned flights. HP systems will have a clean exhaust and high performance. Boosters using HP readily integrate with launch vehicles and their launch operations, because they are very compact for the amount of energy contained. Hybrid propulsion will increase the probability of mission success. In order to properly develop the technologies of HP, preliminary HP concepts are evaluated. System analyses and trade studies were performed to identify technologies applicable to HP.

Schuler, A. L.↗

Achieving the Proper Balance Between Crew and Public Safety

A paramount objective of all human-rated launch and reentry vehicle developers is to ensure that the risks to both the crew onboard and the public are minimized within reasonable cost, schedule, and technical constraints. Past experience has shown that proper attention to range safety requirements necessary to ensure public safety must be given early in the design phase to avoid additional operational complexities or threats to the safety of people onboard. This paper will outline the policy considerations, technical issues, and operational impacts regarding launch and reentry vehicle failure scenarios where crew and public safety are intertwined and thus addressed optimally in an integrated manner. Historical examples and lessons learned from both the Space Shuttle and Constellation Programs will be presented. Using these examples as context, the paper will discuss some operational, design, and analysis approaches to mitigate and balance the risks to people onboard and in the public. Manned vehicle perspectives from the FAA and Air Force organizations that oversee public safety will also be summarized. Finally, the paper will emphasize the need to factor policy, operational, and analysis considerations into the early design trades of new vehicles to help ensure that both crew and public safety are maximized to the greatest extent possible.

Gowan, John↗

Can Cell to Cell Thermal Runaway Propagation be Prevented in a Li-ion Battery Module?

Increasing cell spacing decreased adjacent cell damage center dotElectrically connected adjacent cells drained more than physically adjacent cells center dotRadiant barrier prevents propagation when fully installed between BP cells center dotBP cells vent rapidly and expel contents at 100% SOC -Slower vent with flame/smoke at 50% -Thermal runaway event typically occurs at 160 degC center dotLG cells vent but do not expel contents -Thermal runaway event typically occurs at 200 degC center dotSKC LFP modules did not propagate; fuses on negative terminal of cell may provide a benefit in reducing cell to cell damage propagation. New requirement in NASA-Battery Safety Requirements document: JSC 20793 Rev C 5.1.5.1 Requirements - Thermal Runaway Propagation a. For battery designs greater than a 80-Wh energy employing high specific energy cells (greater than 80 watt-hours/kg, for example, lithium-ion chemistries) with catastrophic failure modes, the battery shall be evaluated to ascertain the severity of a worst-case single-cell thermal runaway event and the propensity of the design to demonstrate cell-to-cell propagation in the intended application and environment. NASA has traditionally addressed the threat of thermal runaway incidents in its battery deployments through comprehensive prevention protocols. This prevention-centered approach has included extensive screening for manufacturing defects, as well as robust battery management controls that prevent abuse-induced runaway even in the face of multiple system failures. This focused strategy has made the likelihood of occurrence of such an event highly improbable. b. The evaluation shall include all necessary analysis and test to quantify the severity (consequence) of the event in the intended application and environment as well as to identify design modifications to the battery or the system that could appreciably reduce that severity. In addition to prevention protocols, programs developing battery designs with catastrophic failure modes should take the steps necessary to assess the severity of a possible thermal runaway event. Programs should assess whether there are reasonable design changes that could appreciably affect the severity of the outcome. Evaluation should include environmental effects to surrounding hardware (i.e., temperature, pressure, shock), contamination effects due to any expelled contaminates, and venting propulsive effects when venting overboard.

Jeevarajan, Judith↗

Power Goals for NASA's Exploration Program

Exciting Future Programs ahead for NASA. Power is needed for all Exploration vehicles and for the missions. For long term missions as in Lunar and Mars programs, safe, high energy/ultra high energy batteries are required. Safety is top priority for human-rated missions. Two-fault tolerance to catastrophic failures is required for human-rated safety To meet power safety goals -inherent cell safety may be required; it can lessen complexity of external protective electronics and prevents dependency on hardware that may also have limitations. Inherent cell safety will eliminate the need to carry out screening of all cells (X-rays, vibration, etc.)

Jeevarajan, Judith A.↗