Expanding a Plant Without Knowing What's in the Walls Is the Most Expensive Mistake You Can Make

Key takeaways

• A plant expansion that touches existing installations is only as accurate as the information feeding the design.
• Before designing, engineering needs four things in real X-Y-Z coordinates: where the ducts are, how they'll be rerouted, how they integrate with the civil design, and where new equipment ties in.
• A laser scan delivers all four as a millimeter-accurate point cloud — used directly, or modeled to CAD/BIM.
• The alternative — designing on old drawings and verifying during construction — turns into stop-and-redesign or field improvisation, usually several times the scan cost.
• The question isn't whether to scan before expanding; it's when. The answer: before the design advances, not after the contractor finds the problem.

When Goodyear decided to expand its tire plant in Lawton, Oklahoma, the challenge wasn't the construction itself — it was what was in the wall.

The expansion meant extending the plant toward a side where a wall had several ducts running tight against it. These weren't minor installations: they were part of the process, and had to be relocated or reconnected for the new space to work. Before the engineering firm could propose how, they needed to know exactly what was there — positions, diameters, routes, connection points. The available drawings weren't enough. So before designing, they scanned.

What you need to know before you move an installation

A plant expansion involving existing installations has a structural problem: the engineering design can only be as precise as the information that feeds it. If the drawings of existing installations have errors, are outdated, or lack the detail detailed engineering requires, the project starts on uncertain ground — and that uncertainty doesn't disappear. It turns into field surprises.

In this case, the engineering team needed four concrete things before it could propose a solution:

1. Exactly where the ducts were — not approximately, but with the precision an engineering model requires: position in X, Y and Z, diameters, real routes.
2. How they'd be relocated or reconnected — to define new routes, you first have to understand current routes and the points where connections are possible.
3. How to integrate those routes into the civil design — the structural design of the expansion had to account for the space the relocated ducts would occupy; it couldn't be designed in isolation.
4. Where new equipment ties in — the tie-in points for new equipment had to be defined in real coordinates, not estimated on a drawing nobody had verified in years.

None of those four was possible without first capturing what existed in that space, accurately.

What the scan delivered

We scanned the area to be modified and delivered the complete point cloud: the existing installations, the wall geometry, the ducts with their real routes, and the full surrounding context captured at millimeter accuracy.

The deliverable was the point cloud directly — no 3D modeling. The engineering firm on the project had experience working with point clouds and chose to model internally. They didn't need us to convert the data to a CAD model; they needed the most accurate data possible, and from there their own team designed the solution.

This is worth underlining: laser scanning doesn't always mean receiving a finished 3D model. For engineering teams experienced in reality capture, the point cloud is the direct work input — often exactly what they need. The deliverable adapts to what the client's team can use best. (When you do want a finished model, that's Scan-to-CAD/BIM.)

What would have happened without the scan

The alternative would have been designing the expansion from available drawings and verifying during construction. That approach has a known cost: when the contractor reaches the site and finds the drawing doesn't match reality, there are two options. Stop, redesign and reschedule — or improvise in the field, which almost always produces a more expensive, messier solution with interference risks discovered only after the problem has already happened.

In active process facilities, improvising with ducts isn't a real option. The cost of resolving a field interference — in construction downtime, change orders, trade coordination — is usually several times the cost of the scan that would have prevented all of it.

The pattern repeats in every serious expansion

Goodyear isn't an exception. It's the case that repeats every time a manufacturing plant grows or changes. Any expansion that touches existing installations — ducts, pipe, structure, equipment — needs to know exactly what's in the area before detailed engineering starts. Not as a rough reference: with the precision to design on that data without creating conflicts the project can't absorb.

The question isn't whether it's worth scanning before expanding. It's when in the project to do it. And the answer is almost always the same: before the design advances, not after the contractor finds the problem.

If you have an expansion or remodel in progress and want to know which area to document first and what deliverable your engineering team needs, tell us. In a short call we can give you a clear estimate of time and scope.

We're based in Houston, ISNetworld®-compliant, serving Texas, Louisiana, Oklahoma and the Gulf Coast. Request a quote or call +1 (832) 746-1497.

Frequently asked questions

When should I scan during a plant expansion project?
Before detailed engineering begins. Capturing existing conditions up front lets the design account for real routes and clearances, instead of discovering conflicts in the field during construction.

Do I get a 3D model or just the point cloud?
Whichever your team can use best. Engineering firms experienced with point clouds often work from the cloud directly; others want a finished Scan-to-CAD/BIM model. We scope the deliverable to your workflow.

How accurate is the scan for engineering design?
Survey-grade — typically ±2 mm with terrestrial scanners — captured in real X-Y-Z coordinates, which is what detailed engineering needs to design on existing conditions without conflicts.

Why not just use our existing drawings?
Because in most plants the drawings don't match the field after years of modifications. Designing an expansion on them moves the discovery of conflicts from the screen (cheap) to construction (expensive).

Can you scan only the area we're modifying?
Yes. We scope to the area to be intervened, which controls cost; the captured cloud can be reused later if the scope expands.