Search NASASearch

SEARCH · Search NASA

Results for “QA documentation”

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 19 records

Review of the Constellation Level II Safety, Reliability, and Quality Assurance (SR&QA) Requirements Documents during Participation in the Constellation Level II SR&QA Forum

At the request of the Exploration Systems Mission Directorate (ESMD) and the Constellation Program (CxP) Safety, Reliability; and Quality Assurance (SR&QA) Requirements Director, the NASA Engineering and Safety Center (NESC) participated in the Cx SR&QA Requirements forum. The Requirements Forum was held June 24-26; 2008, at GRC's Plum Brook Facility. The forums purpose was to gather all stakeholders into a focused meeting to help complete the process of refining the CxP to refine its Level II SR&QA requirements or defining project-specific requirements tailoring. Element prime contractors had raised specific questions about the wording and intent of many requirements in areas they felt were driving costs without adding commensurate value. NESC was asked to provide an independent and thorough review of requirements that contractors believed were driving Program costs, by active participation in the forum. This document contains information from the forum.

Cameron, Kenneth D.

Genesis Solar Wind Sample Curation Documentation

Introduction: A scientist with experience as a sample science analyst, provider of flight hardware for multiple missions, and senior engineer in an ISO 2000-rated manufacturing plant has described the timeline of key participants in any PI-led sample return mission, the breadth of the organizations involved [1,2], and, of interest to this meeting, choosing the types of data to preserve and issues of future data accessibility. This work broadens that perspective by giving similar lessons from Genesis sample curation point-of-view. Curation participation regarding data gathering was part of the mission review process from the beginning. Genesis’ story illustrates outcome of several choices about types of data to record and preserve. Precision analysis of solar wind atoms captured in pure, ultraclean substrates is the driving science goal; therefore, detailed documentation was captured from all mission and curation phases and from investigator laboratories because these processes affect the final analytical results [3]. Pre-flight: Design and fabrication of the spacecraft. Like many modern small sample return missions, Genesis was a tightly managed team integrated across science, engineering and curation. Communication across the team was excellent, and, for the most part, the hands-on engineering technicians understood the impacts of “small choices” they routinely make, and the eyes-on oversight of manufacturing processes by scientists was mindful of details. The payload was designed by the Jet Propulsion Laboratory and the spacecraft by Lockheed Martin. Solar wind collectors and instruments were fabricated by multiple vendors and laboratories. The main portion of the payload was assembled at JSC. Fabrication procedures and contamination-control data (with witness coupons) were stored primarily at JSC. The original composition, dimensions and configuration of components, results of thermal testing, etc. are still needed for interpretation of analytical data. At times, these must be estimated from secondary information acquired pre-flight. Moreover, some files (e.g., original 3-D models and early Powerpoint) cannot be opened using software. Archived curation data includes 2-D drawings, material usage lists, QA documentation and analyses of consumables used during fabrication. Important chemical information still resides in archived hardware, paints and lubricants, material coupons, cleaning coupons, environmental witness plates and reference materials from manufacturing facilities. Purity and cleanliness of collector substrates. Semi-conductor vendors provided surface cleanliness data and some purity data. Purity for specific elements of interest was verified by science team members in their laboratories [4]. Curation archived procurement and shipping records, analysis reports, and non-proprietary fabrication data. A physical archive of flight collector reference materials is maintained for future use so additional data can be collected as analytical techniques improve. These are of increased value due to the hard landing upon re-entry. Cleaning and cleanliness assessments of flight hardware. Cleaning of the science canister payload was performed at JSC in a dedicated ISO 4 cleanroom using ultrapure water (UPW). The cleanliness of this UPW was monitored throughout processing. The archive for the clean lab also includes airborne particle counts, airborne molecular and inorganic contamination measurements as well as cleanroom construction material coupons and witness coupons. Hardware cleanliness was assessed by particle counts in rinse water batches. This information is recorded in batch cleaning forms and logbooks, and are, perhaps, of decreased value due to the hard landing. Post-flight: Curation-generated data. The curation handling history of each Genesis sample is documented in a typical astromaterials sample database which captures sample location, physical description and characterization data. Samples have a “shelf life”. Crucial to the preservation of samples is ongoing documentation of the sample environment, initially under curatorial control but is now a separate facility function with requires coordination. PI-generated data. Data on sample characterization and cleaning techniques continues to be generated by sample users [5]. These are often captured in LPSC abstracts, but these “engineering” results often are not publishable as stand-alone papers. We are actively looking for ways to make this information more accessible to users. Ion implants into samples have aided science return and can be shared among investigators. These (and similar) materials should be added to the curatorial collection with appropriate process and characterization data generated externally. Summary: Complete data archives for returned astromaterial samples must be broad in types and formats, and inclusive of environmental monitoring.

Genesis

Data Quality: 1979 Southeastern Virginia Urban Plume Study (SEV-UPS): Surface and Airborne studies

The SEV-UPS field study conducted during August 1979 involved the coordinated air quality data collection efforts of three different organizations operating a total of four aircraft and 12 ground stations. Incorporated into plans for that program were numerous quality assurance activities designed to identify potential hazards for data quality in time for their correction and to take data to allow assessment of the consistency of the data from different stations. The purpose of this study was to document QA procedures that were performed by participating agencies and revise data from all platforms for mutual compatibility. For the latter effort, cases were identified on 21 occasions on seven different days where two or more monitoring systems were operating in the same location at nearly the same time. Data from the systems involved were tabulated in 200 m altitude segments, averaged and compared to detect any bias between measurements made from different systems. The results of these comparisons along with the results of independent performance audits are presented.

White, J. H.

JPL's End Item Data Packages (EIDPs)

A viewgraph presentation on JPL's End Item Data Packages (EIDPs) is shown. The topics include: 1) Background and past efforts; 2) Current effort; and 3) First look; 4) Final look; and 5) Next steps.

End Item Data Package (EIDP)

Capturing, using, and managing quality assurance knowledge for shuttle post-MECO flight design

Ascent initialization values used by the Shuttle's onboard computer for nominal and abort mission scenarios are verified by a six degrees of freedom computer simulation. The procedure that the Ascent Post Main Engine Cutoff (Post-MECO) group uses to perform quality assurance (QA) of the simulation is time consuming. Also, the QA data, checklists and associated rationale, though known by the group members, is not sufficiently documented, hindering transfer of knowledge and problem resolution. A new QA procedure which retains the current high level of integrity while reducing the time required to perform QA is needed to support the increasing Shuttle flight rate. Documenting the knowledge is also needed to increase its availability for training and problem resolution. To meet these needs, a knowledge capture process, embedded into the group activities, was initiated to verify the existing QA checks, define new ones, and document all rationale. The resulting checks were automated in a conventional software program to achieve the desired standardization, integrity, and time reduction. A prototype electronic knowledge base was developed with Macintosh's HyperCard to serve as a knowledge capture tool and data storage.

Peters, H. L.

HELIOS Critical Design Review: Quality Assurance

The following is an account of the activities of the Quality Assurance (QA) department of the project management office highlighting some of the ways in which it controls QA of the subcontractors on one hand and reports on Quality to GfW (Gesellschaft fur Weltraumforschung) on the other hand. The basic document prepared by MBB (Messerschmitt-Bolkow-Blohm) for QA activities is 1. The QA plan based on GfW 002. The QA department is responsible moreover for monitoring and making decisions about the quality of parts and materials and the governing document for this activity is 2. The Parts and Materials Control Plan based on GfW 001 - the reliability program provisions, as well as GfW 002. A brief survey of the contents of the QA Plan is shown. It should be noted that QA activity dealing with parts procurement is partially covered in a separate presentation entitled "Hi-Rel Parts". Supplementary quality documents are shown.

Benoehr, H. C.

Computer-Assisted Search Of Large Textual Data Bases

"QA" denotes high-speed computer system for searching diverse collections of documents including (but not limited to) technical reference manuals, legal documents, medical documents, news releases, and patents. Incorporates previously available and emerging information-retrieval technology to help user intelligently and rapidly locate information found in large textual data bases. Technology includes provision for inquiries in natural language; statistical ranking of retrieved information; artificial-intelligence implementation of semantics, in which "surface level" knowledge found in text used to improve ranking of retrieved information; and relevance feedback, in which user's judgements of relevance of some retrieved documents used automatically to modify search for further information.

Driscoll, James R.

Qualifying Bulk Metallic Glass Gear Materials for Spacecraft Applications

NASA is evaluating bulk metallic glass (BMG) gears for extreme environment (cryogenic) applications; e.g., Europa Lander. The main purpose of this report is to recommend a quality assurance (QA) protocol for the production of consistent and reliable gear castings. Currently, there are two, separate manufacturers involved; Materion Corporation produces re-melt stock and Visser Precision Cast, Inc. produces BMG castings. Division of the existing alloy specifications document into material supplier-specific documents is proposed. Until a composition-based specification is established, processability- and performance-based methodologies may be an option during manufacturing development. It is recommended that each of the documents has a distinct focus; the processing behavior of crystalline feedstock, and the mechanical behavior of amorphous castings. The report addresses the “gray area” in QA testing between these materials suppliers by outlining an equitable division of responsibilities. The use of a number of dedicated reference dies to produce witness materials for physical and mechanical property evaluation is strongly recommended. Allocation of QA tests between screen testing of gear castings, and formal testing of witness materials, including cryogenic properties, is also proposed. The most effective suite of tests for both physical and mechanical property determination are down-selected from available national and international standards. The contents of this report create a solid basis for selection of QA tests, thereby setting the stage for negotiations between the materials suppliers and the customer.This technical paper:a) provides recommendations to advance materials specifications document JPL D-56223,Rev. A from “draft” to “preliminary” status;b) proposes division of the current document into two supplier-specific documents;c) separates testing methods by “ingots/castings” and “witness materials”;d) classifies test methodology based on “processability” and “performance”;e) assembles candidate ASTM specifications for “screen testing” and “formal testing”;f) identifies standard tests compatible with evaluation of BMG flexspline gears;g) suggests division of responsibilities for processability and performance testing; andh) addresses the QA “gray area” between production of ingots and castings.The report recommends that:a) processability- and performance-based QA methods might be used in lieu ofcompositional specifications during manufacturing development only;b) reference dies be designed for “acceptance” and “qualification” castings;c) witness materials provide physical and mechanical property data;d) formal testing be conducted at ambient and cryogenic temperatures; ande) processing/properties be correlated with compositional variations.

Hales, Stephen J.

NASA Pilot-Engaged Expert Response Using IBM Watson Technology: Prototype Evaluation of Knowledge Retrieval System

NASA Langley Research Center and IBM have been investigating the use of IBM Watson technology in aerospace research and development. One application of Watson technology is the Pilot-Engaged Expert Response (PEER) use case. The PEER system is envisioned as an in-cockpit advisor that will act as a source of situationally-relevant information for pilots and other flight crew members to assist in decision making about real-time events and situations that arise in the course of aircraft operations. PEER will make available vast stores of knowledge and information quickly and directly, putting important informational resources where they are needed most. IBM has worked with NASA to develop an architecture and articulate a roadmap for the development of the PEER system. That vision is built around Watson Discovery Advisor (WDA) software solution, derived from IBM's Jeopardy!-winning automatic question answering system. PEER makes use of WDA's sophisticated question-answering capabilities as its core, adding important User Interface components and other customizations for the cockpit environment, including communication with flight systems and other external data sources. The development plan for PEER includes four development stages, with the current project constituting the first phase. In this project, a prototype instance of PEER was successfully adapted to the aviation domain, enabling users to ask questions about aviation topics and receive useful and accurate answers to these questions. Major tasks accomplished include the development of procedures for domain adaptation through automatic lexicon extraction from domain glossaries; generation of question-answer training data which was used to train the system; and assessment of the effectiveness of domain adaptation, which showed a dramatic improvement in the ability of the PEER system to answer domain-relevant questions. In addition, the vision for the PEER system was pushed forward by the articulation of a plan for the automatic enhancement of question-answering with contextual information. This initial phase focused on two main goals: 1) the targeted domain adaptation of the underlying WDA system to the aviation domain; and, 2) the design of the software systems needed to leverage flight-contextual data. Domain adaptation of the WDA system proceeds via three main activities: Domain data ingestion, lexical customization and model training. A textual corpus consisting of 1,147 individual documents with more than 7.5 million words of text was ingested into the system and this served as the basis of all further development. A domain lexicon of over 3,500 aviation-domain terms was semi-automatically generated from domain documents and used to train the system. In addition, a set of over 500 question-answer (QA) pairs relevant to the PEER use case was developed; these were used to train and assess the system. These important first steps established the basis for the PEER system. In addition, steps were taken towards the integration of the PEER system into the cockpit environment with the development of a functional design for the Contextual Data Augmentation (CDA) subsystem. This subsystem brings to bear contextual data to improve system responses. It has three main submodules: the Contextual Data Collection module, the Contextual Data Selection module, and the Contextual QA Augmentation module. These modules form a processing pipeline that addresses the problems associated with automatically integrating information from external resources into the knowledge-retrieval mechanism.

Machine learning

Safety, Reliability, and Quality Assurance Provisions for the Office of Aeronautics, Exploration and Technology Centers

This Handbook establishes general safety, reliability, and quality assurance (SR&QA) guidelines for use on flight and ground-based projects conducted at the Ames, Langley, and Lewis Research Centers, hereafter identified as the Office of Aeronautics, Exploration and Technology (OAET) Centers. This document is applicable to all projects and operations conducted at these Centers except for those projects covered by more restrictive provisions such as the Space Shuttle, Space Station, and unmanned spacecraft programs. This Handbook is divided into two parts. The first (Chapters 1 and 2) establishes the SR&QA guidelines applicable to the OAET Centers, and the second (Appendices A, B, C, and D) provides examples and definitions for the total SR&QA program. Each center should implement SR&QA programs using these guidelines with tailoring appropriate to the special projects conducted by each Center. This Handbook is issued in loose-leaf form and will be revised by page changes.

Source record

John F. Kennedy Space Center, Safety, Reliability, Maintainability and Quality Assurance, Survey and Audit Program

This document is the product of the KSC Survey and Audit Working Group composed of civil service and contractor Safety, Reliability, and Quality Assurance (SR&QA) personnel. The program described herein provides standardized terminology, uniformity of survey and audit operations, and emphasizes process assessments rather than a program based solely on compliance. The program establishes minimum training requirements, adopts an auditor certification methodology, and includes survey and audit metrics for the audited organizations as well as the auditing organization.

Source record

Photovoltaic system criteria documents. Volume 2: Quality assurance criteria for photovoltaic applications

Quality assurance criteria are described for manufacturers and installers of solar photovoltaic tests and applications. Quality oriented activities are outlined to be pursued by the contractor/subcontractor to assure the physical and operational quality of equipment produced is included. In the broad sense, guidelines are provided for establishing a QA organization if none exists. Mainly, criteria is provided to be considered in any PV quality assurance plan selected as appropriate by the responsible Field Center. A framework is established for a systematic approach to ensure that photovoltaic tests and applications are constructed in a timely and cost effective manner.

Koenig, John C.

NASA software documentation standard software engineering program

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This 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. This 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 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

Experience with modified aerospace reliability and quality assurance method for wind turbines

The SR&QA approach assures that the machine is not hazardous to the public or operating personnel, can operate unattended on a utility grid, demonstrates reliability operation, and helps establish the quality assurance and maintainability requirements for future wind turbine projects. The approach consisted of modified failure modes and effects analysis (FMEA) during the design phase, minimal hardware inspection during parts fabrication, and three simple documents to control activities during machine construction and operation. Five years experience shows that this low cost approach works well enough that it should be considered by others for similar projects.

Klein, W. E.

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.

Modified aerospace R&QA method for wind turbines

This paper describes the Safety, Reliability and Quality Assurance (SR&QA) approach developed for the first large wind turbine generator project, MOD-OA. The SR&QA approach to be used had to assure that the machine would not be hazardous, would operate unattended on a utility grid, would demonstrate reliable operation, and would help establish the quality assurance and maintainability requirements for wind turbine projects. The final approach consisted of a modified Failure Modes and Effects Analysis (FMEA) during the design phase, minimal hardware inspections during parts fabrication, and three documents to control activities during machine construction and operation.

Klein, W. E.

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.