People's reactions to Revit never cease to amaze & amuse me - with the variety in opinions, excitement, reservations, expectations and more all making my job as equally taxing as it is enjoyable. And this week's "big thing" has been the best in a long one...
For whatever reason, it's taken us 6 projects to get into using Keynotes - (don't ask
) but with the NBS specification software now featuring a direct keynote export functionality I demanded we test it out. And within seconds the coos and boos started up.
The coos : Obvious. Automated annotation/tagging linked to the spec.
The boos : Dismay. That you couldn't have a window frame keynote AND and window glazing keynote read the same family*.
*Until now, we've "solved" the above issue with using shared parameter text fields for both, but that's always been dependent on manual tallying to spec.
But of course, I'd like to defend (and advocate) continued use of keynotes - but I've come up short. Tagging shared hosted-families is a given, and individual schedules quite do-able - but one that combines these, (essentially the "want" from our Revit-dissenters) - as attached - has so far defeated me.
...Additionally, what I'm struggling to figure out is how to even approach this (modelling wise) with windows. With door assemblies (made from panels, frames & ironmongery families) there's quite a clear approach - but what of glazing panes? Are they each instance controlled shared nested families?!?
:crazy:
For whatever reason, it's taken us 6 projects to get into using Keynotes - (don't ask

The coos : Obvious. Automated annotation/tagging linked to the spec.

The boos : Dismay. That you couldn't have a window frame keynote AND and window glazing keynote read the same family*.
*Until now, we've "solved" the above issue with using shared parameter text fields for both, but that's always been dependent on manual tallying to spec.
But of course, I'd like to defend (and advocate) continued use of keynotes - but I've come up short. Tagging shared hosted-families is a given, and individual schedules quite do-able - but one that combines these, (essentially the "want" from our Revit-dissenters) - as attached - has so far defeated me.
...Additionally, what I'm struggling to figure out is how to even approach this (modelling wise) with windows. With door assemblies (made from panels, frames & ironmongery families) there's quite a clear approach - but what of glazing panes? Are they each instance controlled shared nested families?!?

Comment