Refinery turnaround with AI — scope creep is not bad luck, it is information that reaches the office late.
A refinery turnaround can move €50-100M, and one day gained on the return to production is worth thousands of barrels. iLEAN plans with field information at second zero, executes with a shared dashboard for every contractor and keeps scope creep in check by putting the consequence in front of the person who decides. The signature is still human — always.
The TA does not overrun in the plan — it overruns in what the plan does not know.
Anyone who has run a turnaround knows the curve by heart: it starts with a frozen scope and a schedule defended in committee, and ends with a swollen scope, a stretched schedule and the legitimate suspicion that “if I had known this earlier, we would have headed it off”. The question is why that happens almost every time, in serious plants, with professional teams:
- The inspection finding that opens a new job sits first in the inspector's notebook, then in the site manager's inbox and, finally, in a change proposal that reaches the turnaround committee two days later — when there is no longer any room to say no.
- The supplier flags over WhatsApp that the spare part will arrive a day late. The forwarding chain passes through three people and reaches the planner after they have already reshuffled other tasks assuming the part was there.
- The work-at-height permit that was not signed in time blocks a crew for half a shift — and the crew next to them cannot enter the same niche either. Information that existed; nobody was cross-referencing it.
- Contractor C uses its own Primavera, contractor D a simplified MS Project, and contractor E sends you a spreadsheet every night. The master plan lives in SAP TR, and real progress is reconciled by hand at the 8 a.m. meeting.
The classic system (site manager + daily meeting + parallel spreadsheets) works, but at the price that the TA only comes into focus the day after. And a one-day delay in the return to production is not a spreadsheet column: it is thousands of barrels off the market.
iLEAN is not yet another turnaround system — it is the putty between SAP TR, the contractor and the field.
SAP TR (or Primavera, or MS Project) does its job well: it plans. That is not the problem. The problem is that the plant changes faster than the planner can record by hand, and what changes in the field (findings, delays, permits, scope changes) travels through human channels before reaching whoever governs the plan. iLEAN acts as the putty between those channels and the plan: it captures what is said by email, WhatsApp or phone call, cross-references it with SAP TR and returns the critical-path consequence before the meeting, not after it.
Connect captures what arrives through every human channel. Brain recalculates the impact on critical path and budget. Writer prepares the change request and the dossier for the committee. The person decides and signs — always with the consequence in front of them.
The three iLEAN pieces applied to managing a turnaround:
- iLEAN Agent — a swarm of agents living on the Central platform that orchestrate the TA 24/7: follow-up agents per contractor, an inspection-findings agent, a spare-parts logistics agent, a work-permit agent. Each one cross-references its patch against the master plan and leaves the consequence ready for the person who decides. Agents do not sign scope changes — they propose, the person decides.
- iLEAN Writer — turns the daily chaos into clean deliverables: a TA daily report with real progress, a formal change request with quantified schedule and budget impact, an evidence dossier per contractor for the final settlement, a file for the auditor. The manager reviews and signs; they do not rewrite.
- iLEAN Brain — cross-references SAP TR / Primavera / MS Project with the real progress captured in the plant, recalculates the critical path on the spot, anticipates bottlenecks and offers “what happens if I take on this new scope” simulations with the consequence in days and in euros before the committee has to decide.
Classic turnaround management vs. a turnaround coordinated with iLEAN
| Aspect | Classic TA (SAP TR + spreadsheets + the 8 a.m. meeting) | With iLEAN Agent + Writer + Brain |
|---|---|---|
| Inspection finding | Reaches the committee two days later, with no quantified impact | Reaches the decision maker with critical-path and € impact ready |
| Multiple contractors | Each with their own system, manual reconciliation | Shared dashboard, formats homogenized at second zero |
| Real progress vs. plan | Daily reconciliation in a meeting | Continuous, with automatic deviation flags |
| Change requests | Email, conversation, hallway pressure | Formal, with an impact dossier and a traced signature |
| Spares and external logistics | Supplier WhatsApp → manual forwarding | Captured at second zero, replanning proposed |
| Closeout and settlement | Rebuilding evidence per contractor, weeks | Dossier per contractor ready on the last day of the TA |
Impact estimate for your plant — to be validated with your numbers.
The block below is an estimate to be validated with the data of your next TA and your scope-creep history. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.
- Refinery or petrochemical complex with a major TA scheduled within the next 12-24 months, dozens of contractors, a critical path several weeks long, SAP TR or Primavera P6 as the master system.
- iLEAN deployment ahead of the TA: agents per contractor, integration with SAP TR/Primavera, Connect capture of human channels (email, business WhatsApp, transcribed calls). First value expected within a few weeks of preparation, even before the TA starts.
- Expected scope-creep reduction ≥ 30% (to be validated against your history). The hard lever is not saving person-hours: it is every day of delay avoided on the return to production, worth thousands of barrels a day.
- Indicative payback within the TA itself if the plant is large; on a small TA, cumulative payback between 4 and 9 months counting the next cycle.
And the TA director's reasonable doubt
“What if the AI gets the critical-path impact wrong and authorizes a change we should not have taken on?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely recontextualizes a piece of data from one system to another (reading an inspection, cross-referencing it with SAP TR, calculating the impact in days and in €), the best models brought error below 1.5% [1]. And even so, the scope does not move on its own: iLEAN proposes the change request with the dossier, the person decides and signs. The three safety rings exist precisely for this.
[1] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.
What people ask about turnarounds with AI
How do you reduce scope creep in a turnaround?
Turnaround scope creep is not contractor indiscipline — it is information that arrives late. The inspection of an exchanger uncovers a problem that “we might as well fix while we're in there”, nobody quantifies the critical-path impact, the planner is never notified, and at closeout the TA carried 80 new work orders nobody had authorized with a cool head. iLEAN intercepts that chain: when an inspection crew opens a finding, the agent cross-references it with the original scope dossier, calculates the impact on the critical path and the budget, prepares the change request with the evidence and puts it in front of the decision maker. The person decides whether to take it on or not — but decides with the consequence in front of them, not blind.
What about the critical path?
The critical path lives in Primavera P6, in MS Project or in SAP TR, but the data that moves it lives somewhere else: in the inspection performed yesterday, in the spare-parts truck the supplier flagged over WhatsApp as arriving a day late, in the work-at-height permit that has not been signed yet. iLEAN Connect captures that data through whatever channel it arrives on (email, WhatsApp, transcribed call, a photo of the inspection report) at second zero, and an agent recalculates the critical-path impact before the 8 a.m. meeting finds out the long way around.
Does it integrate with SAP TR?
Yes. iLEAN Connect connects to SAP TR (Turnaround Management), Primavera P6 and MS Project through the standard routes — API, BAPI/RFC or, if the customer prefers, a scheduled export of the schedule. The agent does not replace the TA ERP: it reads from it, feeds back the real progress captured in the plant and, when there is a change request, prepares the data so the planner can register it. The iLEAN piece is the layer that closes the gap between what was scheduled and what is happening in the field, not a parallel system.
Does it work with multiple contractors?
Yes, and that is where it pays off most. A large TA brings together dozens of contractors with their own planners, different systems and different formats. iLEAN Connect homogenizes those formats at second zero — each crew's daily report, the supplier's delivery note, the welding subcontractor's inspection — and the agent cross-references them against the master plan. The refinery operator stops chasing spreadsheets and starts reading a single dashboard with everyone's information. And at closeout, every contractor has an evidence dossier prepared by iLEAN Writer for the final settlement.
Typical savings in a turnaround?
A refinery turnaround can move €50-100M across civil works, mechanical, instrumentation, electrical and lost production — even a small percentage of that figure is already a huge return. The hard lever is not just the savings in hours: it is every day gained on the return to production, worth thousands of barrels. We send you an estimate within 48h based on the data of your next TA — planned scope, number of contractors, critical milestones — and the ROI comes from that cross-check, not from a generic case.
Tell us about your next turnaround and within 48h we'll send you the estimated ROI of the iLEAN deployment for that TA.
We work on the real data of your TA, your contractors and your history, not ours. Diagnostic with no commitment.
Request estimated ROI in 48h See petrochemical