Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “maintenance engineering”

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 577 records · Page 32

Re-Engineering of the Hubble Space Telescope (HST) to Reduce Operational Costs

Satellite telemetry processing onboard the Hubble Space Telescope (HST) is carried out using dedicated software and hardware. The current ground system is expensive to operate and maintain. The mandate to reduce satellite ground system operations and maintenance costs by the year 2000 led NASA to upgrade the command and control systems in order to improve the data processing capabilities, reduce operator experience levels and increase system standardization. As a result, a command and control system product development team was formed to redesign and develop the HST ground system. The command and control system ground system development consists of six elements. The results of the prototyping phase carried out for the following of these elements are presented: the front end processor; middleware, and the graphical user interface.

Garvis, Michael↗

Bonding soft rubber or plasticized elastomers to metal

Approach using bond-cover coat of unplasticized rubber between soft rubber and adhesive eliminates diffusion problem. Approach is useful in making improved seals in automobile engines, industrial and public plumbing, and in other areas using soft-rubber-to-metal bonds. Seals and gaskets made this way would not have to be replaced very often, reducing cost of maintenance.

Clemons, J. M.↗

Development and integration of the infrared telescope for Spacelab

A description is given of the design features of the Small Helium-Cooled Infrared Telescope (IRT) being developed for the 1983 Spacelab 2 mission and the problems encountered during the development of its (1) superfluid helium system requirements, (2) interfaces with Spacelab, and (3) Kennedy Space Center prelaunch operations requirements and restrictions. The IRT comprises cryogenic, IR optical, mechanical, and electronics subsystems. Attention is given the preflight management of superfluid helium by a vacuum maintenance assembly (VMA), which will operate almost continuously until launch and then be deactivated to fly as unavoidable ballast. The objective of IRT design and development is the meeting of IR science and engineering objectives with a relatively low-cost system.

Urban, E. W.↗

AI, automation and the Flight Telerobotic Servicer

A NASA study for the preliminary definition of a teleoperated robotic device has been recently completed. The Fligt Telerobotic Servicer (FTS) will be used to assist astronauts in many of the on-board tasks of assembly, maintenance, servicing, and inspection of the Space Station. The role of artificial intelligence (AI) in furthering the FTS automation capabilities and, hence, extending its capacity for growth and evolution is discussed. Relevant system engineering issues are identified, and an approach for insertion of AI technology is presented in terms of the NASA/NBS Standard Reference Model control architecture NASREM.

Goforth, Andre↗

Model-based reasoning for power system management using KATE and the SSM/PMAD

The overall goal of this research effort has been the development of a software system which automates tasks related to monitoring and controlling electrical power distribution in spacecraft electrical power systems. The resulting software system is called the Intelligent Power Controller (IPC). The specific tasks performed by the IPC include continuous monitoring of the flow of power from a source to a set of loads, fast detection of anomalous behavior indicating a fault to one of the components of the distribution systems, generation of diagnosis (explanation) of anomalous behavior, isolation of faulty object from remainder of system, and maintenance of flow of power to critical loads and systems (e.g. life-support) despite fault conditions being present (recovery). The IPC system has evolved out of KATE (Knowledge-based Autonomous Test Engineer), developed at NASA-KSC. KATE consists of a set of software tools for developing and applying structure and behavior models to monitoring, diagnostic, and control applications.

Morris, Robert A.↗

Performance as Promised: How the Chandra X-ray Observatory Accomplished One of Nasa's Most Challenging Missions for Billions of Dollars Less than Originally Planned

As the nation looks toward bold new ventures in space, the Chandra X-ray Observatory program offers an example of how billion-dollar missions can be successfully developed within tightening fiscal constraints. Chandra experienced many of challenges facing bold space programs (state-of-the-art technical requirements and budget-induced slips and restructurings), and yet the Chandra team achieved nearly all the originally envisioned performance for dramatically lower cost. This was accomplished by a combination of team- work, systems engineering, advanced technology insertion, and effective approaches for program implementation. A thorough tradeoff of science utility vs. cost led to the selection of a highly elliptical orbit with uncrewed robotic delivery, deployment, and maintenance. Progressive, focused technology demonstrations were accomplished prior to commitment of major resources to critical elements of the system design, such as the high resolution mirror assembly (HRMA). Pathfinder hardware was developed to reduce risks. A variety of schedule risk reduction measures were implemented and resulted in the X-ray calibration taking place exactly within five days of its originally planned date after after five years of development. The team worked together in an effective manner to contain requirements creep. reductions such as the ACIS-2 chip device. It is estimated that the above combination of measures achieved the avoidance of over $4B in costs, while enabling a highly successful mission.

Davidson, Greg↗

Orbital Debris Research in the United States

The presentation includes information about growth of the satellite population, the U.S. Space Surveillance Network, tracking and catalog maintenance, Haystack and HAX radar observation, Goldstone radar, the Michigan Orbital Debris Survey Telescope (MODEST), spacecraft surface examinations and sample of space shuttle impacts. GEO/LEO observations from Kwajalein Atoll, NASA s Orbital Debris Engineering Model (ORDEM2008), a LEO-to-GEO Environment Debris Model (LEGEND), Debris Assessment Software (DAS) 2.0, the NASA/JSC BUMPER-II meteoroid/debris threat assessment code, satellite reentry risk assessment, optical size and shape determination, work on more complicated fragments, and spectral studies.

Stansbery, Gene↗

Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems

When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEJ Software Development Risk Taxonomy [4] focuses on general software development issues. It does not, however, cover all the safety risks. The Software Safety Risk Taxonomy [8] was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a Software Safety Risk Taxonomy Based Questionnaire (TBQ) is generated containing questions addressing each safety attribute in the Software Safety Risk Taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized Product Engineering Class within the Software Safety Risk Taxonomy. At the end of the paper, we present the tool known as the 'Legacy Systems Risk Database Tool' that is used to collect and analyze the data required to show traceability to a particular safety standard

Hill, Janice↗

Description of the Space Shuttle Reaction Control System

The Space Shuttle RCS (reaction control system) is required to provide propulsion thrust for precise attitude control and three-axis translation. This capability must be provided for external tank separation, on-orbit operation, deorbit, and reentry. In order to meet these requirements a bipropellant, pressure-fed system utilizing monomethylhydrazine as fuel, and nitrogen tetroxide as oxidizer has been selected. The RCS engines include 38 primary thrusters rated at 870 lbf thrust and 6 vernier thrusters rated at 25 lbf thrust. The system is divided into three removable modules (one forward and two aft) to achieve maintenance and turnaround requirements. In order to provide additional mission flexibility, the aft modules can be connected together or interconnected with the OMS (orbital maneuvering system).

Blevins, D. R.↗

Advanced propfan engine characteristics and technology needs

A comparative study is presented for two of the advanced gas turbine engine designs developed in the course of a proprietary research effort for the NASA Advanced Propfan Engine Technology research program. In these engines, a cycle pressure ratio of 32.5:1 and a 2500 F maximum turbine temperature provide fuel efficient operation in the 32,000-ft altitude, Mach 0.72 cruise speed regime stipulated. Both of the engine configurations incorporate three spools, of which the compressors are dual-spool and the power turbines are free. A major design challenge for axial compressors in the 10,000-shp class was the maintenance of adequate blade heights in the later stages.

Anderson, R. D.↗

Improving a data-acquisition software system with abstract data type components

Abstract data types and object-oriented design are active research areas in computer science and software engineering. Much of the interest is aimed at new software development. Abstract data type packages developed for a discontinued software project were used to improve a real-time data-acquisition system under maintenance. The result saved effort and contributed to a significant improvement in the performance, maintainability, and reliability of the Goldstone Solar System Radar Data Acquisition System.

Howard, S. D.↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 12: The diffusion of federally funded aerospace Research and Development (R&D) and the information seeking behavior of US aerospace engineers and scientists

The present exploration of the diffusion of federally-funded R&D via the information-seeking behavior of scientists and engineers proceeds under three assumptions: (1) that knowledge transfer and utilization is as important as knowledge production; (2) that the diffusion of knowledge obtained through federally-funded R&D is necessary for the maintenance of U.S. preeminence in the aerospace field; and (3) that federally-funded NASA and DoD technical reports play an important, albeit as-yet undefined, role in aerospace R&D diffusion. A conceptual model is presented for the process of knowledge diffusion that stresses the role of U.S. government-funded technical reports.

Pinelli, Thomas E.↗

Fluid Film Bearing Code Development

The next generation of rocket engine turbopumps is being developed by industry through Government-directed contracts. These turbopumps will use fluid film bearings because they eliminate the life and shaft-speed limitations of rolling-element bearings, increase turbopump design flexibility, and reduce the need for turbopump overhauls and maintenance. The design of the fluid film bearings for these turbopumps, however, requires sophisticated analysis tools to model the complex physical behavior characteristic of fluid film bearings operating at high speeds with low viscosity fluids. State-of-the-art analysis and design tools are being developed at the Texas A&M University under a grant guided by the NASA Lewis Research Center. The latest version of the code, HYDROFLEXT, is a thermohydrodynamic bulk flow analysis with fluid compressibility, full inertia, and fully developed turbulence models. It can predict the static and dynamic force response of rigid and flexible pad hydrodynamic bearings and of rigid and tilting pad hydrostatic bearings. The Texas A&M code is a comprehensive analysis tool, incorporating key fluid phenomenon pertinent to bearings that operate at high speeds with low-viscosity fluids typical of those used in rocket engine turbopumps. Specifically, the energy equation was implemented into the code to enable fluid properties to vary with temperature and pressure. This is particularly important for cryogenic fluids because their properties are sensitive to temperature as well as pressure. As shown in the figure, predicted bearing mass flow rates vary significantly depending on the fluid model used. Because cryogens are semicompressible fluids and the bearing dynamic characteristics are highly sensitive to fluid compressibility, fluid compressibility effects are also modeled. The code contains fluid properties for liquid hydrogen, liquid oxygen, and liquid nitrogen as well as for water and air. Other fluids can be handled by the code provided that the user inputs information that relates the fluid transport properties to the temperature.

Source record↗

Space station data system analysis/architecture study. Task 3: Trade studies, DR-5, volume 2

Results of a Space Station Data System Analysis/Architecture Study for the Goddard Space Flight Center are presented. This study, which emphasized a system engineering design for a complete, end-to-end data system, was divided into six tasks: (1); Functional requirements definition; (2) Options development; (3) Trade studies; (4) System definitions; (5) Program plan; and (6) Study maintenance. The Task inter-relationship and documentation flow are described. Information in volume 2 is devoted to Task 3: trade Studies. Trade Studies have been carried out in the following areas: (1) software development test and integration capability; (2) fault tolerant computing; (3) space qualified computers; (4) distributed data base management system; (5) system integration test and verification; (6) crew workstations; (7) mass storage; (8) command and resource management; and (9) space communications. Results are presented for each task.

Source record↗

Goldstone solar system radar

This task provides for the planning, experiment design, and coordination of the data acquisition and engineering activities in support of all Goldstone planetary radar astronomy. Activities related to up-grades of the receiver systems, transmitter systems, and data processing support systems are currently intense. Also, the hardware and software maintenance of the data processing facility used by many of the Goldstone Solar System Radar investigators are covered.

Jurgens, Raymond F.↗

SCOS 2: An object oriented software development approach

The Spacecraft Control and Operations System 2 (SCOS 2), is intended to provide the generic mission control system infrastructure for future ESA missions. It represents a bold step forward in order to take advantage of state-of-the-art technology and current practices in the area of software engineering. Key features include: (1) use of object oriented analysis and design techniques; (2) use of UNIX, C++ and a distributed architecture as the enabling implementation technology; (3) goal of re-use for development, maintenance and mission specific software implementation; and (4) introduction of the concept of a spacecraft control model. This paper touches upon some of the traditional beliefs surrounding Object Oriented development and describes their relevance to SCOS 2. It gives rationale for why particular approaches were adopted and others not, and describes the impact of these decisions. The development approach followed is discussed, highlighting the evolutionary nature of the overall process and the iterative nature of the various tasks carried out. The emphasis of this paper is on the process of the development with the following being covered: (1) the three phases of the SCOS 2 project - prototyping & analysis, design & implementation and configuration / delivery of mission specific systems; (2) the close cooperation and continual interaction with the users during the development; (3) the management approach - the split between client staff, industry and some of the required project management activities; (4) the lifecycle adopted being an enhancement of the ESA PSS-05 standard with SCOS 2 specific activities and approaches defined; and (5) an examination of some of the difficulties encountered and the solutions adopted. Finally, the lessons learned from the SCOS 2 experience are highlighted, identifying those issues to be used as feedback into future developments of this nature. This paper does not intend to describe the finished product and its operation, but focusing on the journey to arrive there, concentrating therefore on the process and not the products of the SCOS 2 software development.

Symonds, Martin↗

Software Development Technologies for Reactive, Real-Time, and Hybrid Systems

The research is directed towards the design and implementation of a comprehensive deductive environment for the development of high-assurance systems, especially reactive (concurrent, real-time, and hybrid) systems. Reactive systems maintain an ongoing interaction with their environment, and are among the most difficult to design and verify. The project aims to provide engineers with a wide variety of tools within a single, general, formal framework in which the tools will be most effective. The entire development process is considered, including the construction, transformation, validation, verification, debugging, and maintenance of computer systems. The goal is to automate the process as much as possible and reduce the errors that pervade hardware and software development.

Manna, Zohar↗

Systems Maintenance Automated Repair Tasks (SMART)

SMART is a uniform automated discrepancy analysis and repair-authoring platform that improves technical accuracy and timely delivery of repair procedures for a given discrepancy (see figure a). SMART will minimize data errors, create uniform repair processes, and enhance the existing knowledge base of engineering repair processes. This innovation is the first tool developed that links the hardware specification requirements with the actual repair methods, sequences, and required equipment. SMART is flexibly designed to be useable by multiple engineering groups requiring decision analysis, and by any work authorization and disposition platform (see figure b). The organizational logic creates the link between specification requirements of the hardware, and specific procedures required to repair discrepancies. The first segment in the SMART process uses a decision analysis tree to define all the permutations between component/ subcomponent/discrepancy/repair on the hardware. The second segment uses a repair matrix to define what the steps and sequences are for any repair defined in the decision tree. This segment also allows for the selection of specific steps from multivariable steps. SMART will also be able to interface with outside databases and to store information from them to be inserted into the repair-procedure document. Some of the steps will be identified as optional, and would only be used based on the location and the current configuration of the hardware. The output from this analysis would be sent to a work authoring system in the form of a predefined sequence of steps containing required actions, tools, parts, materials, certifications, and specific requirements controlling quality, functional requirements, and limitations.

Schuh, Joseph↗