Search NASA⌕ Search

SEARCH · Search NASA

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 1,423 records · Page 79
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

The Low-Beta Quadrupoles for the High-Luminosity Large Hadron Collider: enabling higher luminosity by using Nb_3Sn conductor

The large-aperture, high-gradient Low Beta Quadrupoles for the High Luminosity Large Hadron Collider at CERN are the cornerstones of this collider. They are first-of-the-kind accelerator magnets bringing Nb_3Sn conductor to High Energy Physics colliders. In the US they are being fabricated and tested by the HL-LHC Accelerator Upgrade Project (AUP), and in Europe by CERN. The design was developed by AUP and CERN in close collaboration. The Q1/Q3 cryo-assemblies contain two 4.2 m long magnets (MQXFA) fabricated and by AUP. They are tested vertically before use in a cry-assembly. In this paper we are going to present the main features of the MQXFA design, results of vertical tests, and main lessons learned. We will also discuss lessons learned for future use of Nb_3Sn magnets in HEP colliders.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
NASA NTRS1995

The Clementine mechanisms

The Clementine spacecraft was developed under the 'faster, better, cheaper' theme. The constraints of a low budget coupled with an unusually tight schedule forced many departures from the normal spacecraft development methods. This paper discusses technical lessons learned about several of the mechanisms on the Clementine spacecraft as well as managerial lessons learned for the entire mechanisms subsystem. A quick overview of the Clementine mission is included; the mission schedule and environment during the mechanisms releases and deployment are highlighted. This paper then describes the entire mechanisms subsystem. The design and test approach and key philosophies for a fast-track program are discussed during the description of the mechanisms subsystem. The mechanism subsystem included a marman clamp separation system, a separation nut separation system, a solar panel deployment and pointing system, a high gain antenna feed deployment system, and two separate sensor cover systems. Each mechanism is briefly discussed. Additional technical discussion is given on the marman clamp design, the sensor cover designs, and the design and testing practices for systems driven by heated actuators (specifically paraffin actuators and frangibolts). All of the other mechanisms were of conventional designs and will receive less emphasis. Lessons learned are discussed throughout the paper as they applied to the systems being discussed. Since there is information on many different systems, this paper is organized so that information on a particular topic can be quickly referenced.

Purdy, William↗
NASA NTRS2011

The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations

Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. This paper will give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified. The training methodology for developing flight controllers has evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers will share their experiences in training and operating the Space Shuttle throughout the Program s history. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The reader will learn what it is like to perform a simulation as a shuttle flight controller. Finally, the paper will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors. These endeavors could range from going to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle and inspire the next generation of space explorers.

Dittemore, Gary D.↗
DOE OSTI2022

Science of the Van Allen Probes Science Operations Centers

The Van Allen Probes mission operations materialized through a distributed model in which operational responsibility was divided between the Mission Operations Center (MOC) and separate instrument specific SOCs. The sole MOC handled all aspects of telemetering and receiving tasks as well as certain scientifically relevant ancillary tasks. Each instrument science team developed individual instrument specific SOCs proficient in unique capabilities in support of science data acquisition, data processing, instrument performance, and tools for the instrument team scientists. In parallel activities, project scientists took on the task of providing a significant modeling tool base usable by the instrument science teams and the larger scientific community. With a mission as complex as Van Allen Probes, scientific inquiry occurred due to constant and significant collaboration between the SOCs and in concert with the project science team. Planned cross-instrument coordinated observations resulted in critical discoveries during the seven-year mission. Instrument cross-calibration activities elucidated a more seamless set of data products. Specific topics include post-launch changes and enhancements to the SOCs, discussion of coordination activities between the SOCs, SOC specific analysis software, modeling software provided by the Van Allen Probes project, and a section on lessons learned. One of the most significant lessons learned was the importance of the original decision to implement individual team SOCs providing timely and well-documented instrument data for the NASA Van Allen Probes Mission scientists and the larger magnetospheric and radiation belt scientific community.

47 OTHER INSTRUMENTATION↗
NASA NTRS1994

Re-engineering the Multimission Command System at the Jet Propulsion Laboratory

The Operations Engineering Lab (OEL) at JPL has developed the multimission command system as part of JPL's Advanced Multimission Operations System. The command system provides an advanced multimission environment for secure, concurrent commanding of multiple spacecraft. The command functions include real-time command generation, command translation and radiation, status reporting, some remote control of Deep Space Network antenna functions, and command file management. The mission-independent architecture has allowed easy adaptation to new flight projects and the system currently supports all JPL planetary missions (Voyager, Galileo, Magellan, Ulysses, Mars Pathfinder, and CASSINI). This paper will discuss the design and implementation of the command software, especially trade-offs and lessons learned from practical operational use. The lessons learned have resulted in a re-engineering of the command system, especially in its user interface and new automation capabilities. The redesign has allowed streamlining of command operations with significant improvements in productivity and ease of use. In addition, the new system has provided a command capability that works equally well for real-time operations and within a spacecraft testbed. This paper will also discuss new development work including a multimission command database toolkit, a universal command translator for sequencing and real-time commands, and incorporation of telecommand capabilities for new missions.

Alexander, Scott↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS2011

Ares Knowledge Capture: Summary and Key Themes Presentation

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 MSFC Chief Engineers Office. 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.

Ares Knowledge↗
NASA NTRS2010

TBCC TSTO Design for the NASA-AFRL Joint System Study

NASA and the Air Force Research Laboratory are involved in a Joint System Study (JSS) on Two-Stage-to-Orbit (TSTO) vehicles. The JSS will examine the performance, operability and uncertainty of unmanned, fully reusable, airbreathing-based TSTO launch vehicle concepts. NASA is providing a concept using turbine-based combined cycle (TBCC) propulsion on the booster stage and an all-rocket orbiter. The Air Force supplied two vehicle concepts, both utilizing an all-rocket booster; one with an all-rocket orbiter, the other using a rocket-based combined cycle orbiter. For NASA, this study is being used for tool assessment and development, and to identify generic technology gaps, not to choose vehicle types or concepts. This presentation starts with an overview of the major JSS ground rules and assumptions. Second, the NASA TSTO concept, Reusable Airbreathing Launch Vehicle - iteration B (RALV-B) is introduced, including its mission profile and, the vehicle (booster and orbiter) layout and packaging. The high speed propulsion concept is then briefly discussed, including the work performed and lessons learned. The low speed TBCC propulsion system is covered next in some detail. An overview for the low speed system is given; then its development is discussed (starting with initial layout and leading to more detailed analyses performed and results). The low speed system portion is wrapped up with lessons learned and summary. Finally, an overall summary and lessons learned so far for the JSS are given as well as work planned to complete the study.

Snyder, Christopher A.↗
NASA NTRSDate not supplied

Insights and Observations from Operating a Geostationary Laser Communication Relay Mission: Operational Lessons from NASA’s Laser Communications Relay Demonstration (LCRD) and Associated Optical Ground Stations (OGSs)

The NASA Laser Communications Relay Demonstration (LCRD) has operated on orbit for the last two years. The LCRD Mission consists of a geostationary payload and two optical ground stations. This technology demonstration mission is NASA’s first two-way, end-to-end optical communications relay. LCRD has performed an extensive experiment campaign to analyze laser communication performance for extended operations. This paper discusses various lessons learned while operating the optical relay mission from early commissioning through two years of operation. Before launch, engineers and operators performed analyses to generate operational procedures based on expected LCRD performance. However, only operation on orbit can supply actual performance data. Additional topics covered in this paper include pre-launch and commissioning testing, ephemeris generation and cadence, environmental configurations, and accommodation concerns. The addition of Integrated Laser Communications Relay Demonstration Low Earth Orbit User Modem and Amplifier Terminal (ILLUMA-T) to the optical network supplemented the LCRD team’s operational experiences and enabled them to garner new lessons learned. The authors of this paper include day-to-day flight leads who consulted with on-console operators, engineers, and subject matter experts analyzing data and experiment results to gather the lessons learned described in this paper. LCRD is a joint project involving NASA Goddard Space Flight Center (GSFC), the California Institute of Technology Jet Propulsion Laboratory (JPL), and Massachusetts Institute of Technology Lincoln Laboratory (MIT LL).

Lessons Learned↗
NASA NTRS2011

Accident Case Study of Organizational Silence Communication Breakdown: Shuttle Columbia, Mission STS-107

This report has been developed by the National Aeronautics and Space Administration (NASA) ESMD Risk and Knowledge Management team. This document provides a point-in-time, cumulative, summary of key lessons learned derived from the official Columbia Accident Investigation Board (CAIB). 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. This report is accompanied by a video that will be sent at request

Lessons Learned↗
NASA NTRS2017

Practical Applications of Cables and Ropes in the ISS Countermeasures System

National Aeronautics and Space Administration (NASA) uses exercise countermeasures on the International Space Station (ISS) to maintain crew health and combat the negative effects of long-duration spaceflight on the human body. Most ISS exercise countermeasures system (CMS) equipment rely heavily on the use of textile and wire ropes to transmit resistive loads and provide stability in a microgravity environment. For a variety of reasons, including challenges in simulating microgravity environments for testing and limits on time available for life cycle testing, the textiles and wire ropes have contributed significantly to on-orbit planned and unplanned maintenance time. As a result, continued ground testing and on-orbit experience since the first expedition on the ISS in 2000 provide valuable data and lessons learned in materials selection, applications, and design techniques to increase service life of these ropes. This paper will present a review of the development and failure history of textile and wire ropes for four exercise countermeasure systems-the Treadmill with Vibration Isolation and Stabilization (TVIS) System, Cycle Ergometer with Vibration Isolation and Stabilization (CEVIS) System, Interim Resistive Exercise Device (IRED), and the Advanced Resistive Exercise Device (ARED)-to identify lessons learned in order to improve future systems. These lessons learned, paired with thorough testing on the ground, offer a forward path towards reduced maintenance time and up-mass for future space missions.

Svetlik, Randall G.↗
DOE OSTI2020

Safety-Related Instrumentation & Control Pilot Upgrade Initiation Phase Implementation Report

This research report (1) describes the process followed and products developed during the SR I&C Pilot Project Initial Scoping Phase, and (2) captures lessons learned. Exelon Generation and LWRS collaborated to develop a Digital Transformation Strategy as part of a larger Advanced Concept of Operations. The proposed SR I&C Pilot Upgrade provides a foundation stone for this Digital Transformation that will improve plant safety, reliability, and operational performance while lowering plant Total Cost of Ownership (TCO). Initial Scoping Phase activities for this Pilot Project have been performed in accordance with industry processes that have been adapted to better support digital upgrades. These processes include IP-ENG-001, Standard Design Process (SDP) [Reference 2], NISP-EN-04, Standard Digital Engineering Process (SDEP) [Reference 3], and Electric Power Research Institute (EPRI) Report 3002011816, Digital Engineering Guide (DEG). Completing Initial Scoping Phase Engineering and Operations, Licensing, and Project Management Activities was necessary to sufficiently bound the scope, schedule, and estimated cost of the Project to enable utility management to authorize moving into the Conceptual Design Phase. A significant finding of the Business Case Analysis (BCA) methodology developed and applied as part of this effort was that the growth rate of material costs for sustaining the operation of obsolete SR I&C equipment is accelerating. This directly contributed to the Project Economic Analysis created to justify continuing the Project. Project Initial Scoping Phase lessons learned have also been captured to assist the larger industry in understanding the Digital Transformation Strategy and SR I&C Pilot Project Initial Scoping Phase efforts. This is in keeping with the public/private partnership that has been established between the Department of Energy (DOE) and Exelon for this effort with engagement from the NRC. By addressing first-of-a-kind (FOAK) risks and capturing lessons learned, the SR I&C Pilot Upgrade Project addresses technical, regulatory, and business risks to enable subsequent implementers of similar upgrades.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2020

Safety-Related Instrumentation and Control Pilot Upgrade (Initial Scoping Phase Implementation Report)

This research report (1) describes the process followed and products developed during the SR I&C Pilot Project Initial Scoping Phase, and (2) captures lessons learned. Exelon Generation and LWRS collaborated to develop a Digital Transformation Strategy as part of a larger Advanced Concept of Operations. The proposed SR I&C Pilot Upgrade provides a foundation stone for this Digital Transformation that will improve plant safety, reliability, and operational performance while lowering plant Total Cost of Ownership (TCO). Initial Scoping Phase activities for this Pilot Project have been performed in accordance with industry processes that have been adapted to better support digital upgrades. These processes include IP-ENG-001, Standard Design Process (SDP), NISP-EN-04, Standard Digital Engineering Process (SDEP), and Electric Power Research Institute (EPRI) Report 3002011816, Digital Engineering Guide (DEG). Completing Initial Scoping Phase Engineering and Operations, Licensing, and Project Management Activities was necessary to sufficiently bound the scope, schedule, and estimated cost of the Project to enable utility management to authorize moving into the Conceptual Design Phase. A significant finding of the Business Case Analysis (BCA) methodology developed and applied as part of this effort was that the growth rate of material costs for sustaining the operation of obsolete SR I&C equipment is accelerating. This directly contributed to the Project Economic Analysis created to justify continuing the Project. Project Initial Scoping Phase lessons learned have also been captured to assist the larger industry in understanding the Digital Transformation Strategy and SR I&C Pilot Project Initial Scoping Phase efforts. This is in keeping with the public/private partnership that has been established between the Department of Energy (DOE) and Exelon for this effort with engagement from the NRC. By addressing first-of-a-kind (FOAK) risks and capturing lessons learned, the SR I&C Pilot Upgrade Project addresses technical, regulatory, and business risks to enable subsequent implementers of similar upgrade.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS2023

The Trash Compaction Processing System (TCPS) Technology Demonstrations Science Objectives and Requirement Definitions

Throughout the Next STEP Phase A and Phase B, the Trash Compaction Processing System (TCPS) is being developed for a technology demonstration (TD) on the International Space Station (ISS) in 2025. For Phase A, two contractors built proof-of-concept hardware. One contractor was chosen to build the TD hardware for Phase B. Both Phase A lessons learned and risk reduction activities at Ames Research Center (ARC) were used to write the TD science objectives, scope, and requirements. The work at ARC aims to retire technical risks and provide design data to TCPS developers and the ISS system integrators. This paper will summarize the lessons learned from the proof-of-concept hardware, the risk reduction activities, and how these lessons learned form the basis of the TD requirement matrix.

TCPS↗
NASA NTRS2011

The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations

Operations of human spaceflight systems is extremely complex; therefore, the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center in Houston, Texas, manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. An overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified, reveals that while the training methodology for developing flight controllers has evolved significantly over the last thirty years the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. Changes in methodology and tools have been driven by many factors, including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers share their experiences in training and operating the space shuttle. The primary training method throughout the program has been mission simulations of the orbit, ascent, and entry phases, to truly train like you fly. A review of lessons learned from flight controller training suggests how they could be applied to future human spaceflight endeavors, including missions to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle.

Dittermore, Gary↗
NASA NTRS1988

Artificial intelligence costs, benefits, risks for selected spacecraft ground system automation scenarios

In response to a number of high-level strategy studies in the early 1980s, expert systems and artificial intelligence (AI/ES) efforts for spacecraft ground systems have proliferated in the past several years primarily as individual small to medium scale applications. It is useful to stop and assess the impact of this technology in view of lessons learned to date, and hopefully, to determine if the overall strategies of some of the earlier studies both are being followed and still seem relevant. To achieve that end four idealized ground system automation scenarios and their attendant AI architecture are postulated and benefits, risks, and lessons learned are examined and compared. These architectures encompass: (1) no AI (baseline), (2) standalone expert systems, (3) standardized, reusable knowledge base management systems (KBMS), and (4) a futuristic unattended automation scenario. The resulting artificial intelligence lessons learned, benefits, and risks for spacecraft ground system automation scenarios are described.

Truszkowski, Walter F.↗
NASA NTRS1988

Artificial intelligence costs, benefits, and risks for selected spacecraft ground system automation scenarios

In response to a number of high-level strategy studies in the early 1980s, expert systems and artificial intelligence (AI/ES) efforts for spacecraft ground systems have proliferated in the past several years primarily as individual small to medium scale applications. It is useful to stop and assess the impact of this technology in view of lessons learned to date, and hopefully, to determine if the overall strategies of some of the earlier studies both are being followed and still seem relevant. To achieve that end four idealized ground system automation scenarios and their attendant AI architecture are postulated and benefits, risks, and lessons learned are examined and compared. These architectures encompass: (1) no AI (baseline); (2) standalone expert systems; (3) standardized, reusable knowledge base management systems (KBMS); and (4) a futuristic unattended automation scenario. The resulting artificial intelligence lessons learned, benefits, and risks for spacecraft ground system automation scenarios are described.

Truszkowski, Walter F.↗