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.

SourceResearch connectionFrom yearThrough year

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

At least 559 records · Page 31

All sources NASA NTRS DOE OSTI

NASA NTRS2014

Loss of Signal: Aeromedical Lessons Learned from the STS-107 Columbia Space Shuttle Mishap

The editors of Loss of Signal wanted to document the aeromedical lessons learned from the Space Shuttle Columbia mishap. The book is intended to be an accurate and easily understood account of the entire process of recovering and analyzing the human remains, investigating and analyzing what happened to the crew, and using the resulting information to recommend ways to prevent mishaps and provide better protection to crewmembers. Our goal is to capture the passions of those who devoted their energies in responding to the Columbia mishap. We have reunited authors who were directly involved in each of these aspects. These authors tell the story of their efforts related to the Columbia mishap from their point of view. They give the reader an honest description of their responsibilities and share their challenges, their experiences, and their lessons learned on how to enhance crew safety and survival, and how to be prepared to support space mishap investigations. As a result of this approach, a few of the chapters have some redundancy of information and authors' opinions may differ. In no way did we or they intend to assign blame or criticize anyone's professional efforts. All those involved did their best to obtain the truth in the situations to which they were assigned.

Stepaniak, Philip C.↗

DOE OSTI2026

Lessons Learned for Transmission Cost Allocation in U.S. Regional Markets

Expanding electric transmission can facilitate generator interconnection and improve grid reliability. Assigning costs for new transmission infrastructure is highly contentious because these costs can have a direct impact on energy prices and ratepayer bills. In this report, we evaluate what factors influence successful transmission cost allocation agreements. Through a review of legal disputes, existing cost allocation practices, and regional case studies, we identify potential strategies to minimize cost allocation disputes for future projects. The report also highlights the processes by which regions can update their cost allocation methods. While we do not consider cost allocation methods currently under development for compliance with FERC Order 1920, the trends and lessons learned identified in this report can inform discussions on effective cost allocation methods to reduce barriers for transmission development.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

NASA NTRS1989

Application of reusable software components at the SEI

Robert Holibaugh of the Software Engineering Institute described a project which is studying the application of reusable software components. The primary goals are to gain practical experience with state-of-the-art reusable components, methods, and tools and to capture the lessons learned in the application of reuse technology. In addition the project will assess the impact of reuse on the software development process and products and will identify and validate the information that facilities software reuse during system development. The project includes two tasks - a reuse experiment and a redevelopment effort. The reuse experiment will define a life cycle and a methodology for reuse-based development, and define and implement a data collection mechanism for measuring the development. The redevelopment effort will construct a reuse test bed and will redevelop and realistically test subsystems from an embedded mission-critical real-time application. The reuse experiment will produce several products including a tested real-time application, reuse-based components and tools evaluation, a reuse-based development method, a framework for data collection, a framework for measuring productivity, and lessons learned data. Successful development with reusable components will require a rich set of components and an integrating methodology. The Tomahawk Land Attack Missile system is the application for the redevelopment effort.

Holibaugh, Robert↗

DOE OSTI2023

Digitalization Guiding Principles and Method for Nuclear Industry Work Processes

The commercial U.S. light-water reactor fleet has been operating at historical efficiency, reliability, and safety over the last decade. Nuclear power has the highest capacity factor of any other power generation technology while also serving as the largest baseload source for carbon-free energy. Despite this remarkable achievement, continued operations for many plants are threatened due to fierce electricity market competition and rising operations and maintenance costs of which continued maintenance of obsolete analog equipment is a contributor. The digital age and associated technologies are where the future lies in process control, and nuclear has yet to take full advantage of the capabilities offered therein. The Light Water Reactor Sustainability Program (LWRS) at Idaho National Laboratory (INL), sponsored by the Department of Energy, has a mission to help the light-water reactor fleet manage its foundational capabilities to continue providing safe and reliable carbon-free power. LWRS helps support that mission by providing scientific, technology-based solutions for advanced concepts of operations with a more viable business model that will allow the fleet to continue to operate at peak levels through extended plant operation. The LWRS Digitalization Project at INL seeks to leverage digital technologies to synthesize and transform work processes. We provide a state-of-the-art analysis of digitalized work processes in nuclear power and investigate ways in which researchers at INL and the nuclear industry can work together to identify what data to access, how to access it, what to do with the data, and most importantly, how to use the insights for decision-making across all levels within the business. Borne from these considerations, we present four guiding principles for digitalization: develop a coherent digitalization plan, apply human factors engineering, establish data governance, and anticipate unintended consequences. Together, these principles form a method that plants can use to effectively to digitalize nuclear industry work processes. Our guiding principles are informed by multiple knowledge sources. First, we document activities from the Work Digitalization Initiative, which was conceived as a means for nuclear organizations to help define and standardize the industry’s approach to digitalizing work. Second, we detail primary research conducted with industry professionals regarding drivers and barriers to digitalization adoption. We present survey results that demonstrate what the industry hopes to get out of digitalization and the ways that INL can continue to support the industry’s digital transformation. Third, we present a digitalization use case with industry partners NextAxiom Technology and Xcel Energy. The project objective was to transform the current condition report work process from paper to digital, incorporating digitalized principles. We report the development of the application and lessons learned. The accomplishments achieved by this research and development serve to identify critical needs for plant guidance in support of digitalization implementation and contribute to the knowledge and strategies available for utilities considering or undertaking digitalization.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

NASA NTRS1991

The atmospheric effects of stratospheric aircraft: A topical review

In the late 1960s the aircraft industry became interested in developing a fleet of supersonic transports (SSTs). Between 1972 and 1975, the Climatic Impact Assessment Program (CIAP) studied the possible environmental impact of SSTs. For environmental and economic reasons, the fleet of SSTs was not developed. The Upper Atmosphere Research Program (UARP) has recently undertaken the responsibility of directing scientific research needed to assess the atmospheric impact of supersonic transports. The UARP and the High-Speed Research Program asked Harold Johnston to review the current understanding of aircraft emissions and their effect on the stratosphere. Johnston and his colleagues have recently re-examined the SST problem using current models for stratospheric ozone chemistry. A unique view is given here of the current scientific issues and the lessons learned since the beginning of CIAP, and it links the current research program with the assessment process that began two years ago.

Johnston, Harold S.↗

NASA NTRS2003

Biotechnology System Facility: Risk Mitigation on Mir

NASA is working with its international partners to develop space vehicles and facilities that will give researchers the opportunity to conduct scientific investigations in space. As part of this activity, NASA's Biotechnology Cell Science Program (BCSP) at the Johnson Space Center (JSC) is developing a world-class biotechnology laboratory facility for the International Space Station (ISS). This report describes the BCSP, including the role of the BTS. We identify the purpose and objectives of the BTS and a detailed description of BTS facility design and operational concept, BTS facility and experiment-specific hardware, and scientific investigations conducted in the facility. We identify the objectives, methods, and results of risk mitigation investigations of the effects of microgravity and cosmic radiation on the BTS data acquisition and control system. These results may apply to many other space experiments that use commercial, terrestrial-based data acquisition technology. Another focal point is a description of the end-to-end process of integrating and operating biotechnology experiments on a variety of space vehicles. The identification of lessons learned that can be applied to future biotechnology experiments is an overall theme of the report. We include a brief summary of the science results, but this is not the focus of the report. The report provides some discussion on the successful 130-day tissue engineering experiment performed in BTS on Mir and describes a seminal gene array investigation that identified a set of unique genes that are activated in space.

Gonda, Steve R., III↗

NASA NTRS2014

Enhanced International Space Station Ku-Band Telemetry Service

The International Space Station (ISS) is in an operational configuration. To fully utilize the ISS and take advantage of the modern protocols and updated Ku-band access, the Huntsville Operations Support Center (HOSC) has designed an approach to extend the Kuband forward link access for payload investigators to their on-orbit payloads. This dramatically increases the ground to ISS communications for those users. This access also enables the ISS flight controllers operating in the Payload Operations and Integration Center to have more direct control over the systems they are responsible for managing and operating. To extend the Ku-band forward link to the payload user community the development of a new command server is necessary. The HOSC subsystems were updated to process the Internet Protocol Encapsulated packets, enable users to use the service based on their approved services, and perform network address translation to insure that the packets are forwarded from the user to the correct payload repeating that process in reverse from ISS to the payload user. This paper presents the architecture, implementation, and lessons learned. This will include the integration of COTS hardware and software as well as how the device is incorporated into the operational mission of the ISS. Thus, this paper also discusses how this technology can be applicable to payload users of the ISS.

Cecil, Andrew J.↗

NASA NTRS2016

V&V on a NASA Technology Demonstration Project: Low Density Supersonic Decelerator

Given their smaller budgets, but higher allowed risk posture, technology demonstration missions face different Verification and Validation (V&V) challenges than typical NASA missions. Despite these challenges, the Low Density Supersonic Decelerator (LDSD) project, managed by NASA’s Jet Propulsion Laboratory (JPL), has been extremely successful in testing new supersonic atmospheric decelerator technologies. A contribution to the project’s success is the unique V&V program that emphasized efficiency and flexibility. This paper will provide an overview of LDSD test objectives, Supersonic Flight Dynamics Tests (SFDT) performed so far, unique requirements structure and V&V processes implemented. The paper will focus on the V&V of the SFDT test architecture. Furthermore, lessons learned will also be presented at the end of the paper to aid future technology demonstration projects.

Murry, Michael L.↗

NASA NTRS2007

CFD to Flight: Some Recent Success Stories of X-plane Design to Flight Test at the NASA Dryden Flight Research Center

Several examples from the past decade of success stories involving the design and ight test of three true X-planes will be described: in particular, X-plane design techniques that relied heavily upon computational fluid dynamics (CFD). Three specific examples chosen from the authors personal experience are presented: the X-36 Tailless Fighter Agility Research Aircraft, the X-45A Unmanned Combat Air Vehicle, and, most recently, the X-48B Blended Wing Body Demonstrator Aircraft. An overview will be presented of the uses of CFD analysis, comparisons and contrasts with wind tunnel testing, and information derived from the CFD analysis that directly related to successful flight test. Some lessons learned on the proper application, and misapplication, of CFD are illustrated. Finally, some highlights of the flight-test results of the three example X-planes will be presented. This overview paper will discuss some of the authors experience with taking an aircraft shape from early concept and three-dimensional modeling through CFD analysis, wind tunnel testing, further re ned CFD analysis, and, finally, flight. An overview of the key roles in which CFD plays well during this process, and some other roles in which it does not, are discussed. How wind tunnel testing complements, calibrates, and verifies CFD analysis is also covered. Lessons learned on where CFD results can be misleading are also given. Strengths and weaknesses of the various types of ow solvers, including panel methods, Euler, and Navier-Stokes techniques, are discussed. The paper concludes with the three specific examples, including some flight test video footage of the X-36, the X-45A, and the X-48B.

Cosentino, Gary B.↗

NASA NTRS2007

CFD to Flight: Some Recent Success Stories of X-Plane Design to Flight Test at the NASA Dryden Flight Research Center

Several examples from the past decade of success stories involving the design and flight test of three true X-planes will be described: in particular, X-plane design techniques that relied heavily upon computational fluid dynamics (CFD). Three specific examples chosen from the author s personal experience are presented: the X-36 Tailless Fighter Agility Research Aircraft, the X-45A Unmanned Combat Air Vehicle, and, most recently, the X-48B Blended Wing Body Demonstrator Aircraft. An overview will be presented of the uses of CFD analysis, comparisons and contrasts with wind tunnel testing, and information derived from the CFD analysis that directly related to successful flight test. Some lessons learned on the proper application, and misapplication, of CFD are illustrated. Finally, some highlights of the flight-test results of the three example X-planes will be presented. This overview paper will discuss some of the author s experience with taking an aircraft shape from early concept and three-dimensional modeling through CFD analysis, wind tunnel testing, further refined CFD analysis, and, finally, flight. An overview of the key roles in which CFD plays well during this process, and some other roles in which it does not, are discussed. How wind tunnel testing complements, calibrates, and verifies CFD analysis is also covered. Lessons learned on where CFD results can be misleading are also given. Strengths and weaknesses of the various types of flow solvers, including panel methods, Euler, and Navier-Stokes techniques, are discussed. The paper concludes with the three specific examples, including some flight test video footage of the X-36, the X-45A, and the X-48B.

Cosentino, Gary B.↗

NASA NTRS1993

Recent advances and plans in processing and geocoding of SAR data at the DFD

Because of the needs of future projects like ENVISAT and the experiences made with the current operational ERS-1 facilities, a radical change in the synthetic aperture radar (SAR) processing scenarios can be predicted for the next years. At the German PAF several new developments were initialized which are driven mainly either by user needs or by system and operational constraints ('lessons learned'). At the end there will be a major simplification and uniformation of all used computer systems. Especially the following changes are likely to be implemented at the German PAF: transcription before archiving, processing of all standard products with high throughput directly at the receiving stations, processing of special 'high-valued' products at the PAF, usage of a single type of processor hardware, implementation of a large and fast on-line data archive, and improved and unified fast data network between the processing and archiving facilities. A short description of the current operational SAR facilities as well as the future implementations are given.

Noack, W.↗

NASA NTRS2012

An Automated Sample Processing System for Planetary Exploration

An Automated Sample Processing System (ASPS) for wet chemistry processing of organic materials on the surface of Mars has been jointly developed by Ball Aerospace and the Jet Propulsion Laboratory. The mechanism has been built and tested to demonstrate TRL level 4. This paper describes the function of the system, mechanism design, lessons learned, and several challenges that were overcome.

traditional mechanical components↗

NASA NTRS2000

ACTS Ka-Band Earth Stations: Technology, Performance, and Lessons Learned

The Advanced Communications Technology Satellite (ACTS) Project invested heavily in prototype Ka-band satellite ground terminals to conduct an experiments program with ACTS. The ACTS experiments program proposed to validate Ka-band satellite and ground-station technology, demonstrate future telecommunication services, demonstrate commercial viability and market acceptability of these new services, evaluate system networking and processing technology, and characterize Ka-band propagation effects, including development of techniques to mitigate signal fading. This paper will present a summary of the fixed ground terminals developed by the NASA Glenn Research Center and its industry partners, emphasizing the technology and performance of the terminals and the lessons learned throughout their 6-year operation, including the inclined orbit phase-of-operations. The fixed ground stations used for experiments by government, academic, and commercial entities used reflector-based offset-fed antenna systems with antennas ranging in size from 0.35 to 3.4 in. in diameter. Gateway earth stations included two systems referred to as the NASA Ground Station (NGS) and the Link Evaluation Terminal (LET).

Reinhart, Richard C.↗

NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

NASA NTRS1998

NASA/Mir Phase 1: A Lesson Learned in Long Duration Mission Planning and Operations

The NASA/Mir Phase I Program is a precursor to the assembly and operations of the International Space Station (ISS). The Phase I Program covers a four-year period and encompasses over ten shuttle flights to the Mir, culminating with the flight of STS-91 in June 1998. The Mir-Orbiting Station (Mir-OS) provides an excellent environment, both onboard and on the ground, for learning and studying the characteristics associated with crew-tended operations on long duration missions. By the end of the Phase I program, NASA astronauts will have accumulated over two years of continuous operations experience working and living onboard the Mir-OS. Ground controllers, working in Russia and at remote sites in the United States, will have gained valuable experience in the generation, maintenance, and coordination of the information and products required to support the long duration crew members onboard the Mir-OS. The experience gained by the crew and ground support personnel in the area of long duration mission operations has resulted in a number of factors that need to be considered in the definition and implementation of the processes and products for the ISS. While there are many areas in which experience has been gained, this paper focuses on the lessons learned regarding the level of detail and flexibility of crew timelines. Provided in this paper is an overview of the characteristics associated with long duration mission timeline development and execution, a summary of applicable lessons learned identified and documented through participation in the NASA/Mir Phase I Program, a detailed discussion of "Gross Timelines" as implementation which addresses the lessons learned. Also discussed are the challenges that must be overcome in getting the ISS program to recognize, evaluate, and learn from the crew and ground controller experience gained through participation in the NASA/Mir Phase I Program.

Hagopian, Jeff↗

NASA NTRS2005

The Pore Formation and Mobility Investigation: A Case Study for Conducting Research on the International Space Station in Support of Exploration

The Pore Formation and Mobility Investigation (PFMI) is being conducted in the Microgravity Science Glovebox (MSG) aboard the International Space Station (ISS) with the goal of understanding bubble generation and interactions during controlled directional solidification processing. Through the course of the experiments, beginning in September 2002, a number of key factors pertinent to solidification processing of materials in a microgravity environment have been directly observed, measured, and modeled. Though most experiments ran uninterrupted, on four separate occasions malfunctions to the PFMI hardware and software were experienced that required crew intervention, including in-space repair. Fortunately, each repair attempt was successful and restored the PFMI apparatus to a fully functional condition. Based on PFMI results and lessons learned, the intent of this presentation is to draw attention to the role ISS experiments/hardware can play in providing insight to potential fabrication processing techniques and repair scenarios that might arise during long duration space transport and/or on the lunar/Mars surface.

Grugel, R. N.↗

NASA NTRS2006

The Pore Formation and Mobility Investigation: A Summary of Conducted Research on the International Space Station

Grugel, R. N.↗

NASA NTRS2010

HDU Pressurized Excursion Module (PEM) Prototype Systems Integration

The Habitat Demonstration Unit (HDU) project team constructed an analog prototype lunar surface laboratory called the Pressurized Excursion Module (PEM). The prototype unit subsystems were integrated in a short amount of time, utilizing a skunk-works approach that brought together over 20 habitation-related technologies from a variety of NASA centers. This paper describes the system integration strategies and lessons learned, that allowed the PEM to be brought from paper design to working field prototype using a multi-center team. The system integration process included establishment of design standards, negotiation of interfaces between subsystems, and scheduling fit checks and installation activities. A major tool used in integration was a coordinated effort to accurately model all the subsystems using CAD, so that conflicts were identified before physical components came together. Some of the major conclusions showed that up-front modularity that emerged as an artifact of construction, such as the eight 45 degree "pie slices" making up the module whose steel rib edges defined structural mounting and loading points, dictated much of the configurational interfaces between the major subsystems and workstations. Therefore, 'one of the lessons learned included the need to use modularity as a tool for organization in advance, and to work harder to prevent non-critical aspects of the platform from dictating the modularity that may eventually inform the fight system.

Gill, Tracy R.↗