Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “reporting”

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 775 records · Page 43
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

International Space Station Increment-6/8 Microgravity Environment Summary Report November 2002 to April 2004

This summary report presents the analysis results of some of the processed acceleration data measured aboard the International Space Station during the period of November 2002 to April 2004. Two accelerometer systems were used to measure the acceleration levels for the activities that took place during Increment-6/8. However, not all of the activities during that period were analyzed in order to keep the size of the report manageable. The National Aeronautics and Space Administration sponsors the Microgravity Acceleration Measurement System and the Space Acceleration Measurement System to support microgravity science experiments that require microgravity acceleration measurements. On April 19, 2001, both the Microgravity Acceleration Measurement System and the Space Acceleration Measurement System units were launched on STS-100 from the Kennedy Space Center for installation on the International Space Station. The Microgravity Acceleration Measurement System unit was flown to the station in support of science experiments requiring quasi-steady acceleration measurements, while the Space Acceleration Measurement System unit was flown to support experiments requiring vibratory acceleration measurement. Both acceleration systems are also used in support of the vehicle microgravity requirements verification as well as in support of the International Space Station support cadre. The International Space Station Increment-6/8 reduced gravity environment analysis presented in this report uses acceleration data collected by both sets of accelerometer systems: 1. The Microgravity Acceleration Measurement System, which consists of two sensors: the Orbital Acceleration Research Experiment Sensor Subsystem, a low frequency range sensor (up to 1 Hz), is used to characterize the quasi-steady environment for payloads and vehicle, and the High Resolution Accelerometer Package, which is used to characterize the vibratory environment up to 100 Hz. 2. The Space Acceleration Measurement System measures vibratory acceleration data in the range of 0.01 to 400 Hz. This summary report presents analysis of some selected quasi-steady and vibratory activities measured by these accelerometers during Increment-6/8 from November 2002 to April 2004.

Jules, Kenol↗
NASA NTRS2006

What Happened, and Why: Toward an Understanding of Human Error Based on Automated Analyses of Incident Reports

The objective of the Aviation System Monitoring and Modeling (ASMM) project of NASA s Aviation Safety and Security Program was to develop technologies that will enable proactive management of safety risk, which entails identifying the precursor events and conditions that foreshadow most accidents. This presents a particular challenge in the aviation system where people are key components and human error is frequently cited as a major contributing factor or cause of incidents and accidents. In the aviation "world", information about what happened can be extracted from quantitative data sources, but the experiential account of the incident reporter is the best available source of information about why an incident happened. This report describes a conceptual model and an approach to automated analyses of textual data sources for the subjective perspective of the reporter of the incident to aid in understanding why an incident occurred. It explores a first-generation process for routinely searching large databases of textual reports of aviation incident or accidents, and reliably analyzing them for causal factors of human behavior (the why of an incident). We have defined a generic structure of information that is postulated to be a sound basis for defining similarities between aviation incidents. Based on this structure, we have introduced the simplifying structure, which we call the Scenario as a pragmatic guide for identifying similarities of what happened based on the objective parameters that define the Context and the Outcome of a Scenario. We believe that it will be possible to design an automated analysis process guided by the structure of the Scenario that will aid aviation-safety experts to understand the systemic issues that are conducive to human error.

Maille, Nicolas P.↗
NASA NTRS2006

GEOSAT Follow-On (GFO) Altimeter Document Series, Volume 8: GFO Altimeter Engineering Assessment Report Update:The First 109 Cycles Since Acceptance November 29, 2000 to December 26, 2005

The purpose of this document is to present and document GFO performance analyses and results. This is the fifth Assessment Report since the initial report. This report extends the performance assessment since acceptance to 26 December 2005. The initial GFO Altimeter Engineering Assessment Report, March 2001 (NASA/TM-2001-209984/Ver.1/Vol.1) covered the GFO performance from Launch to Acceptance (10 February 1998 to 29 November 2000). The second of the series covered the performance from Acceptance to the end of Cycle 20 (29 November 2000 to 21 November 2001). The third of the series covered the performance from Acceptance to the end of Cycle 42 (29 November 2000 to 30 November 2002). The fourth of the series covered the performance from Acceptance to the end of Cycle 64 (29 November 2000 to 17 December 2003). The fifth of the series covered performance from Acceptance to the end of Cycle 86 (29 November 2000 to 17 December 2004). Since launch, we have performed a variety of GFO performance studies; an accumulative index of those studies is provided in Appendix A.

Conger, A. M.↗
NASA NTRS2008

Tropospheric Airborne Meteorological Data Reporting (TAMDAR) Overview

This paper is an overview of the Tropospheric Airborne Meteorological Data Reporting (TAMDAR) project, giving some history on the project, various applications of the atmospheric data, and future ideas and plans. As part of NASA's Aviation Safety and Security Program, the TAMDAR project developed a small low-cost sensor that collects useful meteorological data and makes them available in near real time to improve weather forecasts. This activity has been a joint effort with FAA, NOAA, universities, and industry. A tri-agency team collaborated by developing a concept of operations, determining the sensor specifications, and evaluating sensor performance as reported by Moosakhanian et. al. (2006). Under contract with Georgia Tech Research Institute, NASA worked with AirDat of Raleigh, NC to develop the sensor. The sensor is capable of measuring temperature, relative humidity, pressure, and icing. It can compute pressure altitude, indicated and true air speed, ice accretion rate, wind speed and direction, peak and average turbulence, and eddy dissipation rate. The overall development process, sensor capabilities, and performance based on ground and flight tests is reported by Daniels (2002), Daniels et. al. (2004) and by Tsoucalas et. al. (2006). An in-service evaluation of the sensor was performed called the Great Lakes Fleet Experiment (GLFE), first reported by Moninger et. al. (2004) and Mamrosh et. al. (2005). In this experiment, a Mesaba Airlines fleet was equipped to collect meteorological data over the Great Lakes region during normal revenue-producing flights.

Daniels, Taumi S.↗
NASA NTRS2008

GFO and JASON Altimeter Engineering Assessment Report. Update: GFO--Acceptance to December 27, 2007, JASON--Acceptance to December 26, 2007. Version 1: June 2008

The purpose of this document is to present and document GEOSAT Follow-On (GFO) performance analyses and results. This is the eighth Assessment Report since the initial report. This report extends the performance assessment since acceptance to 27 December 2007. Since launch, a variety of GFO performance studies have been performed: Appendix A provides an accumulative index of those studies. We began the inclusion of analyses of the JASON altimeter after the end of the Topographic Experiment (TOPEX) mission. Prior to this, JASON and TOPEX were compared during our assessment of theTOPEX altimeter. With the end of the TOPEX mission, we developed methods to report on JASON as it relates to GFO.

Conger, A. M.↗
NASA NTRS2008

ABM Drag_Pass Report Generator

dragREPORT software was developed in parallel with abmREPORT, which is described in the preceding article. Both programs were built on the capabilities created during that process. This tool generates a drag_pass report that summarizes vital information from the MRO aerobreaking drag_pass build process to facilitate both sequence reviews and provide a high-level summarization of the sequence for mission management. The script extracts information from the ENV, SSF, FRF, SCMFmax, and OPTG files, presenting them in a single, easy-to-check report providing the majority of parameters needed for cross check and verification as part of the sequence review process. Prior to dragReport, all the needed information was spread across a number of different files, each in a different format. This software is a Perl script that extracts vital summarization information and build-process details from a number of source files into a single, concise report format used to aid the MPST sequence review process and to provide a high-level summarization of the sequence for mission management reference. This software could be adapted for future aerobraking missions to provide similar reports, review and summarization information.

Fisher, Forest↗
NASA NTRS2008

Patterns of Error in Confidential Maintenance Incident Reports

Confidential reports of maintenance incidents are a valuable source of information on maintenance errors and the contexts within which they occur. NASA's Aviation Safety Reporting System (ASRS) has been receiving an increasing number of maintenance incident reports since a specialized maintenance reporting form was introduced in 1996. In a series of studies, the database of ASRS maintenance incidents was examined using correspondence analysis, a statistical technique that converts complex data tables into a visual form. The analyses revealed patterns within the ASRS data set that would have otherwise been difficult to detect. The results have implications for a range of purposes including human factors training, the design of procedures, and the identification of improvements in aircraft design.

Hobbs, Alan↗
NASA NTRS2010

Reporting Differences Between Spacecraft Sequence Files

A suite of computer programs, called seq diff suite, reports differences between the products of other computer programs involved in the generation of sequences of commands for spacecraft. These products consist of files of several types: replacement sequence of events (RSOE), DSN keyword file [DKF (wherein DSN signifies Deep Space Network)], spacecraft activities sequence file (SASF), spacecraft sequence file (SSF), and station allocation file (SAF). These products can include line numbers, request identifications, and other pieces of information that are not relevant when generating command sequence products, though these fields can result in the appearance of many changes to the files, particularly when using the UNIX diff command to inspect file differences. The outputs of prior software tools for reporting differences between such products include differences in these non-relevant pieces of information. In contrast, seq diff suite removes the fields containing the irrelevant pieces of information before processing to extract differences, so that only relevant differences are reported. Thus, seq diff suite is especially useful for reporting changes between successive versions of the various products and in particular flagging difference in fields relevant to the sequence command generation and review process.

Khanampompan, Teerapat↗
NASA NTRS2010

2009 NASA Range Safety Annual Report

This year, NASA Range Safety transitioned to a condensed annual report to allow for Secretariat support to the Range Safety Group, Risk Committee. Although much shorter than in previous years, this report contains full-length articles concerning various subject areas, as well as links to past reports. Additionally, summaries from various NASA Range Safety Program activities that took place throughout the year are presented, as well as information on several projects that may have a profound impact on the way business will be done in the future. The sections include a program overview and 2009 highlights; Range Safety Training; Range Safety Policy; Independent Assessments Support to Program Operations at all ranges conducting NASA launch operations; a continuing overview of emerging range safety-related technologies; and status reports from all of the NASA Centers that have Range Safety responsibilities.

Source record↗
NASA NTRS2003

The ISS Increments 3 and 4 Test Report: For the Active Rack Isolation System ISS Characterization Experiment (ARIS-ICE)

The purpose of ARIS-ICE is to improve, optimize then operationally test and document the performance of the ARIS system on the International Space Station. The ICE program required testing across a full 3 increments (2 through 4). This paper represents the operational report summarizing our accomplishments through the third and fourth increment of testing. The main objectives and results of the increment two testing are discussed in The Increment two Operational Report. This report can be obtained from the ISS Payloads Office or from (http://iss-www.isc.nasa.gov/sslissapt/payofc/OZ3/ARIS.html). In summary these were to ensure the smooth and successful activation of the system and correct operational issues related to long term testing. Then the follow on increment 3 & 4 testing encompassed the majority of the on orbit performance assessments and improvements made to the ARIS system. The intent here is to report these preliminary results of the increment 3 & 4 ARIS-ICE testing as well as the ARIS system improvements made for our users and customers.

Quraishi, Naveed↗
NASA NTRS2013

Determining Component Probability using Problem Report Data for Ground Systems used in Manned Space Flight

During the shuttle era NASA utilized a failure reporting system called the Problem Reporting and Corrective Action (PRACA) it purpose was to identify and track system non-conformance. The PRACA system over the years evolved from a relatively nominal way to identify system problems to a very complex tracking and report generating data base. The PRACA system became the primary method to categorize any and all anomalies from corrosion to catastrophic failure. The systems documented in the PRACA system range from flight hardware to ground or facility support equipment. While the PRACA system is complex, it does possess all the failure modes, times of occurrence, length of system delay, parts repaired or replaced, and corrective action performed. The difficulty is mining the data then to utilize that data in order to estimate component, Line Replaceable Unit (LRU), and system reliability analysis metrics. In this paper, we identify a methodology to categorize qualitative data from the ground system PRACA data base for common ground or facility support equipment. Then utilizing a heuristic developed for review of the PRACA data determine what reports identify a credible failure. These data are the used to determine inter-arrival times to perform an estimation of a metric for repairable component-or LRU reliability. This analysis is used to determine failure modes of the equipment, determine the probability of the component failure mode, and support various quantitative differing techniques for performing repairable system analysis. The result is that an effective and concise estimate of components used in manned space flight operations. The advantage is the components or LRU's are evaluated in the same environment and condition that occurs during the launch process.

Monaghan, Mark W.↗
NASA NTRS2014

The Relationship Between CO2 Levels and CO2 Related Symptoms Reported on the ISS

Medical Operations, Toxicology, and the Lifetime Surveillance of Astronaut Health collaborated to assess the association of CO2 levels on board the International Space Station and USOS crew reported symptoms inflight, i.e. headache and vision changes. Private Medical Conference (PMC) documents and the weekly Space Medicine Operations Team (SMOT) Notes were used to provide a robust data set of inflight medical events. All events and non‐events were documented independent of CO2 levels and other potential contributors. Average (arithmetic mean) and single point maximum ppCO2 was calculated for the 24 hours and 7 days prior to the PMC or SMOT date and time provided by LSAH. Observations falling within the first 7 days of flight (147) were removed from the datasets analyzed to avoid confounding with Space Adaptation Syndrome. The final analysis was based on 1716 observations. For headache, 46 headaches were observed. CO2 level, age at launch, time inflight, and data source were all significantly associated with headache. In particular, for each 1 mmHg increase in CO2, the odds of a crewmember reporting a headache doubled. For vision changes, 29 reports of vision changes were observed. These observations were not found to be statistically associated with CO2 levels as analyzed. While the incidence of headache has was not high (~3%), headaches may be an indicator of underlying increases in intracranial pressure, which may result likely from the synergy between CO2‐induced cerebral vasodilatation and decreased venous drainage in microgravity. Vision changes were inconsistently reported and as a result did not align appropriately with the CO2 levels. Further analysis is needed. Our results support ongoing efforts to lower the CO2 exposure limits in spacecraft.

VanBaalen, M.↗
NASA NTRS2015

KSC 50-MHz Doppler Radar Wind Profiler (DRWP) Operational Acceptance Test (OAT) Report

This report documents analysis results of the Kennedy Space Center updated 50-MHz Doppler Radar Wind Profiler (DRWP) Operational Acceptance Test (OAT). This test was designed to demonstrate that the new DRWP operates in a similar manner to the previous DRWP for use as a situational awareness asset for mission operations at the Eastern Range to identify rapid changes in the wind environment that weather balloons cannot depict. Data examination and two analyses showed that the updated DRWP meets the specifications in the OAT test plan and performs at least as well as the previous DRWP. Data examination verified that the DRWP provides complete profiles every five minutes from 1.8-19.5 km in vertical increments of 150 m. Analysis of 5,426 wind component reports from 49 concurrent DRWP and balloon profiles presented root mean square (RMS) wind component differences around 2.0 m/s. The DRWP's effective vertical resolution (EVR) was found to be 300 m for both the westerly and southerly wind component, which the best EVR possible given the DRWP's vertical sampling interval. A third analysis quantified the sensitivity to rejecting data that do not have adequate signal by assessing the number of first-guess propagations at each altitude. This report documents the data, quality control procedures, methodology, and results of each analysis. It also shows that analysis of the updated DRWP produced results that were at least as good as the previous DRWP with proper rationale. The report recommends acceptance of the updated DRWP for situational awareness usage as per the OAT's intent.

Profiler↗
NASA NTRS2015

Contractors Road Heavy Equipment Area SWMU 055 Corrective Measures Implementation Progress Report Kennedy Space Center, Florida

This Corrective Measures Implementation (CMI) Progress Report documents: (i) activities conducted as part of supplemental assessment activities completed from June 2009 through November 2014; (ii) Engineering Evaluation (EE) Advanced Data Packages (ADPs); and (iii) recommendations for future activities related to corrective measures at the Site. Applicable meeting minutes are provided as Appendix A. The following EE ADPs for CRHE are included with this CMI Progress Report: center dot Supplemental Site Characterization ADP (Step 1 EE) (Appendix B) center dot Site Characterization ADP (Step 1 EE) for Hot Spot 1 (HS1) (Appendix C) center dot Remedial Alternatives Evaluation (Step 2 EE) ADP for HS1 (Appendix D) center dot Interim Measures Work Plan (Step 3 EE) ADP for HS1 (Appendix E) center dot Site Characterization ADP (Step 1 EE) ADP for Hot Spot 2 (HS2), High Concentration Plume (HCP), and Low Concentration Plume (LCP) (Appendix F) A summary of direct-push technology (DPT) and groundwater monitoring well sampling results are provided in Appendices G and H, respectively. The Interim Land Use Control Implementation Plan (LUCIP) is provided as Appendix I. Monitoring well completion reports, other applicable field forms, survey data, and analytical laboratory reports are provided as Appendices J through M, respectively, in the electronic copy of this document. Selected Site photographs are provided in Appendix N. The interim groundwater monitoring plan and document revision log are included as Appendices O and P, respectively. KSC Electronic Data Deliverable (KEDD) files are provided on the attached compact disk.

Johnson, Jill W.↗
NASA NTRS2016

Empirical Analysis and Automated Classification of Security Bug Reports

With the ever expanding amount of sensitive data being placed into computer systems, the need for effective cybersecurity is of utmost importance. However, there is a shortage of detailed empirical studies of security vulnerabilities from which cybersecurity metrics and best practices could be determined. This thesis has two main research goals: (1) to explore the distribution and characteristics of security vulnerabilities based on the information provided in bug tracking systems and (2) to develop data analytics approaches for automatic classification of bug reports as security or non-security related. This work is based on using three NASA datasets as case studies. The empirical analysis showed that the majority of software vulnerabilities belong only to a small number of types. Addressing these types of vulnerabilities will consequently lead to cost efficient improvement of software security. Since this analysis requires labeling of each bug report in the bug tracking system, we explored using machine learning to automate the classification of each bug report as a security or non-security related (two-class classification), as well as each security related bug report as specific security type (multiclass classification). In addition to using supervised machine learning algorithms, a novel unsupervised machine learning approach is proposed. An ac- curacy of 92%, recall of 96%, precision of 92%, probability of false alarm of 4%, F-Score of 81% and G-Score of 90% were the best results achieved during two-class classification. Furthermore, an accuracy of 80%, recall of 80%, precision of 94%, and F-score of 85% were the best results achieved during multiclass classification.

Cybersecurity↗
NASA NTRS2017

ATD-1 Avionics Phase 2: Post-Flight Data Analysis Report

This report aims to satisfy Air Traffic Management Technology Demonstration - 1 (ATD-1) Statement of Work (SOW) 3.6.19 and serves as the delivery mechanism for the analysis described in Annex C of the Flight Test Plan. The report describes the data collected and derived as well as the analysis methodology and associated results extracted from the data set collected during the ATD-1 Flight Test. All analyses described in the SOW were performed and are covered in this report except for the analysis of Final Approach Speed and its effect on performance. This analysis was de-prioritized and, at the time of this report, is not considered feasible in the schedule and costs remaining.

Scharl, Julien↗
NASA NTRS2018

Small Spacecraft Systems Virtual Institute's Federated Databases and State of the Art of Small Spacecraft Technology Report

NASA's Small Spacecraft Systems Virtual Institute (S3VI) is collaborating with the Air Force Research Laboratory and Space Dynamics Laboratory on the development of a small spacecraft parts database called SmallSat Parts On Orbit Now (SPOON). The SPOON database contains small spacecraft parts and technologies categorized by major satellite subsystems developed by industry, academia and government. The State of the Art of Small Spacecraft Technology report reflects small spacecraft parts submitted to the SPOON database and technologies compiled from other sources that were assessed as the current state of the art in each of the major subsystems. The report, first commissioned by NASA's Small Spacecraft Technology Program in mid-2013, is developed in response to the continuing growth in interest in using small spacecraft for many types of missions in Earth orbit and beyond. Due to the high market penetration of CubeSats, particular emphasis is placed on the state of the art of CubeSat-related technology. The 2018 report is planned for release in late summer. A review of SPOON database functionality, federation of additional NASA-internal and external databases along with a common search capability, as well as an overview of the State of the Art of Small Spacecraft Technology report will be presented. The S3VI is jointly sponsored by NASA's Space Technology Mission Directorate and Science Mission Directorate.

Small spacecraft↗
NASA NTRS2016

Human Factors of Remotely Piloted Aircraft Systems: Lessons from Incident Reports

It has been estimated that aviation accidents are typically preceded by numerous minor incidents arising from the same causal factors that ultimately produced the accident. Accident databases provide in-depth information on a relatively small number of occurrences, however incident databases have the potential to provide insights into the human factors of Remotely Piloted Aircraft System (RPAS) operations based on a larger volume of less-detailed reports. Currently, there is a lack of incident data dealing with the human factors of unmanned aircraft systems. An exploratory study is being conducted to examine the feasibility of collecting voluntary critical incident reports from RPAS pilots. Twenty-three experienced RPAS pilots volunteered to participate in focus groups in which they described critical incidents from their own experience. Participants were asked to recall (1) incidents that revealed a system flaw, or (2) highlighted a case where the human operator contributed to system resilience or mission success. A total of 90 incidents were reported. This presentation begins with an overview of RPAS human factors and then considers the emerging issues identified by pilot reports.

incidents↗