Shutdowns, Turnarounds & Outages

Source and Scope Boundary#

This page is the public derivative of `RM-MKS-10009 — Shutdown & Turnaround Management`, v0.3, Approved Internal. It owns the management and governance layer that spans a whole major planned event: who is accountable, which gates exist, how readiness is decided, and how contractors, cost, and lessons learned are governed. The specialist disciplines it sits above — scope development and freeze, utility/continuous-process continuity, and critical-path scheduling — are covered in their own Reliability Method topics (Shutdown and Turnaround Planning, Outage Planning, Turnaround Scheduling). This page is a management reference, not legal, contractual, insurance, or engineering-sign-off guidance.

Plain-English Definition#

A shutdown, turnaround, or outage (STO) is any event where an asset, unit, line, or system is deliberately taken out of normal service for a bounded period to do work that cannot be done while it is running.

STO management is the governance layer that makes that event run as one accountable program instead of three loosely coordinated disciplines — planning, continuity, and scheduling — each running its own way. It answers three questions the individual disciplines cannot answer alone:

• Who decides when planning, continuity, and scheduling priorities conflict?
• Who is accountable when the event as a whole slips, overruns, or has a safety gap?
• How does the organization learn so next year's event is planned better?

Why It Matters#

STO programs rarely fail because a planner, scheduler, or continuity specialist did their own job badly. They fail at the seam between disciplines: no one owns the decision rights that span them. A scope exception changes cost and schedule at once, and no single authority resolves it. Planning says "ready," scheduling says "ready," continuity has one open item — and the event starts anyway. The post-event debrief is filed and never changes anything.

STO management exists to close those gaps: one accountable authority, owned gates, a single escalation path, and lessons learned that are a governed deliverable rather than an optional meeting.

What It Is#

• A named steering committee and event manager for the whole event
• A phase-gate lifecycle where every gate has a clear owner
• A consolidated Execution Readiness Review — one go/no-go, not three
• Program-level contractor, cost, and change governance
• A governed lessons-learned loop that feeds the next event's planning

What It Is Not#

• A planning, continuity, or scheduling *method* — those are separate disciplines
• A guarantee of any specific cost, duration, or safety outcome
• An authority that can override a safety or continuity hold on cost or schedule grounds
• A one-time debrief filed and forgotten

The Four Layers of an STO#

This page governs the authority structure the other three operate inside; it does not restate their technique.

Governance Structure#

A major event is run through a three-tier structure.

Event Lifecycle and Phase Gates#

Gates 1, 4, and 7 are owned by the management layer. Gates 2, 3, 5, and 6 are owned by the specialist disciplines; management recognizes them rather than re-running them.

The Execution Readiness Review#

The single most important control in STO management is the Execution Readiness Review: one consolidated go/no-go before execution is authorized.

• It draws evidence from all three disciplines — planning readiness, continuity go/no-go (where applicable), and mobilization/baseline-schedule readiness.
• A program "green" requires all three inputs evidenced, not assumed. One discipline's "ready" does not cover for another's open gap.
• The decision is recorded as go, conditional go, or hold/no-go, with the evidence basis and decision-maker.

Decision rule: if scheduling reports ready but one continuity or planning item is open, the correct status is conditional go or hold on that item — not a full go on schedule readiness alone.

Roles and Escalation#

Escalation runs one known path: work front → discipline lead → event manager → steering committee. The safety lead's escalation is never gated by a cost or schedule tier — a safety issue rises immediately, and where a governance rule and a safety hold appear to conflict, the safety hold governs.

Contractor and Cost Governance#

Contractors and cost are governed as one program, not per-contract:

• One contractor framework — safety qualification, insurance/certificate verification, and performance expectations applied consistently across every contract and work front.
• Centralized onboarding and access — every contractor employee completes the defined safety orientation before a badge or site access is issued; access is tracked centrally and revoked on incident or contract end. Badge issuance is blocked until orientation is recorded, regardless of schedule pressure.
• Budget structure — the event budget is split into cost categories (labor, materials, contractor services, equipment/rental, contingency), each with a named owner.
• Cost tracked on the schedule cadence — cost variance is reviewed on the same cadence as the schedule (commonly daily during execution) so cost and schedule drift are visible together, not reconciled only at close-out.
• Tiered variance authority — variance is approved through named tiers (lead → event manager → steering committee); a change touching scope, cost, and schedule at once is resolved at the higher of the applicable authorities. Exact thresholds are set locally; no universal figure is asserted.

Safety and Regulatory Considerations#

Program governance adds clarity and speed to decisions; it never overrides safety authority. The safety lead's authority to hold or stop work is independent of cost tier, schedule pressure, or committee composition. No escalation structure, cost policy, or contractor framework may delay, dilute, or bypass a safety hold.

Regulatory applicability depends on jurisdiction, industry, asset type, and contract. For utility or continuous-process outages, regulatory notification content and lead times are a continuity-discipline and qualified-compliance responsibility; the steering committee and event manager are the organizational recipients of that evidence, not its authors. Program cost, contractor, and escalation records may themselves be subject to audit or contractual reporting. This page is not legal advice.

Metrics and KPIs#

Program-governance measures, distinct from the planning, continuity, and scheduling KPIs owned by those disciplines. Not universal targets.

Common Failure Modes#

Best Practices#

• Charter the steering committee and event manager before detailed planning is well underway.
• Build the gate-ownership map into the charter so every discipline knows which gates it owns and which it feeds.
• Make the Execution Readiness Review show all three disciplines' evidence — never a single blended status.
• Centralize contractor onboarding, orientation, and access under one lead regardless of contract count.
• Track cost on the same cadence as schedule so variance is visible before close-out.
• Log escalations with tier and decision; watch escalation cycle time as a health signal.
• Require every post-event finding to produce a named, owned, dated action, and track closure.

Maturity Model#

Practical Example#

A refinery steering committee — chaired by the plant manager, with operations, maintenance/reliability, engineering, safety, and finance — charters an 18-month turnaround program and appoints a turnaround manager and core team. Mid-planning, an inspection finding is accepted as an integrity-critical exception that adds cost beyond the planning lead's tier. Because a change touching both cost and schedule is resolved at the higher authority, the event manager escalates the combined impact to the steering committee rather than approving it alone.

At the Execution Readiness Review, scheduling reports the baseline and mobilization ready, but continuity has one redundancy-verification item still open. The event manager holds the gate at conditional go pending that single item rather than letting schedule readiness override it. At the post-event review, a recurring pattern — deferred inspection work handled through informal risk-acceptance conversations rather than logged exceptions — is assigned as a named action to tighten the challenge criteria for next cycle. No specific outcome is claimed.

Audit Questions#

• Is a steering committee and event manager named for the event?
• Does a documented gate-ownership map exist?
• Was the Execution Readiness Review evidenced by all three disciplines, not one alone?
• Are escalations logged with tier, decision, and date?
• Are cost variances tracked and escalated at the correct authority tier?
• Is contractor safety-orientation completion recorded before access is issued?
• Did the post-event review produce named actions with owners and due dates?
• Did lessons learned demonstrably change the next cycle's planning criteria?

Related Reliability Method Topics#

• Shutdown and Turnaround Planning (scope, challenge, freeze, readiness)
• Outage Planning (utility/continuous-process continuity and restoration)
• Turnaround Scheduling (critical path, float, resource leveling, recovery)
• Maintenance Planning and Maintenance Scheduling
• Work Execution Excellence
• Capital Investment Planning and Asset Criticality Analysis

References#

References trace to the authoritative MKS and its cited context; no licensed standard text is reproduced and no numeric cost, duration, or crew-size benchmarks are asserted.

• RM-MKS-10009 — Shutdown & Turnaround Management
• ISO 55000 — Asset Management
• SMRP Body of Knowledge (verify current edition and licensed access)

Revision History#