BIM. VDC.
Let’s bring it
back to the job.

Picture the space above a ceiling.

Your pipework has to fit around ductwork, cable tray and structure. There needs to be room to install it, support it and reach the equipment later. Before anyone starts cutting material, the team needs to work out how it will all fit.

In this illustrative example, the trades bring their models together. They review a tight crossing, agree a route and update the information. The shop then needs to know what can be made, while the site team needs to know what arrives first and how it will go in.

You may hear that work called BIM, VDC or both. Understanding the terms helps you follow the conversation and ask what is actually expected of your trade.

First, the building and its information: BIM.

BIM stands for Building Information Modelling. Think of the model as a way to connect what an item looks like with what the team needs to know about it. For a pump, that might include its location, connections, equipment reference and maintenance information, depending on the agreed use.

The 3D view helps people see the work. The information behind it helps them check, organise and use it. BIM also includes how that information is created, shared and managed through design, construction and operation. [1][11]

Then, the team and the way the work gets done: VDC.

VDC stands for Virtual Design and Construction. Stanford’s framework brings together three things: the product being built, the organisation doing the work and the process used to deliver it. The team uses them together to work towards agreed project and business goals. [5]

Back at our ceiling, the conversation now includes the modeller, foreperson, shop and planner. Can this section be assembled off site? Can it get through the opening? When must the route be settled? Who needs to make that decision?

These are connected ways of working. BIM has a broad scope, including collaboration and information management. VDC brings particular attention to how the building, people and delivery process perform together. The boundaries can overlap, which is why a project should explain how it uses each term. [5][11]

One job. Connected information and decisions.

Why the same software appears under both names.

A trade modeller might use Revit to develop the model and Navisworks to review it alongside other trades. Those tools can also support a team working under a VDC approach. Autodesk lists Revit, Navisworks and AutoCAD within its VDC offering. [13]

So if the screen looks familiar, that makes sense. The software may be the same while the purpose of the meeting, the information being reviewed or the people making decisions changes.

For our mechanical example, a coordination review asks whether the services fit. A planning review could use the same model to discuss which assemblies go in first. Both use building information; the second also connects it to the delivery sequence.

How we got here.

The story goes back well before today’s software. Researchers were already exploring how to keep drawings, geometry and building information connected in the 1970s. Over time, those ideas developed into modelling methods, shared terminology, training and standards.

BIM and VDC emerged from that wider development. The sources show research, software companies and construction teams contributing along the way. They do not establish a simple handover where designers owned BIM and contractors renamed it VDC.

1. 1974

   The idea starts with connected information.

   Charles Eastman and colleagues described a Building Description System that held geometry and properties, produced drawings and supplied information for analysis. The problem was familiar: keeping separate drawings and information consistent. [1]

2. 1986–1992

   One building, several ways to understand it.

   Robert Aish described connecting drawings, 3D views and attributes in 1986. Van Nederveen and Tolman explored how different disciplines could work with their own views of shared building information in a 1991 conference paper and a 1992 journal article. [2][3][4]

3. 2001–2002

   BIM and VDC become names people recognise.

   Stanford researchers Kunz and Fischer date their introduction of VDC to 2001; a co-author’s bibliography records a VDC conference paper in 2002. That same year, Autodesk promoted BIM and Jerry Laiserin called for a common BIM term across software vendors. [5][21][6][7]

4. 2003

   An early Canadian scanning example.

   In a later interview, EllisDon’s Thomas Strong recalled using 3D scans on the Art Gallery of Ontario project in 2003. Existing conditions were becoming part of the digital work, too. [20]

5. 2008–2009

   Teams, training and practical guidance grow.

   EllisDon’s account dates its VDC group to 2008. The Canada BIM Council also formed that year, and Stanford began its VDC certificate programmes. Penn State released its first BIM Project Execution Planning Guide in October 2009. [20][18][8][9]

6. 2012–2013

   The methods and exchanges become more defined.

   Kunz and Fischer’s 2012 working paper explains VDC through the product, organisation and process. In 2013, IFC4 and ISO 16739 reached publication milestones, supporting a defined way to exchange building information between systems. [5][10]

7. 2018–2024

   Information management gains a common reference.

   ISO 19650-1 was published in 2018, covering information management across an asset’s life. A Canadian adoption followed in 2024 as CAN/CGSB/CSA-ISO 19650-1:24. [11][12]

8. 2025–2026

   Canadian examples bring the ideas together.

   NRC’s now-closed 2025 retrofit research call included scan-to-BIM and asked applicants to measure results. PSPC’s 2026 Centre Block account shows a VDC role and a BIM team working together with scans, models and asset information. [17][19]

These are selected milestones, not a claim about the first use of every term. The 2001 VDC origin and EllisDon’s early dates come from later accounts. The source notes below explain what was reviewed.

Follow the story into Canada.

Canadian construction teams were exploring these ideas long before the recent Centre Block example. EllisDon’s published interview recalls scanning work on the Art Gallery of Ontario project in 2003 and the establishment of its VDC group in 2008. The Canada BIM Council, now Building Transformations, also dates its formation to 2008. [20][18]

Centre Block gives us a useful view of how the terms meet on a real project. In PSPC’s May 2026 account, a VDC manager leads the project’s BIM team. Scans, photographs, existing records and drawings help build the digital representation, while models and a database support tracking and asset information. [19]

Here, BIM and VDC sit together in the same project story. The terminology has an earlier history; Centre Block shows a later application. The sources do not trace the exact route by which the term reached that project.

Scanning and handover can sit under either label.

A scan can help a team understand existing conditions before modelling new work. Later, information about installed assets may support the owner’s records. PCL describes reality capture and turnover within its VDC practice, and EllisDon lists Scan-to-BIM and asset handover among its VDC services. These are the companies’ descriptions of their work. [15][16]

At Centre Block, PSPC also describes an intention to use the model for future maintenance. That is a planned use, rather than evidence of a completed operational handover. For a trade, the practical question is what information the receiving team needs and how they will accept it. [19]

You do not need to learn every term at once.

Start with the work your trade is being asked to do. Then find the guidance that supports it. There are established references behind these methods: Stanford has taught VDC through certificate programmes since 2008, Penn State provides BIM execution-planning guidance, and ISO 19650 addresses information management, with a Canadian adoption of Part 1 published in 2024. [8][9][11][12]

Each helps in a different way. Training helps people learn the method. Standards provide a common reference. A project execution plan explains how the team intends to work together. Your project still needs to identify the deliverables, responsibilities and checks that apply to your scope.

For model exchanges, agree the format and version as well. IFC is a standardised way to exchange building information, but the team still needs to check that the required information arrives correctly in the receiving software. buildingSMART maintains the specification and version records. [10][14]

When another new term appears, use the same approach: ask what it means, where the method comes from and how your team will learn and test it. A clear explanation and a small working example can make the requirement much easier to understand.

Five questions for your next job.

These are BIMTA’s practical questions for turning the terminology into work you can understand, plan and price.

01What will we use it for?

Coordination, quantities, prefabrication, installation or handover? Start with the task and the person who needs the result.

02What do we need to produce?

Agree the model detail, information, format, software version and delivery dates. Ask for an example of an acceptable result.

03Who checks it and releases it?

Identify who makes decisions, checks the work and authorises the next step. Coordination acceptance and fabrication release are separate responsibilities.

04Where is the effort in our price?

Allow for setup, modelling, meetings, checks, revisions and handover. Use the permitted bid-question and change processes when the requirement is unclear or changes.

05How will we know it helped?

Try a representative piece of work. Count preparation and corrections as well as the time saved in the shop or on site.

The reading behind the story.

Edition 1.1 · 19 October 2026. The mechanical example, infographic and practical questions are BIMTA learning material. Historical and Canadian examples link to the sources below. Company accounts describe their own practices; they are not independent proof of savings.