Book a demo

Shutdown, turnaround & outage (STO) planning

iPlan4.0 STO Turnaround planning software that keeps scope, work packs, schedule and progress in one dataset.

Instead of SAP exports, P6 files and spreadsheets, iPlanSTO scores every notification before it is planned, builds packs from the actuals of executed jobs, and tracks earned value at job-step level. You see overrun risk while you can still recover it.

Used by

  • BP
  • CF Industries
  • Altrad
  • UPM
  • SOCAR
  • HMEL
  • INEOS
  • Sadara
  • Essar

Used in 27 countries

  • Winner 2024 · Business Awards UK Tech Business
  • Winner 2024 · NEPIC SME Business
  • Finalist 2025 · Lloyds AI Solution

Where turnarounds overrun

It starts in three places.

01Scope

The work list grows after it's frozen

Notifications reach planning unchallenged, and work is planned that gets cut weeks later. The planning hours are spent either way.

iPlanSTOEvery notification is scored on completeness and J-Factor before it is planned. The list freezes on a set date, and late work is costed separately.

02Estimate

The estimate restarts at every stage

Scope sits in SAP, packs in spreadsheets, the schedule in P6. Each stage produces its own number, and none traces back to the one before. On one offshore FPSO, a recently executed pack took about two-thirds of its planned time.

iPlanSTOOne record from notification to close-out, so when the cost moves you can see which stage moved it.

03Progress

You see the shift a shift late

Supervisors hold hours back to cover later slippage, and emergent work arrives by phone and takes the critical-path crews.

iPlanSTOProgress per job step from mobile. Emergent work is logged where it's found, costed and approved through the same gate as planned work.

01Inside planning

Turnarounds fail in planning, not execution

Three more gaps sit inside the planning phase.
Each one has a mechanism in iPlanSTO.

Estimates

Three planners, three estimates

Nothing checks the estimate against what the job took last time.

Estimates seeded from actuals of executed jobs on similar equipment.

Readiness

Packs released before they're ready

The missing isolation or part is found when the crew arrives.

AI Work Pack Review checks every pack. A pack cannot be scheduled until a named planner approves it.

Schedule

The schedule is retyped from the packs

Within a week the schedule and the work orders disagree.

Approved packs become activities with hours and crews on them. Sync with P6 both ways, or schedule in the built-in Gantt.

02Scope challenge

Turnaround scope challenge: every notification scored before it's planned

  • AI Enrichment AgentReads SAP notifications and maintenance orders and scores each against the 8-category Completeness Indicator.
  • Risk assessmentEach item is scored on a 5×5 likelihood × consequence matrix. Likelihood blends condition, history, frequency and exposure. Consequence takes the highest of HSE, business, environment, community and lost production. The score feeds J-Factor.
  • J-FactorWeighs the cost of doing the work against the reduction in business risk. Mandatory safety and regulatory work is always kept.
  • Monte Carlo on three-point estimatesBest, most likely and worst durations give P10, P50, P90 and the contingency you need, before a pack is written.
  • Scope freezeThe list freezes on an agreed date. Later additions go through the late-work route and are costed separately.
  • Decision written back to SAPInclude, defer or reject, with the reason and an audit trail, so a year later you can say why a job was deferred.
As written in SAP

10045872 · P-301B
"Pump tripped, found coupling worn, replace."

  • No failure mode
  • No isolation requirement
  • No estimate basis
As scored in iPlanSTO
5 / 8Completeness Indicator
StatusNeeds information
J-FactorAssessed after completion
DuplicatesNone found
Example notification. The planner sees it needs more information before anyone spends hours writing its work pack.

03How it works

How iPlanSTO works, from scope to close-out

Each phase writes to the same dataset, so the next phase starts from what the last one decided, not from an export.

Welder inside a pipe section with engineering drawings overlaid01 · PLAN

Build packs from executed jobs

  • iPlanAI drafts steps, crews, manhours and materials from a description, drawings or photos
  • Estimates seeded from the Shutdown Intelligence Library
  • Productivity and no-work-time factors (shift patterns, permit waits, congestion) applied when manhours become durations
  • Planner edits, regenerates or rejects every output
Edit, don't rebuild
Engineer walking a pipe rack between flanged valves02 · REVIEW

Check packs before release

  • AI Work Pack Review against actuals from similar executed packs
  • Labour, crew size, duration, cost, materials and risk
  • Findings graded Critical, Advisory or Information
  • No approval, no scheduling: unapproved packs stay out of the schedule
Nothing changed automatically
Aerial view of plant pipework and storage tanks03 · SCHEDULE

Schedule in iPlanSTO, P6 or both

  • Keep P6: schedules pass both ways by XML, so iPlanSTO and P6 stay in sync
  • Unlimited users on the site licence, so more of your team sees the schedule than P6 seats allow
  • Native CPM with FS, SS, FF, SF logic, calendars and shifts
  • Approved packs arrive as activities with hours, crews and durations on them
  • AI Schedule Review flags orphans and dangling chains
No need to give up P6
Technician updating progress on a tablet at night on site04 · EXECUTE

Track the event as it happens

  • Progress on mobile, at job step or P6 activity level
  • PV, EV, SPI, SV, EAC and forecast completion curves
  • Emergent work logged where it is found, costed separately and approved through the same gate as planned work
  • Contractor progress and delay exposure
Field and office share one dataset
Operator checking wellhead valves at sunset05 · ASSURE

Close QA/QC as you go

  • Inspection test plans and digital check sheets
  • Punch lists, non-conformances and corrective actions
  • System handover certificates
  • No system handed back with an open A-class punch
No end-of-event collation
Three workers in hard hats walking out of a plant building06 · CLOSE OUT

Feed actuals and learning into your next event

  • AI Close-Out Assistant flags variance by equipment, for example "MECH ran 40% over on E-101"
  • Lessons learned drafted for the planner to accept
  • Asset Explorer shows the last three turnarounds side by side
  • Blinds register closed and work orders TECO'd in SAP before handback
See it all in Asset Explorer, logged against your equipment

Closed loop

Each event makes the next one's estimates more accurate.

  1. Close-out actuals
  2. Shutdown Intelligence Library
  3. Next event's estimates

Also in every work pack

  • Isolation plans
  • Blind & spade registers
  • LOTO tracking
  • Flange register with torque settings
  • Turnaround-wide bill of materials
  • PO & delivery tracking

04Inside the software

The schedule and the cost of the turnaround in one system

Five screens from a demo event in iPlan4.0 STO. The cost lines come from the same work orders, steps and materials that drive the schedule.

iPlan4.0 STO Gantt chart with work orders, logic links and the critical pathiPlan4.0 STO total turnaround cost screen showing direct cost and lost productioniPlan4.0 STO cumulative cost S-curve with AFC tracker and daily burniPlan4.0 STO cost breakdown table by unit, category and work orderiPlan4.0 STO funds screen with control estimate, late work fund and contingency

05Cost of delay

What is an hour of your turnaround worth?

Enter your own figures. The calculator gives the production value of each hour the unit is down, and compares it with an iPlanSTO site licence. If your last turnaround finished on time, the case is cost certainty instead: did the estimate hold between scope freeze and close-out?

Barrels, tonnes, MWh
Price or margin

value per hour = throughput per day × value per unit ÷ 24

Lost production value per hour
–
Value of a 24-hour earlier restart
–
A single-site iPlanSTO licence equals
–
of lost production

For context: AP Networks benchmarked more than 1,350 turnarounds. Over two-thirds overran planned cost and schedule by 10% or tripped after start-up, and 40% overran by more than 30%. The figures shown in the calculator are example values. For refineries and chemical plants, use margin per unit rather than product price. Lost production only: contractor standing time, equipment hire and extended permits are not included.

06Compared to what you use today

iPlanSTO vs Primavera P6 and spreadsheets

SAP + P6 + spreadsheetsP6 or MS Project alone
Scope challengeLine-by-line review in scope meetingsNot coveredCompleteness Indicator and J-Factor per notification
EstimatesPlanner experience or generic normsTyped in by handSeeded from actuals of executed jobs
Pack readinessSupervisor review, if there is timeNot coveredAI Work Pack Review before release
Schedule vs. work ordersReconciled by handSchedule onlyGantt edits update linked work orders
ContractorsSAP licences or emailed spreadsheetsNamed-user licencesUnlimited users per site licence
ProgressDaily report, next morningUpdated from field returnsEarned value at job-step level
Emergent workPhone, chat or email; often absorbed unpricedNot coveredLogged at discovery, costed separately, same approval gate
Blinds and isolationsA separate spreadsheetNot coveredRegister inside the pack, closed before handback
Asset historyHeld by the contractor who did the workAn archived scheduleEstimate against actual per operation, kept against the equipment
After the eventA lessons-learned documentAn archived scheduleActuals reused in the next event's estimates

07Who it is for

What turnaround planning software changes for each role

Turnaround manager checking a tablet on site at nightTurnaround managers

See variance during the shift

You are accountable for cost and schedule, but the data is spread across tools.

With iPlanSTOOne dataset from scope opening. Earned value updates as job steps are reported, not in tomorrow's meeting.

Welder inside a pipe section with engineering drawings overlaidPlanners & schedulers

Start from last event's actuals

You rebuild the same packs every event, and estimates differ across the team.

With iPlanSTOEdit executed job plans from the Shutdown Intelligence Library. The schedule is checked for orphans on every recalculation.

Process plant columns and pipework at duskOperations & asset directors

Know the exposure before Day One

Every hour down costs production. The calculator above puts a figure on yours.

With iPlanSTOJ-Factor defers unjustified work before it is planned. Monte Carlo P10/P50/P90 backs the schedule with numbers.

08iPlanSTO AI

AI in turnaround planning: what it does, and what it doesn't

Watch it work · iPlanAI job planning

  1. 01 · ReadsIt reads the job, the history and the drawings

    The work order description, the equipment's prior work orders, attachments and P&IDs.

  2. 02 · DraftsIt drafts steps, trades, hours and materials

    Each labour step gets a trade, crew size, man-hours and a confidence level. Run it on one job, or on many selected work orders in the background.

  3. 03 · DecidesThe planner reviews every step, then creates the work order

    Nothing reaches the pack until a named planner accepts it.

Recreated from a recorded iPlan4.0 STO demo. The figures are from that demo job.

FeatureDoesDoesn't
AI Enrichment AgentScores notifications against the Completeness Indicator and J-FactorAdd or remove scope
iPlanAI job planningDrafts job steps, crews, manhours and materialsRelease a pack
AI Work Pack ReviewChecks packs against actuals of similar executed packsChange the pack
AI Schedule ReviewFlags orphans, dangling chains and resource conflictsRestructure the schedule
AI Close-Out AssistantFlags variance by equipment and drafts lessons learnedFile anything unaccepted

The guardrailNo scope item is added, no schedule change applied and no close-out record filed until a named planner accepts it.

09Experience not theory

Built by people who run turnarounds

Ross Coulman, IAMTech Managing Director, speaking on a panel at STO Time UAE 2023
Ross Coulman, Managing Director, on the panel at STO Time UAE 2023, the shutdowns, turnarounds and outages conference

“Data control is excellent. When preparing for a shutdown, getting the key data in place upfront is crucial. The ability to analyse planning data within iPlan is excellent.”

Matt Ramsdale · SABIC

“This software (iPlan) is really user friendly which is essential for our tradesman on the work-front.”

Nick Thompson · DIAB Engineering

“From the outset they have understood our business and have been able to come up with innovative solutions to meet our complex needs.”

Kevin Robertson · Kaefer
1996Building turnaround software, starting with ICI's process plant operations
27Countries with IAMTech software in use
1 teamSold, built, supported and maintained by one team in one office. No offshoring
CyberCyber Essentials Plus, independently tested. CyberVadis Silver (2026). Hosted on Microsoft Azure: ISO 27001, SOC 2 Type 2

10Integrations

Integrates with SAP S/4HANA, Primavera P6, Maximo and IFS

Start with planning. Your schedulers stay in P6: iPlanSTO sends the approved, resource-loaded schedule to it, and changes made in P6 come back. Moving scheduling into iPlanSTO is optional and can wait. Contractors work in the shared dataset, so you don't add ERP licences or give them SAP access.

SAP S/4HANA

⇄ both directions

Primavera P6

⇄ XML, both ways

IBM Maximo

⇄ API

IFS

⇄ API

MS Project

→ XML export

Two engineers in hard hats reviewing a laptop and tablet at a process plant at night

11Book a demo

See iPlanSTO on your own turnaround

  • 90 minutes, liveFrom scope challenge to close-out
  • Tailored to your goalsYour asset type, turnaround size and targets
  • Your questions answeredIntegrations, rollout and fit with your team
  • Zero commitmentYour data stays confidential

12Questions

Turnaround planning software FAQ

What is turnaround planning software?

Turnaround planning software is a dedicated platform for planning, scheduling, governing and executing industrial shutdowns, turnarounds and outages (STOs). Unlike general project management tools, it is built around the STO workflow: scope development, work pack management, materials coordination, contractor management and execution tracking.

How is STO planning software different from a spreadsheet?

A spreadsheet holds a static copy of the plan with no change control. iPlanSTO connects scope, schedule, materials and execution in one system, so a change to one updates the parts linked to it. It also keeps an audit trail of who changed what, role-based access, and reporting across the whole event.

Can turnaround planning software integrate with existing ERP or CMMS systems?

Yes. iPlanSTO integrates with SAP S/4HANA in both directions (notifications and maintenance orders in, order status and actuals out), and with IBM Maximo and IFS. Schedules sync both ways with Primavera P6 by XML and export to MS Project. Work orders, materials data and cost codes are synchronised so you do not enter them twice.

Do we have to replace Primavera P6?

No. P6 stays your scheduling system of record. iPlanSTO builds the resource-loaded schedule from approved work packs and syncs it with P6 both ways by XML, so changes made in either system appear in the other. The built-in Gantt is there if you later decide to move scheduling into iPlanSTO.

How long does it take to implement iPlanSTO?

Three workshops come first. Workshop 1 documents how you run turnarounds today; the software is not discussed. Workshop 2 compares that with the standard iPlanSTO workflow and lists the gaps. Workshop 3 agrees the design and gives you the configuration cost before you commit. Implementation then runs in two-week sprints with your planners, schedulers and supervisors.

What industries use turnaround planning software?

Oil and gas, refining, petrochemicals, chemicals, LNG and power generation: anywhere planned shutdowns are high-cost events where an overrun has financial and safety consequences.

Is shutdown, turnaround and outage planning software the same thing?

Yes. Shutdowns, turnarounds and outages (STOs) are the same type of planned maintenance event; the name depends on the industry. Refineries and petrochemical plants say turnaround, chemical and process plants often say shutdown, and power generation says outage. iPlanSTO is used for all three.

How much does iPlanSTO cost?

iPlanSTO is sold as one fixed annual site licence with every module included and unlimited users. In the UK a single-site licence is £75,000 per annum, falling per site for multi-site operators (five or more sites: £300,000 per annum). In the US a single-site licence is $99,000 per annum. Final pricing is scoped to your sites and deployment.

See it on your own work

Book a demo of iPlanSTO on your next turnaround

A 90-minute live walkthrough, tailored to your asset type, turnaround size and targets.

Book a demo

Download the iPlan4.0 STO brochure (PDF) · Case studies

Book a demo

Shutdown, turnaround & outage (STO) planning

iPlan4.0 STO Turnaround planning software that keeps scope, work packs, schedule and progress in one dataset.

Instead of SAP exports, P6 files and spreadsheets, iPlanSTO scores every notification before it is planned, builds packs from the actuals of executed jobs, and tracks earned value at job-step level. You see overrun risk while you can still recover it.

Used by

  • BP
  • CF Industries
  • Altrad
  • UPM
  • SOCAR
  • HMEL
  • INEOS
  • Sadara
  • Essar

Used in 27 countries

  • Winner 2024 · Business Awards UK Tech Business
  • Winner 2024 · NEPIC SME Business
  • Finalist 2025 · Lloyds AI Solution

Where turnarounds overrun

It starts in three places.

01Scope

The work list grows after it's frozen

Notifications reach planning unchallenged, and work is planned that gets cut weeks later. The planning hours are spent either way.

iPlanSTOEvery notification is scored on completeness and J-Factor before it is planned. The list freezes on a set date, and late work is costed separately.

02Estimate

The estimate restarts at every stage

Scope sits in SAP, packs in spreadsheets, the schedule in P6. Each stage produces its own number, and none traces back to the one before. On one offshore FPSO, a recently executed pack took about two-thirds of its planned time.

iPlanSTOOne record from notification to close-out, so when the cost moves you can see which stage moved it.

03Progress

You see the shift a shift late

Supervisors hold hours back to cover later slippage, and emergent work arrives by phone and takes the critical-path crews.

iPlanSTOProgress per job step from mobile. Emergent work is logged where it's found, costed and approved through the same gate as planned work.

01Inside planning

Turnarounds fail in planning, not execution

Three more gaps sit inside the planning phase.
Each one has a mechanism in iPlanSTO.

Estimates

Three planners, three estimates

Nothing checks the estimate against what the job took last time.

Estimates seeded from actuals of executed jobs on similar equipment.

Readiness

Packs released before they're ready

The missing isolation or part is found when the crew arrives.

AI Work Pack Review checks every pack. A pack cannot be scheduled until a named planner approves it.

Schedule

The schedule is retyped from the packs

Within a week the schedule and the work orders disagree.

Approved packs become activities with hours and crews on them. Sync with P6 both ways, or schedule in the built-in Gantt.

02Scope challenge

Turnaround scope challenge: every notification scored before it's planned

  • AI Enrichment AgentReads SAP notifications and maintenance orders and scores each against the 8-category Completeness Indicator.
  • Risk assessmentEach item is scored on a 5×5 likelihood × consequence matrix. Likelihood blends condition, history, frequency and exposure. Consequence takes the highest of HSE, business, environment, community and lost production. The score feeds J-Factor.
  • J-FactorWeighs the cost of doing the work against the reduction in business risk. Mandatory safety and regulatory work is always kept.
  • Monte Carlo on three-point estimatesBest, most likely and worst durations give P10, P50, P90 and the contingency you need, before a pack is written.
  • Scope freezeThe list freezes on an agreed date. Later additions go through the late-work route and are costed separately.
  • Decision written back to SAPInclude, defer or reject, with the reason and an audit trail, so a year later you can say why a job was deferred.
As written in SAP

10045872 · P-301B
"Pump tripped, found coupling worn, replace."

  • No failure mode
  • No isolation requirement
  • No estimate basis
As scored in iPlanSTO
5 / 8Completeness Indicator
StatusNeeds information
J-FactorAssessed after completion
DuplicatesNone found
Example notification. The planner sees it needs more information before anyone spends hours writing its work pack.

03How it works

How iPlanSTO works, from scope to close-out

Each phase writes to the same dataset, so the next phase starts from what the last one decided, not from an export.

Welder inside a pipe section with engineering drawings overlaid01 · PLAN

Build packs from executed jobs

  • iPlanAI drafts steps, crews, manhours and materials from a description, drawings or photos
  • Estimates seeded from the Shutdown Intelligence Library
  • Productivity and no-work-time factors (shift patterns, permit waits, congestion) applied when manhours become durations
  • Planner edits, regenerates or rejects every output
Edit, don't rebuild
Engineer walking a pipe rack between flanged valves02 · REVIEW

Check packs before release

  • AI Work Pack Review against actuals from similar executed packs
  • Labour, crew size, duration, cost, materials and risk
  • Findings graded Critical, Advisory or Information
  • No approval, no scheduling: unapproved packs stay out of the schedule
Nothing changed automatically
Aerial view of plant pipework and storage tanks03 · SCHEDULE

Schedule in iPlanSTO, P6 or both

  • Keep P6: schedules pass both ways by XML, so iPlanSTO and P6 stay in sync
  • Unlimited users on the site licence, so more of your team sees the schedule than P6 seats allow
  • Native CPM with FS, SS, FF, SF logic, calendars and shifts
  • Approved packs arrive as activities with hours, crews and durations on them
  • AI Schedule Review flags orphans and dangling chains
No need to give up P6
Technician updating progress on a tablet at night on site04 · EXECUTE

Track the event as it happens

  • Progress on mobile, at job step or P6 activity level
  • PV, EV, SPI, SV, EAC and forecast completion curves
  • Emergent work logged where it is found, costed separately and approved through the same gate as planned work
  • Contractor progress and delay exposure
Field and office share one dataset
Operator checking wellhead valves at sunset05 · ASSURE

Close QA/QC as you go

  • Inspection test plans and digital check sheets
  • Punch lists, non-conformances and corrective actions
  • System handover certificates
  • No system handed back with an open A-class punch
No end-of-event collation
Three workers in hard hats walking out of a plant building06 · CLOSE OUT

Feed actuals and learning into your next event

  • AI Close-Out Assistant flags variance by equipment, for example "MECH ran 40% over on E-101"
  • Lessons learned drafted for the planner to accept
  • Asset Explorer shows the last three turnarounds side by side
  • Blinds register closed and work orders TECO'd in SAP before handback
See it all in Asset Explorer, logged against your equipment

Closed loop

Each event makes the next one's estimates more accurate.

  1. Close-out actuals
  2. Shutdown Intelligence Library
  3. Next event's estimates

Also in every work pack

  • Isolation plans
  • Blind & spade registers
  • LOTO tracking
  • Flange register with torque settings
  • Turnaround-wide bill of materials
  • PO & delivery tracking

04Inside the software

The schedule and the cost of the turnaround in one system

Five screens from a demo event in iPlan4.0 STO. The cost lines come from the same work orders, steps and materials that drive the schedule.

iPlan4.0 STO Gantt chart with work orders, logic links and the critical path
iPlan4.0 STO total turnaround cost screen showing direct cost and lost production
iPlan4.0 STO cumulative cost S-curve with AFC tracker and daily burn
iPlan4.0 STO cost breakdown table by unit, category and work order
iPlan4.0 STO funds screen with control estimate, late work fund and contingency

05Cost of delay

What is an hour of your turnaround worth?

Enter your own figures. The calculator gives the production value of each hour the unit is down, and compares it with an iPlanSTO site licence. If your last turnaround finished on time, the case is cost certainty instead: did the estimate hold between scope freeze and close-out?

Barrels, tonnes, MWh
Price or margin

value per hour = throughput per day × value per unit ÷ 24

Lost production value per hour
–
Value of a 24-hour earlier restart
–
A single-site iPlanSTO licence equals
–
of lost production

For context: AP Networks benchmarked more than 1,350 turnarounds. Over two-thirds overran planned cost and schedule by 10% or tripped after start-up, and 40% overran by more than 30%. The figures shown in the calculator are example values. For refineries and chemical plants, use margin per unit rather than product price. Lost production only: contractor standing time, equipment hire and extended permits are not included.

06Compared to what you use today

iPlanSTO vs Primavera P6 and spreadsheets

SAP + P6 + spreadsheetsP6 or MS Project alone
Scope challengeLine-by-line review in scope meetingsNot coveredCompleteness Indicator and J-Factor per notification
EstimatesPlanner experience or generic normsTyped in by handSeeded from actuals of executed jobs
Pack readinessSupervisor review, if there is timeNot coveredAI Work Pack Review before release
Schedule vs. work ordersReconciled by handSchedule onlyGantt edits update linked work orders
ContractorsSAP licences or emailed spreadsheetsNamed-user licencesUnlimited users per site licence
ProgressDaily report, next morningUpdated from field returnsEarned value at job-step level
Emergent workPhone, chat or email; often absorbed unpricedNot coveredLogged at discovery, costed separately, same approval gate
Blinds and isolationsA separate spreadsheetNot coveredRegister inside the pack, closed before handback
Asset historyHeld by the contractor who did the workAn archived scheduleEstimate against actual per operation, kept against the equipment
After the eventA lessons-learned documentAn archived scheduleActuals reused in the next event's estimates

07Who it is for

What turnaround planning software changes for each role

Turnaround manager checking a tablet on site at nightTurnaround managers

See variance during the shift

You are accountable for cost and schedule, but the data is spread across tools.

With iPlanSTOOne dataset from scope opening. Earned value updates as job steps are reported, not in tomorrow's meeting.

Welder inside a pipe section with engineering drawings overlaidPlanners & schedulers

Start from last event's actuals

You rebuild the same packs every event, and estimates differ across the team.

With iPlanSTOEdit executed job plans from the Shutdown Intelligence Library. The schedule is checked for orphans on every recalculation.

Process plant columns and pipework at duskOperations & asset directors

Know the exposure before Day One

Every hour down costs production. The calculator above puts a figure on yours.

With iPlanSTOJ-Factor defers unjustified work before it is planned. Monte Carlo P10/P50/P90 backs the schedule with numbers.

08iPlanSTO AI

AI in turnaround planning: what it does, and what it doesn't

Watch it work · iPlanAI job planning

  1. 01 · ReadsIt reads the job, the history and the drawings

    The work order description, the equipment's prior work orders, attachments and P&IDs.

  2. 02 · DraftsIt drafts steps, trades, hours and materials

    Each labour step gets a trade, crew size, man-hours and a confidence level. Run it on one job, or on many selected work orders in the background.

  3. 03 · DecidesThe planner reviews every step, then creates the work order

    Nothing reaches the pack until a named planner accepts it.

Recreated from a recorded iPlan4.0 STO demo. The figures are from that demo job.

FeatureDoesDoesn't
AI Enrichment AgentScores notifications against the Completeness Indicator and J-FactorAdd or remove scope
iPlanAI job planningDrafts job steps, crews, manhours and materialsRelease a pack
AI Work Pack ReviewChecks packs against actuals of similar executed packsChange the pack
AI Schedule ReviewFlags orphans, dangling chains and resource conflictsRestructure the schedule
AI Close-Out AssistantFlags variance by equipment and drafts lessons learnedFile anything unaccepted

The guardrailNo scope item is added, no schedule change applied and no close-out record filed until a named planner accepts it.

09Experience not theory

Built by people who run turnarounds

Ross Coulman, IAMTech Managing Director, speaking on a panel at STO Time UAE 2023
Ross Coulman, Managing Director, on the panel at STO Time UAE 2023, the shutdowns, turnarounds and outages conference

“Data control is excellent. When preparing for a shutdown, getting the key data in place upfront is crucial. The ability to analyse planning data within iPlan is excellent.”

Matt Ramsdale · SABIC

“This software (iPlan) is really user friendly which is essential for our tradesman on the work-front.”

Nick Thompson · DIAB Engineering

“From the outset they have understood our business and have been able to come up with innovative solutions to meet our complex needs.”

Kevin Robertson · Kaefer
1996Building turnaround software, starting with ICI's process plant operations
27Countries with IAMTech software in use
1 teamSold, built, supported and maintained by one team in one office. No offshoring
CyberCyber Essentials Plus, independently tested. CyberVadis Silver (2026). Hosted on Microsoft Azure: ISO 27001, SOC 2 Type 2

10Integrations

Integrates with SAP S/4HANA, Primavera P6, Maximo and IFS

Start with planning. Your schedulers stay in P6: iPlanSTO sends the approved, resource-loaded schedule to it, and changes made in P6 come back. Moving scheduling into iPlanSTO is optional and can wait. Contractors work in the shared dataset, so you don't add ERP licences or give them SAP access.

SAP S/4HANA

⇄ both directions

Primavera P6

⇄ XML, both ways

IBM Maximo

⇄ API

IFS

⇄ API

MS Project

→ XML export

Two engineers in hard hats reviewing a laptop and tablet at a process plant at night

11Book a demo

See iPlanSTO on your own turnaround

  • 90 minutes, liveFrom scope challenge to close-out
  • Tailored to your goalsYour asset type, turnaround size and targets
  • Your questions answeredIntegrations, rollout and fit with your team
  • Zero commitmentYour data stays confidential

12Questions

Turnaround planning software FAQ

What is turnaround planning software?

Turnaround planning software is a dedicated platform for planning, scheduling, governing and executing industrial shutdowns, turnarounds and outages (STOs). Unlike general project management tools, it is built around the STO workflow: scope development, work pack management, materials coordination, contractor management and execution tracking.

How is STO planning software different from a spreadsheet?

A spreadsheet holds a static copy of the plan with no change control. iPlanSTO connects scope, schedule, materials and execution in one system, so a change to one updates the parts linked to it. It also keeps an audit trail of who changed what, role-based access, and reporting across the whole event.

Can turnaround planning software integrate with existing ERP or CMMS systems?

Yes. iPlanSTO integrates with SAP S/4HANA in both directions (notifications and maintenance orders in, order status and actuals out), and with IBM Maximo and IFS. Schedules sync both ways with Primavera P6 by XML and export to MS Project. Work orders, materials data and cost codes are synchronised so you do not enter them twice.

Do we have to replace Primavera P6?

No. P6 stays your scheduling system of record. iPlanSTO builds the resource-loaded schedule from approved work packs and syncs it with P6 both ways by XML, so changes made in either system appear in the other. The built-in Gantt is there if you later decide to move scheduling into iPlanSTO.

How long does it take to implement iPlanSTO?

Three workshops come first. Workshop 1 documents how you run turnarounds today; the software is not discussed. Workshop 2 compares that with the standard iPlanSTO workflow and lists the gaps. Workshop 3 agrees the design and gives you the configuration cost before you commit. Implementation then runs in two-week sprints with your planners, schedulers and supervisors.

What industries use turnaround planning software?

Oil and gas, refining, petrochemicals, chemicals, LNG and power generation: anywhere planned shutdowns are high-cost events where an overrun has financial and safety consequences.

Is shutdown, turnaround and outage planning software the same thing?

Yes. Shutdowns, turnarounds and outages (STOs) are the same type of planned maintenance event; the name depends on the industry. Refineries and petrochemical plants say turnaround, chemical and process plants often say shutdown, and power generation says outage. iPlanSTO is used for all three.

How much does iPlanSTO cost?

iPlanSTO is sold as one fixed annual site licence with every module included and unlimited users. In the UK a single-site licence is £75,000 per annum, falling per site for multi-site operators (five or more sites: £300,000 per annum). In the US a single-site licence is $99,000 per annum. Final pricing is scoped to your sites and deployment.

See it on your own work

Book a demo of iPlanSTO on your next turnaround

A 90-minute live walkthrough, tailored to your asset type, turnaround size and targets.

Book a demo

Download the iPlan4.0 STO brochure (PDF) · Case studies