A major turbine overhaul brings a dozen or more contractor crews onto site inside a single outage window, each one running its own schedule, its own tooling, and its own reporting line back to an OEM technical advisor who isn't always reachable outside business hours. The overhaul work itself is rarely the hard part; qualified crews know how to pull a rotor, inspect a diaphragm, and reassemble a casing. What actually breaks a schedule is the coordination layer sitting on top of that work: which crew has claim to the laydown area this shift, whose lift plan needs the crane next, and whether the OEM's inspection sign-off arrived before the next crew tried to close the casing back up. A short session with our team can walk through what a coordinated mobilization schedule looks like against your own outage scope.
Outage Planning · Contractor Mobilization
Turbine Overhaul Contractor Mobilization and Coordination Across a Compressed Outage Window
A single-view schedule that lines up OEM technical directives, tooling and rigging logistics, laydown area assignments, and quality sign-offs across every contractor crew working the overhaul at once, so a scope change on one crew's track doesn't quietly stall three others.
Pre-Mobilization
T-6 Weeks
Scope lock, OEM scope review, contractor sequencing
Mobilization
T-3 Days
Crews on site, tooling staged, laydown assigned
Peak Execution
Day 1 - Day N
Overlapping crews, shared crane and inspection queue
Demobilization
Final 2 Days
Closeout inspection, punch list, site release
12+
contractor crews on a typical HP/IP turbine overhaul
1
shared schedule needed across every OEM and contractor track
Hours
not shifts, is how fast a laydown conflict should surface
The Coordination Gap
Why Contractor Coordination Breaks Down Faster Than the Overhaul Schedule Itself
Most turbine overhaul schedules are built around the mechanical sequence: open the casing, pull the rotor, inspect the diaphragms, replace the blades that failed dimensional check, reassemble, align, and close. That sequence is well understood and rarely the source of a blown outage window. The actual risk sits in the seams between contractors. A rigging crew staged to pull the rotor needs the crane at the same hour an NDE crew scheduled a lift to access a casing weld. A bearing inspection contractor is waiting on an OEM technical directive that hasn't been issued yet, while the reassembly crew behind them assumes the directive already cleared. A laydown area sized for one crew's tooling ends up hosting three crews' pallets by day four, and nobody notices until someone can't find a torque wrench that's buried under someone else's crate. None of these are mechanical failures. They are coordination failures, and they compound daily across an outage that may only run ten to twenty-one days end to end, which means a single day lost to a laydown dispute or a missed sign-off is a real percentage of the entire window.
Where Schedules Actually Slip
Four Coordination Failures That Quietly Extend an Overhaul Outage
OEM Directive Lag
A technical directive on a borderline inspection finding sits with the OEM's remote engineering desk while the crew behind that finding waits idle, with no visibility into how close the directive is to being issued.
Tooling and Rigging Conflicts
Specialty tooling and the site's single overhead crane get double-booked across contractor tracks because each crew schedules against its own plan rather than a shared equipment calendar.
Laydown Area Overlap
Parts, tooling, and temporary structures from multiple crews compete for the same staging footprint, and a part staged out of sequence becomes a search-and-locate problem during a critical path task.
Quality Sign-Off Bottleneck
A reassembly crew is ready to close a casing section before the quality inspector has confirmed the prior finding was actually cleared, creating rework risk if the sign-off arrives after the section is already sealed.
What Actually Needs Coordinating
The Four Coordination Layers Sitting Underneath Every Overhaul Schedule
Every turbine overhaul, regardless of OEM or unit size, runs on the same four coordination layers. Treating them as one undifferentiated "schedule" is exactly what causes them to collide with each other during peak execution.
| Coordination Layer | What It Covers | Typical Failure Mode |
|---|---|---|
| OEM Technical Directives | Inspection findings routed to the OEM for disposition, and the directive that authorizes rework, replacement, or continued service | Directive queued behind other units in the OEM's engineering backlog with no visible status |
| Tooling and Rigging Logistics | Specialty tooling, lift plans, and crane time shared across every contractor crew working the unit | Two crews build lift plans against the same crane window without knowing it |
| Laydown Area Allocation | Physical staging footprint for parts, tooling, and temporary structures by crew and by shift | Footprint sized at planning time doesn't reflect what actually arrives on trucks |
| Quality Control Sign-Off | Inspection holds, witness points, and closure sign-offs that gate reassembly steps | A crew closes a section on the assumption a sign-off is coming rather than confirming it arrived |
See Your Overhaul Scope Laid Out as One Coordinated Schedule
Most outage teams have never seen every contractor track, OEM directive, and laydown assignment sitting on a single timeline. A short session shows what that looks like against your own overhaul scope.
How Coordination Should Run
Five Stages From Scope Lock to Site Release
1
Scope Lock and Contractor Sequencing
Final inspection scope is confirmed against the prior outage's findings, and each contractor's work window is sequenced against the others before mobilization begins.
2
Mobilization Day Logistics
Crews arrive against a fixed laydown assignment and a tooling delivery schedule rather than claiming space and equipment on arrival.
3
Peak Execution Shift Handoffs
Crane time, specialty tooling, and open inspection holds are visible to every crew lead at every shift change, not just the crew that scheduled them.
4
OEM Directive Routing
Borderline findings are routed to the OEM with a visible status, so a waiting crew knows whether to hold, reassign, or proceed on an alternate task.
5
Demobilization and Closeout
Punch list items, outstanding sign-offs, and final quality documentation are closed against a single record before the unit is released back to operations.
Ad Hoc vs Spreadsheet vs Connected Coordination
Three Ways Overhaul Coordination Actually Gets Managed
Most sites run one of three approaches to contractor coordination on a turbine overhaul, and the difference between them shows up most clearly on day six or seven, once the initial plan has already absorbed its first few schedule changes.
Ad Hoc Coordination
Crew leads coordinate directly through radio and morning meetings, which works until two crews need the same crane window on the same shift.
Spreadsheet Tracking
A shared schedule exists but updates lag behind what's actually happening on the floor, so the spreadsheet reflects yesterday's plan rather than today's conflicts.
Connected Coordination Platform
Tooling, laydown, directive status, and sign-offs update in one place as each contractor logs progress, so a conflict surfaces the same shift it happens.
Where Plans Go Wrong
Four Mistakes That Show Up on Nearly Every Overhaul
Sizing Laydown for the Plan, Not the Trucks
Staging footprint is sized against the planned parts list rather than what actually shows up, which is almost always more pallets than planned.
Treating the OEM Desk as a Black Box
Directives are submitted and then simply waited on, with no visibility into queue position or expected turnaround relative to the crew that's idle.
One Crane Calendar, Built Too Late
Crane time is scheduled crew by crew instead of as one shared resource, so the conflict isn't visible until two lift plans collide on the floor.
Closing Sections on Assumed Sign-Off
Reassembly proceeds on the expectation that a quality hold will clear in time, turning a late sign-off into a rework event instead of a scheduling one.
Applied Example
A Crane Conflict That Cost a Full Shift on an HP Rotor Overhaul
On a steam turbine HP rotor overhaul, the rigging contractor scheduled the site's single overhead crane to lift the rotor for bore inspection on day five, second shift. Unknown to that crew, the diaphragm inspection contractor had booked the same crane window for a casing-half lift, working from a separate schedule that had never been reconciled against the rigging plan. Neither crew found out until both showed up to the floor with their lift plans staged. The rotor lift was pushed to the following shift, which delayed the NDE crew waiting on rotor access, which in turn pushed the reassembly crew's start by a full shift. With a shared coordination view, the conflict would have surfaced when both lift plans were entered against the same crane resource, days before either crew mobilized to the floor, giving the outage manager time to resequence one of the two lifts without losing a shift on the critical path.
Getting Started Guidance
What to Confirm Before Coordinating Your Next Overhaul on One Schedule
A short readiness review shows how quickly your existing outage plan can be layered onto a shared coordination schedule.
| Question | Why It Matters |
|---|---|
| How many contractor crews will be on site during peak execution? | Determines how many independent schedules need to be reconciled against shared resources |
| Is crane and specialty tooling time currently tracked in one place? | Shows whether resource conflicts are visible before crews mobilize or only after |
| How are OEM technical directives currently routed and tracked? | Identifies whether idle-crew time from directive delays is currently measured at all |
| Who has authority to resequence a contractor track mid-outage? | Defines the workflow a coordination conflict needs to escalate into |
Common Questions
Turbine Overhaul Contractor Coordination — Frequently Asked
These are the questions outage managers tend to ask first when they're evaluating a shared coordination approach for the first time.
Does this replace the contractor's own project management tools?
No, each contractor typically keeps its own internal planning tools for its crew's task sequence, and a shared coordination layer sits above those rather than replacing them. What it adds is visibility across contractors on the resources and dependencies that no single contractor's tool can see on its own, like shared crane time or an OEM directive another crew is waiting on. Book a demo to see how the two layers work together on an active outage.
How far in advance should coordination planning start?
Most outage teams start locking contractor sequencing and shared resource plans roughly six weeks before mobilization, which gives enough lead time to catch a crane or laydown conflict while it can still be resolved on paper. Starting later tends to mean conflicts surface for the first time once crews are already on site. Contact support to review a mobilization timeline for your outage.
Can this track OEM directive status if the OEM doesn't use our system?
Yes, directive status can be logged and tracked on the outage side even when the OEM's own engineering review happens in a separate system, so the waiting crew still has visibility into submission date, expected turnaround, and current status rather than no information at all. Book a session to see how directive tracking is handled in practice.
Does this help with laydown area planning specifically?
Yes, laydown assignments can be tracked by crew, shift, and footprint alongside the rest of the schedule, which makes it easier to spot an overlap before trucks arrive rather than after pallets are already competing for the same staging area. This is one of the more immediately visible improvements teams notice in their first coordinated outage. Ask our team about laydown planning for your next overhaul.
Is this only useful for large multi-unit overhauls?
No, even a single-unit overhaul with four or five contractor crews benefits from a shared schedule, since the coordination failures described here scale with the number of independent schedules involved rather than with unit count alone. Smaller outages simply have less slack to absorb a coordination miss. Book a call to walk through coordination for an outage of your size.
Put Every Contractor Track on One Coordinated Overhaul Schedule
iFactory brings OEM directives, tooling and crane logistics, laydown assignments, and quality sign-offs into a single view across every contractor working your turbine overhaul, so a conflict surfaces the same shift it happens instead of the shift after.
