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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Rapid Spacecraft Development: Results and Lessons Learned

The Rapid Spacecraft Development Office (RSDO) at NASA's Goddard Space Flight Center is responsible for the management and direction of a dynamic and versatile program for the definition, competition, and acquisition of multiple indefinite delivery and indefinite quantity contracts - resulting in a catalog of spacecraft buses. Five spacecraft delivery orders have been placed by the RSDO and one spacecraft has been launched. Numerous concept and design studies have been performed, most with the intent of leading to a future spacecraft acquisition. A collection of results and lessons learned is recorded to highlight management techniques, methods and processes employed in the conduct of spacecraft acquisition. Topics include working relationships under fixed price delivery orders, price and value, risk management, contingency reserves, and information restrictions.

Watson, William A.↗
NASA NTRS2008

Implementation Challenges for Multivariable Control: What You Did Not Learn in School

Multivariable control allows controller designs that can provide decoupled command tracking and robust performance in the presence of modeling uncertainties. Although the last two decades have seen extensive development of multivariable control theory and example applications to complex systems in software/hardware simulations, there are no production flying systems aircraft or spacecraft, that use multivariable control. This is because of the tremendous challenges associated with implementation of such multivariable control designs. Unfortunately, the curriculum in schools does not provide sufficient time to be able to provide an exposure to the students in such implementation challenges. The objective of this paper is to share the lessons learned by a practitioner of multivariable control in the process of applying some of the modern control theory to the Integrated Flight Propulsion Control (IFPC) design for an advanced Short Take-Off Vertical Landing (STOVL) aircraft simulation.

Garg, Sanjay↗
NASA NTRS2008

Building on the Past - Looking to the Future: A Focus on Payload Safety

The history of the space industry stretches far and above lunar landings to the construction of the International Space Station. For years, humans have sought to understand the nature of the universe. As society grows in knowledge and curiosity of space, the focus of maintaining the safety of the crew and vehicle habitability is of utmost importance to the National Aeronautics and Space Administration (NASA) community. Through the years, Payload Safety has developed not only as a Panel, but also as part of the NASA community, striving to enhance the efficiency and understanding of how business should be conducted as more International Partners become involved. This is the first in a series of papers and presentations in what is hoped to be an annual update that provides continuous challenges and lessons learned in the areas of communication, safety requirements and processes and other areas which have been vital to the Payload Safety Review Panel (PSRP).

Nash, Sally K.↗
NASA NTRS2008

In-Flight Anomalies and Radiation Performance of NASA Missions - Selected Lessons Learned

This presentation addresses in-flight electronic disturbances and radiation, specifically anomaly resolution. The process for anomaly review takes into account the environment, selected parts and design, existing and/or new radiation test data, risk probability and actions to be taken. Noise spikes and the meaning of upset in a fiber optic link are also discussed.

LaBel, Kenneth A.↗
NASA NTRS2010

Building on the Past - Looking to the Future. Part 2: A Focus on Expanding Horizons

The history of space endeavors stretches far from the first liquid-fueled rocket created by the father of modern rocketry, Robert Goddard, in 1926 and will certainly extend far beyond the construction of the International Space Station (ISS) scheduled to be complete with the addition of the Permanent Multipurpose Module on STS-133/ULF5. National Aeronautics and Space Administration (NASA) and the ISS International Partners (IPs) will be the unrelenting venue used to satisfy the curiosities of man as we seek an understanding of space through various experiments (also referred to as payloads) conducted in microgravity. The NASA Payload Safety Review Panel (PSRP) continues to serve as the lead for the review and assessment of payload hardware to assure facility and crew safety. This is the second in a series of papers and presentations that illustrate challenges and lessons learned in the areas of communication, safety requirements, and processes which have been vital to the PSRP.

Nash, Sally K.↗
NASA NTRS2011

Morpheus Lander Testing Campaign

NASA s Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing designed to serve as a testbed for advanced spacecraft technologies. The Morpheus vehicle has successfully performed a set of integrated vehicle test flights including hot-fire and tether tests, ultimately culminating in an un-tethered "free-flight" This development and testing campaign was conducted on-site at the Johnson Space Center (JSC), less than one year after project start. Designed, developed, manufactured and operated in-house by engineers at JSC, the Morpheus Project represents an unprecedented departure from recent NASA programs and projects that traditionally require longer development lifecycles and testing at remote, dedicated testing facilities. This paper documents the integrated testing campaign, including descriptions of test types (hot-fire, tether, and free-flight), test objectives, and the infrastructure of JSC testing facilities. A major focus of the paper will be the fast pace of the project, rapid prototyping, frequent testing, and lessons learned from this departure from the traditional engineering development process at NASA s Johnson Space Center.

Hart, Jeremy J.↗
NASA NTRS2013

Project Morpheus: Lessons Learned in Lander Technology Development

NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing, that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. Designed, developed, manufactured and operated in-house by engineers at Johnson Space Center, the initial flight test campaign began on-site at JSC less than one year after project start. After two years of testing, including two major upgrade periods, and recovery from a test crash that caused the loss of a vehicle, flight testing will evolve to executing autonomous flights simulating a 500m lunar approach trajectory, hazard avoidance maneuvers, and precision landing, incorporating the Autonomous Landing and Hazard Avoidance (ALHAT) sensor suite. These free-flights are conducted at a simulated planetary landscape built at Kennedy Space Center's Shuttle Landing Facility. The Morpheus Project represents a departure from recent NASA programs and projects that traditionally require longer development lifecycles and testing at remote, dedicated testing facilities. This paper expands on the project perspective that technologies offer promise, but capabilities offer solutions. It documents the integrated testing campaign, the infrastructure and testing facilities, and the technologies being evaluated in this testbed. The paper also describes the fast pace of the project, rapid prototyping, frequent testing, and lessons learned during this departure from the traditional engineering development process at NASA's Johnson Space Center.

Olansen, Jon B.↗
NASA NTRS2013

Aircraft Engine Gas Path Diagnostic Methods: Public Benchmarking Results

Recent technology reviews have identified the need for objective assessments of aircraft engine health management (EHM) technologies. To help address this issue, a gas path diagnostic benchmark problem has been created and made publicly available. This software tool, referred to as the Propulsion Diagnostic Method Evaluation Strategy (ProDiMES), has been constructed based on feedback provided by the aircraft EHM community. It provides a standard benchmark problem enabling users to develop, evaluate and compare diagnostic methods. This paper will present an overview of ProDiMES along with a description of four gas path diagnostic methods developed and applied to the problem. These methods, which include analytical and empirical diagnostic techniques, will be described and associated blind-test-case metric results will be presented and compared. Lessons learned along with recommendations for improving the public benchmarking processes will also be presented and discussed.

Simon, Donald L.↗
NASA NTRS2015

Space Launch System Liftoff and Transition Aerodynamic Characterization in the NASA Langley 14- by 22-Foot Subsonic Wind Tunnel

A 1.75% scale force and moment model of the Space Launch System was tested in the NASA Langley Research Center 14- by 22-Foot Subsonic Wind Tunnel to quantify the aerodynamic forces that will be experienced by the launch vehicle during its liftoff and transition to ascent flight. The test consisted of two parts: the first was dedicated to measuring forces and moments for the entire range of angles of attack (0deg to 90deg) and roll angles (0 deg. to 360 deg.). The second was designed to measure the aerodynamic effects of the liftoff tower on the launch vehicle for ground winds from all azimuthal directions (0 deg. to 360 deg.), and vehicle liftoff height ratios from 0 to 0.94. This wind tunnel model also included a set of 154 surface static pressure ports. Details on the experimental setup, and results from both parts of testing are presented, along with a description of how the wind tunnel data was analyzed and post-processed in order to develop an aerodynamic database. Finally, lessons learned from experiencing significant dynamics in the mid-range angles of attack due to steady asymmetric vortex shedding are presented.

Pinier, Jeremy T.↗
NASA NTRS2013

Twenty Years of Systems Engineering on the Cassini-Huygens Mission

Over the past twenty years, the Cassini-Huygens Mission has successfully utilized systems engineering to develop and execute a challenging prime mission and two mission extensions. Systems engineering was not only essential in designing the mission, but as knowledge of the system was gained during cruise and science operations, it was critical in evolving operational strategies and processes. This paper discusses systems engineering successes, challenges, and lessons learned on the Cassini-Huygens Mission gathered from a thorough study of mission plans and developed scenarios, and interviews with key project leaders across its twenty-year history.

Manor-Chapman, Emily↗
NASA NTRS2022

Verification and Validation of Hybridspectral Radiometry Obtained from an Unmanned Surface Vessel (USV) in the Open and Coastal Oceans

The hardware and software capabilities of the compact-profiling hybrid instrumentation for radiometry and ecology (C-PHIRE) instruments on an unmanned surface vessel (USV) are evaluated. Both the radiometers and USV are commercial-off-the-shelf (COTS) products, with the latter being only minimally modified to deploy the C-PHIRE instruments. The hybridspectral C-PHIRE instruments consist of an array of 18 multispectral microradiometers with 10 nm wavebands spanning 320–875 nm plus a hyperspectral compact grating spectrometer (CGS) with 2048 pixels spanning 190–1000 nm. The C-PHIRE data were acquired and processed using two architecturally linked software packages, thereby allowing lessons learned in one to be applied to the other. Using standard data products and unbiased statistics, the C-PHIRE data were validated with those from the well-established compact-optical profiling system (C-OPS) and verified with the marine optical buoy (MOBY). Agreement between algorithm variables used to estimate colored dissolved organic matter (CDOM) absorption and chlorophyll a concentration were also validated. Developing and operating novel technologies, such as the C-PHIRE series of instruments, deployed on a USV increase the frequency and coverage of optical observations, which are required to fully support the present and next-generation validation exercises in radiometric remote sensing of aquatic ecosystems.

Hybridspectral↗
NASA NTRS2006

Lunar e-Library: Putting Space History to Work

As NASA plans and implements the Vision for Space Exploration, managers, engineers, and scientists need historically important information that is readily available and easily accessed. The Lunar e-Library - a searchable collection of 1100 electronic (.PDF) documents - makes it easy to find critical technical data and lessons learned and put space history knowledge in action. The Lunar e-Library, a DVD knowledge database, was developed by NASA to shorten research time and put knowledge at users' fingertips. Funded by NASA's Space Environments and Effects (SEE) Program headquartered at Marshall Space Flight Center (MSFC) and the MSFC Materials and Processes Laboratory, the goal of the Lunar e- Library effort was to identify key lessons learned from Apollo and other lunar programs and missions and to provide technical information from those programs in an easy-to-use format. The SEE Program began distributing the Lunar e-Library knowledge database in 2006. This paper describes the Lunar e-Library development process (including a description of the databases and resources used to acquire the documents) and the contents of the DVD product, demonstrates its usefulness with focused searches, and provides information on how to obtain this free resource.

McMahan, Tracy A.↗
NASA NTRS2017

Lessons Learned from Preparing OSIRIS-REx Spectral Analog Samples for Bennu

NASA's OSIRIS-REx sample return mission launched on September 8th, 2016 to rendezvous with B-type asteroid (101955) Bennu in 2018. Type C and B asteroids have been linked to carbonaceous chondrites because of their similar visible - to - near infrared (VIS-NIR) spectral properties [e.g., 1,2]. The OSIRIS-REx Visible and Infrared Spectrometer (OVIRS) and the Thermal Emission Spectrometer (OTES) will make spectroscopic observations of Bennu during the encounter. Constraining the presence or absence of hydrous minerals (e.g., Ca-carbonate, phyllosilicates) and organic molecules will be key to characterizing Bennu [3] prior to sample site selection. The goal of this study was to develop a suite of analog and meteorite samples and obtain their spectral properties over the wavelength ranges of OVIRS (0.4- 4.3 micrometer) and OTES (5.0-50 micrometer). These spectral data were used to validate the mission science-data processing system. We discuss the reasoning behind the study and share lessons learned.

Schrader, D. L.↗
NASA NTRS2017

Cleared for Launch - Lessons Learned from the OSIRIS-REx System Requirements Verification Program

Requirements verification of a large flight system is a challenge. It is especially challenging for engineers taking on their first role in space systems engineering. This paper describes our approach to verification of the Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) system requirements. It also captures lessons learned along the way from developing systems engineers embroiled in this process. We begin with an overview of the mission and science objectives as well as the project requirements verification program strategy. A description of the requirements flow down is presented including our implementation for managing the thousands of program and element level requirements and associated verification data. We discuss both successes and methods to improve the managing of this data across multiple organizational interfaces. Our approach to verifying system requirements at multiple levels of assembly is presented using examples from our work at instrument, spacecraft, and ground segment levels. We include a discussion of system end-to-end testing limitations and their impacts to the verification program. Finally, we describe lessons learned that are applicable to all emerging space systems engineers using our unique perspectives across multiple organizations of a large NASA program.

Requirements Verification↗
NASA NTRS2000

Session on High Speed Civil Transport Design Capability Using MDO and High Performance Computing

Since the inception of CAS in 1992, NASA Langley has been conducting research into applying multidisciplinary optimization (MDO) and high performance computing toward reducing aircraft design cycle time. The focus of this research has been the development of a series of computational frameworks and associated applications that increased in capability, complexity, and performance over time. The culmination of this effort is an automated high-fidelity analysis capability for a high speed civil transport (HSCT) vehicle installed on a network of heterogeneous computers with a computational framework built using Common Object Request Broker Architecture (CORBA) and Java. The main focus of the research in the early years was the development of the Framework for Interdisciplinary Design Optimization (FIDO) and associated HSCT applications. While the FIDO effort was eventually halted, work continued on HSCT applications of ever increasing complexity. The current application, HSCT4.0, employs high fidelity CFD and FEM analysis codes. For each analysis cycle, the vehicle geometry and computational grids are updated using new values for design variables. Processes for aeroelastic trim, loads convergence, displacement transfer, stress and buckling, and performance have been developed. In all, a total of 70 processes are integrated in the analysis framework. Many of the key processes include automatic differentiation capabilities to provide sensitivity information that can be used in optimization. A software engineering process was developed to manage this large project. Defining the interactions among 70 processes turned out to be an enormous, but essential, task. A formal requirements document was prepared that defined data flow among processes and subprocesses. A design document was then developed that translated the requirements into actual software design. A validation program was defined and implemented to ensure that codes integrated into the framework produced the same results as their standalone counterparts. Finally, a Commercial Off the Shelf (COTS) configuration management system was used to organize the software development. A computational environment, CJOPT, based on the Common Object Request Broker Architecture, CORBA, and the Java programming language has been developed as a framework for multidisciplinary analysis and Optimization. The environment exploits the parallelisms inherent in the application and distributes the constituent disciplines on machines best suited to their needs. In CJOpt, a discipline code is "wrapped" as an object. An interface to the object identifies the functionality (services) provided by the discipline, defined in Interface Definition Language (IDL) and implemented using Java. The results of using the HSCT4.0 capability are described. A summary of lessons learned is also presented. The use of some of the processes, codes, and techniques by industry are highlighted. The application of the methodology developed in this research to other aircraft are described. Finally, we show how the experience gained is being applied to entirely new vehicles, such as the Reusable Space Transportation System. Additional information is contained in the original.

Rehder, Joe↗
NASA NTRSDate not supplied

What You Need to Know about Planetary Protection Categorization for Your Mission

Planetary protection mission categorization helps to define the risk posture for requirements definition and implementation practices on space flight projects with planetary protection considerations. NASA has recently updated it’s planetary protection policy (NPR 8715.24), and with the update comes a major change in how the planetary protection categorization process is performed for NASA missions. Previously, projects would request the NASA Planetary Protection Officer (PPO) provide a categorization letter documenting the planetary protection category assigned to the proposed mission. Under the new policy the project manager (PM) proposes the planetary protection category for their mission. Depending on the level of the category, the PPO either concurs or recommends concurrence to the Chief of Safety and Mission Assurance (SMA) before forwarding to the Mission Directorate Associate Administrator (MDAA) for final approval prior to the system requirements review (SRR). But what topics must be considered for categorization? This presentation will provide key considerations for planetary protection mission categorization including the target solar system body to be explored, the trajectory to get to the target body, and the operations to be performed at the target body. Additional unique scenarios such as secondary and auxiliary payloads, encountering other solar system bodies on the way to the target body, and sample return missions will also be discussed to share lessons learned from missions that have been through the new categorization process.

Elaine Seasly↗
NASA NTRS2011

2010 CEOS Field Reflectance Intercomparisons Lessons Learned

This paper summarizes lessons learned from the 2009 and 2010 joint field campaigns to Tuz Golu, Turkey. Emphasis is placed on the 2010 campaign related to understanding the equipment and measurement protocols, processing schemes, and traceability to SI quantities. Participants in both 2009 and 2010 used an array of measurement approaches to determine surface reflectance. One lesson learned is that even with all of the differences in collection between groups, the differences in reflectance are currently dominated by instrumental artifacts including knowledge of the white reference. Processing methodology plays a limited role once the bi-directional reflectance of the white reference is used rather than a hemispheric-directional value. The lack of a basic set of measurement protocols, or best practices, limits a group s ability to ensure SI traceability and the development of proper error budgets. Finally, rigorous attention to sampling methodology and its impact on instrument behavior is needed. The results of the 2009 and 2010 joint campaigns clearly demonstrate both the need and utility of such campaigns and such comparisons must continue in the future to ensure a coherent set of data that can span multiple sensor types and multiple decades.

Thome, Kurtis↗