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 829 records · Page 46

Lessons learned from an Ada conversion project

Background; SAVVAS architecture; software portability; history of Ada; isolation of non-portable code; simple terminal interface package; constraints of language features; and virtual interfaces are outlined. This presentation is represented by viewgraphs only.

Porter, Tim↗

IVA the robot: Design guidelines and lessons learned from the first space station laboratory manipulation system

The first interactive Space Station Freedom (SSF) lab robot exhibit was installed at the Space and Rocket Center in Huntsville, AL, and has been running daily since. IntraVehicular Activity (IVA) the robot is mounted in a full scale U.S. Lab (USL) mockup to educate the public on possible automation and robotic applications aboard the SSF. Responding to audio and video instructions at the Command Console, exhibit patrons may prompt IVA to perform a housekeeping task or give a speaking tour of the module. Other exemplary space station tasks are simulated and the public can even challenge IVA to a game of tic tac toe. In anticipation of such a system being built for the Space Station, a discussion is provided of the approach taken, along with suggestions for applicability to the Space Station Environment.

Konkel, Carl R.↗

Historical problem areas lessons learned

Historical problem areas in space transportation propulsion technology are identified in viewgraph form. Problem areas discussed include materials compatibility, contamination, pneumatic/feed system flow instabilities, instabilities in rocket engine combustion and fuel sloshing, exhaust plume interference, composite rocket nozzle failure, and freeze/thaw damage.

Sackheim, Bob↗

Lessons learned in the development of the Hubble Space Telescope software

An effort is made to document what was successful in the HST software development, and to present a retrospective analysis indicating what could have been done more efficiently. Consideration is given to systems engineering and design definition, standards and tools, system architecture and design, operational considerations, and reuse and adaptation of existing resources.

Harrington, Michael↗

Lessons learned in control center technologies and non-technologies

Information is given in viewgraph form on the Solar Mesosphere Explorer (SME) Control Center and the Oculometer and Automated Space Interface System (OASIS). Topics covered include SME mission operations functions; technical and non-technical features of the SME control center; general tasks and objects within the Space Station Freedom (SSF) ground system nodes; OASIS-Real Time for the control and monitoring of of space systems and subsystems; and OASIS planning, scheduling, and PC architecture.

Hansen, Elaine R.↗

Getting expert systems off the ground: Lessons learned from integrating model-based diagnostics with prototype flight hardware

As an initial attempt to introduce expert system technology into an onboard environment, a model based diagnostic system using the TRW MARPLE software tool was integrated with prototype flight hardware and its corresponding control software. Because this experiment was designed primarily to test the effectiveness of the model based reasoning technique used, the expert system ran on a separate hardware platform, and interactions between the control software and the model based diagnostics were limited. While this project met its objective of showing that model based reasoning can effectively isolate failures in flight hardware, it also identified the need for an integrated development path for expert system and control software for onboard applications. In developing expert systems that are ready for flight, artificial intelligence techniques must be evaluated to determine whether they offer a real advantage onboard, identify which diagnostic functions should be performed by the expert systems and which are better left to the procedural software, and work closely with both the hardware and the software developers from the beginning of a project to produce a well designed and thoroughly integrated application.

Stephan, Amy↗

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.↗

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.↗

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.↗

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↗

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↗

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.↗

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.↗

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.↗

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.↗

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.↗

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.↗

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↗