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 847 records · Page 47

Low loss injector for Space Shuttle main engine. Center director's discretionary fund

An efficient propellant injection method to raise the Space Shuttle Main Engine (SSME) thrust and payload is discussed. Relatively large diameter injector elements with low pressure loss are recommended for the main combustion chamber and the pre-burners. Smaller losses admit more propellant flow which then raises thrust. Payload is not only gained by specific impulse but also by thrust. The chamber pressure is stabilized by selecting the proper cavity size for the injector elements while reducing the injection pressure loss which normally is kept high for stability. The rather large injector element recesses provide acoustic damping which makes baffles and acoustic absorbers unnecessary. A tenfold reduction of flow induced stresses which are rather high in the present design is shown. Relaxed tolerances, fewer elements, and better maintenance are offered. The study was conducted under a center director discretionary fund assignment.

Vonpragenau, G. L.↗

Avionics System Architecture for the NASA Orion Vehicle

It has been 30 years since the National Aeronautics and Space Administration (NASA) last developed a crewed spacecraft capable of launch, on-orbit operations, and landing. During that time, aerospace avionics technologies have greatly advanced in capability, and these technologies have enabled integrated avionics architectures for aerospace applications. The inception of NASA s Orion Crew Exploration Vehicle (CEV) spacecraft offers the opportunity to leverage the latest integrated avionics technologies into crewed space vehicle architecture. The outstanding question is to what extent to implement these advances in avionics while still meeting the unique crewed spaceflight requirements for safety, reliability and maintainability. Historically, aircraft and spacecraft have very similar avionics requirements. Both aircraft and spacecraft must have high reliability. They also must have as much computing power as possible and provide low latency between user control and effecter response while minimizing weight, volume, and power. However, there are several key differences between aircraft and spacecraft avionics. Typically, the overall spacecraft operational time is much shorter than aircraft operation time, but the typical mission time (and hence, the time between preventive maintenance) is longer for a spacecraft than an aircraft. Also, the radiation environment is typically more severe for spacecraft than aircraft. A "loss of mission" scenario (i.e. - the mission is not a success, but there are no casualties) arguably has a greater impact on a multi-million dollar spaceflight mission than a typical commercial flight. Such differences need to be weighted when determining if an aircraft-like integrated modular avionics (IMA) system is suitable for a crewed spacecraft. This paper will explore the preliminary design process of the Orion vehicle avionics system by first identifying the Orion driving requirements and the difference between Orion requirements and those of other previous crewed spacecraft avionics systems. Common systems engineering methods will be used to evaluate the value propositions, or the factors that weight most heavily in design consideration, of Orion and other aerospace systems. Then, the current Orion avionics architecture will be presented and evaluated.

Baggerman, Clint↗

A Software Architecture for Intelligent Synthesis Environments

The NASA's Intelligent Synthesis Environment (ISE) program is a grand attempt to develop a system to transform the way complex artifacts are engineered. This paper discusses a "middleware" architecture for enabling the development of ISE. Desirable elements of such an Intelligent Synthesis Architecture (ISA) include remote invocation; plug-and-play applications; scripting of applications; management of design artifacts, tools, and artifact and tool attributes; common system services; system management; and systematic enforcement of policies. This paper argues that the ISA extend conventional distributed object technology (DOT) such as CORBA and Product Data Managers with flexible repositories of product and tool annotations and "plug-and-play" mechanisms for inserting "ility" or orthogonal concerns into the system. I describe the Object Infrastructure Framework, an Aspect Oriented Programming (AOP) environment for developing distributed systems that provides utility insertion and enables consistent annotation maintenance. This technology can be used to enforce policies such as maintaining the annotations of artifacts, particularly the provenance and access control rules of artifacts-, performing automatic datatype transformations between representations; supplying alternative servers of the same service; reporting on the status of jobs and the system; conveying privileges throughout an application; supporting long-lived transactions; maintaining version consistency; and providing software redundancy and mobility.

Filman, Robert E.↗

Developing a Fleet Standardization Index for Airline Planning

Quantifying subjective aspects is a difficult task that requires a great dedication of time from researchers and analysts. Nevertheless, one of the main objectives of it is to pave the way for a better understanding of the focused aspects. Fleet standardization is one of these subjective aspects that is extremely difficult to mm into numbers. Although, it is of great importance to know the benefits that may come with a higher level of standardization for airlines, which may be economical advantages, maintenance facilitation and others. A more standardized fleet may represent lower costs of operations and maintenance facilitation and others. A more standardized fleet may represent lower costs of operations and maintenance plus a much better planning of routes and flights. This study presents the first step on developing an index, hereto called "Fleet Standardization Index" or FSI (or IPF in Portuguese, for "Indice de Padronizacao de Frotas"), that will allow senior airline planners to compare different fleets and also simulate some results from maintaining or renewing their fleets. Although being a preliminary study, the results obtained may already be tested to compare different fleets (different airlines) and also analyze some possible impacts of a fleet renewal before it takes place. Therefore, the main objective of this paper is to introduce the proposed IPF index and to demonstrate that it is inversely proportional to the number of different airplane models, engines and other equipment, such as avionics.

deBorgesPan, Alexis George↗

Rotorcraft Diagnostics

Health management (HM) in any engineering systems requires adequate understanding about the system s functioning; a sufficient amount of monitored data; the capability to extract, analyze, and collate information; and the capability to combine understanding and information for HM-related estimation and decision-making. Rotorcraft systems are, in general, highly complex. Obtaining adequate understanding about functioning of such systems is quite difficult, because of the proprietary (restricted access) nature of their designs and dynamic models. Development of an EIM (exact inverse map) solution for rotorcraft requires a process that can overcome the abovementioned difficulties and maximally utilize monitored information for HM facilitation via employing advanced analytic techniques. The goal was to develop a versatile HM solution for rotorcraft for facilitation of the Condition Based Maintenance Plus (CBM+) capabilities. The effort was geared towards developing analytic and reasoning techniques, and proving the ability to embed the required capabilities on a rotorcraft platform, paving the way for implementing the solution on an aircraft-level system for consolidation and reporting. The solution for rotorcraft can he used offboard or embedded directly onto a rotorcraft system. The envisioned solution utilizes available monitored and archived data for real-time fault detection and identification, failure precursor identification, and offline fault detection and diagnostics, health condition forecasting, optimal guided troubleshooting, and maintenance decision support. A variant of the onboard version is a self-contained hardware and software (HW+SW) package that can be embedded on rotorcraft systems. The HM solution comprises components that gather/ingest data and information, perform information/feature extraction, analyze information in conjunction with the dependency/diagnostic model of the target system, facilitate optimal guided troubleshooting, and offer decision support for optimal maintenance.

Haste, Deepak↗

Robonaut: a robot designed to work with humans in space

The Robotics Technology Branch at the NASA Johnson Space Center is developing robotic systems to assist astronauts in space. One such system, Robonaut, is a humanoid robot with the dexterity approaching that of a suited astronaut. Robonaut currently has two dexterous arms and hands, a three degree-of-freedom articulating waist, and a two degree-of-freedom neck used as a camera and sensor platform. In contrast to other space manipulator systems, Robonaut is designed to work within existing corridors and use the same tools as space walking astronauts. Robonaut is envisioned as working with astronauts, both autonomously and by teleoperation, performing a variety of tasks including, routine maintenance, setting up and breaking down worksites, assisting crew members while outside of spacecraft, and serving in a rapid response capacity.

Man-Machine Systems↗

Advanced Prop-fan Engine Technology (APET) single- and counter-rotation gearbox/pitch change mechanism

The preliminary design of advanced technology (1992) turboprop engines for single-rotation prop-fans and conceptual designs of pitch change mechanisms for single- and counter-rotation prop-fan application are discussed. The single-rotation gearbox is a split path, in-line configuration. The counter-rotation gearbox is an in-line, differential planetary design. The pitch change mechanisms for both the single- and counter-rotation arrangements are rotary/hydraulic. The advanced technology single-rotation gearbox yields a 2.4 percent improvement in aircraft fuel burn and a one percent improvement in operating cost relative to a current technology gearbox. The 1992 counter-rotation gearbox is 15 percent lighter, 15 percent more reliable, 5 percent lower in cost, and 45 percent lower in maintenance cost than the 1992 single-rotation gearbox. The pitch controls are modular, accessible, and external.

Reynolds, C. N.↗

Bibliography of NASA-related publications on wind turbine technology 1973-1995

A major program of research and development projects on wind turbines for generating electricity was conducted at the NASA Lewis Research Center from 1973 to 1988. Most of these projects were sponsored by the U.S. Department of Energy (DOE), as a major element of its Federal Wind Energy Program. One other large-scale wind turbine project was sponsored by the Bureau of Reclamation of the Department of Interior (DOI). The peak years for wind energy work at Lewis were 1979-80, when almost 100 engineers, technicians, and administrative personnel were involved. From 1988 their conclusion in 1995, NASA wind energy activities have been directed toward the transfer of technology to commercial and academic organizations. Wind energy activities at NASA can be divided into two broad categories which are closely related and often overlapping: (1) Designing, building, and testing a series of 12 large-scale, experimental, horizontal-axis wind turbines (HAWT's); and (2) conducting supporting research and technology (SR&T) projects. The purpose of this bibliography is to assist those active in the field of wind energy in locating the technical information they need on wind power planning, wind loads, turbine design and analysis, fabrication and installation, laboratory and field testing, and operations and maintenance. This bibliography contains approximately 620 citations of publications by over 520 authors and co-authors. Sources are: (1) NASA reports authored by government grantee, and contractor personnel, (2) papers presented by attendees at NASA-sponsored workshops and conferences, (3) papers presented by NASA personnel at outside workshops and conferences, and (4) outside publications related to research performed at NASA/ DOE wind turbine sites.

Spera, David A.↗

Buckets: Smart Objects for Digital Libraries

Current discussion of digital libraries (DLs) is often dominated by the merits of the respective storage, search and retrieval functionality of archives, repositories, search engines, search interfaces and database systems. While these technologies are necessary for information management, the information content is more important than the systems used for its storage and retrieval. Digital information should have the same long-term survivability prospects as traditional hardcopy information and should be protected to the extent possible from evolving search engine technologies and vendor vagaries in database management systems. Information content and information retrieval systems should progress on independent paths and make limited assumptions about the status or capabilities of the other. Digital information can achieve independence from archives and DL systems through the use of buckets. Buckets are an aggregative, intelligent construct for publishing in DLs. Buckets allow the decoupling of information content from information storage and retrieval. Buckets exist within the Smart Objects and Dumb Archives model for DLs in that many of the functionalities and responsibilities traditionally associated with archives are pushed down (making the archives dumber) into the buckets (making them smarter). Some of the responsibilities imbued to buckets are the enforcement of their terms and conditions, and maintenance and display of their contents.

Nelson, Michael L.↗

Integrating MBSE into Ongoing Projects: Requirements Validation and Test Planning for the ISS SAFER

The International Space Station (ISS) Simplified Aid for Extra Vehicular Activity (EVA) Rescue (SAFER) is the spacewalking astronaut's final safety measure against separating from the ISS and being unable to return safely. Since the late 1990s, the SAFER has been a standard element of the spacewalking astronaut's equipment. The ISS SAFER project was chartered to develop a new block of SAFER units using a highly similar design to the legacy SAFER (known as the USA SAFER). An on-orbit test module was also included in the project to enable periodic maintenance/propulsion system checkout on the ISS SAFER. On the ISS SAFER project, model-based systems engineering (MBSE) was not the initial systems engineering (SE) approach, given the volume of heritage systems engineering and integration (SE&I) products. The initial emphasis was ensuring traceability to ISS program standards as well as to legacy USA SAFER requirements. The requirements management capabilities of the Cradle systems engineering tool were to be utilized to that end. During development, however, MBSE approaches were applied selectively to address specific challenges in requirements validation and test and verification (T&V) planning, which provided measurable efficiencies to the project. From an MBSE perspective, ISS SAFER development presented a challenge and an opportunity. Addressing the challenge first, the project was tasked to use the original USA SAFER operational and design requirements baseline, with a number of additional ISS program requirements to address evolving certification expectations for systems operating on the ISS. Additionally, a need to redesign the ISS SAFER avionics architecture resulted in a set of changes to the design requirements baseline. Finally, the project added an entirely new functionality for on-orbit maintenance. After initial requirements integration, the system requirements count was approaching 1000, which represented a growth of 4x over the original USA SAFER system. This presented the challenge - How to confirm that this new set of requirements set would result in the creation of the desired capability.

Anderson, Herbert A.↗

[MaRS Project]

The Space Exploration Division of the Safety and Mission Assurances Directorate is responsible for reducing the risk to Human Space Flight Programs by providing system safety, reliability, and risk analysis. The Risk & Reliability Analysis branch plays a part in this by utilizing Probabilistic Risk Assessment (PRA) and Reliability and Maintainability (R&M) tools to identify possible types of failure and effective solutions. A continuous effort of this branch is MaRS, or Mass and Reliability System, a tool that was the focus of this internship. Future long duration space missions will have to find a balance between the mass and reliability of their spare parts. They will be unable take spares of everything and will have to determine what is most likely to require maintenance and spares. Currently there is no database that combines mass and reliability data of low level space-grade components. MaRS aims to be the first database to do this. The data in MaRS will be based on the hardware flown on the International Space Stations (ISS). The components on the ISS have a long history and are well documented, making them the perfect source. Currently, MaRS is a functioning excel workbook database; the backend is complete and only requires optimization. MaRS has been populated with all the assemblies and their components that are used on the ISS; the failures of these components are updated regularly. This project was a continuation on the efforts of previous intern groups. Once complete, R&M engineers working on future space flight missions will be able to quickly access failure and mass data on assemblies and components, allowing them to make important decisions and tradeoffs.

Aruljothi, Arunvenkatesh↗

Re-engineering Nascom's network management architecture

The development of Nascom systems for ground communications began in 1958 with Project Vanguard. The low-speed systems (rates less than 9.6 Kbs) were developed following existing standards; but, there were no comparable standards for high-speed systems. As a result, these systems were developed using custom protocols and custom hardware. Technology has made enormous strides since the ground support systems were implemented. Standards for computer equipment, software, and high-speed communications exist and the performance of current workstations exceeds that of the mainframes used in the development of the ground systems. Nascom is in the process of upgrading its ground support systems and providing additional services. The Message Switching System (MSS), Communications Address Processor (CAP), and Multiplexer/Demultiplexer (MDM) Automated Control System (MACS) are all examples of Nascom systems developed using standards such as, X-windows, Motif, and Simple Network Management Protocol (SNMP). Also, the Earth Observing System (EOS) Communications (Ecom) project is stressing standards as an integral part of its network. The move towards standards has produced a reduction in development, maintenance, and interoperability costs, while providing operational quality improvement. The Facility and Resource Manager (FARM) project has been established to integrate the Nascom networks and systems into a common network management architecture. The maximization of standards and implementation of computer automation in the architecture will lead to continued cost reductions and increased operational efficiency. The first step has been to derive overall Nascom requirements and identify the functionality common to all the current management systems. The identification of these common functions will enable the reuse of processes in the management architecture and promote increased use of automation throughout the Nascom network. The MSS, CAP, MACS, and Ecom projects have indicated the potential value of commercial-off-the-shelf (COTS) and standards through reduced cost and high quality. The FARM will allow the application of the lessons learned from these projects to all future Nascom systems.

Drake, Brian C.↗

The Research of Dr. Joanne Simpson: Fifty Years Investigating Hurricanes, Tropical Clouds and Cloud Systems

This AMS Meteorological Monographs is dedicated to Dr. Joanne Simpson for her many pioneering research efforts in tropical meteorology during her fifty-year career. Dr. Simpson's major areas of scientific research involved the "hot tower" hypothesis and its role in hurricanes, structure and maintenance of trade winds, air-sea interaction, and observations and the mechanism for hurricanes and waterspouts. She was also a pioneer in cloud modeling with the first one-dimensional model and had the first cumulus model on a computer. She also played a major role in planning and leading observational experiments on convective cloud systems. The launch of the Tropical Rainfall Measuring Mission (TRMM) satellite, a joint U.S.-Japan project, in November of 1997 made it possible for quantitative measurements of tropical rainfall to be obtained on a continuous basis over the entire global tropics. Dr. Simpson was the TRAM Project Scientist from 1986 until its launch in 1997. Her efforts during this crucial period ensured that the mission was both well planned scientifically and well engineered as well as within budget. In this paper, Dr. J. Simpson's nine specific accomplishments during her fifty-year career: (1) hot tower hypothesis, (2) hurricanes, (3) airflow and clouds over heated islands, (4) cloud models, (5) trade winds and their role in cumulus development, (6) air-sea interaction, (7) cloud-cloud interactions and mergers, (8) waterspouts, and (9) TRMM science, will be described and discussed.

Tao, W. -K.↗

Can Water-Injected Turbomachines Provide Cost-Effective Emissions and Maintenance Reductions?

An investigation has been performed to evaluate the effect of water injection on the performance of the Air Force Research Laboratory (AFRL, Wright-Patterson Air Force Base (WPAFB)) experimental trapped vortex combustor (TVC) over a range of fuel-to-air and water-to-fuel ratios. Performance is characterized by combustor exit quantities: temperature and emissions measurements using rakes, and overall pressure drop, from upstream plenum to combustor exit. Combustor visualization is performed using gray-scale and color still photographs and high-frame-rate videos. A parallel investigation evaluated the performance of a computational fluid dynamics (CFD) tool for the prediction of the reacting flow in a liquid fueled combustor (e.g., TVC) that uses water injection for control of pollutant emissions and turbine inlet temperature. Generally, reasonable agreement is found between data and NO(x) computations. Based on a study assessing the feasibility and performance impact of using water injection on a Boeing 747-400 aircraft to reduce NO(x) emissions during takeoff, retrofitting does not appear to be cost effective; however, an operator of a newly designed engine and airframe might be able to save up to 1.0 percent in operating costs. Other challenges of water injection will be discussed.

Hendricks, Robert C.↗

Effective Materials Property Information Management for the 21st Century

This paper discusses key principles for the development of materials property information management software systems. There are growing needs for automated materials information management in various organizations. In part these are fueled by the demands for higher efficiency in material testing, product design and engineering analysis. But equally important, organizations are being driven by the need for consistency, quality and traceability of data, as well as control of access to sensitive information such as proprietary data. Further, the use of increasingly sophisticated nonlinear, anisotropic and multi-scale engineering analyses requires both processing of large volumes of test data for development of constitutive models and complex materials data input for Computer-Aided Engineering (CAE) software. And finally, the globalization of economy often generates great needs for sharing a single "gold source" of materials information between members of global engineering teams in extended supply chains. Fortunately, material property management systems have kept pace with the growing user demands and evolved to versatile data management systems that can be customized to specific user needs. The more sophisticated of these provide facilities for: (i) data management functions such as access, version, and quality controls; (ii) a wide range of data import, export and analysis capabilities; (iii) data "pedigree" traceability mechanisms; (iv) data searching, reporting and viewing tools; and (v) access to the information via a wide range of interfaces. In this paper the important requirements for advanced material data management systems, future challenges and opportunities such as automated error checking, data quality characterization, identification of gaps in datasets, as well as functionalities and business models to fuel database growth and maintenance are discussed.

Ren, Weiju↗

Lunar Scout Two spacecraft gravity experiment

Measurement of the gravity field of the Moon has a high science priority because of its implications for the internal structure and thermal history of the Moon, and it has a high priority for future exploration activities because of the influence of lunar gravity on spacecraft navigation and orbit maintenance. The current state of knowledge in the lunar gravity field (and the uncertainty in the knowledge) is based primarily on data accumulated from the Lunar Orbiter and Apollo programs. Data are sparse and emphasize the equatorial band (+/- 30 deg) on the near side of the Moon. There are no tracking data on the far side and only the Lunar Orbiter 5 provides a small amount of high inclination data. A host of gravity models developed from different combinations of tracking data have large discrepancies in their predictions of spacecraft motion and orbit lifetimes. There are also large disagreements in the Mercator projections of the gravity acceleration from each model, especially on the far side, where the contours tend to have no obvious relationship with the local topography. The science and engineering requirements for global gravity field mapping will be satisfied with continuous radio metric tracking of Lunar Scout 1 in a low polar orbit using the Deep Space Network and Lunar Scout 2 in a high elliptical orbit. The gravity field of the Moon will be mapped during the Scout Program using a two spacecraft concept. In the two spacecraft concept, one spacecraft is placed in a high altitude eccentric orbit while the second spacecraft is in a low altitude polar orbit. The gravity experiment requires a radio frequency that will permit two-way Doppler tracking between the spacecraft and the Deep Space Network (DSN). Both spacecraft carry NASA standard transponder systems for data transmission to Earth as well as for tracking and orbit determination. Data sufficient to produce a gravity field map could be acquired within one month with this system.

Cheng, Andrew F.↗

JPL Thermal Design Modeling Philosophy and NASA-STD-7009 Standard for Models and Simulations - A Case Study

The Standard JPL thermal engineering practice prescribes worst-case methodologies for design. In this process, environmental and key uncertain thermal parameters (e.g., thermal blanket performance, interface conductance, optical properties) are stacked in a worst case fashion to yield the most hot- or cold-biased temperature. Thus, these simulations would represent the upper and lower bounds. This, effectively, represents JPL thermal design margin philosophy. Uncertainty in the margins and the absolute temperatures is usually estimated by sensitivity analyses and/or by comparing the worst-case results with "expected" results. Applicability of the analytical model for specific design purposes along with any temperature requirement violations are documented in peer and project design review material. In 2008, NASA released NASA-STD-7009, Standard for Models and Simulations. The scope of this standard covers the development and maintenance of models, the operation of simulations, the analysis of the results, training, recommended practices, the assessment of the Modeling and Simulation (M&S) credibility, and the reporting of the M&S results. The Mars Exploration Rover (MER) project thermal control system M&S activity was chosen as a case study determining whether JPL practice is in line with the standard and to identify areas of non-compliance. This paper summarizes the results and makes recommendations regarding the application of this standard to JPL thermal M&S practices.

thermal blanket performance↗

Automated Performance Characterization of DSN System Frequency Stability Using Spacecraft Tracking Data

This software provides an automated capability to measure and qualify the frequency stability performance of the Deep Space Network (DSN) ground system, using daily spacecraft tracking data. The results help to verify if the DSN performance is meeting its specification, therefore ensuring commitments to flight missions; in particular, the radio science investigations. The rich set of data also helps the DSN Operations and Maintenance team to identify the trends and patterns, allowing them to identify the antennas of lower performance and implement corrective action in a timely manner. Unlike the traditional approach where the performance can only be obtained from special calibration sessions that are both time-consuming and require manual setup, the new method taps into the daily spacecraft tracking data. This new approach significantly increases the amount of data available for analysis, roughly by two orders of magnitude, making it possible to conduct trend analysis with good confidence. The software is built with automation in mind for end-to-end processing. From the inputs gathering to computation analysis and later data visualization of the results, all steps are done automatically, making the data production at near zero cost. This allows the limited engineering resource to focus on high-level assessment and to follow up with the exceptions/deviations. To make it possible to process the continual stream of daily incoming data without much effort, and to understand the results quickly, the processing needs to be automated and the data summarized at a high level. Special attention needs to be given to data gathering, input validation, handling anomalous conditions, computation, and presenting the results in a visual form that makes it easy to spot items of exception/ deviation so that further analysis can be directed and corrective actions followed.

Pham, Timothy T.↗