Industrial Maintenance and Reliability Engineering

01Purpose and scope

• This manual supports the course Industrial Maintenance and Reliability Engineering. It describes how maintenance and reliability work is actually carried out in plants, mills, refineries, food facilities, and similar operations that depend on rotating equipment, process systems, and controls. It is written as a working reference for maintenance planners, reliability engineers, supervisors, technicians, and operations staff who share responsibility for keeping equipment available and safe.
• The scope covers the main activities: deciding what to maintain and how, planning and scheduling work, executing and closing out jobs, monitoring equipment condition, analyzing failures, and feeding lessons back into the program. It does not teach detailed repair procedures for any specific machine. Those belong in the equipment manufacturer documentation and the site procedures that reference it.
• Practice changes a good deal with context. A continuous process plant with few spare units tends to put heavy weight on predictive monitoring and redundancy. A batch facility with many small assets may rely more on time-based inspections and standard repair kits. A fleet of mobile equipment may depend on telematics. This manual points out these differences where they matter, and it names the trade-offs and limits of each approach so that you can adapt the ideas to your own site rather than copying a template.

02Core principles

• Reliability starts with a clear definition of the function an asset must perform and the failures that would stop that function. Without that definition, maintenance becomes a list of tasks copied from a manufacturer manual and adjusted by habit. A pump is not just a pump. It is the means of moving a specific flow at a specific pressure, and its failure modes are the ways it loses that ability.
• Maintenance should be chosen for a reason. Common strategies include run to failure, time-based preventive tasks, condition-based tasks triggered by measured change, and redesign or modification to remove the failure cause. Each has a cost, a risk profile, and a set of conditions under which it is the right choice. Run to failure can be sensible for low-consequence, cheap, quickly replaced items. It is rarely sensible for equipment whose failure creates a safety, environmental, or large production loss.
• Work should be controlled. Every job that touches equipment should have a defined scope, required skills, parts, tools, isolation requirements, and a record of what was done. Uncontrolled work is a common source of repeat failures, because the same fault returns and no one has a record of the previous fix.
• Decisions should rest on data, but data is only useful when it is trusted. A failure code that is chosen at random, or a runtime meter that is not calibrated, will lead to wrong conclusions. Reliability work therefore includes data quality as a core responsibility, not an afterthought.

03Planning and preparation

• Start by establishing the asset hierarchy. List the site, areas, systems, functional locations, and individual equipment, with a unique identifier for each. Attach criticality ratings based on consequence of failure. A common approach scores safety, environmental, production, quality, and repair cost consequences on a simple scale and takes the highest result. The scale matters less than consistency, so agree on definitions before anyone rates equipment.
• Next, collect the equipment information you need: nameplate data, drawings, manufacturer manuals, lubrication schedules, spare parts lists, and the history of work orders and failures. Much of this will be incomplete. Accept that, record the gaps, and set a plan to close the important ones. Do not delay the whole program while waiting for perfect records.
• Select the analysis method for the assets that justify it. Failure modes and effects analysis is a widely used structured method. Reliability centered maintenance, described in the SAE JA1011 evaluation criteria, is a more formal process for deciding maintenance tasks for each function and failure mode. A full reliability centered maintenance study is expensive, so reserve it for critical systems and use simpler checklists or root cause reviews elsewhere.
• Prepare the planning environment. Define the work order types, priority levels, planning standards, and the rules for when a job is ready to schedule. A job is ready when the scope is clear, the parts are available or ordered, the permits and isolations are identified, and the required skills are known. Starting work without these items is a frequent cause of delay and unsafe improvisation.

04Recommended workflow

1. 1
   : Confirm the asset register and criticality ratings for the area. Check that the equipment identifiers match the physical plant and that the critical items have current maintenance strategies recorded against them.
2. 2
   : Review the backlog and open defects. Group items by equipment, failure mode, and risk. Remove duplicates, and flag any defect that presents an immediate safety or environmental concern for same day action under the site hazard process.
3. 3
   : Plan each job with a scope, a task list, estimated labor hours by skill, required parts and tools, isolation and lockout points, and any permit needs. Attach the drawing or procedure reference. Where a job is complex, write a short sequence that a technician can follow without guesswork.
4. 4
   : Reserve parts and confirm their location. For critical spares, check condition and shelf life where that applies, such as seals, elastomers, batteries, and certain electronic modules.
5. 5
   : Schedule the job with operations. Agree on the equipment window and the hold points where production must confirm isolation. A schedule that ignores the operating side will be overridden at the last minute, and the work will be done badly or not at all.
6. 6
   : Execute the job according to the plan and the site safety rules. Record actual labor, parts used, findings, and any deviation from the plan at the time of work, not from memory at the end of the shift.
7. 7
   : Verify the work before release. This includes a functional check, a leak or alignment check where relevant, and confirmation that guards, covers, and instrument settings are restored. Return the equipment to operations only after the authorized person signs the release.
8. 8
   : Close the work order with a coded failure cause, the corrective action taken, and any follow up needed. Close only when the record is complete enough that another planner could understand what happened without asking the technician.
9. 9
   : Review repeat failures and trends weekly or at the frequency the site sets. Decide whether a fix needs a root cause analysis, a design change, a revised task, or a change to the monitoring plan.

05Quality checks, risk controls and compliance

• Quality in maintenance means the work meets the specification, the equipment performs its function after the work, and the record is accurate. Build checks into the job rather than adding a separate inspection later. A simple example is a torque check recorded on a bolted joint with a second person confirming the value, or a vibration reading taken after a bearing replacement and compared with the baseline.
• Risk controls for maintenance work include lockout and tagout, confined space entry, hot work permits, working at height, energized electrical work, and handling of hazardous chemicals. Confirm the current requirements with your safety function and the authoritative source for your location.
• Where the work involves pressure systems, rotating equipment with high stored energy, or regulated emissions, check the applicable site permits and environmental conditions. Records of inspection and certification may be legally required for some equipment, and those records must be kept in the form the regulator expects.
• This guidance does not replace qualified professional judgment, approved site procedures, or required authorization. Electrical, structural, pressure, and process safety decisions in particular must be made by people who hold the appropriate qualifications and authority at your facility.
• Asset management frameworks such as ISO 55000 provide a structure for linking maintenance decisions to organizational objectives and risk. They do not prescribe specific tasks, so use them to organize governance and review, not as a substitute for engineering judgment.

06Collaboration and documentation

• Maintenance and reliability work depends on several groups working to the same schedule. Operations decides when equipment can be taken out of service. Maintenance planners and technicians carry out the work. Reliability engineers analyze failures and recommend changes. Stores manages parts. Safety approves isolations and permits. Engineering handles design changes and modifications. Each group should know its decision rights, and the handoffs between them should be written down.
• Documentation has three main purposes: it lets the next person act correctly, it provides evidence for audits and investigations, and it builds the knowledge base for analysis. Keep the number of required fields modest, but make sure the required fields carry real information. A failure code is more useful than a free text note alone, and a note that says fixed is worse than nothing.
• Use a consistent failure coding structure. Many sites separate the failure mode, the cause, and the detection method. Keep the list short enough that technicians will use it. Review the list periodically, and merge codes that nobody distinguishes in practice.
• Store drawings, procedures, and manuals in a controlled location with version numbers. Old procedures left in the shop are a common source of error, especially after equipment modifications.

07Measures and continuous improvement

• Track a small set of indicators that reflect the purpose of the program. Common measures include planned maintenance percentage, schedule compliance, backlog age, mean time between failures for specific equipment, mean time to repair, overtime share, and the proportion of corrective work arising from repeat failures. Each measure has limits. Mean time between failures, for example, depends heavily on how failures are defined and counted, and can look good while a serious degradation hides in a less visible failure mode.
• Set targets with the operations team and review them against actual conditions. A target copied from another plant may be unreachable or may not reflect your equipment age, operating load, or spare parts situation. Treat published benchmarks with caution unless you know the definitions behind them.
• Improvement work usually follows a plan, do, check, act cycle. Pick one problem with a clear measure, make a change, check the result over a meaningful period, and either keep the change or revise it. Avoid launching many initiatives at once, since each needs attention to succeed.
• Condition monitoring programs need the same discipline. Set alarm levels based on baseline data and known equipment behavior, review false alarms, and retire measurements that no one acts on. A vibration route that produces data nobody reviews is a cost without a benefit.

08Common mistakes and how to prevent them

• One common mistake is treating the preventive maintenance schedule as a fixed truth. Tasks are often added after every incident and seldom removed, which fills the schedule with low value work and crowds out the tasks that matter. Review each task against the failure modes it addresses, and retire tasks that do not prevent anything measurable.
• A second mistake is closing work orders with vague records. When a bearing fails for the third time, the record should show what was found, what was replaced, and what conditions existed. Without that, the repeat failure looks like bad luck. Require a minimum set of fields and spot check them.
• A third mistake is poor spare parts control. Critical spares that are not on the shelf turn a short repair into a long outage. The opposite error, stocking everything, ties up cash and creates obsolescence. Base stocking decisions on criticality, lead time, and the probability and consequence of failure.
• A fourth mistake is skipping the verification step after work. Technicians under pressure may leave a guard off, a valve in the wrong position, or a calibration unchecked. Make the release step real, with a named person who signs it.
• A fifth mistake is analyzing only the failures that are easy to see. Hidden failures, such as a standby pump or a safety valve that has been degraded for a long time, can be more dangerous than frequent visible faults. Test protective devices on a defined interval and record the results.

09Practical checklist

• Confirm each critical asset has a recorded functional description, criticality rating, and current maintenance strategy.
• Check that work orders contain scope, skills, parts, isolations, and permit references before scheduling.
• Verify that lockout and tagout steps are documented and that the authorized person is named for each isolation.
• Record actual labor, parts, findings, and deviations during the job rather than afterward.
• Require a functional check and signed release before equipment returns to operation.
• Code every corrective work order with failure mode and cause using the approved list.
• Review repeat failures and open root cause actions at a fixed meeting frequency.
• Test standby and protective devices on a defined interval and record results.
• Review the maintenance task list against failure modes at least once per planning cycle.
• Confirm that drawings and procedures referenced in work orders are the current controlled versions.

★Learning sources

• Micro Degree: Industrial Maintenance and Reliability Engineering
• Micro Degree: Solar Power Systems
• Micro Degree: Energy Management and Audit
• Micro Degree: Industry 4.0 Technologies