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 469 records · Page 26

Lessons Learned: Using UTM paradigm for Urban Air Mobility Operations

Urban Air Mobility (UAM) aims to reduce congestion on the roads and highways by offering air taxi as an alternative to driving on surface roads. Integration of UAM operations in the National Airspace System (NAS) has been the focus of the research conducted at NASA Ames Research Center. A simulation was performed in collaboration with Uber Technologies Inc to investigate if NASA’s UTM architecture and its implementation as demonstrated in the 2019 UTM field tests were extensible for UAM operations, and if the data exchange between multiple operators as planned under UTM were adequate for UAM operations in the shared airspace. In order to explore these research questions, three Use Cases were defined to investigate different airspace management challenges. This paper will describe the lessons learned from exercising the uses cases and the airspace management services including scheduling and separation developed to facilitate initial UAM operations.

Urban Air Mobility↗

LCLS-II Cryomodules Production Experience and Lessons Learned Towards LCLS-II-HE Project

LCLS-II is an upgrade project for the linear coherent light source (LCLS) at SLAC. The LCLS-II linac consists of thirty-five 1.3 GHz and two 3.9 GHz superconducting RF (SRF) continuous wave (CW) cryomodules with high quality factor cavities. Cryomodules were produced at Fermilab and at Jefferson Lab in collaboration with SLAC. Fermilab successfully completed the assembly, testing and delivery of seventeen 1.3 GHz and three 3.9 GHz cryomodules. LCLS-II-HE is a planned upgrade project to LCLS-II. The LCLS-II-HE linac will consist of twenty-three 1.3 GHz cryomodules with high gradient and high quality factor cavities. This paper presents LCLS-II-HE cryomodule production plans, emphasizing the improvements done based on the challenges, mitigations, and lessons learned from LCLS-II.

43 PARTICLE ACCELERATORS↗

Lessons Learned from SMAP Radiometer Pre-/Post-launch Calibration

The Soil Moisture Active Passive(SMAP) mission was launched on 31stJanuary 2015 in a 6 AM/ 6 PM sun-synchronous orbit at 685 km altitude to measure soil moisture and free/thaw globally [1]. The passive instrument of SMAP is a fully polarimetric L-band radiometer (1.4GHz) operating with a bandwidth of 24MHz. The radiometer uses a combination of noise-diodes and Dicke-loads for internal calibration with a design similar to that used by the Aquarius or Jason series radiometers[2,3].Pre-launch calibration activities had been performed since 2012on the engineering model of the radiometer. Post-launch calibration activities have been performed to fine-tune and validate the results from the pre-launch calibration. The major calibration activities and lessons learned in the past 8 years will be described in the following sections.

Jinzheng Peng↗

Lessons learned from the introduction of autonomous monitoring to the EUVE science operations center

The University of California at Berkeley's (UCB) Center for Extreme Ultraviolet Astrophysics (CEA), in conjunction with NASA's Ames Research Center (ARC), has implemented an autonomous monitoring system in the Extreme Ultraviolet Explorer (EUVE) science operations center (ESOC). The implementation was driven by a need to reduce operations costs and has allowed the ESOC to move from continuous, three-shift, human-tended monitoring of the science payload to a one-shift operation in which the off shifts are monitored by an autonomous anomaly detection system. This system includes Eworks, an artificial intelligence (AI) payload telemetry monitoring package based on RTworks, and Epage, an automatic paging system to notify ESOC personnel of detected anomalies. In this age of shrinking NASA budgets, the lessons learned on the EUVE project are useful to other NASA missions looking for ways to reduce their operations budgets. The process of knowledge capture, from the payload controllers for implementation in an expert system, is directly applicable to any mission considering a transition to autonomous monitoring in their control center. The collaboration with ARC demonstrates how a project with limited programming resources can expand the breadth of its goals without incurring the high cost of hiring additional, dedicated programmers. This dispersal of expertise across NASA centers allows future missions to easily access experts for collaborative efforts of their own. Even the criterion used to choose an expert system has widespread impacts on the implementation, including the completion time and the final cost. In this paper we discuss, from inception to completion, the areas where our experiences in moving from three shifts to one shift may offer insights for other NASA missions.

Lewis, M.↗

Space Mechanisms Lessons Learned and Accelerated Testing Studies

A number of mechanism (mechanical moving component) failures and anomalies have recently occurred on satellites. In addition, more demanding operating and life requirements have caused mechanism failures or anomalies to occur even before some satellites were launched (e.g., during the qualification testing of GOES-NEXT, CERES, and the Space Station Freedom Beta Joint Gimbal). For these reasons, it is imperative to determine which mechanisms worked in the past and which have failed so that the best selection of mechanically moving components can be made for future satellites. It is also important to know where the problem areas are so that timely decisions can be made on the initiation of research to develop future needed technology. To chronicle the life and performance characteristics of mechanisms operating in a space environment, a Space Mechanisms Lessons Learned Study was conducted. The work was conducted by the NASA Lewis Research Center and by Mechanical Technologies Inc. (MTI) under contract NAS3-27086. The expectation of the study was to capture and retrieve information relating to the life and performance of mechanisms operating in the space environment to determine what components had operated successfully and what components had produced anomalies.

Fusaro, Robert L.↗

Challenges and Lessons Learned in the Application of Autonomy to Space Operations

NASA's Space Operations Management Office (SOMO) is working toward a goal of providing an integrated infrastructure of mission and data services for space missions undertaken by NASA enterprises. A significant portion of this effort is focused on reducing the cost of these services. We are interested in the potential of autonomy to reduce operations costs. SOMO services support space missions, but are not part of the mission objectives; therefore the level of acceptable risk is very low. In fact, SOMO could be effective ly prevented from applying autonomy if customers merely perceive it as adding risk to their mission(s). We are interested in this workshop from the standpoint of understanding what can be done to realize the potential cost savings due to autonomy while maintaining acceptable risk and serving the needs of our customers. We would like to present our lessons learned so far in adopting autonomy and automation, which we think will contribute to clarifying the challenges facing the use of such technology. SOMO provides services to a diverse and ambitious set of mission customers. Many of these missions are groundbreaking missions for which communications, data, and other operations requirements sometimes cannot be clearly articulated early in the program. This motivates a need for systems that are robust in the face of unanticipated situations so that customer missions are not unreasonably constrained or impacted by "shortcomings" in SOMO services. One of SOMO's primary goals is to realize a paradigm in which SOMO acts as a service provider to organizations that fly space missions for NASA, other government agencies, and even the commercial sector. These organizations purchase SOMO services "by the pound" as customers. We have to provide systems that are not experiments themselves, but rather stable bases from which to do bold experiments. To this end, SOMO also seeks to work closely with industry to see that robust autonomy technology gets infused into products and services for the space industry and beyond. The potential for application of these technologies spans space-based communications networks (e.g. TDRSS) and ground-based assets including communication and tracking antenna systems, data networks, and control centers. There are several problems that are candidates for the application of autonomy, if it can be made reliable enough, including: antenna control, antenna scheduling, communication link scheduling and operation, navigation, attitude determination, fault detection, isolation, and reconfiguration (for spacecraft or ground assets), and mission-level planning and scheduling. Some attempts have been made to apply autonomy and automation in these areas in the past with varying degrees of success. We will present relevant case histories and the lessons inferred from them. Combining this past experience with anticipated future needs, we can clarify the challenges that must be met in order to realize the benefits of autonomy.

Forrest, David J.↗

Partnering with Industry: Lessons Learned from the Wide Field Instrument on the Wide Field InfraRed Survey Telescope Mission

Through most of the project formulation prior to Phase A, the Wide Field InfraRed Survey Telescope (WFIRST) project was developed as a Goddard Space Flight Center (GSFC) in house mission with one secondary instrument developed by JPL and an existing telescope donated from elsewhere in the federal government and managed by the original industry vendor. GSFC was responsible for the spacecraft bus, the instrument supporting structure and the Wide Field Instrument (WFI), which provides the primary science for the mission. Shortly before the beginning of Phase A, NASA codified its acquisition strategy for WFIRST to explore a more substantial role for industry in the mission. The project decided to have a large portion of the WFI be co-developed by industry. This paper describes lessons learned and recommendations for bringing potential industry partners into a project at later stages of conceptual design and presents viewpoints from both the vendor and customer on the experience with WFIRST.

Peabody,Hume L.↗

Gateway to the Future: Lessons Learned in Development of the Refueling Systems for NASA's First Lunar Space Station

Developed in collaboration with international and commercial partners, Gateway will be humanity’s first space station around the Moon as a vital component of NASA’s deep space exploration plans to the Moon, Mars and beyond. As part of it’s focus on developing a sustainable, long term lunar capability, both it’s Xenon based Solar Electric Propulsion System, as well as it’s bi-propellant Reaction Control System of the Gateway are designed to be on-orbit refuellable. Through design studies, numerical modeling, hardware development, and early testing, the system architecture has undergone significant changes to meet mission requirements and utilize evolving hardware capabilities between concept formulation and it’s successful completion of it’s Critical Design Review. This paper presents key lessons learned during this process, highlighting specific design elements and test results that contribute to a robust and adaptable refueling system for the Gateway.

Christopher Radke↗

Technical Oversight of the Nancy Grace Roman Space Telescope Optical Telescope Assembly (OTA) Element Procurement: Opportunities, Challenges, & Lessons Learned (2024 Update)

Nancy Grace Roman Space Telescope Optical Telescope Assembly (OTA) is an out-of-house procurement from L3Harris currently being integrated and tested in Rochester, NY. Building upon L3Harris’s decades of success producing world-class optical systems for government and commercial customers offers NASA a proven partner and a tremendous opportunity for high performance and value. Inheriting significant portions of the telescope (including the primary and secondary mirror, composite metering structures and alignment drives) from a previous program presents the opportunity to save cost and schedule but constrains the design space for the unique challenges of the Roman mission. This seminar will cover a brief description of the OTA and its history, some of the challenges posed by incorporating an established product line and inherited hardware into a Class A mission, and some approaches and lessons learned that may be helpful for those structuring new missions or providing technical oversight of out-of-house procurements.

Joshua Abel↗

Staffing the ISS Control Centers: Lessons Learned from Long-Duration Human Space Flight

The International Space Station (ISS) has been in operation with a permanent human presence in space for over five years, and plans for continued operations stretch ten years into the future. Ground control and support operations are, likewise, a 15-year enterprise. This long-term, 24-hour per day, 7 day per week support has presented numerous challenges in the areas of ground crew training, initial and continued certification, and console staffing. The Mission Control Center in Houston, Texas and the Payload Operations Center in Huntsville, Alabama have both tackled these challenges, with similar, yet distinct, approaches. This paper describes the evolution of the staffing and training policies of both control centers in a chronological progression. The relative merits and shortcomings of the various policies employed are discussed and a summary of "lessons learned" is presented. Finally, recommendations are made as best practices for future long-term space missions.

Olsen, Carrie D.↗

Project Interface Requirements Process Including Shuttle Lessons Learned

Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings

Bauch, Garland T.↗

Constellation Program Design Challenges as Opportunities for Educational Outreach- Lessons Learned

The Texas Space Grant Consortium (TSGC) and the NASA Exploration Systems Mission Directorate (ESMD) Education Office both have programs that present design challenges for university senior design classes that offer great opportunities for educational outreach and workforce development. These design challenges have been identified by NASA engineers and scientists as actual design problems faced by the Constellation Program in its exploration missions and architecture. Student teams formed in their senior design class select and then work on a design challenge for one or two semesters. The senior design class follows the requirements set by their university, but it must also comply with the Accreditation Board for Engineering and Technology (ABET) in order to meet the class academic requirements. Based on a one year fellowship at a TSGC university under the NASA Administrator's Fellowship Program (NAFP) and several years of experience, lessons learned are presented on the NASA Design Challenge Program.

Trevino, Robert C.↗

Constellation Program Lessons Learned in the Quantification and Use of Aerodynamic Uncertainty

The NASA Constellation Program has worked for the past five years to develop a re- placement for the current Space Transportation System. Of the elements that form the Constellation Program, only two require databases that define aerodynamic environments and their respective uncertainty: the Ares launch vehicles and the Orion crew and launch abort vehicles. Teams were established within the Ares and Orion projects to provide repre- sentative aerodynamic models including both baseline values and quantified uncertainties. A technical team was also formed within the Constellation Program to facilitate integra- tion among the project elements. This paper is a summary of the collective experience of the three teams working with the quantification and use of uncertainty in aerodynamic environments: the Ares and Orion project teams as well as the Constellation integration team. Not all of the lessons learned discussed in this paper could be applied during the course of the program, but they are included in the hope of benefiting future projects.

Walker, Eric L.↗

System Identification of Flexible Aircraft: Lessons Learned from the X-56A Phase 1 Flight Tests

The X-56A Multi-Utility Technology Testbed (MUTT) is a subscale airplane that was de-signed as an experimental flight research platform for improving aeroelastic modeling and control technologies. The Phase 1 flight tests, conducted from 2017 to 2019 at the NASA Arm-strong Flight Research Center (AFRC), included 39 flights and approximately 1000 research maneuvers, some of which demonstrated stable closed-loop flight beyond the open-loop flutter speed. This paper summarizes the system identification effort to extract nondimensional stability and control derivatives from the flight test data for constructing aeroelastic models of the flight dynamics. Topics discussed include instrumentation, experiment design, model postulation and reduction, parameter estimation, and others. Throughout the paper, unique challenges for the identification of flexible aircraft, practical aspects of the analysis, and lessons learned are presented.

Jared A Grauer↗

The International Space Station (ISS) Solar Alpha Rotary Joint (SARJ): Materials & Processes (M&P) Lessons Learned for a Large, Spacecraft Rotating Mechanism

The ISS utilizes two large rotating mechanisms, the SARJ, as part of the solar arrays alignment system for more efficient power generation. The SARJ is a 10.3m circumference, nitrided 15-5PH steel race ring of triangular cross-section, with 12 sets of trundle bearing assemblies transferring load across the rolling joint. The SARJ mechanism rotates continuously and slowly - once every orbit, or every 90 minutes. In 2008, the starboard SARJ suffered a lubrication failure, resulting in severe damage (spalling) of one of the race ring surfaces. Extensive effort was conducted to prevent the port SARJ from suffering the same failure, and fortunately was ultimately successful in recovering the functionality of the starboard SARJ. The M&P function was key in determining the cause of failure and the means for mechanism recovery. From a M&P lessons-learned perspective, observations are made concerning the original SARJ design parameters (boundary conditions), the perceived need for nitriding the race ring, the test conditions employed during qualification, the environmental controls used for the hardware preflight, and the lubrication robustness necessary for complex kinematic mechanisms expecting high-reliability and long-life.

Golden, Johnny L.↗

Lessons learned supporting onboard solid-state recorders

With the advance of semiconductor technology, Solid-State Recorders (SSR) have matured and been accepted as primary onboard data storage devices. Their high reliability, simpler interface and control, and high flexibility have made the SSR's a superb choice in today's spacecraft design. While there are many benefits, the use of SSR's may also add significant complexity to ground data systems. For instance, real-time and playback data may be interleaved into the same data stream, making data sequencing and time ordering difficult. Stored data may be played back out of time order, increasing processing load significantly. Data may also be played back after being sorted by Virtual Channels in the SSR, potentially creating bursts in packet rates that exceed the real-time processing capabilities of the ground systems. This paper presents a summary of lessons learned through the efforts in supporting a number of NASA's missions that employ SSR's. It describes various problems encountered through the design process, and their potential impact on ground system performance, resources, and cost. Recommended approaches to minimizing the impact are demonstrated by examples. The discussion leads to the conclusion that the use of SSR's demands an even higher level of cooperation between spacecraft and ground system designers in order to build the most cost effective end-to-end system.

Shi, Jeff↗

Lessons Learned from Recent Testing in the Nuclear Thermal Rocket Element Environmental Simulator

The Nuclear Thermal Rocket Element Environmental Simulator (NTREES) facility is designed to perform realistic non-nuclear testing of nuclear thermal rocket (NTR) fuel elements and fuel materials. Although the NTREES facility cannot reproduce the neutron and gamma environment of an operating NTR, it can simulate the thermal hydraulic environment within an NTR fuel element to provide critical information on material performance and compatibility. The NTREES facility is currently being reconfigured with an all new suite of pyrometers, a new coil and feedthrough design along with a new gas sampling system for the mass spectrometer. Also new is the ability to perform chamber purges using argon. All of these modifications are the result of experiences gained through several years of testing various NTR components under a wide range of operating conditions. The testing details and the lessons learned from those tests are discussed in this presentation.

Emrich, William J., Jr.↗

Habitability Lessons Learned from Field Testing of a Small Pressurized Rover

From 2008 to 2010, the NASA Small Pressurized Rover was tested in the Arizona desert in anticipation of human lunar surface missions. These tests were multi-day mission simulations with crew living in and conducting simulated lunar surface EVAs from the rover prototypes for 3, 7, or 14 days. This two-person surface spacecraft represents a departure from most previous lunar architectures, which either featured Apollo-class unpressurized rovers or large pressurized rovers – in some cases up to the scale of being considered mobile outposts. This paper will discuss the history of the Small Pressurized Rover, some of the values of field testing, the rover’s design evolution including the two prototypes tested in the field, key features and advantages of the SPR, the field test site location, the 2008, 2009, and 2010 field tests, habitability lessons learned from the testing, comparisons with follow-on laboratory/high bay testing, and recommendations for third generation rover design and flight vehicle development.

Pressurized Rover↗