SEARCH · Search NASA

Results for “Guidebook”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

All sources NASA NTRS DOE OSTI

DOE OSTI2024

Distributed Wind Guidebook: Agricultural Producers and Rural Small Business Owners

Distributed wind energy technologies generate clean, carbon-free power close to the point of consumption (i.e., close to people and their energy needs). Distributed wind energy can help individuals, farms, businesses, and communities meet their unique goals, such as reducing impacts on climate change, decreasing electricity bills, boosting energy independence or autonomy from the electric grid, and enhancing grid reliability and resilience. This guidebook is designed to support you in (1) deciding if distributed wind energy is right for you, (2) installing a proven wind turbine technology by working with a reputable installer, and (3) setting up your project for success through its lifetime. The information in this guidebook is tailored to rural small businesses and agricultural producers who are interested in exploring distributed wind energy to meet their electricity, resilience, financial, and environmental goals. You will find gray boxes with key topics, definitions, and considerations throughout the guidebook. The report has been adapted from the Distributed Wind Guidebook, which offers a comprehensive view on core aspects of deploying distributed wind energy technologies. In comparison, this edition of the guidebook is designed to offer a more succinct and tailored guidebook for rural small businesses and agricultural producers. For additional detail on any topic presented within this edition, readers are advised to reference the original version of the Distributed Wind Guidebook.

17 WIND ENERGY↗

NASA NTRS1995

Formal Methods Specification and Analysis Guidebook for the Verification of Software and Computer Systems: A Practitioner's Companion - Volume 2

This guidebook, the second of a two-volume series, is intended to facilitate the transfer of formal methods to the avionics and aerospace community. The 1st volume concentrates on administrative and planning issues [NASA-95a], and the second volume focuses on the technical issues involved in applying formal methods to avionics and aerospace software systems. Hereafter, the term "guidebook" refers exclusively to the second volume of the series. The title of this second volume, A Practitioner's Companion, conveys its intent. The guidebook is written primarily for the nonexpert and requires little or no prior experience with formal methods techniques and tools. However, it does attempt to distill some of the more subtle ingredients in the productive application of formal methods. To the extent that it succeeds, those conversant with formal methods will also nd the guidebook useful. The discussion is illustrated through the development of a realistic example, relevant fragments of which appear in each chapter. The guidebook focuses primarily on the use of formal methods for analysis of requirements and high-level design, the stages at which formal methods have been most productively applied. Although much of the discussion applies to low-level design and implementation, the guidebook does not discuss issues involved in the later life cycle application of formal methods.

Source record↗

NASA NTRS2015

Developing a Fault Management Guidebook for Nasa's Deep Space Robotic Missions

NASA designs and builds systems that achieve incredibly ambitious goals, as evidenced by the Curiosity rover traversing on Mars, the highly complex International Space Station orbiting our Earth, and the compelling plans for capturing, retrieving and redirecting an asteroid into a lunar orbit to create a nearby a target to be investigated by astronauts. In order to accomplish these feats, the missions must be imbued with sufficient knowledge and capability not only to realize the goals, but also to identify and respond to off-nominal conditions. Fault Management (FM) is the discipline of establishing how a system will respond to preserve its ability to function even in the presence of faults. In 2012, NASA released a draft FM Handbook in an attempt to coalesce the field by establishing a unified terminology and a common process for designing FM mechanisms. However, FM approaches are very diverse across NASA, especially between the different mission types such as Earth orbiters, launch vehicles, deep space robotic vehicles and human spaceflight missions, and the authors were challenged to capture and represent all of these views. The authors recognized that a necessary precursor step is for each sub-community to codify its FM policies, practices and approaches in individual, focused guidebooks. Then, the sub-communities can look across NASA to better understand the different ways off-nominal conditions are addressed, and to seek commonality or at least an understanding of the multitude of FM approaches. This paper describes the development of the "Deep Space Robotic Fault Management Guidebook," which is intended to be the first of NASA's FM guidebooks. Its purpose is to be a field-guide for FM practitioners working on deep space robotic missions, as well as a planning tool for project managers. Publication of this Deep Space Robotic FM Guidebook is expected in early 2015. The guidebook will be posted on NASA's Engineering Network on the FM Community of Practice website so that it will be available to all NASA projects. Future plans for subsequent guidebooks for the other NASA sub-communities are proposed.

Fesq, Lorraine M.↗

DOE OSTI2024

Hydropower Black Start: A Guidebook for Retrofitting Grid Dependent Hydropower

Not all United States (US) hydropower plants were designed to provide black start, but they are increasingly needed to uphold resilience in the evolving electric grid. This guidance is designed to help understand the minimal retrofits required for grid dependent hydropower (GDH) plants behind the point of interconnection (POI). For distribution connected hydropower plants or those with dedicated cranking paths, such upgrades can be sufficient for the plant to provide black start. For others, more coordination with the transmission system operator will be needed. This guidebook answers a number of questions relevant to retrofitting hydropower plants with black start capabilities. For example, the guidebook answers: • How flexible do the wicket gate controls need to be? • Who needs to do hydro governor model validation, why, and how? • How robust and flexible do the excitation and AVR controls need to be? • What protection settings need to be adjusted? • What relay(s) will need to be bypassed or overridden and at what risk? • What is the electrical energy demand of the station load or auxiliary power systems? • What should the strategy to energize transformer(s) along cranking path to address inrush currents be? • How should the critical load restoration be sequenced? In addition to outlining the specifications that hydropower plants need to meet for each component to be able to perform black start, this guidebook provides a set of case studies for specific upgrades needed at actual plants. Between the case studies of plants that have already performed black start retrofits and the examples of how this guidebook can be applied to scope future retrofits, five key themes have been identified for retrofit needs. 1. Protection needs “black start” mode: hydropower plants that are not designed with black start capabilities will have protections that prevent them from interconnecting to a “dead bus.” These protections will need to be overridden in every retrofit case and a separate black start mode should be established so that operators can safely switch between black start and grid connected modes, minimizing the risk to the plant. 2. Wicket gates need modern controls: digital governors accelerate the parameter tuning process and gate position sensors improve controllability, so plants with mechanical governors should be upgraded. Furthermore, a black start and islanding mode should be established for controls to maximize plant performance. 3. Robust excitation support: the DC system or excitation generator needs to be reliable enough to form and sustain the rotor electromagnetic field. These systems are typically undersized in plants that were not designed for black start, so they will need to be upgraded. 4. Turbine-governor model validation and operator training: validation of a standard hydro governor model is needed to characterize the dynamic response (i.e., inertial and primary frequency response) of the GDH. This is required for control development and old hydropower plants often have outdated or incorrect models. Operator training is also typically required to ensure the hardware retrofits are utilized correctly during the black start process. 5. Transformer and cranking path energization: any upgradation and control adjustment in front of the POI will depend upon the existing interconnection. Coordination with the transmission or distribution operator may be required.

13 HYDRO ENERGY↗

NASA NTRS1991

Spacesuit guidebook

This guidebook is designed to supplement the Spacesuit wall chart (WAL-114) published by the Education Affairs Division, January 1990. The wall chart depicts Astronaut Bruce McCandless on his historic first untethered spacewalk using the manned maneuvering unit. He flew on Shuttle mission 41-B, and ventured 100 meters for the Shuttle's cargo bay and returned safely. This guidebook explains in depth the elements depicted on the wall chart in see-through and cut-away perspectives. Together the wall chart and guidebook show as well as explain the inside workings of the spacesuit and its various components. Forty separate elements are identified with an accompanying numerical legend. Those elements are further explained in this guidebook along with their functions and how they work in relation to other elements. Additional chapters discuss essential components of the spacesuit such as the primary life support system and the manned maneuvering unit, and the method for donning the spacesuit.

Source record↗

NASA NTRS1990

Software Quality Assurance Audits Guidebooks

The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes that are used in software development. The Software Assurance Guidebook, NASA-GB-A201, issued in September, 1989, provides an overall picture of the NASA concepts and practices in software assurance. Second level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the second level Software Quality Assurance Audits Guidebook that describes software quality assurance audits in a way that is compatible with practices at NASA Centers.

Source record↗

NASA NTRS1993

Software Formal Inspections Guidebook

The Software Formal Inspections Guidebook is designed to support the inspection process of software developed by and for NASA. This document provides information on how to implement a recommended and proven method for conducting formal inspections of NASA software. This Guidebook is a companion document to NASA Standard 2202-93, Software Formal Inspections Standard, approved April 1993, which provides the rules, procedures, and specific requirements for conducting software formal inspections. Application of the Formal Inspections Standard is optional to NASA program or project management. In cases where program or project management decide to use the formal inspections method, this Guidebook provides additional information on how to establish and implement the process. The goal of the formal inspections process as documented in the above-mentioned Standard and this Guidebook is to provide a framework and model for an inspection process that will enable the detection and elimination of defects as early as possible in the software life cycle. An ancillary aspect of the formal inspection process incorporates the collection and analysis of inspection data to effect continual improvement in the inspection process and the quality of the software subjected to the process.

Source record↗

NASA NTRS1995

Software Configuration Management Guidebook

The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes which are used in software development. The Software Assurance Guidebook, SMAP-GB-A201, issued in September, 1989, provides an overall picture of the concepts and practices of NASA in software assurance. Lower level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the Software Configuration Management Guidebook which describes software configuration management in a way that is compatible with practices in industry and at NASA Centers. Software configuration management is a key software development process, and is essential for doing software assurance.

Source record↗

NASA NTRS1993

Software Engineering Guidebook

The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.

Connell, John↗

NASA NTRS1996

Software Engineering Program: Software Process Improvement Guidebook

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Source record↗

NASA NTRS1995

Formal Methods Specification and Verification Guidebook for Software and Computer Systems: Planning and Technology Insertion - Volume 1

The Formal Methods Specification and Verification Guidebook for Software and Computer Systems describes a set of techniques called Formal Methods (FM), and outlines their use in the specification and verification of computer systems and software. Development of increasingly complex systems has created a need for improved specification and verification techniques. NASA's Safety and Mission Quality Office has supported the investigation of techniques such as FM, which are now an accepted method for enhancing the quality of aerospace applications. The guidebook provides information for managers and practitioners who are interested in integrating FM into an existing systems development process. Information includes technical and administrative considerations that must be addressed when establishing the use of FM on a specific project. The guidebook is intended to aid decision makers in the successful application of FM to the development of high-quality systems at reasonable cost. This is the first volume of a planned two-volume set. The current volume focuses on administrative and planning considerations for the successful application of FM.

Source record↗

NASA NTRS1995

Software Measurement Guidebook

This Software Measurement Guidebook is based on the extensive experience of several organizations that have each developed and applied significant measurement programs over a period of at least 10 years. The lessons derived from those experiences reflect not only successes but also failures. By applying those lessons, an organization can minimize, or at least reduce, the time, effort, and frustration of introducing a software measurement program. The Software Measurement Guidebook is aimed at helping organizations to begin or improve a measurement program. It does not provide guidance for the extensive application of specific measures (such as how to estimate software cost or analyze software complexity) other than by providing examples to clarify points. It does contain advice for establishing and using an effective software measurement program and for understanding some of the key lessons that other organizations have learned. Some of that advice will appear counterintuitive, but it is all based on actual experience. Although all of the information presented in this guidebook is derived from specific experiences of mature measurement programs, the reader must keep in mind that the characteristics of every organization are unique. Some degree of measurement is critical for all software development and maintenance organizations, and most of the key rules captured in this report will be generally applicable. Nevertheless, each organization must strive to understand its own environment so that the measurement program can be tailored to suit its characteristics and needs.

Source record↗

NASA NTRS2023

NASA Passive Thermal Control Engineering Guidebook

The NASA Passive Thermal Control Engineering Guidebook provides recommendations, including best practices and lessons learned, related to the passive thermal control engineering discipline. Topics include analysis (including documentation and review), thermal hardware (design/selection, vendors, and integration), testing, and flight operations. The passive thermal discipline includes thermal control and thermal protection systems. The passive thermal control discipline, which is addressed in this Guidebook, is broad and covers internal and external systems, component passive thermal analysis, vehicle on-orbit attitude timeline analysis, integrated thermal analysis, various thermal control apparatus (heaters and controls, coatings, blankets and insulations, isolators, geometric design for view factors, materials emissivity/absorptivity properties), passive cooling of avionics, purge, vent, and drain for vehicle cavities and compartments, thermal model development and correlation, thermal cycle and thermal-vacuum testing. Topics related to thermal protection systems (TPS) are not within the scope of this document. The Guidebook provides a consolidated reference for early career as well as experienced engineers embarking on a new task. Leveraging the experience of the group minimizes the learning curve that exists at the start of new projects, reduces the risk of repeating mistakes, and improves the organization’s ability to deliver high-quality products efficiently. The intent of this document is to provide guidance based on collective experience, and is not intended impose constraints on project work. Best practices can vary substantially and it is important to apply judgment wisely based on careful consideration of the specific design and requirements. Implementation of the methods described will vary from project to project and should be applied in conjunction with the judgment of the thermal engineers performing and reviewing the work. The recommendations in this document are not intended to replace program, project, branch, Center, or NASA requirements and/or policies.

thermal↗

NASA NTRS2023

NASA Passive Thermal Control Engineering Guidebook

thermal↗

DOE OSTI2025

Development of the Table of Initial Isolation and Protective Action Distances for the 2024 Emergency Response Guidebook

The transportation of hazardous materials creates numerous opportunities for the release of toxic substances into the environment, whether caused by traffic accidents, train derailments, equipment failures, or human error. Such releases can pose acute hazards to the general public and to emergency response personnel who are the first to arrive at the scene. To help first responders determine whether a shipment is potentially hazardous and decide what actions should be taken if a toxic spill does occur, the Emergency Response Guidebook (ERG) is published by the U.S. Department of Transportation (DOT), Transport Canada, and the Secretariat of Transport and Communications of Mexico; with contributions from Centro de Informaciòn Quìmica para Emergencias of Argentina. The most recent version is the 2024 edition of the ERG (ERG 2024), titled 2024 Emergency Response Guidebook (ERG2024). The ERG provides essential information about firefighting, spill response, and potential public health effects. For chemicals that are toxic by inhalation (TIH) and chemicals that produce TIH gases upon reaction with water (TIH by water reactivity or TIHWR), the ERG provides initial isolation distances (IIDs) and protective action distances (PADs). The IID defines the radius of the zone around the spill that should be accessed solely by people who are directly involved in emergency response. The PAD is the distance downwind of the source of the release within which persons should be either evacuated or sheltered in place, depending on the severity of the incident and the nature of the population (e.g., density, age, health).

63 RADIATION, THERMAL, AND OTHER ENVIRON. POLLUTAN↗

DOE OSTI2026

Commercial and Industrial Energy Procurement in Nigeria: A Consumer's Guidebook

Across Africa, countries have incorporated a variety of new energy sources into their energy mix to account for increasing demand. In Nigeria, electricity consumption per capita has grown nearly 50% in the past 20 years. To address rising demand for energy in Nigeria, the country has passed several recent policies and regulations aimed at increasing energy generation across the country, improving the country's transmission infrastructure, and ensuring that electricity reliably reaches end users, including commercial and industrial (C&I) customers. This guidebook is designed for C&I customers in Nigeria to use in the consideration of procuring such onsite, captive energy systems to supplement their energy needs. Each section of this guidebook touches on a step of the procurement process and details the relevant stakeholders, processes, and data needed to make decisions during that step.

14 SOLAR ENERGY↗

NASA NTRS1994

Software measurement guidebook

This software Measurement Guidebook presents information on the purpose and importance of measurement. It discusses the specific procedures and activities of a measurement program and the roles of the people involved. The guidebook also clarifies the roles that measurement can and must play in the goal of continual, sustained improvement for all software production and maintenance efforts.

Bassman, Mitchell J.↗

NASA NTRS1996

Software Program: Software Management Guidebook

The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project.

Source record↗