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 361 records · Page 20
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Columbia Accident Investigation Board Report. Volume Three

The Columbia Accident Investigation Board's (CAIB) independent investigation into the February 1, 2003 destruction of the Space Shuttle Columbia produced a six volume report. This is Volume III of the report. Volume III contains other technical documents produced by NASA and other organizations, which were provided to the CAIB in support of its inquiry into the tragedy. Technical documents included in the report are: Appendix E.1 CoFR Endorsements; Appendix E.2 STS-107 Image Analysis Team Final Report; Appendix E.3 An Assessment of Potential Material Candidates for the 'Flight Day 2', Radar Object Observed during the NASA Mission STS-107; Appendix E.4 Columbia Early Sighting Assessment Team Final Report.

STS-107↗
NASA NTRS2003

NASA's Space Shuttle Columbia: Synopsis of the Report of the Columbia Accident Investigation Board

NASA's space shuttle Columbia broke apart on February 1, 2003 as it returned to Earth from a 16-day science mission. All seven astronauts aboard were killed. NASA created the Columbia Accident Investigation Board (CAIB), chaired by Adm. (Ret.) Harold Gehman, to investigate the accident. The Board released its report (available at [http://www.caib.us]) on August 26, 2003, concluding that the tragedy was caused by technical and organizational failures. The CAIB report included 29 recommendations, 15 of which the Board specified must be completed before the shuttle returns to flight status. This report provides a brief synopsis of the Board's conclusions, recommendations, and observations. Further information on Columbia and issues for Congress are available in CRS Report RS21408. This report will not be updated.

Smith, Marcia S.↗
NASA NTRS2003

Using System Mass (SM), Equivalent Mass (EM), Equivalent System Mass (ESM) or Life Cycle Mass (LCM) in Advanced Life Support (ALS) Reporting

The Advanced Life Support (ALS) has used a single number, Equivalent System Mass (ESM), for both reporting progress and technology selection. ESM is the launch mass required to provide a space system. ESM indicates launch cost. ESM alone is inadequate for technology selection, which should include other metrics such as Technology Readiness Level (TRL) and Life Cycle Cost (LCC) and also consider perfom.arxe 2nd risk. ESM has proven difficult to implement as a reporting metric, partly because it includes non-mass technology selection factors. Since it will not be used exclusively for technology selection, a new reporting metric can be made easier to compute and explain. Systems design trades-off performance, cost, and risk, but a risk weighted cost/benefit metric would be too complex to report. Since life support has fixed requirements, different systems usually have roughly equal performance. Risk is important since failure can harm the crew, but it is difficult to treat simply. Cost is not easy to estimate, but preliminary space system cost estimates are usually based on mass, which is better estimated than cost. Amass-based cost estimate, similar to ESM, would be a good single reporting metric. The paper defines and compares four mass-based cost estimates, Equivalent Mass (EM), Equivalent System Mass (ESM), Life Cycle Mass (LCM), and System Mass (SM). EM is traditional in life support and includes mass, volume, power, cooling and logistics. ESM is the specifically defined ALS metric, which adds crew time and possibly other cost factors to EM. LCM is a new metric, a mass-based estimate of LCC measured in mass units. SM includes only the factors of EM that are originally measured in mass, the hardware and logistics mass. All four mass-based metrics usually give similar comparisons. SM is by far the simplest to compute and easiest to explain.

Jones, Harry↗
NASA NTRS1992

Mission Operations Report (MOR) for the Solar, Anomalous, and Magnetosphere Particle Explorer (SAMPEX)

MISSION OPERATIONS REPORTS are published for use by NASA senior management, as required by NASA Headquarters Management Instruction HQMI 8610. lC, effective November 26, 1991. The purpose of these reports is to provide a documentation system that represents an internal discipline to establish critical discriminators selected in advance to measure mission accomplishment, provide a formal written assessment of mission accomplishment, and provide an accountability of technical achievement. Prelaunch reports are prepared and issued for each flight project just prior to launch. Following launch, updating (Post Launch) reports are issued to provide mission status and progress in meeting mission objectives. Primary distribution of these reports is intended for personnel having program/project management responsibilities.

Source record↗
NASA NTRS2006

Enabling the Discovery of Recurring Anomalies in Aerospace System Problem Reports using High-Dimensional Clustering Techniques

This paper describes the results of a significant research and development effort conducted at NASA Ames Research Center to develop new text mining techniques to discover anomalies in free-text reports regarding system health and safety of two aerospace systems. We discuss two problems of significant importance in the aviation industry. The first problem is that of automatic anomaly discovery about an aerospace system through the analysis of tens of thousands of free-text problem reports that are written about the system. The second problem that we address is that of automatic discovery of recurring anomalies, i.e., anomalies that may be described m different ways by different authors, at varying times and under varying conditions, but that are truly about the same part of the system. The intent of recurring anomaly identification is to determine project or system weakness or high-risk issues. The discovery of recurring anomalies is a key goal in building safe, reliable, and cost-effective aerospace systems. We address the anomaly discovery problem on thousands of free-text reports using two strategies: (1) as an unsupervised learning problem where an algorithm takes free-text reports as input and automatically groups them into different bins, where each bin corresponds to a different unknown anomaly category; and (2) as a supervised learning problem where the algorithm classifies the free-text reports into one of a number of known anomaly categories. We then discuss the application of these methods to the problem of discovering recurring anomalies. In fact the special nature of recurring anomalies (very small cluster sizes) requires incorporating new methods and measures to enhance the original approach for anomaly detection. ?& pant 0-

Srivastava, Ashok, N.↗
NASA NTRS2006

NASA Taxonomies for Searching Problem Reports and FMEAs

Many types of hazard and risk analyses are used during the life cycle of complex systems, including Failure Modes and Effects Analysis (FMEA), Hazard Analysis, Fault Tree and Event Tree Analysis, Probabilistic Risk Assessment, Reliability Analysis and analysis of Problem Reporting and Corrective Action (PRACA) databases. The success of these methods depends on the availability of input data and the analysts knowledge. Standard nomenclature can increase the reusability of hazard, risk and problem data. When nomenclature in the source texts is not standard, taxonomies with mapping words (sets of rough synonyms) can be combined with semantic search to identify items and tag them with metadata based on a rich standard nomenclature. Semantic search uses word meanings in the context of parsed phrases to find matches. The NASA taxonomies provide the word meanings. Spacecraft taxonomies and ontologies (generalization hierarchies with attributes and relationships, based on terms meanings) are being developed for types of subsystems, functions, entities, hazards and failures. The ontologies are broad and general, covering hardware, software and human systems. Semantic search of Space Station texts was used to validate and extend the taxonomies. The taxonomies have also been used to extract system connectivity (interaction) models and functions from requirements text. Now the Reconciler semantic search tool and the taxonomies are being applied to improve search in the Space Shuttle PRACA database, to discover recurring patterns of failure. Usual methods of string search and keyword search fall short because the entries are terse and have numerous shortcuts (irregular abbreviations, nonstandard acronyms, cryptic codes) and modifier words cannot be used in sentence context to refine the search. The limited and fixed FMEA categories associated with the entries do not make the fine distinctions needed in the search. The approach assigns PRACA report titles to problem classes in the taxonomy. Each ontology class includes mapping words - near-synonyms naming different manifestations of that problem class. The mapping words for Problems, Entities and Functions are converted to a canonical form plus any of a small set of modifier words (e.g. non-uniformity NOT + UNIFORM.) The report titles are parsed as sentences if possible, or treated as a flat sequence of word tokens if parsing fails. When canonical forms in the title match mapping words, the PRACA entry is associated with the corresponding Problem, Entity or Function in the ontology. The user can search for types of failures associated with types of equipment, clustering by type of problem (e.g., all bearings found with problems of being uneven: rough, irregular, gritty ). The results could also be used for tagging PRACA report entries with rich metadata. This approach could also be applied to searching and tagging failure modes, failure effects and mitigations in FMEAs. In the pilot work, parsing 52K+ truncated titles (the test cases that were available), has resulted in identification of both a type of equipment and type of problem in about 75% of the cases. The results are displayed in a manner analogous to Google search results. The effort has also led to the enrichment of the taxonomy, adding some new categories and many new mapping words. Further work would make enhancements that have been identified for improving the clustering and further reducing the false alarm rate. (In searching for recurring problems, good clustering is more important than reducing false alarms). Searching complete PRACA reports should lead to immediate improvement.

Malin, Jane T.↗
NASA NTRS2008

Problem Reporting System

The Problem Reporting System (PRS) is a Web application, running on two Web servers (load-balanced) and two database servers (RAID-5), which establishes a system for submission, editing, and sharing of reports to manage risk assessment of anomalies identified in NASA's flight projects. PRS consolidates diverse anomaly-reporting systems, maintains a rich database set, and incorporates a robust engine, which allows tracking of any hardware, software, or paper process by configuring an appropriate life cycle. Global and specific project administration and setup tools allow lifecycle tailoring, along with customizable controls for user, e-mail, notifications, and more. PRS is accessible via the World Wide Web for authorized user at most any location. Upon successful log-in, the user receives a customizable window, which displays time-critical 'To Do' items (anomalies requiring the user s input before the system moves the anomaly to the next phase of the lifecycle), anomalies originated by the user, anomalies the user has addressed, and custom queries that can be saved for future use. Access controls exist depending on a user's role as system administrator, project administrator, user, or developer, and then, further by association with user, project, subsystem, company, or item with provisions for business-to-business exclusions, limitations on access according to the covert or overt nature of a given project, all with multiple layers of filtration, as needed. Reporting of metrics is built in. There is a provision for proxy access (in which the user may choose to grant one or more other users to view screens and perform actions as though they were the user, during any part of a tracking life cycle - especially useful during tight build schedules and vacations to keep things moving). The system also provides users the ability to have an anomaly link to or notify other systems, including QA Inspection Reports, Safety, GIDEP (Government-Industry Data Exchange Program) Alert, Corrective Actions, and Lessons Learned. The PRS tracking engine was designed as a very extensible and scalable system, able to support additional applications, with future development possibilities already discussed, including Incident Surprise Anomalies (for anomalies occurring during Operations phases of NASA Flight projects), GIDEP and NASA Alerts, and others.

Potter, Don↗
NASA NTRS2009

GFO and JASON Altimeter Engineering Assessment Report. Update: GFO-Acceptance to End of Mission on October 22, 2008, JASON-Acceptance to September 29, 2008

The purpose of this document is to present and document GEOSAT Follow-On (GFO) performance analyses and results. This is the ninth Assessment Report since the initial report and is our final one. This report extends the performance assessment since acceptance on November 29, 2000 to the end of mission (EOM) on October 22, 2008. Since launch, February 10, 1998 to the EOM, we performed a variety of GFO performance studies; 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 the TOPEX altimeter. With the end of the TOPEX mission, we developed methods to report on JASON as it related to GFO. It should be noted the GFO altimeter, after operating for over 7 years, was power cycled off to on and on to off approximately 14 times a day for over 18 months in space with no failure. The GFO altimeter proved to be a remarkable instrument providing stable ocean surface measurements for nearly eight years. This report completes our GFO altimeter performance assessment.

Conger, A. M.↗
NASA NTRS2012

Simulation Tool for Dielectric Barrier Discharge Plasma Actuators at Atmospheric and Sub-Atmospheric Pressures: SBIR Phase I Final Report

This report is the final report of a SBIR Phase I project. It is identical to the final report submitted, after some proprietary information of administrative nature has been removed. The development of a numerical simulation tool for dielectric barrier discharge (DBD) plasma actuator is reported. The objectives of the project were to analyze and predict DBD operation at wide range of ambient gas pressures. It overcomes the limitations of traditional DBD codes which are limited to low-speed applications and have weak prediction capabilities. The software tool allows DBD actuator analysis and prediction for subsonic to hypersonic flow regime. The simulation tool is based on the VORPAL code developed by Tech-X Corporation. VORPAL's capability of modeling DBD plasma actuator at low pressures (0.1 to 10 torr) using kinetic plasma modeling approach, and at moderate to atmospheric pressures (1 to 10 atm) using hydrodynamic plasma modeling approach, were demonstrated. In addition, results of experiments with pulsed+bias DBD configuration that were performed for validation purposes are reported.

Likhanskii, Alexandre↗
NASA NTRS2012

2012 NASA Range Safety Annual Report

This report provides a NASA Range Safety (NRS) overview for current and potential range users. This report contains articles which cover a variety of subject areas, summaries of various NASA Range Safety Program (RSP) activities performed during the past year, links to past reports, and information on several projects that may have a profound impact on the way business will be conducted in the future. Specific topics discussed in the 2012 NASA Range Safety Annual Report include a program overview and 2012 highlights; Range Safety Training; Independent Assessments; Support to Program Operations at all ranges conducting NASA launch/flight operations; a continuing overview of emerging range safety-related technologies; and status reports from all of the NASA Centers that have Range Safety responsibilities.

Dumont, Alan G.↗
NASA NTRS2009

Semantic Theme Analysis of Pilot Incident Reports

Pilots report accidents or incidents during take-off, on flight and landing to airline authorities and Federal aviation authority as well. The description of pilot reports for an incident contains technical terms related to Flight instruments and operations. Normal text mining approaches collect keywords from text documents and relate them among documents that are stored in database. Present approach will extract specific theme analysis of incident reports and semantically relate hierarchy of terms assigning weights of themes. Once the theme extraction has been performed for a given document, a unique key can be assigned to that document to cross linking the documents. Semantic linking will be used to categorize the documents based on specific rules that can help an end-user to analyze certain types of accidents. This presentation outlines the architecture of text mining for pilot incident reports for autonomous categorization of pilot incident reports using semantic theme analysis.

Thirumalainambi, Rajkumar↗
NASA NTRS2016

C2-Related Incidents Reported by UAS Pilots

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. Participants were asked to only report incidents that could be included in a public document. During each focus group session, a note taker produced a de-identified written record of the incident narratives. At the end of the session, participants reviewed each written incident report, and made edits and corrections as necessary. The incidents were later analyzed to identify contributing factors, with a focus on design issues that either hindered or assisted the pilot during the events. A total of 90 incidents were reported. This presentation focuses on incidents that involved the management of the command and control (C2) link. The identified issues include loss of link, interference from undesired transmissions, voice latency, accidental control transfer, and the use of the lost link timer, or lost link OK features.

unmanned aircraft systems↗
NASA NTRS2017

Ecological Study of Lagoons Surrounding the John F. Kennedy Space Center, Brevard County, Florida : Theses and Project Reports - Volume 2

Many of the detailed studies done in connection with Ecological Study of the Lagoons surrounding the John F. Kennedy Space Port were performed as Master's Thesis investigations by various graduate students enrolled at F. I. T. during and subsequent to the report. The scope and purpose of what we came to call "the KSC Baseline Study" caught the imagination and interest of our student body. Many who were not financially or otherwise connected with the project found their inspiration in studies that were directly connected with project, and thus added materially to the totality of the knowledge gained. An example of one such study is the first article included in this Volume, A Master's Thesis study performed by Shen Phillip Chen, who chose the site for his investigation so that his results would correlate with and extend the results of others. In addition to the Master's Theses contained in this Volume, six other graduate studies must be acknowledged here as contributing to this Report, although they have not reached the stage of final publication. Ms. Sandra Fettes has completed a study of the amounts of five trace metals in mangrove leaves from plants at various locations around the Kennedy Space Center. Mr. Bernard Cohenour has isolated and identified a number of oil consuming bacteria endemic in the waters of the Indian Rivers. Mr. Charles Waterhouse has analyzed historic data of tidal gauges in the lagoonal area and correlated it with wind field records. Mr. Renkert Meyer has measured the vertical and horizontal currents of the lagoons and is attempting an interpretation of them in terms of the wind field as a driving force. Mr. Richard Campbell has measured the rate of nitrogen fixation in both the water columns and the sediments under them in the lagoons. Mr. Craig Weiderhold has measured thl3 annual variations in the populations of benthic invertebrates in the lagoons. An integral part of the F. I. T. curriculum is a requirement that each undergraduate student perform an independent study during his Senior year and submit his results in the form and format of a professional scientific report. While none of these senior Project Reports have been included in this Volume because of space limitations, many of them aided significantly in the overall study. Typical of these were: light and dark bottle studies of the blue-green algae respiration; writing and executing computer studies comparing the water chemistry data from various sites; detection and identification of nitrogen fixation bacteria in the Indian River; measurement of dissolved oils and greases in the river, photographically recording the benthic life-forms found in the river bottom; measuring the vertical structure of drift and slope currents in too lagoons; and measurement of water level variations along the long axis of a lagoon as a function of wind stress. These articles are published as a part of this Final Report in an effort to make available for the record as much of the basic data as possible. The few articles published on the Indian River have in general not contained much detailed data, so that comparisons of current status to conditions of the past are difficult or impossible. A major effort of both the Oceanographic and Ecological communities for the past decade has been the retrieval and storage of basic data in order to permit determinations of trends or changes in baseline conditions. It is believed that the information compiled here will be of great value in any future investigations.

Source record↗
NASA NTRS2017

Description of the TCERT Vetting Reports for Data Release 25

The Q1Q17 DR25 TCERT Vetting Reports are a collection of plots and diagnostics used by the Threshold Crossing Event Review Team (TCERT) to evaluate threshold crossing events (TCEs). While designation of Kepler Objects of Interest (KOIs) and classification of them as Planet Candidates (PCs) or False Positives (FPs) is completely automated via a robotic vetting procedure (the Robovetter) for the Q1Q17 DR25 planet catalog, as described in Thompson et al. (2017), these reports help to visualize the metrics used by the Robovetter and evaluate those robotic decisions for individual objects. For each Q1Q17 DR25 TCE, these reports include the following products: (a) the DV one-page summary, (b) selected pertinent diagnostics and plots from the full DV report, and (c) additional plots and diagnostics not included in the full DV report, including an alternate means of data detrending.

Kepler Objects of Interest↗
NASA NTRS2016

Topic Modeling of NASA Space System Problem Reports: Research in Practice

Problem reports at NASA are similar to bug reports: they capture defects found during test, post-launch operational anomalies, and document the investigation and corrective action of the issue. These artifacts are a rich source of lessons learned for NASA, but are expensive to analyze since problem reports are comprised primarily of natural language text. We apply topic modeling to a corpus of NASA problem reports to extract trends in testing and operational failures. We collected 16,669 problem reports from six NASA space flight missions and applied Latent Dirichlet Allocation topic modeling to the document corpus. We analyze the most popular topics within and across missions, and how popular topics changed over the lifetime of a mission. We find that hardware material and flight software issues are common during the integration and testing phase, while ground station software and equipment issues are more common during the operations phase. We identify a number of challenges in topic modeling for trend analysis: 1) that the process of selecting the topic modeling parameters lacks definitive guidance, 2) defining semantically-meaningful topic labels requires nontrivial effort and domain expertise, 3) topic models derived from the combined corpus of the six missions were biased toward the larger missions, and 4) topics must be semantically distinct as well as cohesive to be useful. Nonetheless,topic modeling can identify problem themes within missions and across mission lifetimes, providing useful feedback to engineers and project managers.

Data Mining↗
NASA NTRS2018

MagicDraw Report Generation for the Resource Prospector Payload

Magic Draw is a tool currently being used by System Engineers to design model-based representations of the Resource Prospector (RP) Payload. Often, reports are needed to display and communicate the information and schematics within the MagicDraw model. Since constant changes are being made to the model, these reports also need to be maintained with each change. Because this is tedious and time consuming, I was assigned to implement MagicDraw Report Wizard Templates using Velocity Template Language (VTL) scripts. These report template scripts pull specific images, data, and elements directly from the MagicDraw model, allowing the user to have a report that is updated with the current state of the model upon its generation.

MagicDraw↗
NASA NTRS2020

Integration Test and Evaluation (IT&E) Flight Test Series 6 Live Virtual Constructive - Distributed Environment (LVC-DE) Test Report

The goals of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) (also UAS-NAS) Project are to reduce the barriers for UAS access and its integration into the NAS. The UAS-NAS project and industry stakeholders conducted a series of flight tests integrating technologies from the Modeling & Simulation (M&S), Human Systems Integration (HSI), and Communication and Control (C2), and Integration, Test & Evaluation (IT&E) research areas. The last of the flight test series, Flight Test Series 6 (FT6) was conducted in late 2019 and focused on evaluating the interaction of the airborne non-cooperative surveillance system and the Detect and Avoid (DAA) technology. The DAA system generated conflict alert and guidance for pilots using a Research Ground Control System (RGCS) to avoid intruder aircraft. The conflict alerting and guidance information was presented on the RGCS’s display using symbology developed by the human factors team. The objective of FT6 was to investigate the interoperability of Low Size, Weight, and Power (Low SWaP) sensors with the DAA alerting, guidance, and display requirements. To support this goal, the distributed test environments (DTE) were developed at Ames Research Center (ARC) and Armstrong Flight Research Center (AFRC) and securely linked over a Virtual Private Network (VPN). These environments took advantage of existing Live Virtual Constructive (LVC) technologies to support research observation at both Centers with the insertion of live UAS and manned intruder aircraft into a simulated NAS environment with Air Traffic Control (ATC) and constructive manned aircraft. The experiment was distributed between AFRC flight operations and research facilities and the Distributed Simulation Research Laboratory (DSRL) and Software Development Laboratory (SDL) in building N243 at ARC. The Air Traffic Controller and pseudo pilots operated from the DSRL and SDL, respectively, using the Multi-Aircraft Control System (MACS). The test subject and researchers operated from the Research Ground Control Station (RGCS) at AFRC using the Vigilant Spirit Control Station (VSCS) and associated DAA software and displays. Flight Operation for the unmanned aircraft (UA) and manned intruder traffic was conducted at AFRC. Virtual traffic was managed by ARC. Voice distribution was accomplished using a combination of disparate communication systems at ARC and AFRC. The purpose of this document is to record the development, design, and execution of activities in support of the FT6 efforts from the perspective of the ARC IT&E team. Furthermore, the Armstrong IT&E team has published a thorough FT6 Test Report, with emphasis on flight test support, facilities and vehicle development; this report complements the Armstrong report. Analysis of collected FT6 data will be conducted and reported by the M&S and HSI teams and will be published in separate reports.

UAS-NAS↗
NASA NTRS2020

SCA Test Report: H4RG-21224 WFIRST

This report summarizes the measured performance for the Sensor Chip Assembly (SCA), which is identified in Table 1. The SCA architecture is a substrate-removed HgCdTe detector with an area of 4096x4096 pixels (with a reference pixel area of four pixels deep around all four sides, available to substitute corresponding image pixels) and a pixel pitch of 10 μm.This SCA has been tested at the Goddard Space Flight Center (GSFC/NASA) Detector Characterization Laboratory (DCL). Teledyne (the vendor) classifies its detectors into different grades based on testing performed at its facility. The classification of this SCA and the tested dates are included in Table 1 below.The tests performed on this array are derived from the document WFIRST-PROC-09220_WFIRST-SCA-ATP_-.docx. A summary of the test parameters, requirements, and test results is presented in Table 2. The details of each test are subsequently described in the report. In the Summary (Table 2), SCA results are reported at an operating temperature of 95K, and 1.0 V bias voltage. In the detailed section of each test, the results for 95 K and 0.5V bias voltage is also reported. The data for the result reported in this document was acquired in pixel reset mode. For all cases, the frame time used is 2.830 seconds. Reference pixel correction was applied to every raw frame.

Laddawan Miko↗