Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “DOCUMENTATION”

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 451 records · Page 25

WFF TOPEX Software Documentation Overview, May 1999

This document provides an overview'of software development activities and the resulting products and procedures developed by the TOPEX Software Development Team (SWDT) at Wallops Flight Facility, in support of the WFF TOPEX Engineering Assessment and Verification efforts.

Brooks, Ronald L.↗

A Metadata Element Set for Project Documentation

Abstract NASA Goddard Space Flight Center is a large engineering enterprise with many projects. We describe our efforts to develop standard metadata sets across project documentation which we term the "Goddard Core". We also address broader issues for project management metadata.

Hodge, Gail↗

Software Manages Documentation in a Large Test Facility

The 3MCS computer program assists and instrumentation engineer in performing the 3 essential functions of design, documentation, and configuration management of measurement and control systems in a large test facility. Services provided by 3MCS are acceptance of input from multiple engineers and technicians working at multiple locations;standardization of drawings;automated cross-referencing; identification of errors;listing of components and resources; downloading of test settings; and provision of information to customers.

Gurneck, Joseph M.↗

Documentation and Validation of the Goddard Earth Observing System (GEOS) Data Assimilation System, Version 4

This document describes the structure and validation of a frozen version of the Goddard Earth Observing System Data Assimilation System (GEOS DAS): GEOS-4.0.3. Significant features of GEOS-4 include: version 3 of the Community Climate Model (CCM3) with the addition of a finite volume dynamical core; version two of the Community Land Model (CLM2); the Physical-space Statistical Analysis System (PSAS); and an interactive retrieval system (iRET) for assimilating TOVS radiance data. Upon completion of the GEOS-4 validation in December 2003, GEOS-4 became operational on 15 January 2004. Products from GEOS-4 have been used in supporting field campaigns and for reprocessing several years of data for CERES.

Suarez, Max J.↗

NASA Space Mechanisms Handbook: Lessons Learned Documented

The need to improve space mechanism reliability is underscored by a long history of flight failures and anomalies caused by malfunctioning mechanisms on spacecraft and launch vehicles. Some examples of these failures are listed in a table. Because much experience has been gained over the years, many specialized design practices have evolved and many unsatisfactory design approaches have been identified.NASA and the NASA Lewis Research Center conducted a Lessons Learned Study (refs. 1 and 2) and wrote a handbook to document what has been learned in the past. The primary goals of the handbook were to identify desirable and undesirable design practices for space mechanisms and to reduce the number of failures caused by the repetition of past design errors. Another goal was to identify a variety of design approaches for specific applications and to provide the associated considerations and caveats for each approach in an effort to help designers choose the approach most suitable for each application. This technical summary outlines the goals and objectives of the handbook and study as well as the contents of the handbook.

Fusaro, Robert L.↗

Tin Whiskers: A History of Documented Electrical System Failures

This viewgraph presentation reviews the history of tin and other metal whiskers, and the damage they have caused equipment. There are pictures of whiskers on various pieces of electronic equipment, and microscopic views of whiskers. There is also a chart with information on the documented failures associated with metal whiskers. There are also examples of on-orbit failures believed to be caused by whiskers.

Leidecker, Henning↗

AIRS Level 1b Algorithm Theoretical Basis Document

The level 1b Algorithm Theoretical Basis Document (ATBD) describes the theoretical bases of the algorithms used to convert the raw detector output (data numbers) from the Atmospheric Infrared Sounder (AIRS), the Advanced Microwave Sounding Unit (AMSU) and Humidity Sounder Brazil (HSB) to physical radiance units and, in the case of AIRS, perform in-orbit spectral calibrations.

infrared calibration Earth observing system spectr↗

Documentation and Control of Flow Separation on a Low Pressure Turbine Linear Cascade of Pak-B Blades Using Plasma Actuators

This work involved the documentation and control of flow separation that occurs over low pressure turbine (LPT) blades at low Reynolds numbers. A specially constructed linear cascade was utilized to study the flow field over a generic LPT cascade consisting of Pratt & Whitney "Pak-B" shaped blades. Flow visualization, surface pressure measurements, LDV measurements, and hot-wire anemometry were conducted to examine the flow fields with and without separation control. Experimental conditions were chosen to give a range of chord Reynolds numbers (based on axial chord and inlet velocity) from 10,000 to 100,000, and a range of freestream turbulence intensities from u'/U(infinity) = 0.08 to 2.85 percent. The blade pressure distributions were measured and used to identify the region of separation that depends on Reynolds number and the turbulence intensity. Separation control was performed using dielectric barrier discharge (DBD) plasma actuators. Both steady and unsteady actuation were implemented and found to work well. The comparison between the steady and unsteady actuators showed that the unsteady actuators worked better than the steady ones. For the steady actuators, it was found that the separated region is significantly reduced. For the unsteady actuators, where the signal was pulsed, the separation was eliminated. The total pressure losses (a low Reynolds number) was reduced by approximately a factor of two. It was also found that lowest plasma duty cycle (10 percent in this work) was as effective as the highest plasma duty cycle (50 percent in this work). The mechanisms of the steady and unsteady plasma actuators were studied. It was suggested by the experimental results that the mechanism for the steady actuators is turbulence tripping, while the mechanism for the unsteady actuators is to generate a train of spanwise structures that promote mixing.

Corke, Thomas c.↗

The Aviation System Monitoring and Modeling (ASMM) Project: A Documentation of its History and Accomplishments: 1999-2005

The Aviation System Monitoring and Modeling (ASMM) Project was one of the projects within NASA s Aviation Safety Program from 1999 through 2005. The objective of the ASMM Project was to develop the technologies to enable the aviation industry to undertake a proactive approach to the management of its system-wide safety risks. The ASMM Project entailed four interdependent elements: (1) Data Analysis Tools Development - develop tools to convert numerical and textual data into information; (2) Intramural Monitoring - test and evaluate the data analysis tools in operational environments; (3) Extramural Monitoring - gain insight into the aviation system performance by surveying its front-line operators; and (4) Modeling and Simulations - provide reliable predictions of the system-wide hazards, their causal factors, and their operational risks that may result from the introduction of new technologies, new procedures, or new operational concepts. This report is a documentation of the history of this highly successful project and of its many accomplishments and contributions to improved safety of the aviation system.

Statler, Irving C.↗

Step 1: Human System Interface (HSI) Functional Requirements Document (FRD). Version 2

This Functional Requirements Document (FRD) establishes a minimum set of Human System Interface (HSI) functional requirements to achieve the Access 5 Vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS)". Basically, it provides what functions are necessary to fly UAS in the NAS. The framework used to identify the appropriate functions was the "Aviate, Navigate, Communicate, and Avoid Hazards" structure identified in the Access 5 FRD. As a result, fifteen high-level functional requirements were developed. In addition, several of them have been decomposed into low-level functional requirements to provide more detail.

Source record↗

HALE UAS Command and Control Communications: Step 1 - Functional Requirements Document. Version 4.0

The High Altitude Long Endurance (HALE) unmanned aircraft system (UAS) communicates with an off-board pilot-in-command in all flight phases via the C2 data link, making it a critical component for the UA to fly in the NAS safely and routinely. This is a new requirement in current FAA communications planning and monitoring processes. This document provides a set of comprehensive C2 communications functional requirements and performance guidelines to help facilitate the future FAA certification process for civil UAS to operate in the NAS. The objective of the guidelines is to provide the ability to validate the functional requirements and in future be used to develop performance-level requirements.

Source record↗

Documenting AUTOGEN and APGEN Model Files

A computer program called "autogen hypertext map generator" satisfies a need for documenting and assisting in visualization of, and navigation through, model files used in the AUTOGEN and APGEN software mentioned in the two immediately preceding articles. This program parses autogen script files, autogen model files, PERL scripts, and apgen activity-definition files and produces a hypertext map of the files to aid in the navigation of the model. This program also provides a facility for adding notes and descriptions, beyond what is in the source model represented by the hypertext map. Further, this program provides access to a summary of the model through variable, function, sub routine, activity and resource declarations as well as providing full access to the source model and source code. The use of the tool enables easy access to the declarations and the ability to traverse routines and calls while analyzing the model.

Gladden, Roy E.↗

An Extensible "SCHEMA-LESS" Database Framework for Managing High-Throughput Semi-Structured Documents

Object-Relational database management system is an integrated hybrid cooperative approach to combine the best practices of both the relational model utilizing SQL queries and the object-oriented, semantic paradigm for supporting complex data creation. In this paper, a highly scalable, information on demand database framework, called NETMARK, is introduced. NETMARK takes advantages of the Oracle 8i object-relational database using physical addresses data types for very efficient keyword search of records spanning across both context and content. NETMARK was originally developed in early 2000 as a research and development prototype to solve the vast amounts of unstructured and semistructured documents existing within NASA enterprises. Today, NETMARK is a flexible, high-throughput open database framework for managing, storing, and searching unstructured or semi-structured arbitrary hierarchal models, such as XML and HTML.

Maluf, David A.↗

Review of the Constellation Level II Safety, Reliability, and Quality Assurance (SR&QA) Requirements Documents during Participation in the Constellation Level II SR&QA Forum

At the request of the Exploration Systems Mission Directorate (ESMD) and the Constellation Program (CxP) Safety, Reliability; and Quality Assurance (SR&QA) Requirements Director, the NASA Engineering and Safety Center (NESC) participated in the Cx SR&QA Requirements forum. The Requirements Forum was held June 24-26; 2008, at GRC's Plum Brook Facility. The forums purpose was to gather all stakeholders into a focused meeting to help complete the process of refining the CxP to refine its Level II SR&QA requirements or defining project-specific requirements tailoring. Element prime contractors had raised specific questions about the wording and intent of many requirements in areas they felt were driving costs without adding commensurate value. NESC was asked to provide an independent and thorough review of requirements that contractors believed were driving Program costs, by active participation in the forum. This document contains information from the forum.

Cameron, Kenneth D.↗