Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Audit Report”

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.

35 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

Agency Agreements Process Champion Support Intern

This document will provide information on the 2018 Spring semester NIFS Intern who represented the Office of Chief Financial Officer (OCFO) as a Reimbursable Accountant at Kennedy Space Center (KSC). This intern supported the Agency Agreements Process Champions and Team Lead, Susan Kroskey, Sandy Massey and Mecca Murphy, with major initiatives to advance the KSC OCFO's vision of creating and innovating healthy financial management practices that maximize the value of resources entrusted to NASA. These initiatives include, but are not limited to: updating the Agency Guidance and NASA Procedural Guidance 9090.1 Agreements, implementing a new budget structure to be utilized across all centers, submitting a Call Request (CRQ) to enhance non-federal customer reporting, initiating a discussion to incorporate a 3-year funding program for NASA agreements, and undertaking the Office of Inspector General (OIG) Audit. In support of these initiatives, this intern identified technical methods to enhance and reduce the workload of financial processes for reimbursable and non-reimbursable agreements, prepared reports in support of accounting functions, and performed administrative work and miscellaneous technical tasks in support of the OCFO as requested. In conclusion of the internship, the intern will become knowledgeable on reimbursable accounting, reimbursable policy, types of reimbursable agreements, the agreements process, estimated pricing reports, and the roles and responsibilities of the Financial Accounting and Financial Services offices.

Process Champion↗
NASA NTRS2005

Software Certification and Software Certificate Management Systems

Incremental certification and re-certification of code as it is developed and modified is a prerequisite for applying modem, evolutionary development processes, which are especially relevant for NASA. For example, the Columbia Accident Investigation Board (CAIB) report 121 concluded there is "the need for improved and uniform statistical sampling, audit, and certification processes". Also, re-certification time has been a limiting factor in making changes to Space Shuttle code close to launch time. This is likely to be an even bigger problem with the rapid turnaround required in developing NASA s replacement for the Space Shuttle, the Crew Exploration Vehicle (CEV). Hence, intelligent development processes are needed which place certification at the center of development. If certification tools provide useful information, such as estimated time and effort, they are more likely to be adopted. The ultimate impact of such a tool will be reduced effort and increased reliability.

Denney, Ewen↗
NASA NTRSDate not supplied

Modern Scientific Data Governance Framework

Science has entered the era of Big Data with new challenges related to data governance, stewardship, and management. The existing data governance practices must catch up to ensure proper data management. Existing data governance policies and stewardship best practices tend to be disconnected from operational data management practices and enforcement and mainly exist in well-meaning documents or reports. These governance policies are, at best, partially implemented and rarely monitored or audited. In addition, existing governance policies keep adding additional data management steps that require a human, ‘a data steward’, in the loop, and the cost of data management can no longer scale proportionately with the current and future increased data volume and complexity. The goal for developing an updated data governance framework is to modernize scientific data governance to the reality of Big data and align it with the current technology trends such as cloud computing and AI. The goals of this framework are two folds. One is to ensure thoroughness that the governance adequately covers the entire data life cycle. Two, provide a practical approach that offers a consistent and repeatable process for different projects. Three core principles ground this framework. First, focus on just enough governance and prevent data governance from becoming a roadblock toward the scientific process. Remove any unnecessary processes and steps. Second, automate data management steps where possible. Actively remove steps that require ‘human in the loop’ within the management process to be efficient and scale with increasing data. Third, all the processes should continually be optimized using quantified metrics to streamline the monitoring and auditing workflows.

Rahul Ramachandran↗
NASA NTRS1983

Energy consumption analysis of the Venus Deep Space Station (DSS-13)

This report continues the energy consumption analysis and verification study of the tracking stations of the Goldstone Deep Space Communications Complex, and presents an audit of the Venus Deep Space Station (DSS 13). Due to the non-continuous radioastronomy research and development operations at the station, estimations of energy usage were employed in the energy consumption simulation of both the 9-meter and 26-meter antenna buildings. A 17.9% decrease in station energy consumption was experienced over the 1979-1981 years under study. A comparison of the ECP computer simulations and the station's main watt-hour meter readings showed good agreement.

Hayes, N. V.↗
NASA NTRS2014

IT Security Support for the Spaceport Command Control System Development

My job title is IT Security support for the Spaceport Command & Control System Development. As a cyber‐security analyst it is my job to ensure NASA's information stays safe from cyber threats, such as, viruses, malware and denial-of-service attacks by establishing and enforcing system access controls. Security is very important in the world of technology and it is used everywhere from personal computers to giant networks ran by Government agencies worldwide. Without constant monitoring analysis, businesses, public organizations and government agencies are vulnerable to potential harmful infiltration of their computer information system. It is my responsibility to ensure authorized access by examining improper access, reporting violations, revoke access, monitor information request by new programming and recommend improvements. My department oversees the Launch Control System and networks. An audit will be conducted for the LCS based on compliance with the Federal Information Security Management Act (FISMA) and The National Institute of Standards and Technology (NIST). I recently finished analyzing the SANS top 20 critical controls to give cost effective recommendations on various software and hardware products for compliance. Upon my completion of this internship, I will have successfully completed my duties as well as gain knowledge that will be helpful to my career in the future as a Cyber Security Analyst.

IT Security↗
NASA NTRS1988

Post-Challenger evaluation of space shuttle risk assessment and management

As the shock of the Space Shuttle Challenger accident began to subside, NASA initiated a wide range of actions designed to ensure greater safety in various aspects of the Shuttle system and an improved focus on safety throughout the National Space Transportation System (NSTS) Program. Certain specific features of the NASA safety process are examined: the Critical Items List (CIL) and the NASA review of the Shuttle primary and backup units whose failure might result in the loss of life, the Shuttle vehicle, or the mission; the failure modes and effects analyses (FMEA); and the hazard analysis and their review. The conception of modern risk management, including the essential element of objective risk assessment is described and it is contrasted with NASA's safety process in general terms. The discussion, findings, and recommendations regarding particular aspects of the NASA STS safety assurance process are reported. The 11 subsections each deal with a different aspect of the process. The main lessons learned by SCRHAAC in the course of the audit are summarized.

Source record↗
NASA NTRS1993

ACTS data center

Viewgraphs on ACTS Data Center status report are included. Topics covered include: ACTS Data Center Functions; data flow overview; PPD flow; RAW data flow; data compression; PPD distribution; RAW Data Archival; PPD Audit; and data analysis.

Syed, Ali↗
NASA NTRS1999

[Component and System Level of the FASTRAC Engine]

The primary activities of Lee & Associates during the period 7/20/99 to 12/31/99 as specified in the referenced Purchase Order has been in direct support of the Advanced Space Technology Program OfFice's Core Propulsion Project. An independent review to assess the program readiness to conduct component and system level testing of the FASTRAC Engine and to proceed into Fabrication has been provided. This was accomplished through the identification of program weaknesses and potential failure areas and where applicable recommended solutions were suggested to the Program Office that would mitigate technical and program risk. The approach taken to satisfy the objectives has been for the contractor to provide a team of experts with relevant experience from past programs and a strong background of experience in the fields critical to the success of the program. The team participated in Test Planning, Test Readiness Reviews for system testing at Stennis Space Center, Anomaly Resolution Reviews, an Operations Audit, and data analysis. This approach worked well in satisfying the objectives and providing the Project Office with valuable information in real time and through monthly reports. During the month of December 1999 the primary effort involved the participation in anomaly resolution and the detailed review of the data from the final H3 and H4 test series performed on the FASTRAC engine in the b-2 Horizontal Test Facility at Stennis. The more significant findings and recommendations from this review are presented in this report.

Source record↗
NASA NTRS1997

Measurement and Analysis of Failures in Computer Systems

This thesis presents a study of software failures spanning several different releases of Tandem's NonStop-UX operating system running on Tandem Integrity S2(TMR) systems. NonStop-UX is based on UNIX System V and is fully compliant with industry standards, such as the X/Open Portability Guide, the IEEE POSIX standards, and the System V Interface Definition (SVID) extensions. In addition to providing a general UNIX interface to the hardware, the operating system has built-in recovery mechanisms and audit routines that check the consistency of the kernel data structures. The analysis is based on data on software failures and repairs collected from Tandem's product report (TPR) logs for a period exceeding three years. A TPR log is created when a customer or an internal developer observes a failure in a Tandem Integrity system. This study concentrates primarily on those TPRs that report a UNIX panic that subsequently crashes the system. Approximately 200 of the TPRs fall into this category. Approximately 50% of the failures reported are from field systems, and the rest are from the testing and development sites. It has been observed by Tandem developers that fewer cases are encountered from the field than from the test centers. Thus, the data selection mechanism has introduced a slight skew.

Thakur, Anshuman↗
NASA NTRS2022

Assessing Several Non-Traditional Data Sources for Value in Aviation Safety

The NASA System-Wide Safety (SWS) project and its predecessor projects have been developing Machine Learning (ML) algorithms for commercial aviation safety for many years. These algorithms have been applied to Flight Operations Quality Assurance (FOQA); radar track data (e.g., Threaded Track); and safety reports, including Aviation Safety Reporting System (ASRS) and Aviation Safety Action Plan (ASAP). SWS is working with partners to get access to other data that air carriers provide, such as maintenance data, and has been assisting carriers in working with other data, such as Line Operations Safety Audit (LOSA) data, using manual methods. However, the project has discussed whether there are other data that are not traditionally used in aviation safety analysis that may be useful. This paper discusses four sets of data and models that are not traditionally used in aviation safety but that have shown promise for such use. In the future, we plan to incorporate such data into ML algorithms to use with data that we have used before and determine the additional benefit that is actually achieved under different contexts from the inclusion of these non-traditional data sources.

Nikunj C. Oza↗
NASA NTRS2012

Security Data Warehouse Application

The Security Data Warehouse (SDW) is used to aggregate and correlate all JSC IT security data. This includes IT asset inventory such as operating systems and patch levels, users, user logins, remote access dial-in and VPN, and vulnerability tracking and reporting. The correlation of this data allows for an integrated understanding of current security issues and systems by providing this data in a format that associates it to an individual host. The cornerstone of the SDW is its unique host-mapping algorithm that has undergone extensive field tests, and provides a high degree of accuracy. The algorithm comprises two parts. The first part employs fuzzy logic to derive a best-guess host assignment using incomplete sensor data. The second part is logic to identify and correct errors in the database, based on subsequent, more complete data. Host records are automatically split or merged, as appropriate. The process had to be refined and thoroughly tested before the SDW deployment was feasible. Complexity was increased by adding the dimension of time. The SDW correlates all data with its relationship to time. This lends support to forensic investigations, audits, and overall situational awareness. Another important feature of the SDW architecture is that all of the underlying complexities of the data model and host-mapping algorithm are encapsulated in an easy-to-use and understandable Perl language Application Programming Interface (API). This allows the SDW to be quickly augmented with additional sensors using minimal coding and testing. It also supports rapid generation of ad hoc reports and integration with other information systems.

Vernon, Lynn R.↗
NASA NTRS2003

Performance and Accountability Report

The NASA Fiscal Year 2002 Performance and Accountability Report is presented. Over the past year, significant changes have been implemented to greatly improve NASA's management while continuing to break new ground in science and technology. Excellent progress has been made in implementing the President's Management Agenda. NASA is leading the government in its implementation of the five government-wide initiatives. NASA received an unqualified audit opinion on FY 2002 financial statements. The vast majority of performance goals have been achieved, furthering each area of NASA's mission. The contents include: 1) NASA Vision and Mission; 2) Management's Discussion and Analysis; 3) Performance; and 4) Financial.

Source record↗
NASA NTRS1981

Report by the Aerospace Safety Advisory Panel

The process of preparation for the first two shuttle flights was observed and information from both flights was gathered in order to confirm the concept and performance of the major elements of the space transportation system. To achieve truly operational operating safety, regularity, and minimum practical cost, the organization of efforts between the R&D community and any transportation service organization should be clearly separated with the latter organization assuming responsibilities for marketing its services; planning and acquiring prime hardware and spares; maintainance; certification of procedures; training; and creation of requirements for future development. A technical audit of the application of redundancy concepts to shuttle systems is suggested. The state of the art of space transportation hardware suggests that a number of concept changes may improve reliability, costs, and operational safety. For the remaining R&D flights, it is suggested that a redline audit be made of limits that should not be exceeded for ready to launch.

Source record↗
NASA NTRS2007

Electrostatic Evaluation of the SRB Velostat(Trademark) Pads

During RSRM Grain inspection, pads constructed of Velostat are grounded and installed in the RSRM bore enabling inspectors to move throughout the bore during the inspection. Velostat pads are installed by grounding the first pad installed and subsequent pads are installed overlapping the previously installed pad maintaining a conductive path to facility ground. Pads are removed upon completion of the inspection in a reverse fashion. As the pads are removed scanning of propellant surfaces is performed per OMRS. During PPICI Audit of B5308.006 (Forward Segment Grain Inspection) in October 07 one audit finding noted that electrostatic scanning of propellant surfaces was being performed during removal of conductive pads following grain inspection. ATK does not perform electrostatic scanning of propellant surfaces during pad removal following final inspection at the plant. The integrated team consisting of NASA SE, USA SE, USA QE, ATK LSS, ATK Systems Safety and ATK DE concurred that electrostatic scanning of propellant surfaces was unnecessary as the conductive pads are grounded. Additional time spent in bore performing scanning presents itself as additional risk. Technicians reported that they have never seen any voltage readings while scanning propellant surfaces during pad removal. USA Systems engineering has written KB 17530 in response to the finding which will delete the requirement (item 2 B47GEN.ll0) to scan propellant surfaces during pad removal. As a result of an E3 panel discussion on December 13, 2007, it was decided that verification of the electrical grounding of the Velostat pads be verified.

Buhler, Charles R.↗
NASA NTRS2004

ISS Asset Tracking Using SAW RFID Technology

A team at the NASA Johnson Space Center (JSC) is undergoing final preparations to test Surface Acoustic Wave (SAW) Radio Frequency Identification (RFID) technology to track assets aboard the International Space Station (ISS). Currently, almost 10,000 U.S. items onboard the ISS are tracked within a database maintained by both the JSC ground teams and crew onboard the ISS. This barcode-based inventory management system has successfully tracked the location of 97% of the items onboard, but its accuracy is dependant on the crew to report hardware movements, taking valuable time away from science and other activities. With the addition of future modules, the volume of inventory to be tracked is expected to increase significantly. The first test of RFID technology on ISS, which will be conducted by the Expedition 16 crew later this year, will evaluate the ability of RFID technology to track consumable items. These consumables, which include office supplies and clothing, are regularly supplied to ISS and can be tagged on the ground. Automation will eliminate line-of-sight auditing requirements, directly saving crew time. This first step in automating an inventory tracking system will pave the way for future uses of RFID for inventory tracking in space. Not only are there immediate benefits for ISS applications, it is a crucial step to ensure efficient logistics support for future vehicles and exploration missions where resupplies are not readily available. Following a successful initial test, the team plans to execute additional tests for new technology, expanded operations concepts, and increased automation.

Schellhase, Amy↗
NASA NTRS1998

MRM Evaluation Research Program

This is an interim report on the current output of the MRM evaluation research program. During 1998 this research program has used new and existing data to create an important tool for the development and improvement of "maintenance resource management" (MRM). Thousands of surveys completed by participants in airline MRM training and/or behavior change programs have, for the first time, been consolidated into a panel of "MRM Attitudes and Opinion Profiles." These profiles can be used to compare the attitudes about decision making and communication in any given company at any stage in its MRM program with attitudes of a large sample of like employees during a similar period in their MRM involvement. This panel of comparison profiles for attitudes and opinions is a tool to help audit the effectiveness of a maintenance human factors program. The profile panel is the first of several tools envisioned for applying the information accumulating in MRM databases produced as one of the program's long range objectives.

Taylor, James C.↗
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↗