Search NASA⌕ Search

SEARCH · Search NASA

Results for “assurance tools”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Earth Science Markup Language: Transitioning From Design to Application

The primary objective of the proposed Earth Science Markup Language (ESML) research is to transition from design to application. The resulting schema and prototype software will foster community acceptance for the "define once, use anywhere" concept central to ESML. Supporting goals include: 1. Refinement of the ESML schema and software libraries in cooperation with the user community. 2. Application of the ESML schema and software libraries to a variety of Earth science data sets and analysis tools. 3. Development of supporting prototype software for enhanced ease of use. 4. Cooperation with standards bodies in order to assure ESML is aligned with related metadata standards as appropriate. 5. Widespread publication of the ESML approach, schema, and software.

Moe, Karen↗
NASA NTRS2003

ESML for Earth Science Data Sets and Analysis

The primary objective of this research project was to transition ESML from design to application. The resulting schema and prototype software will foster community acceptance for the Define once, use anywhere concept central to ESML. Supporting goals include: 1) Refinement of the ESML schema and software libraries in cooperation with the user community; 2) Application of the ESML schema and software to a variety of Earth science data sets and analysis tools; 3) Development of supporting prototype software for enhanced ease of use; 4) Cooperation with standards bodies in order to assure ESML is aligned with related metadata standards as appropriate; and 5) Widespread publication of the ESML approach, schema, and software.

Graves, Sara↗
NASA NTRSDate not supplied

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↗
NASA NTRS2023

Full Lunar Surface Visualization and Simulation Platform

This project created a visualization and simulation software platform for the entire lunar surface. Given the polar Artemis landing targets, the challenging terrain, lighting, and associated integrated crew / vehicle risk assessment, a more integrated approach to mission safety certification, potentially impacting equipment design and crew activity is required. This integrated capability will enable Safety and Mission Assurance (SMA), Flight Operations (FOD), and EVA to effectively collaborate to reduce human lunar exploration operational risk utilizing the identical tools to perform mission planning, rehearsal simulations, and providing the Safety Review Panel with integrated risk analysis capability.

information fusion↗
NASA NTRS1981

Advanced composite aileron for L-1011 transport aircraft: Aileron manufacture

The fabrication activities of the Advanced Composite Aileron (ACA) program are discussed. These activities included detail fabrication, manufacturing development, assembly, repair and quality assurance. Five ship sets of ailerons were manufactured. The detail fabrication effort of ribs, spar and covers was accomplished on male tools to a common cure cycle. Graphite epoxy tape and fabric and syntactic epoxy materials were utilized in the fabrication. The ribs and spar were net cured and required no post cure trim. Material inconsistencies resulted in manufacturing development of the front spar during the production effort. The assembly effort was accomplished in subassembly and assembly fixtures. The manual drilling system utilized a dagger type drill in a hydraulic feed control hand drill. Coupon testing for each detail was done.

Dunning, E. G.↗
NASA NTRS2020

Building a standardized Observing System Simulation Experiment (OSSE) framework for Mars

We advocate that the Decadal Survey recommends the NASA Science Mission Directorate to develop a rigorous Observing System Simulation Experiment (OSSE) framework for Mars, to optimize future atmospheric observations. Atmospheric conditions on Mars are a potential hazard source for landing missions. Errors in the estimates of atmospheric density profiles, inadequate knowledge of wind vertical structure and dust concentration as a function of height are likely causes of uncertainty at the landing site on the order of kilometers. An operational real-time weather forecasting capability for Mars would reduce such uncertainties, carrying enormous benefits to future robotic missions, and would be an invaluable prerequisite for human missions.A real-time forecasting capability relies upon three fundamental components: a critical mass of observing systems, a data assimilation system (DAS), and a global forecast model. The DAS allows the model to ingest the data effectively, optimizing the observational information content,and transforming them into a gridded representation of the atmosphere at a given time, called an ‘analysis’. The analysis is the best estimate of the atmospheric state for that time, and also represents a set of ‘initial conditions’ from which a global model can be initialized, to predict a future state of the atmosphere. The connection between analysis and forecast represents the foundation of modern weather forecasting. However, from the point of view of a forecast system,not all observations are equally impactful, partially because of the problem of “observational error correlation”, one important research topic in data assimilation development. For the Earth, partly due to the spontaneous and deregulated development of observations and forecast capabilities worldwide for more than half a century,the use of observations in contemporary operational forecast systems is suboptimal, with many potentially useful data being underutilized. On the contrary, Mars atmospheric scientists are in the unique situation of designing the next-generation observing systems by learning from the experience gathered on the Earth, so as to assure that the future instruments are specifically optimized to give the maximum benefit to a future weather forecast capability.An immensely powerful tool that has been firmly established by atmospheric scientists on the Earth is represented by a properly designed OSSE framework. A realistic OSSE framework cannot only quantify the benefit of future data types, be them surface based or space borne, but can also help design and optimize an entire observational network. Furthermore, OSSEs can provide deep insights into an atmosphere’s behavior, by addressing conceptual problems of its intrinsic predictability and delineating the regions or features of the atmosphere which are more sensitive to additional data and would benefit from a denser sampling. The difficulties posed by OSSEs are fundamentally different for Earth and Mars. For Earth, the enormous data volume imposes a tremendous constraint on any innovation in the observing systems: it is very hard for a single sensor to impact the skill. For Mars, the problem is the opposite: almost any additional instrument will exert some impact. However, OSSEs can help to evaluate the cost/benefit for every sensor and suggest optimal data configuration and density.The purpose of this white paper is to provide an introduction to a rigorously designed OSSE framework, explain the underlying problems and challenges, and engage the Mars community to collaborate with Earth Atmospheric scientists in order to develop a joint-OSSE framework for Mars with the largest consensual basis possible. An OSSE infrastructure would increase the understanding of the Martian atmosphere, would help NASA to optimize instrument specifications and orbit choice, providing the maximium benefit for a given expenditure of resources, and could even help establishing a roadmap for a future real-time weather forecasting capability.

Oreste Reale↗
NASA NTRS1998

Case-Based Capture and Reuse of Aerospace Design Rationale

The goal of this project is to apply artificial intelligence techniques to facilitate capture and reuse of aerospace design rationale. The project applies case-based reasoning (CBR) and concept mapping (CMAP) tools to the task of capturing, organizing, and interactively accessing experiences or "cases" encapsulating the methods and rationale underlying expert aerospace design. As stipulated in the award, Indiana University and Ames personnel are collaborating on performance of research and determining the direction of research, to assure that the project focuses on high-value tasks. In the first five months of the project, we have made two visits to Ames Research Center to consult with our NASA collaborators, to learn about the advanced aerospace design tools being developed there, and to identify specific needs for intelligent design support. These meetings identified a number of task areas for applying CBR and concept mapping technology. We jointly selected a first task area to focus on: Acquiring the convergence criteria that experts use to guide the selection of useful data from a set of numerical simulations of high-lift systems. During the first funding period, we developed two software systems. First, we have adapted a CBR system developed at Indiana University into a prototype case-based reasoning shell to capture and retrieve information about design experiences, with the sample task of capturing and reusing experts' intuitive criteria for determining convergence (work conducted at Indiana University). Second, we have also adapted and refined existing concept mapping tools that will be used to clarify and capture the rationale underlying those experiences, to facilitate understanding of the expert's reasoning and guide future reuse of captured information (work conducted at the University of West Florida). The tools we have developed are designed to be the basis for a general framework for facilitating tasks within systems developed by the Advanced Design Technologies Testbed (ADTT) project at ARC. The tenets of our framework are (1) that the systems developed should leverage a designer's knowledge, rather than attempting to replace it; (2) that learning and user feedback must play a central role, so that the system can adapt to how it is used, and (3) that the learning and feedback processes must be as natural and as unobtrusive as possible. In the second funding period we will extend our current work, applying the tools to capturing higher-level design rationale.

Leake, David B.↗
NASA NTRS2016

Assurance of Fault Management: Risk-Significant Adverse Condition Awareness

Fault Management (FM) systems are ranked high in risk-based assessment of criticality within flight software, emphasizing the importance of establishing highly competent domain expertise to provide assurance for NASA projects, especially as spaceflight systems continue to increase in complexity. Insight into specific characteristics of FM architectures seen embedded within safety- and mission-critical software systems analyzed by the NASA Independent Verification Validation (IVV) Program has been enhanced with an FM Technical Reference (TR) suite. Benefits are aimed beyond the IVV community to those that seek ways to efficiently and effectively provide software assurance to reduce the FM risk posture of NASA and other space missions. The identification of particular FM architectures, visibility, and associated IVV techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. The role FM has with regard to overall asset protection of flight software systems is being addressed with the development of an adverse condition (AC) database encompassing flight software vulnerabilities.Identification of potential off-nominal conditions and analysis to determine how a system responds to these conditions are important aspects of hazard analysis and fault management. Understanding what ACs the mission may face, and ensuring they are prevented or addressed is the responsibility of the assurance team, which necessarily should have insight into ACs beyond those defined by the project itself. Research efforts sponsored by NASAs Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs, and allowing queries based on project, mission type, domain component, causal fault, and other key characteristics. The repository has a firm structure, initial collection of data, and an interface established for informational queries, with plans for integration within the Enterprise Architecture at NASA IVV, enabling support and accessibility across the Agency. The development of an improved workflow process for adaptive, risk-informed FM assurance is currently underway.

Software Verification & Validation↗
NASA NTRS2009

Baseline Assessment and Prioritization Framework for IVHM Integrity Assurance Enabling Capabilities

Fundamental to vehicle health management is the deployment of systems incorporating advanced technologies for predicting and detecting anomalous conditions in highly complex and integrated environments. Integrated structural integrity health monitoring, statistical algorithms for detection, estimation, prediction, and fusion, and diagnosis supporting adaptive control are examples of advanced technologies that present considerable verification and validation challenges. These systems necessitate interactions between physical and software-based systems that are highly networked with sensing and actuation subsystems, and incorporate technologies that are, in many respects, different from those employed in civil aviation today. A formidable barrier to deploying these advanced technologies in civil aviation is the lack of enabling verification and validation tools, methods, and technologies. The development of new verification and validation capabilities will not only enable the fielding of advanced vehicle health management systems, but will also provide new assurance capabilities for verification and validation of current generation aviation software which has been implicated in anomalous in-flight behavior. This paper describes the research focused on enabling capabilities for verification and validation underway within NASA s Integrated Vehicle Health Management project, discusses the state of the art of these capabilities, and includes a framework for prioritizing activities.

Cooper, Eric G.↗
NASA NTRS1995

An Optimized Integrator Windup Protection Technique Applied to a Turbofan Engine Control

This paper introduces a new technique for providing memoryless integrator windup protection which utilizes readily available optimization software tools. This integrator windup protection synthesis provides a concise methodology for creating integrator windup protection for each actuation system loop independently while assuring both controller and closed loop system stability. The individual actuation system loops' integrator windup protection can then be combined to provide integrator windup protection for the entire system. This technique is applied to an H(exp infinity) based multivariable control designed for a linear model of an advanced afterburning turbofan engine. The resulting transient characteristics are examined for the integrated system while encountering single and multiple actuation limits.

Watts, Stephen R.↗
NASA NTRS2011

External Tank - The Structure Backbone

The External Tank forms the structural backbone of the Space Shuttle in the launch configuration. Because the tank flies to orbital velocity with the Space Shuttle Orbiter, minimization of weight is mandatory, to maximize payload performance. Choice of lightweight materials both for structure and thermal conditioning was necessary. The tank is large, and unique manufacturing facilities, tooling, handling, and transportation operations were required. Weld processes and tooling evolved with the design as it matured through several block changes, to reduce weight. Non Destructive Evaluation methods were used to assure integrity of welds and thermal protection system materials. The aluminum-lithium alloy was used near the end of the program and weld processes and weld repair techniques had to be refined. Development and implementation of friction stir welding was a substantial technology development incorporated during the Program. Automated thermal protection system application processes were developed for the majority of the tank surface. Material obsolescence was an issue throughout the 40 year program. The final configuration and tank weight enabled international space station assembly in a high inclination orbit allowing international cooperation with the Russian Federal Space Agency. Numerous process controls were implemented to assure product quality, and innovative proof testing was accomplished prior to delivery. Process controls were implemented to assure cleanliness in the production environment, to control contaminants, and to preclude corrosion. Each tank was accepted via rigorous inspections, including non-destructive evaluation techniques, proof testing, and all systems testing. In the post STS-107 era, the project focused on ascent debris risk reduction. This was accomplished via stringent process controls, post flight assessment using substantially improved imagery, and selective redesigns. These efforts were supported with a number of test programs to simulate combined environments. Processing improvements included development and use of low spray guns for foam application, additional human factors considerations for production, use of high fidelity mockups during hardware processing with video review, improved tank access, extensive use of non destructive evaluation, and producibility enhancements. Design improvements included redesigned bipod fittings, a bellows heater, a feedline camera active during ascent flight, removal of the protuberance airload ramps, redesigned ice frost ramps, and titanium brackets replaced aluminum brackets on the liquid oxygen feedline. Post flight assessment improved due to significant addition of imagery assets, greatly improving situational awareness. The debris risk was reduced by two orders of magnitude. During this time a major natural disaster was overcome when Katrina damaged the manufacturing facility. Numerous lessons from these efforts are documented within the paper.

Welzyn, Kenneth↗
NASA NTRS2017

Get the Power You Need, When and Where You Need It Aboard the International Space Station (ISS) Using the ISS Plug-In Plan (IPiP) Requirement Request Process

Trying to get your experiment aboard ISS? You likely will need power. Many enditem providers do. ISS Plug-In Plan (IPiP) supports power and data for science, Payloads (or Utilization), vehicle systems, and daily operations through the Electrical Power System (EPS) Secondary Power/Data Subsystem. Yet limited resources and increasing requirements continue to influence decisions on deployment of ISS end items. Given the fluid launch schedule and the rapidly- increasing number of end item providers requiring power support, the focus of the Plug-In Plan has evolved from a simple FIFO recommendation to provide power to end item users, to anticipating future requirements by judicious development and delivery of support equipment (cables, power supplies, power strips, and alternating current (AC) power inverters), employing innovative deployment strategies, and collaborating on end item development. This paper describes the evolution of the ISS Program Office, Engineering Directorate, Flight Operations Directorate (FOD), International Partners and the end item provider relationship and how collaboration successfully leverages unique requirements with limited on- board equipment and resources, tools and processes which result in more agile integration, and describes the process designed for the new ISS end item provider to assure that their power requirements will be met.

Moore, Kevin D.↗
NASA NTRS2002

Architecture-Adaptive Computing Environment: A Tool for Teaching Parallel Programming

Recently, networked and cluster computation have become very popular. This paper is an introduction to a new C based parallel language for architecture-adaptive programming, aCe C. The primary purpose of aCe (Architecture-adaptive Computing Environment) is to encourage programmers to implement applications on parallel architectures by providing them the assurance that future architectures will be able to run their applications with a minimum of modification. A secondary purpose is to encourage computer architects to develop new types of architectures by providing an easily implemented software development environment and a library of test applications. This new language should be an ideal tool to teach parallel programming. In this paper, we will focus on some fundamental features of aCe C.

Dorband, John E.↗
NASA NTRSDate not supplied

Writing Good Risk Statements and Critical Thinking in Risk

The term risk is used ubiquitously in the space community, but more often than not it is used in a counterproductive way. Furthermore, risks are often written to convey some type of concern, but the risk statements are often more emotional in nature than technically substantive. In this talk, we will provide a rigorous view and definition of risk, along with some structured guidelines for writing risk statements centered on critical thinking, which will combine to provide effective risk management tools when dealing with complex space systems.

risk↗
NASA NTRS1996

GOES-8 and -9 mission launch and operations support overview

The new series of geosynchronous operational environmental satellite (GOES) missions, GOES-8 and GOES-9, provide greater instrument coverage flexibility and greater resolution than previous GOES spinners. This added flexibility and the three-axis stabilized operating mode results in control system of increased complexity: almost 5000 real-time commands are sent daily to the satellites compared to 200 commands per day for GOES-7. These advanced technologies present new challenges to the NASA operations support personnel. In order to prepare for launching, post-launch tests and in-orbit operations, a mission planning scheme was developed in order to assure the flight system command and the systems' health monitoring. The mission operations approaches are reviewed together with the associated philosophies and the operation tools developed to assist the personnel in performing complex routine and special operation tasks.

McCuistion, D.↗
NASA NTRS2003

Software Requirements Analysis as Fault Predictor

Waiting until the integration and system test phase to discover errors leads to more costly rework than resolving those same errors earlier in the lifecycle. Costs increase even more significantly once a software system has become operational. WE can assess the quality of system requirements, but do little to correlate this information either to system assurance activities or long-term reliability projections - both of which remain unclear and anecdotal. Extending earlier work on requirements accomplished by the ARM tool, measuring requirements quality information against code complexity and test data for the same system may be used to predict specific software modules containing high impact or deeply embedded faults now escaping in operational systems. Such knowledge would lead to more effective and efficient test programs. It may enable insight into whether a program should be maintained or started over.

Wallace, Dolores↗
NASA NTRS2010

Rapid Response Risk Assessment in New Project Development

A capability for rapidly performing quantitative risk assessments has been developed by JSC Safety and Mission Assurance for use on project design trade studies early in the project life cycle, i.e., concept development through preliminary design phases. A risk assessment tool set has been developed consisting of interactive and integrated software modules that allow a user/project designer to assess the impact of alternative design or programmatic options on the probability of mission success or other risk metrics. The risk and design trade space includes interactive options for selecting parameters and/or metrics for numerous design characteristics including component reliability characteristics, functional redundancy levels, item or system technology readiness levels, and mission event characteristics. This capability is intended for use on any project or system development with a defined mission, and an example project will used for demonstration and descriptive purposes, e.g., landing a robot on the moon. The effects of various alternative design considerations and their impact of these decisions on mission success (or failure) can be measured in real time on a personal computer. This capability provides a high degree of efficiency for quickly providing information in NASA s evolving risk-based decision environment

Graber, Robert R.↗
NASA NTRS2013

Evidence Arguments for Using Formal Methods in Software Certification

We describe a generic approach for automatically integrating the output generated from a formal method/tool into a software safety assurance case, as an evidence argument, by (a) encoding the underlying reasoning as a safety case pattern, and (b) instantiating it using the data produced from the method/tool. We believe this approach not only improves the trustworthiness of the evidence generated from a formal method/tool, by explicitly presenting the reasoning and mechanisms underlying its genesis, but also provides a way to gauge the suitability of the evidence in the context of the wider assurance case. We illustrate our work by application to a real example-an unmanned aircraft system- where we invoke a formal code analysis tool from its autopilot software safety case, automatically transform the verification output into an evidence argument, and then integrate it into the former.

Argumentation↗