Suggestion for easier workflow in revit families

[sefanja-verkaik]

Dear community,

The following problem occurs alot for me. In my use of Revit I like to create alot of Revit families. This avarages out to almost 2 or 3 families per day.

My following problem is that I have a family template for windows for example and I make loads of window families from it. This template has way more parameters than I usually need, so that I just have to remove the parameters to create a new window family. The problem is that deleting is those parameters is alot of work. It would save alot of time to just be able to use the "windows delete" button to do this and give it a enter to finish.

I know that it is a very small issue, however because I believe it to to be as easily solved I thought I post it to the forum.

Kind regards,

Sefanja

PS: Here is an example, everything inside the red boxes needs to be deleted.

[RDAOU · Accepted solution]

@sefanja-verkaik 

I do not model families but I can tell you that the templates we distribute to Consultants and Contractors do not have that much parameters. The templates are kept basic and contain only the common parameters used in all variations. All additional/other parameters are pushed from an excel file to families 

Best way for you is to keep it simple...since you model 2-3 families a day and by now you should have modeled several hundreds of windows; therefore, you should be able to categorize them and create simplified templates for each category...and instead 1 window template, set up 3 or 4 templates based to the complexity and function of the family.

[RDAOU]

@sefanja-verkaik 

Looking closer at the snapshot you added to your original post...Lots of these parameters do not need to be in the family. 

Lots of times I see users stacking all sorts of parameters in the family when such parameters can simply be Project Category Parameters added to the Project Template. Look at it from the following perspective:

• In the Family:
  1. if Parameter is required to define specific types
  2. if Parameter needed to control/drive other family parameters or Geometries (dimensions/finish/material/nested components) 
  3. if Parameter is required to be predefined
• In the Project:
  1. if Parameter reflect specific information which are project specific 
  2. if Parameter does not not required to be predefined and is usually set in the project (on the go)

Example: I have seen on several projects consultants/contractors adding all Ironmongery/hardware/Accessories selections into the family either as a Y/N or text parameters. And such families are loaded with a 100 parameters which are basically blank and only to be decided in the project.

I wouldn't say that is bad practice but definitely unnecessary and can be substituted with (for instance) 1 parameter and a key schedule in the project

[sefanja-verkaik]

Hey Bradley,

Thanks for the support, however the parameters are actually required for the type of the family. They devine wether or not a window is location inside the frame, and each specific square inside the window can be therefor adjusted.

The template also need imrpovements however the more templates I have the more templates I need to update in order to upgrade my families.

My apoligize for making it so complicated. The window can be manipulated to fit different layouts.  5 squares under 5 sqaures above. For me it would be to much work to make a new family for each and every type. So I have multiple types possible in 1 family and than make new families for different layouts. So like the first one is 1 left 2 right and than also for windows that open up outward etc.

Kind regards,

Sefanja

[XXalessio.amodioXX]

Juyst prepare a new family.

[RDAOU]

@sefanja-verkaik 

You are the one modeling so you are the one who decides if they are required or not. I was just saying to simplify you need to consider the IF really required, where are the required  and whether they are required at all...example: instead of all those y/n parameter did you consider a 1x Family<type> label and generate the variation in the nested component...

The way it looks, you are mixing between Parametric families and a window generator app like those you get from manufacturers. Personally before going down that road I would consider the following:

1. What good would all of these types serve if ion my project I will be using only 1 or 2 types?
2. The more one complicates the family the worse it gets when it comes to modifying/updating/troubleshooting
3. It is easier to manage 20 simple families than managing 2 overly complicated ones

And last but not least, has the end-user who is placing and working with these families been taken into consideration? Would she/he need a training course to know how to set up the right window configeration with all these y/n?

[sefanja-verkaik]

My current knowledge of Family <type> has struggle implementing it correctly in my families. However I have thought of trying this out. Would simplify the families by alot. I think it would be good for me to try this out.