Executive Summary
In brownfield projects, the highest return comes from applying engineering design effort at the point of change, supported by accurate point cloud data, rather than continuously updating a federated model.
The practical reality is:
Invest in engineering decisions, not in maintaining a model that becomes outdated faster than the plant changes.
Two Approaches
1. Model Maintenance–Centric (Navisworks)
Using Autodesk Navisworks Manage as an ongoing platform:
- Maintain a full federated model
- Update after every site change
- Re-run coordination and clash detection
- Manage model alignment across disciplines
2. Engineering-Driven (Point Cloud + Targeted CAD)
Using:
- FARO SCENE
- SOLIDWORKS eDrawings
- Capture and retain point cloud data as the primary asset
- Model only what is being modified
- Use CAD and drawings for fabrication and communication
Cost Drivers
Navisworks Model Maintenance
- Initial model creation and federation
- Continuous updates after modifications
- Data conversion and reprocessing
- Coordination meetings and clash resolution
- Ongoing QA and model validation
Additional hidden costs include:
- Model drift corrections
- Rework due to mismatch with site conditions
- Reliance on a limited number of trained users
Engineering-Driven Workflow
- Targeted scanning where required
- Point cloud processing and validation
- Engineering design effort for modifications
- Drawing and component model production
Additional benefits include:
- Reusable scan data
- No requirement to maintain a full plant model
- Faster response to site-driven changes
Benefit Comparison
Navisworks model maintenance offers strong upfront coordination, particularly in greenfield projects, but suffers from degradation over time and high ongoing cost.
Engineering-driven workflows using point cloud data provide higher long-term accuracy, faster turnaround for small changes, and better alignment with real site conditions.
Line-of-Sight Reality
Point cloud data is inherently line-of-sight dependent. This means:
- Only visible surfaces are captured
- Occlusions result in gaps in the dataset
This limitation exists regardless of software platform.
Importing a point cloud into Navisworks does not improve data completeness or accuracy — it simply presents the same data in a different environment.
Practical Example
For a minor electrical upgrade:
Navisworks Approach
- Update the federated model
- Re-run coordination
- Issue revised model
- Proceed with installation
This introduces significant overhead for a simple task.
Engineering Approach
- Review point cloud or site conditions
- Confirm clearances
- Design locally
- Install
- Update drawings if required
This approach is faster, lower cost, and aligned with how work is actually executed.
Where Navisworks Adds Value
Navisworks remains effective when:
- Multiple disciplines are designing simultaneously
- Large-scale coordination is required
- Clash detection is critical
This typically applies to:
- Greenfield projects
- Major brownfield upgrades
It should be treated as a project-phase coordination tool, not a long-term data management system.
Recommended Strategy
- Use point cloud data as the primary reference
- Maintain raw and registered datasets (e.g. E57)
- Model only critical interfaces and new work
- Use drawings for formal deliverables
- Apply Navisworks selectively where coordination is required
Final Position
In brownfield environments, value is created through engineering design and decision-making, not through continuous model maintenance.
One-Line Summary
Design what you’re changing. Scan what you’re keeping. Don’t model what you won’t maintain.
Our clients
Talk to Us – Contact Us
