SEARCH · Search NASA
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.
The Preventive Maintenance (PM) program at Stennis Space Center (SSC) evolved from an ineffective and poorly organized state to a highly organized state in which it became capable of tracking equipment, planning jobs with man hour estimates, and supporting outsourcing. This viewgraph presentation traces the steps the program took to improve itself.
A model is formulated to describe the effect of the time interval chosen for preventive maintenance upon the frequency of failure and frequency of total maintenance. Trade-offs between these two frequencies are determined by computation of an optimal interval in the case where the failure distribution is known. For unknown distributions, an adaptive statistical technique is developed that converges to an optimal preventive maintenance interval. A numerical illustration is given.
Preventive maintenance instructions for bonding and electrical grounding systems to prevent equipment damage by electrical faults, lightning, and radiation - Vol. 3
Reliability equation for complex system with preventive maintenance
To maximize reliability of a spacecraft which performs long-life (over 10-year), deep-space mission (to outer planet), a fault-tolerant environment incorporating automatic on-board preventive maintenance is highly desirable.
Initial data for optimal duration of preventive maintenance in system with possible fault
The long-life deep-space missions associated with NASA's X2000 Advanced Flight Systems Program creates many unprecedented challenges for us.
With respect to the long-life missions associated with NASA's X2000 Advanced Deep-Space System Development Program, reliability implies a system's continuous operation for many years in an unsurveyed radiation-intense environment.
Maintenance program which is concise and inexpensive to operate adapts to almost any system that has a FORTRAN compiler. Program operates on a stored data base with an output consisting of scheduling information and various management reports.
This paper illustrates using Markov models to establish system and maintenance requirements for small electronic controllers where the goal is a high probability of continuous service for a long period of time. The system and maintenance items considered are quality of components, various degrees of simple redundancy, redundancy with reconfiguration, diagnostic levels, periodic maintenance, and preventive maintenance. Markov models permit a quantitative investigation with comparison and contrast. An element of special interest is the use of conditional probability to study the combination of imperfect diagnostics and periodic maintenance.
Preventive maintenance, calibration procedures, system verification, system operating procedures, systems software fundamentals, data base (program files), and patchboard layout are discussed.
It is essential that management and engineering understand the need for an availability requirement for the customer's space transportation system as it enables the meeting of his needs, goal, and objectives. There are three types of availability, e.g., operational availability, achieved availability, or inherent availability. The basic definition of availability is equal to the mean uptime divided by the sum of the mean uptime plus the mean downtime. The major difference is the inclusiveness of the functions within the mean downtime and the mean uptime. This paper will address tIe inherent availability which only addresses the mean downtime as that mean time to repair or the time to determine the failed article, remove it, install a replacement article and verify the functionality of the repaired system. The definitions of operational availability include the replacement hardware supply or maintenance delays and other non-design factors in the mean downtime. Also with inherent availability the mean uptime will only consider the mean time between failures (other availability definitions consider this as mean time between maintenance - preventive and corrective maintenance) that requires the repair of the system to be functional. It is also essential that management and engineering understand all influencing attributes relationships to each other and to the resultant inherent availability requirement. This visibility will provide the decision makers with the understanding necessary to place constraints on the design definition for the major drivers that will determine the inherent availability, safety, reliability, maintainability, and the life cycle cost of the fielded system provided the customer. This inherent availability requirement may be driven by the need to use a multiple launch approach to placing humans on the moon or the desire to control the number of spare parts required to support long stays in either orbit or on the surface of the moon or mars. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability, but also provide the capability to bound the variables providing engineering the insight required to control the system's engineering solution. An example of this visibility will be the need to provide integration of similar discipline functions to allow control of the total parts count of the space transportation system. Also the relationship visibility of selecting a reliability requirement will place a constraint on parts count to achieve a given inherent availability requirement or accepting a larger parts count with the resulting higher reliability requirement. This paper will provide an understanding for the relationship of mean repair time (mean downtime) to maintainability, e.g., accessibility for repair, and both mean time between failure, e.g., reliability of hardware and the system inherent availability. Having an understanding of these relationships and resulting requirements before starting the architectural design concept definition will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.
The maintenance data base collected for 15 weeks of recent unattended and automated operation of DSS 13 is summarized. During this period, DSS 13 was receiving spacecraft telemetry while being controlled remotely from JPL in Pasadena. Corrective and preventive maintenance manhours are reported by subsystem for DSS 13 including the equipment added for the automation demonstration. The corrective and preventive maintenance weekly manhours at DSS 13 averaged 22 and 40, respectively. The antenna hydraulic and electronic systems accounted for about half of the preventive and corrective maintenance manhours for a comparable attended DSN station, DSS 11.
The data base collected during a six month demonstration of an automated Deep Space Station (DSS 13) run unattended and remotely controlled is summarized. During this period, DSS 13 received spacecraft telemetry data from Voyager, Pioneers 10 and 11, and Helios projects. Corrective and preventive maintenance are reported by subsystem including the traditional subsystems and those subsystems added for the automation demonstration. Operations and maintenance data for a comparable manned Deep Space Station (DSS 11) are also presented for comparison. The data suggests that unattended operations may reduce maintenance manhours in addition to reducing operator manhours. Corrective maintenance for the unmanned station was about one third of the manned station, and preventive maintenance was about one half.
The NSTTF O&M Project continues the operation and maintenance activities of the existing critical capabilities and infrastructure at the NSTTF. This project is to support and assure the success of Solar Heat for Industrial Process in the United States and the larger global community by ensuring the NSTTF is a safe and operational facility. The primary goal of this project will be to maintain the solar tower and heliostat field while also allowing NSTTF staff to improve processes for operations and maintenance. This includes expanding our preventative maintenance program, inventory systems, and our data sharing capabilities. Additionally, this will support an outreach program with regular seminars, sharing of data, and the release of open-source software to support heliostat metrology
The operation and maintenance procedures are described for the development model of the fire rescue air pack (FRAP) voice amplifier assembly, including the battery charger. Operational instructions include a general description of the assembly, specifications, and installation and operation. Maintenance instructions include theory of operation, preventive maintenance, repair, adjustment, and a parts list. The FRAP is intended to permit fire rescue personnel to enter a smoke-filled, toxic or oxygen depleted environment carrying their own source of breathing air. The voice amplifier assembly permits the wearer to communicate by voice with other persons in the vicinity. The battery charger assembly provides a means of keeping the amplifier batteries fully charged.
Maintenance data includes information on maintenance performed on the electric vehicles, including preventive maintenance, service calls, and availability of the vehicles. The parameters collected, and their definitions, will vary due to the differences in maintenance tracking systems that exist between fleets. Parameter definitions are detailed in the data dictionary, and specific vehicle information is available in the vehicle attributes table. Vehicle ID can be used as a key between maintenance data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.
Maintenance practices have long focused on time based "preventive maintenance" techniques. Components were changed out and parts replaced based on how long they had been in place instead of what condition they were in. A reliability centered maintenance (RCM) program seeks to offer equal or greater reliability at decreased cost by insuring only applicable, effective maintenance is performed and by in large part replacing time based maintenance with condition based maintenance. A significant portion of this program involved introducing non-intrusive technologies, such as vibration analysis, oil analysis and I/R cameras, to an existing labor force and management team.