headerL
headerR
Left effects
Right effects
Important Site Information:
Notice, if you are using Internet explorer to view this site, it is strongly recommended that you run it in compatibility mode or use firefox or google chrome
TopL TopM TopR
MiddleL


You are not logged in currently. If you are not already a member, please take a moment a complete our free registration (a valid email is required to verify your registration). Once you complete 2 minute registration process, you will be able to create new threads, reply to threads, rate and subscribe to threads, and much more.
If this page has helped you, be sure to give it a google "+1", by clicking the icon to the right or anywhere you see it on this page.
11/29/2010 2:40:58 AM
 
Eldon
30 Posts
Joined 09/15/2010
Entry Type:
Best Practice
Category:
Families
Subcategory:
General
Groups or Families  

Hi

We have in the past created 'Groups' when modelling multiple identical apartments in high rise residential buildings. Do you think this is the best way to do it or would we be better creating everything within the apartment boundary as a Family?

We have had issues with Scheduling, Tagging and Door Numbers.

Advice appreciated.

Cheers, Eldon

 

11/29/2010 5:30:14 AM
 
olopez
20 Posts
Joined 10/12/2010
Re: Groups or Families
In Response To:  Eldon

I've never tried a family for that but I think goups are more appropiated, works for me perfectly including tags and schedules.

11/29/2010 9:37:59 AM
 
PZ
2 Posts
Joined 11/09/2010
Re: Groups or Families
In Response To:  Eldon

Most of the firms I work with are using groups.  I am curious to know what issues you are having with the scheduling and tagging though.  Everyone has seemed to be doing fine with using groups but there are a few tricks to using them well.

You could, depending on how you are scheduling, use a linked file for the apartment units.  Many times, the interior doors and other items are driven by a type based parameter for tagging/scheduling.  Example: All 2' - 10" door are type "3" versus the entry door which may be labeled with the unit number, which would be an instance property.  The type based tagging allows the builder to simply look and see that there are 100 doors of that type for the project.  We then did mini-design packages for each unit, but can still create a total for the entire building.

Families won't work because you can't add walls - or any system family to a component family.  You could nest furniture and other types of component families though.  I think this is a slippery slope though and will add extra complications. You also don't want to use in-place families.  That is an amazing nightmare waiting to happen.

11/29/2010 9:47:38 AM
 
superJMuser
433 Posts
Joined 08/19/2009
Re: Groups or Families
In Response To:  PZ

 PZ explained it well...you don't want to use families.  Only thing I considered using families for related to multi-family residential is the kitchens.  You could, hypothetically, nest all the kitchen components into a singe family.  Benefit could be that you can use a legend for your kitchen type elevations, instead of having to elevate them with actual tags and then deal with tracking how that elevation may move around if you scoot the kitchen stuff one direction or another.

We had this problem on a few projects, and I think this could be a good way to deal with it.  Typically, our kitchen type elevations only display the kitchen with no surrounding context.  We have also sometimes show an elevation of the wall(s) the kitchen is on, for context, and then just block out the kitchen with thick dashed lines and refer to a larger, more specific kitchen elevation that has all the annotation, etc. on it.  

I haven't tried using a family for the entire kitchen on an actual project, so I am not sure what negative consequences may be related to doing it this way, but it seems like it could work well.

_______________
superJMuser
11/29/2010 6:53:21 PM
 
Eldon
30 Posts
Joined 09/15/2010
Re: Groups or Families
In Response To:  superJMuser

Thanks guys, invaluable responses as always and nicely explained :-)

We will go with Groups and let you know. I suspected this to be the case and certainly makes most sense.

Cheers, Eldon

Last Edit on:11/29/2010 6:54:09 PM
3/30/2012 7:36:06 PM
 
VDC Gorilla
12 Posts
Joined 01/03/2011
Re: Groups or Families
In Response To:  Eldon

IMO creating separate "Unit" links is not the way to go.  Files can be: ovewritten, renamed, deleted, moved, repathed, ect. Then there's duplicate files all over the folders & no-one can identify which one is most accurate. AND the link often gets placed inncorrectly in the model, one on top of another or on a different level than was intended OR on the wrong workset. 

Then there's the nightmare of updating families within all these separate Unit files.  Say you need to update a door type, you would have to open each of the Unit files & reload the family you've updated - that could take hours, whereas if you created Unit groups, it would be done in minutes, since ALL the groups will update at once.

While we're on the subject of units - I recommend that any plans that are distributed for review & markups be oriented the same as the original instance in the model. So if in the model the entry door is to the right, the plans that get printed should have the door to the right- that way it doesn't require studying a mirrored or flipped print to see if I've got the door swing correctl, or have updated the vanity.  It's just a time & aggravation saver & should be a standard practice.

Happy Reviteering!

3/31/2012 8:23:59 AM
 
Maciej
23 Posts
Joined 03/13/2012
Re: Groups or Families
In Response To:  VDC Gorilla

Very nice intro.

Last Edit on:4/2/2012 10:58:36 AM


You must be a registered user to Rate entries.  Please take a moment a complete our free registration (a valid email is required to verify your registration).


You must be a registered user to Subscribe to individual entries.  If you would like, you can subscribe to all future new posts and/or replies by filling out this form.  Otherwise, take a moment a complete our free registration (a valid email is required to verify your registration).

Below is a list of things to be aware of when browsing through the Revitinfo.com Forum:

 1)  As a registered user at Revitinfo, you automatically are signed up to recieve emails any time a new post or reply to existing post is made. You can change this setting while logged in under your User Profile by clicking on your user name at the top right of any page, next to the Date (or by clicking on the My Profile Button on any Forum Page). Once you get here, click on the "Edit Profile" link below your Quick Profile Information. Finally, select "Manage Profile" and scroll down the the very bottom to change your forum email subscription Settings. 

 2)  Each Entry must have an assigned Category and EntryType.  Not all categories have subcategories, but if the category you pick has subcategories, please pick the most appropriate for your entry.

 3)  Only registered, logged-in users have the privledges to create posts, reply to posts, and view attachments of posts.  Registration is free, and like any other forum, is our way of increasing forum functionality and security.

 4)  As a registered user, you will also have the ability to subscribe to threads individually, rate them, and view a list of your posts.  You can also edit posts that you have made.  Also, as a registered user at Revitinfo, you automatically are signed up to recieve emails any time a new post or reply to existing post is made. You can change this setting while logged in uder your User Profile by clicking on your user name at the top right of any page, next to the Date. Once you get here, click on the "Edit Profile" button below your Quick Profile Information. Finally, select "Manage Profile to change your profile Settings.

 5)  Soon, there will be a way for users to request other categories/SubCategories via a request form.  Currently, for our system to work the way it has been designed, the category and subcategories as well as EntryTypes must remain a standard for all users of the site, in order to make searching/browsing information faster and easier.

 

Copyright Notice:  Autodesk: Revit is a product that is wholly owned by Autodesk. Any reference to Revit, Revit Architecture, Revit MEP or Revit Structure on this site is made acknowledging this ownership. Refer to Autodesk's own web site and product pages for specific trademark and copyright information. Autodesk represents a great many products and every attempt will be made to respect their ownership whenever one of these other products is mentioned on this site.


MiddleR
BottomL BottomM BottomR