SEARCH · Search NASA

Results for “Audit Checklist”

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.

10 records

All sources NASA NTRS DOE OSTI

NASA NTRS2002

Software Assists in Extensive Environmental Auditing

The Base Enivronmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists on an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign manditory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: It helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

NASA NTRS2002

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

NASA NTRS2003

Software Assists in Extensive Environmental Auditing

Callac, Christopher↗

DOE OSTI2023

GHG Emissions Reduction Audit: A Checklist for Owners

This guidance and accompanying checklist detail recommended services and deliverables for a building-level greenhouse gas (GHG) emissions reduction audit focused on Scope 1 and 2 GHG emissions.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

NASA NTRS2024

Applying Generative-AI to NASA Documentation and Processes

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

NASA Standards↗

DOE OSTI2021

CY20 AIHA Internal Audit of ALAB and NIF-HPL and CY20 Management Review of ALAB

An internal audit was performed in ALAB to ISO 17025:2017; EPA LQST and AIHA requirements using the current AIHA Checklist. The scope of the internal audit was the annual review of AIHA-accredited industrial hygiene methods performer in both ALAB and NIF HPL. The Internal audit resulted in 3 deficiencies and 3 comments.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

DOE OSTI2021

Document Traceability Internal Audit of the Analytical Laboratory Report on 08-26-2021

An internal audit was performed in ALAB 8/25/21 to the NELAC 2016 Standard requirements using the NELAC 2016 checklist (TNI 2016 CSDP-Volume1Checklist-Master-2-15-18-v9). The scope of the internal audit was a document traceability of the environmental testing in LRF-00118, LRF00095, and LRF 00133 performed in ALAB. The internal audit resulted in five deficiencies and two comments. The deficiencies were addressed using the ALAB non-conformance reporting system, see ALAB NCRs 10002742-10002746. FRM-5100 Management Observation and NCRs are attached.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

NASA NTRS1996

Flight Dynamics Mission Support and Quality Assurance Process

This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

Oh, InHwan↗

NASA NTRSDate not supplied

HAT m:N Cognitive Task Analysis (CTA)

This Cognitive Task Analysis (CTA) study was designed to understand the capability of the m:N Tactical Operator (TO) interfaces developed by the Human-Autonomy Teaming Laboratory at NASA Ames to support operators responsible for simplified pilot operations of 100 independently operated small UAS (sUAS) in a constrained geographic area. The m:N sUAS TO interface includes a central Tactical Situation Display (TSD) digital map with moving icons reflecting the sUAS location and planned flight route. The interface also has two side panels. The left panel includes a tabular list of UAS assets and mission tasking, a list of recently viewed assets, and a list of events and alerts. The right panel includes a tabular list of UAS assets and their associated telemetry, text-based chat communication window, and a tabbed checklist window. This CTA was adapted from the incident-based applied cognitive task analysis (Militello & Hutton, 1998) and included demographics questions, scenario-based simulations, a task diagram and knowledge audit methods. In addition to examining the support provided by this m:N sUAS TO interface, this CTA study, conducted with aviation subject matter experts in analogous roles to the future tactical operator, was designed to illuminate and project likely cognitive requirements of the tactical operator. Interviewees participated in two scenario-based simulations using the m:N sUAS TO interfaces. In the first simulation, the interviewees supervised 12 sUAS operating in downtown San Diego, California transiting to and from a central sUAS Hive, restaurant locations, and customer drop off locations. Interviewees were asked to react to a UAS Volume Reservation (UVR) event with a two-phase impact on food delivery operations. In the second scenario, the interviewees supervised 100 sUAS operating in the same airspace and with the same mission. Interviewees used the interfaces to recognize and react to two sUAS air vehicle problems. After each scenario, we asked the interviewees a semi-structured list of questions to elicit their reflections about using the interfaces. Interviewees were confident in their ability to respond to two off-nominal situations in each simulation. Interviewees felt that, given high levels of automation on the sUAS, they would be able to manage the events without requiring additional support or handing off the sUAS to a colleague or supervisor in both the n=12 or n=100 sUAS settings. In the n=12 sUAS condition, interviewees used the center map to understand the asset location and progress along with mission tasking. An additional display window, Asset Telemetry, helped interviewees understand battery state and sUAS altitude. When the number of sUAS increased, interviewees altered their behavior. Rather than maintaining awareness of individual assets, interviewees appeared to become more reactive, managing exceptions. Interviewees reported that they spent less time looking at the nominal aircraft, and focused their attention primarily on the off-nominal aircraft. In addition, in the second simulation with n=100 sUAS, interviewees reported that they relied more on the side panels (Mission Timeline and Asset Telemetry) to gather information.

human-autonomy teaming↗

DOE OSTI2020

INL Waste Management Program Assessment Report

This is an INL annual internal waste management program assessment report that will need to be sent to NNSS for review. The report includes a summary and completed checklists based on the NNSS Waste Acceptance Criteria.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗