Repeated Unit Workflow - Current best practices?

[TaylorK]

Hi All,

 

My my firm has been exploring using a BIM / Project sharing workflow for our latest project and have run into some issues with our previous repeated unit strategy. In the past we've used symbols for repeated apartment units which has worked pretty well. Unfortunately in a bim/project sharing workflow Symbols seem to have issues / bugs that keep cropping up for us.

 

Here are some of the issues.

 

• Symbols aren't aware of what story they're on and do not adjust wall heights in units to accomodate.
• Data tags cant be reliably used in units as they have issues scaling text (fixed in vw 2023) Though tags have to be put in Symbol rather than in annotation space. (See this post)
• More insidiously we've had just straight data loss, when a new working file is made walls and other object just dissappear from within the symbols (See this post)

 

My question is what is the currently recommended workflow for repeated units such as this? We have projects with upwards of 200 Units and need a workaround if we're going to continue using BIM / Project Sharing.

 

Thanks! 

[Samuel Derenboim]

I once used a really ugly method. I used a design layer viewport across multiple stories that referenced one design layer. It worked....sort of. 😂😂

 

Using this method i was able to copy portions of a design layer as well. So you if have several 'units' on multiple design layers, you can reference them in conjunction with each other on other stories. That way - you modify one - you modify all instances. note however - your schedules will be messed up! they will only count 1 design layer as the remainder are viewports. (unless you can reference them somehow independently of the design layer)

Edited August 9, 2023 by Samuel Derenboim

[TaylorK]

Yeah I was testing / theorizing something similar. Where the unit plan (internal walls, fixtures) all live on their own design layer. Then each layer is referenced in place. Seems to have some of the work arounds as you can tag things in that design layer and there aren't scaling issues or data loss. Issue is you cant edit in place and we're constantly upating walls and joining them in reference to the surrounding walls/ grids and this would be more difficult as you would need to go to the units individual design layer. Not ideal but I'll take it over data loss.

[Samuel Derenboim]

whaaaat???you can tag objects in design layer viewports?

Edited August 9, 2023 by Samuel Derenboim

[TaylorK]

Well you need to tag the on its own design layer. Then just put that tag on a class that you turn off in views you dont want it. Not sure how this would interact with scaling at the moment though.

Edited August 9, 2023 by TaylorK

[shorter]

@TaylorK Symbols cannot 'see' outside of symbol 'world' so it is not surprising this has failed.  It is a long standing wishlist item; for objects inside symbols to be storey aware.  however, be careful what you wish for because if the implementation is as bad as Revit 'Groups' it is best finding a workaround.

 

All parametric objects inside symbols are best laid manually, with no reference to layer wall height, or storey level.

 

In fact, we find it is better to place them as 2D and then create the symbol before then giving the walls height.

 

By the way, we have BIM projects in Vectorworks with well over 200 units, and do not use project sharing.

Edited August 10, 2023 by shorter

[Matt Overton]

On 8/10/2023 at 3:48 AM, Samuel Derenboim said:

I once used a really ugly method. I used a design layer viewport across multiple stories that referenced one design layer. It worked....sort of. 😂😂

 

Using this method i was able to copy portions of a design layer as well. So you if have several 'units' on multiple design layers, you can reference them in conjunction with each other on other stories. That way - you modify one - you modify all instances. note however - your schedules will be messed up! they will only count 1 design layer as the remainder are viewports. (unless you can reference them somehow independently of the design layer)

Nothing Ugly about that method. it is full of Style and grace.