Hi everyone,
I have a quick question about an idea i implemented in Revit for our tags.
Actually our company ( engineering) is jumping onto the BIM-train by using Revit.
There are already a few projects running but people are using Revit like Autocad.
For now I'm happy they are getting their sheets out but i want to start automating things.
So for all our families ( where it makes sense) i want to implement an automated tag.
The goal is that the tags collect the information inside the family so when the modeller changes the family or the type of the family the tag will update automatically and he/she will not have to update tags when something changes in the model.
For this i made the following steps:
1) create a share parameter : "familyInfoTag"
2) add the parameter to my template to project parameters
3) create a family and add the "familyInfoTag" parameter to the family as well
4) create a new annotation Symbol - Generic Model - and create a tag. To this tag i add the "familyInfoTag" from the shared parameters.
I will repeat this process for all our families.
In my opinion this is a relative easy method to make sure tags update on change and the users can not change this information because they will not have access to modify the family itself. ( yes, they could change the family and have this in the project but this is a company-Revit-Rule: "users- the people who are responsible for the production do not create families.")
I tested it out and seems to work.
What do you think about this? Is it the way i am supposed to do such a thing or am i missing something?
thanx in advance and have a great day,
Jeff
It is not clear what the goal is. What does the "FamilyInfoTag is supposed to show?
Hi Alfredo_Medina,
thanks for your answer.
Sorry i was not clear about it, i try to explain my goal:
I wanted to find a way that the information on the tag is consistent over all our projects and independent of the person who created the project model.
So the person - probably BIM manager- who creates/manages the families adds the information that shall appear on the tag of this family or even Family type in the parameter "familyInfoTag"
for example, let's say i have a pump family with 3 different types:
Type 1 200x300
Type 2 200x350
Type 3 200x400
so inside the family each type will have exact this information in it.
In other words: the value the "familyInfoTag" has is the text that will appear on the tag.
i hope this clears it up a little
thanks,
Jeff
Thank you for the information. I still don't understand, sorry, and let me repeat my question: what is the "InfoFamilyTag" supposed to show? a type mark designation such as "A", "B", etc... ? the names of the types? what exactly?
The only issue I see here is that you now have to manage a shared parameter text file as well. Seems unnecessary when Revit have so many built-in identity parameters to accomplish what your trying to do. Can't you use one of those?
Thanks for your answers, and sorry for the late response, it seems we are in different time zones.
Actually it is not important what the tag shows, it could report some information from within the family or some customized tag.
for each family i will create the label, maybe with some options too, to be sure that all our plans go out with the same styling, independent of who createt the model.
@Anonymous I really doubt that it is possible to do optimized BIM without getting yoursefl into and using shared parameters. In the beginning it seems difficult but once you understand the idea you see the benefits of the shared parameters.
thx, jeff
I absolutely agree with you Jeff: Shared Parameters are a critical to BIM workflow, as well as, adherence to company standards and therefore must be managed and utilized with due diligence – otherwise you get anarchy.
But, they can be unnecessarily used as well. I was making the point that Revit has many built in system parameters it that could serve your needs as well. Any of us that have been using Revit for a while, have undoubtedly seen, at one time or another, 2 parameters of the same name pop up in scheduling: one a system parameter and the other a shared parameter (i.e. “Type”, “Mark”).
And then there’s the proverbially spelling mistake (e.g. a parameter used in one family named "familyInfoTag" and in another family it’s named “famlyInfoTag”). ARGHHH!
Well well well if you insist:
- Make sure you have a Shared parameter text file saved in a Revit office standards folder on a server. Your project templates and family templates should point to that text file.
- Create different parameter groups with descriptive group names (not group 1, group 2, etc...)
- Establish a naming convention for your parameters. Think about prefix so that they sort properly once get in projects.
- Remember that creating a Shared parameter is a one off. if you need to change ANYTHING you have to delete and redo it allover.
Again, I still don't understand the beef you have against OOTB family parameters. They can do everything Shared parameters do without extra work. I hope you don't confuse OOTB family parameters with user created family parameters.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.