mostapha
(Mostapha)
January 28, 2025, 7:23pm
6
Hi @milog , great stuff!
milog:
To speed up the workflow, I visually inspect the floors in Revit (or pdf floor plans issued from Architects), identify the unique ones, and only process those specific floors with the Revit plugin. Once cleaned up and exported as a hbjson into Rhino, I then copy and paste the duplicate floors, prefix room names with the floor level, to ultimately generate a full-scale building energy model for TM59 analysis, daylighting, PHPP, etc.
Just so you know, you can do all the copying inside the Model Editor, and before going to Rhino.
milog:
Ideally architects just provide a schedule of unique floors, but often this isnt explicitly available, and we need to determine this ourselves. Would it be possible to implement a tool in the Revit Pollination plugin that detects uniqueness across multiple floors? For example, grouping floors into groups based on identical (with some tolerance…?) room geometry (e.g., plug in detects Levels 1-10 are identical, Levels 11-14 etc…)
This could be a very interesting utility that I never of. In theory, we can use a similar workflow that we currently use to compare the same level of different models for comparing the levels in the same building.
The main challenge is that you will still need to export the rooms to be able to compare them. What do you think about this, @chriswmackey ? This will probably be much easier to do once we implement the new workflow to speed up the process of exporting the rooms from Revit to Model Editor.
milog:
I have found the ability to export the windows seperately, and then the shades, and then finally the rooms as 3 seperate steps, a nice way to breakdown the workflow which makes it more manageable for such large models. So that feature in the plug in is definitely a time saver. I then import these three seperate hbsjon files, and use the snap to grids to snap the windows to the facade line which we extract from the room outlines very quickly.
Nice! You are ahead of us here. I’m glad that this approach is working for you in the Rhino plugin! We plan to provide a similar workflow in the Model Editor so you can accomplish the same without the need to use the Rhino plugin.