Forums
|
Forums >> General Discussion >> Revit Project Management >> With upgrading each year, and families not downgradeable, where to make families
|
|
|
active
Joined: Mon, Mar 9, 2009
160 Posts
 |
We did one project in RME 2009 and shortly after that, RME 2010 came out. I dont know how often the Architects will upgrade, or when. Its also quite possible that a building started in 2009 may stay in 2009, and we as PME engineers usually start later on in the project, well after the project is underway. My question is in regards to making families. If I need to make a rooftop unit family, should I make that RTU in 2009, and when complete, saveas and open it up in 2010? This way, the family can be used in both versions. What I dont want to happen is make a familiy in 2010, and need to use the family in 2009. How do others do it, or is not really that big of a deal?
|
This user is offline |
|
 | |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
 |
If you may need it or you think so ... make it in the earlier version. Most times, it doesn't matter at the time you create it - either 2010 or 2009 take the same amount of time so make it where you might need it then keep your library clean and make a 2010 in the 2010 library.
|
This user is offline |
|
|
|
active
Joined: Thu, Jan 24, 2008
193 Posts
 |
I would agree with WWHub on this. But I would like to elaborate on something he touched on. Like he said, if you need it in 2009, then make it in 2009. But if you are also going to use it in 2010, you may want to make a copy to be placed in a library just for 2010. When you bring in something for 2010 from 2009 it does a one time upgrade from the previous version. I am not 100% sure, but you may want to make a copy for the 2010 application just incase it changes the file so you would not be able to use that file in 2009 anymore. If I'm wrong then someone please correct me so as not to misinform jcrocco.
|
This user is offline |
|
|
|
active
Joined: Mon, Mar 9, 2009
160 Posts
|
Thanks both of you. Regarding the two libraries, I thought of that and had implemented two systems libraries, and that is actually what prompted me to ask the question. While I was figuring out how to do it, I thought what should I do when creating new content, so I asked the question to see what others are doing. I was originally under the impression that our clients would always be working on the latest versions. I now found out one of my clients is still in 2009 because they are having issues with jobs in 2010. This is a good point to bring up because I started to work on some content I knew I would need for this job, though I havent received the revit file yet, and started making the content in 2009. Had I started it in 2010, then what would I have done?
|
This user is offline |
|
|
|
active
Joined: Thu, Jan 24, 2008
193 Posts
|
It really does suck that Revit is not backwards compatable or even will save files to older previous versions (like CAD or any other Microsoft Office programs; just to mention a few). I guess the thing to do would be to find out ahead of time if the client would need the Revit file or if you could just print PDFs to show them. Then work with whatever version you need to.
|
This user is offline |
|
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
Not being backwards compatable is a no brainer... the result is that REVIT is not tied to the past and consequently can move forward faster , more efficiently and more compact. Regarding where to create. Our master library was in 2008 and we upgraded all those files to 2009. Any new families we currently build are now in 2009 because that is our standard for new projects now. At some time, when we know all is right with the world, we will copy/upgrade the 2009 library to 2010. But we will still have all 3 libraries!... for a period of time...
|
This user is offline |
|
|
|
active
Joined: Mon, Mar 9, 2009
160 Posts
|
I am planning on doing the same thing, as far as having seperate libraries, but the issue is that we are not the originators of the central files, rather we are users and need to follow suit. As an architect starting the background, you have the option of what program to work in. As an MEP or Structural engineer, we have to follow what the Architect is doing. If we have multiple architects possibly using different versions, and MEP content can be used on multiple jobs, then it is possible I could have an architect in 2010 where I need to make some content, and then later on the same, or another architect has a job in 2009 and the need for that content is still there. One architect in fact I was expecting the work to be done in 2010, and he said that "this job" will be in 2009 still as they are having issues with 2010. So, its possible that I could make content that may be used in multiple versions of Revit. I wanted to see how others have dealt with this situation, and if there is an alternative that I have not thought of or dont know about. If not, I think the safest thing is to draw content in 2009, and then saveas to another library and update it to 2010.
|
This user is offline |
|
|
|
Similar Threads |
|
upgrading issues regarding families and filtering |
General Discussion >> Revit Project Management
|
Thu, Jun 30, 2011 at 1:10:31 PM
|
5
|
|
Template Version |
General Discussion >> Revit Project Management
|
Tue, Apr 22, 2014 at 1:50:19 PM
|
3
|
|
Window families and revit 2011 |
Revit Building >> Technical Support
|
Tue, Jan 10, 2012 at 11:08:25 AM
|
9
|
|
upgrading from 8.1 to 9.0 |
Community >> The Studio
|
Fri, Jul 28, 2006 at 10:19:02 AM
|
6
|
|
10 New REVIT 8.1 'Families' Video Tutorials released |
Revit Building >> Tips & Tricks
|
Tue, Oct 2, 2007 at 12:39:43 PM
|
5
|
|
|
Site Stats
Members: | 1987054 | Objects: | 22874 | Forum Posts: | 152184 | Job Listings: | 3 |
|
Search