Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lessons”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Insights and Observations from Operating a Geostationary Laser Communication Relay Mission: Operational Lessons from NASA’s Laser Communications Relay Demonstration (LCRD) and Associated Optical Ground Stations (OGSs)

The NASA Laser Communications Relay Demonstration (LCRD) has operated on orbit for the last two years. The LCRD Mission consists of a geostationary payload and two optical ground stations. This technology demonstration mission is NASA’s first two-way, end-to-end optical communications relay. LCRD has performed an extensive experiment campaign to analyze laser communication performance for extended operations. This paper discusses various lessons learned while operating the optical relay mission from early commissioning through two years of operation. Before launch, engineers and operators performed analyses to generate operational procedures based on expected LCRD performance. However, only operation on orbit can supply actual performance data. Additional topics covered in this paper include pre-launch and commissioning testing, ephemeris generation and cadence, environmental configurations, and accommodation concerns. The addition of Integrated Laser Communications Relay Demonstration Low Earth Orbit User Modem and Amplifier Terminal (ILLUMA-T) to the optical network supplemented the LCRD team’s operational experiences and enabled them to garner new lessons learned. The authors of this paper include day-to-day flight leads who consulted with on-console operators, engineers, and subject matter experts analyzing data and experiment results to gather the lessons learned described in this paper. LCRD is a joint project involving NASA Goddard Space Flight Center (GSFC), the California Institute of Technology Jet Propulsion Laboratory (JPL), and Massachusetts Institute of Technology Lincoln Laboratory (MIT LL).

Lessons Learned↗
NASA NTRSDate not supplied

A Frank Discussion on Lessons Learned From Adopting and Applying NASA-STD-6030 for Spaceflight Systems

With the advancement and adoption of Additive Manufacturing (AM) for spaceflight systems, numerous lessons have been learned during the qualification and certification of AM components. The lessons learned covered in this presentation will provide an overview of the challenges faced by NASA centers and commercial partners working to design AM hardware that complies with NASA-STD-6030 Additive Manufacturing Requirements (AMR). Topics of interest include tailoring of requirements for specific projects, documentation requirements, and addressing conservative approaches towards mechanical property development and analysis. In addition to that, this presentation aims to impress that these lessons learned will influence the future revisions of the NASA technical standard to facilitate and advance AM technology adoption on NASA projects.

Additive Manufacturing↗
DOE OSTI2015

Lessons learned from the pioneering hot dry rock project at Fenton Hill, USA

Interest in geothermal energy production has grown rapidly in recent years due to the increasing demand for clean, renewable, domestic energy. Recent publications have suggested that geothermal energy from Enhanced Geothermal Systems could satisfy a large portion of the energy needs in the U.S. if the technology were implemented on a large scale. Pertinent to this goal are many of the lessons learned from the pioneering Hot Dry Rock project aimed at producing usable energy form the heat of the earth, conducted from 1970 to 1995 at Fenton Hill, New Mexico, USA. During this project, the Los Alamos National Laboratory created and tested two reservoirs at depths in the range of 2.8–3.5 km in crystalline rock formations underlying the Fenton Hill site. Thermal energies in the range of 3–10 MWt were produced demonstrating the technical feasibility of the concept. Many important lessons were learned regarding the creation, engineering and operation of such subsurface systems—these lessons will prove valuable as the geothermal community moves towards the goal of realizing the immense potential of this ubiquitous renewable energy resource. The purpose here is to provide a brief, easy to read overview of this pioneering project.

58 GEOSCIENCES↗
DOE OSTI2014

Best Practices and Lessons Learned from Deploying and Operating Large-Scale Data-Centric Parallel File Systems, In: SC '14: Proceedings of the International Conference for High Performance Computing, Networking, Storage and Analysis

The Oak Ridge Leadership Computing Facility (OLCF) has deployed multiple large-scale parallel file systems (PFS) to support its operations. During this process, OLCF acquired significant expertise in large-scale storage system design, file system software development, technology evaluation, benchmarking, procurement, deployment, and operational practices. Based on the lessons learned from each new PFS deployment, OLCF improved its operating procedures, and strategies. This paper provides an account of our experience and lessons learned in acquiring, deploying, and operating large-scale parallel file systems. We believe that these lessons will be useful to the wider HPC community.

Computer Science↗
DOE OSTI2012

Lessons from Iowa: Development of a 270 Megawatt Compressed Air Energy Storage Project in Midwest Independent System Operator

The Iowa Stored Energy Park was an innovative, 270 Megawatt, $400 million compressed air energy storage (CAES) project proposed for in-service near Des Moines, Iowa, in 2015. After eight years in development the project was terminated because of site geological limitations. However, much was learned in the development process regarding what it takes to do a utility-scale, bulk energy storage facility and coordinate it with regional renewable wind energy resources in an Independent System Operator (ISO) marketplace. Lessons include the costs and long-term economics of a CAES facility compared to conventional natural gas-fired generation alternatives; market, legislative, and contract issues related to enabling energy storage in an ISO market; the importance of due diligence in project management; and community relations and marketing for siting of large energy projects. Although many of the lessons relate to CAES applications in particular, most of the lessons learned are independent of site location or geology, or even the particular energy storage technology involved.

25 ENERGY STORAGE↗
DOE OSTI2020

Communication of industry knowledge, best practices, and lessons learned in the space of cellulosic biofuels plant design, project development and execution and operations. Task 1 report

ExxonMobil Research and Engineering Company, via a technical services agreement, engages Idaho National Laboratory (INL) to provide general industry knowledge, best practices, and lessons learned in cellulosic ethanol plant design, project execution, and operations. INL will also assess publicly proposed cellulosic plant designs. The scope of work will be accomplished in three tasks: Task 1, Communicate industry knowledge; Task 2, Present high-level lessons learned; Task 3, Provide an engineering assessment of publicly proposed ethanol plant designs. This Task 1 report provides a high-level summary of general industry knowledge, best practice, and lessons learned in biomass feedstock logistics and integration with bioconversion processes.

09 BIOMASS FUELS↗
NASA NTRS1976

Skylab lessons learned as applicable to a large space station, 1967-1974

This report records some of the lessons learned during Skylab development. The approach taken is to list lessons which could have wide application in the development of a large space station. The lessons are amplified and explained in light of the background and experiences of the Skylab development.

Schneider, W. C.↗
NASA NTRS1984

Lessons learned from KSC processing on STS science, applications, and commercial payloads

The present investigation is concerned with an evaluation of the lessons learned in connection with the flights of the Shuttle orbiters Columbia, Challenger, and Discovery. A description is provided of several general and specific lessons related to the processing of free-flying and attached payloads. John F. Kennedy Space Center (KSC), as the prime launch and landing site, is responsible for managing all payload-to-payload, payload-to-simulated orbiter, and payload-to-orbiter operations. For each payload, a KSC Launch Site Support Manager (LSSM) is named as the primary point of contact for the customer. Attention is given to aspects of planning interaction, payload types, and problems of ground processing. The discussed lessons are partly related to the value of early contact between customers and KSC representatives, the primary point of contact, the launch site support plan, and the importance of customer participation.

Williams, W. E.↗
NASA NTRS1987

Shuttle orbit flight control design lessons - Direction for Space Station

The Space Shuttle orbit flight control system, which operates during all exo-atmospheric flight phases, has successfully met operational requirements. Many design integration and operational issues that required resolution during development and testing provide an experience base that will benefit the development of future space systems, particularly the Space Station. To this end, the applicable Shuttle and Space Station hardware/software is reviewed with some perspective provided on how current design groundrules were derived and how issues that affected the Shuttle orbit control system design are a pathway for the Space Station. Some of the most significant lessons learned from the Shuttle are summarized, with a discussion of the effect of performance and design of hardware, including the data processing system on software structures and usage procedures. Crew interface issues and important results from man-in-the-loop tests are summarized. Problems resulting from trying to meet difficult orbital operational objectives, including some sophisticated payload operations are characterized. Several proposed Shuttle flight control design improvements, developed in response to some of the lessons learned so far, are identified. Potential application of the Shuttle design lessons and new control technologies to the Space Station are discussed.

Cox, Kenneth J.↗
NASA NTRS1986

The computerization of programming: Ada (R) lessons learned

One of the largest systems yet written in Ada has been constructed. This system is the Intermetrics Ada compiler. Many lessons have been learned during the implementation of this Ada compiler. Some of these lessons, concentrating on those lessons relevant to large system implementations are described. The characteristics of the Ada compiler implementation project at Intermetrics are also described. Some specific experiences during the implementation are pointed out.

Struble, Dennis D.↗
NASA NTRS1991

Lessons learned in the development of the STOL intelligent tutoring system

Lessons learned during the development of the NASA Systems Test and Operations Language (STOL) Intelligent Tutoring System (ITS), being developed at NASA Goddard Space Flight Center are presented. The purpose of the intelligent tutor is to train STOL users by adapting tutoring based on inferred student strengths and weaknesses. This system has been under development for over one year and numerous lessons learned have emerged. These observations are presented in three sections, as follows. The first section addresses the methodology employed in the development of the STOL ITS and briefly presents the ITS architecture. The second presents lessons learned, in the areas of: intelligent tutor development; documentation and reporting; cost and schedule control; and tools and shells effectiveness. The third section presents recommendations which may be considered by other ITS developers, addressing: access, use and selection of subject matter experts; steps involved in ITS development; use of ITS interface design prototypes as part of knowledge engineering; and tools and shells effectiveness.

Seamster, Thomas↗
NASA NTRS1990

Planning and scheduling lessons learned study, executive summary

The study was performed to document the lessons on planning and scheduling activities for a number of missions and institutional facilities in such a way that they can be applied to future missions; to provide recommendations to both projects and Code 500 that will improve the end-to-end planning and scheduling process; and to identify what, if any, mission characteristics might be related to certain lessons learned. The results are a series of recommendations of both a managerial and technical nature related to the underlying lessons learned.

Robinson, Toni↗
NASA NTRS1991

Lessons learned and their application to program development and cultural issues

The main objectives of space product assurance are, in effect, the same as those of Total Quality Management (TQM) or its many variants. The most significant ingredients are the lessons learned and their application to ongoing and future programs as they are affected by changes in the cultural environment. The cultural issues which affect almost everything done in technical programs and projects are considered. Understanding the lessons learned and the synergism which results from this combination of knowledge, culture, and lessons learned is identified as crucial. A brief discussion of the closed loop linkage that should exist between the world of hands on activities and that of educational institutions is presented.

Roth, Gilbert L.↗
NASA NTRS1992

The role of failure/problems in engineering: A commentary of failures experienced - lessons learned

The written version of a series of seminars given to several aerospace companies and three NASA centers are presented. The results are lessons learned through a study of the problems experienced in 35 years of engineering. The basic conclusion is that the primary cause of problems has not been mission technologies, as important as technology is, but the neglect of basic principles. Undergirding this is the lack of a systems focus from determining requirements through design, verification, and operations phases. Many of the concepts discussed are fundamental to total quality management (TQM) and can be used to augment this product enhanced philosophy. Fourteen principles are addressed with problems experienced and are used as examples. Included is a discussion of the implication of constraints, poorly defined requirements, and schedules. Design guidelines, lessons learned, and future tasks are listed. Two additional sections are included that deal with personal lessons learned and thoughts on future thrusts (TQM).

Ryan, R. S.↗
NASA NTRS1992

Scheduling lessons learned from the Autonomous Power System

The Autonomous Power System (APS) project at NASA LeRC is designed to demonstrate the applications of integrated intelligent diagnosis, control, and scheduling techniques to space power distribution systems. The project consists of three elements: the Autonomous Power Expert System (APEX) for Fault Diagnosis, Isolation, and Recovery (FDIR); the Autonomous Intelligent Power Scheduler (AIPS) to efficiently assign activities start times and resources; and power hardware (Brassboard) to emulate a space-based power system. The AIPS scheduler was tested within the APS system. This scheduler is able to efficiently assign available power to the requesting activities and share this information with other software agents within the APS system in order to implement the generated schedule. The AIPS scheduler is also able to cooperatively recover from fault situations by rescheduling the affected loads on the Brassboard in conjunction with the APEX FDIR system. AIPS served as a learning tool and an initial scheduling testbed for the integration of FDIR and automated scheduling systems. Many lessons were learned from the AIPS scheduler and are now being integrated into a new scheduler called SCRAP (Scheduler for Continuous Resource Allocation and Planning). This paper will service three purposes: an overview of the AIPS implementation, lessons learned from the AIPS scheduler, and a brief section on how these lessons are being applied to the new SCRAP scheduler.

Ringer, Mark J.↗
NASA NTRS1991

Lessons learned for composite structures

Lessons learned for composite structures are presented in three technology areas: materials, manufacturing, and design. In addition, future challenges for composite structures are presented. Composite materials have long gestation periods from the developmental stage to fully matured production status. Many examples exist of unsuccessful attempts to accelerate this gestation period. Experience has shown that technology transition of a new material system to fully matured production status is time consuming, involves risk, is expensive and should not be undertaken lightly. The future challenges for composite materials require an intensification of the science based approach to material development, extension of the vendor/customer interaction process to include all engineering disciplines of the end user, reduced material costs because they are a significant factor in overall part cost, and improved batch-to-batch pre-preg physical property control. Historical manufacturing lessons learned are presented using current in-service production structure as examples. Most producibility problems for these structures can be traced to their sequential engineering design. This caused an excessive emphasis on design-to-weight and schedule at the expense of design-to-cost. This resulted in expensive performance originated designs, which required costly tooling and led to non-producible parts. Historically these problems have been allowed to persist throughout the production run. The current/future approach for the production of affordable composite structures mandates concurrent engineering design where equal emphasis is placed on product and process design. Design for simplified assembly is also emphasized, since assembly costs account for a major portion of total airframe costs. The future challenge for composite manufacturing is, therefore, to utilize concurrent engineering in conjunction with automated manufacturing techniques to build affordable composite structures. Composite design experience has shown that significant weight savings have been achieved, outstanding fatigue and corrosion resistance have been demonstrated, and in-service performance has been very successful. Currently no structural design show stoppers exist for composite structures. A major lesson learned is that the full scale static test is the key test for composites, since it is the primary structural 'hot spot' indicator. The major durability issue is supportability of thin skinned structure. Impact damage has been identified as the most significant issue for the damage tolerance control of composite structures. However, delaminations induced during assembly operations have demonstrated a significant nuisance value. The future challenges for composite structures are threefold. Firstly, composite airframe weight fraction should increase to 60 percent. At the same time, the cost of composite structures must be reduced by 50 percent to attain the goal of affordability. To support these challenges it is essential to develop lower cost materials and processes.

Whitehead, R. S.↗
NASA NTRS1993

Lessons learned applying CASE methods/tools to Ada software development projects

This paper describes the lessons learned from introducing CASE methods/tools into organizations and applying them to actual Ada software development projects. This paper will be useful to any organization planning to introduce a software engineering environment (SEE) or evolving an existing one. It contains management level lessons learned, as well as lessons learned in using specific SEE tools/methods. The experiences presented are from Alpha Test projects established under the STARS (Software Technology for Adaptable and Reliable Systems) project. They reflect the front end efforts by those projects to understand the tools/methods, initial experiences in their introduction and use, and later experiences in the use of specific tools/methods and the introduction of new ones.

Blumberg, Maurice H.↗