Search NASA⌕ Search

SEARCH · Search NASA

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

Decal Process Document and Catalog

The Decal Process Document and Catalog, JSC 27260 is the standard flight decal catalog, complete with illustrations and part numbers. As hardware developers identify labels that have common applicability across end items, these labels can be evaluated for "standard decal classification" and entered into the decal catalog for general use. The hardware developer must have a label design that meets current, applicable labeling requirements, and submit to the Decal Design and Production Facility (DDPF) as a standard label candidate. Upon approval, the label will be added to the decal catalog. The Decal Process Document and Catalog provides a selection of decals from which the NASA and NASA contractor customers can easily order. The decals shown in the catalog have been previously produced and have released engineering/fabrication drawings on file in the (DDPF). A released drawing is required before a decal can be produced or placed into the catalog. Some decals included in the catalog have a common applicability and are used in various NASA vehicles/habitats. It is the intent of the DDPF to maintain this catalog as a "living document" to which decals/placards can be added as they are repeatedly used. The advantage of identifYing flight decals in this catalog is that a released drawing is already in place, and the products will be flight certified.

Source record↗
NASA NTRS2011

Content Documents Management

The Content Documents are created and managed under the System Software group with. Launch Control System (LCS) project. The System Software product group is lead by NASA Engineering Control and Data Systems branch (NE~C3) at Kennedy Space Center. The team is working on creating Operating System Images (OSI) for different platforms (i.e. AIX, Linux, Solaris and Windows). Before the OSI can be created, the team must create a Content Document which provides the information of a workstation or server, with the list of all the software that is to be installed on it and also the set where the hardware belongs. This can be for example in the LDS, the ADS or the FR-l. The objective of this project is to create a User Interface Web application that can manage the information of the Content Documents, with all the correct validations and filters for administrator purposes. For this project we used one of the most excellent tools in agile development applications called Ruby on Rails. This tool helps pragmatic programmers develop Web applications with Rails framework and Ruby programming language. It is very amazing to see how a student can learn about OOP features with the Ruby language, manage the user interface with HTML and CSS, create associations and queries with gems, manage databases and run a server with MYSQL, run shell commands with command prompt and create Web frameworks with Rails. All of this in a real world project and in just fifteen weeks!

Muniz, R.↗
NASA NTRS2012

The Algorithm Theoretical Basis Document for Level 1A Processing

The first process of the Geoscience Laser Altimeter System (GLAS) Science Algorithm Software converts the Level 0 data into the Level 1A Data Products. The Level 1A Data Products are the time ordered instrument data converted from counts to engineering units. This document defines the equations that convert the raw instrument data into engineering units. Required scale factors, bias values, and coefficients are defined in this document. Additionally, required quality assurance and browse products are defined in this document.

Jester, Peggy L.↗
NASA NTRS2013

Model Based Document and Report Generation for Systems Engineering

As Model Based Systems Engineering (MBSE) practices gain adoption, various approaches have been developed in order to simplify and automate the process of generating documents from models. Essentially, all of these techniques can be unified around the concept of producing different views of the model according to the needs of the intended audience. In this paper, we will describe a technique developed at JPL of applying SysML Viewpoints and Views to generate documents and reports. An architecture of model-based view and document generation will be presented, and the necessary extensions to SysML with associated rationale will be explained. A survey of examples will highlight a variety of views that can be generated, and will provide some insight into how collaboration and integration is enabled. We will also describe the basic architecture for the enterprise applications that support this approach.

Architecture↗
NASA NTRS2015

ISS Crew Transportation and Services Requirements Document

Under the guidance of processes provided by Crew Transportation Plan (CCT-PLN-1100), this document with its sister documents, Crew Transportation Technical Management Processes (CCT-PLN-1120), Crew Transportation Technical Standards and Design Evaluation Criteria (CCT-STD-1140), and Crew Transportation Operations Standards (CCT-STD-1150), and International Space Station (ISS) to Commercial Orbital Transportation Services Interface Requirements Document (SSP 50808), provides the basis for a National Aeronautics and Space Administration (NASA) certification for services to the ISS for the Commercial Provider. When NASA Crew Transportation System (CTS) certification is achieved for ISS transportation, the Commercial Provider will be eligible to provide services to and from the ISS during the services phase of the NASA Commercial Crew Program (CCP).

Commercial Crew Program↗
NASA NTRS2016

Documenting the NASA Armstrong Flight Research Center Oblate Earth Simulation Equations of Motion and Integration Algorithm

A desire for more complete documentation of the National Aeronautics and Space Administration (NASA) Armstrong Flight Research Center (AFRC), Edwards, California legacy code used in the core simulation has led to this e ort to fully document the oblate Earth six-degree-of-freedom equations of motion and integration algorithm. The authors of this report have taken much of the earlier work of the simulation engineering group and used it as a jumping-o point for this report. The largest addition this report makes is that each element of the equations of motion is traced back to first principles and at no point is the reader forced to take an equation on faith alone. There are no discoveries of previously unknown principles contained in this report; this report is a collection and presentation of textbook principles. The value of this report is that those textbook principles are herein documented in standard nomenclature that matches the form of the computer code DERIVC. Previous handwritten notes are much of the backbone of this work, however, in almost every area, derivations are explicitly shown to assure the reader that the equations which make up the oblate Earth version of the computer routine, DERIVC, are correct.

integrators↗
NASA NTRS2016

NASA Hybrid Wing Aircraft Aeroacoustic Test Documentation Report

This report summarizes results of the Hybrid Wing Body (HWB) N2A-EXTE model aeroacoustic test. The N2A-EXTE model was tested in the NASA Langley 14- by 22-Foot Subsonic Tunnel (14x22 Tunnel) from September 12, 2012 until January 28, 2013 and was designated as test T598. This document contains the following main sections: Section 1 - Introduction, Section 2 - Main Personnel, Section 3 - Test Equipment, Section 4 - Data Acquisition Systems, Section 5 - Instrumentation and Calibration, Section 6 - Test Matrix, Section 7 - Data Processing, and Section 8 - Summary. Due to the amount of material to be documented, this HWB test documentation report does not cover analysis of acquired data, which is to be presented separately by the principal investigators. Also, no attempt was made to include preliminary risk reduction tests (such as Broadband Engine Noise Simulator and Compact Jet Engine Simulator characterization tests, shielding measurement technique studies, and speaker calibration method studies), which were performed in support of this HWB test. Separate reports containing these preliminary tests are referenced where applicable.

Heath, Stephanie L.↗
NASA NTRS2015

Pressurized Payloads Interface Requirements Document: International Space Station Program

This Interface Requirements Document (IRD) is the principle source for interface design requirements for all National Aeronautics and Space Administration (NASA) developed payloads operating in the pressurized volume of the ISS, and for ESA and JAXA payloads operated in the USOS (all non-Russian modules except JEM and Columbus). Payload developers must verify the applicable requirements in this document to ensure the safety of the ISS crew, transport vehicles, on-orbit ISS systems hardware, and neighboring payloads. This document also provides design guidance that ensures the basic operation of the payload and affects the payload's mission success. It is the responsibility of the payload developer (PD) to design in accordance with the design guidance.

Nelson, George C.↗
NASA NTRS2018

External Wireless Communications (EWC) Coverage Expansion Boom Interface Control Document (ICD)

This document defines and controls the physical and functional interfaces between the External Wireless Communications Coverage Expansion (EWCCE) boom and any payload that is planned to be installed on the scarred locations on the boom. The hardware will be referenced as EWCCE boom or simply boom in this document. The boom is comprised of two short boom sections,the upper boom and the lower boom, an Active Worksite Interface (AWIF) and two mounting plates. The boom will be launched soft stowed in a bag and assembled in the Internation Space Station (ISS) via IVA. The assembly will include two sections of the boom and a built-to-print AWIF. The installation of the final assembly to the ISS Truss location is designated as a free-float EVA worksite activity. Once installed on the truss, the interfaces on the Long Boom may be used for attachment of future Orbital Replacement Units (ORUs) to either the Television Camera (TVC) Mounting Slide interface (e.g., an External High Definition Camera [EHDC] or similar ORU) or to future On-orbit Installed Hand-rails (OIHs) installed at the seat track interfaces. Compliance with this Interface Control Document (ICD) will ensure compatibility and successful integration of the hardware.

Vidyasagar, Sagar↗
NASA NTRSDate not supplied

Standardizing Algorithm Documentation For Improved Scientific Data Understanding: The Algorithm Publication Tool Prototype

Algorithm Theoretical Basis Documents (ATBDs) are documents which accompany Earth observation data products generated from algorithms. While ATBDs are essential to scientific reproducibility, these key documents are not standardized and are often difficult to find. In this paper, we present the prototype Algorithm Publication Tool (APT), a cloud-based ATBD authoring and editing tool for NASA’s Earth science data systems. A standardized ATBD information model is also described as well as lessons learned from developing the prototype tool.

Kaylin Bugbee↗
NASA NTRS2021

Methods for Recording and Documenting Ambient Environmental Sound for use in Listening Devices

The potential for implementing Advanced Air Mobility (AAM) vehicles as a viable new transportation system into communities will likely be significantly affected by the psychoacoustic impact of these new noise sources into the existing ambient soundscape. This document addresses a need within the research community for a consistent means of documenting recordings of the ambient soundscape via a metadata framework (Rizzi, et al. 2020). Such recordings can provide a cognitive context for AAM vehicle sounds, as well as a fixed condition or independent variable against which experimental manipulations of vehicle sounds can be evaluated in listening tests. This document also provides recommendations for recording and reproduction techniques of ambient sound. A brief review is made of the use of ambient recordings in prior aircraft noise studies, and of psychoacoustic motivations for its implementation is reviewed from the fields of soundscape, auditory scene analysis, and time-varying partial specific loudness research.

urban air mobility↗
NASA NTRS2022

Global Energy and Water Exchanges Program Surface Radiation Budget Release 4 Integrated Product: Algorithm Theoretical Basis Document

This document represents the Algorithm Theoretical Basis Document (ATBD) describing the NASA Langley Research Center's Surface Radiation budget (SRB) developed in collaboration with the World Research Climate Programme's Global Energy and Water Exchanges Program. The top of atmosphere and surface fluxes span from July 1, 1983 through June 30, 2017. The shortwave or solar wavelengths span the entire record. The thermal infrared or longwave fluxes span globally from January 1, 1988 to December 30, 2009. Before 1988, only the land-only fluxes are available. After 2009 only the ocean fluxes are available. This document describes all the inputs and radiative transfer algorithms used to generate the TOA and surface radiative fluxes. The fluxes include upward and downward, all-sky, clear-sky and pristine sky conditions. Surface net fluxes and cloud radiative effect are computed and presented as part of the analysis. Comparisons to other data products are made to assess the top-of-atmosphere and surface fluxes. Additionally, surface measurements are utilized to validation the surface fluxes. The surface validation analysis shows the the radiative fluxes are improved compared to the previous version. Data set cautions are also presented.

surface radiation budget↗
NASA NTRS2023

Human Landing System (HLS) Program Extravehicular Activity (EVA) Compatibility Interface Requirements Document (IRD)

The purpose of this document is to establish a set of EVA compatibility design requirements for the HLS Program. This document contains the fundamental information required for building hardware compatible with suited EVA flight crewmembers to perform EVAs. Compatibility requirements are located in section 3.0 with a gravity field applicability table provided in APPENDIX G, Human Landing System Program Applicability Matrix. Each HLS Provider will use the EHP-provided matrix in Appendix G to assess applicability to the awarded mission provider on a per-mission basis. Providers will negotiate applicability with EHP, and this will be documented in the appropriate Annex (reference section 2.2)

Christine N Kovich↗
NASA NTRS2023

Creating a Fully-Electronic GFE Work Authorization Document Process for JSC

JSC’s Electronic Document System (EDS) was published in 2013 by SMA to store and process Task Performance Sheets (TPS), Discrepancy Reports (DR), Hardware Movement Documents (EZT), etc. The 2013 transition turned a fully paper process into an electronic routing one with document level electronic approvals but maintained an in-line paper process . - Today, all work and buy-offs continue to be captured on paper, walked between buildings, and is susceptible to approval errors, a rapidly slowing processing time, and led to projects requesting waivers to use alternate WAD systems, damaging JSC’s QMS. - NT Data Systems team collaborated with multiple platform providers, test user groups, and stakeholders, to find a solution for this growing need in a way that exceeds JSC’s current process, is adaptable to future innovation, and within our limited resource constraints

Nicholas Holaday↗
NASA NTRS2024

X-57 Maxwell Vehicle Geometry Document ANLYS-CEPT-002 Rev C

This report documents the two primary coordinate systems used on the X-57 project and their relationship. The coordinate systems (CS) are the Tecnam OEM CS and the X-57 Project CS. All project measurements, unless noted, are taken from the X-57 Project CS. Also, other important locations on the COTS aircraft and the X-57 composite wing are noted and documented. This report also documents the X-57 wing baseline location and other important geometric aspects of the wing. All dimensions are in inches unless otherwise noted.

Edward J Nemie↗
DOE OSTI2025

GridLAB-D Technical Support Document: Residential Equivalent Thermal Parameter Model

GridLAB-D is a power distribution systems simulation and analysis tool developed by Pacific Northwest National Laboratory. Although GridLAB-D and its underlying residential load model has been used in a variety of power systems analyses, comprehensive documentation of the derivation of the residential house model has not been formally published. The purpose of this technical support document is to serve as a comprehensive resource for the thermal dynamics modeling and house definition implemented in GridLAB-D. It covers model derivation, parameter definitions, and implementation steps in the codebase.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2011

Automatic Extraction of JPF Options and Documentation

Documenting existing Java PathFinder (JPF) projects or developing new extensions is a challenging task. JPF provides a platform for creating new extensions and relies on key-value properties for their configuration. Keeping track of all possible options and extension mechanisms in JPF can be difficult. This paper presents jpf-autodoc-options, a tool that automatically extracts JPF projects options and other documentation-related information, which can greatly help both JPF users and developers of JPF extensions.

Static Analysis↗
NASA NTRS1994

Automating Testbed Documentation and Database Access Using World Wide Web (WWW) Tools

A method for providing uniform transparent access to disparate distributed information systems was demonstrated. A prototype testing interface was developed to access documentation and information using publicly available hypermedia tools. The prototype gives testers a uniform, platform-independent user interface to on-line documentation, user manuals, and mission-specific test and operations data. Mosaic was the common user interface, and HTML (Hypertext Markup Language) provided hypertext capability.

documentation↗