SEARCH · Search NASA

Results for “lessons learned process”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

All sources NASA NTRS DOE OSTI

NASA NTRS2003

The Successful Development of an Automated Rendezvous and Capture (AR&C) System for the National Aeronautics and Space Administration

During the 1990's, the Marshall Space Flight Center (MSFC) conducted pioneering research in the development of an automated rendezvous and capture/docking (AR&C) system for U.S. space vehicles. Development and demonstration of a rendezvous sensor was identified early in the AR&C Program as the critical enabling technology that allows automated proximity operations and docking. A first generation rendezvous sensor, the Video Guidance Sensor (VGS), was developed and successfully flown on STS-87 and STS-95, proving the concept of a video- based sensor. A ground demonstration of the entire system and software was successfully tested. Advances in both video and signal processing technologies and the lessons learned from the two successful flight experiments provided a baseline for the development, by the MSFC, of a new generation of video based rendezvous sensor. The Advanced Video Guidance Sensor (AGS) has greatly increased performance and additional capability for longer-range operation with a new target designed as a direct replacement for existing ISS hemispherical reflectors.

Roe, Fred D.↗

NASA NTRS2002

Successful Development of an Automated Rendezvous and Capture System

During the 1990's, the Marshall Space Flight Center (MSFC) conducted pioneering research in the development of an automated rendezvous and capture/docking system for U.S. space vehicles. Development and demonstration of a rendezvous sensor was identified early in the AR&C Program as the critical enabling technology that allows automated proximity operations and docking. A first generation rendezvous sensor, the Video Guidance Sensor (VGS) was developed and successfully flown on STS 87 and again on STS 95, proving the concept of a video-based sensor. Advances in both video and signal processing technologies and the lessons learned from the two successful flight experiments provided a baseline for the development, by the MSFC, of a new generation of video based rendezvous sensor. The Advanced Video Guidance Sensor (AVGS) has greatly increased performance and additional capability for longer-range operation with a new Target designed as a direct replacement for existing ISS hemispherical reflectors. A ground demonstration of the entire system and software was successfully tested.

Roe, Fred D.↗

NASA NTRS2004

SDM Virtualness Project

In the summer of 2001, NASA and Ford Motor Company co-sponsored a research project aimed at improving the education process and application of lessons learned through distant education. The System Design & Management Program (SDM) was used as a laboratory for improving distance learning capabilities. The research project was a follow up to previous research on globally dispersed teams.

Lim, Christopher Yit-Seong↗

NASA NTRS2000

Project Galileo: completing Europa, preparing for Io

Galileo has completed the Europa leg of the Galileo Europa Mission, and is now pumping down the apojove in each succeeding orbit in preparation for the Io phase. Including three encounters earlier in the primary mission, the total of ten close passes by Europa have provided a wealth of interesting and provocative information about this intriguing body. The results presented include new and exciting information about Europa's interactions with Jupiter's magnetosphere, its interior structure, and its tantalizing surface features, which strongly hint at a watery subsurface layer. Additional data concerning Callisto, and its own outlook for a subsurface ocean are also presented. In addition the engineering aspects of operating the spacecraft during the past year are explored, as well as a brief examination of what will be the challenges to prepare for the Io encounters. The steadily increasing radiation dosage that the spacecraft is experiencing is well beyond the original design parameters, and is contributing to a number of spacecraft problems and concerns. The ability of the flight team to analyze and solve these problems, even at the reduced staffing levels of an extended mission, is a testament to their tenacity and loyalty to the mission. The engineering data being generated by these continuing radiation-induced anomalies will prove invaluable to designers of future spacecraft to Jupiter and its satellites. The lessons learned during this arduous process are presented. c 2000 International Astronautical Federation. Published by Elsevier Science Ltd. All rights reserved.

long duration↗

NASA NTRS2004

Hierarchical Storage Management at the NASA Center for Computational Sciences: From UniTree to SAM-QFS

This paper presents the data management issues associated with a large center like the NCCS and how these issues are addressed. More specifically, the focus of this paper is on the recent transition from a legacy UniTree (Legato) system to a SAM-QFS (Sun) system. Therefore, this paper will describe the motivations, from both a hardware and software perspective, for migrating from one system to another. Coupled with the migration from UniTree into SAM-QFS, the complete mass storage environment was upgraded to provide high availability, redundancy, and enhanced performance. This paper will describe the resulting solution and lessons learned throughout the migration process.

Salmon, Ellen↗

NASA NTRS2007

Hydra Rendezvous and Docking Sensor

The U.S. technology to support a CEV AR&D activity is mature and was developed by NASA and supporting industry during an extensive research and development program conducted during the 1990's and early 2000 time frame at the Marshall Space Flight Center. Development and demonstration of a rendezvous/docking sensor was identified early in the AR&D Program as the critical enabling technology that allows automated proxin~ity operations and docking. A first generation rendezvous/docking sensor, the Video Guidance Sensor (VGS) was developed and successfully flown on STS 87 and again on STS 95, proving the concept of a video-based sensor. Advances in both video and signal processing technologies and the lessons learned from the two successful flight experiments provided a baseline for the development of a new generation of video based rendezvous/docking sensor. The Advanced Video Guidance Sensor (AVGS) has greatly increased performance and additional capability for longer-range operation. A Demonstration Automatic Rendezvous Technology (DART) flight experiment was flown in April 2005 using AVGS as the primary proximity operations sensor. Because of the absence of a docking mechanism on the target satellite, this mission did not demonstrate the ability of the sensor to co~ltrold ocking. Mission results indicate that the rendezvous sensor operated successfully in "spot mode" (2 km acquisition of the target, bearing data only) but was never commanded to "acquire and track" the docking target. Parts obsolescence issues prevent the construction of current design AVGS units to support the NASA Exploration initiative. This flight proven AR&D technology is being modularized and upgraded with additional capabilities through the Hydra project at the Marshall Space Flight Center. Hydra brings a unique engineering approach and sensor architecture to the table, to solve the continuing issues of parts obsolescence and multiple sensor integration. This paper presents an approach to sensor hardware trades, to address the needs of future vehicles that may rendezvous and dock with the International Space Station (ISS). It will also discuss approaches for upgrading AVGS to address parts obsolescence, and concepts for modularizing the sensor to provide configuration flexibility for multiple vehicle applications. Options for complementary sensors to be integrated into the multi-head Hydra system will also be presented. Complementary sensor options include ULTOR, a digital image correlator system that could provide relative six-degree-of-freedom information independently from AVGS, and time-of-flight sensors, which determine the range between vehicles by timing pulses that travel from the sensor to the target and back. Common targets and integrated targets, suitable for use with the multi-sensor options in Hydra, will also be addressed.

Roe, Fred↗

NASA NTRS2015

International Space Station (ISS) 3D Printer Performance and Material Characterization Methodology

In order for human exploration of the Solar System to be sustainable, manufacturing of necessary items on-demand in space or on planetary surfaces will be a requirement. As a first step towards this goal, the 3D Printing In Zero-G (3D Print) technology demonstration made the first items fabricated in space on the International Space Station. From those items, and comparable prints made on the ground, information about the microgravity effects on the printing process can be determined. Lessons learned from this technology demonstration will be applicable to other in-space manufacturing technologies, and may affect the terrestrial manufacturing industry as well. The flight samples were received at the George C. Marshall Space Flight Center on 6 April 2015. These samples will undergo a series of tests designed to not only thoroughly characterize the samples, but to identify microgravity effects manifested during printing by comparing their results to those of samples printed on the ground. Samples will be visually inspected, photographed, scanned with structured light, and analyzed with scanning electron microscopy. Selected samples will be analyzed with computed tomography; some will be assessed using ASTM standard tests. These tests will provide the information required to determine the effects of microgravity on 3D printing in microgravity.

Bean, Q. A.↗

NASA NTRS2017

Correleation of the SAGE III on ISS Thermal Models in Thermal Desktop

The Stratospheric Aerosol and Gas Experiment III (SAGE III) instrument is the fifth in a series of instruments developed for monitoring aerosols and gaseous constituents in the stratosphere and troposphere. SAGE III was launched on February 19, 2017 and mounted to the International Space Station (ISS) to begin its three-year mission. A detailed thermal model of the SAGE III payload, which consists of multiple subsystems, has been developed in Thermal Desktop (TD). Correlation of the thermal model is important since the payload will be expected to survive a three-year mission on ISS under varying thermal environments. Three major thermal vacuum (TVAC) tests were completed during the development of the SAGE III Instrument Payload (IP); two subsystem-level tests and a payload-level test. Additionally, a characterization TVAC test was performed in order to verify performance of a system of heater plates that was designed to allow the IP to achieve the required temperatures during payload-level testing; model correlation was performed for this test configuration as well as those including the SAGE III flight hardware. This document presents the methods that were used to correlate the SAGE III models to TVAC at the subsystem and IP level, including the approach for modeling the parts of the payload in the thermal chamber, generating pre-test predictions, and making adjustments to the model to align predictions with temperatures observed during testing. Model correlation quality will be presented and discussed, and lessons learned during the correlation process will be shared.

Amundsen, Ruth M.↗

NASA NTRS2020

Control System Software Development: Fall 2020 Internship Final Report

The Launch Control System (LCS) is an integral part of the Space Launch System (SLS) as it responds and sends instructions to both the vehicle and ground systems. This semester, the focus has been on the development of assurance tests for the Graphical User Interface (GUI) software components of the LCS. This will help ensure that the system software functions as intended. This paper describes the goals, procedures, and results of this process as well as lessons learned that may be useful for future interns working on similar projects.

software↗

NASA NTRSDate not supplied

Risk Reduction through Early Software Prototyping for the Mars Ascent Vehicle

Despite the critical nature flight software plays in the development of spacecraft, software development teams are often brought on to the project after initial requirements definition and design efforts have started, and well after the conceptual design phase has completed. The flight software development team for the Mars Ascent Vehicle has supported the project from project formulation and conceptual design into the formal design and development. This approach has allowed for the development of a robust software prototype that supported risk reduction in numerous areas for the project. Early software prototyping supported decision making in the areas of hardware selection and considerations, software architecture, and simulation requirements. The prototype software actively supported ongoing trade studies and analyses for the project and enable valuable collaboration across multiple subsystems as well as between MSFC and the Jet Propulsion Laboratory. This early development also allowed the team to leverage past projects’ lessons learned to make valuable process improvements.

Stefanie Justice↗

NASA NTRS2006

Techniques for Embedding Instrumentation in Pressure Vessel Test Articles

Many interesting structural and thermal events occur in materials that are housed within a surrounding pressure vessel. In order to measure the environment during these events and explore their causes instrumentation must be installed on or in the material. Transducers can be selected that are small enough to be embedded within the test material but these instruments must interface with an external system in order to apply excitation voltages and output the desired data. The methods for installing the instrumentation and creating an interface are complicated when the material is located in a case or housing containing high pressures and hot gases. Installation techniques for overcoming some of these difficulties were developed while testing a series of small-scale solid propellant and hybrid rocket motors at Marshall Space Flight Center. These techniques have potential applications in other test articles where data are acquired from materials that require containment due to the severe environment encountered during the test process. This severe environment could include high pressure, hot gases, or ionized atmospheres. The development of these techniques, problems encountered, and the lessons learned from the ongoing testing process are summarized.

Cornelius, Michael↗

NASA NTRS2009

Spacecraft Electrical Connector Selection and Application Processes

This assessment was initiated by the NASA Engineering & Safety Center (NESC) after a number of recent "high profile" connector problems, the most visible and publicized of these being the problem with the Space Shuttle's Engine Cut-Off System cryogenic feed-thru connector. The NESC commissioned a review of NASA's connector selection and application processes for space flight applications, including how lessons learned and past problem records are fed back into the processes to avoid recurring issues. Team members were primarily from the various NASA Centers and included connector and electrical parts specialists. The commissioned study was conducted on spacecraft connector selection and application processes at NASA Centers. The team also compared the NASA spacecraft connector selection and application process to the military process, identified recent high profile connector failures, and analyzed problem report data looking for trends and common occurrences. The team characterized NASA's connector problem experience into a list of top connector issues based on anecdotal evidence of a system's impact and commonality between Centers. These top issues are as follows, in no particular rank order: electrically shorted, bent and/or recessed contact pins, contact pin/socket contamination leading to electrically open or intermittencies, connector plating corrosion or corrosion of connector components, low or inadequate contact pin retention forces, contact crimp failures, unmated connectors and mis-wiring due to workmanship errors during installation or maintenance, loose connectors due to manufacturing defects such as wavy washer and worn bayonet retention, damaged connector elastomeric seals and cryogenic connector failure. A survey was also conducted of SAE Connector AE-8C1 committee members regarding their experience relative to the NASA concerns on connectors. The most common responses in order of occurrence were contact retention, plating issues, worn-out or damaged coupling mechanisms, bent pins, contact crimp barrel cracking and torn seals. In addition to these common themes, responses included issues with markings, dimensional errors on the build, contact/socket damage (handling), manufacturing defects and customer misapplication and mishandling. The NESC team concluded that considering the large quantity and wide variety of connectors successfully flown on human and robotic space applications, the number of failures is quite low. However, "high profile" failures with significant cost, schedule, safety, and/or mission success impacts continue to occur. It was also concluded that connector failures occur throughout a system's life-cycle with the majority of connector issues application related. A number of recommendations were identified for improving NASA connector selection processes and overall space connector reliability and performance.

Iannello, Chris↗

NASA NTRS2002

Integrating Theory and Practice: Applying the Quality Improvement Paradigm to Product Line Engineering

My assertion is that not only are product lines a relevant research topic, but that the tools used by empirical software engineering researchers can address observed practical problems. Our experience at NASA has been there are often externally proposed solutions available, but that we have had difficulties applying them in our particular context. We have also focused on return on investment issues when evaluating product lines, and while these are important, one can not attain objective data on success or failure until several applications from a product family have been deployed. The use of the Quality Improvement Paradigm (QIP) can address these issues: (1) Planning an adoption path from an organization's current state to a product line approach; (2) Constructing a development process to fit the organization's adoption path; (3) Evaluation of product line development processes as the project is being developed. The QIP consists of the following six steps: (1) Characterize the project and its environment; (2) Set quantifiable goals for successful project performance; (3) Choose the appropriate process models, supporting methods, and tools for the project; (4) Execute the process, analyze interim results, and provide real-time feedback for corrective action; (5) Analyze the results of completed projects and recommend improvements; and (6) Package the lessons learned as updated and refined process models. A figure shows the QIP in detail. The iterative nature of the QIP supports an incremental development approach to product lines, and the project learning and feedback provide the necessary early evaluations.

Stark, Michael↗

NASA NTRS1996

Software Engineering Program: Software Process Improvement Guidebook

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Source record↗

NASA NTRS2017

Lessons Learned from Applying Design Thinking in a NASA Rapid Design Study in Aeronautics

In late 2015, NASA's Aeronautics Research Mission Directorate (ARMD) funded an experiment in rapid design and rapid teaming to explore new approaches to solving challenging design problems in aeronautics in an effort to cultivate and foster innovation. This report summarizes several lessons learned from the rapid design portion of the study. This effort entailed learning and applying design thinking, a human-centered design approach, to complete the conceptual design for an open-ended design challenge within six months. The design challenge focused on creating a capability to advance experimental testing of autonomous aeronautics systems, an area of great interest to NASA, the US government as a whole, and an entire ecosystem of users and developers around the globe. A team of nine civil servant researchers from three of NASA's aeronautics field centers with backgrounds in several disciplines was assembled and rapidly trained in design thinking under the guidance of the innovation and design firm IDEO. The design thinking process, while used extensively outside the aerospace industry, is less common and even counter to many practices within the aerospace industry. In this report, several contrasts between common aerospace research and development practices and design thinking are discussed, drawing upon the lessons learned from the NASA rapid design study. The lessons discussed included working towards a design solution without a set of detailed design requirements, which may not be practical or even feasible for management to ascertain for complex, challenging problems. This approach allowed for the possibility of redesigning the original problem statement to better meet the needs of the users. Another lesson learned was to approach problems holistically from the perspective of the needs of individuals that may be affected by advances in topic area instead of purely from a technological feasibility viewpoint. The interdisciplinary nature of the design team also provided valuable experience by allowing team members from different technological backgrounds to work side-by-side instead of dividing into smaller teams, as is frequently done in traditional multidisciplinary design. The team also learned how to work with qualitative data obtained primarily through the 70-plus interviews that were conducted over the course of this project, which was a sharp contrast to using quantitative data with regards to identifying, capturing, analyzing, storing, and recalling the data. When identifying potential interviewees who may have useful contributions to the design subject area, the team found great value in talking to non-traditional users and potential beneficiaries of autonomous aeronautics systems whose impact on the aeronautics autonomy ecosystem is growing swiftly. Finally, the team benefitted from using "sacrificial prototyping," which is a method of rapidly prototyping draft concepts and ideas with the intent of enabling potential users to provide significant feedback early in the design process. This contrasts the more common approach of using expensive prototypes that focus on demonstrating technical feasibility. The unique design approach and lessons learned by the team throughout this process culminated in a final design concept that was quite different than what the team originally assumed would be the design concept initially. A summary of the more usercentered final design concept is also provided.

McGowan, Anna-Maria↗

NASA NTRS2005

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. As part of the NASA Technical Standards Program activities, engineering lessons learned datasets have been identified from a number of sources. These are being searched and screened for those having a relation to Technical Standards. This paper will address some of these Systems Engineering Lessons Learned and how they are being related to Technical Standards within the NASA Technical Standards Program, including linking to the Agency's Interactive Engineering Discipline Training Courses and the life cycle for a flight vehicle development program.

Gill, Paul S.↗

NASA NTRS1982

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.↗

NASA NTRSDate not supplied

Having a Come-Apart: Lessons Learned from Additively Manufactured Hardware Failures

NASA has been engaged with additively manufactured (AM) process and component development since the 2000’s. AM offers various technical advantages, such as enhanced hardware design complexity, part consolidation, and processing of novel alloys in addition to programmatic advantages for reduction in processing time and cost. The focus of much of the AM development at NASA has been to mature the various processes, characterize material properties, develop standards, produce demonstrator parts, and integrate AM hardware in liquid rocket engines. These aspects have been demonstrated through process and design iterations using a methodical characterization, test-fail-fix cycles, as well as application and dissemination of lessons learned. In addition to these fundamental demonstrations of the AM process and hardware development, alloys that provide performance advantages in the high temperature and high-pressure environments have been matured for use in rocket engines. These environments are challenging for any alloy and any design, and the AM process is required to fully meet the intended design requirements. The importance of proper AM process was made evident in the failure of a Laser Powder Bed Fusion (L-PBF) copper-alloy combustion chamber during a hot-fire test due to a degraded material quality resulted from an AM process issue. The hot-fire test aimed to demonstrate high duty cycle under a risk-tolerant development project, where consequences of component failure would be minimal. However, the unintentional component failure emphasized the necessity of robust material characterization and rigorous process control procedures for the safe use of AM components in critical applications. In part, such concerns motivate the AM certification approach that NASA has recently adopted in NASA-STD-6030 “Additive Manufacturing Requirements for Spaceflight Systems”. This presentation provides an overview of the previously mentioned failure, a discussion on the evaluation of the failed chamber and supplemental chambers produced at the same time, a representative material samples that included intentional build witness lines, and a summary of the key results and recommendations from the evaluations. NASA continues to approach AM processes and designs with a level of risk and acceptance of failures that is appropriate for the project objectives, with the overall goal of safe implementation of AM technology and transferring AM technology into commercial space applications. The objective of this presentation is to provide awareness to the community working critical and non-critical AM components and the lessons learned on proper implementation of AM.

Additive Manufacturing↗