top of page

Is VDC what BIM was intended to be?

Writer: liam birkett
liam birkett
Nov 10
4 min read

Updated: 7d

Around seven years ago, in the New Zealand design office I worked in, the phrase "BIM" became common speak. We weren't draughtsmen (or draughtswomen) anymore; we were "BIM modellers" or "BIM coordinators". All of a sudden there was a BIM manager strutting around in a three-piece suit. We didn't know what he did, and we didn't really know exactly what BIM was or what it meant for us. Obviously we associated BIM with Revit, information quality and model coordination, but we didn't yet associate it strongly with information management in the way we do today.


Around three years ago (2023), I moved to the UK and switched from the design side to the construction/contractor side. The UK, at least on large commercial projects, was clearly more "BIM mature" than New Zealand. The RIBA framework was in place, ISO 19650 was generally accepted and adopted, and clients would usually give some direction on their appetite for "BIM" on their projects. Now it was the client's BIM consultant wearing the three-piece suit, copy-pasting excessively long EIRs, which the contractor's BIM manager would copy-paste right back at them as a BEP.


I found construction in the UK particularly bureaucratic. "BIM" was touted as a solution to rising construction costs and the decline in building quality. The golden thread arrived and was woven in under the BIM umbrella. BIM managers were now information managers. Ensuring the CDE was set up and used correctly was half of the BIM manager's job. The other half was coordination meetings and sending out questionable clash detection reports. It was a good day for the BIM manager if they managed to spin around in Revit for a while.


More recently it has felt like the role of the BIM manager (and the purpose of BIM) is changing again. The BIM model has become a deliverable and a potential programme blocker. On large projects you don't build until the model has been coordinated and approved in 3D. Having the models at the centre of the project is great, but it means the focus of BIM has shifted into design management. It's less about the process and more about the quality of the 3D information. BIM managers are chasing engineers for design rather than looking after the standards and processes behind it. In turn, project managers are chasing the BIM manager rather than the designers. Information management is still under the ever-broadening BIM umbrella, but an army of document controllers and overpriced CDEs are largely taking care of that now.


So, adding up the versions of BIM I've worked in, I would say that BIM is now "the process of managing digital design and construction information". Which is an incredibly dull and broad statement.


So what is VDC? It's the new kid on the block. It might be everything that BIM was supposed to be. VDC stands for Virtual Design and Construction. I consider VDC to be "the implementation of virtual tools and digital construction hardware within the construction process". I appreciate that isn't a particularly artful description, but it's better than Autodesk's: "Virtual Design and Construction (VDC) is a type of technology that creates digital models of buildings and project sites." (Link)


If you google VDC, you'll find what I consider to be narrow-minded descriptions of VDC as the use of 3D–6D models during construction. To me, the models are the backbone of VDC, but the real project value is in what I would call digital construction hardware: laser scanners, drones, 360 cameras, GPS-enabled plant and so on.


Then there's the software. We're seeing a wave of new and exciting platforms, many of them AI-powered. I can't open LinkedIn without getting punched in the head by a DroneDeploy post. Cupix and OpenSpace both have excellent 360 capture platforms, and Trimble continues to excel with its survey workflows, particularly around GPS-enabled plant for earthworks.


Hardware costs are coming down. A drone now costs less than the software to manage its data, terrestrial laser scanners are being replaced by more affordable handheld scanners, 360 cameras are durable, and the Insta360 X6 largely resolves low-light issues. The software subscriptions are now the barrier. Getting a small contractor to spend NZ$50k on three more annual software subscriptions is a big ask, even if you know the ROI is there. But if I can vibe code a photogrammetry processor and viewer, then surely these subscription costs will have to become more competitive?


In my opinion, VDC will be the wave that carries us past caring so much about bureaucratic BIM processes. In my VDC and BIM utopia, the designers will start the models. The contractors will take them over and fix them. The models will feed into the digital construction hardware. Reality capture tools and AI checks will validate what has been installed. No longer will we spend our days asking site engineers to re-upload documents to Aconex with correctly formatted file names. The VDC manager will rule their corner of the site office (wearing hi-vis rather than a three-piece suit).


So, to relate back to the title: is VDC what BIM was intended to be? Was BIM supposed to be the information management process? Or was it expected to be the implementation of digital workflows on site? My take is that BIM was always intended to be the use of digital tools from concept through to operation, but along the way it got lost in the paperwork.


Let me know your opinion in the comments.



Whats is VDC .vs BIM?

 
 
 

Comments


bottom of page