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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

James Webb Space Telescope - Applying Lessons Learned to I&T

The James Webb Space Telescope (JWST) is part of a new generation of spacecraft acquiring large data volumes from remote regions in space. To support a mission such as the JWST, it is imperative that lessons learned from the development of previous missions such as the Hubble Space Telescope and the Earth Observing System mission set be applied throughout the development and operational lifecycles. One example of a key lesson that should be applied is that core components, such as the command and telemetry system and the project database, should be developed early, used throughout development and testing, and evolved into the operational system. The purpose of applying lessons learned is to reap benefits in programmatic or technical parameters such as risk reduction, end product quality, cost efficiency, and schedule optimization. In the cited example, the early development and use of the operational command and telemetry system as well as the establishment of the intended operational database will allow these components to be used by the developers of various spacecraft components such that development, testing, and operations will all use the same core components. This will reduce risk through the elimination of transitions between development and operational components and improve end product quality by extending the verification of those components through continual use. This paper will discuss key lessons learned that have been or are being applied to the JWST Ground Segment integration and test program.

Johns, Alan↗
NASA NTRS2008

Lessons Learned from the Wide Field Camera 3 TV1 and TV2 Thermal Vacuum Test Campaigns

The Wide Field Camera 3 (WFC3) instrument has undergone two complete thermal vacuum tests (TV1 and TV2), during which valuable lessons were learned regarding test configuration, test execution, model capabilities, and modeling practices. The very complex thermal design of WFC3 produced a number of challenging aspects to ground testing with numerous ThermoElectric Coolers and heat pipes, not all of which were functional. Lessons learned during TV1 resulted in significant upgrades to the model capabilities and a change in the test environment approach for TV2. These upgrades proved invaluable during TV2 when pretest modeling assumptions proved to be false. Each of the lessons learned relate to one of two following broad statements: 1. Ensure the design can be tested and that the effect of non-flight like conditions is well understood, particularly with respect to non passive devices (TECs, Heat Pipes, etc) 2. Ensure that the model is sufficiently detailed and is capable of predicting off-nominal behavior and the power dissipation of any thermal devices, especially TECs This paper outlines a number of the lessons learned over these two test campaigns with respect to the thermal design, model, and test configuration and presents recommendations for future tests.

Peabody, Hume↗
NASA NTRS2010

Lessons Learned from the Node 1 Temperature and Humidity Control Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Temperature and Humidity Control (THC) subsystem and it will document some of the lessons that have been learned to date for this subsystem and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs. 1

Williams, David E.↗
NASA NTRS2011

Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allow the mission flight control teams and the astronaut crews to plan, train and fly every Space Shuttle mission have been developed by the Flight Planning Branch at the NASA Johnson Space Center. As the Space Shuttle Program ends, lessons learned have been collected from each phase of the successful execution of these Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines will be discussed, as well as techniques and methods used to solve complex spacecraft and instrument orientation problems. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the shuttle and ground team has also defined specific lessons used in the improving the control teams effectiveness. Methodologies to communicate and transmit messages, images, and files from Mission Control to the Orbiter evolved over several years. These lessons have been vital in shaping the effectiveness of safe and successful mission planning that have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of shuttle flight missions are not only documented in this paper, but are also discussed as how they pertain to changes in process and consideration for future space flight planning.

Price, Jennifer B.↗
NASA NTRS2011

NASA Flight Planning Branch Space Shuttle Lessons Learned

Planning products and procedures that allowed the mission Flight Control Teams and the Astronaut crews to plan, train and fly every Space Shuttle mission were developed by the Flight Planning Branch at the NASA Johnson Space Center in Houston, Texas. As the Space Shuttle Program came to a close, lessons learned were collected from each phase of the successful execution of these Space Shuttle missions. Specific examples of how roles and responsibilities of console positions that develop the crew and vehicle attitude timelines have been analyzed and will be discussed. Additionally, the relationships and procedural hurdles experienced through international collaboration have molded operations. These facets will be explored and related to current and future operations with the International Space Station and future vehicles. Along with these important aspects, the evolution of technology and continual improvement of data transfer tools between the Space Shuttle and ground team has also defined specific lessons used in improving the control team s effectiveness. Methodologies to communicate and transmit messages, images, and files from the Mission Control Center to the Orbiter evolved over several years. These lessons were vital in shaping the effectiveness of safe and successful mission planning and have been applied to current mission planning work in addition to being incorporated into future space flight planning. The critical lessons from all aspects of previous plan, train, and fly phases of Space Shuttle flight missions are not only documented in this paper, but are also discussed regarding how they pertain to changes in process and consideration for future space flight planning.

Clevenger, Jennifer D.↗
NASA NTRS2012

Lessons Learned from Ares I Upper Stage Structures and Thermal Design

The Ares 1 Upper Stage was part of the vehicle intended to succeed the Space Shuttle as the United States manned spaceflight vehicle. Although the Upper Stage project was cancelled, there were many lessons learned that are applicable to future vehicle design. Lessons learned that are briefly detailed in this Technical Memorandum are for specific technical areas such as tank design, common bulkhead design, thrust oscillation, control of flight and slosh loads, purge and hazardous gas system. In addition, lessons learned from a systems engineering and vehicle integration perspective are also included, such as computer aided design and engineering, scheduling, and data management. The need for detailed systems engineering in the early stages of a project is emphasized throughout this report. The intent is that future projects will be able to apply these lessons learned to keep costs down, schedules brief, and deliver products that perform to the expectations of their customers.

Ahmed, Rafiq↗
NASA NTRS2009

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↗
NASA NTRS2012

Assuring that Lessons Learned Critical to Mission Success Get Used

NASA has an established process for documenting and disseminating lessons learned from spaceflight missions and related activities. However, independent assessments of the NASA lessons learned process conducted in 2002, 2003, and 2011 have concluded that NASA programs and projects are failing to heed and apply these lessons learned. JPL recently completed implementation of a three-pronged approach to assure that NASA lessons learned get used by JPL spaceflight projects.

Oberhettinger, David↗
NASA NTRS2013

Lessons Learned During Instrument Testing for the Thermal Infrared Sensor (TIRS)

The Themal InfraRed Sensor (TIRS) instrument, set to launch on the Landsat Data Continuity Mission in 2013, features a passively cooled telescope and IR detectors which are actively cooled by a two stage cryocooler. In order to proceed to the instrument level test campaign, at least one full functional test was required, necessitating a thermal vacuum test to sufficiently cool the detectors and demonstrate performance. This was fairly unique in that this test occurred before the Pre Environmental Review, but yielded significant knowledge gains before the planned instrument level test. During the pre-PER test, numerous discrepancies were found between the model and the actual hardware, which were revealed by poor correlation between model predictions and test data. With the inclusion of pseudo-balance points, the test also provided an opportunity to perform a pre-correlation to test data prior to the instrument level test campaign. Various lessons were learned during this test related to modeling and design of both the flight hardware and the Ground Support Equipment and test setup. The lessons learned in the pre-PER test resulted in a better test setup for the nstrument level test and the completion of the final instrument model correlation in a shorter period of time. Upon completion of the correlation, the flight predictions were generated including the full suite of off-nominal cases, including some new cases defined by the spacecraft. For some of these ·new cases, some components now revealed limit exceedances, in particular for a portion of the hardware that could not be tested due to its size and chamber limitations.. Further lessons were learned during the completion of flight predictions. With a correlated detalled instrument model, significant efforts were made to generate a reduced model suitable for observatory level analyses. This proved a major effort both to generate an appropriate network as well as to convert to the final model to the required format and yielded additional lessons learned. In spite of all the challenges encountered by TIRS, the instrument was successfully delivered to the spacecraft and will soon be tested at observatory level in preparation for a successful mission launch.

Peabody, Hume L.↗
NASA NTRS2016

Lessons Learned from the Advanced Topographic Laser Altimeter System

The ICESat-2 Advanced Topographic Laser Altimeter System (ATLAS) instrument is an upcoming Earth Science mission focusing on the effects of climate change. The flight instrument passed all environmental testing at GSFC (Goddard Space Flight Center) and is now ready to be shipped to the spacecraft vendor for integration and testing. This presentation walks through the lessons learned from design, hardware, analysis and testing perspective. ATLAS lessons learned include general thermal design, analysis, hardware, and testing issues as well as lessons specific to laser systems, two-phase thermal control, and optical assemblies with precision alignment requirements.

Thermal↗
NASA NTRS2017

Designing to Sample the Unknown: Lessons from OSIRIS-REx Project Systems Engineering

On September 8, 2016, the third NASA New Frontiers mission launched on an Atlas V 411. The Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) will rendezvous with asteroid Bennu in 2018, collect a sample in 2020, and return that sample to Earth in September 2023. The development team has overcome a number of challenges in order to design and build a system that will make contact with an unexplored, airless, low-gravity body. This paper will provide an overview of the mission, then focus in on the system-level challenges and some of the key system-level processes. Some of the lessons here are unique to the type of mission, like discussion of operating at a largely-unknown, low-gravity object. Other lessons, particularly from the build phase, have broad implications. The OSIRIS-REx risk management process was particularly effective in achieving an on-time and under-budget development effort. The systematic requirements management and verification and the system validation also helped identify numerous potential problems. The final assessment of the OSIRIS-REx performance will need to wait until the sample is returned in 2023, but this post-launch assessment will capture some of the key systems-engineering lessons from the development team.

Asteroid↗
NASA NTRS2021

Spacecraft Line-of-Sight Jitter Management and Mitigation Lessons Learned and Engineering Best Practices

Predicting, managing, controlling, and testing spacecraft line-of-sight (LoS) jitter caused by micro-vibrations due to on-board internal disturbance sources is a formidable multidisciplinary engineering task. It is especially challenging for those missions hosting high-performance (e.g., nano-radian/milli-arcsecond class), vibration-sensitive optical sensor payloads with stringent pointing stability requirements. The Nation Aeronautics and Space Administration (NASA) and the European Space Agency (ESA) are planning technically aggressive spaceflight missions that include ultra-high-performance optical payloads with delicate, highly vibration-sensitive scientific and observational instruments. The guidance, navigation, and control community of practice will need to leverage collective experiences and document their best practices and lessons learned to address future micro-vibration challenges. To identify lessons learned and best practices the NASA Engineering & Safety Center sponsored a 2-day Spacecraft LoS Jitter Workshop in late 2019. The workshop’s goal was to provide a multidisciplinary forum to elicit deeper understanding of the issues related to addressing the spacecraft LoS jitter/micro-vibration problem. The primary objective was to identify, document, and share lessons learned, best practices, and preferred options for jitter-related analysis and test activities. Representatives from NASA, ESA, along with NASA’s industrial partners, independent consultant subject matter experts, and members of academia participated in the workshop. This paper describes the motivation for the workshop and summarize the identified findings and recommendations.

Lessons Learned↗
NASA NTRSDate not supplied

Insights and Observations from Operating a Geostationary Laser Communication Relay Mission: Operational Lessons from NASA’s Laser Communications Relay Demonstration (LCRD) and Associated Optical Ground Stations (OGSs)

The NASA Laser Communications Relay Demonstration (LCRD) has operated on orbit for the last two years. The LCRD Mission consists of a geostationary payload and two optical ground stations. This technology demonstration mission is NASA’s first two-way, end-to-end optical communications relay. LCRD has performed an extensive experiment campaign to analyze laser communication performance for extended operations. This paper discusses various lessons learned while operating the optical relay mission from early commissioning through two years of operation. Before launch, engineers and operators performed analyses to generate operational procedures based on expected LCRD performance. However, only operation on orbit can supply actual performance data. Additional topics covered in this paper include pre-launch and commissioning testing, ephemeris generation and cadence, environmental configurations, and accommodation concerns. The addition of Integrated Laser Communications Relay Demonstration Low Earth Orbit User Modem and Amplifier Terminal (ILLUMA-T) to the optical network supplemented the LCRD team’s operational experiences and enabled them to garner new lessons learned. The authors of this paper include day-to-day flight leads who consulted with on-console operators, engineers, and subject matter experts analyzing data and experiment results to gather the lessons learned described in this paper. LCRD is a joint project involving NASA Goddard Space Flight Center (GSFC), the California Institute of Technology Jet Propulsion Laboratory (JPL), and Massachusetts Institute of Technology Lincoln Laboratory (MIT LL).

Lessons Learned↗
NASA NTRSDate not supplied

A Frank Discussion on Lessons Learned From Adopting and Applying NASA-STD-6030 for Spaceflight Systems

With the advancement and adoption of Additive Manufacturing (AM) for spaceflight systems, numerous lessons have been learned during the qualification and certification of AM components. The lessons learned covered in this presentation will provide an overview of the challenges faced by NASA centers and commercial partners working to design AM hardware that complies with NASA-STD-6030 Additive Manufacturing Requirements (AMR). Topics of interest include tailoring of requirements for specific projects, documentation requirements, and addressing conservative approaches towards mechanical property development and analysis. In addition to that, this presentation aims to impress that these lessons learned will influence the future revisions of the NASA technical standard to facilitate and advance AM technology adoption on NASA projects.

Additive Manufacturing↗
NASA NTRS1976

Skylab lessons learned as applicable to a large space station, 1967-1974

This report records some of the lessons learned during Skylab development. The approach taken is to list lessons which could have wide application in the development of a large space station. The lessons are amplified and explained in light of the background and experiences of the Skylab development.

Schneider, W. C.↗
NASA NTRS1984

Lessons learned from KSC processing on STS science, applications, and commercial payloads

The present investigation is concerned with an evaluation of the lessons learned in connection with the flights of the Shuttle orbiters Columbia, Challenger, and Discovery. A description is provided of several general and specific lessons related to the processing of free-flying and attached payloads. John F. Kennedy Space Center (KSC), as the prime launch and landing site, is responsible for managing all payload-to-payload, payload-to-simulated orbiter, and payload-to-orbiter operations. For each payload, a KSC Launch Site Support Manager (LSSM) is named as the primary point of contact for the customer. Attention is given to aspects of planning interaction, payload types, and problems of ground processing. The discussed lessons are partly related to the value of early contact between customers and KSC representatives, the primary point of contact, the launch site support plan, and the importance of customer participation.

Williams, W. E.↗
NASA NTRS1987

Shuttle orbit flight control design lessons - Direction for Space Station

The Space Shuttle orbit flight control system, which operates during all exo-atmospheric flight phases, has successfully met operational requirements. Many design integration and operational issues that required resolution during development and testing provide an experience base that will benefit the development of future space systems, particularly the Space Station. To this end, the applicable Shuttle and Space Station hardware/software is reviewed with some perspective provided on how current design groundrules were derived and how issues that affected the Shuttle orbit control system design are a pathway for the Space Station. Some of the most significant lessons learned from the Shuttle are summarized, with a discussion of the effect of performance and design of hardware, including the data processing system on software structures and usage procedures. Crew interface issues and important results from man-in-the-loop tests are summarized. Problems resulting from trying to meet difficult orbital operational objectives, including some sophisticated payload operations are characterized. Several proposed Shuttle flight control design improvements, developed in response to some of the lessons learned so far, are identified. Potential application of the Shuttle design lessons and new control technologies to the Space Station are discussed.

Cox, Kenneth J.↗
NASA NTRS1986

The computerization of programming: Ada (R) lessons learned

One of the largest systems yet written in Ada has been constructed. This system is the Intermetrics Ada compiler. Many lessons have been learned during the implementation of this Ada compiler. Some of these lessons, concentrating on those lessons relevant to large system implementations are described. The characteristics of the Ada compiler implementation project at Intermetrics are also described. Some specific experiences during the implementation are pointed out.

Struble, Dennis D.↗