Forums >> Revit Structure >> Technical Support >> Shared or Project Parameters?
|
|
active
Joined: Fri, Apr 17, 2009
30 Posts No Rating |
Could someone please help me understand, beyond tagging ability, what the difference is between using project parameters and shared parameters. Does it make sense to create all parametrs as shared parameters in an office wide standard file? From everything I can see This seems to make the best sense. The parameters would be available in all RVT and RFA file - unless I am missing something. Thanks in advance.
|
This user is offline |
|
|
|
site moderator|||
Joined: Tue, May 22, 2007
5921 Posts
|
directly from the HELP menu:
-----------------------------------
I Hope and I Wish to LEARN more, and more, and more.... REVIT |
This user is offline |
|
|
active
Joined: Fri, Apr 17, 2009
30 Posts No Rating |
I have read the help file and several tutorials ect.I understand the basic difference. My question is related to project management and best practices when it comes to shared parameters. Project parameters can be shared between projects using the 'transfer project standards'. (The help filkes don't mention this) That makes the differences between the two less signifigant. On the project I am working on, I have downloaded several door families from this website. For scheduling I need to add about 8 parameters to theese families, 2 of them require tagging abilitity. I made the 2 that require tagging shared parameters. If I then make them and the other 6 project parameters, in one exercise these parameters are added to all of the door families loaded into the project. This seems to be the most efficient. But the 6 non-shared parameters are not in the family files if I open them. Alternatively, I could make all 8 parameters shared parameters. I then have to load them and create them in each of my door families. This is much more time consuming. From a standarization standpoint both approaches offer standardization. Certainly the sharedparameter process is more organized withe the parameter grouping. The shared parameter process is more consistant is all parameters are entered that way versus creating those for tagging as shared and non-tagging as project based. To me the fundamental question is do you apply parameters to families on the prject sude or on the family side.I have gotten the impression from other posts that in some facility management and specification software that runs along side Revit, works better with the shared parameters. The question is wich method is best.
|
This user is offline |
|
|
active
Joined: Wed, Nov 14, 2007
2 Posts No Rating |
I am researching the same thing right now. I am finding that shared parameters are a great way to keep it organized and such but am finding that it will be extremely time consuming to edit all the families we have in our library: ones that come with Revit, ones that have been downloaded, created,....it becomes very overwhelming. I am trying to create a template/standard for our office. If anyone has suggestions, I am open to them.
|
This user is offline |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
Go slow.... Until you really understand what you need, don't jump into this. Most stock REVIT families come with everything you need that should be shared. RC or manufacturer families are unknows. You need shared for tags and for data that needs to be exported. We keep saying that REVIT requires you to think ahead.... This is one of those places where you should think ahead but you really can't until you really understand this process. You need to get some use under your belt.
|
This user is offline |
|
|
site moderator|||
Joined: Mon, Jan 12, 2004
2889 Posts
|
I disagree, I think its a really good idea to think about this in advance. I do recommend that you consult a revit expert though to ensure you don't "over do it". Whenever I do an implementation I always look into what is required as an output, and also what further is desired but isn't achieved because it was previously too difficult. There are API plugins available that automate the process of adding shared parameters across many families at once...
-----------------------------------
Regards,
Chris.
Co-Founder | BIM Consultant | Software Designer  B. Arch)
Xrev Revit API Addins | Revit Rants |
This user is offline |
View Website
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
Chris, I guess I said that badly. I am saying that they need to understand the process before the jump into modifing families adding shared parameters they may not need. Before they do that, they do need to think ahead but this requires a through understanding.
|
This user is offline |
|
|
active
Joined: Wed, Mar 12, 2008
322 Posts
|
BUMP Just read this post- I as well need help with project parameters. I have experience with shared parameters, but not with project parameters. I guess what I'm hoping for is the ability to control certain parameters within my project in a universal fashion. What I don't understand is how to correctly apply and control the project parameters. Creating them- I think I got it. But applying and controling is more difficult. Controling them- How? With a beam or column, you just select the element and either change the type or the parameter as required. Fine and fair- easy peasy. What about project parameters. Here is what I want to accomplish. I have an .rfa family. I intend to use this family multiple times within a project (and on multiple projects), but one of the dimensional parameters is going to change depending on the project criteria. So, how do I utilize project parameters to leverage project information in a way that is more parametric. How can I link this .rfa family parameter with my project parameter? How do I control it once it is linked? I have the F1 key, so please do not direct me to the help menu. I need a concrete example of how to do it. Or, point me to an example in the out-of-box templates. Any help is appreciated- even if it's just plan text explaining principles. Thank you in advance. Is my goal unattainable?
|
This user is offline |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
I think the fact you got no snswer is your answer but I can give you some information. Project parameters don't / can't control anything. They are just added to families at the project level for scheduling purposes. From the HELP: "User-defined fields .... are specific to the project and cannot be shared....<used> in multi-category or single-category schedules." Family parameters can be shared or not and they can control parametrics of a family. Shared parameters can be used across multiple projects and familes. Could shared parameters be used to drive familes? Yes - they already are. Look at type tables. Can they be used at the project level?... You may be able to write an app for this - way beyond my scope.
|
This user is offline |
|
|
active
Joined: Wed, Mar 12, 2008
322 Posts
|
Thank you for the response... So in essence- project parameters are kind of like in-place families; they are specific to the project they live in, and cannot be extracted for use in other projects. How dissapointing. Sad face.
|
This user is offline |
|
|
|
active
Joined: Wed, Mar 12, 2008
322 Posts
|
But wait. Here is what I was thinking, and please let me know if my thought process is not in-line with a feasible solution. I am very bad with Revit schedules. Couldn't you create a schedule which has this parameter (and maybe it doesn't even need to be a project parameter) and control the value on a project-basis through the schedule? Is it possible to filter all instances of this parameter into a single column/row and control universally? I'm trying to push the I in BIM here, where information is represented throughout the project.
Edited on: Tue, Jan 19, 2010 at 7:09:21 PM
|
This user is offline |
|
|
|