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

NASA Audit Follow-up Handbook

This NASA Audit Follow-up Handbook is issued pursuant to the requirements of the Office of Management and Budget (OMB) Circular A-50, Audit Follow-up, dated September 29, 1982. It sets forth policy, uniform performance standards, and procedural guidance to NASA personnel for use when considering reports issued by the Office of Inspector General (OIG), other executive branch audit organizations, the Defense Contract Audit Agency (DCAA), and the General Accounting Office (GAO). It is intended to: specify principal roles; strengthen the procedures for management decisions (resolution) on audit findings and corrective action on audit report recommendations; emphasize the importance of monitoring agreed upon corrective actions to assure actual accomplishment; and foster the use of audit reports as effective tools of management. A flow chart depicting the NASA audit and management decision process is in Appendix A. This handbook is a controlled handbook issued in loose-leaf form and will be revised by page changes. Additional copies for internal use may be obtained through normal distribution channels.

Source record↗

Challenges of Developing New Classes of NASA Self-Managing Mission

NASA is proposing increasingly complex missions that will require a high degree of autonomy and autonomicity. These missions pose hereto unforeseen problems and raise issues that have not been well-addressed by the community. Assuring success of such missions will require new software development techniques and tools. This paper discusses some of the challenges that NASA and the rest of the software development community are facing in developing these ever-increasingly complex systems. We give an overview of a proposed NASA mission as well as techniques and tools that are being developed to address autonomic management and the complexity issues inherent in these missions.

Hinchey, M. G.↗

The Significant Incidents and Close Calls in Human Space Flight Chart: Lessons Learned Gone Viral

This presentation will explore the surprising history and events that transformed a mundane spreadsheet of historical spaceflight incidents into a popular and widely distributed visual compendium of lessons learned. The Significant Incidents and Close Calls in Human Space Flight Chart (a.k.a. The Significant Incidents Chart) is a popular and visually captivating reference product that has arisen from the work of the Johnson Space Center (JSC) Safety and Mission Assurance (S&MA) Flight Safety Office (FSO). It began as an internal tool intended to increase our team s awareness of historical and modern space flight incidents. Today, the chart is widely recognized across the agency as a reference tool. It appears in several training and education programs. It is used in familiarization training in the JSC Building 9 Mockup Facility and is seen by hundreds of center visitors each week. The chart visually summarizes injuries, fatalities, and close calls sustained during the continuing development of human space flight. The poster-sized chart displays over 100 total events that have direct connections to human space flight endeavors. The chart is updated periodically. The update process itself has become a collaborative effort. Many people, spanning multiple NASA organizations, have provided suggestions for additional entries. The FSO maintains a growing list of subscribers who have requested to receive updates. The presenters will discuss the origins and motivations behind the significant incidents chart. A review of the inclusion criteria used to select events will be offered. We will address how the chart is used today by S&MA and offer a vision of how it might be used by other organizations now and in the future. Particular emphasis will be placed on features of the chart that have met with broad acceptance and have helped spread awareness of the most important lessons in human spaceflight.

Wood, Bill↗

Progressively Enabling Earth Independent Medical Operations (EIMO)

This panel presents the findings from a series of Technical Interchange Meetings (TIMs) hosted by the Exploration Medical Capability Element (ExMC) in NASA’s Human Research Program. The topics for the TIMs were derived from a 2-day conference of senior leaders and subject matters experts that collectively outlined a multi-faceted strategy designed to optimize crew health and performance through an increasingly autonomous medical approach. The first abstract in this panel outlines the scope of issues related to data collection, usage, transmission and computing capacity to facilitate EIMO. The second presentation provides an overview of the challenges in developing curricula and advanced training tools to baseline knowledge, skills and abilities (KSA), verify clinical competency and assure retention during prolonged durations inherent in exploration-class missions. An overview of the complicated medical supply and resource chain necessary to facilitate EIMO is provided in the third presentation of this panel. The final presentation in this EIMO panel surveys the breadth and depth of demands on cognitive load expected to be experienced by crew on an exploration mission and proposes strategies to mitigate the prospect of cognitive overload through methods to shift task load from the crew to multi-modal artificial intelligence based medical support systems. Taken together, these presentations summarize the challenges to be expected and potential solution spaces to be explored and developed to progressively enable increasing autonomous medical operations to support crewed missions beyond low earth orbit. Through EIMO focused pre-mission planning, integrated data architecture design, innovative training development and AI-assisted task load management, the gradual transition of medical care and decision making from terrestrial to space-based assets enabling support of astronaut health and performance and reducing overall mission risk is achievable.

Jay Lemery↗

Progressively Enabling Earth Independent Medical Operations (EIMO)

This panel presents the findings from a series of Technical Interchange Meetings (TIMs) hosted by the Exploration Medical Capability Element (ExMC) in NASA’s Human Research Program. The topics for the TIMs were derived from a 2-day conference of senior leaders and subject matters experts that collectively outlined a multi-faceted strategy designed to optimize crew health and performance through an increasingly autonomous medical approach. The first abstract in this panel outlines the scope of issues related to data collection, usage, transmission and computing capacity to facilitate EIMO. The second presentation provides an overview of the challenges in developing curricula and advanced training tools to baseline knowledge, skills and abilities (KSA), verify clinical competency and assure retention during prolonged durations inherent in exploration-class missions. An overview of the complicated medical supply and resource chain necessary to facilitate EIMO is provided in the third presentation of this panel. The final presentation in this EIMO panel surveys the breadth and depth of demands on cognitive load expected to be experienced by crew on an exploration mission and proposes strategies to mitigate the prospect of cognitive overload through methods to shift task load from the crew to multi-modal artificial intelligence based medical support systems. Taken together, these presentations summarize the challenges to be expected and potential solution spaces to be explored and developed to progressively enable increasing autonomous medical operations to support crewed missions beyond low earth orbit. Through EIMO focused pre-mission planning, integrated data architecture design, innovative training development and AI-assisted task load management, the gradual transition of medical care and decision making from terrestrial to space-based assets enabling support of astronaut health and performance and reducing overall mission risk is achievable.

John Lemery↗

Recommendations on Evidence and Process for Certification of Learning-enabled Components in Aerospace Systems

This report primarily identifies a collection of relevant and necessary evidence for assurance of machine learnt components (MLCs)—also known as learning-enabled components—integrated into aircraft systems, and gives preliminary suggestions on the elements of a certification process that invoke the identified evidence. The main focus is on feedforward neural networks that are static and trained offline through supervised learning. A brief background on the generic elements of the lifecycle of an MLC is given to contextualize the assurance considerations and, consequently, the evidence that is relevant and necessary to support certification. At the level of an MLC, those considerations relate to: (i) the consistency and correctness of MLC contributions to system functions in the context of a validated functional intent; and (ii) the absence of MLC contributions to aircraft-level failure conditions. At an ML model level, confidence in model and data properties contribute to assurance of the containing MLC, in particular: (a) generalizability and robustness of models, in the presence of inputs not previously seen during training, disturbances to inputs, and unexpected inputs; and (b) valid data, i.e., data that are at least representative, relevant, complete, and accurate. Evidence for the above span the elements of the ML lifecycle, and includes, at a minimum, lifecycle artifacts that pertain to: (1) properties of requirements capturing functional intent, safety constraints, and aspects of the intended use and operating environment; (2) model performance, model complexity and design, and algorithm choice; (3) achievement of required performance at the levels of a trained model during model development, a trained model after model development is complete, and a trained model that is transformed into an executable equivalent; (4) model implementation aspects necessary for transforming a trained model into the executable equivalent; (5) integration of the executable trained model into the containing MLC, and eventually the larger system; and, (6) lastly, the verification and validation (V&V) of each of the above. Such V&V lifecycle artifacts themselves include: aspects of coverage, e.g., of various levels of requirements by the input space of the model and the data; traceability (where applicable); application of formal methods for property specification, analysis, and checking. Examples of evidence generation methods and tools further ground the discussion on what constitutes evidence, and the contribution to assurance during certification. The identified assurance considerations and supporting evidence is not a comprehensive set. Additionally, neither what should be considered as sufficient evidence relative to the assigned criticality of an MLC, nor how criticality ought to be determined and adjusted, have been considered in this report. However, suggestions are made for potential activities of the ML lifecycle that are aimed at providing confidence that an MLC can be relied upon when integrated into its containing (aircraft) system. Those activities are proposed as candidate elements of a certification process for MLCs. The main purpose of this report to inform regulatory guidance and consensus standards that may be used to meet the safety intent of the applicable regulations.

Aviation safety↗

Radiation Data Collection and Risk Assessment

In order to advance the approach for parts assurance in the space community to the current decade and to remain nimble for the future, NASA GSFC, in collaboration with the Aerospace Corporation’s Mission Success Improvement Workshop and broad space community participation, has been reviewing and categorizing 40 years’ worth of on-orbit anomaly data to support broad assessments of radiation-related risk and the development of tools to rigorously assess risk in general project situations. Part of the changing approach in parts assurance involves phasing in the use of COTS parts (or as preferred, alternate grade parts). This talk will convey some of the early findings of the effort, including the fact that expanded use of COTS parts does not increase radiation-related risk, while also pointing out that a very small percentage of parts in a typical parts list are actives and thus require radiation assessment. These are important because they remove radiation as a factor in broad consideration in the use of COTS, without diminishing the importance of addressing the effects of radiation in space.

risk↗

A Survey of Formal Methods for Intelligent Swarms

Swarms of intelligent autonomous spacecraft, involving complex behaviors and interactions, are being proposed for future space exploration missions. Such missions provide greater flexibility and offer the possibility of gathering more science data than traditional single spacecraft missions. The emergent properties of swarms make these missions powerful, but simultaneously far more difficult to design, and to assure that the proper behaviors will emerge. These missions are also considerably more complex than previous types of missions, and NASA, like other organizations, has little experience in developing or in verifying and validating these types of missions. A significant challenge when verifying and validating swarms of intelligent interacting agents is how to determine that the possible exponential interactions and emergent behaviors are producing the desired results. Assuring correct behavior and interactions of swarms will be critical to mission success. The Autonomous Nano Technology Swarm (ANTS) mission is an example of one of the swarm types of missions NASA is considering. The ANTS mission will use a swarm of picospacecraft that will fly from Earth orbit to the Asteroid Belt. Using an insect colony analogy, ANTS will be composed of specialized workers for asteroid exploration. Exploration would consist of cataloguing the mass, density, morphology, and chemical composition of the asteroids, including any anomalous concentrations of specific minerals. To perform this task, ANTS would carry miniaturized instruments, such as imagers, spectrometers, and detectors. Since ANTS and other similar missions are going to consist of autonomous spacecraft that may be out of contact with the earth for extended periods of time, and have low bandwidths due to weight constraints, it will be difficult to observe improper behavior and to correct any errors after launch. Providing V&V (verification and validation) for this type of mission is new to NASA, and represents the cutting edge in system correctness, and requires higher levels of assurance than other (traditional) missions that use a single or small number of spacecraft that are deterministic in nature and have near continuous communication access. One of the highest possible levels of assurance comes from the application of formal methods. Formal methods are mathematics-based tools and techniques for specifying and verifying (software and hardware) systems. They are particularly useful for specifying complex parallel systems, such as exemplified by the ANTS mission, where the entire system is difficult for a single person to fully understand, a problem that is multiplied with multiple developers. Once written, a formal specification can be used to prove properties of a system (e.g., the underlying system will go from one state to another or not into a specific state) and check for particular types of errors (e.g., race or livelock conditions). A formal specification can also be used as input to a model checker for further validation. This report gives the results of a survey of formal methods techniques for verification and validation of space missions that use swarm technology. Multiple formal methods were evaluated to determine their effectiveness in modeling and assuring the behavior of swarms of spacecraft using the ANTS mission as an example system. This report is the first result of the project to determine formal approaches that are promising for formally specifying swarm-based systems. From this survey, the most promising approaches were selected and are discussed relative to their possible application to the ANTS mission. Future work will include the application of an integrated approach, based on the selected approaches identified in this report, to the formal specification of the ANTS mission.

Truszkowski, Walt↗

Testing, Requirements, and Metrics

The criticality of correct, complete, testable requirements is a fundamental tenet of software engineering. Also critical is complete requirements based testing of the final product. Modern tools for managing requirements allow new metrics to be used in support of both of these critical processes. Using these tools, potential problems with the quality of the requirements and the test plan can be identified early in the life cycle. Some of these quality factors include: ambiguous or incomplete requirements, poorly designed requirements databases, excessive or insufficient test cases, and incomplete linkage of tests to requirements. This paper discusses how metrics can be used to evaluate the quality of the requirements and test to avoid problems later. Requirements management and requirements based testing have always been critical in the implementation of high quality software systems. Recently, automated tools have become available to support requirements management. At NASA's Goddard Space Flight Center (GSFC), automated requirements management tools are being used on several large projects. The use of these tools opens the door to innovative uses of metrics in characterizing test plan quality and assessing overall testing risks. In support of these projects, the Software Assurance Technology Center (SATC) is working to develop and apply a metrics program that utilizes the information now available through the application of requirements management tools. Metrics based on this information provides real-time insight into the testing of requirements and these metrics assist the Project Quality Office in its testing oversight role. This paper discusses three facets of the SATC's efforts to evaluate the quality of the requirements and test plan early in the life cycle, thus preventing costly errors and time delays later.

Rosenberg, Linda↗

Experience Report: A Do-It-Yourself High-Assurance Compiler

Embedded domain-specific languages (EDSLs) are an approach for quickly building new languages while maintaining the advantages of a rich metalanguage. We argue in this experience report that the "EDSL approach" can surprisingly ease the task of building a high-assurance compiler.We do not strive to build a fully formally-verified tool-chain, but take a "do-it-yourself" approach to increase our confidence in compiler-correctness without too much effort. Copilot is an EDSL developed by Galois, Inc. and the National Institute of Aerospace under contract to NASA for the purpose of runtime monitoring of flight-critical avionics. We report our experience in using type-checking, QuickCheck, and model-checking "off-the-shelf" to quickly increase confidence in our EDSL tool-chain.

Pike, Lee↗

Check-Cases for Verification of 6-Degree-of-Freedom Flight Vehicle Simulations

The rise of innovative unmanned aeronautical systems and the emergence of commercial space activities have resulted in a number of relatively new aerospace organizations that are designing innovative systems and solutions. These organizations use a variety of commercial off-the-shelf and in-house-developed simulation and analysis tools including 6-degree-of-freedom (6-DOF) flight simulation tools. The increased affordability of computing capability has made highfidelity flight simulation practical for all participants. Verification of the tools' equations-of-motion and environment models (e.g., atmosphere, gravitation, and geodesy) is desirable to assure accuracy of results. However, aside from simple textbook examples, minimal verification data exists in open literature for 6-DOF flight simulation problems. This assessment compared multiple solution trajectories to a set of verification check-cases that covered atmospheric and exo-atmospheric (i.e., orbital) flight. Each scenario consisted of predefined flight vehicles, initial conditions, and maneuvers. These scenarios were implemented and executed in a variety of analytical and real-time simulation tools. This tool-set included simulation tools in a variety of programming languages based on modified flat-Earth, round- Earth, and rotating oblate spheroidal Earth geodesy and gravitation models, and independently derived equations-of-motion and propagation techniques. The resulting simulated parameter trajectories were compared by over-plotting and difference-plotting to yield a family of solutions. In total, seven simulation tools were exercised.

Murri, Daniel G.↗

The SPASE Data Model: A Metadata Standard for Registering, Finding, Accessing, and Using Heliophysics Data Obtained from Observations and Modeling

The Space Physics Archive Search and Extract Consortium has developed and implemented the SPASE Data Model that provides a common language for registering a wide range of Heliophysics data and other products. The Data Model enables discovery and access tools such that any researcher can obtain data easily, thereby facilitating research, including on space weather. The Data Model includes descriptions of Simulation Models and Numerical Output, pioneered by the Integrated Medium for Planetary Exploration (IMPEx) group in Europe, and subsequently adopted by the Community Coordinated Modeling Center (CCMC). The SPASE group intends to register all relevant Heliophysics data resources, including space-, ground-, and model-based. Substantial progress has been made, especially for space-based observational data and associated observatories, instruments, and display data. Legacy product registrations and access go back more than 50 years. Real-time data will be included. The National Aeronautics and Space Administration (NASA) portion of the SPASE group has funding that assures continuity in the upkeep of the Data Model and aids with adding new products. Tools are being developed for making and editing data descriptions. Digital Object Identifiers (DOIs) for Data Products can now be included in the descriptions. The data access that SPASE facilitates is becoming more uniform, and work is progressing on Web Service access via a standard Application Programming Interface. The SPASE Data Model is stable; changes over the past 9 years were additions of terms and capabilities that are backward compatible. This paper provides a summary of the history, structure, use, and future of the SPASE Data Model.

Roberts, D. Aaron↗

Addressing Uniqueness and Unison of Reliability and Safety for a Better Integration

Over time, it has been observed that Safety and Reliability have not been clearly differentiated, which leads to confusion, inefficiency, and, sometimes, counter-productive practices in executing each of these two disciplines. It is imperative to address this situation to help Reliability and Safety disciplines improve their effectiveness and efficiency. The paper poses an important question to address, "Safety and Reliability - Are they unique or unisonous?" To answer the question, the paper reviewed several most commonly used analyses from each of the disciplines, namely, FMEA, reliability allocation and prediction, reliability design involvement, system safety hazard analysis, Fault Tree Analysis, and Probabilistic Risk Assessment. The paper pointed out uniqueness and unison of Safety and Reliability in their respective roles, requirements, approaches, and tools, and presented some suggestions for enhancing and improving the individual disciplines, as well as promoting the integration of the two. The paper concludes that Safety and Reliability are unique, but compensating each other in many aspects, and need to be integrated. Particularly, the individual roles of Safety and Reliability need to be differentiated, that is, Safety is to ensure and assure the product meets safety requirements, goals, or desires, and Reliability is to ensure and assure maximum achievability of intended design functions. With the integration of Safety and Reliability, personnel can be shared, tools and analyses have to be integrated, and skill sets can be possessed by the same person with the purpose of providing the best value to a product development.

Huang, Zhaofeng↗

Applying Generative-AI to NASA Documentation and Processes

This research and development project leverages generative-AI to assist in the generation of software process documentation based on NASA standards. By utilizing fine-tuned AI models, the proposed system will analyze NASA's software guidelines, helping to translate them into well-structured, compliant process documents. This assistance can reduce the manual effort required to produce such documentation, enhance consistency, and assure alignment with NASA's stringent software development and operational requirements. In addition to assisting in the generation of software process documentation, the project explores how generative-AI can help create audit checklists as well as assess the compliance of NASA provider documentation against applicable NASA standards. This approach would support the compliance auditing process, providing real-time insights and assessments. The intended result will be a streamlined process, potentially including a Python-based tool and database, that improves audit efficiency, reduces human error, lowers manpower costs and required manhours, and assures continuous compliance with NASA and industry evolving standards for safety-critical software development. Future task might be to investigate the software industry approach and standards for potential collaboration.

NASA Standards↗

Fiber optic combiner and duplicator

The investigation of the possible development of two optical devices, one to take two images as inputs and to present their arithmetic sum as a single output, the other to take one image as input and present two identical images as outputs is described. Significant engineering time was invested in establishing precision fiber optics drawing capabilities, real time monitoring of the fiber size and exact measuring of fiber optics ribbons. Various assembly procedures and tooling designs were investigated and prototype models were built and evaluated that established technical assurance that the device was feasible and could be fabricated. Although the interleaver specification in its entirety was not achieved, the techniques developed in the course of the program improved the quality of images transmitted by fiber optic arrays by at least an order of magnitude. These techniques are already being applied to the manufacture of precise fiber optic components.

Source record↗

Space station common module power system network topology and hardware development

Candidate power system newtork topologies for the space station common module are defined and developed and the necessary hardware for test and evaluation is provided. Martin Marietta's approach to performing the proposed program is presented. Performance of the tasks described will assure systematic development and evaluation of program results, and will provide the necessary management tools, visibility, and control techniques for performance assessment. The plan is submitted in accordance with the data requirements given and includes a comprehensive task logic flow diagram, time phased manpower requirements, a program milestone schedule, and detailed descriptions of each program task.

Landis, D. M.↗

Terminal - Tactical Separation Assured Flight Environment (T-TSafe)

The Tactical Separation Assured Flight Environment (TSAFE) has been previously tested as a conflict detection and resolution tool in the en-route phase of flight. Fast time simulations of a terminal version of this tool called Terminal TSAFE (T-TSAFE) have shown promise over the current conflict detection tools. It has shown to have fewer false alerts (as low as 2 per hour) and better prediction to conflict time than Conflict Alert. The tool will be tested in the simulated terminal area of Los Angeles International Airport, in a Human-in-the-loop experiment to identify controller procedures and information requirements. The simulation will include comparisons of T-TSAFE with NASA's version of Conflict Alert. Also, some other variables such as altitude entry by the controller, which improve T-TSAFE's predictions for conflict detection, will be tested. T-TSAFE integrates features of current conflict detection tools such as Automated Terminal Proximity Alert used to alleviate compression errors in the final approach phase. Based on fast-time simulation analysis, the anticipated benefits of T-TSAFE over Conflict Alert include reduced false/missed alerts and increased time to predicted loss of separation. Other metrics that will be used to evaluate the tool's impact on the controller include controller intervention, workload, and situation awareness.

Verma, Savita Arora↗

NASA Blue Team: Determining Operational Security Posture of Critical Systems and Networks

Emergence of Cybersecurity has increased the focus on security risks to Information Technology (IT) assets going beyond traditional Information Assurance (IA) concerns: More sophisticated threats have emerged from increasing sources as advanced hacker tools and techniques have emerged and proliferated to broaden the attack surface available across globally interconnected networks.

cybersecurity↗