Search NASA⌕ Search

SEARCH · Search NASA

Results for “best practices”

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 361 records · Page 20
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Radiated Emissions from a Remote-Controlled Airplane-Measured in a Reverberation Chamber

A full-vehicle, subscale all-electric model airplane was tested for radiated emissions, using a reverberation chamber. The mission of the NASA model airplane is to test in-flight airframe damage diagnosis and battery prognosis algorithms, and provide experimental data for other aviation safety research. Subscale model airplanes are economical experimental tools, but assembling their systems from hobbyist and low-cost components may lead to unforseen electromagnetic compatibility problems. This report provides a guide for accommodating the on-board radio systems, so that all model airplane systems may be operated during radiated emission testing. Radiated emission data are provided for on-board systems being operated separately and together, so that potential interferors can be isolated and mitigated. The report concludes with recommendations for EMI/EMC best practices for subscale model airplanes and airships used for research.

Ely, Jay J.↗
NASA NTRS2011

International Space Station (ISS) Risk Reduction Activities

As the assembly of the ISS nears completion, it is worthwhile to step back and review some of the actions pursued by the Program in recent years to reduce risk and enhance the safety and health of ISS crewmembers, visitors, and space flight participants. While the ISS requirements and initial design were intended to provide the best practicable levels of safety, it is always possible to reduce risk -- given the determination and commitment to do so. The following is a summary of some of the steps taken by the ISS Program Manager, by our International Partners, by hardware and software designers, by operational specialists, and by safety personnel to continuously enhance the safety of the ISS. While decades of work went into developing the ISS requirements, there are many things in a Program like the ISS that can only be learned through actual operational experience. These risk reduction activities can be divided into roughly three categories: (1) Areas that were initially noncompliant which have subsequently been brought into compliance or near compliance (i.e., Micrometeoroid and Orbital Debris [MMOD] protection, acoustics) (2) Areas where initial design requirements were eventually considered inadequate and were subsequently augmented (i.e., Toxicity Level 4 materials, emergency hardware and procedures) (3) Areas where risks were initially underestimated, and have subsequently been addressed through additional mitigation (i.e., Extravehicular Activity [EVA] sharp edges, plasma shock hazards) Due to the hard work and cooperation of many parties working together across the span of nearly a decade, the ISS is now a safer and healthier environment for our crew, in many cases exceeding the risk reduction targets inherent in the intent of the original design. It will provide a safe and stable platform for utilization and discovery.

Fodroci, Michael↗
NASA NTRS2011

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↗
NASA NTRS2010

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 NTRS2006

Adding Hierarchical Objects to Relational Database General-Purpose XML-Based Information Managements

NETMARK is a flexible, high-throughput software system for managing, storing, and rapid searching of unstructured and semi-structured documents. NETMARK transforms such documents from their original highly complex, constantly changing, heterogeneous data formats into well-structured, common data formats in using Hypertext Markup Language (HTML) and/or Extensible Markup Language (XML). The software implements an object-relational database system that combines the best practices of the relational model utilizing Structured Query Language (SQL) with those of the object-oriented, semantic database model for creating complex data. In particular, NETMARK takes advantage of the Oracle 8i object-relational database model using physical-address data types for very efficient keyword searches of records across both context and content. NETMARK also supports multiple international standards such as WEBDAV for drag-and-drop file management and SOAP for integrated information management using Web services. The document-organization and -searching capabilities afforded by NETMARK are likely to make this software attractive for use in disciplines as diverse as science, auditing, and law enforcement.

Lin, Shu-Chun↗
NASA NTRS2011

Putting the Power of Configuration in the Hands of the Users

Goal was to reduce the overall cost of human space flight while maintaining the most demanding standards for safety and mission success. In support of this goal, a project team was chartered to replace 18 legacy Space Shuttle nonconformance processes and systems with one fully integrated system Problem Reporting and Corrective Action (PRACA) processes provide a closed-loop system for the identification, disposition, resolution, closure, and reporting of all Space Shuttle hardware/software problems PRACA processes are integrated throughout the Space Shuttle organizational processes and are critical to assuring a safe and successful program Primary Project Objectives Develop a fully integrated system that provides an automated workflow with electronic signatures Support multiple NASA programs and contracts with a single "system" architecture Define standard processes, implement best practices, and minimize process variations

Al-Shihabi, Mary-Jo↗
NASA NTRS2011

Introduction

It would be hard to argue against the fact that Integrated Computational Materials Engineering (ICME) is a fast growing discipline within material science and engineering. A quick scan of the proceedings from conferences such as Aeromat, Material Science and Technology, and the TMS Annual Meeting clearly shows it. What began a few years ago as one symposium has grown into multiple ICME related symposia at each of these conferences. As encouraging as the number of symposia being offered is the attendance at the symposia. For example, one of the ICME symposia at MS&T 10, the symposium in which this book is based, had five sessions which culminated in a panel discussion that was standing room only. In addition to the large, annual materials science and engineering conferences, smaller 1 to 2-day conferences/workshops sponsored by government agencies (e.g. AFRL and NIST) on specific aspects of ICME and by universities promoting their ICME work are regularly offered. And arguably the most significant news with regards to ICME and conferences is the July 2011 First World Congress on ICME. This five day TMS sponsored conference, specifically focused on ICME with an international advisory board of ICME leaders, shows how far ICME has spread across the globe. Evidence for the growth of ICME can also be found in Academia. The University Materials Council (UMC) is composed of department heads for material science and engineering from major U.S. and Canadian universities. Meeting twice a year to share best practices in order to strengthen both the engineering content [1] and the educational process, the UMC s agenda for their Spring 2010 meeting was dedicated to ICME [2]. This meeting was held in response to the growing awareness that the universities play a major role in the success of ICME and therefore need to develop ICME curriculum in order to meet that need. To aid educators in the development of ICME courses, NSF is funding a "Summer School" on ICME to be held at the University of Michigan in 2011 [3]. Northwestern University recently announced a MS Certificate Program in ICME [4]. Course work for this certificate begins in the Fall of 2011. Other signs that ICME is growing comes from the formation of ICME initiatives from work that did not start off with ICME in mind. One of the committees in ASM International is the Materials Properties Database Committee (MPDC). In the 2010 meeting of the MPDC, based on a study by ASM, the committee decided that it would create an ICME sub-committee in order to determine how ASM can meet the growing needs of the ICME community [5]. In 1999, the Air Force Research Laboratory (AFRL) created a consortium, the Metals Affordability Initiative (MAI), with members from both industry and government with a goal of reducing the cost and time to market of producing metal parts for aerospace applications [6].

Arnold, Steven M.↗
NASA NTRS2011

Long-Term International Space Station (ISS) Risk Reduction Activities

As the assembly of the ISS nears completion, it is worthwhile to step back and review some of the actions pursued by the Program in recent years to reduce risk and enhance the safety and health of ISS crewmembers, visitors, and space flight participants. While the initial ISS requirements and design were intended to provide the best practicable levels of safety, it is always possible to further reduce risk given the determination, commitment, and resources to do so. The following is a summary of some of the steps taken by the ISS Program Manager, by our International Partners, by hardware and software designers, by operational specialists, and by safety personnel to continuously enhance the safety of the ISS, and to reduce risk to all crewmembers. While years of work went into the development of ISS requirements, there are many things associated with risk reduction in a Program like the ISS that can only be learned through actual operational experience. These risk reduction activities can be divided into roughly three categories: Areas that were initially noncompliant which have subsequently been brought into compliance or near compliance (i.e., Micrometeoroid and Orbital Debris [MMOD] protection, acoustics) Areas where initial design requirements were eventually considered inadequate and were subsequently augmented (i.e., Toxicity hazard level-4 materials, emergency procedures, emergency equipment, control of drag-throughs) Areas where risks were initially underestimated, and have subsequently been addressed through additional mitigation (i.e., Extravehicular Activity [EVA] sharp edges, plasma shock hazards). Due to the hard work and cooperation of many parties working together across the span of more than a decade, the ISS is now a safer and healthier environment for our crew, in many cases exceeding the risk reduction targets inherent in the intent of the original design. It will provide a safe and stable platform for utilization and discovery for years to come.

Forroci, Michael P.↗
NASA NTRS2011

Which Way is Up? Lessons Learned from Space Shuttle Sensorimotor Research

The Space Shuttle Program provided the opportunity to examine sensorimotor adaptation to space flight in unprecedented numbers of astronauts, including many over multiple missions. Space motion sickness (SMS) severity was highly variable across crewmembers. SMS generally lasted 2-3 days in-flight with approximately 1/3 of crewmembers experiencing moderate to severe symptoms, and decreased incidence in repeat flyers. While SMS has proven difficult to predict from susceptibility to terrestrial analogs, symptoms were alleviated by medications, restriction of early activities, maintaining familiar orientation with respect to the visual environment and maintaining contact cues. Adaptive changes were also reflected by the oculomotor and perceptual disturbances experienced early inflight and by the perceptual and motor coordination problems experienced during re-entry and landing. According to crew self-reports, systematic head movements performed during reentry, as long as paced within one's threshold for motion tolerance, facilitated the early readaptation process. The Shuttle provided early postflight crew access to document the initial performance decrements and time course of recovery. These early postflight measurements were critical to inform the program of risks associated with extending the duration of Shuttle missions. Neurological postflight deficits were documented using a standardized subjective rating by flight surgeons. Computerized dynamic posturography was also implemented as a quantitative means of assessing sensorimotor function to support crew return-to-duty assessments. Towards the end of the Shuttle Program, more emphasis has been placed on mapping physiological changes to functional performance. Future commercial flights will benefit from pre-mission training including exposures to launch and entry G transitions and sensorimotor adaptability assessments. While SMS medication usage will continue to be refined, non-pharmacological countermeasures (e.g., sensory aids) will have both space and Earth-based applications. Early postflight field tests are recommended to provide the evidence base for best practices for future commercial flight programs. Learning Objective: Overview of the Space Shuttle Program regarding adaptive changes in sensorimotor function, including what was learned from research, what was implemented for medical operations, and what is recommended for commercial flights.

Wood, S. J.↗
NASA NTRS2011

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↗
NASA NTRS2011

Geodetic Strain Analysis Tool

A geodetic software analysis tool enables the user to analyze 2D crustal strain from geodetic ground motion, and create models of crustal deformation using a graphical interface. Users can use any geodetic measurements of ground motion and derive the 2D crustal strain interactively. This software also provides a forward-modeling tool that calculates a geodetic velocity and strain field for a given fault model, and lets the user compare the modeled strain field with the strain field obtained from the user s data. Users may change parameters on-the-fly and obtain a real-time recalculation of the resulting strain field. Four data products are computed: maximum shear, dilatation, shear angle, and principal components. The current view and data dependencies are processed first. The remaining data products and views are then computed in a round-robin fashion to anticipate view changes. When an analysis or display parameter is changed, the affected data products and views are invalidated and progressively re-displayed as available. This software is designed to facilitate the derivation of the strain fields from the GPS and strain meter data that sample it to facilitate the understanding of the strengths and weaknesses of the strain field derivation from continuous GPS (CGPS) and other geodetic data from a variety of tectonic settings, to converge on the "best practices" strain derivation strategy for the Solid Earth Science ESDR System (SESES) project given the CGPS station distribution in the western U.S., and to provide SESES users with a scientific and educational tool to explore the strain field on their own with user-defined parameters.

Kedar, Sharon↗
NASA NTRS2011

NASA's Human Rating Requirements - A Historical Interpretive Perspective

Section 3.0 of NASA's Human Rating Requirements for Space Systems, NPR 8705.2, represents technical engineering requirements that the Agenc y requires of Human Space Systems. In many cases the requirements are not unlike requirements for any space system, crewed or uncrewed, th ey deal with successfully accomplishing the mission objectives. Howev er, they go one step further and have requirements that go beyond suc cessful completion of the mission and dictate functions or actions ne cessary to assure the survival of the crew. In that regard they are u nique from other space system requirements. Even with their uniquenes s the technical requirements of the NPR 8705.2 have been relatively u nchanged in overall intent over the revisions. They all have provided for system redundancy, crew habitable environment, crew situational awareness, crew operation, system control, emergency egress and abort systems. In a few cases the intent of the requirement was changed in tentionally, either to restrict certain types of systems or their fun ctions, or to encompass lessons learned from previous programs. For t he most part the requirements are non controversial and represent the current best practices for human space systems, however, a few requi rements are always debated and have evolved over revisions of the NPR due to studies conducted with various programs like the Orbital Spac e Plane and the Constellation Programs. Those requirements will be di scussed using results of trade studies conducted during past programs highlighting how these particular requirements have evolved through the revisions of the NPR. Comments will also be provided for requirem ents that although not debated, have provided challenges in interpret ation.

Langford, Gerald↗
NASA NTRS2011

2010 CEOS Field Reflectance Intercomparisons Lessons Learned

This paper summarizes lessons learned from the 2009 and 2010 joint field campaigns to Tuz Golu, Turkey. Emphasis is placed on the 2010 campaign related to understanding the equipment and measurement protocols, processing schemes, and traceability to SI quantities. Participants in both 2009 and 2010 used an array of measurement approaches to determine surface reflectance. One lesson learned is that even with all of the differences in collection between groups, the differences in reflectance are currently dominated by instrumental artifacts including knowledge of the white reference. Processing methodology plays a limited role once the bi-directional reflectance of the white reference is used rather than a hemispheric-directional value. The lack of a basic set of measurement protocols, or best practices, limits a group s ability to ensure SI traceability and the development of proper error budgets. Finally, rigorous attention to sampling methodology and its impact on instrument behavior is needed. The results of the 2009 and 2010 joint campaigns clearly demonstrate both the need and utility of such campaigns and such comparisons must continue in the future to ensure a coherent set of data that can span multiple sensor types and multiple decades.

Thome, Kurtis↗
NASA NTRS2012

Take the Reins on Model Quality with ModelCHECK and Gatekeeper

Model quality and consistency has been an issue for us due to the diverse experience level and imaginative modeling techniques of our users. Fortunately, setting up ModelCHECK and Gatekeeper to enforce our best practices has helped greatly, but it wasn't easy. There were many challenges associated with setting up ModelCHECK and Gatekeeper including: limited documentation, restrictions within ModelCHECK, and resistance from end users. However, we consider ours a success story. In this presentation we will describe how we overcame these obstacles and present some of the details of how we configured them to work for us.

Jones, Corey↗
NASA NTRS2011

Fault Management Guiding Principles

Regardless of the mission type: deep space or low Earth orbit, robotic or human spaceflight, Fault Management (FM) is a critical aspect of NASA space missions. As the complexity of space missions grows, the complexity of supporting FM systems increase in turn. Data on recent NASA missions show that development of FM capabilities is a common driver for significant cost overruns late in the project development cycle. Efforts to understand the drivers behind these cost overruns, spearheaded by NASA's Science Mission Directorate (SMD), indicate that they are primarily caused by the growing complexity of FM systems and the lack of maturity of FM as an engineering discipline. NASA can and does develop FM systems that effectively protect mission functionality and assets. The cost growth results from a lack of FM planning and emphasis by project management, as well the maturity of FM as an engineering discipline, which lags behind the maturity of other engineering disciplines. As a step towards controlling the cost growth associated with FM development, SMD has commissioned a multi-institution team to develop a practitioner's handbook representing best practices for the end-to-end processes involved in engineering FM systems. While currently concentrating primarily on FM for science missions, the expectation is that this handbook will grow into a NASA-wide handbook, serving as a companion to the NASA Systems Engineering Handbook. This paper presents a snapshot of the principles that have been identified to guide FM development from cradle to grave. The principles range from considerations for integrating FM into the project and SE organizational structure, the relationship between FM designs and mission risk, and the use of the various tools of FM (e.g., redundancy) to meet the FM goal of protecting mission functionality and assets.

principles↗
NASA NTRS2011

Bounding Species Distribution Models

Species distribution models are increasing in popularity for mapping suitable habitat for species of management concern. Many investigators now recognize that extrapolations of these models with geographic information systems (GIS) might be sensitive to the environmental bounds of the data used in their development, yet there is no recommended best practice for "clamping" model extrapolations. We relied on two commonly used modeling approaches: classification and regression tree (CART) and maximum entropy (Maxent) models, and we tested a simple alteration of the model extrapolations, bounding extrapolations to the maximum and minimum values of primary environmental predictors, to provide a more realistic map of suitable habitat of hybridized Africanized honey bees in the southwestern United States. Findings suggest that multiple models of bounding, and the most conservative bounding of species distribution models, like those presented here, should probably replace the unbounded or loosely bounded techniques currently used [Current Zoology 57 (5): 642-647, 2011].

Stohlgren, Thomas J.↗
NASA NTRS2012

Field Geologic Observation and Sample Collection Strategies for Planetary Surface Exploration: Insights from the 2010 Desert RATS Geologist Crewmembers

Observation is the primary role of all field geologists, and geologic observations put into an evolving conceptual context will be the most important data stream that will be relayed to Earth during a planetary exploration mission. Sample collection is also an important planetary field activity, and its success is closely tied to the quality of contextual observations. To test protocols for doing effective planetary geologic field- work, the Desert RATS(Research and Technology Studies) project deployed two prototype rovers for two weeks of simulated exploratory traverses in the San Francisco volcanic field of northern Arizona. The authors of this paper represent the geologist crew members who participated in the 2010 field test.We document the procedures adopted for Desert RATS 2010 and report on our experiences regarding these protocols. Careful consideration must be made of various issues that impact the interplay between field geologic observations and sample collection, including time management; strategies relatedtoduplicationofsamplesandobservations;logisticalconstraintson the volume and mass of samples and the volume/transfer of data collected; and paradigms for evaluation of mission success. We find that the 2010 field protocols brought to light important aspects of each of these issues, and we recommend best practices and modifications to training and operational protocols to address them. Underlying our recommendations is the recognition that the capacity of the crew to flexibly execute their activities is paramount. Careful design of mission parameters, especially field geologic protocols, is critical for enabling the crews to successfully meet their science objectives.

Hurtado, Jose M., Jr.↗
NASA NTRS2012

Flow Analysis Tool White Paper

Faster networks are continually being built to accommodate larger data transfers. While it is intuitive to think that implementing faster networks will result in higher throughput rates, this is often not the case. There are many elements involved in data transfer, many of which are beyond the scope of the network itself. Although networks may get bigger and support faster technologies, the presence of other legacy components, such as older application software or kernel parameters, can often cause bottlenecks. Engineers must be able to identify when data flows are reaching a bottleneck that is not imposed by the network and then troubleshoot it using the tools available to them. The current best practice is to collect as much information as possible on the network traffic flows so that analysis is quick and easy. Unfortunately, no single method of collecting this information can sufficiently capture the whole endto- end picture. This becomes even more of a hurdle when large, multi-user systems are involved. In order to capture all the necessary information, multiple data sources are required. This paper presents a method for developing a flow analysis tool to effectively collect network flow data from multiple sources and provide that information to engineers in a clear, concise way for analysis. The purpose of this method is to collect enough information to quickly (and automatically) identify poorly performing flows along with the cause of the problem. The method involves the development of a set of database tables that can be populated with flow data from multiple sources, along with an easyto- use, web-based front-end interface to help network engineers access, organize, analyze, and manage all the information.

Boscia, Nichole K.↗