Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Guideline 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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS1965

Gemini Program Mission Planning Report

This report defines the Gemini Program objectives and presents guidelines for the individual Gemini missions. It provides general space vehicle configuration data, and descriptions of planned missions. Contingency mission requirements and extravehicular operations to be performed during specific missions are described in the last two sections of the basic document. Data on spacecraft weights and Gemini Launch Vehicle performance capabilities are provided in Appendix A, while Appendix B provides descriptions of onboard experiments to be conducted during Gemini missions.

Source record↗
NASA NTRS1984

A guideline for heavy ion radiation testing for Single Event Upset (SEU)

A guideline for heavy ion radiation testing for single event upset was prepared to assist new experimenters in preparing and directing tests. How to estimate parts vulnerability and select an irradiation facility is described. A broad brush description of JPL equipment is given, certain necessary pre-test procedures are outlined and the roles and testing guidelines for on-site test personnel are indicated. Detailed descriptions of equipment needed to interface with JPL test crew and equipment are not provided, nor does it meet the more generalized and broader requirements of a MIL-STD document. A detailed equipment description is available upon request, and a MIL-STD document is in the early stages of preparation.

Nichols, D. K.↗
NASA NTRSDate not supplied

Making Dataset Quality Information FAIR: Supporting Open-Source Science and Enhancing (Re)Use and Trustworthiness of Scientific Data

- Quality information should be documented and readily shared within and across domains. - Sharing of dataset quality information supports open science and trustworthiness of scientific data. - Dataset quality is more than data quality. - Quality tends to be domain-specific and context-dependent. - Community guidelines provide practical steps towards FAIR dataset quality information.

Ge Peng↗
NASA NTRS2022

Spacecraft Maximum Allowable Concentrations for Airborne Contaminants: Revision B

The enclosed table lists official Spacecraft Maximum Allowable Concentrations (SMACs) for selected airborne contaminants. They are based upon experiments conducted at standard pressure and oxygen environments and may or may not be applicable to altered atmospheres. These are guideline values set by the National Aeronautics and Space Administration (NASA)/Johnson Space Center (JSC) Toxicology Group in cooperation with the National Research Council Committee on Toxicology (NRCCOT) or through publication in the peer-reviewed scientific literature. Based on documented guidance (NRC, 1992; NRC, 2016), NASA has established SMACs for 60 chemical compounds that are particularly relevant to atmospheric contamination of the International Space Station (ISS) and targets of Exploration. Some long‐term limits (1000‐days) have also been established to support manned deep‐space exploration. Summaries of these SMACs are presented in tabular form as part of this publication. Short-term (1- and 24-hour) SMACs apply to off nominal situations, such as accidental releases aboard a spacecraft. These limits permit risk of minor, reversible effects, such as mild mucosal irritation. In contrast, the long term SMACs are set to fully protect healthy crewmembers from adverse effects resulting from continuous exposure to specific air pollutants for up to 1000 days. Because allergic reactions or chemical idiosyncrasy to certain airborne pollutants are very difficult to predict, crewmembers with allergies or unusual sensitivity to trace pollutants may not be afforded complete protection, even when long-term SMACs are not exceeded. Conversely, exceedance of a SMAC does not mean that health impairment is certain (there are many other factors that influence ultimate health outcomes), although it does indicate that the crew may be subject to increased risks that must be closely evaluated. Environmental pollutant control to mitigate exposure will likely be triggered.

SMACs↗
NASA NTRS1986

The NASA Aerospace Battery Safety Handbook

This handbook has been written for the purpose of acquainting those involved with batteries with the information necessary for the safe handling, storage, and disposal of these energy storage devices. Included in the document is a discussion of the cell and battery design considerations and the role of the components within a cell. The cell and battery hazards are related to user- and/or manufacturer-induced causes. The Johnson Space Center (JSC) Payload Safety Guidelines for battery use in Shuttle applications are also provided. The electrochemical systems are divided into zinc anode and lithium anode primaries, secondary cells, and fuel cells. Each system is briefly described, typical applications are given, advantages and disadvantages are tabulated, and most importantly, safety hazards associated with its use are given.

Halpert, Gerald↗
NASA NTRS2000

Intelligent Tutoring Systems for Procedural Task Training of Remote Payload Operations at NASA

Intelligent Tutoring Systems (ITSs) encode and apply the subject matter and teaching expertise of experienced instructors to provide students with individualized instruction automatically. ITSs complement training simulators by providing automated instruction when it is not economical or feasible to dedicate an instructor to each student during training simulations. Despite their proven training effectiveness and favorable operating cost, however, relatively few ITSs are in use. This is largely because it is usually costly and difficult to encode the task knowledge used by the ITS to evaluate the student's actions and assess the student's performance. Procedural tasks are tasks for which there exist procedures, guidelines, and strategies that determine the correct set of steps to be taken within each situation. To lower the cost and difficulty of creating tutoring systems for procedural task training, Stottler Henke Associates, Inc. (SHAI) worked closely with the Operations Training Group at NASA's Marshall Space Flight Center to develop the Task Tutor Toolkit (T (exp 3)), a generic tutoring system shell and scenario authoring tool. The Task Tutor Toolkit employs a case-based reasoning approach where the instructor creates a procedure template that specifies the range of student actions that are "correct" within each scenario. Because each procedure template is specific to a single scenario, the system can employ relatively simple reasoning methods to represent a correct set of actions and assess student performance. This simplicity enables a non-programmer to specify task knowledge quickly and easily by via graphical user interface, using a "demonstrate, generalize, and annotate" paradigm, that recognizes the range of possible valid actions and infers principles understood (or misunderstood) by the student when those actions are carried out. The Task Tutor Toolkit was also designed to be modular and general, so that it can be interfaced with a wide range of training simulators and support a variety of training domains. SHAI and NASA applied the Task Tutor Toolkit to create the Remote Payload Operations Tutor (RPOT). RPOT is a specific tutoring system application which lets scientists who are new to space mission operations learn to monitor and control their experiments aboard the International Space Station according to NASA payload regulations, guidelines, and procedures. The RPOT simulator lets students practice these skills by monitoring the telemetry variable values of a simple, hypothetical experiment, sending commands to the experiment, coordinating with NASA personnel via voice communication loops, and submitting and retrieving information via documents and forms. At the end of each scenario, RPOT displays the principles correctly or incorrectly demonstrated by the student, along with explanations and background information. The effectiveness of RPOT and the Task Tutor Toolkit are currently under evaluation at NASA.

Ong, James↗
DOE OSTI2020

An Integrated Energy Systems Prototype Human-System Interface for a Steam Extraction Loop System to Support Joint Electricity-Hydrogen Flexible Operations

Due to increasing economic competition from renewables and combined-cycle natural gas plants, nuclear power plants are looking toward flexible operations to enhance their cost competitiveness. The Integrated Energy Systems project under the Light Water Reactor Sustainability program of the U.S. Department of Energy focuses on joint electricity-hydrogen flexible operations. Joint electricity-hydrogen flexible operations entail the nuclear power plant diverting thermal energy via main steam to a hydrogen production plant located nearby. The steam serves to enhance the efficiency of the hydrogen production. Furthermore, high temperature electrolysis requires a large amount of electricity, which the plant can also provide. The plant provides steam and electricity to the hydrogen plant throughout the day, but during peak demand hours the nuclear power plant returns to solely providing electricity to meet the high demand. Through this flexible concept of operations, the plant can optimize the thermal energy it produces without having to maneuver the power of the plant. This report documents the human factors process to design and develop a prototype human-system interface for the steam extraction loop that serves as the conduit between the nuclear power plant and the adjacent hydrogen plant. The design process followed the human factors guidelines set by NUREG-0711, Human Factors Engineering Program Review Model (O’Hara, Higgins, & Fleger, 2012), and expanded upon by the Guideline for Operational Nuclear Usability and Knowledge Elicitation (GONUKE; Boring, Ulrich, Joe, & Lew, 2015; Boring, Lew, & Ulrich, 2016). The design process entailed operator interviews to determine the concept of operations for the steam extraction loop, a review and adaptation of digital interface design concepts developed by the team in prior projects, an iterative design process, and reviews conducted by both operators and human factors experts. Several versions of the prototype human-system interface were developed. Operators were interviewed to determine what design features they found useful and would like to see in the interface. The design underwent a review by human factors experts against NUREG-0700, Human Interface Design Review Guidelines (U.S. Nuclear Regulatory Commission, 2019), to ensure compliance with the latest human factors standards for digital interfaces in nuclear applications. The design was then prototyped as a functional windows-based application integrated with the Generic Pressurized Water Reactor simulator modified to include the steam extraction loop. The simulation is supported by the Human Systems Simulation Laboratory at Idaho National Laboratory, which supports operator-in-the-loop testing. This is an ongoing project and the next phase of the project entails performing an operator-in-the-loop usability study to evaluate the interface and examine the proposed concept of operations to extraction steam from the nuclear power plant for delivery to the coupled hydrogen production plant.

99 GENERAL AND MISCELLANEOUS↗
NASA NTRS2006

Constellation Operations: Lessons Learned For Future Exploration

The Earth science community has long advocated placing numerous instruments in space to study the Earth and its environment. Space agencies from many countries have responded to this call with a wide range of orbiting satellites. Scientists also envisioned placing some satellites in constellations, to enable diverse remote sensing instruments to observe the same part of the Earth (or its atmosphere) at about the same time, thereby increasing the opportunities for coincident science observations. The Earth Science Afternoon Constellation is answering this call, but there have been unique challenges on the way to its deployment. Currently, the Afternoon Constellation is to comprise six satellites. Three are currently on orbit: NASA's Earth Observing System (EOS)-Aqua (2002) and EOS-Aura (2004), and CNES's Polarization & Anisotropy of Reflectances for Atmospheric Sciences coupled with Observations from a Lidar (PARASOL) (2004). Two more satellites, the Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observation (CALIPSO) and Cloudsat, are to be jointly launched in late 2005, followed by the Orbiting Carbon Observatory (OCO) in 2008. The Afternoon Constellation is unlike most satellite constellations in that: 1) It is not a homogenous mix of identical satellites; rather it comprises several satellites with complementary observational capabilities; 2) The satellites are not spaced around the Earth to provide instantaneous, global coverage (as for a communications satellite constellation); rather they orbit in close proximity so observations occur at about the same time over approximately the same region; and 3) Lastly, the satellites are not managed and controlled by one organization; rather the list of organizations is diverse: CNES in France, NASA Centers at Goddard, Langley, and the Jet Propulsion Laboratory, and the US Air Force facility in New Mexico. The PARASOL launch and early orbit (L&EO) phase proved to be a learning experience for constellation members (including Constellation management). Prior to launch, all members signed an operations coordination document that spelled out basic requirements for keeping the constellation safe and resolving non-nominal events. Once PARASOL reached orbit and the mission teams gained experience using the newly-developed constellation monitoring tools, it became clear that some of the guidelines in the signed agreements had to be adjusted. This paper presents the L&EO lessons learned and how they were used to prepare for the next phase - the period following the CloudSat/CALIPSO launch.

Kelly, Angelita C.↗
DOE OSTI2026

Toward a standardization of cryostructure and cryogenic soil structure terminology for the field description of permafrost‐affected soils

This paper establishes standardized terminology and field documentation protocols for cryostructures and cryogenic soil structures in permafrost‐affected soils and provides brief guidance on descriptions of ground ice morphology and ice volume estimates. We consolidate permafrost terminology from Russian and North American literature, clarify long‐standing ambiguities, and provide explicit guidelines that align with US Department of Agriculture‐Natural Resources Conservation Service soil description standards. Our scheme makes critical distinctions between cryostructure, the distribution of ice within soil, and cryogenic soil structure, the morphological structure of soil resulting from ice formation. The scheme organizes cryostructures into three main categories: non‐segregated ice, visible segregated ice, and ice matrices. We introduce standardized codes and parameters for field descriptions of ice and soil that enable machine‐readable data collection compatible with existing soil information systems. This standardization will significantly enhance the integration of field observations into landscape‐scale assessments of permafrost stability, infrastructure vulnerability, and ecosystem response to permafrost thaw, addressing an urgent need for quantitative data to inform modeling and decision‐making in rapidly changing Arctic and subarctic environments.

Andersen, Megan L. [University of Minnesota, Saint↗
NASA NTRS2014

Turbulence Modeling Verification and Validation

Computational fluid dynamics (CFD) software that solves the Reynolds-averaged Navier-Stokes (RANS) equations has been in routine use for more than a quarter of a century. It is currently employed not only for basic research in fluid dynamics, but also for the analysis and design processes in many industries worldwide, including aerospace, automotive, power generation, chemical manufacturing, polymer processing, and petroleum exploration. A key feature of RANS CFD is the turbulence model. Because the RANS equations are unclosed, a model is necessary to describe the effects of the turbulence on the mean flow, through the Reynolds stress terms. The turbulence model is one of the largest sources of uncertainty in RANS CFD, and most models are known to be flawed in one way or another. Alternative methods such as direct numerical simulations (DNS) and large eddy simulations (LES) rely less on modeling and hence include more physics than RANS. In DNS all turbulent scales are resolved, and in LES the large scales are resolved and the effects of the smallest turbulence scales are modeled. However, both DNS and LES are too expensive for most routine industrial usage on today's computers. Hybrid RANS-LES, which blends RANS near walls with LES away from walls, helps to moderate the cost while still retaining some of the scale-resolving capability of LES, but for some applications it can still be too expensive. Even considering its associated uncertainties, RANS turbulence modeling has proved to be very useful for a wide variety of applications. For example, in the aerospace field, many RANS models are considered to be reliable for computing attached flows. However, existing turbulence models are known to be inaccurate for many flows involving separation. Research has been ongoing for decades in an attempt to improve turbulence models for separated and other nonequilibrium flows. When developing or improving turbulence models, both verification and validation are important steps in the process. Verification insures that the CFD code is solving the equations as intended (no errors in the implementation). This is typically done either through the method of manufactured solutions (MMS) or through careful step-by-step comparisons with other verified codes. After the verification step is concluded, validation is performed to document the ability of the turbulence model to represent different types of flow physics. Validation can involve a large number of test case comparisons with experiments, theory, or DNS. Organized workshops have proved to be valuable resources for the turbulence modeling community in its pursuit of turbulence modeling verification and validation. Workshop contributors using different CFD codes run the same cases, often according to strict guidelines, and compare results. Through these comparisons, it is often possible to (1) identify codes that have likely implementation errors, and (2) gain insight into the capabilities and shortcomings of different turbulence models to predict the flow physics associated with particular types of flows. These are valuable lessons because they help bring consistency to CFD codes by encouraging the correction of faulty programming and facilitating the adoption of better models. They also sometimes point to specific areas needed for improvement in the models. In this paper, several recent workshops are summarized primarily from the point of view of turbulence modeling verification and validation. Furthermore, the NASA Langley Turbulence Modeling Resource website is described. The purpose of this site is to provide a central location where RANS turbulence models are documented, and test cases, grids, and data are provided. The goal of this paper is to provide an abbreviated survey of turbulence modeling verification and validation efforts, summarize some of the outcomes, and give some ideas for future endeavors in this area.

Rumsey, Christopher L.↗
NASA NTRS1996

Contamination control engineering design guidelines for the aerospace community

Thermal control surfaces, solar arrays, and optical devices may be adversely affected by a small quantity of molecular and/or particulate contamination. What is rarely discussed is how one: (1) quantifies the level of contamination that must be maintained in order for the system to function properly, and (2) enforces contamination control to ensure compliance with requirements. This document is designed to address these specific issues and is intended to serve as a handbook on contamination control for the reader, illustrating process and methodology while providing direction to more detailed references when needed. The effects of molecular contamination on reflecting and transmitting surfaces are examined and quantified in accordance with MIL STD 1246C. The generation, transportation, and deposition of molecular contamination is reviewed and specific examples are worked to illustrate the process a design engineer can use to estimate end of life cleanliness levels required by solar arrays, thermal control surfaces, and optical surfaces. A similar process is used to describe the effect of particulate contamination as related to percent area coverage (PAC) and bi-directional reflectance distribution function (BRDF). Relationships between PAC and surface cleanliness, which include the effects of submicron sized particles, are developed and BRDF is related to specific sensor design parameters such as Point Source Transmittance (PST). The pros and cons of various methods of preventing, monitoring, and cleaning surfaces are examined and discussed.

Tribble, A. C.↗
NASA NTRS1978

Manufacturing process applications team (MATeam)

Activities of the manufacturing applications team (MATeam) in effecting widespread transfer of NASA technology to aid in the solution of manufacturing problems in the industrial sector are described. During the program's first year of operation, 450 companies, industry associations, and government agencies were contacted, 150 manufacturing problems were documented, and 20 potential technology transfers were identified. Although none of the technology transfers has been commercialized and put in use, several are in the applications engineering phase, and others are in the early stages of implementation. The technology transfer process is described and guidelines used for the preparation of problems statements are included.

Bangs, E. R.↗
NASA NTRS1979

Implementation Procedure for STS Payloads, System Safety Requirements

Guidelines and instructions for the implementation of the SP&R system safety requirements applicable to STS payloads are provided. The initial contact meeting with the payload organization and the subsequent safety reviews necessary to comply with the system safety requirements of the SP&R document are described. Waiver instructions are included for the cases in which a safety requirement cannot be met.

Source record↗
NASA NTRS2014

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗
NASA NTRS1997

HARV ANSER Flight Test Data Retrieval and Processing Procedures

Under the NASA High-Alpha Technology Program the High Alpha Research Vehicle (HARV) was used to conduct flight tests of advanced control effectors, advanced control laws, and high-alpha design guidelines for future super-maneuverable fighters. The High-Alpha Research Vehicle is a pre-production F/A-18 airplane modified with a multi-axis thrust-vectoring system for augmented pitch and yaw control power and Actuated Nose Strakes for Enhanced Rolling (ANSER) to augment body-axis yaw control power. Flight testing at the Dryden Flight Research Center (DFRC) began in July 1995 and continued until May 1996. Flight data will be utilized to evaluate control law performance and aircraft dynamics, determine aircraft control and stability derivatives using parameter identification techniques, and validate design guidelines. To accomplish these purposes, essential flight data parameters were retrieved from the DFRC data system and stored on the Dynamics and Control Branch (DCB) computer complex at Langley. This report describes the multi-step task used to retrieve and process this data and documents the results of these tasks. Documentation includes software listings, flight information, maneuver information, time intervals for which data were retrieved, lists of data parameters and definitions, and example data plots.

Yeager, Jessie C.↗
NASA NTRS2013

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere was heightened from Airports to the communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning and configuration of network devices i.e. routers and IDSsIPSs. In addition I will be completing security assessments on software and hardware, vulnerability assessments and reporting, conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, policies and procedures.

computer information security↗
DOE OSTI2020

ESS-DIVE reporting format for leaf-level gas exchange data and metadata

Here we present documentation of the ESS-DIVE reporting format for leaf-level gas exchange data and metadata. This reporting format provides guidance to data contributors on how to store data to maximize their discoverability, facilitate their efficient reuse, and add value to individual datasets. For data users, the reporting format will better allow data repositories to optimize data search and extraction, and more readily integrate similar data into harmonized synthesis products. The reporting format specifies data table variable naming and unit conventions, as well as metadata characterizing experimental conditions and protocols. For common data types that were the focus of this initial version of the reporting format, i.e., survey measurements, dark respiration, carbon dioxide and light response curves, and parameters derived from those measurements, we took a further step of defining required additional data that would maximize the potential reuse of those data types. To aid data contributors and the development of data ingest tools by data repositories we provided a translation table comparing the outputs of common gas exchange instruments. The reporting format presented here is intended to form a foundation for future development that will incorporate additional data types and variables as gas exchange systems and measurement approaches advance in the future. The reporting format documentation is maintained and updated on the ESS-DIVE Community Space GitHub. This data package is the first published version of this reporting format, and comprises a zip file of the complete content of https://github.com/ess-dive-community/essdive-leaf-gas-exchange v1.0. The zip contains the reporting format description, guidelines, variable tables and instructions in GitHub markdown language (*.md) and 2 metadata templates as spreadsheets with drop down options (*.xlsx files, also function in GoogleSheets).

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1965

NASA agenda D mission capabilities and restraints catalog, volume 1

The purpose of this document is to provide a single source of information regarding Agena D mission capabilities and restraints which affect spacecraft design. Utilized as a handbook during conceptual design and program planning, this catalog is intended to supplement the designer's knowledge of the Agena D and specify guidelines that enable him to design a spacecraft configuration which is: - Compatible with the booster system - Designed to realize maximum capabilities of the existing launch vehicle and associated equipment

Lockheed Missiles and Space Company↗