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 1,693 records · Page 94

Linear Proof Mass Actuator

This paper describes the mechanical design, analysis, fabrication, testing, and lessons learned by developing a uniquely designed spaceflight-like actuator. The Linear Proof Mass Actuator (LPMA) was designed to attach to both a large space structure and a ground test model without modification. Previous designs lacked the power to perform in a terrestrial environment while other designs failed to produce the desired accelerations or frequency range for spaceflight applications. Thus, the design for a unique actuator was conceived and developed at NASA Langley Research Center. The basic design consists of four large mechanical parts (Mass, Upper Housing, Lower Housing, and Center Support) and numerous smaller supporting components including an accelerometer, encoder, and four drive motors. Fabrication personnel were included early in the design phase of the LPMA as part of an integrated manufacturing process to alleviate potential difficulties in machining an already challenging design. Operational testing of the LPMA demonstrated that the actuator is capable of various types of load functions.

Holloway, S. E., III↗

Integrated planning and scheduling for Earth science data processing

Several current NASA programs such as the EOSDIS Core System (ECS) have data processing and data management requirements that call for an integrated planning and scheduling capability. In this paper, we describe the experience of applying advanced scheduling technology operationally, in terms of what was accomplished, lessons learned, and what remains to be done in order to achieve similar successes in ECS and other programs. We discuss the importance and benefits of advanced scheduling tools, and our progress toward realizing them, through examples and illustrations based on ECS requirements. The first part of the paper focuses on the Data Archive and Distribution (DADS) V0 Scheduler. We then discuss system integration issues ranging from communication with the scheduler to the monitoring of system events and re-scheduling in response to them. The challenge of adapting the scheduler to domain-specific features and scheduling policies is also considered. Extrapolation to the ECS domain raises issues of integrating scheduling with a product-generation planner (such as PlaSTiC), and implementing conditional planning in an operational system. We conclude by briefly noting ongoing technology development and deployment projects being undertaken by HTC and the ISTB.

Boddy, Mark↗

System results from FRECOPA

The work carried out over the past three years on FRECOPA and the LDEF has enabled a large quantity of information to be collected, part of which has already been exploited. As far as CNES is concerned, the major spin-offs of this mission mainly focus on the orbital environment and the behavior of materials in such an environment. With respect to the environment, the authors shall develop the lessons learned from expert appraisals on impacts by microparticles, which are the main feature observed in this area. As for the materials, the results show a variety of behavior when subjected to the space environment and even now constitute a wealth of information for the designing and validation of future mechanical systems. Apart from these direct spin-offs, there are repercussions on in-flight and ground testing, the calibration of test benches and improvements to simulation models.

Durin, Christian↗

Geostationary Operational Environmental Satellite (GOES)-8 mission flight experience

The Geostationary Operational Environmental Satellite (GOES)-8 spacecraft was launched on April 13, 1994, at 06:04:02 coordinated universal time (UTC), with separation from the Atlas-Centaur launch vehicle occurring at 06:33:05 UTC. The launch was followed by a series of complex, intense operations to maneuver the spacecraft into its geosynchronous mission orbit. The Flight Dynamics Facility (FDF) of the Goddard Space Flight Center (GSFC) Flight Dynamics Division (FDD) was responsible for GOES-8 attitude, orbit maneuver, orbit determination, and station acquisition support during the ascent phase. This paper summarizes the efforts of the FDF support teams and highlights some of the unique challenges the launch team faced during critical GOES-8 mission support. FDF operations experience discussed includes: (1) The abort of apogee maneuver firing-1 (AMF-1), cancellation of AMF-3, and the subsequent replans of the maneuver profile; (2) The unexpectedly large temperature dependence of the digital integrating rate assembly (DIRA) and its effect on GOES-8 attitude targeting in support of perigee raising maneuvers; (3) The significant effect of attitude control thrusting on GOES-8 orbit determination solutions; (4) Adjustment of the trim tab to minimize torque due to solar radiation pressure; and (5) Postlaunch analysis performed to estimate the GOES-8 separation attitude. The paper also discusses some key FDF GOES-8 lessons learned to be considered for the GOES-J launch which is currently scheduled for May 19, 1995.

Noonan, C. H.↗

Developmental problems and their solution for the Space Shuttle main engine alternate liquid oxygen high-pressure turbopump: Anomaly or failure investigation the key

The Space Shuttle main engine (SSME) alternate high-pressure liquid oxygen pump experienced synchronous vibration and ball bearing life problems that were program threatening. The success of the program hinged on the ability to solve these development problems. The design and solutions to these problems are engirded in the lessons learned and experiences from prior programs, technology programs, and the ability to properly conduct failure or anomaly investigations. The failure investigation determines the problem cause and is the basis for recommending design solutions. For a complex problem, a comprehensive solution requires that formal investigation procedures be used, including fault trees, resolution logic, and action items worked through a concurrent engineering-multidiscipline team. The normal tendency to use an intuitive, cut-and-try approach will usually prove to be costly, both in money and time and will reach a less than optimum, poorly understood answer. The SSME alternate high-pressure oxidizer turbopump development has had two complex problems critical to program success: (1) high synchronous vibrations and (2) excessive ball bearing wear. This paper will use these two problems as examples of this formal failure investigation approach. The results of the team's investigation provides insight into the complexity of the turbomachinery technical discipline interacting/sensitivities and the fine balance of competing investigations required to solve problems and guarantee program success. It is very important to the solution process that maximum use be made of the resources that both the contractor and Government can bring to the problem in a supporting and noncompeting way. There is no place for the not-invented-here attitude. The resources include, but are not limited to: (1) specially skilled professionals; (2) supporting technologies; (3) computational codes and capabilities; and (4) test and manufacturing facilities.

Ryan, R.↗

Application of CFD in aeronautics at NASA Ames Research Center

The role of Computational Fluid Dynamics (CFD) at Ames Research Center has expanded to address a broad range of aeronautical problems, including wind tunnel support, flight test support, design, and analysis. Balancing the requirements of each new problem against the available resources - software, hardware, time, and expertise - is critical to the effective use of CFD. Several case studies of recent applications highlight the depth of CFD capability at Ames, the tradeoffs involved in various approaches, and lessons learned in the use of CFD as an engineering tool.

Maksymiuk, Catherine M.↗

High-Temperature Optical Window Design

A high-temperature optical window is essential to the optical diagnostics of high-temperature combustion rigs. Laser Doppler velocimetry, schlieren photography, light sheet visualization, and laser-induced fluorescence spectroscopy are a few of the tests that require optically clear access to the combustor flow stream. A design was developed for a high-temperature window that could withstand the severe environment of the NASA Lewis 3200 F Lean Premixed Prevaporized (LPP) Flame Tube Test Rig. The development of this design was both time consuming and costly. This report documents the design process and the lessons learned, in an effort to reduce the cost of developing future designs for high-temperature optical windows.

Roeloffs, Norman↗

Object-oriented approach for gas turbine engine simulation

An object-oriented gas turbine engine simulation program was developed. This program is a prototype for a more complete, commercial grade engine performance program now being proposed as part of the Numerical Propulsion System Simulator (NPSS). This report discusses architectural issues of this complex software system and the lessons learned from developing the prototype code. The prototype code is a fully functional, general purpose engine simulation program, however, only the component models necessary to model a transient compressor test rig have been written. The production system will be capable of steady state and transient modeling of almost any turbine engine configuration. Chief among the architectural considerations for this code was the framework in which the various software modules will interact. These modules include the equation solver, simulation code, data model, event handler, and user interface. Also documented in this report is the component based design of the simulation module and the inter-component communication paradigm. Object class hierarchies for some of the code modules are given.

Curlett, Brian P.↗

Making intelligent systems team players. A guide to developing intelligent monitoring systems

This reference guide for developers of intelligent monitoring systems is based on lessons learned by developers of the DEcision Support SYstem (DESSY), an expert system that monitors Space Shuttle telemetry data in real time. DESSY makes inferences about commands, state transitions, and simple failures. It performs failure detection rather than in-depth failure diagnostics. A listing of rules from DESSY and cue cards from DESSY subsystems are included to give the development community a better understanding of the selected model system. The G-2 programming tool used in developing DESSY provides an object-oriented, rule-based environment, but many of the principles in use here can be applied to any type of monitoring intelligent system. The step-by-step instructions and examples given for each stage of development are in G-2, but can be used with other development tools. This guide first defines the authors' concept of real-time monitoring systems, then tells prospective developers how to determine system requirements, how to build the system through a combined design/development process, and how to solve problems involved in working with real-time data. It explains the relationships among operational prototyping, software evolution, and the user interface. It also explains methods of testing, verification, and validation. It includes suggestions for preparing reference documentation and training users.

Land, Sherry A.↗

The Personal Software Process: Downscaling the factory

It is argued that the next wave of software process improvement (SPI) activities will be based on a people-centered paradigm. The most promising such paradigm, Watts Humphrey's personal software process (PSP), is summarized and its advantages are listed. The concepts of the PSP are shown also to fit a down-scaled version of Basili's experience factory. The author's data and lessons learned while practicing the PSP are presented along with personal experience, observations, and advice from the perspective of a consultant and teacher for the personal software process.

Roy, Daniel M.↗

The Oak Ridge Refrigerant Management Program

For many years, chlorofluorocarbons (CFC's) have been used by the Department of Energy's (DOE) Oak Ridge Y-12 Plant in air conditioning and process refrigeration systems. However, Title 6 of the Clean Air Act Amendments (CAAA) and Executive Order 12843 (Procurement Requirements and Policies for Federal Agencies for Ozone Depleting Substances) signed by President Clinton require, as policy, that all federal agencies maximize their use of safe, alternate refrigerants and minimize, where economically practical, the use of Class 1 refrigerants. Unfortunately, many government facilities and industrial plants have no plan or strategy in place to make this changeover, even though their air conditioning and process refrigeration equipment may not be sustainable after CFC production ends December 31, 1995. The Y-12 Plant in Oak Ridge, Tennessee, has taken an aggressive approach to complying with the CAAA and is working with private industry and other government agencies to solve tough manufacturing and application problems associated with CFC and hydrochlorofluorocarbon (HCFC) alternatives. Y-12 was the first DOE Defense Program (DP) facility to develop a long-range Stratospheric Ozone Protection Plan for refrigerant management for compliance with the CAAA. It was also the first DOE DP facility to complete detailed engineering studies on retrofitting and replacing all air conditioning and process refrigeration equipment to enable operation with alternate refrigerants. The management plan and engineering studies are models for use by other government agencies, manufacturing plants, and private industry. This presentation identifies some of the hidden pitfalls to be encountered in the accelerated phaseout schedule of CFC's and explains how to overcome and prevent these problems. In addition, it outlines the general issues that must be considered when addressing the phase-out of ozone depleting substances and gives some 'lessons learned' by Y-12 from its Refrigerant Management Program. Discussion topics include requirements for developing a refrigerant management plan and establishing priorities for cost-effective compliance with the CAAA, as well as ways in which employees can be empowered to develop a comprehensive refrigerant management plan. The result of this employee empowerment was a cooperative labor-management effort that is beneficial for Y-12, DOE, and the environment.

Kevil, Thomas H.↗

The effect of environmental initiatives on NASA specifications and standards activities

The NASA Operational Environment Team (NOET) has conducted a survey of NASA centers specifications and standards that require the use of Ozone Depleting Substances (ODS's) (Chlorofluorocarbons (CFCs), Halons, and chlorinated solvents). The results of this survey are presented here, along with a pathfinder approach utilized at Marshall Space Flight Center (MSFC) to eliminate the use of ODS's in targeted specifications and standards. Presented here are the lessons learned from a pathfinder effort to replace CFC-113 in a significant MSFC specification for cleaning and cleanliness verification methods for oxygen, fuel and pneumatic service, including Shuttle propulsion elements.

Griffin, Dennis↗

Air-breathing aerospace plane development essential: Hypersonic propulsion flight tests

Hypersonic airbreathing propulsion utilizing scramjets can change transatmospheric accelerators for low earth-to-orbit and return transportation. The value and limitation of ground tests, of flight tests, and of computations are presented, and scramjet development requirements are discussed. It is proposed that near full-scale hypersonic propulsion flight tests are essential for developing computational design technology so that it can be used for designing this system. In order to determine how these objectives should be achieved, some lessons learned from past programs are presented. A conceptual two-stage-to-orbit (TSTO) prototype/experimental aerospace plane is recommended as a means of providing access-to-space and for conducting flight tests.

Mehta, Unmeel B.↗

Coastal zone color scanner 'system calibration': A retrospective examination

During its lifetime the Coastal Zone Color Scanner (CZCS) produced approximately 66,000 images. These have been placed in an archive of 'raw' radiance (sensor counts) in a subsampled format that is easily accessible. They have also been processed to form global fields, at reduced resolution, of normalized water-leaving radiance, phytoplankton pigments, and diffuse attenuation coefficient. Using this archive, we have tried to characterize some aspects of the 'system calibration' for the 8-year lifetime of CZCS. Specifically, we have assumed that the sensitivity of the red band decayed in a simple manner similar to the well-known long-term degradation of the shorter-wavelength bands, and we examined the sensitivity of the green and yellow bands by computing the globally averaged water-leaving radiance, over 10-day periods, for all of the imagery. The results provided evidence that in addition to the long-term degradation, short-term (2 weeks to 1 month) variations in the radiometric sensitivity of these bands started in early fall 1981 and continued for the rest of the mission. In contrast, the data suggested the absence of such variations prior to August 1981. It is reasonable to believe that the sensitivity of the blue (and probably the red) band underwent such variations as well; however our methodology cannot be used to study the other bands. Thus, after these fluctuations began, the actual values of CZCS - estimated pigment concentrations at a given location should be viewed with skepticism; however, the global patterns of derived pigment concentrations should be valid. Had an extensive set of surface measurements of water-leaving radiance, e.r., from moored buoyes or drifters, had been available during the CZCS mission, these fluctuations could have been removed from the data set, and this would have greatly increased its value. The lessons learned from CZCS that is, the requirement of good radiometric calibration and stability and the necessity of 'sea truth' stations to monitor the performance of the system (sensor plus algorithms), are being applied to the sea-viewing wide-field-of-view senso (Sea WiFS) scheduled for launch in August 1993.

Evans, Robert H.↗

Spacecraft fault tolerance: The Magellan experience

Interplanetary and earth orbiting missions are now imposing unique fault tolerant requirements upon spacecraft design. Mission success is the prime motivator for building spacecraft with fault tolerant systems. The Magellan spacecraft had many such requirements imposed upon its design. Magellan met these requirements by building redundancy into all the major subsystem components and designing the onboard hardware and software with the capability to detect a fault, isolate it to a component, and issue commands to achieve a back-up configuration. This discussion is limited to fault protection, which is the autonomous capability to respond to a fault. The Magellan fault protection design is discussed, as well as the developmental and flight experiences and a summary of the lessons learned.

Kasuda, Rick↗

Magellan attitude control mission operations

From the Martin Marietta Astronautics Group base in Denver, Colorado, spacecraft engineers have been operating the Magellan spacecraft for the past three and one half years, along with the Jet Propulsion Laboratory, for NASA. The spacecraft team in Denver is responsible for the health of the vehicle, from command generation to evaluation of engineering telemetry. Operation of the spacecraft's Attitude and Articulation Control Subsystem (AACS) has specifically posed several in-flight challenges. This system must provide accurate pointing of the spacecraft throughout each 3.2 hour orbit which typically consists of 5 - 9 discrete maneuvers. Preparation of bi-weekly command sequences, monitoring execution, and trending of subsystem performance is of paramount importance, but in-flight anomalies have also demanded the attention of AACS engineers. Anomalies are often very interesting and challenging aspects of a project, and the Magellan mission was no exception. From the first unsuccessful attempts to perform a starscan, to spacecraft safing events, much has been experienced to add to the `lessons learned' from this mission. Many of Magellan's in-flight experiences, anomalies, and their resolutions are highlighted in this paper.

Dukes, Eileen M.↗

Hypersonic propulsion flight tests as essential to air-breathing aerospace plane development

Hypersonic air-breathing propulsion utilizing scramjets can fundamentally change transatmospheric acclerators for transportation from low Earth orbits (LEOs). The value and limitations of ground tests, of flight tests, and of computations are presented, and scramjet development requirements are discussed. Near-full-scale hypersonic propulsion flight tests are essential for developing a prototype hypersonic propulsion system and for developing computation-design technology that can be used in designing that system. In order to determine how these objectives should be achieved, some lessons learned from past programs are presented. A conceptual two-stage-to-orbit (TSTO) prototype/experimental aerospace plane is recommended as a means of providing access-to-space and for conducting flight tests. A road map for achieving these objectives is also presented.

Mehta, U.↗

The widest practicable dissemination: The NASA technical report server

The search for innovative methods to distribute NASA's information lead a gross-roots team to create the NASA Technical Report Server (NTRS), which uses the World Wide Web and other popular Internet-based information systems as search engines. The NTRS is an inter-center effort which provides uniform access to various distributed publication servers residing on the Internet. Users have immediate desktop access to technical publications from NASA centers and institutes. This paper presents the NTRS architecture, usage metrics, and the lessons learned while implementing and maintaining the services over the initial 6-month period. The NTRS is largely constructed with freely available software running on existing hardware. NTRS builds upon existing hardware and software, and the resulting additional exposure for the body of literature contained will allow NASA to ensure that its institutional knowledge base will continue to receive the widest practicable and appropriate dissemination.

Nelson, Michael L.↗