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.

SourceResearch connectionFrom yearThrough year

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

At least 613 records · Page 34

All sources NASA NTRS DOE OSTI

NASA NTRS1991

Tiltrotor research aircraft composite blade repairs: Lessons learned

The XV-15, N703NA Tiltrotor Research Aircraft located at the NASA Ames Research Center, Moffett Field, California, currently uses a set of composite rotor blades of complex shape known as the advanced technology blades (ATBs). The main structural element of the blades is a D-spar constructed of unidirectional, angled fiberglass/graphite, with the aft fairing portion of the blades constructed of a fiberglass cross-ply skin bonded to a Nomex honeycomb core. The blade tip is a removable laminate shell that fits over the outboard section of the spar structure, which contains a cavity to retain balance weights. Two types of tip shells are used for research. One is highly twisted (more than a conventional helicopter blade) and has a hollow core constructed of a thin Nomex-honeycomb-and-fiberglass-skin sandwich; the other is untwisted with a solid Nomex honeycomb core and a fiberglass cross-ply skin. During initial flight testing of the blades, a number of problems in the composite structure were encountered. These problems included debonding between the fiberglass skin and the honeycomb core, failure of the honeycomb core, failures in fiberglass splices, cracks in fiberglass blocks, misalignment of mated composite parts, and failures of retention of metal fasteners. Substantial time was spent in identifying and repairing these problems. Discussed here are the types of problems encountered, the inspection procedures used to identify each problem, the repairs performed on the damaged or flawed areas, the level of criticality of the problems, and the monitoring of repaired areas. It is hoped that this discussion will help designers, analysts, and experimenters in the future as the use of composites becomes more prevalent.

Espinosa, Paul S.↗

NASA NTRS1991

Autonomous rough terrain navigation - Lessons learned

Because of light-time delays, a planetary rover located on Mars or beyond will probably need to be able to navigate autonomously, in order to do significant exploration. Recent work at JPL has explored several different autonomous navigation strategies. This work includes highly deliberative methods that require large amounts of computation and internal storage but yield very planful behavior to more reactive systems that require less resources but whose behavior is more difficult to model. This paper briefly presents these methods, the results from experiments both in simulation and in the field, and some conclusions on the value of different approaches, and their possible impact on the structure of the robot and the mission architecture.

Miller, David P.↗

NASA NTRS1991

The Extreme Ultraviolet Explorer science instruments development - Lessons learned

The science instruments development project for the Extreme Ultraviolet Explorer (EUVE) satellite is reviewed. Issues discussed include the philosophical basis of the program, the establishment of a tight development team, the approach to planning and phasing activities, the handling of the most difficult technical problems, and the assessment of the work done during the preimplemntation period of the project.

Malina, Roger F.↗

NASA NTRS1992

The U.S. Antarctic Program's operational goals, strategies, and concepts - Correlations and lessons learned for the Space Exploration Initiative

Results of an assessment of two programs, NASA SEI and the National Science Foundation's U.S. Antarctic Program (USAP) are presented. The assessment was aimed at determining the elements of USAP's operations which are relevant to living and working on the moon and Mars and at identifying operational concepts, procedures, and techniques which might be considered by NASA as it formulates the SEI concept. The assessment shows strong similarities in goals, related operational functions and accommodations, and fundamental strategies and policies for mission execution. Besides, both programs share logistical and operational constraints. There are differences in concepts for execution because of the unique aspects of accessing, living, and working in these environments.

Buoni, Corinne↗

NASA NTRS1993

Orbiter lessons learned: A guide to future vehicle development

Topics addressed are: (1) wind persistence loads methodology; (2) emphasize supportability in design of reusable vehicles; (3) design for robustness; (4) improved aerodynamic environment prediction methods for complex vehicles; (5) automated integration of aerothermal, manufacturing, and structures analysis; (6) continued electronic documentation of structural design and analysis; and (7) landing gear rollout load simulations.

Greenberg, Harry Stan↗

NASA NTRS1992

Tiltrotor Research Aircraft composite blade repairs - Lessons learned

Espinosa, Paul S.↗

NASA NTRS1991

Lessons learned from Space Shuttle flight software and Mission Control software

The techniques utilized by NASA to manage risk in the development and operations of flight software and Mission Control Center software for the Space Shuttle are reviewed. Particular attention is given to independent software in the backup flight system, structured requirements and design techniques, multiple levels of testing in development and production, independent testing following production, and independence of development and production, and the Mission Control Center model for Real Time Data System project.

Muratore, John F.↗

NASA NTRS1991

The Space Flight Operations Center first phase - Lessons learned

This paper is a retrospective look at the Space Flight Operations Center Project; a large, complex, multimission ground data system which is currently under development at the Jet Propulsion Laboratory (JPL), Pasadena. The Project was established in February 1984 and will be completed in April 1992 when the Magellan, Voyager, Ulysses, Galileo and Mars Observer Projects will be fully supported. The first phase of this project covers the development of a subset of multimission Baseline subsystems, the development of the mission-specific adaptations to this Baseline set for the Magellan Project, the development of a Magellan-specific high rate processor together with the delivery of these subsystems to operations. This first phase became operational in January 1989 in readiness for the Magellan launch in May 1989.

Gainsborough, A. J.↗

NASA NTRS1992

Lessons learned from the Autonomous Power System

The Autonomous Power System (APS) project at the NASA Lewis Research Center 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 APS project had been through one design iteration. Each of the three elements of the APS project has been designed, tested, and integrated into a complete working system. After these three portions were completed, an evaluation period was initiated. Each piece of the system was critiqued based on individual performance as well as the ability to interact with the other portions of the APS project. These critiques were then used to determine guidelines for new and improved components of the APS system.

Ringer, Mark J.↗

NASA NTRS1993

Launches and the environment - Lessons learned

An evaluation is presented of the consequences of NASA's study of the ways in which the launch of a Space Shuttle generates a plume of HCl and Al2O3; in combination with water from the Shuttle's sound-suppressor cooling water system, these substances can create a corrosive and hard-to-remove Al2O3 coating on nearby surfaces. Attention is given to the site-specific character of such environmental complications, the need to involve environmental-risk specialists in hardware-development teams, and the nonlinearity of many environmental impacts.

Vaughan, William W.↗

NASA NTRS1992

The Soft X-ray Telescope for Solar-A - Design evolution and lessons learned

The Japanese Solar-A satellite mission's Soft X-ray Telescope uses grazing-incidence optics, a CCD detector, and a pair of filter wheels for wavelength selection. A coaxially-mounted visible-light lens furnished sunspot and magnetic plage images, together with aspect information which aids in aligning the soft X-ray images with those from the satellite's Hard X-ray Telescope. Instrument electronics are microprocessor-based, and imbedded in a tightly integrated distributed system. Control software is divided between the instrument microprocessor and the spacecraft control computer.

Bruner, Marilyn E.↗

NASA NTRS1988

Lessons learned from an Ada conversion project

Recognizing the importance of building software with the robustness to accommodate rapid advances in technology, developers have focused on methods which preserve both past and future investment in software and in providing an advanced software engineering environment that frees the engineer, to the greatest extent possible, from the more routine aspects of software design and development. The software engineer is permitted to concentrate on the creative aspects of problem resolution. Standard languages such as Ada maximize portability across hardware and operating systems. Standard interfaces which enhance portability and permit the incorporation of new technology as it becomes available have been developed. Software design and development techniques which maximize portability receive increasing emphasis. Experience gained in porting an Ada application between two widely varying environments is evaluated in light of current practices to maximize software portability.

Porter, Tim↗

NASA NTRS1993

Some lessons learned in three years with ADS-33C

Three years of using the U.S. Army's rotorcraft handling qualities specification, Aeronautical Design Standard - 33, has shown it to be surprisingly robust. It appears to provide an excellent basis for design and for assessment, however, as the subtleties become more well understood, several areas needing refinement became apparent. Three responses to these needs have been documented in this paper: (1) The yaw-axis attitude quickness for hover target acquisition and tracking can be relaxed slightly. (2) Understanding and application of criteria for degraded visual environments needed elaboration. This and some guidelines for testing to obtain visual cue ratings have been documented. (3) The flight test maneuvers were an innovation that turned out to be very valuable. Their extensive use has made it necessary to tighten definitions and testing guidance. This was accomplished for a good visual environment and is underway for degraded visual environments.

Key, David L.↗

NASA NTRS1994

Handbook for handling and storage of nickel-cadmium batteries: Lessons learned

The handbook provides guidelines for the handling and storage of conventional NiCd flight batteries. The guidelines are based on many years of experience with ground and in-flight handling of batteries. The overall goal is to minimize the deterioration and irreversible effects of improper handling of NiCd flight batteries on flight performance. A secondary goal is to provide the reader with an understanding, in nonanalytical terms, of the degradation mechanisms of NiCd cells and how these mechanisms are affected by improper ground handling of flight hardware. Section 2 provides the reader with a brief introduction to NiCd cells. The effects of the environment on NiCd batteries are discussed in Section 3, and Section 4 contains 12 guidelines for battery handling and storage with supporting rationale for each guideline. The appendix provides a synopsis of NiCd cell design and evolution over 30 years of space flight on Goddard Space Flight Center (GSFC) satellites, along with a chronological review of key events that influenced the design of NiCd cells being flown today.

Ford, Floyd E.↗

NASA NTRS1994

La Chalupa-30: Lessons learned from a 30-day subsea mission analogue

The Behavior and Performance Laboratory (BPL) utilizes space mission analogs to study issues such as the psychological health and well-being, team characteristics, and task performance of crew members on long-duration missions. The analog used in this investigation was an underwater habitat named La Chalupa, which was selected for its similar features to a space station environment. The primary objectives of the La Chalupa-30 investigation were to evaluate the efficiency of several methods for collecting data in remote environments and to assess aspects of living and working under isolated and confined conditions.

Vanderark, Steve↗

NASA NTRS1993

Benefits gained and lessons learned from NASA's Small Explorer (SMEX) Program

NASA's Small Explorer Program (SMEX) is a sustained program of scientific satellites limited in mass to 200-300 kg (depending on orbital inclination) for a 500-km circular orbit. The SMEX program was undertaken to obtain the benefits of scientific yield, short development time, and high flight rate, with the goal to launch a mission every year. NASA also uses the program to train engineers and managers in designing and developing spacecraft. The phases of a SMEX mission life cycle are described including the competitive selection of missions through announcement of opportunity and evaluation of proposals, the definition of mission and system requirements, design and development of the spacecraft, testing, launch, and operations. Program content of some SMEX missions is then reviewed. The first SMEX mission was the Solar, Anomalous, and Magnetospheric Particle Explorer, which confirmed that anomalous cosmic rays are only partially ionized atoms. The Fast Auroral Snapshot Explorer was intended to measure the electric, magnetic, and time-variable fields and to record particle flow in the auroral acceleration region. A future mission is the Submillimeter Wave Astronomy Satellite to examine low-level molecular transitions.

Gilman, David↗

NASA NTRS1993

Lessons learned - MO&DA at JPL

The issues of how to avoid future surprise growth in Mission Operations and Data Analysis (MO&DA) costs and how to minimize total MO&DA costs for planetary missions are discussed within the context of JPL mission operations support. It is argued that there is no simple, single solution: the entire Project life-cycle must be addressed. It is concluded that cost models that can predict both MO&DA cost as well as Ground System development costs are needed. The first year MO&DA budget plotted against the total of ground and flight systems developments is shown. In order to better recognize changes and control costs in general, a modified funding line item breakdown is recommended to distinguish between development costs (prelaunch and postlaunch) and MO&DA costs.

Handley, Thomas H., Jr.↗

NASA NTRS1992

Formal methods technology transfer: Some lessons learned

IBM has a long history in the application of formal methods to software development and verification. There have been many successes in the development of methods, tools and training to support formal methods. And formal methods have been very successful on several projects. However, the use of formal methods has not been as widespread as hoped. This presentation summarizes several approaches that have been taken to encourage more widespread use of formal methods, and discusses the results so far. The basic problem is one of technology transfer, which is a very difficult problem. It is even more difficult for formal methods. General problems of technology transfer, especially the transfer of formal methods technology, are also discussed. Finally, some prospects for the future are mentioned.

Hamilton, David↗