The JPL Deep Space Network Simplification Project (NSP): lessons learned 1998-2004
Explore the source record for details and available documents.
Network Simplification Project↗
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.
Europa Mission Concept Studies : Early Formulation MBSE and Lessons Learned
No abstract available
project formulation↗
Lessons learned from the NEPTUNE power system and other deep-sea adventures
The development of underwater science systems presents some challenging technical issues. It seems that the best efforts of the engineers and scientists involved are sometimes inadequate, and projects that once seemed straightforward end up being late, or overbudget, or cancelled. This paper will review some of the lessons that may be learned from the examples of three science projects in the deep ocean: the DUMAND neutrino detector, the H20 observatory, and the power system part of the NEPTUNE regional cabled observatory.
ocean science↗
Profile of NASA software engineering: Lessons learned from building the baseline
It is critically important in any improvement activity to first understand the organization's current status, strengths, and weaknesses and, only after that understanding is achieved, examine and implement promising improvements. This fundamental rule is certainly true for an organization seeking to further its software viability and effectiveness. This paper addresses the role of the organizational process baseline in a software improvement effort and the lessons we learned assembling such an understanding for NASA overall and for the NASA Goddard Space Flight Center in particular. We discuss important, core data that must be captured and contrast that with our experience in actually finding such information. Our baselining efforts have evolved into a set of data gathering, analysis, and crosschecking techniques and information presentation formats that may prove useful to others seeking to establish similar baselines for their organization.
Hall, Dana↗
Lessons learned studying design issues for lunar and Mars settlements
In a study of lunar and Mars settlement concepts, an analysis was made of fundamental design assumptions in five technical areas against a model list of occupational and environmental health concerns. The technical areas included the proposed science projects to be supported, habitat and construction issues, closed ecosystem issues, the "MMM" issues (mining, material processing, and manufacturing), and the human elements of physiology, behavior, and mission approach. Four major lessons were learned. First it is possible to relate public health concerns to complex technological development in a proactive design mode, which has the potential for long-term cost savings. Second, it became very apparent that prior to committing any nation or international group to spending the billions to start and complete a lunar settlement, over the next century, that a significantly different approach must be taken from those previously proposed, to solve the closed ecosystem and "MMM" problems. Third, it also appears that the health concerns and technology issues to be addressed for human exploration into space are fundamentally those to be solved for human habitation of the Earth (as a closed ecosystem) in the 21st century. Finally, it is proposed that ecosystem design modeling must develop new tools, based on probabilistic models as a step up from closed circuit models.
Life Support Systems↗
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. Some attempts have already been made to apply autonomy and automation in these areas in the past with varying degrees of success. We present brief case histories and the lessons inferred from them. Combining this past experience with anticipated future needs, we attempt to clarify the challenges that must be met in order to realize the benefits of autonomy.
challenges↗
Lesson Learned During Implementation and Early Operations of the DS1 Beacon Monitor Experiment
A new approach to mission operations will be flight validated on NASA's New Millennium Program Deep Space One (DS1) mission which launched in October 1998.
becon↗
CloudSat Anomaly Recovery and Operational Lessons Learned
Nov 2011: NASA/JPL declared CloudSat fully operational in DO ]OP Mode . CloudSat collects science data during sunlit portion of orbit, stable spin hibernation in eclipse . New CONOPS requires constant monitoring of thermal and power profiles, while allowing collection of 54 mins of science data per sunlit orbit
spacecraft systems↗
Learning Lessons from the X-37 Project
The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite's White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with and turnaround maintenance performed. The fight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development. NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This recent partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of the X-37 effort, the team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff research and development and provides valuable experience to implement the exploration vision.
Turner, Susan↗
Learning Lessons from the X-37 Project
The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite s White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with landing and turnaround maintenance performed. The Flight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development (R&D). NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of this effort, the X-37 team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff R&D and provides valuable experience to implement the Vision for Space Exploration.
Turner, Susan↗
Morpheus and Ascent Abort-2 Lessons Learned in Lean SE&I
The purpose of this presentation is to describe key features of the streamlined systems engineering approach for two in-house NASA projects, the Morpheus lander (2010-2014) and Orion’s Ascent Abort 2 (AA-2) Crew Module and Separation Ring (CSR) project.
Lean development↗
Testing Planetary Rovers: Technologies, Perspectives, and Lessons Learned
Rovers are a vital component of NASA's strategy for manned and unmanned exploration of space. For the past five years, the Intelligent Mechanisms Group at the NASA Ames Research Center has conducted a vigorous program of field testing of rovers from both technology and science team productivity perspective. In this talk, I will give an overview of the the last two years of the test program, focusing on tests conducted in the Painted Desert of Arizona, the Atacama desert in Chile, and on IMG participation in the Mars Pathfinder mission. An overview of autonomy, manipulation, and user interface technologies developed in response to these missions will be presented, and lesson's learned in these missions and their impact on future flight missions will be presented. I will close with some perspectives on how the testing program has affected current rover systems.
Thomas, Hans↗
Lessons Learned on the Use of Data Surfaces for Ffowcs Williams-Hawkings Calculations: Airframe Noise Applications
The use of integral solutions to the acoustic analogy-based Ffowcs Williams-Hawkings (FW-H) formulation is the defacto industrial and academic approach for assessing far-field acoustic behavior from airframe noise simulations. The methodology utilizes time-accurate flow variables obtained at arbitrary data surfaces to determine far-field spectra. The solid surface approach, where the time history of pressure is recorded on the surface of the aircraft, is generally preferred. Permeable surfaces, where pressure and velocity are recorded on a user-defined surface enclosing the aircraft, are also used. This paper seeks to share some of the valuable lessons we learned over the past several years on the limitations of the FW-H formulation and best practices for its successful application. We show results for various configurations comprising isolated landing gears, a business jet, a large commercial transport, and a generic low boom supersonic prototype, all at landing conditions. We demonstrate that the solid FW-H approach has significant accuracy limitations for most realistic cases and that the permeable FW-H approach may also fail in specific scenarios, requiring additional costly steps to extract the correct far-field noise spectra. Suggested guidelines for proper FW-H calculations are also given.
Acoustic propagation, Ffowcs Williams-Hawkings Cal↗
An Overview of Lessons Learned from Sonic-Boom Flight Research Projects Conducted by NASA Armstrong Flight Research Center
This presentation describes the planning and executing of large scale sonic-boom acoustics tests as a part of LBFD testing with the goal to give the future teams the road-map for how to efficiently and effectively plan and execute these types of tests.
lessons learned↗
Lessons learned - Americans in space
Milestones in the learning process during development of spaceflight capability for different NASA missions are traced from the initial launch of the Mercury escape rocket to the advent of the Shuttle. A detached heat shield on the first manned Mercury orbital flight led to a decision for reentry with retrorockets attached, a situation which demonstrated a need for on-line communications with the spacecraft construction engineers. The Gemini program served to develop EVA techniques and docking procedures essential for the Apollo missions. Apollo 8 circled the moon after only one manned test flight of the equipment due to the success of the first flight. Lunar landing simulation training exposed the astronauts to situations beyond the human ability to respond. The training was justified when computer overload required the pilot to retake manual control of some spacecraft functions during the successful first lunar landing. All lessons previously learned were used to safely return the damaged Apollo 13 to earth. The Skylab missions provided an opportunity to maintain rotating teams of flight controllers on a 24-hr/day basis for periods of months. Finally, the six-year hiatus of U.S. manned space activities between the end of the Skylab missions and the first Shuttle flight provided time for incorporating previous lessons into new procedures, training strategies, and data resources.
Kranz, E.↗
A History of Space Toxicology Mishaps: Lessons Learned and Risk Management
After several decades of human spaceflight, the community of space-faring nations has accumulated a diverse and sometimes harrowing history of toxicological events that have plagued human space endeavors almost from the very beginning. Lessons have been learned in ground-based test beds and others were discovered the hard way - when human lives were at stake in space. From such lessons one can build a risk-management framework for toxicological events to minimize the probability of a harmful exposure, while recognizing that we cannot foresee all events. Space toxicologists have learned that relatively harmless compounds can be converted by air revitalization systems into compounds that cause serious harm to the crew. Our toxic risk management strategy now includes an assessment of the fate of any compound that might be released into the atmosphere. Propellants are highly toxic compounds, yet we have not always been able to thoroughly isolate the crew from exposure to these toxicants. Leakage of fluids from systems has resulted in hazardous conditions at times, and the behavior of such compounds inside a spacecraft has taught us how to manage potentially harmful escapes should they occur. Potential combustion events are an ever-present threat to the wellbeing of the crew. Such events have been sufficiently common that we have learned that one cannot judge the health threat of a given fire by the magnitude of the event. Management of such risks demands monitoring of combustion products. In the category of unpredictable toxic events, if one assumes that fires are predictable, we can place experience with toxic microbial metabolites, upsets during repair operations, and discharges from filters that have accumulated a substantial load of pollutants in their absorption beds. Management of such events requires a broad-spectrum, real-time analytical capability to discern the identity and concentrations of pollutants if they enter the atmosphere. Adverse events are an integral part of any human activity, and the spacefaring community must learn as much as possible from mistakes and near misses.
James, John T.↗
Lessons Learned in Architecting Human Spaceflight Programs
This paper discusses the fundamentals of architecting a major human spaceflight program and the lessons that can be learned from Constellation. Constellation is/was NASA's program to implement a new generation of human exploration missions to the moon and beyond. It is/was a tightly-coupled program where a unique set of architectural challenges can be seen and evaluated to better understand how architecting of such systems can be improved upon in the future. While the specific issues discussed in this paper derive from the current Constellation architecture they share threads with previously-crewed systems including Apollo and Shuttle and are likely to be common to any human exploration system or system of significant technical and programmatic complexity.
Muirhead, Brian↗
Guidance and Lessons Learned from COVID-19 for Human-Subjects Research
The goal of this effort was to identify innovative strategies, approaches, and methods that have enabled researchers to continue doing meaningful human subjects research during the COVID-19 pandemic. Many organizations and recent literature primarily focus on efforts for future research in a post-COVID environment. Additionally, there have been no systematic efforts across the agency or broader human factors community to coordinate or share strategies. Therefore, the focus was on acquiring knowledge gained by researchers from experiences during COVID that could be valuable to continue human-subjects research under existing restrictions.
Coronavirus Disease 2019↗