If you take a unit down on a schedule, this applies.
Turnarounds, shutdowns, and outages go by different names in different industries. The way they fail is the same.
One discipline, several names
A refinery calls it a turnaround. A chemical plant calls it a shutdown. A generating station calls it an outage. The vocabulary changes; the work doesn't. A unit comes offline on a planned date, an enormous amount of scope is executed in a compressed window by a workforce that mostly doesn't work there, and everything depends on the plan being real and the materials being ready.
What every sector has in common
Scope is discovered during execution, not before it. Contractor headcount multiplies overnight and then leaves. Material lead times are measured in months while decisions are measured in hours. And the financial system reports on a calendar that has nothing to do with the event.
Those four conditions are why general project and cost-management tools struggle here. They assume a fixed scope, a long runway, and a monthly reporting cycle. A turnaround has none of those.
What changes by sector
What differs is where the pressure lands. In refining it is the coupling between long-lead material and the critical path. In chemical it is carryover, because the next event is planned before the last one closes out. In power it is a fixed window with revenue accruing by the hour against long-lead components.
EZTRAK is built around the control points those events share, and configured around the ones they don't.
Where the pressure lands differently.
Refining
Unit-based scope, high contractor density, and the tightest coupling between material readiness and the critical path of any sector we work in.
Refinery turnaround management →Chemical & Petrochemical
Shorter, more frequent events with overlapping planning cycles, where what carries between shutdowns matters more than what happens inside any one of them.
Chemical plant shutdowns →Power Generation
Fixed outage windows with generation revenue accruing by the hour, dominated by long-lead components and documentation produced as work happens.
Power plant outages →The platform applies wherever these conditions hold.
Discovered, not defined
Inspection findings add scope after the unit is open, so the plan has to absorb change without losing the audit trail.
Mostly not yours
A contractor-heavy workforce mobilises, executes, and demobilises — and the record of how the event ran leaves with them unless you own it.
Fixed, and expensive
When the return-to-service date is set by something other than the work, every hour of recovered float has a number attached to it.
Send us your next event.
If your events share those conditions, the platform applies. Send the dates and rough scope size and we'll tell you honestly whether we're a fit.
See what your next turnaround could save.
Answer six questions in under two minutes and receive a conservative savings estimate based on results from live events. Find out where better visibility, control, and execution could make the greatest impact.