Key takeaways
Short answer: A shutdown and a turnaround both mean stopping equipment to do maintenance that cannot be done while running, but they differ enormously in scope and scale. A shutdown is any planned stop — of a single machine, a line, or a unit — to perform maintenance; it may be short and relatively frequent. A turnaround (also called a TAR or, in utilities, an outage) is a large, infrequent, whole-unit or whole-plant shutdown for major overhaul, statutory inspection, and capital work — heavily project-managed, lasting weeks, and recurring only every few years. Every turnaround is a shutdown, but a turnaround is a shutdown at the largest, most complex scale.
Shutdown maintenance is maintenance performed while equipment is deliberately stopped, because the work cannot be done safely or effectively while it is running. The scope is usually contained: a single machine, a line, or a process unit is brought down for a defined set of tasks — replacing a pump, cleaning a heat exchanger, changing a worn component, performing an internal inspection — and then restarted. Shutdowns are planned and scheduled (distinct from an unplanned breakdown), and they tend to be relatively short — hours to a few days — and relatively frequent, fitting into the normal maintenance calendar. The defining feature is simply that the equipment must be off for the work: you cannot replace bearings or open a vessel while it is in service. A shutdown is the everyday tool for doing the maintenance that running operation makes impossible, on a scale small enough to schedule into routine production planning without it becoming a major event.
A turnaround (TAR, sometimes "shutdown" used loosely in some plants, or an "outage" in power and utilities) is a planned, periodic event in which an entire unit or whole plant is taken offline for major maintenance, inspection, and capital work that can only be done when everything is down. Turnarounds are large in every dimension: scope (hundreds or thousands of individual jobs), duration (often weeks), workforce (a large surge of contractors on top of the regular team), and budget (frequently the single largest maintenance expenditure in a plant's year). They bundle together statutory and insurance inspections of pressure vessels and piping, catalyst and internals replacement, major equipment overhauls, and tie-ins for capital projects — work that genuinely requires the whole unit cold and depressurized. Because of their size and the production lost while down, turnarounds are infrequent, recurring only every two to six years depending on the process and regulatory cycle, and they are run as formal projects with dedicated planning teams.
The relationship between the two is one of scale: every turnaround is a shutdown — the plant is stopped to do maintenance — but a turnaround is a shutdown at the largest, most complex end of the spectrum. A routine shutdown is narrow and short; a turnaround is plant-wide and long. The jump is not just "bigger," it is a change in kind: a shutdown is a maintenance task, while a turnaround is a major project with its own planning organization, work-package management, contractor mobilization, and critical-path schedule. This is why the terms are kept distinct even though both involve stopping equipment. Calling a turnaround "a shutdown" understates the planning, risk, and coordination it demands; calling a routine shutdown "a turnaround" overstates a piece of ordinary scheduled work. The useful mental model is a continuum of planned stops, with everyday shutdowns at one end and the multi-year, whole-plant turnaround at the other.
The scale difference drives a planning-horizon difference. A routine shutdown is planned in the normal maintenance window — work orders raised, parts staged, a slot found in the production schedule weeks ahead. A turnaround is planned one to two years in advance by a dedicated turnaround team: the work list (scope) is frozen well ahead to control creep, long-lead materials and major components are ordered months out, contractor crews are contracted, and the entire event is built into a critical-path project schedule with daily progress tracking during execution. Scope control is the central discipline — every late addition to a turnaround's work list ripples through the schedule and cost, so mature organizations lock scope early and challenge additions hard. The contrast is stark: a shutdown is scheduled maintenance, a turnaround is a capital-scale project that happens to be about maintenance. Treating a turnaround with shutdown-level planning is a classic and expensive failure mode.
Consider a single process unit in a continuous plant. Through the year it takes several short shutdowns: a two-day stop to swap a failing pump and clean two exchangers, another one-day stop to replace a control valve and inspect a small vessel. Each is scheduled a few weeks ahead, uses the in-house crew, and costs relatively little in both work and lost production. Then, once every four years, the unit takes a turnaround: a three-week, around-the-clock event involving several hundred discrete jobs — full internal inspection of every pressure vessel for the statutory cycle, catalyst replacement, overhaul of the main compressor, retubing an exchanger, and tying in a small capital upgrade — executed by the regular team plus a large contractor surge, planned over the preceding eighteen months, and representing the unit's biggest single maintenance cost. Same unit, same basic idea of "stop and do the work," but the turnaround is an order of magnitude larger in scope, duration, workforce, cost, and planning lead time. That gap is exactly the distinction the two words carry.
The two are complementary, not alternatives — a plant uses both, and the choice is about what the work requires. Use a routine shutdown for contained, schedulable work on a machine, line, or unit that does not need the whole plant cold: component replacements, cleanings, smaller inspections, and anything that fits in a short window. Reserve the turnaround for work that genuinely requires the entire unit or plant offline and depressurized, that is tied to statutory inspection cycles, or that is too large and interconnected to do piecemeal — and batch as much of that work as possible into the same event, because the production loss of taking the plant down is so high that you want to do everything at once. Continuous-process industries (refining, chemicals, power) live by this rhythm of frequent small shutdowns punctuated by periodic turnarounds; discrete manufacturers use the same logic with planned line shutdowns and occasional major overhauls. The art is putting each job in the right bucket so routine work is not deferred to a turnaround and turnaround-only work is not attempted in a short shutdown.
Shutdowns and turnarounds are both planned events, so how they hit OEE depends on how planned downtime is defined. Time the plant is intentionally down for a scheduled shutdown or turnaround is usually excluded from planned production time, so it does not count against the Availability factor — much like the distinction in planned vs unplanned downtime. What does affect OEE is execution: a shutdown or turnaround that overruns eats into planned production time and delays the return to output, and a botched restart produces a slow, defect-prone ramp that drags Quality and Performance for days. Conversely, the whole point of this maintenance is to restore equipment to a condition that runs reliably — preventing the unplanned breakdowns that would otherwise destroy Availability. Good shutdown and turnaround execution is therefore an investment in future OEE, and tying these events to a condition-based or time-based strategy ensures you stop for the right work at the right time.
Fabrico links maintenance events to the OEE that follows them, so you can see whether a shutdown or turnaround actually delivered the reliability it was meant to. By tracking downtime causes and post-event performance against live OEE, it shows whether breakdowns dropped after the work — and whether the restart ramp went cleanly or dragged. That feedback turns turnaround spend into something measurable: did equipment run better afterward, or did the same losses return? Book a demo to connect your maintenance events to real production results.
A shutdown is any planned stop of equipment or a unit to do maintenance that cannot be done while running. A turnaround is a large, infrequent, whole-unit or whole-plant shutdown for major overhaul and statutory inspection. Every turnaround is a shutdown, but at the largest, most project-managed scale.
Turnarounds are infrequent, typically recurring every two to six years depending on the process and regulatory inspection cycle. Routine shutdowns happen much more often — fitted into the normal maintenance schedule throughout the year.
Because of their scale: hundreds or thousands of jobs, weeks of duration, a large contractor surge, and major budgets. Long-lead materials, contracts, and a critical-path schedule must be arranged one to two years ahead, with scope frozen early to control cost and schedule.
Effectively yes — "outage" is the term used in power and utility industries for the same concept: a large, planned, periodic shutdown for major maintenance and inspection. "Turnaround" (or TAR) is the more common term in refining and chemicals.
Usually they are treated as planned downtime and excluded from planned production time, so they do not reduce the Availability factor directly. What hurts OEE is overruns that eat into production time or a poor restart that drags Performance and Quality during the ramp-up.
Anmeldung
Blog
