Search NASA⌕ Search

SEARCH · Search NASA

Results for “Lessons”

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 253 records · Page 14
All sourcesNASA NTRSDOE OSTI
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 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 NTRSDate not supplied

Ideas for Applying Artificial Intelligence to NASA Lessons Learned

Artificial intelligence is it tool that has existed for many years. Recent developments in generative AI has rapidly expanded the applications for this tool across many domains such as writing, analyzing, summarizing, creating videos, creating graphics and others. Charts in this presentation will prompt attendees to discuss the pros and cons, and potential validation methodology for imbedding artificial intelligence tools in the NASA lessons learned knowledge sharing environment.

Knowledge Management↗
NASA NTRS2024

Lessons Learned from Particulate Characterization Laboratory Anomalies

The White Sands Test Facility chemistry laboratory provides quality control for cleanroom operations including cleanliness verification of aerospace hardware by particulate counts and non-volatile residue determinations, particulate counts for liquid hypergolic propellants, gaseous helium and nitrogen propellant pressurizing agents used for ground support equipment and flight test article valve actuation, gaseous oxygen primarily used for component testing, and deionized water for refurbished propellant hardware flushing. Cleanliness verification includes particulate counts and non-volatile residue determinations to industry standard, NASA, and program specifications and levels. Particulate counts are typically to customer-specified specifications and levels including JPR 5322.1H (2016) Levels 50 and 100, Orion (MPCV 70156. Revision H (2018)) Level 100, RPTSTD-8070-0001 Revision 3 (2022), and IEST-STD-CC1246E (2013) Levels 50 and 100. The laboratory issues high pressure filter holders containing membrane filters to test operations personnel, who collect samples by flowing the required volumes of fluid through the filter holder, and the filter holder is returned to the lab for counting. A passing particulate count is required before testing may proceed. Rapid data reduction and issuing of reports indicating a pass or fail of the particulate specification are required. Corrective action and resampling invariably occurs if a sample fails. Consequently, the laboratory must maintain the highest degree of reliability to facilitate quality data used to decide if testing may proceed. Experience and continual improvements have enabled reliability. However, anomalies attributed to lab processes and hardware including filter holders, membranes, and Petri dishes have been encountered. This paper presents a summary of problems, solutions, successes, and lessons learned from particle counting experience for over 35 years.

Lessons Learned↗
NASA NTRS1974

MSFC Skylab lessons learned

Key lessons learned during the Skylab Program that could have impact on on-going and future programs are presented. They present early and sometimes subjective opinions; however, they give insights into key areas of concern. These experiences from a complex space program management and space flight serve as an early assessment to provide the most advantage to programs underway. References to other more detailed reports are provided.

Source record↗
NASA NTRS1974

Lessons learned on the Skylab program

Lessons learned in the Skylab program and their application and adaptation to other space programs are summarized. Recommendations and action taken on particular problems are described. The use of Skylab recommendations to identify potential problems of future space programs is discussed.

Source record↗
NASA NTRS1982

First Spacelab mission status and lessons learned

There are 38 experiments and/or facilities currently under development, or undergoing testing, which will be incorporated into Spacelab for its first mission. These experiments cover a range of scientific disciplines which includes atmospheric research, life sciences, space plasma research, materials science, and space industrialization technology. In addition to the full development of individual experiments, the final design of the integrated payload and the development of all requisite integration hardware have been accomplished. Attention is given to the project management lessons learned during payload integration development.

Craft, H. G., Jr.↗
NASA NTRS1983

The Space Shuttle focused-technology program - Lessons learned

The results of a focused technology program (FTP), its management structure, the development of the Space Shuttle, and lessons applicable to future space programs such as a space station are discussed. A committee was formed by NASA in 1969 to define the technologies necessary for a reusable spacecraft. Basic and applied research assessments were featured at the beginning of the process. Working groups were established to cover all necessary areas, e.g., Operations, Structures and Materials, Aerothermodynamics, etc., and tasks were distributed to appropriate NASA centers. Funding was drawn from existing budgets. The FTP proceeded successfully because of an understanding of the respective roles of industry and government, the willingness of industry to invest early in a new technology, and the unclassified status of information generated by the program. The in-house design and technology transfer methods that brought the project to a technology demonstration phase are explored, noting the necessity for users to take part in the development within their field.

Fitzgerald, P. E., Jr.↗
NASA NTRS1983

Space shuttle launch vehicle aerodynamic uncertainties: Lessons learned

The chronological development and evolution of an uncertainties model which defines the complex interdependency and interaction of the individual Space Shuttle element and component uncertainties for the launch vehicle are presented. Emphasis is placed on user requirements which dictated certain concessions, simplifications, and assumptions in the analytical model. The use of the uncertainty model in the vehicle design process and flight planning support is discussed. The terminology and justification associated with tolerances as opposed to variations are also presented. Comparisons of and conclusions drawn from flight minus predicted data and uncertainties are given. Lessons learned from the Space Shuttle program concerning aerodynamic uncertainties are examined.

Hamilton, J. T.↗
NASA NTRS1983

Lessons learned from the development and manufacture of ceramic reusable surface insulation materials for the space shuttle orbiters

Three ceramic, reusable surface insulation materials and two borosilicate glass coatings were used in the fabrication of tiles for the Space Shuttle orbiters. Approximately 77,000 tiles were made from these materials for the first three orbiters, Columbia, Challenger, and Discovery. Lessons learned in the development, scale up to production and manufacturing phases of these materials will benefit future production of ceramic reusable surface insulation materials. Processing of raw materials into tile blanks and coating slurries; programming and machining of tiles using numerical controlled milling machines; preparing and spraying tiles with the two coatings; and controlling material shrinkage during the high temperature (2100-2275 F) coating glazing cycles are among the topics discussed.

Banas, R. P.↗
NASA NTRS1982

OSTA-1 lessons learned and recommendations for future payloads

Five remote sensing experiments, together with one air pollution and one bioengineering experiment, were incorporated into the first Space Shuttle scientific payload of the NASA Office of Space and Terrestrial Applications (OSTA-1). The instrument package, experimental procedures, and specialized personnel teams all performed satisfactorily. Attention is presently given to the lessons learned during the OSTA-1-incorporating mission, STS-2 of November 12, 1981. Payload test and integration teams should never take unfamiliar facilities for granted. Training, especially if it employs hands-on experience with full-scale mockups and mission simulations, is found to be highly effective. Ephemeris data is too important to trust to table-top calculators, since errors propagate in repeated calculations. Terminal access to an off-line computer is required.

Baldwin, R. R.↗
NASA NTRS1986

Some lessons learned with wind tunnels

A review is presented of some of the lessons learned from wind tunnel tests since World War II. Wind tunnels achieved a very high productivity rate during the war due in part to development testing of numerous military aircraft concepts. Following the war, in addition to development testing, a rapid increase in basic research testing occurred in order to explore areas of interest revealed by the conduct of war and to expand on advanced technology that became available from Germany and Italy. The research test areas discussed are those primarily related to the transition from subsonic flight to supersonic flight.

Spearman, M. L.↗
NASA NTRS1985

Measuring the software process and product: Lessons learned in the SEL

The software development process and product can and should be measured. The software measurement process at the Software Engineering Laboratory (SEL) has taught a major lesson: develop a goal-driven paradigm (also characterized as a goal/question/metric paradigm) for data collection. Project analysis under this paradigm leads to a design for evaluating and improving the methodology of software development and maintenance.

Basili, V. R.↗
NASA NTRS1986

High-angle-of-attack aerodynamics - Lessons learned

Recently, the military and civil technical communities have undertaken numerous studies of the high angle-of-attack aerodynamic characteristics of advanced airplane and missile configurations. The method of approach and the design methodology employed have necessarily been experimental and exploratory in nature, due to the complex nature of separated flows. However, despite the relatively poor definition of many of the key aerodynamic phenomena involved for high-alpha conditions, some generic guidelines for design consideration have been identified. The present paper summarizes some of the more important lessons learned in the area of high angle-of-attack aerodynamics with examples of a number of key concepts and with particular emphasis on high-alpha stability and control characteristics of high performance aircraft. Topics covered in the discussion include the impact of design evolution, forebody flows, control of separated flows, configuration effects, aerodynamic controls, wind-tunnel flight correlation, and recent NASA research activities.

Chambers, J. R.↗