VDC Engineers

31/08/2026

🏗️ DAY 4 — CLASH DETECTION IS NOT BIM COORDINATION

Many teams still assume that once clash detection is run and a report is issued, BIM coordination is complete.

It isn’t.

Clash detection identifies potential conflicts.

BIM coordination manages those conflicts through review, decision-making, resolution and closure.

Typical clashes may include:

✅ Hard clashes

✅ Clearance / soft clashes

✅ Interface conflicts

✅ Duplicate or overlapping elements

Platforms such as Navisworks, Revizto, Solibri, BIMcollab Zoom and Autodesk Model Coordination can help detect and manage these issues.

But software alone does not deliver coordination.

A professional BIM coordination process involves:

✅ Model readiness and quality checks

✅ Model federation

✅ Clash rules and tolerances

✅ Clash review and filtering

✅ Risk-based prioritization

✅ Issue assignment and ownership

✅ Multidisciplinary coordination

✅ Resolution tracking

✅ Verification and close-out

That is why:

Clash Detection = Finding conflicts

Clash Management = Tracking and controlling issues

BIM Coordination = Achieving coordinated solutions

It is also important to remember:

Not every clash is a coordination problem.

And not every coordination problem is a clash.

A model may appear clash-free and still contain problems related to:

❌ Constructability

❌ Maintenance access

❌ Incorrect interfaces

❌ Missing openings

❌ Incomplete information

❌ Installation sequencing

So the goal is not to create the biggest clash report. The real goal is to resolve the right issues early enough to reduce rework, delays, cost and construction risk.

In an ISO 19650-aligned process, coordination should be supported by structured information management, defined responsibilities, controlled workflows, traceable issue resolution and effective information exchange across the CDE.

💬 What is the bigger challenge on your projects — finding clashes, assigning ownership, or getting issues closed on time?

30/08/2026

🏗️ DAY 3 — CDE IS MORE THAN A CLOUD FOLDER

A Common Data Environment (CDE) is often misunderstood as simply a place to upload and store project files.

But in an ISO 19650-aligned information management process, a CDE is much more than storage.

It provides a controlled environment for creating, reviewing, sharing, authorizing, exchanging, using and retaining information throughout the project and asset lifecycle.

A typical CDE workflow includes:

✅ WIP — Work in Progress
Information being developed within a task team.

✅ SHARED
Information made available to authorized teams for coordination, review and collaboration.

✅ PUBLISHED
Authorized information made available for its defined project or asset purpose.

✅ ARCHIVED
Retained information records supporting traceability, audit and future reference.

A well-managed CDE also supports:

✅ Information naming and identification
✅ Revision and status control
✅ Review and authorization workflows
✅ Permissions and access control
✅ Multidisciplinary coordination
✅ Issue management and traceability
✅ Controlled information exchange
✅ Audit trails and accountability
✅ Project Information Model (PIM)
✅ Asset Information Model (AIM)

Technology platforms such as Autodesk Construction Cloud (ACC), Bentley ProjectWise and Oracle Aconex can support CDE implementation.

But remember:

The software platform itself is not the CDE.

A successful CDE brings together:

INFORMATION + WORKFLOW + GOVERNANCE + TECHNOLOGY

The objective is simple:

➡️ The right information
➡️ To the right people
➡️ At the right time
➡️ In the right status
➡️ For the right purpose

When implemented properly, a CDE improves coordination, reduces duplication, prevents the use of outdated information and strengthens project accountability.

📘 ISO 19650 Reference — 2026 Update

This post is informed by the currently published ISO 19650 series together with the 2026 Edition 2 Draft International Standards (DIS) currently under development:

• ISO/DIS 19650-1 — Edition 2: Concepts and principles
• ISO/DIS 19650-2 — Edition 2: Information management process
• ISO/DIS 19650-3 — Edition 2: Implementation of the information management process
• ISO 19650-4:2022: Information exchange — currently published

The 2026 Edition 2 documents are Draft International Standards and should not yet be referenced as published ISO 19650:2026 standards.

💬 How is the CDE managed on your projects — as a controlled information management workflow or mainly as a document storage platform?

29/08/2026

🏗️ BIM vs BIM TOOLS — THEY ARE NOT THE SAME

One of the most common misunderstandings in the AEC industry is that knowing BIM software means knowing BIM.

It doesn’t.

BIM tools and platforms support the BIM process — but they are not BIM themselves.

Tools such as:

Revit | Civil 3D | Archicad | Tekla Structures | Bentley OpenBuildings | OpenRoads | OpenTunnel | Navisworks | Autodesk Construction Cloud | SYNCHRO | FOZUR | Power BI | ArcGIS | QGIS

all play important roles in digital project delivery.

But they serve different purposes.

Some are used for authoring and modelling, some for coordination and review, some for information collaboration, some for 4D planning, and others for analytics, reporting or GIS integration.

BIM itself is broader.

Under the ISO 19650 approach, BIM is fundamentally about information management using building information modelling across the asset lifecycle.

A successful BIM process involves:

✅ Information Requirements
✅ Information Management
✅ Common Data Environment (CDE) workflows
✅ Information Coordination
✅ Model Federation and Clash Management
✅ Controlled Information Exchange
✅ Project Information Model (PIM)
✅ Asset Information Model (AIM)
✅ Asset Information and COBie
✅ Lifecycle Information Management
✅ Collaboration between project stakeholders

So the important distinction is:

BIM Tools = Technology

BIM = People + Process + Information + Technology

Software enables BIM.

But software alone cannot establish a successful BIM process.

The real value comes from defining the right information requirements, responsibilities, workflows, coordination processes and information exchanges — and then using the right technology to support them.

A BIM professional therefore needs more than software knowledge.

They need to understand how information is created, coordinated, reviewed, approved, exchanged and managed throughout the project and asset lifecycle.

💬 What do you think is more important for a BIM professional — software expertise or understanding the BIM process?

28/08/2026

13/06/2026

Key areas of expertise include:

• Information Management and Digital Delivery Governance
• ISO 19650-aligned Information and BIM Management Processes
• Common Data Environment (CDE) Administration and Governance
• Autodesk Construction Cloud (ACC), Aconex, Revizto, and Collaborative Platforms
• Information Standards, Model Auditing, and Quality Assurance
• Design, Construction, Handover, and Asset Information Workflows
• Multidisciplinary Coordination and Stakeholder Management
• BIM Ex*****on Planning and Digital Transformation Initiatives

31/05/2026

VDC ENGINEERS
Building BIM Professionals. Delivering BIM Solutions.

🚀 Your Engineering Degree is the Foundation.
🏗 BIM is the Future.

Master industry-relevant BIM skills and become job-ready with practical training, real projects, and expert guidance.

✅ Civil
✅ Architecture
✅ Structural
✅ Mechanical
✅ Electrical

📞 7995913997

💬 Comment "BIM" to receive the course brochure and career roadmap.