Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Development assurance”

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 595 records · Page 33
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Psychophysiological Methods to Assess Pilot Productive Safety Behaviors

The NASA System-Wide Safety (SWS) Project is focused on developing new technologies and operational concepts for the aviation industry to meet the increasing global demand while maintaining the current ultra-safe system safety levels. To achieve this, the SWS Project is developing research priorities, including In-time System-wide Safety Assurance (ISSA) and In-time Aviation Safety Management System (IASMS; Ellis et al., 2019). A critical component of the IASMS is the human as pilot and in other roles in aviation operations as demonstrated by SWS human factors research on rare occurrences of human error and the far more prevalent human safety producing behaviors (e.g., Hollnagel, 2016). The talk presented by Chad Stephens of NASA Langley Research Center and NASA SWS Project will describe the history of human factors research involving psychophysiological and biocybernetics methods supporting aviation safety conducted at NASA. Specific examples of recent NASA crew state monitoring research focused on a psychophysiological assessment method and system to enable Training for Attention Management will be demonstrated. Current SWS research including the SWS Operations and Technologies for Enabling Resilient In-Time Assurance (SOTERIA) flight simulation study and a data testbed created to enable study of Human Contributions to Safety (HC2S) will be presented. Ongoing collaborative research efforts with Boeing researchers will be highlighted and opportunities for further collaboration will be discussed.

psychophysiology↗
DOE OSTI2022

Evaluation of Improvements in Storage Efficiencies, Containment, Assurance, CO 2 Plume Movement, and Verification of Storage Technologies

This report summarizes some of the evolving improvements in key technical skills that are developing to support a large-scale commercial application of CCS as well as support rapidly increasing interest in carbon negative technologies. It does not attempt to review relatively well-known processes and procedures that are familiar to many CCS experts; rather focuses on novel concepts that have the potential to provide breakthroughs and add high benefit as projects evolve. Some elements described are in development or not yet proven ideas for which we provide an expression of status of confidence at the time of writing. Topics covered are evaluation of improvements in storage efficiency estimation, containment assurance methods, CO 2 plume movement and pressure prediction, and monitoring and verification of storage methods.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS2019

NASA Electronic Parts and Packaging (NEPP) Program: Overview and Technology Focus Areas - Responsive Technology Assurance for Civil Space

NASA Electronic Parts and Packaging (NEPP) Program Overview and Technology Highlights – The NEPP Program provides NASA's leadership for developing and maintaining guidance for the screening, qualification, test, and reliable use of electrical, electronic, and electromechanical parts by NASA, in collaboration with other government agencies and industry. The NASA Electronic Parts Assurance Group (NEPAG) is a core portion of NEPP. This presentation highlights key focus areas for 2019.

radiation effects↗
NASA NTRS1991

NASA Software Documentation Standard

The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. The basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗
NASA NTRS2006

Infusing Software Assurance Research Techniques into Use

Research in the software engineering community continues to lead to new development techniques that encompass processes, methods and tools. However, a number of obstacles impede their infusion into software development practices. These are the recurring obstacles common to many forms of research. Practitioners cannot readily identify the emerging techniques that may benefit them, and cannot afford to risk time and effort evaluating and trying one out while there remains uncertainty about whether it will work for them. Researchers cannot readily identify the practitioners whose problems would be amenable to their techniques, and, lacking feedback from practical applications, are hard-pressed to gauge the where and in what ways to evolve their techniques to make them more likely to be successful. This paper describes an ongoing effort conducted by a software engineering research infusion team established by NASA s Software Engineering Initiative to overcome these obstacles. .

Pressburger, Thomas↗
NASA NTRS2005

Infusing software assurance research techniques into use

Research in the software engineering community continues to lead to new development techniques that encompass processes, methods and tools. However, a number of obstacles impede their infusion into software deveopment practices. This paper describes an ongoing effort conducted by a software engineering research infusion team established by NASA's Software Engineering Intiative to overcome these obstacles.

Trevino, Luis C.↗
NASA NTRS2015

Advanced Ground Systems Maintenance Prognostics Project

The project implements prognostics capabilities to predict when a component system or subsystem will no longer meet desired functional or performance criteria, called the end of life. The capability also provides an assessment of the remaining useful life of a hardware component. The project enables the delivery of system health advisories to ground system operators. This project will use modeling techniques and algorithms to assess components' health andpredict remaining life for such components. The prognostics capability being developed will beused:during the design phase and during pre/post operations to conduct planning and analysis ofsystem design, maintenance & logistics plans, and system/mission operations plansduring real-time operations to monitor changes to components' health and assess their impacton operations.This capability will be interfaced to Ground Operations' command and control system as a part ofthe AGSM project to help assure system availability and mission success. The initial modelingeffort for this capability will be developed for Liquid Oxygen ground loading applications.

Prognostics↗
DOE OSTI2025

Software Quality Assurance for the MOOSE-Based Open-Source Multiphysics Code Cardinal - An Expanded CI Testing Suite

Cardinal is a wrapping of the GPU-oriented spectral element Computational Fluid Dynamics (CFD) code NekRS and the Monte Carlo particle transport code OpenMC within the Multiphysics Object-Oriented Simulation Environment (MOOSE). Cardinal provides high-resolution thermal-hydraulics and/or radiation transport feedback to MOOSE multiphysics simulations. Multiphysics feedback is implemented in a geometry-agnostic manner which eliminates the need for rigid one-to-one mappings. A generic data transfer implementation also allows NekRS and OpenMC to couple to any MOOSE application, enabling a broad set of multiphysics capabilities. Cardinal simulations can also leverage combinations of MPI, OpenMP, and GPU resources. Cardinal continuous development and improvement efforts have led to the software being considered as a high-fidelity design and licensing tool for key areas of nuclear reactor relevant physics, including neutron transport, fluid flow, heat transfer, and mechanical processes. The fast development and expansion of the software from a pure R&D framework towards its application in the nuclear industry and regulation require a focus on developing, enhancing and, maintaining Cardinal’s software quality through strict adherence to a Software Quality Assurance (SQA) framework and SQA program. To facilitate compliance with SQA standards, the Cardinal SQA Program has been initiated during Fiscal Year 2023 (FY23). During the development of the Cardinal SQA Program, multiple gaps have been identified. These gaps are primarily related to model verification and code pedigree as they relate to the use of Cardinal as a safety analysis tool. These gaps have been captured in a report published in 2023. A second report highlighted the progress made during Fiscal Year 2024 (FY24) and described Argonne’s effort to document and integrate software verification within Cardinal’s software development process. This report documents a snapshot of the verification test cases currently available for Cardinal and NekRS in their assimilation into a Continuous Integration (CI) platform. Following the CI practice permits the integrating of source code changes frequently and ensuring that the integrated codebase clears the verification testing for the software. It should be noted that the SQA program itself, including the program plans, procedures, configuration management, and testing strategies, need to be developed in a future step of this task.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS2010

Automated Conflict Resolution, Arrival Management and Weather Avoidance for ATM

The paper describes a unified solution to three types of separation assurance problems that occur in en-route airspace: separation conflicts, arrival sequencing, and weather-cell avoidance. Algorithms for solving these problems play a key role in the design of future air traffic management systems such as NextGen. Because these problems can arise simultaneously in any combination, it is necessary to develop integrated algorithms for solving them. A unified and comprehensive solution to these problems provides the foundation for a future air traffic management system that requires a high level of automation in separation assurance. The paper describes the three algorithms developed for solving each problem and then shows how they are used sequentially to solve any combination of these problems. The first algorithm resolves loss-of-separation conflicts and is an evolution of an algorithm described in an earlier paper. The new version generates multiple resolutions for each conflict and then selects the one giving the least delay. Two new algorithms, one for sequencing and merging of arrival traffic, referred to as the Arrival Manager, and the other for weather-cell avoidance are the major focus of the paper. Because these three problems constitute a substantial fraction of the workload of en-route controllers, integrated algorithms to solve them is a basic requirement for automated separation assurance. The paper also reviews the Advanced Airspace Concept, a proposed design for a ground-based system that postulates redundant systems for separation assurance in order to achieve both high levels of safety and airspace capacity. It is proposed that automated separation assurance be introduced operationally in several steps, each step reducing controller workload further while increasing airspace capacity. A fast time simulation was used to determine performance statistics of the algorithm at up to 3 times current traffic levels.

Erzberger, H.↗
NASA NTRS2011

Software Development Standard Processes (SDSP)

A JPL-created set of standard processes is to be used throughout the lifecycle of software development. These SDSPs cover a range of activities, from management and engineering activities, to assurance and support activities. These processes must be applied to software tasks per a prescribed set of procedures. JPL s Software Quality Improvement Project is currently working at the behest of the JPL Software Process Owner to ensure that all applicable software tasks follow these procedures. The SDSPs are captured as a set of 22 standards in JPL s software process domain. They were developed in-house at JPL by a number of Subject Matter Experts (SMEs) residing primarily within the Engineering and Science Directorate, but also from the Business Operations Directorate and Safety and Mission Success Directorate. These practices include not only currently performed best practices, but also JPL-desired future practices in key thrust areas like software architecting and software reuse analysis. Additionally, these SDSPs conform to many standards and requirements to which JPL projects are beholden.

Lavin, Milton L.↗
NASA NTRS2016

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗
NASA NTRS2010

A Heuristic Model of Consciousness with Applications to the Development of Science and Society

A working model of consciousness is fundamental to understanding of the interactions of the observer in science. This paper examines contemporary understanding of consciousness. A heuristic model of consciousness is suggested that is consistent with psycophysics measurements of bandwidth of consciousness relative to unconscious perception. While the self reference nature of consciousness confers a survival benefit by assuring the all points of view regarding a problem are experienced in sufficiently large population, conscious bandwidth is constrained by design to avoid chaotic behavior. The multiple hypotheses provided by conscious reflection enable the rapid progression of science and technology. The questions of free will and the problem of attention are discussed in relation to the model. Finally the combination of rapid technology growth with the assurance of many unpredictable points of view is considered in respect to contemporary constraints to the development of society.

Curreri, Peter A.↗
NASA NTRS1983

Productivity in an evolutionary space station

Space station productivity is treated from a systems point of view, considering the functions and attributes of space station development, formation, and operation that affect productivity. An optimum planning method is needed to assure that the station will have mission flexibility, technology advancement, maintainability, and evolutionary capability. Advanced technology will be designed into the housekeeping and utility functions of the station. Greater risk taking may be allowed into designs if the potential benefits of the advanced system support the risk, and if the system can be buffered from causing a failure cascade throughout the station. A common data base is needed to store and track all designs, developments, and changes in the station subsystems. Systems that can be automated and free the human inhabitants for more productive work are favored, as are modular components that are highly fault-free. Human control must also be possible, especially during check-out and verification, and also for teaching the automated systems new or modified tasks.

Anderson, J. L.↗
NASA NTRS2000

X-33, Stepping Stone ot Low Cost Access to Space

In response to the Access to Space Study, which was conducted in 1993 through the Office of Space Systems Development, an advanced technology Reusable Launch Vehicle (RLV) was selected for demonstration. The X-33 was advanced as an demonstration project, to build and test a 53-percent scale prototype of an operational RLV, it would also demonstrate new technologies which would be required to assure the operation of the new RLV. This presentation reviews the progress of the X-33 development and supporting sites. The X-33 design has been completed and fabrication and assembly is progressing well. The X-33 launch site has been completed. The first LH2 tank and engine is in testing. This will lead to the full scale development of VentureStar(tm).

Naftel, J. Chris↗
NASA NTRS2011

External Tank Program - Legacy of Success

The largest single element of Space Shuttle is the External Tank (ET), which serves as the structural backbone of the vehicle during ascent and provides liquid propellants to the Orbiter s three Main Engines. The ET absorbs most of the seven million pounds of thrust exerted by the Solid Rocket Boosters and Main Engines. The design evolved through several block changes, reducing weight each time. Because the tank flies to orbital velocity with the Space Shuttle Orbiter, minimization of weight is mandatory, to maximize payload performance. The initial configuration, the standard weight tank, weighed 76,000 pounds and was an aluminum 2219 structure. The light weight tank weighed 66,000 pounds and flew 86 missions. The super light weight tank weighed 58,500 pounds and was primarily an aluminum-lithium structure. The final configuration and low weight enabled system level performance sufficient for assembly of the International Space Station in a high inclination orbit, vital for international cooperation. Another significant challenge was the minimization of ice formation on the cryogenic tanks. This was essential due to the system configuration and the choice of ceramic thermal protection system materials on the Orbiter. Ice would have been a major debris hazard. Spray on foam insulation materials served multiple functions including thermal insulation, conditioning of cryogenic propellants, and thermal protection for the tank structure during ascent and entry. The tank is large, and unique manufacturing facilities, tooling, and handling, and transportation operations were developed. Weld processes and tooling evolved with the design as it matured through several block changes. 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 multi-decade program. 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. The debris risk was reduced by two orders of magnitude. During this time a major natural disaster was overcome when hurricane Katrina damaged the manufacturing facility. Numerous lessons from these efforts, the manufacturing and material processing issues, the key design features, and evolution of the design will be discussed.

Pilet, Jeffery C.↗
DOE OSTI2022

Nuclide inventory validation: radiochemical assay data quality and modeling challenges in benchmark models development

Oak Ridge National Laboratory is conducting radiochemical assay experiments, using high-precision analytical protocols validated with a comprehensive quality assurance plan, to expand the nuclide inventory validation basis for high burnup spent nuclear fuel. Preliminary measurement data for key actinides and fission products in two pressurized water reactor spent fuel samples are being used to investigate the impact of measurement data uncertainty on the sample burnup estimation. These measurement data are also being used to examine the impact of assumptions applied when developing best-estimate computational models to simulate fuel irradiation history. The simulations are being performed using depletion capabilities in the SCALE code system. Comparison of calculated and measured nuclide concentrations shows good agreement for the considered nuclides. (authors)

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
DOE OSTI2025

Applications of Federated Learning in Semiconductor Manufacturing [Poster]

As semiconductor manufacturers explore advanced data analytics and modeling techniques and data hungry machine learning models increase in popularity due to their accuracy in solving generalized problems and ability to learn complex relationships, federated learning emerges as a privacy preserving machine learning technique for preserving data privacy and ensuring intellectual property protection. Federated Learning is a machine learning technique focused on training models using distributed data that never needs to be centrally stored, allowing the use of advanced machine learning techniques without compromising data privacy, and in the semiconductor manufacturing industry advanced machine learning techniques can reduce cost and time, but maintaining data privacy is essential to maintaining a competitive advantage. This paper systematically reviews existing literature on applications of federated learning in the semiconductor manufacturing industry with a focus on identifying common themes, algorithms, and gaps within the literature to drive future research directions. The findings reveal five key themes, including improvements in quality assurance, virtual models, privacy preservation, reliable data practices, and emerging trends and developments. By identifying key themes in literature on federated learning and semiconductor manufacturing and analyzing gaps and discussed methodologies, this study highlights several potential future research directions to expand the application of federated learning techniques in the semiconductor manufacturing domain.

42 ENGINEERING↗
NASA NTRS1976

Quality assurance program guidelines for application to and use by manufacturers of rail/guideway vehicles, buses, automatic train control systems, and their major subsystems

Guidelines are presented for a quality assurance system to be implemented by the manufacturer in support of designing, developing, fabricating, assembling, inspecting, testing, handling, and delivery of equipment being procured for use in public urban mass transit systems. The guidelines apply to this equipment when being procured for: (1) use in revenue service; (2) demonstration of systems that will be revenue producing or used by the public; (3) use as a prototype for follow-on operational/revenue producing equipment procurements; and (4) qualification tests.

Witkin, S. A.↗