What 10 Years in Laser Scanning Has Taught Us About Engineering Delays

When people talk about engineering delays they tend to focus on the obvious causes. Procurement issues, contractor availability, design changes, unexpected site conditions. After spending more than ten years working in laser scanning and reality capture we’ve found ourselves looking at delays slightly differently.

The longer we’ve been involved in projects the more we’ve come to believe that delays are rarely caused by a single event. More often than not they’re the result of uncertainty that has been present from the very beginning. It sits quietly in the background of a project, often unnoticed, until eventually it surfaces as a problem that somebody has to solve.

We’ve seen this pattern across manufacturing facilities, process plants, commercial buildings, infrastructure projects and operational environments where change is constant. The details vary from project to project but the underlying story is incredibly similar. A team begins work using the best information available, decisions are made, designs progress and schedules are agreed. Then at some point reality and documentation stop matching one another.

A pipe route isn’t where the drawings say it is. Structural elements have been modified over the years. Equipment has been replaced multiple times since the original documentation was produced. Dimensions that seemed certain suddenly become questionable. What follows is usually a sequence of entirely reasonable actions. Engineers seek clarification, contractors request confirmation, additional surveys are commissioned and designs are revised. Nobody has necessarily made a mistake yet the programme starts to slip.

What’s interesting is that the delay itself is often treated as the problem, when in reality it is simply the symptom. The real issue existed much earlier. The project was operating with incomplete knowledge of existing conditions.

One of the most valuable things laser scanning has given us over the years isn’t just data, It’s perspective. We’ve had the opportunity to walk through hundreds of facilities and observe how assets evolve over time. One thing becomes apparent very quickly: the physical world changes far more often than most documentation systems can keep up with.

Even facilities with excellent documentation standards experience this. Small modifications are made during shutdown periods or equipment is relocated, pipework is rerouted, temporary solutions become permanent solutions, the list is endless. Over a period of ten or twenty years these individual changes accumulate until the site that exists today is subtly different from the site represented in its drawings.

This isn’t a criticism of traditional documentation it’s just the reality of operating complex assets. Keeping records perfectly aligned with the physical environment is incredibly difficult particularly when facilities are under constant pressure to remain productive.

What we’ve learned is that engineering teams are generally very good at solving problems. The challenge is that they often spend an enormous amount of time solving problems that originate from uncertainty rather than technical complexity. There is a significant difference between overcoming a genuine engineering challenge and spending weeks confirming dimensions, validating assumptions or revisiting site conditions that should have been understood from the outset.

One experience that stands out over the years is how often projects return to site. In many cases the first survey is completed with a specific objective in mind. The required information is collected, the project moves forward and everything appears to be progressing smoothly but then a new requirement emerges. An engineer needs a measurement that wasn’t considered important at the time or perhaps a contractor wants additional context, a clash is identified and requires investigation.

Suddenly the team is organising another visit.

The financial cost of these return visits is usually easy to calculate. Travel expenses, labour costs, permits and access arrangements all have obvious price tags attached to them. What is harder to quantify is the disruption they create because projects like these rely heavily on momentum. Once progress is interrupted the delays rarely remain isolated and design work pauses while information is gathered. Procurement decisions wait for confirmation, installation activities are pushed back making this initial small interruption a much larger fault.

Over the years we’ve become convinced that one of the most overlooked causes of delay is simply the lack of confidence in available information. When teams trust the data they’re working from, decisions happen faster and designs progress with greater certainty. When risks can be assessed more accurately the discussions focus on solutions rather than verification.

This is why our own view of laser scanning has changed significantly since CUB3D first started. Initially, like many people, we saw scanning primarily as a measurement tool. Today, we see it as a confidence tool.

The point cloud, the model and the drawings are important outputs, but they aren’t the real product. The real product is assurance. It’s giving project teams the confidence to make decisions without constantly questioning whether the underlying information is accurate.

Looking back over ten years, that’s probably the lesson that stands out most. Engineering projects are becoming more complex. While facilities are ageing, infrastructure is under increasing pressure and expectations around efficiency continue to rise.

The projects that perform best aren’t necessarily the ones with the most advanced technology or the largest budgets. They’re often the ones that establish clarity early and invest time in understanding challenges before they begin changing it.

After spending a decade capturing the built world, we’ve come to a simple conclusion. Delays rarely begin when work stops. They begin much earlier, at the moment assumptions replace certainty.

And the longer a project relies on assumptions, the more likely those assumptions are to become tomorrow’s delay. Contact us today to discuss your ideas!

Related Posts

Part 4: How Laser Scanning Is Used in Real Projects

Part 2: What Is a Point Cloud? 

Part 1: What is 3D Laser Scanning?