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 577 records · Page 32
All sourcesNASA NTRSDOE OSTI
NASA NTRS1999

NASA Ocean Altimeter Pathfinder Project: Data Set Validation - Report 2

The NOAA/NASA Pathfinder program was created by the Earth Observing System (EOS) Program Office to determine how existing satellite-based data sets can be processed and used to study global change. The data sets are designed to be long time-series data processed with stable calibration and community consensus algorithms to better assist the research community. The Ocean Altimeter Pathfinder Project involves the reprocessing of all altimeter observations with a consistent set of improved algorithms, based on the results from TOPEX/POSEIDON (T/P), into easy-to-use data sets for the oceanographic community for climate research. Details are currently presented in two technical reports: Report# 1: Data Processing Handbook Report #2: Data Set Validation This report describes the validation of the data sets against a global network of high quality tide gauge measurements and provides an estimate of the error budget. The first report describes the processing schemes used to produce the geodetic consistent data set comprised of SEASAT, GEOSAT, ERS-1, TOPEX/ POSEIDON, and ERS-2 satellite observations.

Koblinsky, C. J.↗
NASA NTRS2000

Aerospace Safety Advisory Panel Annual Report for 1999

This report covers the activities of the Aerospace Safety Advisory Panel (ASAP) for the calendar year 1999.This was a year of notable achievements and significant frustrations. Both the Space Shuttle and International Space Station (ISS) programs were delayed.The Space Shuttle prudently postponed launches after the occurrence of a wiring short during ascent of the STS-93 mission. The ISS construction schedule slipped as a result of the Space Shuttle delays and problems the Russians experienced in readying the Service Module and its launch vehicle. Each of these setbacks was dealt with in a constructive way. The STS-93 short circuit led to detailed wiring inspections and repairs on all four orbiters as well as analysis of other key subsystems for similar types of hidden damage. The ISS launch delays afforded time for further testing, training, development, and contingency planning. The safety consciousness of the NASA and contractor workforces, from hands-on labor to top management, continues high. Nevertheless, workforce issues remain among the most serious safety concerns of the Panel. Cutbacks and reorganizations over the past several years have resulted in problems related to workforce size, critical skills, and the extent of on-the-job experience. These problems have the potential to impact safety as the Space Shuttle launch rate increases to meet the demands of the ISS and its other customers. As with last year's report, these work- force-related issues were considered of sufficient import to place them first in the material that follows. Some of the same issues of concern for the Space Shuttle and ISS arose in a review of the launch vehicle for the Terra mission that the Panel was asked by NASA to undertake. Other areas the Panel was requested to assess included the readiness of the Inertial Upper Stage for the deployment of the Chandra X-ray Observatory and the possible safety impact of electromagnetic effects on the Space Shuttle. The findings and recommendations in this report do not highlight any major, immediate issues that might compromise the safe pursuit of the various NASA programs. They do, however, cover concerns that the Panel believes should be addressed in the interest of maintaining NASA's excellent safety record.The Panel is pleased to note that remedial efforts for some of the findings raised are underway. Given appropriate funding and cooperative efforts among the Administration, the Congress and the various contractors, the Panel is convinced that safety problems can be avoided or solved resulting in lower risk for NASA's human space and aeronautics programs. Section II of this report contains specific findings and recommendations generated by Panel activities during the calendar year 1999. Section III presents more detailed information in support of these findings and recommendations. A current roster of Panel members, consultants, and staff is included as Appendix A. Appendix B contains NASA's response to the findings and recommendations from the 1998 annual report. It has been augmented this year to include brief explanations of why the Panel classified the NASA response as " open,""continuing," or "closed." Appendix C lists the fact-finding activities of the Panel in 1999.

Blomberg, Richard D.↗
NASA NTRS2000

Assessment of Existing Data and Reports for System Evaluation

This report describes work done as part of the Weather Datalink Research project grant. We describe the work done under Task 1 of this project: the assessment of the suitability of available reports and data for use in evaluation of candidate weather datalink systems, and the development of a performance parameter set for comparative system evaluation. It was found that existing data and reports are inadequate for a complete physical layer characterization, but that these reports provide a good foundation for system comparison. In addition, these reports also contain some information useful for evaluation at higher layers. The performance parameter list compiled can be viewed as near complete-additional investigations, both analytical/simulation and experimental, will likely result in additions and improvements to this list.

Matolak, David W.↗
NASA NTRS2002

National Aeronautics and Space Administration Fiscal Year 2001 Accountability Report

The National Aeronautics and Space Administration (NASA) is an independent Agency established to plan and manage the future of the Nation's civil aeronautics and space program. This Accountability Report covers Federal Fiscal Year (FY) 2001 (October 1, 2000, through September 30, 2001), with discussion of some subsequent events. The Report contains an overview addressing the Agency's critical programs and financial performance and includes highlights of performance organized by goals and objectives of the Enterprises and Crosscutting Processes. The Report also summarizes NASA's stewardship over budget and financial resources, including audited financial statements and footnotes. The financial statements reflect an overall position of offices and activities, including assets and liabilities, as well as results of operations, pursuant to requirements of Federal law (31 U.S.C. 3515(b)). The auditor's opinions on NASA's financial statements, reports on internal controls, and compliance with laws and regulations are included in this report.

Source record↗
NASA NTRS2002

Database Reports Over the Internet

Most of the summer was spent developing software that would permit existing test report forms to be printed over the web on a printer that is supported by Adobe Acrobat Reader. The data is stored in a DBMS (Data Base Management System). The client asks for the information from the database using an HTML (Hyper Text Markup Language) form in a web browser. JavaScript is used with the forms to assist the user and verify the integrity of the entered data. Queries to a database are made in SQL (Sequential Query Language), a widely supported standard for making queries to databases. Java servlets, programs written in the Java programming language running under the control of network server software, interrogate the database and complete a PDF form template kept in a file. The completed report is sent to the browser requesting the report. Some errors are sent to the browser in an HTML web page, others are reported to the server. Access to the databases was restricted since the data are being transported to new DBMS software that will run on new hardware. However, the SQL queries were made to Microsoft Access, a DBMS that is available on most PCs (Personal Computers). Access does support the SQL commands that were used, and a database was created with Access that contained typical data for the report forms.

Dean Lance Smith↗
NASA NTRS2001

National Aeronautics and Space Administration FY 2001 Accountability Report

The National Aeronautics and Space Administration (NASA) is an independent Agency established to plan and manage the future of the Nation's civil aeronautics and space program. This Accountability Report covers Federal Fiscal Year (FY) 2001 (October 1, 2000, through September 30, 2001), with discussion of some subsequent events The Report contains an overview addressing the Agency's critical programs and financial performance and includes highlights of performance organized by goals and objectives of the Enterprises and Crosscutting Processes. The Report also summarizes NASA's stewardship over budget and financial resources, including audited financial statements and footnotes. The financial statements reflect an overall position of offices and activities, including assets and liabilities, as well as results of operations, pursuant to requirements of Federal law (31 U.S.C. 3515(b)). The auditor's opinions on NASA's financial statements, reports on internal controls, and compliance with laws and regulations are included in this Report.

Source record↗
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↗