Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “TRUST”

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 397 records · Page 22

Implementing JEDI into NASA GMAO’s Real Time Production Suite

NASA’s Global Modeling and Assimilation Office (GMAO) has prepared their first production system involving the Joint Effort for Data assimilation Integration (JEDI) framework. In this system the central analysis, that drives the deterministic forecast, will be provided using JEDI. This talk outlines the phased approach to implementing JEDI into production that GMAO has designed, and how this approach will allow for a careful analysis of the system against the existing data assimilation framework (GSI). In the first phase of implementation the existing data assimilation system will perform certain actions that are still under development in JEDI. These include thinning the observations and producing satellite bias correction coefficients. JEDI is hooked up to the existing workflow so a single line switch can activate whether the existing or JEDI-based analysis is cycled. Outside of the monumental effort to construct JEDI that is ongoing at the Joint Center for Satellite Data Assimilation (JCSDA), GMAO have undertaken two areas of considerable effort. The talk will describe these efforts and highlight the main challenges that have been encountered. The first area of work is to implement the background error model from the existing data assimilation system into JEDI. The second is to validate the observing system in JEDI against the one in GSI, which has involved several new features being added to the observation operators in JEDI. While the longer-term plans involve trying to improve on the GSI in these two areas, GMAO is keen to have JEDI start from a trusted baseline. This is also key to implementing JEDI quickly so other priorities, such as increasing the number of model levels, can be easily worked on in parallel. GMAO is actively working on a framework to shepherd in the next generation coupled data assimilation system and model. As JEDI is implemented for the first time the plan is to ambitiously cycle through implementations, frequently bringing JEDI features to production. Details of these plans will be given in the talk and we will highlight key implementation and product milestones that we hope to achieve, as well as touch on the development environment that we will use to support frequent refreshing of the production system.

JEDI↗

NASA Strategy for Technology Development

At the National Aeronautics and Space Administration (NASA), foresight is a coordinated, iterative, and continual process for making informed decisions. NASA faces diverse and relatively unique challenges and opportunities as the leading U.S. agency for aeronautics development, cutting-edge scientific discovery, and human space exploration. To address these challenges and leverage opportunities, NASA uses foresight to strategically plan technology development across four mission directorates: Aeronautics Research Mission Directorate, Space Technology Mission Directorate, Science Mission Directorate, and Human Exploration and Operations Mission Directorate (recently separated into the new Exploration Systems Development Mission Directorate and Space Operations Mission Directorate). The mission directorates leverage a broad community of experts and partners to incorporate technology foresight into mission and program planning. Through this process NASA realizes tangible benefits to the agency’s science, technology, and exploration programs. As an independent office, NASA’s Office of Technology, Policy, and Strategy (OTPS) provides strategic advice, supported by independent assessments and rigorous analysis, to inform NASA senior leadership on key areas to align mission and agency-level activities. OTPS serves as a trusted authority to inform technology strategy at the agency to enable future missions. Specifically, OTPS coordinates and uses inputs from a broad community of experts, both internal and external to NASA, to inform decision making for technology plans, investments, and partnerships. OTPS develops and maintains the NASA Technology Taxonomy to standardize communication across the agency’s diverse technology portfolio and the related Strategic Technology Investment Plan that integrates priorities and informs technology investment. Through these efforts, OTPS has refined elements of foresight-informed strategic planning that may be applicable to other technology-driven industries where foresight is essential for resilience. This chapter describes the processes of foresight for technology development at NASA and provides insight into the value the agency derives from these processes. The chapter further describes the role of OTPS as an independent advisory office that supports NASA’s efforts to capitalize on foresight and strategic technology planning. We present these examples with consideration for how organizations in defense, security, and other technology-driven industries can operationalize foresight in their own strategic technology development.

Erica Rodgers↗

Human Factors Research Needs for In-Time Aviation Safety Management Systems (IASMS) Design: Enabling the NASA “Sky for All” Future Airspace Vision

Integrated safety management will be paramount for safely enabling the envisioned transformations of the future National Airspace System. Addressing the increasing need for advanced data analytics and fusion of aviation safety data, managed by human decision-makers, is essential for realizing the vision. The proposal, if accepted, will discuss safety management system challenges and how the concept of In-time Aviation Safety Management Systems addresses the need. It will also discuss human factors challenges involved in future integrated safety management, including trust, over-reliance, human-optimized data visualization, human-autonomy teaming, training, communication and dissemination of data, situation awareness, task load, and accountability.

Lawrence J Prinzel III↗

Embedding Differential Dynamic Logic in PVS

Runtime assurance is a control framework where a complex controller operates under the observation of a monitor. If the monitor detects the controller exhibiting undesirable behavior, control is passed off to a trusted controller until a desirable state is regained. The runtime assurance architecture provides a layer of assurance to the system being controlled, but special care must be taken that the resulting overall system, consisting of the monitors and controllers, is behaving as intended. This talk aims to formally model and reason about runtime assurance-equipped systems as hybrid programs- which are models that consist of both discrete and continuous components. Using the verification tool Plaidypvs, safety properties of some examples involving RTA architectures is shown.

Formal Verification↗

TruePAL – An AI Assistant for First Responder Safety

This paper presents the development of an AI assistant, Trusted and Explainable Artificial Intelligence for Saving Lives (TruePAL), to provide real-time warning of risks of potential crashes to the first responders. The TruePAL system employs an AI and deep learning technology for saving first responders and roadside crews lives in and around active traffic. A deep neural network (DNN) and a Non-Axiomatic Reasoning System (NARS) are implemented as an AI system. A mobile app with AI interface is developed to perform verbal communication with the first responders. The TruePAL team has developed an explainable AI approach by opening up the DNN blackbox to extract the activation filters of various features and parts of the targeted objects. The combination of DNN and NARS makes the TruePAL system explainable to the users. TruePAL ingests on-board cameras, radar, and other sensor signals, analyzes the environment and traffic patterns to generate timely warning to drivers and roadside crews to avoid crashes. The TruePAL team, in collaboration with the Miami/Dade Police Dept., has designed five use cases and multiple sub-scenarios in a CARLA driving simulator to test the capability of TruePAL in timely warning to the first responder drivers in potential crash scenarios. We have successfully demonstrated its capability of timely warning in over a dozen scenarios based on the use cases. The preliminary test simulation results show that TruePAL could provide the drivers and crew members advanced warning before a crash occurs.

Chow, Edward↗

Breaking Down Data Silos

Siloed schedule data creates barriers to information sharing and collaboration. In short, siloed data is not healthy data. If schedule data isn't easy to find and use in a timely fashion (or can't be trusted when it is found) it isn’t adding value. Many programs, projects, and initiatives are accustomed to working in their own worlds with their own lingo, processes, and challenges. This culture of separation carries over to schedules. This presentation will showcase SCaN’s efforts to break down the silo mentality.

schedule↗

Research and Technology Challenges for Human Data Analysts in Future Safety Management Systems

Enabling new and novel concepts of operations for Advanced Air Mobility poses an important need to evolve current safety management systems (SMS) and is posited to be realized through advances in Machine Learning (ML) Data Sciences and Artificial Intelligence. The “In-time Aviation Safety Management System” (IASMS) concept of operations supports the need to evolve today’s SMS to become more tailorable, scalable, and interoperable in response to forecasted changes expected for the future airspace system. Key to IASMS is integration of proactive and predictive ML algorithms trained to provide “in time” detection and mitigation of hazards and emergent risks through new methods and novel data types. IASMS research and technology development includes human factors design considerations for these systems to include human-system teaming, innovations in human interfaces and management of complex digital data information, human-system interaction/model-based system engineering, and verification and validation for data assurance and trust.

Chad L Stephens↗

NASA’s Digital Information Platform to Accelerate the Transformation of the National Airspace System

In order to accelerate the digital transformation of airspace operations, a foundational framework and infrastructure for providing sustainable, data-driven, and cohesive decision-making digital services for both traditional and emergent air vehicles is being developed. The reference implementation of Digital Information Platform builds an ecosystem for the aviation community by providing access to a secure and trusted source of aviation data and services. Several key features and services have been implemented to enable secure data sharing, communication, and service registration on the Platform. The technical approach used to implement these features is presented here. NASA-developed integrated aviation data and machine learning based prediction services to optimize airspace operations are available on the Platform. These services are being evaluated in an operational environment by flight operators and the real-world benefits are being captured. The Platform fosters collaboration among industry and researchers to develop complex aviation services and the aim is to make it publicly accessible for consumption by the aviation community.

Digital Transformation↗

NASA’s Digital Information Platform to Accelerate the Transformation of the National Airspace System

In order to accelerate the digital transformation of airspace operations, a foundational framework and infrastructure for providing sustainable, data-driven, and cohesive decision-making digital services for both traditional and emergent air vehicles is being developed. The reference implementation of Digital Information Platform builds an ecosystem for the aviation community by providing access to a secure and trusted source of aviation data and services. Several key features and services have been implemented to enable secure data sharing, communication, and service registration on the Platform. The technical approach used to implement these features is presented here. NASA-developed integrated aviation data and machine learning based prediction services to optimize airspace operations are available on the Platform. These services are being evaluated in an operational environment by flight operators and the real-world benefits are being captured. The Platform fosters collaboration among industry and researchers to develop complex aviation services and the aim is to make it publicly accessible for consumption by the aviation community.

Digital Transformation↗

Virtual Assistant for First Responders Using Natural Language Understanding and Optical Character Recognition

Commercial deep learning capabilities are available for many applications such as computer vision processing and intelligent chat bots. The Google Cloud Platform product Google Dialogflow provides lifelike conversational artificial intelligence (AI) using machine learning (ML) to generate natural conversations between computers and humans. This ML utilizes natural language understanding (NLU) to recognize a user’s intent and extracts key information into a form of entities. We have developed a user-friendly application through understanding the hazardous material database, first aid safety guidelines and observing the process of first responders who access this information in the field. We created the Trusted and Explainable Artificial Intelligence for Saving Lives (TruePAL) virtual assistant using Dialogflow1 and TensorFlow2 paired with EasyOCR.3 The chatbot supports first responders by providing voice interaction which helps limit additional steps such as browsing through multiple categories when searching for information. Using feedback from our field interviews, the voice interface has been developed to enable the first responder to focus on the immediate emergency. With less distractions, the first responder is able to engage the incident more effectively. The partial hands-free TruePAL chatbot assistant improves the accessibility to the correct guidance by an average of 1.9 seconds compared to the widely used application, NIH WISER, which requires full attention to operate. We combined this intelligent chatbot with a separate visual processing capability to produce hazardous signage analysis and generate the proper guidance for first responders. With the evolving functionality of AI tools, the use of virtual assistants in first responder technology will be an advancement, benefiting the safety of both first responders and civilians.

Chow, Edward↗

The Open Data Repository - an Open Science Platform for Long-Tail Research Data

Introduction: ‘Long-tail’ research is performed by individual PIs and small research teams, producing what are often highly diverse, but relatively small da-tasets that span a variety of traditional scientific disci-plines. ‘Long-tail’ research is a fundamental part of realizing NASA’s goals in planetary sciences and a key input feeding into mission life cycles. The ‘long-tail’ has traditionally lacked the resources (available to larg-er groups and missions) to overcome barriers inhibit-ing the adoption of open science practices, including lack of acknowledgment, time, money, guidance, ex-pertise, and trust in available platforms1. Here we show how the Open Data Repository’s (ODR) data publish-ing platform could help lower some of these barriers and accelerate the adoption of open-science practices in planetary science.

‘Long-tail’ research↗

Guiding Integration of Formal Verification in Assurance Cases

Assurance cases are being increasingly acknowledged as away to build trust in complex systems with autonomous capabilities. An assurance case is a comprehensive, defensible, and valid justification that a system will function as intended for a specific mission and operating environment. Formal verification is often reserved for the most critical components of such systems. However, formal verification tools are often complex, and their usage is subject to many constraints and contextual dependencies. This can raise challenges both for performing the verification as well as reflecting the verification results appropriately in the assurance case, especially for non-expert users of the verification tool. To address these challenges, we present a tool-supported methodology for integrating formal verification results in an assurance case by capturing key verification method information in a rigorously constructed assurance case. In particular, we capture the tool specification in terms of its inputs, outputs, and assurance constraints as assumptions over inputs and guarantees provided over its outputs. The tool specification is parametrized over the inputs and outputs to both guide the intended application of the tool, as well as to check that the tool has been applied following the stated assumptions and that the guarantees hold. We define a generic tool assurance argument pattern that enables integration of the verification results in the assurance case by allowing custom refinement and automated instantiation for each tool use. We demonstrate our methodology on two formal verification tools and their applications to the verification of neural network properties for the aircraft domain.

Assurance Cases↗

Dynamic Assurance of Autonomous Systems through Ground Control Software∗

Assurance cases are being increasingly acknowledged as a way to build trust in complex systems with autonomous capabilities [1]. An assurance case is a comprehensive, defensible, and valid justification that a system will function as intended for the specific mission and operating environment. Such justifications for systems with autonomous capabilities are often based on various probabilistic quantifications [2]. Due to the dynamic nature of the environmental conditions in which these systems operate, as well as the changing nature of the autonomous systems themselves, these probabilistic quantifications cannot be simply estimated once during design time. Rather, they need to be continually evaluated during systems operations to ensure that the assurance case justifications are valid. We refer to the assurance case that combines both the static and dynamic elements as a Dynamic Assurance Case (DAC).

dynamic assurance case↗

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Performance of Two Battery Prognostic Applications used by Two Octocopters for Safe Low Altitude Autonomous Flight Operations

This paper addresses the problem of building trust in online predictions of the remaining available flying time for two different electric Unmanned Aerial Vehicles (eUAVs) powered by lithium-ion-polymer batteries. Flight tests for various automation research missions for the two vehicles were monitored using two on-board battery health management applications to make predictions of the remaining flying time (RFT) for each eUAV and to predict the state of the battery. Playback of the voltage, current and temperature profiles of the battery discharge were used to assess the accuracy of the estimation of the voltage and the charge states of the models as well as the estimate of the RFT. The reference ground truth values were the observed landing time and the measured battery pack resting pack voltage 20 minutes after the flight. The predicted RFT, state of charge (SoC), and state of energy (SoE) were compared with the observed results. Noise values of one standard deviation from the mean values of the internal charge states of the battery model during a reference run were used to vary the states during simulation. One application used an equivalent circuit model of the electrical dynamics of the battery pack, and the other application used a reduced-order electrochemistry model. The variation of the model state components was compared to the variation in the estimate of the RFT and the variation in the SoE to estimate a confidence factor. Variation in the estimates caused by factors affecting the off-line laboratory parameter identification experiments is considered. Variation in the estimates due to environmental factors are discussed.

Assurance↗

National Campaign Development Test Executive Summary

NASA’s vision for Advanced Air Mobility (AAM) is to provide safe, sustainable, accessible, and affordable aviation for transformational local and intraregional missions and includes the transportation of passengers and cargo as well as aerial work missions, such as infrastructure inspection or search and rescue operations. NASA’s technical expertise, intergovernmental relationships, and high level of public trust will help this technology come to market concurrent with infrastructure readiness, public acceptance, and constructive regulation. By advising and integrating disparate AAM efforts across the country and working collaboratively with the FAA, the National Campaign (NC) objective is to motivate industry progress and support the development of policy, regulatory, and technical standards in a manner that best ensures public safety and benefit to the American people. NC began with the Dry Run and Developmental Test (NC-DT), which served as a pathfinder for collaboration and direct involvement with industry partners in integrated simulation exercises and flight tests. NC-DT culminated with an acoustics-gathering flight test in September 2021 with industry partner Joby’s prototype S4 2.0 air vehicle, which delivered the first foundational baseline of noise levels present in Electric Vertical Takeoff and Landing (eVTOL) vehicles. Through the DT phase, the NC team built and tested the airspace and range infrastructure while assessing the readiness level of industry partners leading up to future NC events. The purpose of this paper is to provide an overview of NC-DT.

National Campaign↗

Introduction of an Agile Systems Engineering Process to the NASA Armstrong Flight Research Center

This paper will provide background on the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD) ARMD Test Data Portal (ATDP) effort along with the rationale that motivated the ATDP team to consider implementing an agile systems engineering (SE) process. The primary motivation for using this new SE process was based on the desire to mitigate a major risk to project success. Since the agile SE process had never been used before at the NASA Armstrong Flight Research Center (AFRC), utilizing this new SE process required a trailblazing effort to introduce it to NASA AFRC leadership. As a result, the ATDP team chose to adhere to the agile SE process in addition to the trusted classical waterfall SE process on ATDP. Through successful execution of this hybrid SE process during Phase I, along with demonstrating the value and rigor of the agile SE process, NASA AFRC leadership ultimately permitted the ATDP project to solely use the agile SE process for developments beyond Phase I. While it is the opinion of the authors that the classical SE process is more effective for most projects at NASA AFRC, some projects may deem that the agile SE process is more advantageous. Although this paper is focused on introducing the agile SE process to NASA AFRC, lessons learned will be valuable to other organizations as well. Details of how the ATDP team implemented the agile SE process during Phase I will be summarized, along with how the team met all required classical SE milestones. Lessons learned throughout Phase I of this effort will also be highlighted.

Daniel S. Jones↗