Scan-to-Model — Piping Passion

The workflow

Scope definition & scan planning

Before sending anyone to site with a scanner, define exactly which areas need to be captured, what level of detail is required, and what the data will be used for. A scan for clash checking needs different coverage than a scan for as-built documentation.

Field tip — Plan your scan station positions on a plot plan first. You need at least 30% overlap between adjacent scans for reliable registration. In congested pipe racks, this means more stations than you think.

Site scanning & data capture

The quality of your model is limited by the quality of your scan. Scanner positioning, environmental conditions, target placement, and coverage decisions made on site cannot be corrected back at the office. Accompany the scan operator when possible — a piping designer's eye catches gaps that a generic surveyor won't notice.

Field tip — Check scan registration on a field tablet before leaving each area. Cloud-to-cloud registration errors discovered on site can be corrected immediately. The same errors discovered back at the office mean a second site visit.

Point cloud registration & cleaning

Individual scan stations must be registered (stitched together) into a single coherent point cloud. Accuracy depends on target quality, overlap, and the registration software. After registration, noise reduction and classification improve usability.

Field tip — Never skip the visual inspection of the registered cloud. Misregistered areas show up as double lines or blurry surfaces. Catch them now before they cause routing errors downstream.

Point cloud import into 3D design tool

Most modern piping design tools (PDMS, E3D, Plant 3D, AVEVA) can reference point cloud data directly. The cloud becomes the background against which you model new equipment and piping. Accuracy here depends on the coordinate system alignment.

Field tip — Confirm the coordinate system of the point cloud matches your model before any design work begins. A misaligned cloud that looks "close enough" will compound errors across the entire project.

As-built verification & clash checking

With the point cloud loaded, verify existing conditions against drawings, identify discrepancies, and use the cloud as the reference for all clearance checks. Any new piping routed through the model can be checked against the cloud for physical conflicts.

Field tip — Small-bore pipes (2" and below) are often missed in scans due to point density limitations. Always check areas with dense small-bore runs manually, regardless of what the clash report says.

Deliverable & documentation update

The scan data, once captured and registered, is a permanent record of the plant at that point in time. Update as-built drawings from the cloud. Archive the registered scan file. This investment pays back on every future project in the same area.