SEARCH · Search NASA

Results for “standards and best practice”

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 73 records · Page 4

All sources NASA NTRS DOE OSTI

NASA NTRS2010

Workmanship Challenges for NASA Mission Hardware

This slide presentation reviews several challenges in workmanship for NASA mission hardware development. Several standards for NASA workmanship exist, that are required for all programs, projects, contracts and subcontracts. These Standards contain our best known methods for avoiding past assembly problems and defects. These best practices may not be available if suppliers are used who are not compliant with them. Compliance includes having certified operators and inspectors. Some examples of problems that have occured from the lack of requirements flow-down to contractors are reviewed. The presentation contains a detailed example of the challenge in regards to The Packaging "Design" Dilemma.

Plante, Jeannette↗

NASA NTRS2021

Classifications and Requirements for Testing Systems and Hardware to be Exposed to Dust in Planetary Environments

The purpose of this NASA Technical Standard is to establish minimum requirements and provide effective guidance regarding methodologies and best practices for testing systems and hardware to be exposed to dust in dust laden and generating environments. The intent is to facilitate consistency and efficiency in testing space systems, subsystems, or components with operations and missions in dusty environments.

Kristen Kathleen John↗

NASA NTRS2017

Embracing Open Source for NASA's Earth Science Data Systems

The overarching purpose of NASAs Earth Science program is to develop a scientific understanding of Earth as a system. Scientific knowledge is most robust and actionable when resulting from transparent, traceable, and reproducible methods. Reproducibility includes open access to the data as well as the software used to arrive at results. Additionally, software that is custom-developed for NASA should be open to the greatest degree possible, to enable re-use across Federal agencies, reduce overall costs to the government, remove barriers to innovation, and promote consistency through the use of uniform standards. Finally, Open Source Software (OSS) practices facilitate collaboration between agencies and the private sector. To best meet these ends, NASAs Earth Science Division promotes the full and open sharing of not only all data, metadata, products, information, documentation, models, images, and research results but also the source code used to generate, manipulate and analyze them. This talk focuses on the challenges to open sourcing NASA developed software within ESD and the growing pains associated with establishing policies running the gamut of tracking issues, properly documenting build processes, engaging the open source community, maintaining internal compliance, and accepting contributions from external sources. This talk also covers the adoption of existing open source technologies and standards to enhance our custom solutions and our contributions back to the community. Finally, we will be introducing the most recent OSS contributions from NASA Earth Science program and promoting these projects for wider community review and adoption.

Earth Science↗

NASA NTRS1995

Research Problems Associated with Limiting the Applied Force in Vibration Tests and Conducting Base-Drive Modal Vibration Tests

The intent of this paper is to make a case for developing and conducting vibration tests which are both realistic and practical (a question of tailoring versus standards). Tests are essential for finding things overlooked in the analyses. The best test is often the most realistic test which can be conducted within the cost and budget constraints. Some standards are essential, but the author believes more in the individual's ingenuity to solve a specific problem than in the application of standards which reduce problems (and technology) to their lowest common denominator. Force limited vibration tests and base-drive modal tests are two examples of realistic, but practical testing approaches. Since both of these approaches are relatively new, a number of interesting research problems exist, and these are emphasized herein.

tests tailored tests cost analysis↗

NASA NTRS2015

JSC Design and Procedural Standards

This document contains design and procedural requirements for human spaceflight equipment based on lessons learned and best practices.

Yates, Russell↗

NASA NTRS2015

JSC Design and Procedural Standards

This document contains design and procedural requirements for human spaceflight equipment based on lessons learned and best practices.

Yates, Russell E.↗

NASA NTRS2015

JSC Design and Procedural Standards

This document contains design and procedural requirements for human spaceflight equipment based on lessons learned and best practices.

Yates, Russell↗

NASA NTRS2007

Software Process Assurance for Complex Electronics

Complex Electronics (CE) now perform tasks that were previously handled in software, such as communication protocols. Many methods used to develop software bare a close resemblance to CE development. Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. With CE devices obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that used standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques were used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that was more easily maintained, consistent and configurable based on the device used.

Plastow, Richard A.↗

NASA NTRS2007

Software Process Assurance for Complex Electronics (SPACE)

Complex Electronics (CE) are now programmed to perform tasks that were previously handled in software, such as communication protocols. Many of the methods used to develop software bare a close resemblance to CE development. For instance, Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that looks at using standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques can be used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that will be more easily maintained, consistent and configurable based on the device used.

Plastow, Richard A.↗

NASA NTRS2024

Appendix N. Pc Calculation Approaches – UPDATE 3/20/24

This document represents a technical content update to Appendix N of the NASA Spacecraft Conjunction Assessment and Collision Avoidance Best Practices Handbook (OCE-51, available on NODIS) requested by the Consultative Committee for Space Data Standards (CCSDS) to document the background on why NASA populates certain fields of the Conjunction Data Message (CDM) in certain ways. This update was requested to be used as reference material for the CCSDS CDM documentation update and so is being published as a white paper out of cycle from Handbook updates. When the full Handbook is next updated, these Appendix redlines may be incorporated into the official document. Two versions are attached - the redlines to the published Handbook for use in understanding what has changed and a clean copy.

conjunction assessment↗

NASA NTRS2016

Final Report of the NASA Office of Safety and Mission Assurance Agile Benchmarking Team

To ensure that the NASA Safety and Mission Assurance (SMA) community remains in a position to perform reliable Software Assurance (SA) on NASAs critical software (SW) systems with the software industry rapidly transitioning from waterfall to Agile processes, Terry Wilcutt, Chief, Safety and Mission Assurance, Office of Safety and Mission Assurance (OSMA) established the Agile Benchmarking Team (ABT). The Team's tasks were: 1. Research background literature on current Agile processes, 2. Perform benchmark activities with other organizations that are involved in software Agile processes to determine best practices, 3. Collect information on Agile-developed systems to enable improvements to the current NASA standards and processes to enhance their ability to perform reliable software assurance on NASA Agile-developed systems, 4. Suggest additional guidance and recommendations for updates to those standards and processes, as needed. The ABT's findings and recommendations for software management, engineering and software assurance are addressed herein.

Software Assurance↗

NASA NTRS2011

Software Development Standard Processes (SDSP)

A JPL-created set of standard processes is to be used throughout the lifecycle of software development. These SDSPs cover a range of activities, from management and engineering activities, to assurance and support activities. These processes must be applied to software tasks per a prescribed set of procedures. JPL s Software Quality Improvement Project is currently working at the behest of the JPL Software Process Owner to ensure that all applicable software tasks follow these procedures. The SDSPs are captured as a set of 22 standards in JPL s software process domain. They were developed in-house at JPL by a number of Subject Matter Experts (SMEs) residing primarily within the Engineering and Science Directorate, but also from the Business Operations Directorate and Safety and Mission Success Directorate. These practices include not only currently performed best practices, but also JPL-desired future practices in key thrust areas like software architecting and software reuse analysis. Additionally, these SDSPs conform to many standards and requirements to which JPL projects are beholden.

Lavin, Milton L.↗

NASA NTRSDate not supplied

Summary of Propagation Cases of the Third AIAA Sonic Boom Prediction Workshop

A summary is provided for the propagation portion of the Third AIAA Sonic Boom Prediction Workshop held January 5, 2020 in conjunction with the AIAA SciTech 2020 conference. Near-field pressure waveforms for two cases were supplied at multiple azimuthal angles. Ground signatures across the breadth of the sonic boom primary carpet and their corresponding loudness metrics were requested. Each case had some required, as well as some optional, runs. The required cases included atmospheric profiles with measured data including winds. Optional cases included a level-acceleration sonic boom focusing case as well as prediction under standard atmospheric conditions. Participants provided ground signatures along with several loudness metrics using their best sonic boom prediction practices. All the participants' submissions are compared and discussed for each case. Noise or loudness measures are calculated and detailed comparisons and statistical analyses are performed and presented. Compared to previous workshops, the selected cases in the current workshop have much lower boom loudness levels. As was observed in the past workshops, the variation in the loudness measures and spread between participants' submissions increased as the computation proceeded from under-track locations towards the lateral cut-off. Lessons learned during this workshop are discussed and recommendations are made for potential improvements and possible subsequent workshops as we collectively attempt to refine our analysis methods.

SBPW3↗

NASA NTRSDate not supplied

Safe Space Conduct: NASA Best Practices Overview

While prevention of launch and on-orbit collisions has been an institutional concern of NASA for several decades (beginning with the Shuttle program), historically the paucity of spaceactors and deployed payloads made the conduct of such protection activities relatively straightforward. With the substantial increases in launched payloads over the last several years, collision avoidance operations have become substantially more complicated. At the same time, many operators are uncertain regarding what collision avoidance activities are appropriate to their missions. The lack of a space traffic management authority to articulate standards and guidelines for such conduct has only increased the confusion.In response to this situation, NASA has published a Spacecraft Conjunction Assessment and Collision Avoidance Handbook, which articulates and explains the launch and on-orbit collision avoidance best practices that the Agency has developed and is requiring of present and future NASA missions. Because the CA2 Handbook is a living document regularly updated to reflect best practices changes as the industry develops, feedback from both NASA missions and other users is continuously collected in order to issue CA2 Handbook updates.This talk will summarize and explain the collision avoidance best practices from the CA2Handbook, along with the key issues that drove the selection of those practices.

Conjunction Assessment↗

NASA NTRS2003

Standards Advisor-Advanced Information Technology for Advanced Information Delivery

Developers of space systems must deal with an increasing amount of information in responding to extensive requirements and standards from numerous sources. Accessing these requirements and standards, understanding them, comparing them, negotiating them and responding to them is often an overwhelming task. There are resources to aid the space systems developer, such as lessons learned and best practices. Again, though, accessing, understanding, and using this information is often more difficult than helpful. This results in space systems that: 1. Do not meet all their requirements. 2. Do not incorporate prior engineering experience. 3. Cost more to develop. 4. Take longer to develop. The NASA Technical Standards Program (NTSP) web site at http://standards.nasa.gov has made significant improvements in making standards, lessons learned, and related material available to space systems developers agency-wide. The Standards Advisor was conceived to take the next steps beyond the current product, continuing to apply evolving information technology that continues to improve information delivery to space systems developers. This report describes the features of the Standards Advisor and suggests a technical approach to its development.

Hawker, J. Scott↗

NASA NTRSDate not supplied

NASA Best Practices Overview

While prevention of launch and on-orbit collisions has been an institutional concern of NASA for several decades (beginning with the Shuttle program), historically the paucity of space actors and deployed payloads made the conduct of such protection activities relatively straightforward. With the substantial increases in launched payloads over the last several years, collision avoidance operations have become substantially more complicated. At the same time, many operators are uncertain regarding what collision avoidance activities are appropriate to their missions. The lack of a space traffic management authority to articulate standards and guidelines for such conduct has only increased the confusion. In response to this situation, NASA has published a Spacecraft Conjunction Assessment and Collision Avoidance Handbook, which articulates and explains the launch and on-orbit collision avoidance best practices that the Agency has developed and is requiring of present and future NASA missions. Because the CA2 Handbook is a living document regularly updated to reflect best practices changes as the industry develops, feedback from both NASA missions and other users is continuously collected in order to issue CA2 Handbook updates. This talk will summarize and explain the collision avoidance best practices from the CA2 Handbook, along with the key issues that drove the selection of those practices.

Conjunction Assessment↗

NASA NTRSDate not supplied

TOLNet’s FAIR Journey: Yesterday, Today, and Tomorrow

The Tropospheric Ozone Lidar Network (TOLNet) has generated over a decade of ozone vertical profile data products over North America and contributed to several air quality focused field studies. The science value of the TOLNet data has been demonstrated in numerous peer-reviewed publications on air quality and ozone relevant research. As the broad scientific community has moved towards adopting FAIR Principles to make data more findable, accessible, interoperable, and (re)usable, the TOLNet team has been consistently making data more FAIR. This effort has many challenges, partially reflecting on the FAIR principles being domain agnostic while the implementation needs to be domain specific. The FAIR principles declare the dependence on the community standards, domain-relevant metadata, and rich metadata. This presentation uses the TOLNet data and data system as an example to explore the best practices to implement FAIR principle. Particularly, we will examine the metadata and the “richness” to support findability and usability as well as machine-to-machine actionability via API. Last year, as part of our FAIR journey, we launched the TOLNet website (https://tolnet.larc.nasa.gov/) and the API (https://tolnet.larc.nasa.gov/api/). Part of this process included extracting and cataloging metadata across the entire TOLNet mission timeframe. This enabled users to search through the mission by various metadata criteria, improving the findability and accessibility. And computers could connect directly to the TOLNet API to extract both metadata and data, providing a level of interoperability never present before for TOLNet data. On top of that, all new TOLNet data is now automatically validated using the API to ensure it complies with GEOMS standards, aiding in reusability. It takes both technology and scientists working together to make progress. The next step is to evaluate the current TOLNet offerings against NASA’s Practical Guide for Open, Free & FAIR NASA Earth Science Data Products (https://doi.org/10.5067/DOC/ESCO/ESDSWG-0002V1).

TOLNet↗

NASA NTRSDate not supplied

Trends in Human Spaceflight: Analysis of Observed Propulsion Failure Modes Following NASA’s Artemis I Mission

In 2022, NASA’s Artemis program returned the agency to lunar space, propelled by the Orion European Service Module (ESM). Through rigorous ground test campaigns for Artemis I and II and the collection and transmission of operational data during the Artemis I flight, the Safety and Mission Assurance (S&MA) team created and maintained a robust database of component nonconformances. This study analyzes in-flight and ground processing findings on the Artemis ESM propulsion subsystem to track reliability and safety metrics, as well as comparing the data to that of previous human spaceflight programs, Apollo and Space Shuttle. In drawing a comparison to the Artemis I flight, recommendations can be made for the Artemis II crewed mission to ensure best practices for flight safety, including redundancy and failure tolerance in the system. The results reinforce a need for robust safety standards and caution against the complacency of a single successful test flight.

human spaceflight safety↗