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 361 records · Page 20

Integration and Test (I&T) Horror Stories and the Lessons Learned

I've been asked to be a presenter along with a panel of fellow NASA Electromagnetic Compatibility (EMC) engineers at this year's IEEE EMC & Signal and Power Integrity (SIPI) 2019 symposium. The topic I am asked to cover is in regards to I&T horror stories because of my 15 years of personal experience as an EMC test engineer with Code 549. I am planning on only having slides with photos of test methods we no longer use as well as cover some mishaps that have happened over the years both within my organization and throughout the space industry. Highlighting the mistakes that were made, the lessons learned from those incidents and how they've effected how we test today.

EMI↗

Shuttle Shortfalls and Lessons Learned for the Sustainment of Human Space Exploration

Much debate and national soul searching has taken place over the value of the Space Shuttle which first flew in 1981 and which is currently scheduled to be retired in 2010. Originally developed post-Saturn Apollo to emphasize affordability and safety, the reusable Space Shuttle instead came to be perceived as economically unsustainable and lacking the technology maturity to assure safe, routine access to low earth orbit (LEO). After the loss of two crews, aboard Challenger and Columbia, followed by the decision to retire the system in 2010, it is critical that this three decades worth of human space flight experience be well understood. Understanding of the past is imperative to further those goals for which the Space Shuttle was a stepping-stone in the advancement of knowledge. There was significant reduction in life cycle costs between the Saturn Apollo and the Space Shuttle. However, the advancement in life cycle cost reduction from Saturn Apollo to the Space Shuttle fell far short of its goal. This paper will explore the reasons for this shortfall. Shortfalls and lessons learned can be categorized as related to design factors, at the architecture, element and sub-system levels, as well as to programmatic factors, in terms of goals, requirements, management and organization. Additionally, no review of the Space Shuttle program and attempt to take away key lessons would be complete without a strategic review. That is, how do national space goals drive future space transportation development strategies? The lessons of the Space Shuttle are invaluable in all respects - technical, as in design, program-wise, as in organizational approach and goal setting, and strategically, within the context of the generational march toward an expanded human presence in space. Beyond lessons though (and the innumerable papers, anecdotes and opinions published on this topic) this paper traces tangible, achievable steps, derived from the Space Shuttle program experience, that must be a part of any 2l century initiatives furthering a growing human presence beyond earth.

Zapata, Edgar↗

LAADS DAAC Migrates to the Cloud: Lessons Learned from Communicating About Earth Science Data on the Cloud

The Level-1 and Atmosphere Archive Distribution System (LAADS) Distributed Active Archive Center (DAAC) is migrating data to the cloud. As one of twelve DAACS supported by NASA’s Earth Science Data and Information System (ESDIS), LAADS is using moving away from on premise data storage facilities to migrating to Amazon Web Services, where the massive archive of data from the Moderate Imaging Spectroradiometer (MODIS) and the Visible Infrared Imaging Radiometer Suite (VIIRS) will be available for download and post-processing transformations online. The migration is happening in three phases and LAADS is concluding its beta testing period. This poster shows the lessons learned from communicating with a select group of users about how to effectively educate data users on using data in the cloud.

Tassia Owen↗

Lessons learned from and the future for NASA's Small Explorer Program

NASA started the Small Explorer Program to provide space scientists with an opportunity to conduct space science research in the Explorer Program using scientific payloads launched on small-class expendable launch vehicles. A series of small payload, scientific missions was envisioned that could be launched at the rate of one to two missions per year. Three missions were selected in April 1989: Solar Anomalous and Magnetospheric Particle Explorer, Fast Auroral Snapshot Explorer, and Sub-millimeter Wave Astronomy. These missions are planned for launch in June 1992, September 1994 and June 1995, respectively. At a program level, this paper presents the history, objectives, status, and lessons learned which may be applicable to similar programs, and discusses future program plans.

Newton, George P.↗

Behavioral Health Factors in Long Duration Space Flight: Lessons Learned From Apollo And Their Implications For Artemis

Behavioral health will be a critical factor in future Long Duration Spaceflights (LDSF). As humans venture further from Earth, astronauts will face greater isolation and need to be more autonomous than ever before. Astronauts will face a plethora of stressors, both internally and externally, and it will be mission critical to optimize their mind and bodies to endure and overcome these challenges. Personalities, environmental and physical factors will affect each individual and crew in different ways and it will be important to look at these factors independently and as a whole to maximize the chances of a successful mission. By analyzing environments analogous to space and building upon the lessons learned from the Apollo missions and over 50 years of Low Earth Orbit spaceflight, we hypothesize that a general framework can be developed to optimize crew mental wellbeing.

Nicolas Heft↗

Phase III integrated water recovery testing at MSFC - Partially closed hygiene loop and open potable loop results and lessons learned

A series of tests has been conducted at the NASA Marshall Space Flight Center (MSFC) to evaluate the performance of a predevelopment water recovery system. Potable, hygiene, and urine reclamation subsystems were integrated with end-use equipment items and successfully operated in open and partially closed-loop modes, with man-in-the-loop, for a total of 28 days. Several significant subsystem physical anomalies were encountered during testing. Reclaimed potable and hygiene water generally met the current Space Station Freedom (SSF) water quality specifications for inorganic and microbiological constituents, but exceeded the maximum allowable concentrations for Total Organic Carbon (TOC). This paper summarizes the test objectives, system design, test activities/protocols, significant results/anomalies, and major lessons learned.

Bagdigian, R. M.↗

Medical Challenges of the First Canadian Long-Duration Space Mission: Lessons Learned

In 2008, Dr. Thirsk was assigned to the crew of Expedition 20/21. This Expedition represented a milestone for the Canadian Space Program since it was the first time that a Canadian would take part in a long-duration mission. Robert Thirsk had the privilege of expanding the boundaries of space exploration by living and working on board the International Space Station for six months. The launch took place on May 27, 2009 aboard a Soyuz rocket from the Cosmodrome in Baikonur, Kazakhstan. This abstract was written before Dr. Thirsk returned to Kazakhstan. Objective: To gather all medically relevant data needed to support the first Canadian long-duration mission in space, and process it to derive lessons learned for presentation and for public disclosure. Methods: Sources of data used for analysis for Expedition 20 on International Space Station included flight selection data, maintenance annual physicals, Flight Medicine Clinic visits, parabolic flight experiments, preflight exams and baseline data collections, daily in-flight exercise countermeasure and science payloads, weekly periodic fitness, nutrition, radiation and payload assessments, postflight medical exams, rehabilitation, and science activities.

Hamilton, Douglas R.↗

Compass Concurrent Engineering Lessons Learned in Remote and Hybrid Environments

The Compass Team at NASA’s Glenn Research Center (GRC) is a concurrent engineering team which specializes in conceptual spacecraft mission designs. Detailed descriptions of the team, its history, and its operating model can be found in [1] and [2]. During the COVID-19 pandemic, the team was required to move to remote (virtual) operation from their in-person model for approximately 22 months. As the restrictions began to lift and team members were able to return in-person to the Compass Lab, the team moved into a hybrid mode of operation, with some participants still tying in remotely some or all of the time. This paper discusses many of the lessons learned from these experiences, highlighting improvements, outstanding challenges and the tools and methodologies used to address both. Throughout this discussion the terms “in-person”, “hybrid”, “virtual” and “remote” will be used. For the purposes of this paper, “in-person” will be understood to mean when team members are interacting simultaneously, physically within the Compass Lab. “Remote” or “virtual” will refer to when interactions are happening between people who are not co-located using only technology to interface. “Hybrid” will refer to when two or more participants are physically located in the Compass Lab and one or more participant(s) is participating remotely. Media richness is described as “a medium’s ability to communicate effectively based of four factors. They are the capacity for immediate feedback, the number of cues and channels it utilizes, the degree of personalization it affords, and its ability to communicate using natural language” [3]. This theory will be referenced and discussed in multiple of the following sections due to its relevance when choosing how to operate in remote and hybrid modes, as well as in making tool selections. The key to selecting the best mode of communication lays in how complicated the discussion is and the level of ambiguity involved. Not all conversations or interactions require media rich mediums. For example, providing information about which there is little to no ambiguity can easily be done in less rich methods - such as email. A conversation including high levels of ambiguity and/or complex information is better suited to a richer medium, such as in-person or a video call with shared screens.

Concurrent Engineering↗

Lessons Learned from Deploying an Analytical Task Management Database

Defining requirements, missions, technologies, and concepts for space exploration involves multiple levels of organizations, teams of people with complementary skills, and analytical models and simulations. Analytical activities range from filling a To-Be-Determined (TBD) in a requirement to creating animations and simulations of exploration missions. In a program as large as returning to the Moon, there are hundreds of simultaneous analysis activities. A way to manage and integrate efforts of this magnitude is to deploy a centralized database that provides the capability to define tasks, identify resources, describe products, schedule deliveries, and generate a variety of reports. This paper describes a web-accessible task management system and explains the lessons learned during the development and deployment of the database. Through the database, managers and team leaders can define tasks, establish review schedules, assign teams, link tasks to specific requirements, identify products, and link the task data records to external repositories that contain the products. Data filters and spreadsheet export utilities provide a powerful capability to create custom reports. Import utilities provide a means to populate the database from previously filled form files. Within a four month period, a small team analyzed requirements, developed a prototype, conducted multiple system demonstrations, and deployed a working system supporting hundreds of users across the aeros pace community. Open-source technologies and agile software development techniques, applied by a skilled team enabled this impressive achievement. Topics in the paper cover the web application technologies, agile software development, an overview of the system's functions and features, dealing with increasing scope, and deploying new versions of the system.

O'Neil, Daniel A.↗

Status Report and Lessons Learned from the Univ. of Arizona NMSD

We will present the latest generation of space mirror technology being developed at the Univ. of Arizona (UA). Unlike conventional monolithic mirrors, the UA mirrors are completely active in their operation. This allows greater flexibility in the mass, volume and performance specifications. The UA mirror design uses a thin flexible substrate for the optical surface and an actuated lightweight structure for surface accuracy and support. We provide an update on the UA NGST Mirror System Demonstrator (NMSD). The 2-m, f/5 NMSD mirror uses a 2 mm thick glass substrate and weighs 86 pounds. We review the mirror's design, discuss the mythology schemes used to actuate the figure, and present a list of the lessons learned.

Baiocchi, Dave↗

Environmentally-driven Materials Obsolescence: Material Replacements and Lessons Learned from NASA's Space Shuttle Program

The Space Shuttle Program was terminated in 2011 with the last flight of the Shuttle Endeavour. During the 30 years of its operating history, the number of domestic and international environmental regulations increased rapidly and resulted in materials obsolescence risks to the program. Initial replacement efforts focused on ozone depleting substances. As pressure from environmental regulations increased, Shuttle worked on the replacement of heavy metals. volatile organic compounds and hazardous air pollutants. Near the end of the program. Shuttle identified potential material obsolescence driven by international regulations and the potential for suppliers to reformulate materials. During the Shuttle Program a team focused on environmentally-driven materials obsolescence worked to identify and mitigate these risks. Lessons learned from the Shuttle experience can be applied to new NASA Programs as well as other high reliability applications.

Meinhold, Anne↗

Lessons Learned from the Construction of Upgrades to the NASA Glenn Icing Research Tunnel and Re-activation Testing

Major upgrades were made in 1999 to the 6- by 9-Foot (1.8- by 2.7-m) Icing Research Tunnel (IRT) at the NASA Glenn Research Center. These included replacement of the electronic controls for the variable-speed drive motor, replacement of the heat exchanger, complete replacement and enlargement of the leg of the tunnel containing the new heat-exchanger, the addition of flow-expanding and flow-contracting turning vanes upstream and downstream of the heat exchanger, respectively, and the addition of fan outlet guide vanes (OGV's). This paper presents an overview of the construction and reactivation testing phases of the project. Important lessons learned during the technical and contract management work are documented.

Sheldon, David W.↗

RSRA/X-Wing flight control system development - Lessons learned

The X-Wing, in concept, marries the efficiencies of a helicopter and fixed wing aircraft through the use of a four-bladed wing/rotor that can be rotated or stopped in flight. The RSRA/X-Wing flight test program was a technology demonstration of this concept which, after three successful flights, was discontinued in late 1987. In spite of many technical challenges in this program, such as the use of circulation control, the fabrication of a large all-composite rotor, the development of an advanced, quadruplex digital flight control system, and the need for higher harmonic control, no major technical problems had been encountered at the time of the stop-work order. This paper addresses the issues of flight control system development and focuses on lessons learned. As with other such programs, software development was the most consuming issue. Other subjects of discussion include the problems of balancing program goals with technical goals, software- and hard-ware-related problems, safety issues, and system testing.

Corliss, Lloyd D.↗

The Advanced Communications Technology Satellite - Performance, Reliability and Lessons Learned

The Advanced Communications Satellite (ACTS) was conceived and developed in the mid- 1980s as an experimental satellite to demonstrate unproven Ka-band technology, and potential new commercial applications and services. Since launch into geostationary orbit in September 1993. ACTS has accumulated almost seven years of essentially trouble-free operation and met all program objectives. The unique technology, service experiments. and system level demonstrations accomplished by ACTS have been reported in many forums over the past several years. As ACTS completes its final experiments activity, this paper will relate the top-level program goals that have been achieved in the design, operation, and performance of the particular satellite subsystems. Pre-launch decisions to ensure satellite reliability and the subsequent operational experiences contribute to lessons learned that may be applicable to other comsat programs.

Krawczyk, Richard J.↗

GN&C Flight Experience and Lessons Learned from BioSentinel: A 6U Deep Space Cubesat

This paper reviews the flight experiences of the BioSentinel propulsion and Attitude Determination and Control System (ADCS) teams. BioSentinel is a 6U cubesat that launched as a secondary payload aboard the Space Launch System's (SLS) maiden flight in November of 2022 and is now operating in an Earth trailing heliocentric orbit. We discuss the mission's original GNC approach as well as several improvements made in-flight, in particular a novel approach to gyro bias estimation in the spacecraft’s sun safe controller. The development and flight experience of the spacecraft's RCS propulsion system is also discussed, along with modifications made to the momentum management approach in response to a failed thruster valve. Finally, we present lessons learned and recommendations for GNC design in future deep-space cubesats.

BioSentinel↗

Aerospace Meteorology Lessons Learned Relative to Aerospace Vehicle Design and Operations

Aerospace Meteorology came into being in the 1950s as the development of rockets for military and civilian usage grew in the United States. The term was coined to identify those involved in the development of natural environment models, design/operational requirements, and environment measurement systems to support the needs of aerospace vehicles, both launch vehicles and spacecraft. It encompassed the atmospheric environment of the Earth, including Earth orbit environments. Several groups within the United States were active in this area, including the Department of Defense, National Aeronautics and Space Administration, and a few of the aerospace industry groups. Some aerospace meteorology efforts were similar to those being undertaken relative to aviation interests. As part of the aerospace meteorology activities a number of lessons learned resulted that produced follow on efforts which benefited from these experiences, thus leading to the rather efficient and technologically current descriptions of terrestrial environment design requirements, prelaunch monitoring systems, and forecast capabilities available to support the development and operations of aerospace vehicles.

Vaughan, William W.↗

Overview With Results and Lessons Learned of the X-43A Mach 10 Flight

This paper provides an overview of the final flight of the NASA X-43A project. The project consisted of three flights, two planned for Mach 7 and one for Mach 10. The third and final flight, November 16, 2004, was the first Mach 10 flight demonstration of an airframe-integrated, scramjet-powered, hypersonic vehicle. The goals and objectives for the project as well as those for the third flight are presented. The configuration of the Hyper-X stack including the X-43A, Hyper-X launch vehicle, and Hyper-X research vehicle adapter is discussed. The second flight of the X-43A was successfully conducted on March 27, 2004. Mission differences, vehicle modifications and lessons learned from the second flight as they applied to the third flight are also discussed. An overview of flight 3 results is presented.

Marshall, Laurie A.↗

Lessons Learned from the Flight Unit Testing of the Near Earth Asteroid Scout Flight System

The Near Earth Asteroid Scout flight mission is set to launch on the maiden voyage of the Space Launch System as a secondary payload. The spacecraft will be jettisoned in cis-lunar space and embark on an ambitious 2.5 year mission to image an asteroid. The spacecraft is uniquely equipped with an 85m2 solar sail as the main propulsion system. The monolithic sail system is designed to package within a 6U volume for launch and then deploy during flight. The NEA Scout team has presented in the past to the International Symposium on Solar Sailing topics related to the engineering development unit and design efforts to achieve flight hardware build. This paper will focus on the lessons learned from building and testing the NEA Scout flight system. Focus will be on the mechanical, software, and electrical interfaces as well as preparation for subsystem environmental tests, including thermal vacuum. Due to the unique design of the spacecraft, the solar sail subsystem was required to be located in the center of the spacecraft. This requirement lead to design challenges such as designing and accommodating critical cable harnesses to run through the center of the sail subsystem, packaging and deployment design of the sail subsystem, and integrated testing efforts through an avionics test bed to verify and validate a complete system architecture.

Lockett, Tiffany Russell↗