Engineering Papers⌕ Search

SEARCH · Engineering Papers

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.

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

At least 289 records · Page 16

Team Collaboration: Lessons Learned Report

An Agency team collaboration pilot was conducted from July 2002 until June 2003 and then extended for an additional year. The objective of the pilot was to assess the value of collaboration tools and adoption processes as applied to NASA teams. In an effort to share knowledge and experiences, the lessons that have been learned thus far are documented in this report. Overall, the pilot has been successful. An entire system has been piloted - tools, adoption, and support. The pilot consisted of two collaboration tools, a team space and a virtual team meeting capability. Of the two tools that were evaluated, the team meeting tool has been more widely accepted. Though the team space tool has been met with a lesser degree of acceptance, the need for such a tool in the NASA environment has been evidenced. Both adoption techniques and support were carefully developed and implemented in a way that has been well received by the pilot participant community.

Arterberrie, Rhonda Y.↗

Systems engineering and integration and management for manned space flight programs

This paper discusses the history of SE&I management of the overall program architecture, organizational structure and the relationship of SE&I to other program organizational elements. A brief discussion of the method of executing the SE&I process, a summary of some of the major lessons learned, and identification of things that have proven successful are included.

Morris, Owen↗

Lessons Learned Implementing DOORS in a Citrix Environment

NASA's James Web Space Telescope (JWST) Project is a large multi-national project with geographically dispersed contractors that all need access to the Projects requirement database. Initially, the project utilized multiple DOORS databases with the built-in partitions feature to exchange modules amongst the various contractor sites. As the requirements databases matured the use of partitions became extremely difficult. There have been many issues such as incompatible versions of DOORS, inefficient mechanism for sharing modules, security concerns, performance issues, and inconsistent document import and export formats. Deployment of the client software with limited IT resources available was also an issue. The solution chosen by JWST was to integrate the use of a Citrix environment with the DOORS database to address most of the project concerns. The use of the Citrix solution allowed a single Requirements database in a secure environment via a web interface. The Citrix environment allows JWST to upgrade to the most current version of DOORS without having to coordinate multiple sites and user upgrades. The single requirements database eliminates a multitude of Configuration Management concerns and facilitated the standardization of documentation formats. This paper discusses the obstacles and the lessons learned throughout the installation, implementation, usage and deployment process of a centralized DOORS database solution.

Bussman, Marie↗

Reusable Solid Rocket Motor - Accomplishment, Lessons, and a Culture of Success

The Reusable Solid Rocket Motor (RSRM) represents the largest solid rocket motor (SRM) ever flown and the only human-rated solid motor. High reliability of the RSRM has been the result of challenges addressed and lessons learned. Advancements have resulted by applying attention to process control, testing, and postflight through timely and thorough communication in dealing with all issues. A structured and disciplined approach was taken to identify and disposition all concerns. Careful consideration and application of alternate opinions was embraced. Focus was placed on process control, ground test programs, and postflight assessment. Process control is mandatory for an SRM, because an acceptance test of the delivered product is not feasible. The RSRM maintained both full-scale and subscale test articles, which enabled continuous improvement of design and evaluation of process control and material behavior. Additionally RSRM reliability was achieved through attention to detail in post flight assessment to observe any shift in performance. The postflight analysis and inspections provided invaluable reliability data as it enables observation of actual flight performance, most of which would not be available if the motors were not recovered. RSRM reusability offered unique opportunities to learn about the hardware. NASA is moving forward with the Space Launch System that incorporates propulsion systems that takes advantage of the heritage Shuttle and Ares solid motor programs. These unique challenges, features of the RSRM, materials and manufacturing issues, and design improvements will be discussed in the paper.

Moore, D. R.↗

Development of Constellation's Launch Control System

The paper focuses on the National Aeronautics and Space Administration (NASA) Constellation Program's Launch Control System (LCS) development effort at Kennedy Space Center (KSC). It provides a brief history of some preceding efforts to provide launch control and ground processing systems for other NASA programs, and some lessons learned from those experiences. It then provides high level descriptions of the LCS mission, objectives, organization, architecture, and progress. It discusses some of our development tenets, including our use of standards based design and use of off-the-shelf products whenever possible, incremental development cycles, and highly reliable, available, and supportable enterprise class system servers. It concludes with some new lessons learned and our plans for the future.

Lougheed, Kirk D.↗

Preliminary Characterization Results from the DebriSat Project

The DebriSat project is a continuing effort sponsored by NASA and DoD to update existing break-up models using data obtained from two separate hypervelocity impact tests used to simulate on-orbit collisions. To protect the fragments resulting from the impact tests, "soft-catch" arenas made of polyurethane foam panels were utilized. After each impact test, the test chamber was cleaned and debris resulting from the catastrophic demise of the test article were collected and shipped to the University of Florida for post-impact processing. The post-impact processing activities include collecting, characterizing, and cataloging of the fragments. Since the impact tests, a team of students has been working to characterize the fragments in terms of their mass, size, shape, color and material content. The focus of the 20 months since the impact tests has been on the collection of 2 millimeters- and larger fragments resulting from impact test on the 56 kilogram-representative LEO (Low Earth Orbit) satellite referred to as DebriSat. To date we have recovered in excess of 115,000 fragments, 30,000 more than the prediction of 85,000 fragments from the existing model. We continue to collect fragments but have transitioned to the characterization phase of the post-impact activities. Since the start of the characterization phase, the focus has been to utilize automation to (i) expedite fragment characterization process and (ii) minimize human-in-the- loop. We have developed and implemented such automated processes; e.g., we have automated the data entry process to reduce operator errors during transcription of the measurement data. However, at all steps of the process, there is human oversight to ensure the integrity of the data. Additionally, we have developed and implemented repeatability and reproducibility tests to ensure that the instrumentation used in the characterization process is accurate and properly calibrated. In this paper, the implemented processes are described and preliminary results presented. Additionally, lessons learned from the implemented automations and their impacts on the integrity of the results are discussed.

Rivero, M.↗

A Thermal Review of the Sample Cartridge Assembly (SCA) Gravitational Effect of Distortion in Sintering (GEDS) Experiment Flight Processing

NASA’s Sample Cartridge Assembly (SCA) first flight experiment, Gravitational Effect of Distortion in Sintering (GEDS), was processed on the International Space Station (ISS) between 2019 and 2020. The SCA was heated in the European Space Agency’s (ESA) Low Gradient Furnace (LGF) that is housed inside the Material Science Research Rack (MSRR) located in the U.S. Laboratory Module. This summary will give a review of the design and flight experiment development for the GEDS SCA. It describes flight processing and the role of thermal engineering support. Lessons learned and future Principle Investigators (PI) will be discussed.

Micro-gravity Science↗

A Thermal Review of the Sample Cartridge Assembly (SCA) Gravitational Effect of Distortion in Sintering (GEDS) Experiment Flight Processing

NASA’s Sample Cartridge Assembly (SCA) first flight experiment, Gravitational Effect of Distortion in Sintering (GEDS), was processed on the International Space Station (ISS) between 2019 and 2020. The SCA was heated in the European Space Agency’s (ESA) Low Gradient Furnace (LGF) that is housed inside the Material Science Research Rack (MSRR) located in the U.S. Laboratory Module. This summary will give a review of the design and flight experiment development for the GEDS SCA. It describes flight processing and the role of thermal engineering support. Lessons learned and future Principle Investigators (PI) will be discussed.

MIcro-gravity Science↗

Planetary Protection Knowledge Gaps for Human Extraterrestrial Missions Workshop Booklet - 2015

Although NASA's preparations for the Apollo lunar missions had only a limited time to consider issues associated with the protection of the Moon from biological contamination and the quarantine of the astronauts returning to Earth, they learned many valuable lessons (both positive and negative) in the process. As such, those efforts represent the baseline of planetary protection preparations for sending humans to Mars. Neither the post-Apollo experience or the Shuttle and other follow-on missions of either the US or Russian human spaceflight programs could add many additional insights to that baseline. Current mission designers have had the intervening four decades for their consideration, and in that time there has been much learned about human-associated microbes, about Mars, and about humans in space that has helped prepare us for a broad spectrum of considerations regarding potential biological contamination in human Mars missions and how to control it. This paper will review the approaches used in getting this far, and highlight some implications of this history for the future development of planetary protection provisions for human missions to Mars. The role of NASA and ESA's planetary protection offices, and the aegis of COSPAR have been particularly important in the ongoing process.

Fonda, Mark L.↗

The Soil Moisture Acttive Passive Mission: Fault Protection Performance and Lessons Learned

Fault protection as a discipline involves a collection of flight software logic and operational processes for detecting unacceptable anomalous behavior, responding prior to reaching criticality, restricting the propagation of a failure beyond a fault containment region, and recovering the vehicle back to full or degraded functionality if possible. The System Fault Protection (SFP) design for the SMAP Earth orbiter was put to the test during its 90-day vehicle commissioning activities. During this time, the SFP software autonomously protected the vehicle from multiple faults to critical hardware, and the operations team successfully returned the observatory to its science state. The SFP also performed well in the presence of anomalous behavior below true safety limits by not taking unnecessary response actions, instead allowing the operations team time to monitor the behavior. Certain aspects of the SFP design were modified during operations via both parameter updates and a full flight software update in order to better match the vehicle behavior in the flight environment. An evaluation of the SMAP SFP performance during vehicle Commissioning will be provided in this paper, as well as a set of lessons learned largely focused on visibility, SFP mutability in operations, responses to peripheral device faults, and Safe Mode recovery and design. By capturing some of the knowledge gained during SMAP Commissioning, it is intended that this paper provide guidance for making future System Fault Protection designs more robust and supportive of operations.

Clark, Jessica↗

Engineering Lessons Learned and Technical Standards Integration: Capturing Key Technologies for Future Space Missions

Capturing engineering lessons learned derived from past experiences and new technologies, then integrating them with technical standards, provides a viable process for enhancing engineering capabilities. The development of future space missions will require ready access, not only to the latest technical standards, but also to lessons learned derived from past experiences and new technologies. The integration of this information such that it is readily accessible by engineering and programmatic personnel is a key aspect of enabling technology. This paper addresses the development of a new and innovative Lessons Learned/Best Practices/Applications Notes--Standards Integration System, including experiences with its initial implementation as a pilot effort within the NASA Technical Standards Program. Included are metrics on the Program, feedbacks from users, future plans, and key issues that are being addressed to expand the System's utility. The objective is the enhancement of engineering capabilities on all aspects of systems development applicable to the success of future space missions.

Mellen, Daniele P.↗

Holistic and Pragmatic Standards Processes Enable Interdisciplinary Science

Open, interdisciplinary science inevitably relies heavily on standards. Standards are those often unseen agreements that we take for granted when systems and processes are working fine. Yet standards work is perpetual, laborious, and sometimes contentious, especially for standards to work across diverse disciplines. Standards development, maintenance, and implementation is a complex, ongoing socio-technical process. NASA has developed a progressively open science policy and strategy that calls for the establishment of a data standards process reaching across the five diverse divisions of the Science Mission Directorate. This is a delicate exercise. We, therefore, seek to apply a holistic yet pragmatic approach to developing and maintaining a standards process. We adopt an ecological philosophy that focuses on the interactions within the data ecosystem and how standards facilitate those interactions. We couple high-level analysis with on the ground experimentation. We began by 1) mapping information ecosystem components (e.g. data centers, missions, services, protocols, users), 2)establishing how the components interact (e.g. sharing (meta)data, funding, personnel exchange), and 3) modelling system dynamics (e.g. creation of products from multiple data centers, redundant processes, shared services). The goal is to apply understanding of the ecosystem to real world applications (e.g. planning a new mission, implementing new policy requirements, improving process efficiency, etc.). We have also conducted studies of historical standardization efforts, documenting lessons learned and cautionary tales. We then contrast this more abstract work with real examples. We reviewed and assessed multiple existing standards development processes both within and external to NASA. We now work to implement an initial test process which can be further optimized. We seek to define a consistent approach for assigning persistent identifiers for research objects, especially for the purposes of citation. The experience from this relatively ‘simple’ test case adds a pragmatic perspective on how researchers and engineers actually work. This presentation will review the details of this methodology, our initial findings, and how they might apply to other interdisciplinary standardization efforts.

Mark A Parsons↗

The Applied Meteorology Unit: Nineteen Years Successfully Transitioning Research into Operations for America's Space Program

The Applied Meteorology Unit (AMU) provides technology transition and technique development to improve operational weather support to the Space Shuttle and the entire American space program. The AMU is funded and managed by NASA and operated by a contractor that provides five meteorologists with a diverse mix of advanced degrees, operational experience, and associated skills including data processing, statistics, and the development of graphical user interfaces. The AMU's primary customers are the U.S. Air Force 45th Weather Squadron at Patrick Air Force Base, the National Weather Service Spaceflight Meteorology Group at NASA Johnson Space Center, and the National Weather Service Melbourne FL Forecast Office. The AMU has transitioned research into operations for nineteen years and worked on a wide range of topics, including new forecasting techniques for lightning probability, synoptic peak winds,.convective winds, and summer severe weather; satellite tools to predict anvil cloud trajectories and evaluate camera line of sight for Space Shuttle launch; optimized radar scan strategies; evaluated and implemented local numerical models; evaluated weather sensors; and many more. The AMU has completed 113 projects with 5 more scheduled to be completed by the end of 2010. During this rich history, the AMU and its customers have learned many lessons on how to effectively transition research into operations. Some of these lessons learned include collocating with the operational customer and periodically visiting geographically separated customers, operator submitted projects, consensus tasking process, use of operator primary advocates for each project, customer AMU liaisons with experience in both operations and research, flexibility in adapting the project plan based on lessons learned during the project, and incorporating training and other transition assistance into the project plans. Operator involvement has been critical to the AMU's remarkable success and many awards from NASA, the National Weather Association, and two citations from the Navy's Center of Excellence for Best Manufacturing Practices. This paper will present the AMU's proven methods and explain how they may be applied by other organizations to effectively transition research into operations.

Madura, John T.↗

Lessons learned supporting onboard solid-state recorders

With the advance of semiconductor technology, Solid-State Recorders (SSR) have matured and been accepted as primary onboard data storage devices. Their high reliability, simpler interface and control, and high flexibility have made the SSR's a superb choice in today's spacecraft design. While there are many benefits, the use of SSR's may also add significant complexity to ground data systems. For instance, real-time and playback data may be interleaved into the same data stream, making data sequencing and time ordering difficult. Stored data may be played back out of time order, increasing processing load significantly. Data may also be played back after being sorted by Virtual Channels in the SSR, potentially creating bursts in packet rates that exceed the real-time processing capabilities of the ground systems. This paper presents a summary of lessons learned through the efforts in supporting a number of NASA's missions that employ SSR's. It describes various problems encountered through the design process, and their potential impact on ground system performance, resources, and cost. Recommended approaches to minimizing the impact are demonstrated by examples. The discussion leads to the conclusion that the use of SSR's demands an even higher level of cooperation between spacecraft and ground system designers in order to build the most cost effective end-to-end system.

Shi, Jeff↗

A path to in-space welding and to other in-space metal processing technologies using Space Shuttle small payloads

As we venture into space, it becomes necessary to assemble, expand, and repair space-based structures for our housing, research, and manufacturing. The zero gravity-vacuum of space challenges us to employ construction options which are commonplace on Earth. Rockwell International (RI) has begun to undertake the challenge of space-based construction via numerous options, of which one is welding. As of today, RI divisions have developed appropriate resources and technologies to bring space-based welding within our grasp. Further work, specifically in the area of developing space experiments to test RI technology, is required. RI Space Welding Project's achievements to date, from research and development (R&E) efforts in the areas of microgravity, vacuum, intra- / extra- vehicular activity and spinoff technologies, are reviewed. Special emphasis is given to results for G-169's (Get Away Special) microgravity flights aboard a NASA KC-135. Based on these achievements, a path to actual development of a space welding system is proposed with options to explore spinoff in-space metal processing technologies. This path is constructed by following a series of milestone experiments, of which several are to utilize NASA's Shuttle Small Payload Programs. Conceptual designs of the proposed shuttle payload experiments are discussed with application of lessons learned from G-169's design, development, integration, testing, safety approval process, and KC-135 flights.

Tamir, David↗

Quo Vadis Payload Safety?

As we complete the preparations for the fourth Hubble Space Telescope (HST) servicing mission, we note an anniversary approaching: it was 30 years ago in July that the first HST payload safety review panel meeting was held. This, in turn, was just over a year after the very first payload safety review, a Phase 0 review for the Tracking and Data Relay Satellite and its Inertial Upper Stage, held in June of 1977. In adapting a process that had been used in the review and certification of earlier Skylab payloads, National Aeronautics and Space Administration (NASA) engineers sought to preserve the lessons learned in the development of technical payload safety requirements, while creating a new process that would serve the very different needs of the new space shuttle program. Their success in this undertaking is substantiated by the fact that this process and these requirements have proven to be remarkably robust, flexible, and adaptable. Furthermore, the payload safety process has, to date, served us well in the critical mission of safeguarding our astronauts, cosmonauts, and spaceflight participants. Both the technical requirements and their interpretation, as well as the associated process requirements have grown, evolved, been streamlined, and have been adapted to fit multiple programs, including the International Space Station (ISS) program, the Shuttle/Mir program, and most recently the United States Constellation program. From its earliest days, it was anticipated that the payload safety process would be international in scope, and so it has been. European Space Agency (ESA), Japan Aerospace Exploration Agency (JAXA), German Space Agency (DLR), Canadian Space Agency (CSA), Russian Space Agency (RSA), and many additional countries have flown payloads on both the space shuttle and on the ISS. Our close cooperation and long-term working relationships have culminated in the franchising of the payload safety review process itself to our partners in ESA, which in turn will serve as a roadmap for extending the franchise to other Partners.

Fodroci, Michael P.↗

A Rapid Assessment of a Lunar Surface Laboratory Module

Johnson Space Center has piloted an innovation team known as the Forge to perform rapid turnaround, concurrent engineering studies. The Forge is intended to be able to pull together a team of strategically selected domain experts to innovatively solve a specified problem within a short period of time. The Forge’s inaugural project was the development of a Lunar Surface Laboratory Module concept. The lab module is intended as an option for the NASA Lunar Architecture Team and may allow for increased science productivity and return on investment than with only the Surface Habitat. The Forge team developed two concepts, a stationary laboratory and a mobile laboratory. Human factors evaluations have been conducted to determine the acceptability of the resulting design concepts. The human factors evaluations conducted include a card sort evaluation of the laboratories by science discipline and the System Usability Scale (SUS). The card sort focused subject matter expert expectations for the relative positioning of the laboratory functional areas, determining whether a given lab area should be adjacent to, or separated from, another. The SUS focused on layout efficiency. Both used human factors personnel and both life and physical scientists as subject matter experts. Each of these evaluations will focus primarily on objective data with limited subjective comments, reducing the time required for processing responses. The results of the card sort and SUS evaluations and their implications will be discussed. Based on the evaluation data, an overall acceptability of the Lunar Surface Laboratory Module produced by the Forge study can be determined. Lessons learned and recommendations for future use of human factors rapid assessment processes in early design trades will also be provided.

Forge↗

Rapid Assessment of a Lunar Surface Laboratory Module

Johnson Space Center has piloted an innovation team known as the Forge to perform rapid turnaround, concurrent engineering studies. The Forge is intended to be able to pull together a team of strategically selected domain experts to innovatively solve a specified problem within a short period of time. The Forge’s inaugural project was the development of a Lunar Surface Laboratory Module concept. The lab module is intended as an option for the NASA Lunar Architecture Team and may allow for increased science productivity and return on investment than with only the Surface Habitat. The Forge team developed two concepts, a stationary laboratory and a mobile laboratory. Human factors evaluations have been conducted to determine the acceptability of the resulting design concepts. The human factors evaluations conducted include a card sort evaluation of the laboratories by science discipline and the System Usability Scale (SUS). The card sort is focused subject matter expert expectations for the relative positioning of the laboratory functional areas, determining whether a given lab area should be adjacent to, or separated from, another. The SUS will focus on layout efficiency. Both will use human factors personnel and both life and physical scientists as subject matter experts. Each of these evaluations will focus primarily on objective data with limited subjective comments, reducing the time required for processing responses. The results of the card sort and SUS evaluations and their implications will be discussed. Based on the evaluation data, an overall acceptability of the Lunar Surface Laboratory Module produced by the Forge study can be determined. Lessons learned and recommendations for future use of human factors rapid assessment processes in early design trades will also be provided.

Human Factors↗