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 181 records · Page 10

NASA Planetary Protection Handbook

This handbook provides guidance to mission providers and Planetary Protection (PP) practitioners on implementing PP measures for both robotic and crewed space missions. This handbook represents major updates to PP practices since a previously drafted handbook from 2010. In 2017, NASA reorganized the Office of Planetary Protection (OPP) from the Science Mission Directorate (SMD) to a Technical Authority (TA) within the Office of Safety and Mission Assurance (OSMA). With this organizational change came a complete overhaul of NASA’s PP policy and technical standards. This handbook reflects the latest NASA PP policy updates in NPR 8715.24, Planetary Protection Provisions for Robotic Extraterrestrial Missions and technical requirements of NASA-STD-8719.27, Implementing Planetary Protection Requirements for Space Flight. This handbook is a companion document to the NPR and technical standard and provides guidance, best practices, background information, and advice for practitioners to consider when implementing PP on NASA missions and NASA-partnered missions.

Nick Benardini↗

The Way to the Future Has Already Started: ICAO Aeronautical Telecommunication Network (ATN) Using Internet Protocol Suite (IPS) Standards and Protocol Evolution Update

Millions of people are able to exchange information over phones, computers, tablets and an array of new interconnected devices such as sensors, cameras, home appliances and others are increasingly becoming networked. At the core of this sizeable interconnection is a set of underlying protocols that enable millions of devices to seamlessly talk to each other. Aviation, as many other industries have, utilizes the internet protocol for ground-to-ground network communications and efforts are underway to bring it to the cockpit.In 2015, the International Civil Aviation Organization (ICAO) published the second edition of Document 9896 (Doc 9896) titled: Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. This manual adopted the Internet protocol version 6 (IPv6) for Internet layer interoperability. Document 9896 defined data communications protocols and services to be used for implementing aeronautical telecommunication network (ATN) using the Internet protocol suite (IPS). The document provided technical specifications that addressed security, network and transport protocols, described applications, supported by ATN/IPS and provided communications guidance. The international aviation community working under the guidance of ICAO initiated work on updates to Doc 9896. Under the ICAO Communication Panel, Working Group Internetworking (WG-I) got this challenging task. Key areas of work for WG-I are related to ATN/IPS Security and ANT/IPS Mobility. Two sub-groups have been assembled to work on these elements. The ICAO anticipates the release of updated Doc 9896 in 2020. Additional ATN/IPS standardization efforts include Radio Technical Commission for Aeronautics Special Committee 223 (RTCA SC-223) IPS profile development, Airlines Electronic Engineering Committee (AEEC) A658 Roadmap of IPS future activities and European Organization for Civil Aviation Equipment (EUROCAE) WG-108 development of guidance documentation.This paper describes ICAO WG-I approach to update key areas of the document in closed coordination with AEEC, RTCA and EUROCAE committees supporting the development of ATN/IPS. Additionally, the paper will explore WG-I mobility solutions under investigation, security developments, IPv6 addressing challenges and other proposed updates. Finally, as new operational expectations such as Free Route and Remote Piloted Aircraft System integration are currently pushing the boundaries set by old operational concepts, the paper identifies the emerging new challenges that will drive the ATN/IPS development beyond 2020. They are related to future voice utilization, System Wide Information Management and Remotely Piloted Aircraft System deployment. IPS systems are seen as the only way forward.

Apaza, Rafael↗

Basis for Dose and Reactor Safety Design Criteria for Army Regulation AR 50–7 and DA Pamphlet

This report describes the basis used to develop the radiological dose acceptance and design criteria contained in the draft updates to Army Regulation 50–7 (AR 50–7) Army Reactor Program and its accompanying draft Department of the Army (DA) Pamphlet (PAM), Army Reactor Program Procedures. These criteria will apply to Army nuclear reactors that fall under AR 50–7 and its accompanying DA PAM and ensure alignment with the overall objectives of the Army Reactor Program. The development basis for the radiological dose and design criteria supports a modern, technology-neutral, risk-informed, and performance-based approach to Army regulation of reactors and the demonstration of “adequate protection of the public.” To establish these criteria that support the Army’s unique operational requirements, multiple well-known and well-established standards and their supporting documentation were reviewed to ensure consistency with existing regulatory safety levels, including guidance from U.S. and international sources. These include the U.S. Nuclear Regulatory Commission’s (NRC’s) regulations and policy, the Canadian Nuclear Safety Commission’s (CNSC’s) regulatory documents, the International Atomic Energy Agency’s (IAEA’s) safety standards, as well as industry input that is tailored specifically to advanced microreactors. This report walks through the key definitions and associated references used for these criteria, which are outlined in Section 2.0. Based on these definitions, the dose acceptance criteria were established for various receptors for routine reactor operations (Section 3.2), design basis accidents (Section 3.3), and beyond design basis accidents (Section 3.4). Comparisons of multiple national and international dose limits are provided in these sections. Lastly, Section 4.0 outlines the reactor safety design criteria contained in the draft DA PAM and their associated bases.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

NASA Schedule Management Handbook

The purpose of schedule management is to provide the framework for time-phasing, resource planning, coordination, and communicating the necessary tasks within a work effort. The intent is to improve schedule management by providing recommended concepts, processes, and techniques used within the Agency and private industry. The intended function of this handbook is two-fold: first, to provide guidance for meeting the scheduling requirements contained in NPR 7120.5, NASA Space Flight Program and Project Management Requirements, NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Requirements, NPR 7120.8, NASA Research and Technology Program and Project Management Requirements, and NPD 1000.5, Policy for NASA Acquisition. The second function is to describe the schedule management approach and the recommended best practices for carrying out this project control function. With regards to the above project management requirements documents, it should be noted that those space flight projects previously established and approved under the guidance of prior versions of NPR 7120.5 will continue to comply with those requirements until project completion has been achieved. This handbook will be updated as needed, to enhance efficient and effective schedule management across the Agency. It is acknowledged that most, if not all, external organizations participating in NASA programs/projects will have their own internal schedule management documents. Issues that arise from conflicting schedule guidance will be resolved on a case by case basis as contracts and partnering relationships are established. It is also acknowledged and understood that all projects are not the same and may require different levels of schedule visibility, scrutiny and control. Project type, value, and complexity are factors that typically dictate which schedule management practices should be employed.

Source record↗

Extravehicular Activity and Human Surface Mobility Program (EHP): Integrated Concept of Operations (ConOps), Revision B

The EHP Integrated ConOps detailed in this document are intended to provide the operational context to inform the development of the xEVA System, LTV, and PR projects. This document describes a bounding set of Design Reference Missions (DRM) to provide scope for interpretation and implementation guidance of the controlled requirements in EHP-10012, Extravehicular Activity and Human Surface Mobility Program (EHP) System Requirements Document.

Extravehicular Activity↗

Human Performance Considerations for Remotely Piloted Aircraft Systems (RPAS)

Successful integration of Remotely Piloted Aircraft Systems (RPAS) into civil airspace will not only require solutions to technical challenges, but will also require that the design and operation of RPAS take into account human limitations and capabilities. Human factors can affect overall system performance whenever the system relies on people to interact with another element of the system. Four types of broad interactions can be described. These are (1) interactions between people and hardware, such as controls and displays; (2) human use of procedures and documentation; (3) impact of the task environment, including lighting, noise and monotony; and lastly, (4) interactions between operational personnel, including communication and coordination. In addition to the human factors that have been identified for conventional aviation, RPAS operations introduce a set of unique human challenges. The purpose of document is to raise human factors issues for consideration by workgroups of the ICAO RPAS panel as they work to develop guidance material and additions to ICAO annexes. It is anticipated that the content of this document will be revised and updated as the work of the panel progresses.

ICAO↗

Human Factors Guidelines for Remotely Piloted Aircraft System (RPAS) Remote Pilot Stations (RPS): Guidelines - Version 1.1

This document contains a list of human factors guidelines for remote pilot stations (RPS) arranged within an organizing structure. The guidelines are intended for the remote pilot stations (RPSs) of remotely piloted aircraft (RPA) that are capable of operating beyond visual line-of-sight in all airspace classes of the United States National Airspace System (NAS). Numerous human factors guidelines and standards for technological systems have been published by standards agencies and regulatory authorities. In compiling this document, the intent was not to reproduce or re-state existing human factors material. Instead, this document focuses on the unique issues of civilian RPAS, and contains guidelines specific to this sector. As a result, it should be seen as a supplement to existing aviation human factors standards and guidance material. Two constraints were used to focus the scope of this document. First, the assumptions contained in the FAA (2013a) UAS roadmap were used to define the responsibilities that will be assigned to the pilot of a RPAS operating beyond visual line-of-sight in the NAS. This in turn, helped to define the tasks that the remote pilot must perform via the RPS, and thereby the required features and characteristics of the RPS. Second, the points of difference between RPAS and conventional aviation were used to further focus the guidelines on the considerations that make piloting a RPA significantly different to piloting a conventional aircraft. Five broad categories of guidelines are identified. These are (1) performance-based descriptions of pilot tasks that must be accomplished via the RPS, (2) information content of displays, (3) descriptions of control inputs, (4) properties of the interface, and (5) high-level design considerations. Some of the guidelines in this document have been adapted from existing RPAS human factors material from several sources, including RTCA publications and Standardization Agreements (STANAGs) published by the North Atlantic Treaty Organization (NATO).

unmanned↗

Final Technical Report (FTR) - DE-EE0009084: Prefabricated Construction: Guidance, Technical Assistance, and Virtual Inspections

This final technical report summarizes research, case studies, and resources developed from 2020–2025 on prefabricated construction and remote virtual inspections. It documents key findings on benefits, challenges, and best practices, highlights examples from multiple states, and provides guidance to support wider adoption of these innovations in the construction sector.

99 GENERAL AND MISCELLANEOUS↗

Certification of Safety-Critical Software Under DO-178C and DO-278A

The RTCA has recently released DO-178C and DO-278A as new certification guidance for the production of airborne and ground-based air traffic management software, respectively. Additionally, RTCA special committee SC-205 has also produced, at the same time, five other companion documents. These documents are RTCA DO-248C, DO-330, DO-331, DO- 332, and DO-333. These supplements address frequently asked questions about software certification, provide guidance on tool qualification requirements, and illustrate the modifications recommended to DO-178C when using model-based software design, object oriented programming, and formal methods. The objective of this paper is to first explain the relationship of DO-178C to the former DO-178B in order to give those familiar with DO- 178B an indication of what has been changed and what has not been changed. With this background, the relationship of DO-178C and DO-278 to the new DO-278A document for ground-based software development is shown. Last, an overview of the new guidance contained in the tool qualification document and the three new supplements to DO-178C and DO-278A is presented. For those unfamiliar with DO-178B, this paper serves to provide an entry point to this new certification guidance for airborne and ground-based CNS/ATM software certification.

Jacklin, Stephen A.↗

OFT ascent/descent ancillary data requirements document

Requirements are presented for the ascent/descent (A/D) navigation and attitude-dependent ancillary data products to be generated for the space shuttle orbiter in support of orbital flight test requirements, MPAD guidance and navigation performance assessment, and the mission evaluation team. It was intended that this document serve as the sole requirements control instrument between MPB/MPAD and the A/D ancillary data users. The requirements are primarily functional in nature, but some detail level requirements are also included.

Bond, A. C., Jr.↗

Design criteria for payload workstation accommodations

Anticipated shuttle sortie payload man-system design criteria needs are investigated. Man-system interactions for the scientific disciplines are listed and the extent is assessed to which documented Skylab experience is expected to provide system design guidance for each of the identified interactions. Where the analysis revealed that the reduced Skylab data does not answer the anticipated needs candidate criteria, based on unreduced Skylab data, available prior research, original analysis, or related requirements derived from previous space programs, are provided.

Watters, H. H.↗

Documentation of GEMASS entry to touchdown simulation

The entry-to-touchdown space shuttle orbiter simulation capability incorporated into the GEMASS subprogram 33 (3-DOF) is documented. A digital autopilot interfaces between GEMASS and the guidance. Vehicle attitude is determined by use of the ability of GEMASS to integrate differential equations in addition to the equations of motion. Vehicle aerodynamic characteristics are obtained from an aerodynamic data tape and control surface deflections required to trim the vehicle, and trimmed aerodynamic coefficients are determined internally. Several indicators to allow evaluation of subsystem performance are included; as is the ability of the user to activate any of several error dispersion sources. The performance of the simulation compares well with more sophisticated simulations.

Waibel, R. H.↗

GCS programmer's manual

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

Lowman, Douglas S.↗

Portable Wireless LAN Device and Two-Way Radio Threat Assessment for Aircraft VHF Communication Radio Band

This document summarizes the safety analysis performed on a Flight Guidance System (FGS) requirements model. In particular, the safety properties desired of the FGS model are identified and the presence of the safety properties in the model is formally verified. Chapter 1 provides an introduction to the entire project, while Chapter 2 gives a brief overview of the problem domain, the nature of accidents, model based development, and the four-variable model. Chapter 3 outlines the approach. Chapter 4 presents the results of the traditional safety analysis techniques and illustrates how the hazardous conditions associated with the system trace into specific safety properties. Chapter 5 presents the results of the formal methods analysis technique model checking that was used to verify the presence of the safety properties in the requirements model. Finally, Chapter 6 summarizes the main conclusions of the study, first and foremost that model checking is a very effective verification technique to use on discrete models with reasonable state spaces. Additional supporting details are provided in the appendices.

Nguyen, Truong X.↗

Comparison of A-SMGCS Requirements with Observed Performance of an Integrated Airport CNS System

The International Civil Aviation Organization (ICAO) has recently drafted a reference document describing the operational requirements for Advanced Surface Movement Guidance and Control Systems (A-SMGCS). During the summer of 1997, NASA, the FAA, industry, and academia partners demonstrated a holistic system approach that has the potential to meet many of the proposed A-SMGCS requirements. An assessment of the field tested system and data resulting from the field testing is presented to determine its compliance with A-SMGCS requirements. In those areas where compliance was not demonstrated, a recommendation is presented suggesting further research or a modification of the system architecture.

Young, Steven D.↗

Rendezvous Guidance Technology

The literature on rendezvous guidance technology is reviewed and a bibliography of about 160 documents is presented. The importance of the proper selection of the ascent trajectory and of the orbit for a manned space station or an orbiting launch complex is emphasized. The way the launch delay problem affects the selection of the ascent trajectory and the target orbit is discussed. A specific ascent trajectory and an orbit for a manned space station or an orbiting launch complex is recommended on the premise that launch delay problems will continue to outweigh most of the other orbit selection criteria. A new method for determining the velocity corrections required for mid-course guidance is proposed . The proposed methods consist of an "exact-numerical" solution of the relative equations of motion in the "Shell-coordinate system." The proposed "exact-numerical" method extends the applicability of the mid- course equations to a much greater range than that of the currently available linear methods .

Trajectory↗

Developing IVHM Requirements for Aerospace Systems

The term Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable sustainable and safe operation of components and subsystems within aerospace platforms. However, very little guidance exists for the systems engineering aspects of design with IVHM in mind. It is probably because of this that designers have to use knowledge picked up exclusively by experience rather than by established process. This motivated a group of leading IVHM practitioners within the aerospace industry under the aegis of SAE's HM-1 technical committee to author a document that hopes to give working engineers and program managers clear guidance on all the elements of IVHM that they need to consider before designing a system. This proposed recommended practice (ARP6883 [1]) will describe all the steps of requirements generation and management as it applies to IVHM systems, and demonstrate these with a "real-world" example related to designing a landing gear system. The team hopes that this paper and presentation will help start a dialog with the larger aerospace community and that the feedback can be used to improve the ARP and subsequently the practice of IVHM from a systems engineering point-of-view.

IVHM↗

The GMAO Hybrid Ensemble-Variational Atmospheric Data Assimilation System: Version 2.0

This document describes the implementation and usage of the Goddard Earth Observing System (GEOS) Hybrid Ensemble-Variational Atmospheric Data Assimilation System (Hybrid EVADAS). Its aim is to provide comprehensive guidance to users of GEOS ADAS interested in experimenting with its hybrid functionalities. The document is also aimed at providing a short summary of the state-of-science in this release of the hybrid system. As explained here, the ensemble data assimilation system (EnADAS) mechanism added to GEOS ADAS to enable hybrid data assimilation applications has been introduced to the pre-existing machinery of GEOS in the most non-intrusive possible way. Only very minor changes have been made to the original scripts controlling GEOS ADAS with the objective of facilitating its usage by both researchers and the GMAO's near-real-time Forward Processing applications. In a hybrid scenario two data assimilation systems run concurrently in a two-way feedback mode such that: the ensemble provides background ensemble perturbations required by the ADAS deterministic (typically high resolution) hybrid analysis; and the deterministic ADAS provides analysis information for recentering of the EnADAS analyses and information necessary to ensure that observation bias correction procedures are consistent between both the deterministic ADAS and the EnADAS. The nonintrusive approach to introducing hybrid capability to GEOS ADAS means, in particular, that previously existing features continue to be available. Thus, not only is this upgraded version of GEOS ADAS capable of supporting new applications such as Hybrid 3D-Var, 3D-EnVar, 4D-EnVar and Hybrid 4D-EnVar, it remains possible to use GEOS ADAS in its traditional 3D-Var mode which has been used in both MERRA and MERRA-2. Furthermore, as described in this document, GEOS ADAS also supports a configuration for exercising a purely ensemble-based assimilation strategy which can be fully decoupled from its variational component. We should point out that Release 1.0 of this document was made available to GMAO in mid-2013, when we introduced Hybrid 3D-Var capability to GEOS ADAS. This initial version of the documentation included a considerably different state-of-science introductory section but many of the same detailed description of the mechanisms of GEOS EnADAS. We are glad to report that a few of the desirable Future Works listed in Release 1.0 have now been added to the present version of GEOS EnADAS. These include the ability to exercise an Ensemble Prediction System that uses the ensemble analyses of GEOS EnADAS and (a very early, but functional version of) a tool to support Ensemble Forecast Sensitivity and Observation Impact applications.

Todling, Ricardo↗