Archispeak Episode #354 - "Fighting Revit"

Hosts: Evan Troxel & Cormac Phalen
Release Date: December 9, 2024
Description: In this episode, Evan and Cormac delve deep into the challenges and frustrations of working with Revit, one of the industry's leading Building Information Modeling (BIM) software. They explore the inefficiencies caused by large models, the impact on productivity, and discuss potential solutions to streamline workflows.

1. Introduction to the Episode

The episode kicks off with a light-hearted conversation about the hosts' new dog and their attempts to curate the perfect playlist for him. This segment sets a relaxed tone before transitioning into the core topic of the day—Revit and its associated challenges.

2. The Main Frustration: Revit's Inefficiency

a. Exporting Challenges

Cormac shares his recent experiences with exporting PDFs and CAD files from Revit, highlighting the time-consuming nature of the process.

• Cormac:
  "[04:43]... It takes about 20, 25, 30 minutes just for the CAD export. They were locked. It was constantly locking up the Revit."

Evan questions the necessity of exporting CAD files when models are already being shared, prompting Cormac to explain the client's specific requirements.

• Evan:
  "[21:26]... What would they do with the CAD that they can't do with the PDF?"

• Cormac:
  "[21:39]... They're using it for some basis of shops or something."

b. Impact on Productivity

The prolonged export times significantly reduce productivity. Evan emphasizes the hidden costs associated with these inefficiencies.

• Evan:
  "[44:21]... You can't do anything else."

• Cormac:
  "[52:18]... If you're billable at 40 hours a week, you're really technically only working 30 hours because you're waiting on your machine and the software hardware."

c. Model Size and Complexity

Cormac discusses the massive size of their Revit models, citing a single model at 2.2 gigabytes, which exacerbates the export delays.

• Evan:
  "[30:31]... it's in the cloud, I assume it is."

• Cormac:
  "[30:40]... One model was 2.2 gigs."

3. Root Causes of Revit Frustrations

a. Model Setup and Organizational Decisions

A critical point of discussion revolves around how the initial setup of Revit models can lead to inefficiencies. Cormac reflects on past decisions to consolidate multiple buildings into a single model, which now hinders performance.

• Cormac:
  "[31:04]... We have eight buildings and it should have been eight different models because then it would have been a little less cumbersome."

• Evan:
  "[37:54]... I cannot believe you guys decided to put multiple buildings in one file."

b. Version Compatibility and Software Constraints

The team struggles with maintaining model compatibility across different Revit versions, leading to further complications and inefficiencies.

• Evan:
  "[24:03]... One of the features of 2025..."

• Cormac:
  "[25:02]... it was far more efficient in the more current versions, but I can't upgrade them any further than what the client has."

4. Potential Solutions and Strategies

a. Hardware Upgrades

Evan advocates for regular hardware upgrades to improve Revit's performance, emphasizing the return on investment through increased productivity.

• Evan:
  "[48:14]... Faster computer makes a measurable difference that is totally peanuts compared to your billable rate."

b. Virtual Machines and Cloud Computing

Discussing advanced solutions, Evan introduces the concept of virtual machines to handle large Revit models more efficiently.

• Evan:
  "[54:04]... A virtualized machine is literally logging in and using a computer that sits somewhere else. It could be in a data center, making processing much faster and reducing downtime."

c. Model Segmentation

Cormac agrees that segmenting models by individual buildings could alleviate many of the issues they're currently facing.

• Cormac:
  "[32:28]... It should have been eight different models... that was the mistake."

5. The Hidden Costs of Poor Workflow Management

Evan and Cormac highlight the often-overlooked costs associated with inefficient Revit workflows, such as lost billable hours and increased project timelines.

• Evan:
  "[50:03]... A faster computer makes a measurable difference..."

• Cormac:
  "[52:00]... If you're billable at 40 hours a week, you're really technically only working 30 hours."

6. Notable Quotes

• Cormac (04:43):
  "It was taking like 20, 25, 30 minutes just for the CAD export. They were locked. It was constantly locking up the Revit."

• Evan (21:26):
  "What would they do with the CAD that they can't do with the PDF?"

• Evan (44:21):
  "You can't do anything else."

• Cormac (52:18):
  "If you're billable at 40 hours a week, you're really technically only working 30 hours because you're waiting on your machine and the software hardware."

• Evan (54:04):
  "A virtualized machine is literally logging in and using a computer that sits somewhere else. It could be in a data center, making processing much faster and reducing downtime."

7. Conclusion and Reflections

Towards the end of the episode, the hosts reflect on the lessons learned from their struggles with Revit. Cormac expresses regret over past decisions and emphasizes the importance of adapting workflows to better suit the demands of large-scale projects.

• Cormac:
  "[58:28]... I feel the blame."

Evan reiterates the necessity of leveraging technology and efficient workflow management to mitigate the challenges posed by complex Revit models.

• Evan:
  "[57:21]... Our people are our differentiator. They can work faster."

8. Final Thoughts

"Fighting Revit" serves as a candid exploration of the real-world challenges architects face with BIM software. Through their personal experiences, Evan and Cormac shed light on the inefficiencies within current workflows and advocate for proactive solutions to enhance productivity and project outcomes.

Join the Conversation:
To continue the discussion or learn more about the hosts, visit archispeakpodcast.com.