Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Lessons learned”

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 127 records · Page 7

Previous experience in manned space flight: A survey of human factors lessons learned

Previous experience in manned space flight programs can be used to compile a data base of human factors lessons learned for the purpose of developing aids in the future design of inhabited spacecraft. The objectives are to gather information available from relevant sources, to develop a taxonomy of human factors data, and to produce a data base that can be used in the future for those people involved in the design of manned spacecraft operations. A study is currently underway at the Johnson Space Center with the objective of compiling, classifying, and summarizing relevant human factors data bearing on the lessons learned from previous manned space flights. The research reported defines sources of data, methods for collection, and proposes a classification for human factors data that may be a model for other human factors disciplines.

Chandlee, George O.↗

Lessons Learned JSC Micro-Wireless Instrumentation Systems on Space Shuttle and International Space Station CANEUS 2006

A viewgraph presentation on lessons learned from NASA Johnson Space Center's micro-wireless instrumentation is shown. The topics include: 1) Background, Rationale and Vision; 2) NASA JSC/Structural Engineering Approach & History; 3) Orbiter Wing Leading Edge Impact Detection System; 4) WLEIDS Confidence and Micro-WIS Lessons Learned; and 5) Current Projects and Recommendations.

Studor, George↗

Commercial Orbital Transportation Services (COTS) Program Lessons Learned

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team in close coordination with the COTS Program. This document provides a point-in-time, cumulative, summary of actionable key lessons learned derived from the design project. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

COTS↗

Loss of Signal: Aeromedical Lessons Learned from the STS-107 Columbia Space Shuttle Mishap

The editors of Loss of Signal wanted to document the aeromedical lessons learned from the Space Shuttle Columbia mishap. The book is intended to be an accurate and easily understood account of the entire process of recovering and analyzing the human remains, investigating and analyzing what happened to the crew, and using the resulting information to recommend ways to prevent mishaps and provide better protection to crewmembers. Our goal is to capture the passions of those who devoted their energies in responding to the Columbia mishap. We have reunited authors who were directly involved in each of these aspects. These authors tell the story of their efforts related to the Columbia mishap from their point of view. They give the reader an honest description of their responsibilities and share their challenges, their experiences, and their lessons learned on how to enhance crew safety and survival, and how to be prepared to support space mishap investigations. As a result of this approach, a few of the chapters have some redundancy of information and authors' opinions may differ. In no way did we or they intend to assign blame or criticize anyone's professional efforts. All those involved did their best to obtain the truth in the situations to which they were assigned.

Stepaniak, Philip C.↗

Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

Williams, David E.↗

Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

Williams, David E.↗

Lessons Learned Implementing Multi-Mission Sequencing Software

This paper will describe the software and its uses to provide context for its criticality. The different approaches that have been taken to implement the software in a multi-mission format will be outlined. The advantages and disadvantages as well as the lessons learned during development and maintenance of these different architectures will be discussed, Finally. the use of multi-mission software in operations and the lessons learned from using it will be discussed.This paper will provide valuable information to organizations exploring the use of multi-mission software. regardless of whether the change is to minimize spacecraft ground software development time or cost reduction. Similarly. the paper will provide insight into some of the steps that can be taken during software development and operational use that will minimize difficulty later.

software↗

Heritage Adoption Lessons Learned: Cover Deployment and Latch Mechanism

Within JPL, there is a technology thrust need to develop a larger Cover Deployment and Latch Mechanism (CDLM) for future missions. The approach taken was to adopt and scale the CDLM design as used on the Galaxy Evolution Explorer (GALEX) project. The three separate mechanisms that comprise the CDLM will be discussed in this paper in addition to a focus on heritage adoption lessons learned and specific examples. These lessons learned will be valuable to any project considering the use of heritage designs.

Wincentsen, James↗

Lessons Learned from MARVEL Initial Fabrication and Testing

The Microreactor Applications Research Validation and Evaluation (MARVEL) project is intended to be amongst the first U.S. advanced reactor demonstrations in four decades. By virtue of being sponsored directly by the U.S. Department of Energy, the reactor is intended to benefit the broader nuclear community by exercising design processes, safety reviews, and supply chains. This project is intent on publicly documenting key lessons learned along the way toward demonstration. Building on a 2024 report that focused on lessons learned from the design and project management phase, this 2025 edition focuses on findings from the MARVEL guard vessel fabrication and primary coolant apparatus test (PCAT) testing.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Spacecraft Line-Of-Sight Jitter Mitigation and Management Lessons Learned and Engineering Best Practices

Predicting, managing, controlling, and testing spacecraft line-of-sight (LoS) jitter caused by micro-vibrations due to onboard internal disturbance sources is a formidable multidisciplinary engineering task. It is especially challenging for those missions hosting high-performance, vibration-sensitive optical sensor payloads with stringent pointing stability requirements. Both NASA and ESA are planning technically aggressive spaceflight missions that include ultra-high-performance optical payloads with delicate, highly vibration-sensitive scientific and observational instruments. The GN&C community of practice will need to leverage and build upon their collective experiences and lessons learned to better address future micro-vibration challenges. To identify lessons learned and best engineering practices the NASA Engineering & Safety Center (NESC) sponsored a two-day Spacecraft LoS Jitter Workshop in late 2019. The workshop’s goal was to provide a multidisciplinary forum to elicit deeper understanding of the issues related to solving the spacecraft LoS jitter/micro-vibration problem. A primary objective was to identify and share best practices, rules of thumb, and options for jitter-related activities. Representatives from NASA, JPL, ESA, along with NASA’s industrial partners, independent consultant subject matter experts, and members of academia participated in the workshop. This paper will describe the motivation for the NASA Spacecraft LoS Jitter Workshop and summarize the identified findings, observations, and recommendations.

Lessons Learned;↗

Systems Engineering Lessons Learned from Solar Array Structures and Mechanisms Deployment

This report has been developed by the National Aeronautics and Space Administration (NASA) Human Exploration and Operations Mission Directorate (HEOMD) Risk Management team in close coordination with the Engineering Directorate at LaRC. This document provides a point-in-time, cumulative, summary of actionable key lessons learned derived from the design project. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.

Solar Array Structures↗

Hayabusa Recovery, Curation and Preliminary Sample Analysis: Lessons Learned from Recent Sample Return Mission

I describe lessons learned from my participation on the Hayabusa Mission, which returned regolith grains from asteroid Itokawa in 2010 [1], comparing this with the recently returned Stardust Spacecraft, which sampled the Jupiter Family comet Wild 2. Spacecraft Recovery Operations: The mission Science and Curation teams must actively participate in planning, testing and implementing spacecraft recovery operations. The crash of the Genesis spacecraft underscored the importance of thinking through multiple contingency scenarios and practicing field recovery for these potential circumstances. Having the contingency supplies on-hand was critical, and at least one full year of planning for Stardust and Hayabusa recovery operations was necessary. Care must be taken to coordinate recovery operations with local organizations and inform relevant government bodies well in advance. Recovery plans for both Stardust and Hayabusa had to be adjusted for unexpectedly wet landing site conditions. Documentation of every step of spacecraft recovery and deintegration was necessary, and collection and analysis of launch and landing site soils was critical. We found the operation of the Woomera Text Range (South Australia) to be excellent in the case of Hayabusa, and in many respects this site is superior to the Utah Test and Training Range (used for Stardust) in the USA. Recovery operations for all recovered spacecraft suffered from the lack of a hermetic seal for the samples. Mission engineers should be pushed to provide hermetic seals for returned samples. Sample Curation Issues: More than two full years were required to prepare curation facilities for Stardust and Hayabusa. Despite this seemingly adequate lead time, major changes to curation procedures were required once the actual state of the returned samples became apparent. Sample databases must be fully implemented before sample return for Stardust we did not adequately think through all of the possible sub sampling and analytical activities before settling on a database design - Hayabusa has done a better job of this. Also, analysis teams must not be permitted to devise their own sample naming schemes. The sample handling and storage facilities for Hayabusa are the finest that exist, and we are now modifying Stardust curation to take advantage of the Hayabusa facilities. Remote storage of a sample subset is desirable. Preliminary Examination (PE) of Samples: There must be some determination of the state and quantity of the returned samples, to provide a necessary guide to persons requesting samples and oversight committees tasked with sample curation oversight. Hayabusa s sample PE, which is called HASPET, was designed so that late additions to the analysis protocols were possible, as new analytical techniques became available. A small but representative number of recovered grains are being subjected to in-depth characterization. The bulk of the recovered samples are being left untouched, to limit contamination. The HASPET plan takes maximum advantage of the unique strengths of sample return missions

Zolensky, Michael E.↗

Constellation Lessons Learned Executive Summary

This slide presentation reviews the lessons learned from the Constellation Program (CxP) and identified several factors that contributed to the inability of the CxP to meet the cost and schedule commitments. The review includes a significant section on the context in which the CxP operated since new programs are likely to experience the same constraints.

Thomas, L. Dale↗

ATLAS Beam Steering Mechanism Lessons Learned

This paper describes the design, testing, and lessons learned during the development of the Advanced Topographic Laser Altimeter System (ATLAS) Beam Steering Mechanism (BSM). The BSM is a 2 degree-of-freedom tip-tilt mechanism for the purpose of pointing a flat mirror to tightly control the co-alignment of the transmitted laser and the receiver telescope of the ATLAS instrument. The high resolution needs of the mission resulted in sub-arcsecond pointing and knowledge requirements, which have been met. Development of the methodology to verify performance required significant effort. The BSM will fly as part of the Ice, Cloud, and Elevation Satellite II Mission (ICESat II), which is scheduled to be launched in 2017. The ICESat II primary mission is to map the earth's surface topography for the determination of seasonal changes of ice sheet thickness and vegetation canopy thickness to establish long-term trends.

controls↗

Beam Steering Mechanism (BSM) Lessons Learned

This paper describes the design, testing, and lessons learned during the development of the Advanced Topographic Laser Altimeter System (ATLAS) Beam Steering Mechanism (BSM). The BSM is a 2 degree-of-freedom tip-tilt mechanism for the purpose of pointing a flat mirror to tightly control the co-alignment of the transmitted laser and the receiver telescope of the ATLAS instrument. High resolution needs of the mission resulted in sub-arcsecond pointing and knowledge requirements, which have been met. Development of methodology to verify performance was a significant effortadvancement. The BSM will fly as part of the Ice, Cloud, and Elevation Satellite 2 Mission (ICESat 2), which is scheduled to be launched in 2017. The ICESat 2 primary mission is to map the earths surface topography for the determination of seasonal changes of ice sheet thickness as well as vegetation canopy thickness.

Mechanism↗

ATLAS Beam Steering Mechanism (BSM) Lessons Learned

This paper describes the design, testing, and lessons learned during the development of the Advanced Topographic Laser Altimeter System (ATLAS) Beam Steering Mechanism (BSM). The BSM is a 2 degree-of-freedom tip-tilt mechanism for the purpose of pointing a flat mirror to tightly control the co-alignment of the transmitted laser and the receiver telescope of the ATLAS instrument. The high resolution needs of the mission resulted in sub-arcsecond pointing and knowledge requirements, which have been met. Development of the methodology to verify performance required significant effort. The BSM will fly as part of the Ice, Cloud, and Elevation Satellite II Mission (ICESat II), which is scheduled to be launched in 2017. The ICESat II primary mission is to map the Earth's surface topography for the determination of seasonal changes of ice sheet thickness and vegetation canopy thickness to establish long-term trends.

Blumenstock, Kenneth A.↗

Lessons Learned from Optical Payload for Lasercomm Science (OPALS) Mission Operations

This paper provides an overview of Optical Payload for Lasercomm Science (OPALS) activities and lessons learned during mission operations. Activities described cover the periods of commissioning, prime, and extended mission operations, during which primary and secondary mission objectives were achieved for demonstrating space-to-ground optical communications. Lessons learned cover Mission Operations System topics in areas of: architecture verification and validation, staffing, mission support area, workstations, workstation tools, interfaces with support services, supporting ground stations, team training, procedures, flight software upgrades, post-processing tools, and public outreach.

Sindiy, Oleg V.↗