Search NASA⌕ Search

SEARCH · Search NASA

Results for “guidance document”

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 145 records · Page 8

Computer simulation and performance assessment of the packet-data service of the Aeronautical Mobile Satellite Service (AMSS)

The ICAO Aeronautical Mobile Communications Panel (AMCP) completed the drafting of the Aeronautical Mobile Satellite Service (AMSS) Standards and Recommended Practices (SARP's) and the associated Guidance Material and submitted these documents to ICAO Air Navigation Commission (ANC) for ratification in May 1994. This effort, encompassed an extensive, multi-national SARP's validation. As part of this activity, the US Federal Aviation Administration (FAA) sponsored an effort to validate the SARP's via computer simulation. This paper provides a description of this effort. Specifically, it describes: (1) the approach selected for the creation of a high-fidelity AMSS computer model; (2) the test traffic generation scenarios; and (3) the resultant AMSS performance assessment. More recently, the AMSS computer model was also used to provide AMSS performance statistics in support of the RTCA standardization activities. This paper describes this effort as well.

Ferzali, Wassim↗

DC-8 scanning lidar characterization of aircraft contrails and cirrus clouds

A Subsonic Assessment (SASS) element of the overall Atmospheric Effects of Aviation Project (AEAP) was initiated by NASA to assess the atmospheric impact of subsonic aircraft. SRI was awarded a project to develop and test a scanning backscatter lidar for installation on the NASA DC-8 (year 1), participate in the Subsonic Aircraft: Contrail and Cloud Effects Special Study (SUCCESS) field program (year 2), and conduct a comprehensive analysis of field data (year 3). A scanning mirror pod attached to the DC-8 aircraft provides for scanning lidar observations ahead of the DC-8 and fixed-angle upward or downward observations. The lidar system installed within the DC-8 transmits 275 MJ at 1.06 gm wavelength or about 130 mJ at 1.06 and 0.53 gm simultaneously. Range-resolved aerosol backscatter is displayed in real time in terms of cloud/contrail spatial distributions. The objectives of the project are to map contrail/cloud vertical distributions ahead of DC-8; provide DC-8 guidance into enhanced scattering layers; document DC-8 flight path intersection of contrail and cloud geometries (in-situ measurement positions relative to cloud/contrail shape and an extension of in-situ measurements into the vertical -- integrated contrail/cloud properties); analyze contrail/cloud radiative properties with LIRAD (combined lidar and radiometry) technique; evaluate mean particle sizes of aircraft emissions from two-wavelength observations; study contrail/cloud interactions, diffusion, and mass decay/growth; and make observations in the near-field of aircraft engine emissions. The scanning mirror pod may also provide a scanning capability for other remote sensing instruments.

Nielsen, Norman B.↗

Integrated Demand Management: Concepts and Procedures

This report provides a comprehensive description of the Integrated Demand Management concept. Motivation: NASA’s Integrated Demand Management (IDM) research explores the idea that, under certain conditions, time-based flow management (TBFM) arrival operations can benefit from the coordinated use of a strategic traffic management initiative (TMI) to “precondition” the inbound demand. The research was motivated by the observation that TBFM was usually turned off during convective weather, even in facilities where it was routinely used. Our hypothesis was that strategic adjustments to the inbound traffic so that it provided a better match to the off-nominal changes in capacity observed during these conditions could enable TBFM scheduling to continue to provide effective support for arrival traffic management. Concept: IDM proposes that a TMI (e.g., a Collaborative Trajectory Options Program, or CTOP) be used to adjust the rate and/or geographic distribution across flows of the traffic inbound to a high-demand, TBFM-managed airport before that traffic reaches the TBFM planning horizon. After this strategic preconditioning, TBFM can then tactically fine-tune the demand to deliver a well-managed, orderly feed to the destination airport. Coordinated use of these two flow management capabilities is intended to improve system performance in terms of: • Equity of ground delay assignment, avoiding excessive ground delay for TBFM-scheduled departures, without penalizing longer flights; • Throughput, by distributing traffic to maximize use of available capacity; • Predictability for operators, providing advance notice about the impact on individual flights; • Increased flexibility, supporting operator mitigation strategies such as slot swapping or trajectory options; • Efficiency of flight operations, using ground delay more effectively and reducing airborne delay. The operational description in this document highlights how the IDM concept builds upon already existing tools and procedures, and also indicates where tool enhancements could facilitate conduct of IDM operations. However, enhanced tools are not a requirement for concept introduction. In fact, initial deployment that focused on training procedures and rationale for coordinated use of TFMS and TBFM, without changes to existing tools, might be a simpler way to introduce and to familiarize traffic managers with the idea of preconditioning. The concept and procedures described in this document can hopefully provide useful guidance for introduction of IDM into field operations..

IDM↗

Recommendations on Use of Commercial-Off-The-Shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) Parts for NASA Missions

The NASA Electronic Parts & Packaging Program Manager, requested a NASA Engineering and Safety Center independent assessment to summarize Commercial Crew Program and NASA Centers’ current and best practices, and lessons learned, on use of commercial-off-the-shelf (COTS) for all mission risk classifications, and provide recommendations that could lead to future NASA Electronic Parts and Packaging Program and/or Agency guidance on COTS parts. This document contains the outcome of the assessment.

Commercial-Off-The-Shelf↗

Model-Agnostic Signal Discovery with Machine Learning: Bridging the Gap Between Theory and Practice

Searches for new phenomena in complex scientific data are predominantly model-dependent, optimized for specific hypotheses, and therefore limited in their coverage of the space of possible signals. Recently, new AI-based model-agnostic search strategies, many of which have been pioneered in high-energy physics, have been proposed which provide a complementary paradigm, prioritizing broad exploration over tailored analyses. These techniques offer an opportunity to enhance the overall discovery potential of modern experiments, especially in regimes where theoretical guidance is scarce. In this document, we review the conceptual framework behind the main classes of AI-based model-agnostic strategies. We discuss the potential pitfalls of these methods, and strategies for their validation and interpretation. We aim for this document to serve as a useful reference both for practitioners and for researchers interested in learning more about these model-agnostic search strategies.

Amram, Oz [Fermilab] (ORCID:0000000237653123)↗

System Engineering Curriculum Into

This document is intended to provide useful guidance and information on systems engineering for engineering students. It provides a generic description of Systems Engineering (SE) as it should be applied throughout engineering design, implementation, testing, and operations. This document will increase awareness and consistency across engineering fields and advance the practice of SE.

Kenneth Freeman↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for WBS and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Christopher Lewis Sadler↗

Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Source record↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Planning↗

Independent Orbiter Assessment (IOA): Analysis of the guidance, navigation, and control subsystem

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) is presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The independent analysis results corresponding to the Orbiter Guidance, Navigation, and Control (GNC) Subsystem hardware are documented. The function of the GNC hardware is to respond to guidance, navigation, and control software commands to effect vehicle control and to provide sensor and controller data to GNC software. Some of the GNC hardware for which failure modes analysis was performed includes: hand controllers; Rudder Pedal Transducer Assembly (RPTA); Speed Brake Thrust Controller (SBTC); Inertial Measurement Unit (IMU); Star Tracker (ST); Crew Optical Alignment Site (COAS); Air Data Transducer Assembly (ADTA); Rate Gyro Assemblies; Accelerometer Assembly (AA); Aerosurface Servo Amplifier (ASA); and Ascent Thrust Vector Control (ATVC). The IOA analysis process utilized available GNC hardware drawings, workbooks, specifications, schematics, and systems briefs for defining hardware assemblies, components, and circuits. Each hardware item was evaluated and analyzed for possible failure modes and effects. Criticality was assigned based upon the severity of the effect for each failure mode.

Trahan, W. H.↗

Space Shuttle Guidance, Navigation, and Rendezvous Knowledge Capture Reports

This document is a catalog and readers guide to lessons learned, experience, and technical history reports, as well as compilation volumes prepared by United Space Alliance personnel for the NASA/Johnson Space Center (JSC) Flight Dynamics Division.1 It is intended to make it easier for future generations of engineers to locate knowledge capture documentation from the Shuttle Program. The first chapter covers observations on documentation quality and research challenges encountered during the Space Shuttle and Orion programs. The second chapter covers the knowledge capture approach used to create many of the reports covered in this document. These chapters are intended to provide future flight programs with insight that could be used to formulate knowledge capture and management strategies. The following chapters contain descriptions of each knowledge capture report. The majority of the reports concern the Space Shuttle. Three are included that were written in support of the Orion Program. Most of the reports were written from the years 2001 to 2011. Lessons learned reports concern primarily the shuttle Global Positioning System (GPS) upgrade and the knowledge capture process. Experience reports on navigation and rendezvous provide examples of how challenges were overcome and how best practices were identified and applied. Some reports are of a more technical history nature covering navigation and rendezvous. They provide an overview of mission activities and the evolution of operations concepts and trajectory design. The lessons learned, experience, and history reports would be considered secondary sources by historians and archivists.

John L Goodman↗

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.↗

Repository-Based Software Engineering Program: Working Program Management Plan

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

Source record↗

Reference manual for the Thermal Analyst's Help Desk Expert System

This document provides technical information and programming guidance for the maintenance and future development of the Thermal Analyst's Help Desk. Help Desk is an expert system that operates within the EXSYSTM expert system shell, and is used to determine first approximations of thermal capacity for spacecraft and instruments. The five analyses supported in Help Desk are: (1) surface area required for a radiating surface, (2) equilibrium temperature of a surface, (3) enclosure temperature and heat loads for a defined position in orbit, (4) enclosure temperature and heat loads over a complete orbit and, (5) selection of appropriate surface properties. The two geometries supported by Help Desk are a single flat plate and a rectangular box enclosure. The technical information includes the mathematical approach and analytical derivations used in the analyses such as: radiation heat balance, view factor calculation, and orbit determination with coordinate transformation. The programming guide for developers describes techniques for enhancement of Help Desk. Examples are provided showing the addition of new features, user interface development and enhancement, and external program interfaces.

Ormsby, Rachel A.↗

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.↗

Experimental and Numerical Analysis of Structural Acousticcontrol Interior Noise Reduction

The research results contained in this technical report were performed under the NASA grant entitled "Experimental and Numerical Structural Acoustic Control for Interior Noise Reduction". The report is based essentially on partial progress of the Ph.D. dissertation prepared by Jeffrey S. Bevan under direct guidance of Dr. Chuh Mei. The document presents a finite element formulation and control of sound radiated from cylindrical panels embedded with piezoceramic actuators. The extended MIN6 shallow shell element is fully electrical-structural coupled. A piezoelectric modal actuator participation (PMAP) is defined which indicates the actuator performance to each of the offending modes. Genetic algorithm is also employed to validate the sensor and actuator locations determined by the PMAP criteria. The work was conducted at the Department of Aerospace Engineering, Old Dominion University. Mr. Travis L. Turner, Structural Acoustics Branch, NASA Langley Research Center is the technical monitor.

Mei, Chuh↗

Zero Gravity Research Facility User's Guide

The Zero Gravity Research Facility (ZGF) is operated by the Space Experiments Division of the NASA John H. Glenn Research Center (GRC) for investigators sponsored by the Microgravity Science and Applications Division of NASA Headquarters. This unique facility has been utilized by scientists and engineers for reduced gravity experimentation since 1966. The ZGF has provided fundamental scientific information, has been used as an important test facility in the space flight hardware design, development, and test process, and has also been a valuable source of data in the flight experiment definition process. The purpose of this document is to provide information and guidance to prospective researchers regarding the design, buildup, and testing of microgravity experiments.

Thompson, Dennis M.↗

Airspace Systems Program: Next Generation Air Transportation System Concepts and Technology Development FY2010 Project Plan Version 3.0

This document describes the FY2010 plan for the management and execution of the Next Generation Air Transportation System (NextGen) Concepts and Technology Development (CTD) Project. The document was developed in response to guidance from the Airspace Systems Program (ASP), as approved by the Associate Administrator of the Aeronautics Research Mission Directorate (ARMD), and from guidelines in the Airspace Systems Program Plan. Congress established the multi-agency Joint Planning and Development Office (JPDO) in 2003 to develop a vision for the 2025 Next Generation Air Transportation System (NextGen) and to define the research required to enable it. NASA is one of seven agency partners contributing to the effort. Accordingly, NASA's ARMD realigned the Airspace Systems Program in 2007 to "directly address the fundamental research needs of the Next Generation Air Transportation System...in partnership with the member agencies of the JPDO." The Program subsequently established two new projects to meet this objective: the NextGen-Airspace Project and the NextGen-Airportal Project. Together, the projects will also focus NASA s technical expertise and world-class facilities to address the question of where, when, how and the extent to which automation can be applied to moving aircraft safely and efficiently through the NAS and technologies that address optimal allocation of ground and air technologies necessary for NextGen. Additionally, the roles and responsibilities of humans and automation influence in the NAS will be addressed by both projects. Foundational concept and technology research and development begun under the NextGen-Airspace and NextGen-Airportal projects will continue. There will be no change in NASA Research Announcement (NRA) strategy, nor will there be any change to NASA interfaces with the JPDO, Federal Aviation Administration (FAA), Research Transition Teams (RTTs), or other stakeholders

Kopardekar, Parimal H.↗