IFC ProvisionForVoid in Revit - Open vs. referencing / binding

Slot and breakthrough planning often involves working with ProvisionForVoids, which are usually exported as separate IFCs. But what is the best way to read such an IFC into Revit in order to actually be able to use or edit the breakthrough bodies as deduction objects and to see the relevant properties?

If the IFC is only referenced, the breakthrough elements are visible but cannot be intersected with the elements in the current file.

The most obvious idea is often to open the IFC in Revit, but this is not always optimal - a separate type is created for each breakthrough and relevant properties are read in as type properties:

If the IFC is first referenced in Revit and then "bound", the result looks like this:

All relevant properties are available here as specimen properties and the breakout bodies can be intersected directly with the components.

It should be noted, however, that in this case it is not possible to simply update the original file in the event of changes, as would be the case with a link. However, since I recently received this question and only found out about the behavior through testing, I thought this tip might also be of interest to some of you.

In any case, it depends on the workflow which approach makes the most sense - in practice, the coordination of openings is often handled by special tools and plugins that also automatically intersect the geometry. You can find out more about various workflows and approaches in RUG DACH's great guide to slot and breakthrough planning: https://www.rug-dach.de/download/durchbruchsplanung.html

What does your workflow look like?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Previous Article

APS Bootcamp

Next Article

Export Revit phases to IFC