Tag: Brownfield

The Reality of Brownfield Development

Brownfield projects are not clean, linear, or model-driven.

They are:

• Reactive
• Incremental
• Constrained by existing infrastructure
• Driven by time, cost, and operational pressure

In this environment, the idea of maintaining a fully coordinated 3D model is often unrealistic.

A simple example illustrates this:

An electrician installs an additional power point on site. The work is completed, energised, and signed off. The drawings may be updated later — the model almost never is.

This is not a failure of process — it is the reality of brownfield operations.

---

Engineering Reality: From Sketch to CAD

Before anything becomes a 3D model, it starts much simpler.

As engineers, we still:

• Sketch ideas
• Mark up drawings
• Discuss constraints on site

Only after this thinking process do concepts become CAD models.

This reinforces a key principle:

Engineering decisions are not driven by software — software supports engineering judgement.

---

The Problem with Model-Centric Workflows

Platforms such as Autodesk Navisworks Manage are often positioned as central coordination tools, and in the right context they are highly effective.

However, in brownfield environments they introduce challenges:

Model Drift

• Models quickly become outdated
• Site changes are rarely captured in real time

High Maintenance Cost

• Continuous updates require time and budget
• Maintenance of models is rarely prioritised operationally

Limited Long-Term Trust

• Teams revert back to:
  • Drawings
  • Site verification
  • Experience

The result is that the model becomes a temporary tool rather than a reliable long-term asset.

---

Where Multi-Discipline Coordination Actually Matters

Navisworks is most powerful when used for:

• Multi-discipline coordination
• Clash detection
• Design validation

This is critical in greenfield environments where:

• Structural, mechanical, electrical, and civil systems are designed simultaneously
• Multiple teams work in parallel
• Design clashes must be resolved before construction

In these cases, Navisworks plays a vital role in reducing risk and improving delivery outcomes.

---

Brownfield Reality: Coordination Happens on Site

In brownfield environments, the situation is very different.

Work is typically:

• Localised
• Task-specific
• Carried out in isolation

Constraints are:

• Already physically present
• Visible and measurable
• Managed in real time on site

In many cases:

Multi-discipline coordination is minimal or already resolved physically.

For example, an electrician installing a new outlet:

• Reviews the environment
• Works around existing services
• Completes the installation

There is no model update, no coordination session, and no Navisworks workflow involved.

---

Point Cloud Data: The True As-Built Record

Using platforms such as FARO SCENE, point cloud data provides:

• A direct capture of real-world conditions
• A measurable and verifiable dataset
• A snapshot of the plant at a point in time

Unlike models, point clouds are not interpretations — they are records of reality.

---

Critical Limitation: Line-of-Sight

Point cloud data is inherently line-of-sight dependent.

This means:

• Only visible surfaces are captured
• Occlusions create gaps in the dataset

When navigating a point cloud — whether in SCENE or Navisworks — moving outside original scan positions reveals these gaps.

Importantly:

• This is not a software limitation
• It is a fundamental characteristic of LiDAR capture

Creating a Navisworks model from a point cloud does not resolve this issue. It simply introduces another layer of processing without improving data completeness.

---

Why Navisworks Adds Limited Value for Point Cloud Management

If the objective is:

• Visualisation
• Measurement
• Inspection

Then native scan platforms already provide these capabilities.

Within SCENE, users can:

• Navigate freely
• Measure accurately
• Clip and section data
• Access models using free viewer tools

Introducing Navisworks adds:

• Additional processing steps
• Data conversion (e.g. E57 to RCP)
• Larger and duplicated datasets
• No improvement in scan accuracy or completeness

Navisworks does not remove line-of-sight limitations, does not fill missing data, and does not enhance the underlying scan.

---

Best Practice: Brownfield Data Strategy

A more practical and effective approach is:

1. Point Cloud as the Primary Asset

• Maintain original scan data (e.g. E57)
• Store registered datasets
• Use native platforms for access and interrogation

2. Targeted Modelling Only Where Required

• Model critical interfaces and tie-in points
• Avoid full plant modelling unless necessary

3. Drawings for Formal Deliverables

• Maintain as-built documentation
• Use redlines where appropriate

4. Navisworks for Project Phases Only

• Apply Navisworks during major upgrades or greenfield-style coordination
• Do not rely on it as a long-term data environment

---

Key Project Management Insight

Models degrade over time in brownfield environments.

Point cloud data remains a verifiable record of reality.

---

Conclusion

Navisworks remains a powerful tool for coordination and design validation, particularly in greenfield projects where multi-discipline interaction is high.

However, for brownfield project management:

• Point clouds provide truth
• Drawings provide documentation
• Navisworks provides temporary coordination

If the objective is to visualise, measure, and understand existing conditions, managing point cloud data within native scanning platforms is more efficient, more accurate, and more sustainable than relying on Navisworks models.

---

One-Line Summary

In brownfield projects, the scan is the asset — the model is only a moment in time.

---

Our clients

Contact Us – Talk to Us