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 559 records · Page 31

Medical Database Accomplishments and Lessons Learned - 2021

The Medical Database (MD) is a virtual repository consisting of two software components: the Medical Item Database (MedID) and the Evidence Library (EL). MedID consists of engineering data and associated information for specific medical resource items (e.g., pharmaceutical, medical devices, and supporting components), while the EL is a tool which provides all of the medical evidence necessary. The Medical Database will serve as the single “source of truth” for the Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) tool suite for both medical evidence and medical resource engineering data. It will be used in conjunction with the IMPACT tool suite to inform research prioritizations and perform systematic trade study evaluations using probabilistic risk assessment and simulated human spaceflight missions to aid stakeholders in making informed decisions during Pre-Phase-A planning of human spaceflight missions. The IMPACT project is conducted under the Exploration Medical Capability (ExMC) element of the Human Research Program (HRP), within NASA’s Human Exploration and Operations Mission Directorate. Over the past year, the MedID software has been successfully merged with the Evidence Library into one cohesive Medical Database with two independent user interface experiences for modifying either clinical evidence or resource engineering data. As MD has evolved substantially over the past year, a number of challenges have been encountered and overcome along the way. A number of ‘lessons learned’ and practical/logistical realizations have emerged which will be detailed in the forthcoming Medical Database presentation.

Exploration Medical Capability↗

Development of a State Machine Sequencer for the Keck Interferometer: Evolution, Development and Lessons Learned using a CASE Tool Approach

This paper presents a discussion of the evolution of a sequencer from a simple EPICS (Experimental Physics and Industrial Control System) based sequencer into a complex implementation designed utilizing UML (Unified Modeling Language) methodologies and a CASE (Computer Aided Software Engineering) tool approach. The main purpose of the sequencer (called the IF Sequencer) is to provide overall control of the Keck Interferometer to enable science operations be carried out by a single operator (and/or observer). The interferometer links the two 10m telescopes of the W. M. Keck Observatory at Mauna Kea, Hawaii. The IF Sequencer is a high-level, multi-threaded, Hare1 finite state machine, software program designed to orchestrate several lower-level hardware and software hard real time subsystems that must perform their work in a specific and sequential order. The sequencing need not be done in hard real-time. Each state machine thread commands either a high-speed real-time multiple mode embedded controller via CORB A, or slower controllers via EPICS Channel Access interfaces. The overall operation of the system is simplified by the automation. The UML is discussed and our use of it to implement the sequencer is presented. The decision to use the Rhapsody product as our CASE tool is explained and reflected upon. Most importantly, a section on lessons learned is presented and the difficulty of integrating CASE tool automatically generated C++ code into a large control system consisting of multiple infrastructures is presented.

interferometer↗

Kennedy Space Center's NASA/Contractor Team-Centered Total Quality Management Seminar: Results, methods, and lessons learned

It is apparent to everyone associated with the Nation's aeronautics and space programs that the challenge of continuous improvement can be reasonably addressed only if NASA and its contractors act together in a fully integrated and cooperative manner that transcends the traditional boundaries of proprietary interest. It is, however, one thing to assent to the need for such integration and cooperation; it is quite another thing to undertake the hard tasks of turning such a need into action. Whatever else total quality management is, it is fundamentally a team-centered and team-driven process of continuous improvement. The introduction of total quality management at KSC, therefore, has given the Center a special opportunity to translate the need for closer integration and cooperation among all its organizations into specific initiatives. One such initiative that NASA and its contractors have undertaken at KSC is a NASA/Contractor team-centered Total Quality Management Seminar. It is this seminar which is the subject of this paper. The specific purposes of this paper are to describe the following: Background, development, and evolution of Kennedy Space Center's Total Quality Management Seminar; Special characteristics of the seminar; Content of the seminar; Meaning and utility of a team-centered design for TQM training; Results of the seminar; Use that one KSC contractor, EG&G Florida, Inc. has made of the seminar in its Total Quality Management initiative; and Lessons learned.

Kinlaw, Dennis C.↗

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being reengineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEiX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the reengineering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team s experiences with integrating multiple missions into a fleet-based automated ground system.

Madden, Maureen↗

A Tale of Two Chambers: Iterative Approaches and Lessons Learned from Life Support Systems Testing in Altitude Chambers

The drive for the journey to Mars is in a higher gear than ever before. We are developing new spacecraft and life support systems to take humans to the Red Planet. The journey that development hardware takes before its final incarnation in a fully integrated spacecraft can take years, as is the case for the Orion environmental control and life support system (ECLSS). Through the Pressure Integrated Suit Test (PIST) series, NASA personnel at Johnson Space Center have been characterizing the behavior of a closed loop ECLSS in the event of cabin depressurization. This kind of testing - one of the most hazardous activities performed at JSC - requires an iterative approach, increasing in complexity and hazards). The PIST series, conducted in the Crew and Thermal Systems Division (CTSD) 11-ft Chamber, started with unmanned test precursors before moving to a human-in-the-loop phase, and continues to evolve with the eventual goal of a qualification test for the final system that will be installed on Orion. Meanwhile, the Human Exploration Spacecraft Testbed for Integration and Advancement (HESTIA) program is an effort to research and develop technologies that will work in concert to support habitation on Mars. September 2015 marked the first unmanned HESTIA test, with the goal of characterizing how ECLSS technologies work together in a closed environment. HESTIA will culminate in crewed testing, but it can benefit from the lessons learned from another test that is farther ahead in its development and life cycle. Discussing PIST and HESTIA, this paper illustrates how we approach testing, the kind of information that facility teams need to ensure efficient collaborations and successful testing, and how we can apply what we learn to execute future tests.

Callini, Gianluca↗

The Story Behind the Numbers: Lessons Learned from the Integration of Monitoring Resources in Addressing an ISS Water Quality Anomaly

Beginning in June of 2010 an environmental mystery was unfolding on the International Space Station (ISS). The U.S. Water Processor Assembly (WPA) began to produce water with increasing levels of total organic carbon (TOC). A surprisingly consistent upward TOC trend was observed through weekly in-flight total organic carbon analyzer (TOCA) monitoring. As TOC is a general organics indicator, return of water archive samples was needed to make better-informed crew health decisions and to aid in WPA troubleshooting. TOCA-measured TOC was more than halfway to its health-based screening limit before archive samples could be returned on Soyuz 22 and analyzed. Although TOC was confirmed to be elevated, somewhat surprisingly, none of the typical target compounds were the source. After some solid detective work, it was confirmed that the TOC was associated with a compound known as dimethylsilanediol (DMSD). DMSD is believed to be a breakdown product of silicon-containing compounds present on ISS. A toxicological limit was set for DMSD and a forward plan developed for operations given this new understanding of the source of the TOC. This required extensive coordination with ISS stakeholders and innovative use of available in-flight and archive monitoring resources. Behind the numbers and scientific detail surrounding this anomaly, there exists a compelling story of multi-disciplinary awareness, teamwork, and important environmental lessons learned.

McCoy, Torin↗

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

Madden, Maureen↗

Lessons Learned From Smallsat Microwave Sounders Data Assimilation in the NASA Goddard Earth Observing System (GEOS)

The NASA Time-Resolved Observations of Precipitation structure and storm Intensity with a Constellation of Smallsats (TROPICS) mission is a constellation of small satellites carrying state-of-art microwave temperature and humidity sounders with 12 channels between 91 GHz and 205 GHz frequency. Including TROPICS-pathfinder, launched on 30 June 2021, five TROPICS satellites operate and provide temperature and humidity data to NWP and atmospheric retrieval communities. This study evaluates the quality of radiance data from these five satellites. It assesses data impacts on NASA Goddard Earth Observing System (GEOS) global NWP analysis and forecasts while seeking answers to the following key questions: 1. What information do TROPICS satellites bring to NWP analysis? 2. How will TROPICS data assimilation affect NWP forecasts, including tropical cyclone analysis and forecasts? 3. What are the benefits of having multiple TROPICS satellites in NWP forecasts? 4. What are the weaknesses regarding instrument stability, consistency, and data quality of these CubeSats? 5. Can multiple TROPICS make similar impacts as conventional MW sensors such as ATMS or GPM Microwave Imager (GMI)? The sensitivities of each TROPICS channel to temperature, water vapor, cloud, and precipitation are examined in various weather conditions. Results from observing system experiments assimilating TROPICS radiance are used for evaluation metrics, including forecast skills and fit to other observations such as radiosondes and microwave and infrared sounders. Finally, the lessons learned from using these cube satellite radiance data in the GEOS atmospheric data assimilation system are shared.

Min-Jeong Kim↗

NextSTEP Appendix A Modular ECLSS Effort Lessons Learned

NASA’s Artemis program provides the first steps for earth-independent exploration starting with crewed habitats in cislunar space and progressing toward crewed landings on the lunar surface that will prepare systems and crews for the exploration of Mars. The Next Space Technology for Exploration Partnerships (NextSTEP) is a public-private partnership model that facilitates commercial development of deep space exploration capabilities in support of more extensive human spaceflight missions in and beyond cislunar space. NASA issued the original NextSTEP Broad Agency Announcement (BAA) to U.S. industry in late 2014 and issued the second BAA (NextSTEP-2) in April 2016. The first appendix under NextSTEP-2, Appendix A, focused on developing deep space habitation concepts, engineering design and development, and risk reduction efforts leading to a habitation capability in cislunar space. NASA solicited concepts to develop and refine the evolvable, modular architecture, functional allocation options, standards, and common interfaces required to enable interoperability of the aggregate system to provide long duration deep space transit habitation, specifically enhancements and testing of deep space Environmental Control and Life Support Systems (ECLSS). Collins Aerospace, formerly UTC Aerospace Systems (UTAS), was awarded a Phase 1 and subsequent Phase 2 contract to “develop concepts that group ECLS systems into logical modules maximizing the use of common components and the development of unique methods and design concepts that support in-flight maintenance and repair for future exploration systems.” This paper summarizes the work accomplished under this effort, the lessons that can be applied to development of forthcoming habitation elements, and the gaps remaining to achieve a more resilient, maintainable, repairable and adaptable system capable of installation on a wide variety of habitat platforms. A primary accomplishment of this effort is the development and maturation of a modular palletization concept to enable standard rack interfaces, post-launch outfitting, and decoupling of structural supports that withstand launch environments from those needed for lower on-orbit loads in order to reduce installed mass and repurposing of panels within the habitat. In the course of the effort, Collins assessed numerous architecture trades, including the use of condensing and noncondensing heat exchangers, the ability of modular units to accommodate various habitat volumes and thermal loading, and the most appropriate order of and timing of delivery of regenerative ECLSS hardware to orbital habitats. In addition to the modularity of hardware elements, Collins developed software approaches for distributed/modular command, control, and communication systems and innovative Bayesian fault detection and isolation techniques. Finally, the effort explored advanced maintainability and supportability concepts including the definition of maintenance units (MUs) in place of the traditional Orbital Replacement Units (ORUs), increasing parts commonality to reduce the number and type of spare parts, the use of augmented reality to guide crews during maintenance and repair procedures, and how crews would prepare for and recover from long durations of habitat dormancy. Now that the NextSTEP Modular ECLSS effort has come to a close, it’s important to identify the lessons learned and where they can be leveraged to improve NASA’s broader program of ECLSS technology development and demonstration and ultimately how they can increase the performance of future surface and orbital habitats.

NextSTEP↗

NextSTEP Appendix A Modular ECLSS Effort Lessons Learned

NASA’s Artemis program provides the first steps for earth-independent exploration starting with crewed habitats in cislunar space and progressing toward crewed landings on the lunar surface that will prepare systems and crews for the exploration of Mars. The Next Space Technology for Exploration Partnerships (NextSTEP) is a public-private partnership model that facilitates commercial development of deep space exploration capabilities in support of more extensive human spaceflight missions in and beyond cislunar space. NASA issued the original NextSTEP Broad Agency Announcement (BAA) to U.S. industry in late 2014 and issued the second BAA (NextSTEP-2) in April 2016. The first appendix under NextSTEP-2, Appendix A, focused on developing deep space habitation concepts, engineering design and development, and risk reduction efforts leading to a habitation capability in cislunar space. NASA solicited concepts to develop and refine the evolvable, modular architecture, functional allocation options, standards, and common interfaces required to enable interoperability of the aggregate system to provide long duration deep space transit habitation, specifically enhancements and testing of deep space Environmental Control and Life Support Systems (ECLSS). Collins Aerospace, formerly UTC Aerospace Systems (UTAS), was awarded a Phase 1 and subsequent Phase 2 contract to “develop concepts that group ECLS systems into logical modules maximizing the use of common components and the development of unique methods and design concepts that support in-flight maintenance and repair for future exploration systems.” This paper summarizes the work accomplished under this effort, the lessons that can be applied to development of forthcoming habitation elements, and the gaps remaining to achieve a more resilient, maintainable, repairable and adaptable system capable of installation on a wide variety of habitat platforms. A primary accomplishment of this effort is the development and maturation of a modular palletization concept to enable standard rack interfaces, post-launch outfitting, and decoupling of structural supports that withstand launch environments from those needed for lower on-orbit loads in order to reduce installed mass and repurposing of panels within the habitat. In the course of the effort, Collins assessed numerous architecture trades, including the use of condensing and noncondensing heat exchangers, the ability of modular units to accommodate various habitat volumes and thermal loading, and the most appropriate order of and timing of delivery of regenerative ECLSS hardware to orbital habitats. In addition to the modularity of hardware elements, Collins developed software approaches for distributed/modular command, control, and communication systems and innovative Bayesian fault detection and isolation techniques. Finally, the effort explored advanced maintainability and supportability concepts including the definition of maintenance units (MUs) in place of the traditional Orbital Replacement Units (ORUs), increasing parts commonality to reduce the number and type of spare parts, the use of augmented reality to guide crews during maintenance and repair procedures, and how crews would prepare for and recover from long durations of habitat dormancy. Now that the NextSTEP Modular ECLSS effort has come to a close, it’s important to identify the lessons learned and where they can be leveraged to improve NASA’s broader program of ECLSS technology development and demonstration and ultimately how they can increase the performance of future surface and orbital habitats.

NextSTEP↗

Lessons Learned from Open-Source Software Training Toward Expanding the Fusion Workforce

Within the United States (U.S.), the Fusion Innovation Research Engine (FIRE) Collaboratives seek to accelerate fusion technology development through wide-ranging community-driven research activities that bring together industry, laboratories, research institutes, and academia. Increasing the maturity of key components and systems for future fusion power plants (FPPs) toward commercialization, will, by necessity, increase the need for knowledgeable engineers, designers, and researchers in industry capable of integrating and further improving these technologies within industry FPP concepts. Further, various modeling and simulation packages support these programs and are under-development within them to drive design iteration and the development of FPP digital twins. To derive the greatest benefit from model output and capabilities, training these same specialists will be vital. Thus, the development of effective and accessible software onboarding and professional development opportunities focused on fusion will be key to keeping the pace of growth high in the coming decade and beyond. A similar need exists within the advanced fission reactor community, driven by an ever-growing need for carbon-free baseload power for industrial and data center applications. Within the U.S. and around the world, several open-source packages and frameworks exist to support this endeavor, and two we will highlight here are the Multiphysics Object Oriented Simulation Environment (MOOSE) framework and OpenMC. These packages, notably, are also being utilized in the FIRE Collaboratives program. In this presentation, we will highlight the lessons learned from over 30 years of combined software development and training experience, focused on developing strong technical software foundations within the nuclear workforce, from students to professional engineers & scientists. We will connect this experience to present and emerging needs in the fusion energy community, and, finally, will outline possible paths forward to develop a large, robust, global fusion workforce.

70 - PLASMA PHYSICS AND FUSION TECHNOLOGY↗

Project Morpheus: Lessons Learned in Lander Technology Development

NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing, that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. Designed, developed, manufactured and operated in-house by engineers at Johnson Space Center, the initial flight test campaign began on-site at JSC less than one year after project start. After two years of testing, including two major upgrade periods, and recovery from a test crash that caused the loss of a vehicle, flight testing will evolve to executing autonomous flights simulating a 500m lunar approach trajectory, hazard avoidance maneuvers, and precision landing, incorporating the Autonomous Landing and Hazard Avoidance (ALHAT) sensor suite. These free-flights are conducted at a simulated planetary landscape built at Kennedy Space Center's Shuttle Landing Facility. The Morpheus Project represents a departure from recent NASA programs and projects that traditionally require longer development lifecycles and testing at remote, dedicated testing facilities. This paper expands on the project perspective that technologies offer promise, but capabilities offer solutions. It documents the integrated testing campaign, the infrastructure and testing facilities, and the technologies being evaluated in this testbed. The paper also describes the fast pace of the project, rapid prototyping, frequent testing, and lessons learned during this departure from the traditional engineering development process at NASA's Johnson Space Center.

Olansen, Jon B.↗

A Step Towards the Final Frontier: Lessons Learned from Acceptance Testing of the First HPE/Cray EX 3000 System at ORNL

In this paper, we summarize the deployment of the Air Force Weather (AFW) HPC11 system at Oak Ridge National Laboratory (ORNL) including the process followed to successfully complete acceptance testing of the system. HPC11 is the first HPE/Cray EX 3000 system that has been successfully released to its user community in a federal facility. HPC11 consists of two identical 800-node supercomputers, Fawbush and Miller, with access to two independent and identical Lustre parallel file systems. HPC11 is equipped with Slingshot 10 interconnect technology and relies on the HPE Performance Cluster Manager (HPCM) software for system configuration. ORNL has a clearly defined acceptance testing process used to ensure that every new system deployed can provide the necessary capabilities to support user workloads. We worked closely with HPE and AFW to develop a set of tests that used the United Kingdom’s Meteorological Office’s Unified Model (UM) and 4DVAR. We also included benchmarks and applications from the Oak Ridge Leadership Computing Facility (OLCF) portfolio to fully exercise the HPE/Cray programming environment and evaluate the functionality and performance of the system. Acceptance testing of HPC11 required parallel execution of each element on Fawbush and Miller. In addition, careful coordination was needed to ensure successful acceptance of the newly deployed Lustre file systems alongside the compute resources. In this work, we present test results from specific system components and provide an overview of the issues identified, challenges encountered, and the lessons learned along the way.

Melesse Vergara, Veronica↗

A step towards the final frontier: Lessons learned from acceptance testing of the first HPE/Cray EX 3000 system at ORNL

Summary In this article, we summarize the deployment of the Air Force Weather (AFW) HPC11 system at Oak Ridge National Laboratory (ORNL) including the process followed to successfully complete acceptance testing of the system. HPC11 is the first HPE/Cray EX 3000 system that has been successfully released to its user community in a federal facility. HPC11 consists of two identical 800‐node supercomputers, Fawbush and Miller, with access to two independent and identical lustre parallel file systems. HPC11 is equipped with Slingshot 10 interconnect technology and relies on the HPE Performance Cluster Manager software for system configuration. ORNL has a clearly defined acceptance testing process used to ensure that every new system deployed can provide the necessary capabilities to support user workloads. We worked closely with HPE and AFW to develop a set of tests that used the United Kingdom's Meteorological Office's Unified Model and 4‐dimensional variational data assimilation. We also included benchmarks and applications from the Oak Ridge Leadership Computing Facility portfolio to fully exercise the HPE/Cray programming environment and evaluate the functionality and performance of the system. Acceptance testing of HPC11 required parallel execution of each element on Fawbush and Miller. In addition, careful coordination was needed to ensure successful acceptance of the newly deployed lustre file systems alongside the compute resources. In this work, we present test results from specific system components and provide an overview of the issues identified, challenges encountered, and the lessons learned along the way.

Melesse Vergara, Verónica G.↗

Lessons Learned in Launching Ares I-X

The Ares I-X flight test, scheduled for 2009, is the first opportunity for the Constellation Program and Ares Projects to obtain important data on the in-flight loads, first stage recovery, and ground-handling characteristics of the Ares I crew launch vehicle. The flight test vehicle will incorporate a mix of flight and mockup hardware, reflecting an acceptable representation of the mass and outer mold line characteristics of the operational Ares I vehicle. It will be powered by a four-segment solid rocket motor from the Space Shuttle inventory and will include a fifth, inert spacer segment and new forward structures to make it the same shape as the Ares I first stage. The vehicle also includes mass simulators for the upper stage, Orion crew module, and launch abort system to match the outer mold line of Ares I; an active roll control system; and avionics derived from Shuttle and Atlas hardware. This suborbital mission will take the flight test vehicle from stacking in the Vehicle Assembly Building (VAB) at Kennedy Space Center (KSC) through liftoff, maximum dynamic pressure, first stage separation, and recovery. Ares I-X presented NASA with unique project management challenges. This presentation will address those unique challenges, including managing a virtual nationwide team under a constrained timeline; designing and building the launch vehicle and ground systems; working concurrently with Space Shuttle activities; and integrating technical and management functions. It also will identify key data collected and lessons learned from the flight that will be applied to future exploration missions.

Davis, Stephan R.↗

CloudSat Anomaly Recovery and Operational Lessons Learned

In April 2011, NASA's pioneering cloud profiling radar satellite, CloudSat, experienced a battery anomaly that placed it into emergency mode and rendered it operations incapable. All initial attempts to recover the spacecraft failed as the resultant power limitations could not support even the lowest power mode. Originally part of a six-satellite constellation known as the "A-Train", CloudSat was unable to stay within its assigned control box, posing a threat to other A-Train satellites. CloudSat needed to exit the constellation, but with the tenuous power profile, conducting maneuvers was very risky. The team was able to execute a complex sequence of operations which recovered control, conducted an orbit lower maneuver, and returned the satellite to safe mode, within one 65 minute sunlit period. During the course of the anomaly recovery, the team developed several bold, innovative operational strategies. Details of the investigation into the root-cause and the multiple approaches to revive CloudSat are examined. Satellite communication and commanding during the anomaly are presented. A radical new system of "Daylight Only Operations" (DO-OP) was developed, which cycles the payload and subsystem components off in tune with earth eclipse entry and exit in order to maintain positive power and thermal profiles. The scientific methodology and operational results behind the graduated testing and ramp-up to DO-OP are analyzed. In November 2011, the CloudSat team successfully restored the vehicle to consistent operational collection of cloud radar data during sunlit portions of the orbit. Lessons learned throughout the six-month return-to-operations recovery effort are discussed and offered for application to other R&D satellites, in the context of on-orbit anomaly resolution efforts.

cloud profiling radar satellite↗

Lessons Learned During TBCC 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 analysis uncertainty of unmanned, fully reusable, TSTO launch vehicle concepts. NASA is providing a vehicle concept using turbine-based combined cycle (TBCC) propulsion on the booster stage and an all-rocket orbiter. The variation in vehicle and mission requirements for different potential customers, combined with analysis uncertainties, make it problematic to define optimum vehicle types or concepts, but the study is being used by NASA for tool assessment and development, and to identify technology gaps. Preliminary analyses were performed on the entire TBCC booster concept; then higher-fidelity analyses were performed for particular areas to verify results or reduce analysis uncertainties. Preliminary TBCC system analyses indicated that there would be sufficient thrust margin over its mission portion. The higher fidelity analyses, which included inlet and nozzle performance corrections for significant area mismatches between TBCC propulsion requirements versus the vehicle design, resulted in significant performance penalties from the preliminary results. TBCC system design and vehicle operation assumptions were reviewed to identify items to mitigate these performance penalties. The most promising items were then applied and analyses rerun to update performance predictions. A study overview is given to orient the reader, quickly focusing upon the NASA TBCC booster and low speed propulsion system. Details for the TBCC concept and the analyses performed are described. Finally, a summary of "Lessons Learned" are discussed with suggestions to improve future study efforts.

Snyder, Christopher A.↗

Lessons Learned from the Space Shuttle Engine Hydrogen Flow Control Valve Poppet Breakage

The Main Propulsion System (MPS) uses three Flow Control Valves (FCV) to modulate the flow of pressurant hydrogen gas from the Space Shuttle Main Engines (SSME) to the hydrogen External Tank (ET). This maintains pressure in the ullage volume as the liquid level drops, preserving ET structural integrity and assuring the engines receive a sufficient amount of head pressure. On Space Transportation System (STS)-126 (2009), with only a handful of International Space Station (ISS) assembly flights from the end of the Shuttle program, a portion of a single FCV?s poppet head broke off at about a minute and a half after liftoff. The risk of the poppet head failure is that the increased flow area through the FCV could result in excessive gaseous hydrogen flow back to the external tank, which could result in overboard venting of hydrogen ullage pressure. If the hydrogen venting were to occur in first stage (i.e., lower atmosphere), a flammability hazard exists that could lead to catastrophic loss of crew and vehicle. Other failure risks included particle impact damage to MPS downstream hardware. Although the FCV design had been plagued by contamination-related sluggish valve response problems prior to a redesign at STS-80 (1996), contamination was ruled out as the cause of the STS-126 failure. Employing a combination of enhanced hardware inspection and a better understanding of the consequences of a poppet failure, safe flight rationale for subsequent flights (STS-119 and later) was achieved. This paper deals with the technical lessons learned during the investigation and mitigation of this problem at a time when assembly flights were each in the critical path to Space Station success.

Martinez, Hugo E.↗