A turnaround schedule can look perfectly sound on paper right up until the first day of mobilization, when a scaffold crew discovers that the access route drawn on the plan runs directly through a pipe rack nobody accounted for, or a crane pad sits closer to a live line than the lift plan assumed. These clashes are rarely caught until people and equipment are already on site, at which point every hour spent replanning is an hour added to a schedule that was already tight. A 3D laser scan of the unit paired with AI-driven clash analysis surfaces these conflicts weeks before mobilization instead of on day one. See how iFactory processes point cloud scans into a pre-turnaround clash report with a Book a Demo.
Find The Scaffold Clash Before The Crew Finds It On Day One
A laser scan of the process unit captures every pipe, structure, and obstruction as it actually exists today, not as the outdated as-built drawing shows it. iFactory runs AI clash analysis against that point cloud to flag scaffold, access, and lifting conflicts before mobilization begins.
Turnaround Planning Still Relies On Drawings That Don't Match Reality
Most turnaround planning starts from as-built drawings and P&IDs that were accurate at some point in the unit's history but have accumulated small, undocumented changes ever since, from a rerouted pipe run to a temporary platform that became permanent. The planning team works from what the drawing says, while the field crew works from what is actually standing there, and the gap between the two only becomes visible once mobilization is underway.
Drawings Lag Behind Field Modifications
A pipe support added during a prior maintenance campaign or a platform extension installed without a formal drawing update means the planning team is working from an incomplete picture of the actual site.
Scaffold Design Happens Without True Spatial Data
Scaffold designers often work from general arrangement drawings rather than precise measurements, which means access routes and standing platforms get planned around an approximate layout instead of the exact obstructions present.
Lift Plans Assume Clearances That May Not Exist
A crane lift plan calculated from drawing dimensions can miss an as-built clearance issue with an overhead line or an adjacent structure that only becomes apparent once the crane is actually positioned on site.
Field Discovery Consumes Schedule Contingency
Every clash discovered after mobilization eats into the schedule contingency that was meant to absorb unexpected problems during the turnaround itself, not problems that could have been identified during planning.
From Point Cloud To A Ranked List Of Conflicts
Turning a raw laser scan into an actionable clash report involves several distinct stages, each of which determines how useful the final output is to the planning team.
Field Scanning
A laser scanner captures the unit from multiple positions, recording millions of precise measurement points that together form a complete point cloud of the current physical layout.
Point Cloud Registration
Individual scan positions are aligned and merged into a single unified point cloud, giving a continuous and geometrically accurate model of the entire unit rather than disconnected fragments.
AI Object Recognition
AI models process the point cloud to identify and classify pipe runs, structural steel, platforms, and equipment, converting raw geometry into a labeled model the planning team can actually query.
Clash Detection Against Plans
The labeled model is checked against the proposed scaffold layout, access routes, and lift plans to identify where a planned element intersects with or comes too close to an actual physical obstruction.
The Conflicts A Pre-Turnaround Scan Catches Most Often
Certain categories of clashes appear repeatedly across turnaround projects, and knowing where to look first helps planning teams prioritize which areas of the unit need the closest review.
| Clash Type | Common Cause | Typical Impact If Found Late |
|---|---|---|
| Scaffold-to-pipe interference | Undocumented pipe reroute since last as-built update | Rework of scaffold design after erection begins |
| Access route obstruction | Temporary platform or equipment left in place from prior work | Delayed crew mobilization into the work area |
| Crane clearance conflict | Overhead line or structure not reflected in lift plan drawing | Lift plan revision or crane repositioning on site |
| Laydown area overlap | Planned staging area occupied by existing structure or equipment | Search for alternate staging space during mobilization |
Areas of the unit that have gone through multiple prior maintenance campaigns or informal field modifications tend to accumulate the highest concentration of undocumented clashes, making them a priority for scanning even when the overall unit is not being scanned in full.
Where 3D Scanning Initiatives Fall Short Of Their Value
Capturing a scan is only the first step, and a few recurring mistakes can prevent the resulting data from actually improving turnaround planning outcomes.
Scanning Too Close To Mobilization
Scheduling the scan and clash analysis only a few days before mobilization leaves little time to actually redesign a scaffold layout or revise a lift plan once a conflict is identified, undermining much of the benefit of catching it early.
Scanning Without A Defined Analysis Scope
Capturing a scan without a clear plan for which proposed scaffold, access, and lift designs will be checked against it often results in a large dataset that never gets systematically reviewed for clashes.
Treating The Scan As A One-Time Snapshot
A point cloud captured for one turnaround becomes outdated once further field modifications occur, so relying on an old scan for a future turnaround without rescanning can reintroduce the same gap between drawing and reality.
Findings Not Communicated Back To Field Planners
A clash report that stays with the engineering team without being translated into a revised scaffold drawing or lift plan for the field crew fails to prevent the exact problem the scan was meant to catch.
On our last turnaround, we scanned the unit six weeks before mobilization and the clash analysis flagged a scaffold design that would have run directly into a pipe support nobody had drawn correctly in years. Redesigning that section on paper took an afternoon. Finding it after the scaffold crew was already on site would have cost us at least two days of rework in the middle of a schedule with almost no slack left in it.
Know Every Clash Before The Crew Mobilizes
iFactory processes your unit's point cloud scan and flags scaffold, access, and lift plan conflicts weeks ahead of turnaround start, giving planners time to redesign instead of react.
What Turnaround Teams Typically See From Pre-Scan Clash Detection
Results vary with unit complexity and how far ahead of mobilization the scan is completed, but the ranges below reflect what turnaround teams commonly report after adding a pre-turnaround scan and AI clash analysis to their planning process.
Resolution And Accuracy Levels That Actually Support Clash Detection
Not every scan is captured at a resolution fine enough to support reliable clash detection, and understanding what level of accuracy a given use case needs helps avoid both wasted scanning effort and gaps that let a real clash slip through undetected.
Point Density And Registration Accuracy
A scan with insufficient point density can miss small but critical obstructions such as a support bracket or a narrow pipe run, while poor registration between individual scan positions introduces small alignment errors that compound into a misleading overall model.
Coverage Of Occluded Areas
Areas hidden behind existing structure or equipment from a single scanner position need additional scan setups to capture, since a gap in coverage in exactly the area a scaffold needs to pass through defeats the purpose of the scan.
Tolerance Appropriate To The Application
Scaffold and access clash detection generally needs coarser tolerance than precision dimensional work such as fabrication verification, so matching the scan specification to the actual planning use case avoids over-scanning areas that do not need survey-grade precision.
Connecting Clash Findings To Turnaround Management Systems
A clash report is most useful when it flows directly into the systems planners already use to track scope, schedule, and work orders, rather than existing as a separate document that has to be manually cross-referenced.
Linking Clashes To Work Scope Items
Tying each identified clash directly to the specific scaffold, access, or lift work scope item it affects means a planner reviewing that scope item sees the conflict immediately rather than discovering it separately in a standalone report.
Tracking Resolution Status
Recording whether a flagged clash has been reviewed, redesigned, or accepted as-is gives the planning team a clear status view across potentially dozens of findings rather than relying on memory or scattered email threads.
Feeding The Digital Twin Forward
A processed point cloud built for one turnaround's clash detection can also serve as a reference model for future planning cycles, provided it gets refreshed as field modifications accumulate over time.
Frequently Asked Questions
Q: How far in advance of a turnaround should the unit be scanned?
Most turnaround teams see the best results scanning four to eight weeks ahead of mobilization, which leaves enough time to run the clash analysis, redesign any conflicting scaffold or lift plans, and get the revised plans approved before crews arrive on site. Scanning too close to mobilization reduces the value of catching a clash early, since there may not be enough time left to act on the finding.
Q: Does the entire unit need to be scanned, or just the turnaround work areas?
Scanning can be scoped to the specific areas involved in the turnaround work scope, including scaffold zones, access routes, and lift paths, rather than the entire unit, which keeps the scanning effort proportional to the actual planning need. Areas with a history of undocumented field modifications are generally worth prioritizing even if they fall outside the immediate work scope, since they carry a higher likelihood of hidden clashes.
Q: How does AI clash detection differ from a planner manually reviewing the scan?
A planner manually reviewing a point cloud can check specific areas of concern but cannot realistically review every intersection between a proposed scaffold design and millions of scan points by hand. AI-driven analysis systematically checks the full proposed layout against the complete scan, surfacing conflicts a manual review would likely miss simply due to the volume of data involved. A Book a Demo session can show how this analysis works against your specific unit layout.
Q: Can a scan from a previous turnaround be reused for the next one?
A prior scan can be a useful reference, but it should not be treated as fully current if any field modifications, temporary installations, or structural changes have occurred since it was captured. Rescanning before each major turnaround, or at minimum verifying that no significant changes have occurred in the relevant work areas, keeps the clash analysis based on the unit as it actually exists today.
Q: What happens once a clash is identified in the analysis?
Once a clash is flagged, the finding is typically routed back to the scaffold designer, access planner, or lift plan engineer responsible for that specific element, along with the precise location and dimensions of the conflict from the scan data. This lets the affected plan be revised on paper well before mobilization rather than discovered and corrected in the field. Reach out through Support Contact to discuss how findings integrate with your existing turnaround planning workflow.
Redesign On Paper, Not On The Scaffold
iFactory turns a pre-turnaround laser scan into a ranked clash report weeks before mobilization, giving your planning team time to fix conflicts before they cost schedule days.
