Search NASA⌕ Search

SEARCH · Search NASA

Results for “QUALITY 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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Management of government quality assurance functions for NASA contracts

This handbook sets forth requirements for NASA direction and management of government quality assurance functions performed for NASA contracts and is applicable to all NASA installations. These requirements will standardize management to provide the minimum oversight and effective use of resources. This handbook implements Federal Acquisition Regulation (FAR) Part 46, NASA FAR Supplement 18-46, Quality Assurance, and NMI 7410.1. Achievement of established quality and reliability goals at all levels is essential to the success of NASA programs. Active participation by NASA and other agency quality assurance personnel in all phases of contract operations, including precontract activity, will assist in the economic and timely achievement of program results. This involves broad participation in design, development, procurement, inspection, testing, and preventive and corrective actions. Consequently, government, as well as industry, must place strong emphasis on the accomplishment of all functions having a significant bearing on quality and reliability from program initiation through end-use of supplies and services produced. For purposes of implementing NASA and other agency agreements, and to provide for uniformity and consistency, the terminology and definitions prescribed herein and in a future handbook shall be utilized for all NASA quality assurance delegations and subsequent redelegations.

Source record↗
NASA NTRS1966

New developments in NASA quality assurance

The purpose of this talk is to examine and discuss NASA's basic quality concept, the policy and procedures which define and implement this concept and subsequently explore the NASA-Industry quality relationships which are essential to the success of NASA's quality assurance concept. It is important to emphasize that NASA's Quality Assurance program is predicated on the concept of an individually tailored quality program for each significant NASA procurement - particularly, large space systems. As a result, NASA's Quality Assurance program - to be effective - must be responsive to various technologies, hardware systems, and space missions. In addition, the program must be responsive to changing policies and practices in research, engineering and procurement. Key issues in the NASA-Contractor quality relationships in the framework of an over all NASA-Industry partnership include: (1) the necessity for NASA to effectively discharge its responsibility for providing clear and complete definition of quality requirements at all phases of the procurement cycle; (2) the right of the contractor to expect an explicit definition of NASA quality requirements in each RFP and contract and to request same if it is not provided; (3) the necessity for the contractor to have a dynamic and responsive quality program which is directed towards assuring that the hardware meets all technical requirements and to accomplish this in an effective and efficient manner; and (4) the critical need for investigation and study of the economic aspects of quality and an evaluation of our policies and practices based upon the results of such a study.

Condon, John E.↗
NASA NTRS1988

Modernization of software quality assurance

The customers satisfaction depends not only on functional performance, it also depends on the quality characteristics of the software products. An examination of this quality aspect of software products will provide a clear, well defined framework for quality assurance functions, which improve the life-cycle activities of software development. Software developers must be aware of the following aspects which have been expressed by many quality experts: quality cannot be added on; the level of quality built into a program is a function of the quality attributes employed during the development process; and finally, quality must be managed. These concepts have guided our development of the following definition for a Software Quality Assurance function: Software Quality Assurance is a formal, planned approach of actions designed to evaluate the degree of an identifiable set of quality attributes present in all software systems and their products. This paper is an explanation of how this definition was developed and how it is used.

Bhaumik, Gokul↗
DOE OSTI2021

MCC On Boarding Section J-2 (Exhibit H) Quality Assurance Requirements [Slides]

Upon MATOC Award, SUBCONTRACTOR shall submit a Quality Assurance Program for evaluation in accordance with subcontract technical and quality requirements. This may be the Subcontractors corporate QA program. Acceptance by Triad of the SUBCONTRACTORS Quality Assurance Program (QAP), as prescribed in Exhibit H, QC-01A and 01B, allows the SUBCONTRACTOR to execute this contract using their approved QAP. SUBCONTRACTORS QAP as approved by CONTRACTOR must meet the applicable requirements of DOE Order 414.1D (see next slide) and must address flow down of the quality requirements to lower tier subcontractors. Triad acceptance of SUBCONTRACTOR’s QAP approval is required prior to Notice to Proceed with on-site work. A Project Specific QA plan may on rare occasions be required for a specific task

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
NASA NTRS1980

Modified aerospace reliability and quality assurance method for wind turbines

The safety, reliability, and quality assurance (SR&QA) approach developed for the first large wind turbine generator project is described. The SR&QA approach was used to assure that the machine would not be hazardous to the public or operating personnel, would operate unattended on a utility grid, would demonstrate reliable operation and would help establish the quality assurance and maintainability requirements for future wind turbine projects. A modified failure modes and effects analysis during the design phase, minimal hardware inspections during parts fabrication, and three simple documents to control activities during machine construction and operation were presented.

Klein, W. E.↗
DOE OSTI2024

ORCA Software Quality Assurance Plan

This document summarizes the software quality assurance (SQA) planning activities conducted for the Optimization of Real-time Capacity Allocation (ORCA) plug-in. It outlines the approaches and document structures adopted to maintain high standards of software quality. It also gives examples of certain SQA documents.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2021

Software Quality Assurance for EBR-II Fuels Irradiation and Physics Database (FIPD)

The Fuels Irradiation and Physics Database (FIPD) is an ongoing DOE project on archival of the EBR-II metal-alloy fuel irradiation experiments. As part of its use in support of license applications, the Quality Assurance Program Plan (QAPP) was drafted and endorsed by NRC in an effort to demonstrate its compliance with regulatory expectations. Software Quality Assurance (SQA) for the physics portion of FIPD is intended to qualify the calculated quantities such as fuel and cladding temperatures, neutron fluence and axially varying burnup estimates for irradiated fuel elements. This report covers the initial evaluation of SQA status of three neutron physics and thermo-fluid codes (REBUS, RCT and SE2RCT) that form the basis of calculated quantities for as-irradiated characteristics of the tested metallic fuel elements. The report also introduces an SQA plan to address the identified deficiencies. The REBUS, RCT, and SE2RCT codes are all part of the Argonne Reactor Code (ARC) code system. There is considerable knowledge and experience on REBUS and RCT but relatively less on SE2RCT. During FY2021, efforts focused on an assessment of how the data in the EBR-II Physics and Analysis DataBase (PADB) is generated with SE2RCT and used in FIPD. Additional tasks included considerations of uncertainties for power estimates in REBUS and RCT calculations and their impact on the combined RCT methodology. The RCT software usage in FIPD was assessed this year and the input/output details studied. A “requirements” document was created that identifies the key features of the RCT software being used in FIPD that need to have SQA documentation. A brief discussion on the history of RCT and its input is included in this report along with the basic SQA roadmap laid out in the requirements document. The SE2RCT software usage in FIPD is still being studied noting that there is no current manual. As part of the work done this year, two bugs were identified in the SE2RCT software which have a minor impact on the accuracy of the results it produces. No requirements document has been created, but one identified feature of SE2RCT being used that needs verification was its fuel pin temperature calculation. The work completed this year confirms that the approximations which will be included in the software verification report for SE2RCT are accurate. In addition to software quality assurance work for RCT and SE2RCT, an automated verification framework is proposed to simplify the software quality assurance process. The purpose of this framework is to streamline code verification and documentation while minimizing repetitive tasks for code developers and reviewers. The reduction of repeated input (between reference solution, software, and documentation input) throughout the SQA process reduces potential for human errors during the preparation of the supporting software quality records. The automation of the verification and documentation process proposed for this project leverages the existing verification structure already in place for the SAS4A/SASSYS-1 code.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
NASA NTRS2014

The Significance of Breakdown Voltages for Quality Assurance of Low-Voltage BME Ceramic Capacitors

Application of thin dielectric, base metal electrode (BME) ceramic capacitors for high-reliability applications requires development of testing procedures that can assure high quality and reliability of the parts. In this work, distributions of breakdown voltages (VBR) in variety of low-voltage BME multilayer ceramic capacitors (MLCCs) have been measured and analyzed. It has been shown that analysis of the distributions can indicate the proportion of defective parts in the lot and significance of the defects. Variations of the distributions after solder dip testing allow for an assessment of the robustness of capacitors to soldering-related stresses. The drawbacks of the existing screening and qualification methods to reveal defects in high-value, low-voltage MLCCs and the importance of VBR measurements are discussed. Analysis has shown that due to a larger concentration of oxygen vacancies, defect-related degradation of the insulation resistance (IR) and failures are more likely in BME compared to the precious metal electrode (PME) capacitors.

reliability↗
NASA NTRS1981

Reliability and quality assurance on the MOD 2 wind system

The Safety, Reliability, and Quality Assurance (R&QA) approach developed for the largest wind turbine generator, the Mod 2, is described. The R&QA approach assures that the machine is not hazardous to the public or to the operating personnel, is operated unattended on a utility grid, demonstrates reliable operation, and helps establish the quality assurance and maintainability requirements for future wind turbine projects. The significant guideline consisted of a failure modes and effects analysis (FMEA) during the design phase, hardware inspections during parts fabrication, and three simple documents to control activities during machine construction and operation.

Mason, W. E. B.↗
NASA NTRS1993

Experience with Formal Methods techniques at the Jet Propulsion Laboratory from a quality assurance perspective

Recent experience with Formal Methods (FM) in the Software Quality Assurance Section at the Jet Propulsion Lab is presented. An integrated Formal Method process is presented to show how related existing requirements analysis and FM techniques complement one another. Example application of FM techniques such as formal specifications and specification animators are presented. The authors suggest that the quality assurance organization is a natural home for the Formal Methods specialist, whose expertise can then be used to best advantage across a range of projects.

Kelly, John C.↗
NASA NTRS1972

Electron-proton spectrometer quality assurance procedures for equipment and parts

Quality control procedures are established for personnel who are concerned with receiving, storage, transfer, inspection, and use of flight or mission related hardware for the electron/proton spectrometer (EPS) program. While general guidelines, designed to cover all situations, exist, this document provides guidelines and procedures specifically designed to supplement the quality assurance activity on the EPS Program. It is the purpose of this document to insure that all equipment, parts and other hardware received and/or used in the EPS program meet or surpass the standards and requirements established by cognizant authorities.

Gleeson, P.↗
NASA NTRS1990

Software quality assurance plan for GCS

The software quality assurance (SQA) function for the Guidance and Control Software (GCS) project which is part of a software error studies research program is described. The SQA plan outlines all of the procedures, controls, and audits to be carried out by the SQA organization to ensure adherence to the policies, procedures, and standards for the GCS project.

Duncan, Stephen E.↗
NASA NTRS1976

Summary of development and recommendations for a quality assurance program for the procurement and manufacture of urban mass transit operating equipment and systems

A viable quality program for the urban mass transit industry, and a management approach to ensure compliance with the program are outlined. Included are: (1) a set of guidelines for quality assurance to be imposed on transit authorities, and a management approach to ensure compliance with them; (2) a management approach to be used by the transit authorities (properties) for assuring compliance with the QA guidelines; and (3) quality assurance guidelines to be imposed by properties and umta for procurement of hardware and systems.

Witkin, S. A.↗
DOE OSTI2024

ORNL Package Testing Program Software Quality Assurance Plan

The Oak Ridge National Laboratory (ORNL) Package Testing Program (PTP) uses commercial off-the-shelf (COTS) software in performing data collection of thermal test results for package designs that contain radioactive materials. Specifically, this software is used to collect temperature data from the furnace, packages, and ambient air to prepare and execute the thermal test specified in 10 CFR 71.73, “Thermal Test.” This software quality assurance (SQA) plan sets forth the guidelines, standards, and procedures that shall be used to provide SQA for PTP software applications. This is a living document that will be maintained for the lifecycle of the PTP program. The SQA plan follows the requirements set forth in ORNL Standards Based Management System (SBMS): Information Technology; Subject Area: Software Quality Assurance. When applicable to the requirements as described in ORNL SBMS, Software Quality Assurance, the software shall be listed in the ORNL Software Registration System (SRS). Exemptions to this SBMS are COTS and firmware that are not modified; spreadsheet applications and personal productivity tools that do not have a utility or safety application, research applications, legacy software, system software, vendor-supplied software used to interface with the vendor’s services, software used within the organization to facilitate processing or management of information, and software developed for applications not specific to the US Department of Energy (DOE).

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1990

Software Quality Assurance Audits Guidebooks

The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes that are used in software development. The Software Assurance Guidebook, NASA-GB-A201, issued in September, 1989, provides an overall picture of the NASA concepts and practices in software assurance. Second level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the second level Software Quality Assurance Audits Guidebook that describes software quality assurance audits in a way that is compatible with practices at NASA Centers.

Source record↗
NASA NTRS2020

NASA Quality Assurance in an MBSE world

Over the past decade or so, the emergence of Model Based Systems Engineering (MBSE) has demonstrated its desirability and value in terms of 1) being a single source of truth, 2) unambiguous definitions and relationships, and 3) after representation, the ability to explore/extract any sets of data on demand. While much work has been done in showing the value to the system engineering discipline in these areas, how does that value translate to the Safety and Mission Assurance (S&MA) world? This paper provides a vision of a very desirable future of NASA S&MA after it is fully integrated into the MBSE framework. We explore the impact and consequences of the MBSE Value items discussed above and how they impact the disciplines of quality assurance, reliability and maintainability, system safety, and software assurance. We provide insight into how the MBSE modeling tools can be used to define S&MA processes (ideally as a result of Use Case [1] elaboration of processes represented in MagicDraw®), produce S&MA products (ViewEditor output of various items), and represent S&MA disciplines (S&MA inside of MagicDraw). We also provide insight into the degree to which some elements can be directly integrated into a SysML® model and when, as often happens, an interface to some external source must be provided. The desirability of this future is part of the reason for the NASA Office of Safety and Mission Assurance’s (OSMA) recent creation of a Model Based Mission Assurance (MBMA) Program [2] and the MBMA annual workshops. We briefly summarize the efforts to date to generate S&MA Use Cases for eventual deployment into pilot and project efforts. Even simple use of the SysML modeling tools can be used to capture quality assurance tasks and integrate them with the systems engineering and produce products that are easy to use by quality practitioners that are unfamiliar with these methods. We anticipate finding opportunities to pilot and implement various Quality Assurance (QA) Use Cases in FY20. The MBMA Program is focused on implementation; the NASA Office of the Chief Engineer's Community of Practice, as well as the SmallSat communities, are very interested in the integration of S&MA. Finally, as projects move forward utilizing whatever efficiency increases they can find in a cost-constrained environment, the S&MA community cannot be caught unawares and needs to continue preparing for the ever-growing implementation of MBSE across NASA and our government and commercial partners.

Evans, John W↗