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.

SourceResearch connectionFrom yearThrough year

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

At least 595 records · Page 33

All sources NASA NTRS DOE OSTI

NASA NTRS1994

Undersea applications of dexterous robotics

The revolution and application of dexterous robotics in the undersea energy production industry and how this mature technology has affected planned SSF dexterous robotic tasks are examined. Undersea telerobotics, or Remotely Operated Vehicles (ROV's), have evolved in design and use since the mid-1970s. Originally developed to replace commercial divers for both planned and unplanned tasks, they are now most commonly used to perform planned robotic tasks in all phases of assembly, inspection, and maintenance of undersea structures and installations. To accomplish these tasks, the worksites, the tasks themselves, and the tools are now engineered with both the telerobot's and the diver's capabilities in mind. In many cases, this planning has permitted a reduction in telerobot system complexity and cost. The philosophies and design practices that have resulted in the successful incorporation of telerobotics into the highly competitive and cost conscious offshore production industry have been largely ignored in the space community. Cases where these philosophies have been adopted or may be successfully adopted in the near future are explored.

Gittleman, Mark M.↗

NASA NTRS2003

A Brighter Choice for Safety

Emergency exit signs can be lifesavers, but only if they remain visible when people need them. All too often, power losses or poor visibility can render the signs ineffective. Luna Technologies International, Inc., of Kent, Washington, is shining new light on this safety issue. The company s LUNAplast(trademark) product line illuminates without the need for electricity, maintenance, or a power connection. LUNAplast, which benefited from tests conducted at Johnson Space Center, is so successful that NASA engineers selected it for the emergency exit pathway indicators on the International Space Station (ISS).

Source record↗

NASA NTRS2008

The NASA Orbiting Carbon Observatory (OCO) Mission: Objectives, Approach, and Status

The Orbiting Carbon Observatory (OCO) is a NASA Earth System Science Pathfinder (ESSP) mission that is currently under development at the Jet Propulsion Laboratory (JPL). OCO will make global, space-based measurements of atmospheric carbon dioxide (CO2) with the precision, resolution, and coverage needed to characterize regional-scale sources and sinks of this important greenhouse gas. The observatory consists of a dedicated spacecraft bus that carries a single instrument. The bus employs single-string version of Orbital Sciences Corporation (OSC) LEOStar-2 architecture. This 3-axis stabilized bus includes a propulsion system for orbit insertion and maintenance, provides power, points the instrument, receives and processes commands from the ground, and records, stores, and downlinks science and engineering data. The OCO instrument incorporates 3 oboresighted, high resolution grating spectrometers that will make coincident measurements of reflected sunlight in near-infrared CO2 and molecular oxygen (O2) bands. The instrument was designed and manufactured by Hamilton Sundstrand (Pomona, CA), and then integrated, flight qualified, and calibrated by JPL. It is scheduled for delivery to OSC (Dulles, VA) for integration with the spacecraft bus in the spring of 2008. OCO will be launched from the Vandenberg Air Force Base on a dedicated OSC Taurus XL launch vehicle in December 2008. It will fly in formation with the Earth Observing System Afternoon Constellation, a group of satellites that files in a 98.8 minute, 705 km altitude, sun-synchronous orbit. This orbit provides coverage of the sunlit hemisphere with a 16-day ground track repeat cycle. OCO will fly approx.4 minutes ahead of the EOS Aqua platform, with an ascending nodal crossing time of approx.1:26 PM. The OCO science data will be transmitted to the NASA Ground Network Stations in Alaska and Virginia, and then transferred to the OCO Ground Data System at JPL. There, the CO2 and O2 spectra will be analyzed by the OCO Science Team to provide spatially resolved estimates of the column-averaged CO2 dry air mole fraction, XCO2. These measurements are expected to improve our understanding of the nature and processes that regulate atmospheric CO2 enabling more reliable forecasts of CO2 buildup and its impact on climate change.

global measurements↗

NASA NTRS1982

Other Fabric Structures

Architects, engineers and building owners are turning increasingly to fabric structures because of their aesthetic appeal, relatively low initial cost, low maintenance outlays, energy efficiency and good space utilization. Several examples are shown.

Source record↗

NASA NTRS2010

SSME Electrical Harness and Cable Development and Evolution

The Space Shuttle Main Engine (SSME) electrical harness and cable system consists of the various interconnecting devices necessary for operation of complex rocket engine functions. Thirty seven harnesses incorporate unique connectors, backshell adapters, conductors, insulation, shielding, and physical barriers for a long maintenance-free life while providing the means to satisfy performance requirements and to mitigate adverse environmental influences. The objective of this paper is to provide a description of the SSME electrical harness and cable designs as well as the development history and lessons learned.

Abrams, Russ↗

NASA NTRS1985

Some key considerations in evolving a computer system and software engineering support environment for the space station program

The space station data management system involves networks of computing resources that must work cooperatively and reliably over an indefinite life span. This program requires a long schedule of modular growth and an even longer period of maintenance and operation. The development and operation of space station computing resources will involve a spectrum of systems and software life cycle activities distributed across a variety of hosts, an integration, verification, and validation host with test bed, and distributed targets. The requirement for the early establishment and use of an apporopriate Computer Systems and Software Engineering Support Environment is identified. This environment will support the Research and Development Productivity challenges presented by the space station computing system.

Mckay, C. W.↗

DOE OSTI2026

Extending Component Lifetime And Improving Inverter Reliability (ECLAIIR)

Inverter reliability remains one of the most persistent challenges limiting the performance, availability, and economic viability of utility‑scale photovoltaic (PV) plants. Industry data consistently show that inverters account for the highest share of corrective maintenance events and unplanned outages across PV fleets. These failures result in energy losses, increased O&M costs, and reduced confidence in long‑term solar asset performance. Motivated by these challenges, this project—Extending Component Lifetime and Improving Inverter Reliability (ECLAIIR)—was undertaken to systematically investigate inverter degradation and failure mechanisms, develop predictive maintenance capabilities, and establish data‑driven pathways to improve service life and reduce the Levelized Cost of Energy (LCOE) for large‑scale PV systems. The primary goal of the project was to identify pre‑failure signatures in string inverters using both lab‑based accelerated lifetime testing and field‑based data and to develop predictive maintenance algorithms that can anticipate inverter faults before they occur. Through collaboration with inverter testing laboratory, solar PV plant owner, and failure‑analysis experts, the project advanced the technical understanding of inverter reliability. By instrumenting inverters with thermistors, humidity sensors, power‑quality meters, and acoustic sensors, the research established how multiple sensing modalities can reliably detect deviations from normal behavior hours to days before failure. These findings substantially enhance scientific understanding of inverter failure kinetics and provide the PV industry with the most comprehensive cross‑OEM characterization of early‑stage failure indicators reported to date. Technically, the project demonstrated the effectiveness of predictive maintenance by developing and validating the PreDICT (Predictive Diagnostics of PV Inverters Using Condition Monitoring and Trend Analysis) framework—a multi‑layer diagnostic architecture combining peer‑to‑peer analytics, historical trend modeling, and advanced machine‑learning techniques such as the Sequential Conditional Variational Autoencoder (SCVAE). This predictive model achieved more than 90% accuracy in detecting pre‑failure conditions and provided up to four days of lead time before inverter failure in field scenarios. Economically, the project’s LCOE analysis showed that predictive maintenance can reduce lifetime energy losses and minimize corrective maintenance interventions. Modeling indicated that, depending on inverter failure rates and replacement timelines, predictive maintenance can significantly reduce LCOE impacts associated with inverter downtime: from as high as 19.4% under conventional maintenance strategies to 0.1%–10.17% when predictive analytics are adopted. These results confirm that predictive maintenance is both technically feasible and economically advantageous for utilities and plant operators. The project’s findings also have broad public benefit. By improving inverter reliability and reducing downtime, predictive maintenance directly increases electricity generation from existing PV assets. Enhanced reliability lowers operational costs for utilities, which can translate over time into lower energy costs for consumers. Furthermore, the project’s technical publications, conference presentations, and industry workshops ensure that knowledge gained is shared broadly across the solar industry, supporting workforce development and enabling utilities of all sizes to adopt modern asset‑health monitoring practices. The retrofitting case study and service‑life prediction framework further support informed decision‑making for aging PV fleets, helping operators extend system life and reduce electronic waste. In summary, the ECLAIIR project significantly advanced the state of knowledge on inverter degradation, demonstrated the technical and economic value of predictive maintenance, and delivered actionable tools and insights that support more reliable, cost‑effective, and sustainable PV plant operation. The outcomes of this project will continue to inform utility practices, guide inverter design improvements, and strengthen the long‑term performance of solar assets nationwide.

14 SOLAR ENERGY↗

NASA NTRS1992

Advanced software development workstation project: Engineering scripting language. Graphical editor

Software development is widely considered to be a bottleneck in the development of complex systems, both in terms of development and in terms of maintenance of deployed systems. Cost of software development and maintenance can also be very high. One approach to reducing costs and relieving this bottleneck is increasing the reuse of software designs and software components. A method for achieving such reuse is a software parts composition system. Such a system consists of a language for modeling software parts and their interfaces, a catalog of existing parts, an editor for combining parts, and a code generator that takes a specification and generates code for that application in the target language. The Advanced Software Development Workstation is intended to be an expert system shell designed to provide the capabilities of a software part composition system.

Source record↗

NASA NTRSDate not supplied

Short Circuiting the Controller –Missteps in Maintenance and Inspection of Process and Wiring in STS-93

During the launch of the Chandra X-Ray Observatory in 1999, an in-flight anomaly occurred a few seconds after liftoff. A power fluctuation caused two Main Engine controllers to drop offline. Fortunately, due to redundancy, the Space Shuttle Columbia was able to successfully reach orbit and avoid an abort. After the successful deployment of Chandra and the safe return of the crew, in-vestigation revealed that the controller failure was due to a wire short in the pay-load bay. It was suspected that the Kapton insulation on the wire rubbed off against a burred screw head, the result of overtightening of the screw during a maintenance event 4 to 5 years prior to the STS-93 mission. Vibrations led the abraded wire to short during flight. The Space Shuttle Program was grounded for 4 months while a program-wide inspection and wire chafing mitigation effort of all orbiter wiring ensued.

Kristy S Yun↗

NASA NTRS1986

Astronomy on a manned Mars mission

Three extra-solar-system astronomical experiments onboard a manned Mars mission are proposed. First, a modest, 50 cm aperture optical-ultraviolet-infrared telescope (or pair used as an interferometer) coupled with the Mars-Sun baseline would increase the number (by a factor of 3.4) and a volume of stars with accurately measured distances via stellar parallax and, therefore, greatly improve upon the cosmic distance scale; the darker sky at Mars would also provide nearly a full astronomical magnitude deeper images of distant and low brightness objects (limited by zodiacal light). Second, a gamma-ray burst detector coupled with similar detectors in other parts of the solar system will be used to reduce the position error boxes and to study the nature of these energetic sources. Third, the long baselines on a Mars mission radio interferometer will provide a view of the radio universe at unprescedented resolution, 4 x 10 to the minus 9th arcsec at 1 mm wavelength, which can potentially resolve the engine in nearby active galaxies. Each of these experiments is relatively inexpensive, taking advantage of the human presence for operation and maintenance, and the long Earth to Mars baseline.

Burns, Jack O.↗

NASA NTRS1996

The shuttle main engine: A first look

Anyone entering the Space Shuttle Main Engine (SSME) team attends a two week course to become familiar with the design and workings of the engine. This course provides intensive coverage of the individual hardware items and their functions. Some individuals, particularly those involved with software maintenance and development, have felt overwhelmed by this volume of material and their lack of a logical framework in which to place it. To provide this logical framework, it was decided that a brief self-taught introduction to the overall operation of the SSME should be designed. To aid the people or new team members with an interest in the software, this new course should also explain the structure and functioning of the controller and its software. This paper presents a description of this presentation.

Schreur, Barbara↗

NASA NTRS1997

Designing for Maintainability and System Availability

The final goal for a delivered system (whether a car, aircraft, avionics box or computer) should be its availability to operate and perform its intended function over its expected design life. Hence, in designing a system, we cannot think in terms of delivering the system and just walking away. The system supplier needs to provide support throughout the operating life of the product. Here, supportability requires an effective combination of reliability, maintainability, logistics and operations engineering (as well as safety engineering) to have a system that is available for its intended use throughout its designated mission lifetime. Maintainability is a key driving element in the effective support and upkeep of the system as well as providing the ability to modify and upgrade the system throughout its lifetime. This paper then, will concentrate on maintainability and its integration into the system engineering and design process. The topics to be covered include elements of maintainability, the total cost of ownership, how system availability, maintenance and logistics costs and spare parts cost effect the overall program costs. System analysis and maintainability will show how maintainability fits into the overall systems approach to project development. Maintainability processes and documents will focus on how maintainability is to be performed and what documents are typically generated for a large scale program. Maintainability analysis shows how trade-offs can be performed for various alternative components. The conclusions summarize the paper and are followed by specific problems for hands-on training.

Lalli, Vincent R.↗

NASA NTRS1989

Required Technologies for A 10-16 m UV-Visible-IR Telescope on the Moon

A successor to the Hubble Space Telescope, incorporating a 10 to 16 meter mirror, and operating in the UV-Visible-IR is being considered for emplacement on the Moon in the 21st Century. To take advantage of the characteristics of the lunar environment, such a telescope requires appropriate advances in technology. These technologies are in the areas of contamination/interference control, test and evaluation, manufacturing, construction, autonomous operations and maintenance, power and heating/cooling, stable precision structures, optics, parabolic antennas, and communications/control. This telescope for the lunar surface needs to be engineered to operate for long periods with minimal intervention by humans or robots. What is essential for lunar observatory operation is enforcement of a systems engineering approach that makes compatible all lunar operations associated with habitation, resource development, and science.

Johnson, Stewart W.↗

NASA NTRS2020

Blackbird: Object-Oriented Planning, Simulation, and Sequencing Framework Used by Multiple Missions

Every JPL flight mission relies on activity planning and sequence generation software to perform operations. Most such tools in use at JPL and elsewhere use attribute-based schemas or domain-specific languages (DSLs) to define activities. This reliance poses user training, software maintenance, performance, and other challenges. To solve this problem for future missions, a new software called Blackbird was developed which allows engineers to specify behavior in standard Java. The new code base has over an order of magnitude fewer lines of code than other JPL planning software, since no DSL or schema interpreter is needed. The use of Java for defining activities also allows mission adapters to debug their code in an integrated development environment, seamlessly call external libraries, and set up truly multimission models. These efficiency gains have significantly reduced the amount of development effort required to support the software. This paper discusses Blackbird’s design, principles, and use cases.

Lawler, Christopher↗

NASA NTRS1995

A Comprehensive Approach to Management of Workplace and Environmental Noise at NASA Lewis Research Center

NASA Lewis Research Center is home to more than 100 experimental research testing facilities and laboratories, including large wind tunnels and engine test cells, which in combination create a varied and complex noise environment. Much of the equipment was manufactured prior to the enactment of legislation limiting product noise emissions or occupational noise exposure. Routine facility maintenance and associated construction also contributes to a noise exposure management responsibility which is equal in magnitude and scope to that of several small industrial companies. The Noise Program, centrally managed within the Office of Environmental Programs at LRC, maintains overall responsibility for hearing conservation, community noise control, and acoustical and noise control engineering. Centralized management of the LRC Noise Program facilitates the timely development and implementation of engineered noise control solutions for problems identified via either the Hearing Conservation of Community Noise Program. The key element of the Lewis Research Center Noise Program, Acoustical and Noise Control Engineering Services, is focused on developing solutions that permanently reduce employee and community noise exposure and maximize research productivity by reducing or eliminating administrative and operational controls and by improving the safety and comfort of the work environment. The Hearing Conservation Program provides noise exposure assessment, medical monitoring, and training for civil servant and contractor employees. The Community Noise Program aims to maintain the support of LRC's neighboring communities while enabling necessary research operations to accomplish their programmatic goals. Noise control engineering capability resides within the Noise Program. The noise control engineering, based on specific exposure limits, is a fundamental consideration throughout the design phase of new test facilities, labs, and office buildings. In summary, the Noise Program addresses hearing conservation, community noise control, and acoustical and noise control engineering.

Cooper, Beth A.↗

DOE OSTI2024

Software stewardship and advancement of a high-performance computing scientific application: QMCPACK

Here, we provide an overview of the software engineering efforts and their impact in QMCPACK, a production-level ab-initio Quantum Monte Carlo open-source code targeting high-performance computing (HPC) systems. Aspects included are: (i) strategic expansion of continuous integration (CI) targeting CPUs, using GitHub Actions own runners, and NVIDIA and AMD GPUs used in pre-exascale systems, (ii) incremental reduction of memory leaks using sanitizers, (iii) incorporation of Docker containers for CI and reproducibility, and (iv) refactoring efforts to improve maintainability, testing coverage, and memory lifetime management. We quantify the value of these improvements by providing metrics to illustrate the shift towards a predictive, rather than reactive, maintenance approach. Our goal, in documenting the impact of these efforts on QMCPACK, is to contribute to the body of knowledge on the importance of research software engineering (RSE) for the stewardship and advancement of community HPC codes to enable scientific discovery at scale.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2024

Software engineering to sustain a high-performance computing scientific application: QMCPACK

We provide an overview of the software engineering efforts and their impact in QMCPACK, a production-level ab-initio Quantum MonteCarlo open-source code targeting high-performance computing (HPC) systems. Aspects included are: (i) strategic expansion ofcontinuous integration (CI) targeting CPU, using GitHub Actions runners, and graphics processing units (GPU) in pre-exascalesystems, using self-hosted hardware; (ii) incremental reduction of memory leaks using sanitizers, (iii) incorporation of Dockercontainers for CI and reproducibility, and (iv) refactoring efforts to improve maintainability, testing coverage, and memory lifetime management. We quantify the value of these improvements by providing metrics to illustrate the shift towards a predictive, rather than reactive, sustainable maintenance approach. Our goal, in documenting the impact of these efforts on QMCPACK, is to contribute to the body of knowledge on the importance of research software engineering (RSE) for the sustainability of community HPC codes and scientific discovery at scale.

Godoy, William↗

NASA NTRS1996

Software Engineering Program: Software Process Improvement Guidebook

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Source record↗