SEARCH · Engineering Papers

Results for “risk informed design”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 577 records · Page 32

All sources NASA NTRS DOE OSTI

DOE OSTI2023

High-Reliability Systems and the Control of National Security Data and Information

High-reliability systems are characterized by catastrophic implications in the event of failure. These implications can include substantive damage to the environment, social order, and loss of life. Examples of high-reliability systems include nuclear submarines, nuclear reactors, the electric grid, and nuclear weapons. Due to the catastrophic implications of failure, there are heightened awareness and control mechanisms surrounding related data and information. However, defining the difference between data and information is often ambiguous across scholarly disciplines and in United States policy and legislation. For high-reliability systems, the implications of ambiguity between data and information may affect the security of United States interests and even cost lives. For security, data are raw facts or figures without context, while information is the compilation or articulation of data that forms context. Security depends on clarity in the differences between data and information and how to control them. Control is necessary to ensure that data and information are not unintentionally released to foreign governments, the public, or those without need-to-know. A primary concern in the practice of security is the control of data to avoid the unintended conversion to information. Intra-institutionally, this control is highly complex given the amalgam of legacy data systems and the numerous and constantly evolving nature of modern data systems that were not necessarily designed to be integrated. The complexity of this concern is augmented when institutions are part of interinstitutional collaborations or networks of public-private partnerships that share data and information. Additionally, institutions that share data as a function of policy and legislative action— particularly formally integrated data and information system infrastructures—may be at higher security risk. This paper will present an intra-institutional paradigm that utilizes and integrates concepts from numerous disciplines to frame a critical and underspecified practical issue in security—controlling for the unintended conversion of data to information.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

DOE OSTI2020

Empirical Study of Effect of Dynamic Travel Time Information on Driver Route Choice Behavior

The objective of this paper is to study the effect of travel time information on day-to-day driver route choice behavior. A real-world experimental study is designed to have participants repeatedly choose between two alternative routes for five origin-destination pairs over multiple days after providing them with dynamically updated travel time information (average travel time and travel time variability). The results demonstrate that historical travel time information enhances behavioral rationality by 10% on average and reduces inertial tendencies to increase risk seeking in the gain domain. Furthermore, expected travel time information is demonstrated to be more effective than travel time variability information in enhancing rational behavior when drivers have limited experiences. After drivers gain sufficient knowledge of routes, however, the difference in behavior associated with the two information types becomes insignificant. The results also demonstrate that, when drivers lack experience, the faster less reliable route is more attractive than the slower more reliable route. However, with cumulative experiences, drivers become more willing to take the more reliable route given that they are reluctant to become risk seekers once experience is gained. Furthermore, the effect of information on driver behavior differs significantly by participant and trip, which is, to a large extent, dependent on personal traits and trip characteristics.

99 GENERAL AND MISCELLANEOUS↗

NASA NTRS2001

Team Expo: A State-of-the-Art JSC Advanced Design Team

In concert with the NASA-wide Intelligent Synthesis Environment Program, the Exploration Office at the Johnson Space Center has assembled an Advanced Design Team. The purpose of this team is two-fold. The first is to identify, use, and develop software applications, tools, and design processes that streamline and enhance a collaborative engineering environment. The second is to use this collaborative engineering environment to produce conceptual, system-level-of-detail designs in a relatively short turnaround time, using a standing team of systems and integration experts. This includes running rapid trade studies on varying mission architectures, as well as producing vehicle and/or subsystem designs. The standing core team is made up of experts from all of the relevant engineering divisions (e.g. Power, Thermal, Structures, etc.) as well as representatives from Risk and Safety, Mission Operations, and Crew Life Sciences among others. The Team works together during 2- hour sessions in the same specially enhanced room to ensure real-time integration/identification of cross-disciplinary issues and solutions. All subsystem designs are collectively reviewed and approved during these same sessions. In addition there is an Information sub-team that captures and formats all data and makes it accessible for use by the following day. The result is Team Expo: an Advanced Design Team that is leading the change from a philosophy of "over the fence" design to one of collaborative engineering that pushes the envelope to achieve the next-generation analysis and design environment.

Tripathi, Abhishek↗

NASA NTRS2012

A Bayesian Framework for Reliability Analysis of Spacecraft Deployments

Deployable subsystems are essential to mission success of most spacecraft. These subsystems enable critical functions including power, communications and thermal control. The loss of any of these functions will generally result in loss of the mission. These subsystems and their components often consist of unique designs and applications for which various standardized data sources are not applicable for estimating reliability and for assessing risks. In this study, a two stage sequential Bayesian framework for reliability estimation of spacecraft deployment was developed for this purpose. This process was then applied to the James Webb Space Telescope (JWST) Sunshield subsystem, a unique design intended for thermal control of the Optical Telescope Element. Initially, detailed studies of NASA deployment history, "heritage information", were conducted, extending over 45 years of spacecraft launches. This information was then coupled to a non-informative prior and a binomial likelihood function to create a posterior distribution for deployments of various subsystems uSing Monte Carlo Markov Chain sampling. Select distributions were then coupled to a subsequent analysis, using test data and anomaly occurrences on successive ground test deployments of scale model test articles of JWST hardware, to update the NASA heritage data. This allowed for a realistic prediction for the reliability of the complex Sunshield deployment, with credibility limits, within this two stage Bayesian framework.

Evans, John W.↗

NASA NTRS2011

The Near Earth Asteroid Medical Conditions List

Purpose: The Exploration Medical Capability (ExMC) element is one of six elements within NASA s Human Research Program (HRP) and is responsible for addressing the risk of "the inability to adequately recognize or treat an ill or injured crewmember" for exploration-class missions. The Near Earth Asteroid (NEA) Medical Conditions List, constructed by ExMC, is the first step in addressing the above-mentioned risk for the 13-month long NEA mission. The NEA mission is being designed by NASA's Human Space Flight Architecture Team (HAT). The purpose of the conditions list is to serve as an evidence-based foundation for determining which medical conditions could affect a crewmember during the NEA mission, which of those conditions would be of concern and require treatment, and for which conditions a gap in knowledge or technology development exists. This information is used to focus research efforts and technology development to ensure that the appropriate medical capabilities are available for exploration-class missions. Scope and Approach: The NEA Medical Conditions List is part of a broader Space Medicine Exploration Medical Conditions List (SMEMCL), which incorporates various exploration-class design reference missions (DRMs). The conditions list contains 85 medical conditions which could occur during space flight and which are derived from several sources: Long-Term Surveillance of Astronaut Health (LSAH) in-flight occurrence data, The Space Shuttle (STS) Medical Checklist, The International Space Station (ISS) Medical Checklist, and subject matter expert opinion. Each medical condition listed has been assigned a clinical priority and a clinical priority rationale based on incidence, consequence, and mitigation capability. Implementation: The conditions list is a "living document" and as such, new conditions can be added to the list, and the priority of conditions on the list can be adjusted as the DRM changes, and as screening, diagnosis, or treatment capabilities change. The NEA medical conditions list was used recently as the basis for identifying gaps in in-flight medical evaluation (screening) capabilities. Learning Objectives: The audience will become familiar with the approach taken by NASA's Exploration Medical Capability element in addressing the risk of inability to recognize and treat medical conditions in the setting of a Near Earth Asteroid mission. Which one of the following statements is incorrect? a) The Near Earth Asteroid (NEA) medical conditions list includes 85 medical conditions which could occur during space flight. b) Each condition on the NEA medical conditions list has been assigned a clinical priority and a clinical priority rationale. c) The NEA medical conditions list targets a mission to Mars. d) The NEA medical conditions list should be viewed as a "living document" where new conditions can be added and clinical priorities adjusted to address changes in the design reference mission or medical capabilities. The incorrect answer is c). The NEA medical conditions list targets a mission to a Near Earth Asteroid.

Barr, Yael R.↗

DOE OSTI2021

Digital Engineering Sensor Architectures for Future Microreactor Builds

The development of new nuclear reactors continues to be high risk during the construction phase, with many programs exceeding their budget by 2–3×. This work entails an investigation of sensors that can be utilized during the construction of microreactors and their incorporation into a digital twin supporting the construction process. These sensors can be used to monitor construction progress, inform of variances from the expected design, and verify that the reactor is being built to the planned building information management model. This will ensure reactor equipment and components accurately interact through welding or additive manufacturing technologies. This study illustrates the importance of the digital engineering architecture for microreactor deployment.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

DOE OSTI2022

Integration of Control Methods and Digital Twins for Advanced Nuclear Reactors

Advanced nuclear reactors offer a new set of features to energy generation, due to their ability to adapt to variable energy demand, operate autonomously, be deployed in rural locations and monitored remotely, afford compact size and lower power ratings, and rely on novel technologies to achieve safer operations. Thus, a requirement for the success of these reactors is the use of intelligent forms of control to track changing power demands, make autonomous decisions, and reduce the need for human involvement. Regulatory requirements pertaining to control of nuclear reactors could be met via historical means of control; however, these are not expected to enable the level of highly autonomous operations desired in advanced nuclear reactors. Historical control methods rely on both logical and high-performance (HP) control. These two types of control are usually used separately, with a human element being introduced whenever decisions are cascaded from one science to another. AI/ML control, on the other hand, can replace the human element in the current U.S. fleet of nuclear power plants (NPPs) by acting as a supervisory optimizer that understands the plant internal/external variables in order to make control decisions, and can easily handle non-linear and multi-input/multi out (MIMO) decisions—another requirement for advanced nuclear reactors that could be difficult to handle via logical and HP control. Because of the harsh operating environments produced in advanced reactors, resulting in the frequent failure of sensors and other types of equipment, and considering the lack of operating history for advanced nuclear reactors, control of advanced nuclear reactors would necessitate relying on a model that can track and adapt to the actual process (i.e., a digital twin). This digital twin can make approximations when knowledge and data are unavailable and would evolve as more knowledge is gained. The reactor control must also be risk-informed to account for the high-consequence nature of advanced reactors. This report introduces a high-level (i.e., not method- or process-specific) integration of the three different control and digital twinning methods able to meet the requirements for advanced nuclear reactors. These methods could be applied during both the operational and design stages of these reactors. The aim is to demonstrate how each method interfaces with and highlights enabling solutions necessitated by the unique features of advanced nuclear reactors.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

NASA NTRS2002

Rapid Spacecraft Development: Results and Lessons Learned

The Rapid Spacecraft Development Office (RSDO) at NASA's Goddard Space Flight Center is responsible for the management and direction of a dynamic and versatile program for the definition, competition, and acquisition of multiple indefinite delivery and indefinite quantity contracts - resulting in a catalog of spacecraft buses. Five spacecraft delivery orders have been placed by the RSDO and one spacecraft has been launched. Numerous concept and design studies have been performed, most with the intent of leading to a future spacecraft acquisition. A collection of results and lessons learned is recorded to highlight management techniques, methods and processes employed in the conduct of spacecraft acquisition. Topics include working relationships under fixed price delivery orders, price and value, risk management, contingency reserves, and information restrictions.

Watson, William A.↗

NASA NTRS2020

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA’s Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA’s Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V’s desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V’s assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Gerek Whitman↗

NASA NTRS2020

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA's Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA's Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V's desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V's assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Whitman, Gerek↗

DOE OSTI2024

Brick Schema Standardized Plug Load Control Strategies for Load Reduction: Preprint

Plug loads comprise a significant percentage of commercial building energy consumption. Applying intelligent controls to turn off plug loads when unused can provide dynamic load reduction and flexibility, which are key traits of grid-interactive efficient buildings. This capability is important for equitable decarbonization as it can enable disadvantaged communities to electrify buildings without costly upgrades to electrical infrastructure. In this work, we present the effectiveness of various control strategies along with the operational lessons that informed their design. During a three-year period, we operated over 600 smart outlets in 12 university office buildings. The attached plug loads consisted primarily of printers, TVs, water dispensers, and copiers. After recording baseline power measurements for one year, we designed plug load control (PLC) strategies for each plug load type, use, and for different risk tolerance levels because PLC can potentially be disruptive to daily work. We used the Brick Schema to facilitate the management of plug load locations and other metadata. For advanced controls, we integrated the smart plugs with heating, ventilation, and air conditioning (HVAC) systems through the campus building automation system. We found static schedules to be the least disruptive and most predictable for occupants, resulting in 38% and 66% energy savings in two studies. For printers, print server-triggered PLC produced 86% savings, the highest of all strategies with minimal occupant impact. Scheduling of water dispensers and digital signage TVs produced 49% and 70% savings respectively with opportunities to improve performance with the use of HVAC occupancy data.

ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATION↗

NASA NTRSDate not supplied

Visualizations to Aid Decision-Making in the ACCP Value Framework

NASA’s priorities for Earth Science are informed by the 2017-2027 Decadal Survey for Earth Science and Applications from Space of the National Academies of Sciences, Engineering and Medicine. In that document, five Designated Observables are identified as priorities for research, two of which are Aerosols, and Clouds, Convection, and Precipitation. NASA is addressing these two Designated Observables by a combined study (the Aerosols, Clouds, Convection, and Precipitation, or ACCP, study). In this context of the ACCP study’s multiple objectives and multiple stakeholders, heuristic-based approaches are insufficient to assess candidate observing system concepts due to the complexity of the decision problem. For the ACCP study, this complexity in assessment is such that absent a structured approach that permits understanding of the steps leading to a decision, the decision risks being made on an incomplete basis. While prose and numeric data both have their place in effective communication, visualizations play an important part not only in presenting information, but also in structuring conversations around that information. Each of the visualizations developed for the ACCP Value Framework serve at least one of several functions: it structures communication about a method or process, it facilitates the elicitation and aggregation of data, or it summarizes complex information to enable analysis. Thus, these visualizations can present information, structure conversations, or do both.

Christopher A Jones↗

DOE OSTI2023

High-Reliability Systems and the Control of National Security Data and Information

High-reliability systems are characterized by catastrophic implications in the event of failure. These implications can include substantive damage to the environment, social order, and loss of life. Examples of high-reliability systems include nuclear submarines, nuclear reactors, the electric grid, and nuclear weapons. Due to the catastrophic implications of failure, there are heightened awareness and control mechanisms surrounding related data and information. However, defining the difference between data and information is often ambiguous across scholarly disciplines and in United States policy and legislation. For high-reliability systems, the implications of ambiguity between data and information may affect the security of United States interests and even cost lives. For security, data are raw facts or figures without context, while information is the compilation or articulation of data that forms context. Security depends on clarity in the differences between data and information and how to control them. Control is necessary to ensure that data and information are not unintentionally released to foreign governments, the public, or those without need-to-know. A primary concern in the practice of security is the control of data to avoid the unintended conversion to information. Intra-institutionally, this control is highly complex given the amalgam of legacy data systems and the numerous and constantly evolving nature of modern data systems that were not necessarily designed to be integrated. The complexity of this concern is augmented when institutions are part of inter-institutional collaborations or networks of public-private partnerships that share data and information. Additionally, institutions that share data as a function of policy and legislative action—particularly formally integrated data and information system infrastructures—may be at higher security risk. This paper will present an intra-institutional paradigm that utilizes and integrates concepts from numerous disciplines to frame a critical and underspecified practical issue in security—controlling for the unintended conversion of data to information.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

NASA NTRS2005

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned and technical standards. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. Systems Engineering has been defined (EINIS-632) as "an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system people, product, and process solutions that satisfy customer needs". Designing reliable space-based systems has always been a goal for NASA, and many painful lessons have been learned along the way. One of the continuing functions of a system engineer is to compile development and operations "lessons learned" documents and ensure their integration into future systems development activities. They can produce insights and information for risk identification identification and characterization. on a new project. Lessons learned files from previous projects are especially valuable in risk

Gill, Paul S.↗

NASA NTRS2005

Knowledge Capture and Management for Space Flight Systems

The incorporation of knowledge capture and knowledge management strategies early in the development phase of an exploration program is necessary for safe and successful missions of human and robotic exploration vehicles over the life of a program. Following the transition from the development to the flight phase, loss of underlying theory and rationale governing design and requirements occur through a number of mechanisms. This degrades the quality of engineering work resulting in increased life cycle costs and risk to mission success and safety of flight. Due to budget constraints, concerned personnel in legacy programs often have to improvise methods for knowledge capture and management using existing, but often sub-optimal, information technology and archival resources. Application of advanced information technology to perform knowledge capture and management would be most effective if program wide requirements are defined at the beginning of a program.

Goodman, John L.↗

NASA NTRS2012

The Role of Cis-Lunar Space in Future Global Space Exploration

Cis-lunar space offers affordable near-term opportunities to help pave the way for future global human exploration of deep space, acting as a bridge between present missions and future deep space missions. While missions in cis-lunar space have value unto themselves, they can also play an important role in enabling and reducing risk for future human missions to the Moon, Near-Earth Asteroids (NEAs), Mars, and other deep space destinations. The Cis-Lunar Destination Team of NASA's Human Spaceflight Architecture Team (HAT) has been analyzing cis-lunar destination activities and developing notional missions (or "destination Design Reference Missions" [DRMs]) for cis-lunar locations to inform roadmap and architecture development, transportation and destination elements definition, operations, and strategic knowledge gaps. The cis-lunar domain is defined as that area of deep space under the gravitational influence of the earth-moon system. This includes a set of earth-centered orbital locations in low earth orbit (LEO), geosynchronous earth orbit (GEO), highly elliptical and high earth orbits (HEO), earth-moon libration or "Lagrange" points (E-ML1 through E-ML5, and in particular, E-ML1 and E-ML2), and low lunar orbit (LLO). To help explore this large possibility space, we developed a set of high level cis-lunar mission concepts in the form of a large mission tree, defined primarily by mission duration, pre-deployment, type of mission, and location. The mission tree has provided an overall analytical context and has helped in developing more detailed design reference missions that are then intended to inform capabilities, operations, and architectures. With the mission tree as context, we will describe two destination DRMs to LEO and GEO, based on present human space exploration architectural considerations, as well as our recent work on defining mission activities that could be conducted with an EML1 or EML2 facility, the latter of which will be an emphasis of this paper, motivated in part by recent interest expressed at the Global Exploration Roadmap Stakeholder meeting. This paper will also explore the links between this HAT Cis-Lunar Destination Team analysis and the recently released ISECG Global Exploration Roadmap and other potential international considerations, such as preventing harmful interference to radio astronomy observations in the shielded zone of the moon.

Bobskill, Marianne R.↗

NASA NTRS2020

Mars Ascent Vehicle Solid Propulsion Configuration

As part of a Mars Sample Return (MSR) campaign, two Mars Ascent Vehicle (MAV) configurations have been designed in parallel. Each ascent vehicle configuration has a different propulsion system, which ultimately leads to two unique vehicle designs. As part of a Preliminary Architecture Assessment (PAA), these vehicle designs were developed to the same level of maturity in order to inform the selection of one of the vehicles as the point of departure design for the campaign. The selection will be made in November 2019. Although the initial MSR architecture called for a hybrid-based propulsion MAV featuring solid wax fuel with liquid oxidizer, a configuration using more traditional solid propulsion was developed as an additional risk mitigation option. Though lacking in the single stage to orbit (SSTO) and throttle flexibility of a hybrid configuration, a solid configuration vehicle allows a simpler design with significantly longer flight heritage and higher Technology Readiness Level (TRL). This paper describes the design of the solid propulsion configuration. An additional paper will be published describing the design of the hybrid propulsion configuration. The solid propulsion configuration MAV was developed in 2019 by NASA Marshall Space Flight Center (MSFC) in association with NASA Jet Propulsion Laboratory (JPL). It features two stages with a modified STAR-17 motor for the second stage and a traditional electromechanical actuator Thrust Vector Controller (TVC). The vehicle was designed to deliver approximately 0.47kg of Martian geological samples to a circular orbit at Mars of 343km at a 25° inclination. Although solid motor designs in general are at a relatively high TRL, the integrated vehicle subsystems that operate in conjunction with these propulsion elements do not typically operate in a Martian environment, which in this application can get as cold as -40°C. The PAA advanced the maturity of these subsystems by performing detailed design and analysis on the vehicle with respect to structures and mechanisms, Guidance/Navigation/Control (GNC) systems, avionics, Reaction Control System (RCS), TVC, thermal environments, and advanced Computational Fluid Dynamics (CFD). This paper will summarize the results of these studies.

Yaghoubi, Darius↗

NASA NTRS2020

Mars Ascent Vehicle Solid Propulsion Configuration

Yaghoubi, Darius↗