Engineering Papers⌕ Search

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.

At least 1,369 records · Page 76

Shaping NASA's Kennedy Space Center Safety for the Future

With the completion of the Space Shuttle Program, the Kennedy Space Center (KSC) safety function will be required to evolve beyond the single launch vehicle launch site focus that has held prominence for almost fifty years. This paper will discuss how that evolution is taking place. Specifically, we will discuss the future of safety as it relates to a site that will have multiple, very disparate, functions. These functions will include new business; KSC facilities not under the control of NASA; traditional payload and launch vehicle processing; and, operations conducted by NASA personnel, NASA contractors or a combination of both. A key element in this process is the adaptation of the current KSC set of safety requirements into a multi-faceted set that can address each of the functions above, while maintaining our world class safety environment. One of the biggest challenges that will be addressed is how to protect our personnel and property without dictating how other Non-NASA organizations protect their own employees and property. The past history of KSC Safety will be described and how the lessons learned from previous programs will be applied to the future. The lessons learned from this process will also be discussed as information for other locations that may undergo such a transformation.

Kirkpatrick, Paul↗

The OSIRIS-Rex Asteroid Sample Return: Mission Operations Design

The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the missions science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the SRC lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis.Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together space craft, instrument and operations scenarios. The project implemented lessons learned from other small body missions: APLNEAR, JPLDAWN and ESARosetta. The key lesson learned was expected the unexpected and implement planning tools early in the lifecycle. In preparation to PDR, the project changed the asteroid arrival date, to arrive one year earlier and provided additional time margin. STK is used for Mission Design and STKScheduler for instrument coverage analysis.

SatCORPS Global Cloud Composite (GCC): the Design and Delivery of A High Quality, High Resolution, Global Cloud Product Available in Near-Real Time

The NASA Satellite ClOud and Radiation Property retrieval System (SatCORPS) supports the development of an analysis ready and cloud-optimized data transformation pipeline and geospatial service enablement of a global cloud composite (GCC) product derived from global geostationary satellite imagery. This geospatial service will be available at high temporal and spatial resolution via the SatCORPS web mapping application for visualization and analysis as well as direct ingestion to common geospatial software and custom programming. The resulting global cloud composite products from the processing pipeline can then be geospatially-service enabled as ArcGIS Image Services and Open Geospatial Consortium (OGC) Web Mapping/Coverage Services for visualization and analysis via a web mapping application and common geospatial software. Near real time global observations are created through the composition of five geostationary satellites that provides modelling and forecasting communities with the capability to provide high quality and timely information to start the projection process. The Global Cloud Composite product combines information from geostationary satellites, GOES-16, GOES-17, Himawari-8, Meteosat-11 and Meteosat-9 to create a single global composite netcdf file and images using the different products within the netcdf file. The SatCORPS team, though our Global Cloud Composite (GCC) product and web-based visualization tools including Geographical Information System (GIS) services provide near real time global cloud product information to both automated processes and traditional web users that is timely and high quality derived from geostationary satellites. The Global Cloud Composite product takes advantage of the scalable processing resources provided by the AWS batch service to provide new composites every thirty minutes. Because information from each of the low earth orbiting satellites is available on schedules tuned to the specific satellite, the processing algorithm temporally composites the final dataset as each satellite’s information becomes available. The SatCORPS team has leveraged our experience using Amazon Web Services (AWS) to build a low latency high availability tool that allows end users both human and automated to acquire high quality and high-resolution Geostationary Earth Orbiting (GEO) information at zero cost to the end user. This presentation will describe how we architected and implemented the service as well as lessons learned based on our experiences both developing and operating the system. The lessons learned include how we integrated multiple services including Amazon Batch, Amazon S3 and Amazon Lambda service to create a low cost but high-performance processing system that is capable of identifying and processing the most appropriate satellite overpass information into global cloud composites. We will also describe our web-based tools including our Geographic Information System that can be used for visualization and analysis. The products from the processing can be geospatially-service enabled as ArcGIS Image Services and Open Geospatial Consortium (OGC) Web Mapping/Coverage Services for visualization and analysis via a web mapping application and common geospatial software. The SatCORPS Global Composite Cloud product provides sophisticated global composited cloud research products with very low latency that we see that as filling a rapidly growing need in the research and modelling community with no up-front nor ongoing costs associated with downloading or using the information.

AWS AMCE SMCE GCC SATCORPS GLOBAL CLOUD COMPOSITE ↗

Understanding and Predicting the Process of Software Maintenance Releases

One of the major concerns of any maintenance organization is to understand and estimate the cost of maintenance releases of software systems. Planning the next release so as to maximize the increase in functionality and the improvement in quality are vital to successful maintenance management. The objective of this paper is to present the results of a case study in which an incremental approach was used to better understand the effort distribution of releases and build a predictive effort model for software maintenance releases. This study was conducted in the Flight Dynamics Division (FDD) of NASA Goddard Space Flight Center(GSFC). This paper presents three main results: 1) a predictive effort model developed for the FDD's software maintenance release process; 2) measurement-based lessons learned about the maintenance process in the FDD; and 3) a set of lessons learned about the establishment of a measurement-based software maintenance improvement program. In addition, this study provides insights and guidelines for obtaining similar results in other maintenance organizations.

Basili, Victor↗

Mars Program Independent Assessment Team Report

The Mars Climate Orbiter failed to achieve Mars orbit on September 23, 1999. On December 3, 1999, Mars Polar Lander and two Deep Space 2 microprobes failed. As a result, the NASA Administrator established the Mars Program Independent Assessment Team (MPIAT) with the following charter: 1) Review and analyze successes and failures of recent Mars and Deep Space Missions which include: a) Mars Global Surveyor, b) Mars Climate Orbiter, c) Pathfinder, d) Mars Polar Lander, e) Deep Space 1, and f) Deep Space 2; 2) Examine the relationship between and among, NASA Jet Propulsion Laboratory (JPL), California Institute of Technology (Caltech), NASA Headquarters, and industry partners; 3) Assess effectiveness of involvement of scientists; 4) Identify lessons learned from successes and failures; 5) Review revised Mars Surveyor Program to assure lessons learned are utilized; 6) Oversee Mars Polar Lander and Deep Space 2 failure reviews; and 7) Complete by March 15, 2000. In-depth reviews were conducted at NASA Headquarters, JPL, and Lockheed Martin Astronautics (LMA). Structured reviews, informal sessions with numerous Mars Program participants, and extensive debate and discussion within the MPIAT establish the basis for this report. The review process began on January 7, 2000, and concluded with a briefing to the NASA Administrator on March 14, 2000. This report represents the integrated views of the members of the MPIAT who are identified in the appendix. In total, three related reports have been produced: a summary report, this report entitled "Mars Program Independent Assessment Team Report," and the "Report on the Loss of the Mars Polar Lander and Deep Space 2 Missions".

Young, Thomas↗

Novel Advancements in Internet-Based Real-Time Data Technologies

AZ Technology has been working with NASA MSFC (Marshall Space Flight Center) to find ways to make it easier for remote experimenters (RPI's) to monitor their International Space Station (ISS) payloads in real-time from anywhere using standard/familiar devices. That effort resulted in a product called 'EZStream' which is in use on several ISS-related projects. Although the initial implementation is geared toward ISS, the architecture and lessons learned are applicable to other space-related programs. This paper begins with a brief history on why Internet-based real-time data is important and where EZStream or products like it fit in the flow of data from orbit to experimenter/researcher. A high-level architecture is then presented along with explanations of the components used. A combination of commercial-off-the-shelf (COTS), Open Source, and custom components are discussed. The use of standard protocols is shown along with some details on how data flows between server and client. Some examples are presented to illustrate how a system like EZStream can be used in real world applications and how care was taken to make the end-user experience as painless as possible. A system such as EZStream has potential in the commercial (non-ISS) arena and some possibilities are presented. During the development and fielding of EZStream, a lot was learned. Good and not so good decisions were made. Some of the major lessons learned will be shared. The development of EZStream is continuing and the future of EZStream will be discussed to shed some light over the technological horizon.

Myers, Gerry↗

Examination of Communication Delays on Team Performance: Utilizing the International Space Station (ISS) as a Test Bed for Analog Research

Operational conjectures about space exploration missions of the future indicate that space crews will need to be more autonomous from mission control and operate independently. This is in part due to the expectation that communication quality between the ground and exploration crews will be more limited and delayed. Because of potential adverse effects on communication quality, both researchers and operational training and engineering experts have suggested that communication delays and the impact these delays have on the quality of communications to the crew will create performance decrements if crews are not given adequate training and tools to support more autonomous operations. This presentation will provide an overview of a research study led by the Behavioral Health and Performance Element (BHP) of the NASA Human Research Program that examines the impact of implementing a communication delay on ISS on individual and team factors and outcomes, including performance and related perceptions of autonomy. The methodological design, data collection efforts, and initial results of this study to date will be discussed . The results will focus on completed missions, DRATS and NEEMO15. Lessons learned from implementing this study within analog environments will also be discussed. One lesson learned is that the complexities of garnishing a successful data collection campaign from these high fidelity analogs requires perseverance and a strong relationship with operational experts. Results of this study will provide a preliminary understanding of the impact of communication delays on individual and team performance as well as an insight into how teams perform and interact in a space-like environment . This will help prepare for implementation of communication delay tests on the ISS, targeted for Increment 35/36.

Keeton, K. E.↗

Visualizations to Aid Decision-Making in the ACCP Value Framework

The Aerosols, Clouds, Convection, and Precipitation Value Framework is used to introduce structure, transparency, and traceability into the decision-making process for a study formulating and assessing potential observing system concepts to respond to the 2017-2027 Decadal Survey for Earth Science and Applications. Within the Value Framework, visualizations play an important role in presenting information and structuring conversations around that information. This paper describes three guiding principles that were applied to the design of the visualizations of the Value Framework, presents examples of visualizations that serve at least one of several functions (structuring communication, facilitating elicitation and aggregation of data, and summarizing complex information), and identifies lessons learned from the development and implementation of those visualizations. The guiding principles and lessons learned have not only contributed to the success of the Value Framework and the ACCP study, but also can be applied in other decision-making activities.

Christopher A. Jones↗

Visualizations to Aid Decision-Making in the ACCP Value Framework

The Aerosols, Clouds, Convection, and Precipitation Value Framework is used to introduce structure, transparency, and traceability into the decision-making process for a study formulating and assessing potential observing system concepts to respond to the 2017-2027 Decadal Survey for Earth Science and Applications. Within the Value Framework, visualizations play an important role in presenting information and structuring conversations around that information. This paper describes three guiding principles that were applied to the design of the visualizations of the Value Framework, presents examples of visualizations that serve at least one of several functions (structuring communication, facilitating elicitation and aggregation of data, and summarizing complex information), and identifies lessons learned from the development and implementation of those visualizations. The guiding principles and lessons learned have not only contributed to the success of the Value Framework and the ACCP study, but also can be applied in other decision-making activities.

Christopher A Jones↗

Telescience testbed pilot program, volume 2: Program results

Space Station Freedom and its associated labs, coupled with the availability of new computing and communications technologies, have the potential for significantly enhancing scientific research. A Telescience Testbed Pilot Program (TTPP), aimed at developing the experience base to deal with issues in the design of the future information system of the Space Station era. The testbeds represented four scientific disciplines (astronomy and astrophysics, earth sciences, life sciences, and microgravity sciences) and studied issues in payload design, operation, and data analysis. This volume, of a 3 volume set, which all contain the results of the TTPP, contains the integrated results. Background is provided of the program and highlights of the program results. The various testbed experiments and the programmatic approach is summarized. The results are summarized on a discipline by discipline basis, highlighting the lessons learned for each discipline. Then the results are integrated across each discipline, summarizing the lessons learned overall.

Leiner, Barry M.↗

Helpful hints to painless payload processing

The helpful hints herein describe, from a system perspective, the functional flow of hardware and software. The flow will begin at the experiment development stage and continue through build-up, test, verification, delivery, launch and deintegration of the experiment. An effort will be made to identify those interfaces and transfer functions of processing that can be improved upon in the new world of 'Faster, Better, and Cheaper.' The documentation necessary to ensure configuration and processing requirements satisfaction will also be discussed. Hints and suggestions for improvements to enhance each phase of the flow will be derived from extensive experience and documented lessons learned. Charts will be utilized to define the functional flow and a list of 'lessons learned' will be addressed to show applicability. In conclusion, specific improvements for several areas of hardware processing, procedure development and quality assurance, that are generic to all Small Payloads, will be identified.

Terhune, Terry↗

Using Pilots to Assess the Value and Approach of CMMI Implementation

At Goddard Space Flight Center (GSFC), we have chosen to use Capability Maturity Model Integrated (CMMI) to guide our process improvement program. Projects at GSFC consist of complex systems of software and hardware that control satellites, operate ground systems, run instruments, manage databases and data and support scientific research. It is a challenge to launch a process improvement program that encompasses our diverse systems, yet is manageable in terms of cost effectiveness. In order to establish the best approach for improvement, our process improvement effort was divided into three phases: 1) Pilot projects; 2) Staged implementation; and 3) Sustainment and continual improvement. During Phase 1 the focus of the activities was on a baselining process, using pre-appraisals in order to get a baseline for making a better cost and effort estimate for the improvement effort. Pilot pre-appraisals were conducted from different perspectives so different approaches for process implementation could be evaluated. Phase 1 also concentrated on establishing an improvement infrastructure and training of the improvement teams. At the time of this paper, three pilot appraisals have been completed. Our initial appraisal was performed in a flight software area, considering the flight software organization as the organization. The second appraisal was done from a project perspective, focusing on systems engineering and acquisition, and using the organization as GSFC. The final appraisal was in a ground support software area, again using GSFC as the organization. This paper will present our initial approach, lessons learned from all three pilots and the changes in our approach based on the lessons learned.

Godfrey, Sara↗

Notional Airspace Operations Demonstration Plan

The airspace operations demonstration (AOD) is intended to show that the Access 5 Step 1 functional requirements can be met. The demonstration will occur in two phases. The initial on-range phase will be carried out in restricted airspace to demonstrate the cooperative collision avoidance (CCA) functional requirements and to provide risk-reduction for the AOD by allowing the test team to rehearse some elements of the demonstration mission. The CCA system to be used in these flights is based on Automatic Dependent Surveillance-Broadcast (ADS-B) which is a commercially-available system by which airplanes constantly broadcast their current position and altitude to other aircraft and ground resources over a dedicated radio datalink. The final phase will occur in the national airspace (NAS) and will be the formal demonstration of the remainder of the proposed functional requirements. The general objectives of the AOD are as follows: (1) Demonstrate that the UAS can aviate in the NAS (2) Demonstrate that the UAS can navigate in the NAS (3) Demonstrate that the UAS can communicate with the NAS (4) Demonstrate that the UAS can perform selected collision avoidance functions in the NAS (5) Demonstrate that the UAS can evaluate and avoid weather conflicts in the NAS (6) Demonstrate that the UAS can provide adequate command and control in the NAS In addition to the stated objectives, there are a number of goals for the flight demonstration. The demo can be accomplished successfully without achieving these goals, but these goals are to be used as a guideline for preparing for the mission. The goals are: (1) Mission duration of at least 24 hours (2) Loiter over heavy traffic to evaluate the data block issue identified during the Access 5 Airspace Operations Simulations (3) Document the contingency management process and lessons learned (4) Document the coordination process for Ground Control Stations (GCS) handoff (5) Document lessons learned regarding the process of flying in the NAS Preliminary planning for a notional mission to achieve the objectives and goals has been prepared. The planning is intended to serve as a guide for detailed planning of the AOD.

Trongale, Nicholas A.↗

Detecting and Characterizing Patterns of Failure in Complex Engineered Systems: an Ontology Development and Clustering Approach

While the causes of failures in complex engineered systems are often clear in hindsight, it can be challenging to predict failures proactively during the design of novel engineered products or systems. Identifying patterns can be useful for capturing common characteristics that may lead to failure. In this paper, we present a methodology for identifying patterns of failure from NASA’s publicly available Lessons Learned Information System (LLIS). We apply an ontology development and clustering approach to identify representative patterns leading to failures in historical lessons learned. A joint inductive-deductive approach reveals the key themes in lessons that lead to failure, which are formalized and recorded as an ontology of complex systems failure causes. Documents from the LLIS are manually tagged with relevant characteristics from the ontology. From the tagged set, clustering is used to capture co-occurring sets of characteristics that lead to failure. The primary contribution of this work is a method for extracting a set of generic failure patterns in complex engineered systems and characteristics for these patterns that can be identified at design time, knowledge of which can be used to plan mitigation strategies.

Systems Engineering↗

Detecting and Characterizing Patterns of Failure in Complex Systems: An Ontology Development and Clustering Approach

While the causes of failures in complex engineered systems are often clear in hindsight, it can be challenging to predict failures proactively during the design of novel engineered products or systems. Identifying patterns can be useful for capturing common characteristics that may lead to failure. In this paper, we present a methodology for identifying patterns of failure from NASA’s publicly available Lessons Learned Information System (LLIS). We apply an ontology development and clustering approach to identify representative patterns leading to failures in historical lessons learned. A joint inductive-deductive approach reveals the key themes in lessons that lead to failure, which are formalized and recorded as an ontology of complex systems failure causes. Documents from the LLIS are manually tagged with relevant characteristics from the ontology. From the tagged set, clustering is used to capture co-occurring sets of characteristics that lead to failure. The primary contribution of this work is a method for extracting a set of generic failure patterns in complex engineered systems and characteristics for these patterns that can be identified at design time, knowledge of which can be used to plan mitigation strategies.

Systems Engineering↗

Eleven Countries, an Integrated Spacecraft: the Story of International Collaboration that Built the Orion Spacecraft and Powered the Success of the Artemis I Mission

The quest to return humans to the Moon in the next step towards humanity's exploration of space is more alive than ever. After a great deal of achievements, failures, and lessons learned, the Artemis I mission set o to the Moon on November 16, 2022, with the goal of testing a new rocket, the Space Launch System, and a new spacecraft, Orion: designed, assembled, and tested across two continents, and 11 countries. Behind this mission, decades of experience with the International Space Station, Autonomous Transfer Vehicle operations, and many other program collaborations built the know-how on how to succeed together in the toughest environment | deep space. The Artemis I mission proved to be an incredible success, meeting 161 total mission objectives, including 21 developed during the flight based on outperforming spacecraft. It was also a case-study in international collaboration, given that ESA, NASA, and industry partners Airbus and Lockheed Martin for the first time had to design, build, test, and fly a fully integrated human-rated spacecraft, with most critical functions dependent and interconnected across U.S. and European systems. The U.S.-built Orion Crew Module and Crew Module Adapter and European-built European Service Module (ESM) shared critical interfaces and commodities, from propulsion, avionics, active/passive thermal, electrical power generation, storage and distribution to the software that managed it all. In this paper, we will describe relevant aspects of the integrated spacecraft design, providing context for the challenges that the team faced in all phases required to get Orion ready to fly, and provide a direct account of how the joint team formed, trained, and supported the operations of the successful Artemis I mission. We will also explore the evolution of the partnerships, given that these allow a multi-national e ort to sustain the program production, share costs, leverage a broader base of engineering expertise, and build more diverse capabilities over the long haul to support the Artemis goals and objectives. Lastly, we will cover critical lessons learned and how the Orion Program has implemented these in preparation of the next Artemis missions to repeat the success of Artemis I. The purpose of this paper is to document knowledge we gained and lessons we learned through the development of an integrated Orion spacecraft, since it is imperative we build on this now, at the dawn of the Artemis Program, an international endeavor to push human space exploration.

Deep Space Exploration↗

Small Satellite Reliability Initiative (SSRI) Knowledge Base Tool: Update and Future Direction

NASA’s Small Satellite Reliability Initiative (SSRI), in conjunction with NASA’s Small Spacecraft Systems Virtual Institute (S3VI), has developed the SSRI Knowledge Base to improve mission confidence for small spacecraft. The SSRI Knowledge Base is a comprehensive and searchable online tool that consolidates and organizes resources, best practices, and lessons learned from previous small satellite missions sponsored by NASA, other government agencies, and academia. This free, publicly available tool is available to the entire SmallSat community at: NASA SSRI Knowledge Base | Explore. The SSRI Knowledge Base provides vetted, high-quality sources of information on elements that are key to successful small satellite missions. These resources include SSRI working group generated documents and presentations in addition to existing guides, publications, standards, software tools, websites, and books. The Knowledge Base is fully searchable, offers downloadable content when possible, and otherwise links to or references content directly from within the tool. All 58 of the planned topic pages that comprise the SSRI Knowledge Base have been recently completed and include over 450 unique resources that are now available for review. Over the past several months significant enhancements to the tool’s capabilities have been developed and implemented. These enhancements consist of the completed baseline content; development of an Application Programming Interface (API); improved user interfaces; scalable and searchable Best Practices and Lessons Learned (BPLL) lists with ratings; and custom website analytics. This presentation and paper will discuss the motivation for and development of the SSRI Knowledge Base, demonstrate the existing tool, and outline plans for further development. The SSRI is a collaborative activity with broad participation from civil, Department of Defense, and both national and international commercial space systems providers and stakeholders. The S3VI is jointly sponsored by NASA’s Space Technology Mission Directorate and Science Mission Directorate.

Small Spacecraft↗

Small Satellite Reliability Initiative (SSRI) Knowledge Base Tool: Update and Future Direction

NASA’s Small Satellite Reliability Initiative (SSRI), in conjunction with NASA’s Small Spacecraft Systems Virtual Institute (S3VI), has developed the SSRI Knowledge Base to improve mission confidence for small spacecraft. The SSRI Knowledge Base is a comprehensive and searchable online tool that consolidates and organizes resources, best practices, and lessons learned from previous small satellite missions sponsored by NASA, other government agencies, and academia. This free, publicly available tool is available to the entire SmallSat community at: NASA SSRI Knowledge Base | Explore. The SSRI Knowledge Base provides vetted, high-quality sources of information on elements that are key to successful small satellite missions. These resources include SSRI working group generated documents and presentations in addition to existing guides, publications, standards, software tools, websites, and books. The Knowledge Base is fully searchable, offers downloadable content when possible, and otherwise links to or references content directly from within the tool. All 58 of the planned topic pages that comprise the SSRI Knowledge Base have been recently completed and include over 450 unique resources that are now available for review. Over the past several months significant enhancements to the tool’s capabilities have been developed and implemented. These enhancements consist of the completed baseline content; development of an Application Programming Interface (API); improved user interfaces; scalable and searchable Best Practices and Lessons Learned (BPLL) lists with ratings; and custom website analytics. This presentation and paper will discuss the motivation for and development of the SSRI Knowledge Base, demonstrate the existing tool, and outline plans for further development. The SSRI is a collaborative activity with broad participation from civil, Department of Defense, and both national and international commercial space systems providers and stakeholders. The S3VI is jointly sponsored by NASA’s Space Technology Mission Directorate and Science Mission Directorate.

Small Spacecraft↗