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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Lightning Protection for the Orion Space Vehicle

The Orion space vehicle is designed to requirements for both direct attachment and indirect effects of lightning. Both sets of requirements are based on a full threat 200kA strike, in accordance with constraints and guidelines contained in SAE ARP documents applicable to both commercial and military aircraft and space vehicles. This paper describes the requirements as levied against the vehicle, as well as the means whereby the design shows full compliance.

Scully, Robert↗
NASA NTRS1990

GCS support/development system configuration document

The software programming environment used in the development of Guidance and Control Software (GCS) implementations used in a software error studies experiment conducted by the Research Triangle Institute (RTI) and the NASA-Langley is described. The Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines are fulfilled, and requirements for document number 9 in which the hardware, software, and processes used to develop and maintain the software for the GCS project are described. The software programming environment for GCS largely consists of tools that are included in Digital Equipment Corporations software layered product library or are a part of the VAX/VMS baseline system.

Lowman, Douglas S.↗
NASA NTRS1972

Long life assurance study for manned spacecraft long life hardware. Volume 1: Summary of long life assurance guidelines

A long life assurance program for the development of design, process, test, and application guidelines for achieving reliable spacecraft hardware was conducted. The study approach consisted of a review of technical data performed concurrently with a survey of the aerospace industry. The data reviewed included design and operating characteristics, failure histories and solutions, and similar documents. The topics covered by the guidelines are reported. It is concluded that long life hardware is achieved through meticulous attention to many details and no simple set of rules can suffice.

Source record↗
NASA NTRS1981

AgRISTARS: Foreign Commodity production forecasting. Project procedures designation and description document, volume 1

The crop estimation analysis procedures documentation of the AgRISTARS - Foreign Commodity Production Forecasting Project (FCPF) is presented. Specifically it includes the technical/management documentation of the remote sensing data analysis procedures prepared in accordance with the guidelines provided in the FCPF communication/documentation standards manual. Standard documentation sets are given arranged by procedural type and level then by crop types or other technically differentiating categories.

Waggoner, J. T.↗
NASA NTRS2003

New NASA SEE LEO Spacecraft Charging Design Guidelines: How to Survive in LEO Rather Than GEO

It has been almost two solar cycles since the 1984 GEO Guidelines of Purvis, Garrett, Whittlesey, and Stevens were published. In that time, interest in high voltage LEO systems has increased. Correct and conventional wisdom has been that LEO conditions are sufficiently different from GEO that the GEO Guidelines (and other GEO and POLAR documents produced since then) should not be used for LEO spacecraft. Because of significant recent GEO spacecraft failures that have been shown in ground testing to be likely to also occur on LEO spacecraft, the SEE program commissioned the production of the new LEO Spacecraft Charging Design Guidelines. Now available in CD-ROM form, the LEO Guidelines highlight mitigation techniques to prevent spacecraft arcing on LEO solar arrays and other systems. We compare and contrast the mitigation techniques for LEO and GEO in this paper. We also discuss the extensive bibliography included in the LEO Guidelines, so results can be found in their primary sources.

Ferguson, Dale C.↗
NASA NTRS2004

New NASA SEE LEO Spacecraft Charging Design Guidelines: How to Survive in LEO Rather than GEO

It has been almost two solar cycles since the GEO Guidelines of Purvis et al (1984) were published. In that time, interest in high voltage LEO systems has increased. The correct and conventional wisdom has been that LEO conditions are sufficiently different from GEO that the GEO Guidelines (and other GEO and POLAR documents produced since then) should not be used for LEO spacecraft. Because of significant recent GEO spacecraft failures that have been shown in ground testing to be likely to also occur on LEO spacecraft, the SEE program commissioned the production of the new LEO Spacecraft Charging Design Guidelines (hereafter referred to as the LEO Guidelines). Now available in CD-ROM form, the LEO Guidelines highlight mitigation techniques to prevent spacecraft arcing on LEO solar arrays and other systems. We compare and contrast the mitigation techniques for LEO and GEO in this paper. We also discuss the extensive bibliography included in the LEO Guidelines, so results can be found in their primary sources.

Ferguson, Dale C.↗
NASA NTRS2014

Orbital Debris Mitigation

Policies on limiting orbital debris are found throughout the US Government, many foreign space agencies, and as adopted guidelines in the United Nations. The underlying purpose of these policies is to ensure the environment remains safe for the operation of robotic and human spacecraft in near‐ Earth orbit. For this reason, it is important to consider orbital debris mitigation during the design of all space vehicles. Documenting compliance with the debris mitigation guidelines occurs after the vehicle has already been designed and fabricated for many CubeSats, whereas larger satellites are evaluated throughout the design process. This paper will provide a brief explanation of the US Government Orbital Debris Mitigation Standard Practices, a discussion of international guidelines, as well as NASA's process for compliance evaluation. In addition, it will discuss the educational value of considering orbital debris mitigation requirements as a part of student built satellite design.

Kelley, R. L.↗
NASA NTRS1996

System Guidelines for EMC Safety-Critical Circuits: Design, Selection, and Margin Demonstration

Demonstration of safety margins for critical points (circuits) has traditionally been required since it first became a part of systems-level Electromagnetic Compatibility (EMC) requirements of MIL-E-6051C. The goal of this document is to present cost-effective guidelines for ensuring adequate Electromagnetic Effects (EME) safety margins on spacecraft critical circuits. It is for the use of NASA and other government agencies and their contractors to prevent loss of life, loss of spacecraft, or unacceptable degradation. This document provides practical definition and treatment guidance to contain costs within affordable limits.

Lawton, R. M.↗
NASA NTRS1979

Photovoltaic system criteria documents. Volume 4: Review criteria for photovoltaic applications

Guidelines are provided for the organization, preparation and conduct of program reviews for photovoltaic applications. These criteria apply to all photovoltaic applications. They include, but are not limited to, the following: (1) Conceptual design review; (2) Preliminary design review; (3) Critical design review; and (4) Operational readiness review. Contract goal's and objectives are met through program monitoring for cost, schedule, and performance for both managerial and technical elements for all PV applications activities.

Koenig, John C.↗
NASA NTRS1994

Natural orbital environment definition guidelines for use in aerospace vehicle development

This document provides definitions of the natural near-Earth space environment suitable for use in the initial development/design phase of any space vehicle. The natural environment includes the neutral atmosphere, plasma, charged particle radiation, electromagnetic radiation (EMR), meteoroids, orbital debris, magnetic field, physical and thermal constants, and gravitational field. Communications and other unmanned satellites operate in geosynchronous-Earth orbit (GEO); therefore, some data are given for GEO, but emphasis is on altitudes from 200 km to 1000 km (low-Earth orbit (LEO)). This document does not cover the induced environment of other effects resulting from presence of the space vehicle. Manmade factors are included as part of the ambient natural environment; i.e., orbital debris and radio frequency (RF) noise generated on Earth, because they are not caused by the presence of the space vehicle but form part of the ambient environment that the space vehicle experiences.

Anderson, B. Jeffrey↗
NASA NTRS1995

Guidelines for qualifying cleaning and verification materials

This document is intended to provide guidance in identifying technical issues which must be addressed in a comprehensive qualification plan for materials used in cleaning and cleanliness verification processes. Information presented herein is intended to facilitate development of a definitive checklist that should address all pertinent materials issues when down selecting a cleaning/verification media.

Webb, D.↗
NASA NTRS1984

Vacuum stability requirements of polymeric material for spacecraft application

The purpose of this document is to establish outgassing requirements and test guidelines for polymeric materials used in the space thermal/vacuum environment around sensitive optical or thermal control surfaces. The scope of this document covers the control of polymeric materials used near or adjacent to optical or thermal control surfaces that are exposed to the thermal/vacuum environment of space. This document establishes the requirements and defines the test method to evaluate polymeric materials used in the vicinity of these surfaces in space applications.

Craig, J. W.↗
NASA NTRS2021

A Fully Automated Approach to Requirement Extraction from Design Documents

Design documents are intended to outline the goalsof a system or project, which are utilized in the creation ofspecific software requirements. At the NASA Jet PropulsionLaboratory, California Institute of Technology, Functional DesignDescription (FDD) documents describe the scope of theproject and reflect the design and implementation of the system.The specifications in the document are not explicitly writtenas requirements, though these guidelines must be reflected inthe official software requirements. In this work we present afully automatic approach to extracting software requirementsfrom design documents as well as comparing the extractedrequirements to those that exist in the official software requirementdatabase. We do this through (1) sentence extractionfrom the design document, (2) the incorporation of coreferenttext, and (3) aligning the extracted text to the official softwarerequirements. Via natural language processing and informationretrieval techniques, our system results in an automated processthat ensures that the specifications in the design document resultin official software requirements. We find that extraction ofimperatives results in a recall rate of 0.73 and the TF-IDF cosinesimilarity metric is shown to be a useful and successful way tocompare requirements.Though there has been recent work investigating the usefulnessof natural language processing techniques in requirement engineering,this has not been made use of in the aerospace industry.Aerospace requirement engineering is a field particularly ripefor this type of innovation because these techniques can bothautomate some of needlessly manual work and contribute toaerospace safety practices by identifying issues that a humanmay miss. We present the first fully automated approach thatextracts requirements from a design document and comparesthem to a database, and use these findings as encouragementfor future work that makes use of natural language processingtechniques in aerospace requirement engineering.

Briggs, Paul↗
NASA NTRS2006

HSI Guidelines Outline for the Air Vehicle Control Station. Version 2

This document provides guidance to the FAA and manufacturers on how to develop UAS Pilot Vehicle Interfaces to safely and effectively integrate UASs into the NAS. Preliminary guidelines are provided for Aviate, Communicate, Navigate and Avoid Hazard functions. The pilot shall have information and control capability so that pilot-UA interactions are not adverse, unfavorable, nor compromise safety. Unfavorable interactions include anomalous aircraft-pilot coupling (APC) interactions (closed loop), pilot-involved oscillations (categories I, II or III), and non-oscillatory APC events (e.g., divergence). - Human Systems Integration Pilot-Technology Interface Requirements for Command, Control, and Communications (C3)

Source record↗
NASA NTRS1972

The management approach to the NASA space station definition studies at the Manned Spacecraft Center

The overall management approach to the NASA Phase B definition studies for space stations, which were initiated in September 1969 and completed in July 1972, is reviewed with particular emphasis placed on the management approach used by the Manned Spacecraft Center. The internal working organizations of the Manned Spacecraft Center and its prime contractor, North American Rockwell, are delineated along with the interfacing techniques used for the joint Government and industry study. Working interfaces with other NASA centers, industry, and Government agencies are briefly highlighted. The controlling documentation for the study (such as guidelines and constraints, bibliography, and key personnel) is reviewed. The historical background and content of the experiment program prepared for use in this Phase B study are outlined and management concepts that may be considered for future programs are proposed.

Heberlig, J. C.↗
NASA NTRS1981

The role of pilots

The need for detailed specifications is addressed. Candidates for standardization include hardware interfaces, communication protocols, and data exchange services. Atmosphere, Ocean, and Resource pilot programs, utilization of current techniques and technologies in the use and exchange of data and to facilitate access to data are discussed. Pilot objectives aim to: (1) demonstrate the use of advanced technologies, (2) provide a test bed environment for data handling technique evaluation, (3) evolve requirements and capabilities, and (4) document validated methodologies as standards and guidelines for data systems planning use. A user oriented catalog system, data set management, a network communication system, and a user interface are also discussed.

Gary, J. P.↗