SEARCH · Search NASA

Results for “consequence management”

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 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS2009

Integrated System Health Management: Foundational Concepts, Approach, and Implementation

A sound basis to guide the community in the conception and implementation of ISHM (Integrated System Health Management) capability in operational systems was provided. The concept of "ISHM Model of a System" and a related architecture defined as a unique Data, Information, and Knowledge (DIaK) architecture were described. The ISHM architecture is independent of the typical system architecture, which is based on grouping physical elements that are assembled to make up a subsystem, and subsystems combine to form systems, etc. It was emphasized that ISHM capability needs to be implemented first at a low functional capability level (FCL), or limited ability to detect anomalies, diagnose, determine consequences, etc. As algorithms and tools to augment or improve the FCL are identified, they should be incorporated into the system. This means that the architecture, DIaK management, and software, must be modular and standards-based, in order to enable systematic augmentation of FCL (no ad-hoc modifications). A set of technologies (and tools) needed to implement ISHM were described. One essential tool is a software environment to create the ISHM Model. The software environment encapsulates DIaK, and an infrastructure to focus DIaK on determining health (detect anomalies, determine causes, determine effects, and provide integrated awareness of the system to the operator). The environment includes gateways to communicate in accordance to standards, specially the IEEE 1451.1 Standard for Smart Sensors and Actuators.

Figueroa, Fernando↗

NASA NTRS1995

Training for Aviation Decision Making: The Naturalistic Decision Making Perspective

This paper describes the implications of a naturalistic decision making (NDM) perspective for training air crews to make flight-related decisions. The implications are based on two types of analyses: (a) identification of distinctive features that serve as a basis for classifying a diverse set of decision events actually encountered by flight crews, and (b) performance strategies that distinguished more from less effective crews flying full-mission simulators, as well as performance analyses from NTSB accident investigations. Six training recommendations are offered: (1) Because of the diversity of decision situations, crews need to be aware that different strategies may be appropriate for different problems; (2) Given that situation assessment is essential to making a good decision, it is important to train specific content knowledge needed to recognize critical conditions, to assess risks and available time, and to develop strategies to verify or diagnose the problem; (3) Tendencies to oversimplify problems may be overcome by training to evaluate options in terms of goals, constraints, consequences, and prevailing conditions; (4) In order to provide the time to gather information and consider options, it is essential to manage the situation, which includes managing crew workload, prioritizing tasks, contingency planning, buying time (e.g., requesting holding or vectors), and using low workload periods to prepare for high workload; (5) Evaluating resource requirements ("What do I need?") and capabilities ("'What do I have?" ) are essential to making good decisions. Using resources to meet requirements may involve the cabin crew, ATC, dispatchers, and maintenance personnel; (6) Given that decisions must often be made under high risk, time pressure, and workload, train under realistic flight conditions to promote the development of robust decision skills.

Orasanu, Judith↗

NASA NTRS2005

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite's White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with and turnaround maintenance performed. The fight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development. NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This recent partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of the X-37 effort, the team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff research and development and provides valuable experience to implement the exploration vision.

Turner, Susan↗

NASA NTRS2005

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite s White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with landing and turnaround maintenance performed. The Flight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development (R&D). NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of this effort, the X-37 team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff R&D and provides valuable experience to implement the Vision for Space Exploration.

Turner, Susan↗

NASA NTRS2007

Ultra-Thin, Triple-Bandgap GaInP/GaAs/GaInAs Monolithic Tandem Solar Cells

The performance of state-of-the-art, series-connected, lattice-matched (LM), triple-junction (TJ), III-V tandem solar cells could be improved substantially (10-12%) by replacing the Ge bottom subcell with a subcell having a bandgap of approx.1 eV. For the last several years, research has been conducted by a number of organizations to develop approx.1-eV, LM GaInAsN to provide such a subcell, but, so far, the approach has proven unsuccessful. Thus, the need for a high-performance, monolithically integrable, 1-eV subcell for TJ tandems has remained. In this paper, we present a new TJ tandem cell design that addresses the above-mentioned problem. Our approach involves inverted epitaxial growth to allow the monolithic integration of a lattice-mismatched (LMM) approx.1- eV GaInAs/GaInP double-heterostructure (DH) bottom subcell with LM GaAs (middle) and GaInP (top) upper subcells. A transparent GaInP compositionally graded layer facilitates the integration of the LM and LMM components. Handle-mounted, ultra-thin device fabrication is a natural consequence of the inverted-structure approach, which results in a number of advantages, including robustness, potential low cost, improved thermal management, incorporation of back-surface reflectors, and possible reclamation/reuse of the parent crystalline substrate for further cost reduction. Our initial work has concerned GaInP/GaAs/GaInAs tandem cells grown on GaAs substrates. In this case, the 1- eV GaInAs experiences 2.2% compressive LMM with respect to the substrate. Specially designed GaInP graded layers are used to produce 1-eV subcells with performance parameters nearly equaling those of LM devices with the same bandgap (e.g., LM, 1-eV GaInAsP grown on InP). Previously, we reported preliminary ultra-thin tandem devices (0.237 cm2) with NREL-confirmed efficiencies of 31.3% (global spectrum, one sun) (1), 29.7% (AM0 spectrum, one sun) (2), and 37.9% (low-AOD direct spectrum, 10.1 suns) (3), all at 25 C. Here, we include recent results of testing similar devices under the concentrated AMO spectrum, and also present the first demonstration of a high-efficiency, ultra-thin GaInP/GaAs/GaInAs tandem cell processed on a flexible kapton handle.

Wanlass, M. W.↗

NASA NTRSDate not supplied

Big-data Efficient and Automated Science Transfer (BEAST): An Open-Source Software Architecture for Arc Jet Data Management, Modeling, and Automation

Big-data Efficient and Automated Science Transfer (BEAST) was conceived to address the existing ground testing data management of the NASA Ames arc jet facilities (e.g., manually entered Excel files and USB drive data transfers). These data management practices were seen as a choke point for future thermal protection system (TPS) development as they limit statistical tracking, resolution of diagnostics, coordination between video/time series, data throughput, and data processing speed/efficiency. Consequently, BEAST was developed to provide a new data infrastructure with streamlined data collection, processing, transfer, and analysis. This new framework also seeks to implement the FAIR principles of data stewardship: Findable, Accessible, Interoperable, and Reusable. The BEAST framework is based on a combination of the Python Django web framework and the Python data stack to provide a monolithic, open-source platform for data management, automation, and machine learning. This architecture was chosen for maintainability and scalability for a small, in-house development team. This paper will describe the application framework, deployment, and discuss the benefits and future plans for the system.

Data management↗

NASA NTRSDate not supplied

Big-data Efficient Automated Science Transfer (BEAST): an open-source software architecture for arc jet data management, modeling, and automation

Data management↗

NASA NTRS2019

NASA's Earth Observing Data and Information System (EOSDIS)

NASA's Earth Observing System Data and Information System (EOSDIS) has been a central component of the NASA Earth observation program since the 1990's. The data collected by NASA represent a significant public investment in research. Consequently, NASA developed a free, open and non-discriminatory policy consistent with existing international policies to maximize access to data. EOSDIS manages data covering a wide range of Earth science disciplines including cryosphere, land cover change, polar processes, field campaigns, ocean surface, geodesy, atmosphere dynamics and composition, and inter-disciplinary research, and many others.

Remote Sensing↗

NASA NTRS2019

NASA's Earth Observing Data and Information System (EOSDIS)

Data Systems↗

NASA NTRSDate not supplied

Accounting for Point Estimate Uncertainty in Space Systems Reliability and Risk Analysis

Understanding and accounting for uncertainty in risk analysis is a critical step in the management and communication of risk in engineered systems. The component and system-level analysis to determine the probability of a negative outcome and its consequence is often quantified by a point estimate. Many Program and Enterprise decisions involving technical concerns and issues rely on reliability engineering activities to produce quantified risk analysis to inform the decision making process. At NASA, it is common to use a Probabilistic Risk Analysis (PRA) to inform the overall risk to Loss of Mission or Loss of Crew that involves integration across all spacecraft subsystem fault trees to produce an overall probability of mission failure. The point estimate is an estimate of this overall probability and is an immediate result of a fault tree model. It is the result of a model where the probability of each event is taken to be equal to its mean. The value provides an approximation of the overall mean without running any uncertainty calculations (e.g., no sampling). Using only the point estimate can lead to a false sense of precision and the point estimate may not match the resulting mean when uncertainty is taken into consideration. This paper will explore five conditions that can cause the PRA model mean to diverge from the point estimate and will provide engineers and managers insight into the importance of understanding uncertainty in the elements of PRA models.

Paul J Collier↗

NASA NTRS2013

Putting Integrated Systems Health Management Capabilities to Work: Development of an Advanced Caution and Warning System for Next-Generation Crewed Spacecraft Missions

Integrated System Health Management (ISHM) technologies have advanced to the point where they can provide significant automated assistance with real-time fault detection, diagnosis, guided troubleshooting, and failure consequence assessment. To exploit these capabilities in actual operational environments, however, ISHM information must be integrated into operational concepts and associated information displays in ways that enable human operators to process and understand the ISHM system information rapidly and effectively. In this paper, we explore these design issues in the context of an advanced caution and warning system (ACAWS) for next-generation crewed spacecraft missions. User interface concepts for depicting failure diagnoses, failure effects, redundancy loss, "what-if" failure analysis scenarios, and resolution of ambiguity groups are discussed and illustrated.

integrated system management↗

NASA NTRS2004

Integrated Risk Management Within NASA Programs/Projects

As NASA Project Risk Management activities continue to evolve, the need to successfully integrate risk management processes across the life cycle, between functional disciplines, stakeholders, various management policies, and within cost, schedule and performance requirements/constraints become more evident and important. Today's programs and projects are complex undertakings that include a myriad of processes, tools, techniques, management arrangements and other variables all of which must function together in order to achieve mission success. The perception and impact of risk may vary significantly among stakeholders and may influence decisions that may have unintended consequences on the project during a future phase of the life cycle. In these cases, risks may be unintentionally and/or arbitrarily transferred to others without the benefit of a comprehensive systemic risk assessment. Integrating risk across people, processes, and project requirements/constraints serves to enhance decisions, strengthen communication pathways, and reinforce the ability of the project team to identify and manage risks across the broad spectrum of project management responsibilities. The ability to identify risks in all areas of project management increases the likelihood a project will identify significant issues before they become problems and allows projects to make effective and efficient use of shrinking resources. By getting a total team integrated risk effort, applying a disciplined and rigorous process, along with understanding project requirements/constraints provides the opportunity for more effective risk management. Applying an integrated approach to risk management makes it possible to do a better job at balancing safety, cost, schedule, operational performance and other elements of risk. This paper will examine how people, processes, and project requirements/constraints can be integrated across the project lifecycle for better risk management and ultimately improve the chances for mission success.

Connley, Warren↗

NASA NTRS2018

Generalizing a Data Analysis Pipeline in the Cloud to Handle Diverse Use Cases in NASA's EOSDIS

NASA's Earth Observing System Data and Information System (EOSDIS) is tasked with archiving and distributing Earth Observation data across a range of disciplines, including atmospheric science, oceanography, land processes, natural hazards, solar radiance and even socioeconomic aspects relating to the environment. Driven by rapidly rising data volumes, EOSDIS is migrating to a cloud computing based archive over the next few years. Although this simplifies data management somewhat, the main aim is to provide the data in an environment where end users can bring their analysis to the data rather than attempting to download and manage ever-increasing volumes. To that end, a cloud-based analysis platform is being constructed to enable data transformations, analyses and visualization without egressing the data from the cloud. In this endeavor, we expect a wide variety of users, algorithms and use cases. Consequently, the architecture of this cloud analytics platform is expressly designed to be based on open services, thus fostering an ecosystem that enables the efficient combination of common components with data-specific or analysis-specific components. Reviewed and approved by Andrew Mitchell, ESDIS project manager.

Cloud computing↗

NASA NTRS1981

Soil spectral characterization

The spectral characterization of soils is discussed with particular reference to the bidirectional reflectance factor as a quantitative measure of soil spectral properties, the role of soil color, soil parameters affecting soil reflectance, and field characteristics of soil reflectance. Comparisons between laboratory-measured soil spectra and Landsat MSS data have shown good agreement, especially in discriminating relative drainage conditions and organic matter levels in unvegetated soils. The capacity to measure both visible and infrared soil reflectance provides information on other soil characteristics and makes it possible to predict soil response to different management conditions. Field and laboratory soil spectral characterization helps define the extent to which intrinsic spectral information is available from soils as a consequence of their composition and field characteristics.

Stoner, E. R.↗

NASA NTRS2001

The Role of Space Medicine in Management of Risk in Spaceflight

The purpose of Space Medicine is to ensure mission success by providing quality and comprehensive health care throughout all mission phases to optimize crew health and performance and to prevent negative long-term health consequences. Space flight presents additional hazards and associated risks to crew health, performance, and safety. With an extended human presence in space it is expected that illness and injury will occur on orbit, which may present a significant threat to crew health and performance and to mission success. Maintaining crew health, safety and performance and preventing illness and injury are high priorities necessary for mission success and agency goals. Space flight health care should meet the standards of practice of evidence based clinical medicine. The function of Space Medicine is expected to meet the agency goals as stated in the 1998 NASA Strategic Plan and the priorities established by the Critical Path Roadmap Project. The Critical Path Roadmap Project is an integrated NASA cross-disciplinary strategy to assess, understand, mitigate, and manage the risks associated with long-term exposure to the space flight environment. The evidence based approach to space medicine should be standardized, objective process yielding expected results and establishing clinical practice standards while balancing individual risk with mission (programmatic) risk. The ability to methodically apply available knowledge and expertise to individual and mission health issues will ensure appropriate priorities are assigned and resources are allocated. NASA Space Medicine risk management process is a combined clinical and engineering approach. Competition for weight, power, volume, cost, and crew time must be balanced in making decisions about the care of individual crew with competing agency resources.

Clark, Jonathan B.↗

NASA NTRS2016

Pitfalls and Precautions When Using Predicted Failure Data for Quantitative Analysis of Safety Risk for Human Rated Launch Vehicles

Launch vehicle reliability analysis is largely dependent upon using predicted failure rates from data sources such as MIL-HDBK-217F. Reliability prediction methodologies based on component data do not take into account system integration risks such as those attributable to manufacturing and assembly. These sources often dominate component level risk. While consequence of failure is often understood, using predicted values in a risk model to estimate the probability of occurrence may underestimate the actual risk. Managers and decision makers use the probability of occurrence to influence the determination whether to accept the risk or require a design modification. The actual risk threshold for acceptance may not be fully understood due to the absence of system level test data or operational data. This paper will establish a method and approach to identify the pitfalls and precautions of accepting risk based solely upon predicted failure data. This approach will provide a set of guidelines that may be useful to arrive at a more realistic quantification of risk prior to acceptance by a program.

Hatfield, Glen S.↗

NASA NTRS2017

Design and Requirements Creep In A Build-To-Print Mission

Build-to-Print designs, or rebuilds of flight proven designs, are attractive to mission stakeholders, as they give the appearance of minimal engineering development cost, risk, and schedule. The reality is that seldom is a project an exact duplicate of a predecessor. Mission reclassification, improvements in hardware, and science objective changes can all serve as a source of requirements and design creep and have ramifications often not fully anticipated during initial proposals. The Thermal Infrared Sensor Instrument (TIRS) was a late addition to the LandSat-8 program to provide infrared imaging to measure evapotranspiration for water cycle management. To meet the launch requirements for LandSat-8, instrument design life requirements were relaxed, the sensor development expedited, and technology development was minimized. Consequently, TIRS was designed as a higher risk instrument, with less redundancy than an instrument critical to mission success. After the successful LandSat-8 launch in 2013 and instrument performance, a rebuild of the instrument for the next LandSat spacecraft was included in the baseline mission success criteria. This paper discusses the technical challenges encountered during the rebuild of the TIRS-2 (Thermal Infrared Sensor 2) instrument and the resultant impacts on the thermal system design.

TIRS-2 Thermal Design↗

NASA NTRS2021

An Innovative Approach to Modeling VIPER Rover Software Life Cycle Cost

NASA’s “Volatiles Investigating Polar Exploration Rover” (VIPER) will be the first robotic mission to prospect for water ice near the south pole of the Moon in late 2023 on a 100-Earth-day mission. The information that the VIPER rover provides will help improve understanding of the composition, distribution, and accessibility of Lunar polar volatiles and will help determine how the Moon’s resources can support future human space exploration. VIPER, however, represents a radical departure from the way that NASA has traditionally developed planetary robotic missions. A key consequence of these differences is that estimating the cost of VIPER’s rover software is challenging and complex.For example, VIPER is being developed using management procedures typically applied to NASA research and technology projects, rather than space flight programs. In addition, key portions of the rover’s software are being designed as ground software to run on mission control computers (rather than on-board the rover as flight software as with prior planetary missions) taking advantage of continuous, interactive data communications between the Moon and Earth and higher performance computing available on the ground. Moreover, the rover’s software is being engineered using Agile software development practices and incorporates a significant amount of open-source, rather than following traditional (spiral, waterfall, etc.) development methods and in-house code. In this paper, we present an innovative process to estimate the life cycle cost of VIPER’s rover software. We first describe how we modeled the architecture and code counts for three software elements: Rover Flight Software (RFSW), Rover Ground Software (RGSW), and Rover Simulation Software (RSIM). We then discuss key challenges and unique aspects of our approach, such as the lack of Lunar rover analogies, the need to integrate and test large open source software, and the strategies developed to account for use of non-space flight management practices and the impact of the COVID-19 pandemic. We conclude with a summary of our results, including cumulative distribution, nearest neighbors and cluster analysis, as well as heuristics used to confirm the reasonableness of the cost estimate.

Utz, Hans↗