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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗
NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗
NASA NTRS2012

Lessons Learned for Improving Spacecraft Ground Operations

NASA has a unique history in processing the Space Shuttle fleet for launches. Some of this experience has been captured in the NASA Lessons Learned Information System (LLIS). This tool provides a convenient way for design engineers to review lessons from the past to prevent problems from reoccurring and incorporate positive lessons in new designs. At the Kennedy Space Center, the LLIS is being used to design ground support equipment for the next generation of launch and crewed vehicles. This paper describes the LLIS process and offers some examples.

Bell, Michael A.↗
NASA NTRS2010

Selected Lessons Learned over the ISS Design, Development, Assembly, and Operations: Applicability to International Cooperation for Standardization

This slide presentation reviews some of the lessons learned in the sphere of international cooperation during the development, assembly and operation of the International Space Station. From the begining all Partners shared a common objective to build, operate and utilize a crewed laboratory in low orbit as an international partnership. The importance of standards is emphasized.

Hirsch, David B.↗
NASA NTRS2007

Lessons Learned in the Specification, Purchase, Validation and Final Installation Process of a Replacement PCM Bit Synchronizer

This paper intends to describe the lessons learned while specifying validating and installing a bit sync to replace the 30 year old Aydin Model 335a PCM bit sync used in the Space Shuttle Launch Control Center. The engineer had to analyze the original requirements and specifications and then create new requirements documentation that more correctly described our needs. One issue to consider was the removal of unnecessary requirements such as various data formats when only one format is used. The conversion to a system that no longer has an assortment of analog rotary switches required retraining of the operators. Finally, post-procurement corrections for undisclosed user requirements and missed design requirements required close contact with a manufacturer who was willing to accommodate the changes.

Price, Richard N.↗
NASA NTRS1994

Composite chronicles: A study of the lessons learned in the development, production, and service of composite structures

A study of past composite aircraft structures programs was conducted to determine the lessons learned during the programs. The study focused on finding major underlying principles and practices that experience showed have significant effects on the development process and should be recognized and understood by those responsible for using of composites. Published information on programs was reviewed and interviews were conducted with personnel associated with current and past major development programs. In all, interviews were conducted with about 56 people representing 32 organizations. Most of the people interviewed have been involved in the engineering and manufacturing development of composites for the past 20 to 25 years. Although composites technology has made great advances over the past 30 years, the effective application of composites to aircraft is still a complex problem that requires experienced personnel with special knowledge. All disciplines involved in the development process must work together in real time to minimize risk and assure total product quality and performance at acceptable costs. The most successful programs have made effective use of integrated, collocated, concurrent engineering teams, and most often used well-planned, systematic development efforts wherein the design and manufacturing processes are validated in a step-by-step or 'building block' approach. Such approaches reduce program risk and are cost effective.

Vosteen, Louis F.↗
NASA NTRSDate not supplied

NASA’s Student Airborne Science Activation for Minority Serving Institutions: Inaugural Program, Educational Outcomes, and Lessons Learned

The NASA Student Airborne Science Activation (SaSa) for Minority Serving Institutions (MSIs) held its inaugural summer research program for early career undergraduates interested in the Geosciences. SaSa is a NASA Science Activation funded 8-week summer internship program. Twenty-four first- and second-year undergraduates from MSIs across the U.S. participated in the summer program - June 6 to July 29, 2022. Students had the opportunity to gain hands-on research experience in all components of an airborne science campaign including flying on-board a NASA research aircraft to collect atmospheric measurements. Students conducted independent research projects related to the atmosphere, ocean, and geosciences that feed into NASA’s broader Earth Science Division’s and Decadal Survey goals using air quality, meteorological, and oceanic measurements from surface, airborne, and satellite-based observations. The program split its time between partner institution, University of Maryland Baltimore County and NASA’s Wallops Flight Facility in Wallops Island, Virginia. Students also made site visits at partner institutions, including: Hampton University, University of Maryland Eastern Shore, Morgan State University, Howard University, and Coppin State University and attended lectures from visiting faculty and NASA Subject Matter Experts. Students were guided on their research projects by near-peer graduate mentors, SaSa program leadership, co-Is at partner institutions, and NASA scientists to address two major research themes: 1) how human-caused air pollution has human and environmental implications, and 2) how large-scale meteorological factors influence local weather conditions. Students sorted into research groups, based on sub-discipline areas in the Geosciences, including: “Clouds, Aerosols and Radiation”, “Meteorology and Planetary Boundary Layer”, “Air Quality: Particle Pollution and Trace Gases”, and “Air-Water-Land Interface”. Their research was presented as 3-minute lightning talks and in-person poster presentations at a close-out event at NASA Goddard Space Flight Center in Greenbelt, Maryland. The students’ inter- and trans-disciplinary research experiences centered in the use of multiple ground, airborne, and satellite remote sensing NASA Earth Science Division assets. Providing a unique experience aligned to recognize the societal benefits that NASA contributes in the areas of resource management, air quality monitoring and policy decisions, energy and weather predictions, and research on the Earth’s climate. The SaSa program aims to increase the number of students from MSIs that identify as underrepresented or underserved individuals in the Geosciences discipline, Earth System Science graduate programs, and the NASA workforce. A summary of the summer research program, educational, scientific, and programmatic outcomes, as well as lessons learned will be presented.

NASA↗
NASA NTRS1992

Scheduling lessons learned from the Autonomous Power System

The Autonomous Power System (APS) project at NASA LeRC is designed to demonstrate the applications of integrated intelligent diagnosis, control, and scheduling techniques to space power distribution systems. The project consists of three elements: the Autonomous Power Expert System (APEX) for Fault Diagnosis, Isolation, and Recovery (FDIR); the Autonomous Intelligent Power Scheduler (AIPS) to efficiently assign activities start times and resources; and power hardware (Brassboard) to emulate a space-based power system. The AIPS scheduler was tested within the APS system. This scheduler is able to efficiently assign available power to the requesting activities and share this information with other software agents within the APS system in order to implement the generated schedule. The AIPS scheduler is also able to cooperatively recover from fault situations by rescheduling the affected loads on the Brassboard in conjunction with the APEX FDIR system. AIPS served as a learning tool and an initial scheduling testbed for the integration of FDIR and automated scheduling systems. Many lessons were learned from the AIPS scheduler and are now being integrated into a new scheduler called SCRAP (Scheduler for Continuous Resource Allocation and Planning). This paper will service three purposes: an overview of the AIPS implementation, lessons learned from the AIPS scheduler, and a brief section on how these lessons are being applied to the new SCRAP scheduler.

Ringer, Mark J.↗
NASA NTRS2010

Lessons Learned on Implementing Fault Detection, Isolation, and Recovery (FDIR) in a Ground Launch Environment

This paper's main purpose is to detail issues and lessons learned regarding designing, integrating, and implementing Fault Detection Isolation and Recovery (FDIR) for Constellation Exploration Program (CxP) Ground Operations at Kennedy Space Center (KSC). Part of the0 overall implementation of National Aeronautics and Space Administration's (NASA's) CxP, FDIR is being implemented in three main components of the program (Ares, Orion, and Ground Operations/Processing). While not initially part of the design baseline for the CxP Ground Operations, NASA felt that FDIR is important enough to develop, that NASA's Exploration Systems Mission Directorate's (ESMD's) Exploration Technology Development Program (ETDP) initiated a task for it under their Integrated System Health Management (ISHM) research area. This task, referred to as the FDIIR project, is a multi-year multi-center effort. The primary purpose of the FDIR project is to develop a prototype and pathway upon which Fault Detection and Isolation (FDI) may be transitioned into the Ground Operations baseline. Currently, Qualtech Systems Inc (QSI) Commercial Off The Shelf (COTS) software products Testability Engineering and Maintenance System (TEAMS) Designer and TEAMS RDS/RT are being utilized in the implementation of FDI within the FDIR project. The TEAMS Designer COTS software product is being utilized to model the system with Functional Fault Models (FFMs). A limited set of systems in Ground Operations are being modeled by the FDIR project, and the entire Ares Launch Vehicle is being modeled under the Functional Fault Analysis (FFA) project at Marshall Space Flight Center (MSFC). Integration of the Ares FFMs and the Ground Processing FFMs is being done under the FDIR project also utilizing the TEAMS Designer COTS software product. One of the most significant challenges related to integration is to ensure that FFMs developed by different organizations can be integrated easily and without errors. Software Interface Control Documents (ICDs) for the FFMs and their usage will be addressed as the solution to this issue. In particular, the advantages and disadvantages of these ICDs across physically separate development groups will be delineated.

Ferrell, Bob A.↗
NASA NTRSDate not supplied

High-Lift Prediction Workshops: Retrospective, Lessons Learned, and Future Prospects

A series of workshops focused on high lift, ongoing since 2010, is discussed. The series goal is to improve computational fluid dynamics prediction of high-lift flowfields, which has historically been very unreliable. The workshops center on CFD verification and validation exercises addressed in common by experts from organizations around the world, thereby enabling more rapid learning and improvement than would be possible with independent research alone. The workshop goals and structure are described, lessons learned to date are summarized, and potential future prospects for high-lift prediction are given.

high lift↗
NASA NTRSDate not supplied

Lessons Learned in Concurrent Mission and Systems Design at NASA Glenn Research Center: Almost Fifteen Years of the Compass Team

This paper is a retrospective of the lessons learned during the almost 15-year history of the Compass concurrent mission and systems design team at NASA’s Glenn Research Center (GRC). It examines the key factors in the team’s evolution from a temporary group gathered to perform a single study to the successful, sustainable team it is today. Compass is a matrixed team of experts with various technical backgrounds and personalities. They collaborate over a two-week period either physically in a dedicated meeting space, or virtually to design a space system (Spacecraft, stage, science package, etc). Over the years, because of the rapid nature of the design studies, the team leadership has iterated on the optimal team member personality makeup, facility elements and tools as well as NASA GRC management support necessary to lead to sustained success.

systems engineering↗
NASA NTRS2014

ISS Ammonia Pump Failure, Recovery, and Lesson Learned A Hydrodynamic Bearing Perspective

The design, development, and operation of long duration spaceflight hardware has become an evolutionary process in which meticulous attention to details and lessons learned from previous experiences play a critical role. Invaluable to this process is the ability to retrieve and examine spaceflight hardware that has experienced a premature failure. While these situations are rare and unfortunate, the failure investigation and recovery from the event serve a valuable purpose in advancing future space mechanism development. Such a scenario began on July 31, 2010 with the premature failure of an ammonia pump on the external active thermal control system of the International Space Station. The ground-based inspections of the returned pump and ensuing failure investigation revealed five potential bearing forces that were un-accounted for in the design phase and qualification testing of the pump. These forces could combine in a number of random orientations to overload the pump bearings leading to solid-surface contact, wear, and premature failure. The recovery plan identified one of these five forces as being related to the square of the operating speed of the pump and this fact was used to recover design life through a change in flight rules for the operation of the pump module. Through the course of the failure investigation, recovery, and follow-on assessment of pump wear life, design guidance has been developed to improve the life of future mechanically pumped thermal control systems for both human and robotic exploration missions.

Bruckner, Robert J.↗
NASA NTRS2011

Microbiological Lessons Learned from the Space Shuttle

After 30 years of being the centerpiece of NASA s human spacecraft, the Space Shuttle will retire. This highly successful program provided many valuable lessons for the International Space Station (ISS) and future spacecraft. Major microbiological risks to crewmembers include food, water, air, surfaces, payloads, animals, other crewmembers, and ground support personnel. Adverse effects of microorganisms are varied and can jeopardize crew health and safety, spacecraft systems, and mission objectives. Engineering practices and operational procedures can minimize the negative effects of microorganisms. To minimize problems associated with microorganisms, appropriate steps must begin in the design phase of new spacecraft or space habitats. Spacecraft design must include requirements to control accumulation of water including humidity, leaks, and condensate on surfaces. Materials used in habitable volumes must not contribute to microbial growth. Use of appropriate materials and the implementation of robust housekeeping that utilizes periodic cleaning and disinfection will prevent high levels of microbial growth on surfaces. Air filtration can ensure low levels of bioaerosols and particulates in the breathing air. The use of physical and chemical steps to disinfect drinking water coupled with filtration can provide safe drinking water. Thorough preflight examination of flight crews, consumables, and the environment can greatly reduce pathogens in spacecraft. The advances in knowledge of living and working onboard the Space Shuttle formed the foundation for environmental microbiology requirements and operations for the International Space Station (ISS) and future spacecraft. Research conducted during the Space Shuttle Program resulted in an improved understanding of the effects of spaceflight on human physiology, microbial properties, and specifically the host-microbe interactions. Host-microbe interactions are substantially affected by spaceflight. Astronaut immune functions were found to be altered. Selected microorganisms were found to become more virulent during spaceflight. The increased knowledge gained on the Space Shuttle resulted in further studies of the host-microbe interactions on the ISS to determine if countermeasures were necessary. Lessons learned from the Space Shuttle Program were integrated into the ISS resulting in the safest space habitat to date.

Pierson, Duane L.↗
NASA NTRS2010

The Significant Incidents and Close Calls in Human Space Flight Chart: Lessons Learned Gone Viral

This presentation will explore the surprising history and events that transformed a mundane spreadsheet of historical spaceflight incidents into a popular and widely distributed visual compendium of lessons learned. The Significant Incidents and Close Calls in Human Space Flight Chart (a.k.a. The Significant Incidents Chart) is a popular and visually captivating reference product that has arisen from the work of the Johnson Space Center (JSC) Safety and Mission Assurance (S&MA) Flight Safety Office (FSO). It began as an internal tool intended to increase our team s awareness of historical and modern space flight incidents. Today, the chart is widely recognized across the agency as a reference tool. It appears in several training and education programs. It is used in familiarization training in the JSC Building 9 Mockup Facility and is seen by hundreds of center visitors each week. The chart visually summarizes injuries, fatalities, and close calls sustained during the continuing development of human space flight. The poster-sized chart displays over 100 total events that have direct connections to human space flight endeavors. The chart is updated periodically. The update process itself has become a collaborative effort. Many people, spanning multiple NASA organizations, have provided suggestions for additional entries. The FSO maintains a growing list of subscribers who have requested to receive updates. The presenters will discuss the origins and motivations behind the significant incidents chart. A review of the inclusion criteria used to select events will be offered. We will address how the chart is used today by S&MA and offer a vision of how it might be used by other organizations now and in the future. Particular emphasis will be placed on features of the chart that have met with broad acceptance and have helped spread awareness of the most important lessons in human spaceflight.

Wood, Bill↗
NASA NTRS1988

Tethered system/space platform integration - TSS lessons learned

Tethered spacecraft systems must be integrated with their user platforms in a way that allows both to carry out their design functions efficiently and safely. This paper describes the lessons learned about tethered system integration with a space platform from the NASA/PSN Tethered Satellite System. Items discussed include platform attitude control, induced voltage and current control, satellite tracking and tether length measurement, satellite communications and system operations sensitivities. A number of engineering issues yet to be resolved are noted. Tethered systems are complex and require careful design to ensure successful operation.

Rudolph, L. K.↗