SEARCH · Engineering Papers

Results for “software reliability”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 469 records · Page 26

All sources NASA NTRS DOE OSTI

DOE OSTI2019

Probabilistic Risk Assessment of Flexible Power Operation of a Nuclear Power Plant

Nuclear power plants (NPPs) are becoming cost prohibitive to operate. This is due to historically low natural gas prices and wind and solar prices often being less than the marginal cost of operating baseload coal and NPPs, which sometimes forces NPPs to pay for the electricity they create. Thus, the feasibility of using part of the heat from an NPP to create other commodities such as hydrogen is being evaluated; operating in this way is called flexible power operation (FPO). To change the NPP design and operation, a license review must happen. Part of the review is the Probabilistic Risk Assessment (PRA) which proves the safety of the design and operation by identifying sequences of events that result in plant failure and estimating their likelihood of occurrence. A Level 1 PRA model that evaluates the risk of removing heat from the secondary side of NPP was created. The model was developed using Systems Analysis Program for Hands-On Integrated Reliability Evaluations (SAPHIRE 8) software to calculate core damage frequency (CDF). It is a fault tree that represents the possible pathways that could lead to a loss of steam inventory in the secondary loop. A loss of steam inventory can induce steam generator tube rupture or other events that activates response systems to avoid core damage. This is the main concern for the Nuclear Regulatory Commission (NRC), the group in the United States that licenses NPPs. This model will calculate a total CDF of any of these pathways occurring which will be compared to the baseline CDF in a generic NPP PRA for licensing support.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

NASA NTRS1998

Credible Software and Simulation Uncertainty

The utility of software primarily depends on its reliability and performance; whereas, its significance depends solely on its credibility for intended use. The credibility of simulations confirms the credibility of software. The level of veracity and the level of validity of simulations determine the degree of credibility of simulations. The process of assessing this credibility in fields such as computational mechanics (CM) differs from that followed by the Defense Modeling and Simulation Office in operations research. Verification and validation (V&V) of CM simulations is not the same as V&V of CM software. Uncertainty is the measure of simulation credibility. Designers who use software are concerned with management of simulation uncertainty. Terminology and concepts are presented with a few examples from computational fluid dynamics.

Mehta, Unmeel B.↗

NASA NTRS2004

Automating Structural Analysis of Spacecraft Vehicles

A major effort within NASA's vehicle analysis discipline has been to automate structural analysis and sizing optimization during conceptual design studies of advanced spacecraft. Traditional spacecraft structural sizing has involved detailed finite element analysis (FEA) requiring large degree-of-freedom (DOF) finite element models (FEM). Creation and analysis of these models can be time consuming and limit model size during conceptual designs. The goal is to find an optimal design that meets the mission requirements but produces the lightest structure. A structural sizing tool called HyperSizer has been successfully used in the conceptual design phase of a reusable launch vehicle and planetary exploration spacecraft. The program couples with FEA to enable system level performance assessments and weight predictions including design optimization of material selections and sizing of spacecraft members. The software's analysis capabilities are based on established aerospace structural methods for strength, stability and stiffness that produce adequately sized members and reliable structural weight estimates. The software also helps to identify potential structural deficiencies early in the conceptual design so changes can be made without wasted time. HyperSizer's automated analysis and sizing optimization increases productivity and brings standardization to a systems study. These benefits will be illustrated in examining two different types of conceptual spacecraft designed using the software. A hypersonic air breathing, single stage to orbit (SSTO), reusable launch vehicle (RLV) will be highlighted as well as an aeroshell for a planetary exploration vehicle used for aerocapture at Mars. By showing the two different types of vehicles, the software's flexibility will be demonstrated with an emphasis on reducing aeroshell structural weight. Member sizes, concepts and material selections will be discussed as well as analysis methods used in optimizing the structure. Analysis based on the HyperSizer structural sizing software will be discussed. Design trades required to optimize structural weight will be presented.

Hrinda, Glenn A.↗

NASA NTRS2006

Probabilistic Prediction of Lifetimes of Ceramic Parts

ANSYS/CARES/PDS is a software system that combines the ANSYS Probabilistic Design System (PDS) software with a modified version of the Ceramics Analysis and Reliability Evaluation of Structures Life (CARES/Life) Version 6.0 software. [A prior version of CARES/Life was reported in Program for Evaluation of Reliability of Ceramic Parts (LEW-16018), NASA Tech Briefs, Vol. 20, No. 3 (March 1996), page 28.] CARES/Life models effects of stochastic strength, slow crack growth, and stress distribution on the overall reliability of a ceramic component. The essence of the enhancement in CARES/Life 6.0 is the capability to predict the probability of failure using results from transient finite-element analysis. ANSYS PDS models the effects of uncertainty in material properties, dimensions, and loading on the stress distribution and deformation. ANSYS/CARES/PDS accounts for the effects of probabilistic strength, probabilistic loads, probabilistic material properties, and probabilistic tolerances on the lifetime and reliability of the component. Even failure probability becomes a stochastic quantity that can be tracked as a response variable. ANSYS/CARES/PDS enables tracking of all stochastic quantities in the design space, thereby enabling more precise probabilistic prediction of lifetimes of ceramic components.

Nemeth, Noel N.↗

DOE OSTI2020

Southwest Wind Power R&D Test Site Development at the National Wind Technology Center (CRADA CRD-12-00472 Final Report)

Southwest Windpower, Inc. (SWWP) has been designing and distributing small wind turbines for more than 22 years and is the recognized global leader in the design, manufacturing and distribution of small wind systems (400-3000 watts). The company has been a pioneer in the development of wind technology and has built and shipped more than 170,000 wind turbines to over 120 countries worldwide. Headquartered in Flagstaff AZ, SWWP has sales representatives in over 88 countries. Applications for SWWP systems include residential homes, commercial properties, micro grids, remote cabins, telecom transmitters, offshore platforms, water pumping and sailboats. In addition, U.S. Department of Defense uses SWWP’s products in Forward Operating Bases (FOB’s), USGS uses them for remote monitoring of glacier movements and the CIA uses them to provide power seismic monitoring. Today, SWWP plans development of new technologies to address distributed energy market needs and become even more aggressive in international markets. This strategy includes extensive Research, Development, Demonstration & Deployment (RDD&D) activities to improve existing production line into more simple, reliable, and cost-effective wind turbine systems. Important part of such activities is the field testing of the new systems, which should provide: (i) validation of the reliable operation of hardware and software; (ii) validation of numerical models of the system and its components; (iii) field comparison of various control and optimization strategies; (iv) customized reliability testing; (v) customized monitoring and analysis testing; and (vi) IEC certification testing (vii) filed demonstration of system performance and reliability. Such field testing facility should encompass multiple towers and appropriate data acquisition systems. SWWP is exploring to move part of the engineering department to Colorado, and execute its RDD&D strategies in this new location. Partnership with NREL will provide great insights into SWWP’s RDD&D processes and more efficient commercialization by utilizing NWTC as the field testing site, and working close with NREL personnel. NWTC is ideally suited to strain the design. NREL is very experienced with customized and IEC testing. During this project, Southwest Windpower aims to improve the value proposition of distributed renewable energy, and make it a competitive choice in the energy markets. As of today, more then 170,000 small wind turbines, manufactured in the U.S., are installed in more then 180 countries. With the improved value proposition, Southwest Windpower wants to create and address new market needs, substantially increase its sales domestically and internationally, which should have positive impact on the creation of American jobs, competitiveness of U.S. economy, export or U.S. products, and the use of renewable energy.

17 WIND ENERGY↗

NASA NTRS1991

NASA product assurance in the 1990s

The objectives of NASA product assurance in the 1990s are identified. They are to provide for personnel safety, and safe and reliable operation of hardware and software during the lifetime of a program or mission. The NASA product assurance program, a multi-discipline effort that focuses on safety, reliability, maintainability, and quality assurance expertise to meet NASA operational requirements is described. This program supports NASA 's unmanned launch vehicles such as satellites and planetary probes, manned spacecraft (such as the Space Shuttle and Space Station Freedom), and ground support equipment.

Rodney, George A.↗

NASA NTRS2006

Software Reuse Within the Earth Science Community

Scientific missions in the Earth sciences frequently require cost-effective, highly reliable, and easy-to-use software, which can be a challenge for software developers to provide. The NASA Earth Science Enterprise (ESE) spends a significant amount of resources developing software components and other software development artifacts that may also be of value if reused in other projects requiring similar functionality. In general, software reuse is often defined as utilizing existing software artifacts. Software reuse can improve productivity and quality while decreasing the cost of software development, as documented by case studies in the literature. Since large software systems are often the results of the integration of many smaller and sometimes reusable components, ensuring reusability of such software components becomes a necessity. Indeed, designing software components with reusability as a requirement can increase the software reuse potential within a community such as the NASA ESE community. The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group is chartered to oversee the development of a process that will maximize the reuse potential of existing software components while recommending strategies for maximizing the reusability potential of yet-to-be-designed components. As part of this work, two surveys of the Earth science community were conducted. The first was performed in 2004 and distributed among government employees and contractors. A follow-up survey was performed in 2005 and distributed among a wider community, to include members of industry and academia. The surveys were designed to collect information on subjects such as the current software reuse practices of Earth science software developers, why they choose to reuse software, and what perceived barriers prevent them from reusing software. In this paper, we compare the results of these surveys, summarize the observed trends, and discuss the findings. The results are very similar, with the second, larger survey confirming the basic results of the first, smaller survey. The results suggest that reuse of ESE software can drive down the cost and time of system development, increase flexibility and responsiveness of these systems to new technologies and requirements, and increase effective and accountable community participation.

Marshall, James J.↗

NASA NTRS2001

Reliability of Fault Tolerant Control Systems

This paper reports Part I of a two part effort, that is intended to delineate the relationship between reliability and fault tolerant control in a quantitative manner. Reliability analysis of fault-tolerant control systems is performed using Markov models. Reliability properties, peculiar to fault-tolerant control systems are emphasized. As a consequence, coverage of failures through redundancy management can be severely limited. It is shown that in the early life of a syi1ein composed of highly reliable subsystems, the reliability of the overall system is affine with respect to coverage, and inadequate coverage induces dominant single point failures. The utility of some existing software tools for assessing the reliability of fault tolerant control systems is also discussed. Coverage modeling is attempted in Part II in a way that captures its dependence on the control performance and on the diagnostic resolution.

Wu, N. Eva↗

DOE OSTI2016

SU-F-T-163: Improve Proton Therapy Efficiency: Report of a Workshop

Purpose: The technology of proton therapy, especially the pencil beam scanning technique, is evolving very quickly. However, the efficiency of proton therapy seems to lag behind conventional photon therapy. The purpose of the abstract is to report on the findings of a workshop on improvement of QA, planning and treatment efficiency in proton therapy. Methods: A panel of physicists, clinicians, and vendor representatives from over 18 institutions in the United States and internationally were convened in Knoxville, Tennessee in November, 2015. The panel discussed several topics on how to improve proton therapy efficiency, including 1) lean principle and failure mode and effects analysis, 2) commissioning and machine QA, 3) treatment planning, optimization and evaluation, 4) patient positioning and IGRT, 5) vendor liaison and machine availability, and 6) staffing, education and training. Results: The relative time needed for machine QA, treatment planning & check in proton therapy was found to range from 1 to 2.5 times of that in photon therapy. Current status in proton QA, planning and treatment was assessed. Key areas for efficiency improvement, such as elimination of unnecessary QA items or steps and development of efficient software or hardware tools, were identified. A white paper to summarize our findings is being written. Conclusion: It is critical to improve efficiency by developing reliable proton beam lines, efficient software tools on treatment planning, optimization and evaluation, and dedicated proton QA device. Conscious efforts and collaborations from both industry leaders and proton therapy centers are needed to achieve this goal and further advance the technology of proton therapy.

60 APPLIED LIFE SCIENCES↗

DOE OSTI2017

Complexity and error potential of digital I and C - 135

Utilization of digital I and C for application in nuclear power plants led to a growing discussion on how to create methods for a probabilistic evaluation on such systems. Issues arise on the one hand due to a lack of commonly accepted models for quantitative evaluation of availability and reliability and on the other hand due to the integration of such models into the evaluation of reliability of an overall system. Nevertheless programmable and even more complex systems are implemented to satisfy growing functionality requirements. Therefore the question for a method to evaluate the reliability of systems based on software or on programmable logic became even more urgent. The approach described is based on the commonly accepted assumption that more complex designs are less reliable. (authors)

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

NASA NTRS1992

Advanced techniques in reliability model representation and solution

The current tendency of flight control system designs is towards increased integration of applications and increased distribution of computational elements. The reliability analysis of such systems is difficult because subsystem interactions are increasingly interdependent. Researchers at NASA Langley Research Center have been working for several years to extend the capability of Markov modeling techniques to address these problems. This effort has been focused in the areas of increased model abstraction and increased computational capability. The reliability model generator (RMG) is a software tool that uses as input a graphical object-oriented block diagram of the system. RMG uses a failure-effects algorithm to produce the reliability model from the graphical description. The ASSURE software tool is a parallel processing program that uses the semi-Markov unreliability range evaluator (SURE) solution technique and the abstract semi-Markov specification interface to the SURE tool (ASSIST) modeling language. A failure modes-effects simulation is used by ASSURE. These tools were used to analyze a significant portion of a complex flight control system. The successful combination of the power of graphical representation, automated model generation, and parallel computation leads to the conclusion that distributed fault-tolerant system architectures can now be analyzed.

Palumbo, Daniel L.↗

NASA NTRS2022

Real-Time Exposure Control and Instrument Operation With the NEID Spectrograph GUI

The NEID spectrograph on the WIYN 3.5-m telescope at Kitt Peak has completed its first full year of science operations and is reliably delivering sub-m/s precision radial velocity measurements. The NEID instrument control system uses the TIMS package (Bender et al. 2016), which is a client-server software system built around the twisted python software stack. During science observations, interaction with the NEID spectrograph is handled through a pair of graphical user interfaces (GUIs), written in PyQT, which wrap the underlying instrument control software and provide straightforward and reliable access to the instrument. Here, we detail the design of these interfaces and present an overview of their use for NEID operations. Observers can use the NEID GUIs to set the exposure time, signal-to-noise ratio (SNR) threshold, and other relevant parameters for observations, configure the calibration bench and observing mode, track or edit observation metadata, and monitor the current state of the instrument. These GUIs facilitate automatic spectrograph configuration and target ingestion from the nightly observing queue, which improves operational efficiency and consistency across epochs. By interfacing with the NEID exposure meter, the GUIs also allow observers to monitor the progress of individual exposures and trigger the shutter on user-defined SNR thresholds. In addition, inset plots of the instantaneous and cumulative exposure meter counts as each observation progresses allow for rapid diagnosis of changing observing conditions as well as guiding failure and other emergent issues.

Arvind F Gupta↗

DOE OSTI2020

Operationalizing Synchrophasors for Enhanced Grid Reliability and Asset Utilization

The report discusses the development of production-grade synchrophasor software applications. The objective is to improve system reliability and asset utilization for offline as well as real-time considerations, as per the Department of Energy (DOE) guidelines specified by Funding Opportunity Announcement (FOA) DE-FOA-0001492. On the one hand, we have developed grid management applications on how to transform synchrophasor-based monitoring into operator guidance, and commercial grade tools addressing industry needs such as NERC Reliability Standards (MOD 26, MOD 27 and MOD 33). On the other hand, with the wide industrial adoption in mind, the developed applications have been fully discussed with utility partners and installed in the utility partners site including 6 field tests. The Model Validation and Calibration software module has been integrated into GE’s PhasorAnalyticsTM. The first commercial contract has been signed even before the close date of this project. The Angle-based Grid Management (AGM), Fast Voltage Security Assessment (FastVSA), Enhanced Islanding Monitoring(EIM) and Enhanced Disturbance Management (EDM) have been integrated into GE’s Grid Stability Assessment line of applications in e-terra Suite of EMS product.

24 POWER TRANSMISSION AND DISTRIBUTION↗

NASA NTRS1994

Implementing Software Safety in the NASA Environment

Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of the system to be built. Shortly thereafter, as the system requirements are being defined, the second iteration of hazard analyses takes place, the systems hazard analysis (SHA). During the systems requirements phase, decisions are made as to what functions of the system will be the responsibility of software. This is the most critical time to affect the safety of the software. From this point, software safety analyses as well as software engineering practices are the main focus for assuring safe software. While many of the steps proposed in this paper seem like just sound engineering practices, they are the best technical and most cost effective means to assure safe software within a safe system.

Wetherholt, Martha S.↗

NASA NTRS2009

Test Rack Development for Extended Operation of Advanced Stirling Convertors at NASA Glenn Research Center

The U.S. Department of Energy (DOE), Lockheed Martin Space Company (LMSC), Sun power Inc., and NASA Glenn Research Center (GRC) have been developing an Advanced Stirling Radioisotope Generator (ASRG) for use as a power system on space science missions. This generator will make use of free-piston Stirling convertors to achieve higher conversion efficiency than currently available alternatives. NASA GRC's support of ASRG development includes extended operation testing of Advanced Stirling Convertors (ASCs) developed by Sunpower Inc. In the past year, NASA GRC has been building a test facility to support extended operation of a pair of engineering level ASCs. Operation of the convertors in the test facility provides convertor performance data over an extended period of time. Mechanical support hardware, data acquisition software, and an instrumentation rack were developed to prepare the pair of convertors for continuous extended operation. Short-term tests were performed to gather baseline performance data before extended operation was initiated. These tests included workmanship vibration, insulation thermal loss characterization, low-temperature checkout, and fUll-power operation. Hardware and software features are implemented to ensure reliability of support systems. This paper discusses the mechanical support hardware, instrumentation rack, data acquisition software, short-term tests, and safety features designed to support continuous unattended operation of a pair of ASCs.

Dugala, Gina M.↗

NASA NTRS2000

Software IV and V Research Priorities and Applied Program Accomplishments Within NASA

The mission of this research is to be world-class creators and facilitators of innovative, intelligent, high performance, reliable information technologies that enable NASA missions to (1) increase software safety and quality through error avoidance, early detection and resolution of errors, by utilizing and applying empirically based software engineering best practices; (2) ensure customer software risks are identified and/or that requirements are met and/or exceeded; (3) research, develop, apply, verify, and publish software technologies for competitive advantage and the advancement of science; and (4) facilitate the transfer of science and engineering data, methods, and practices to NASA, educational institutions, state agencies, and commercial organizations. The goals are to become a national Center Of Excellence (COE) in software and system independent verification and validation, and to become an international leading force in the field of software engineering for improving the safety, quality, reliability, and cost performance of software systems. This project addresses the following problems: Ensure safety of NASA missions, ensure requirements are met, minimize programmatic and technological risks of software development and operations, improve software quality, reduce costs and time to delivery, and improve the science of software engineering

Blazy, Louis J.↗

NASA NTRS2004

Software Quality Assurance Metrics

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

McRae, Kalindra A.↗

NASA NTRS1991

Object oriented development of engineering software using CLIPS

Engineering applications involve numeric complexity and manipulations of a large amount of data. Traditionally, numeric computation has been the concern in developing an engineering software. As engineering application software became larger and more complex, management of resources such as data, rather than the numeric complexity, has become the major software design problem. Object oriented design and implementation methodologies can improve the reliability, flexibility, and maintainability of the resulting software; however, some tasks are better solved with the traditional procedural paradigm. The C Language Integrated Production System (CLIPS), with deffunction and defgeneric constructs, supports the procedural paradigm. The natural blending of object oriented and procedural paradigms has been cited as the reason for the popularity of the C++ language. The CLIPS Object Oriented Language's (COOL) object oriented features are more versatile than C++'s. A software design methodology based on object oriented and procedural approaches appropriate for engineering software, and to be implemented in CLIPS was outlined. A method for sensor placement for Space Station Freedom is being implemented in COOL as a sample problem.

Yoon, C. John↗