Staying Current

[antman]

Personally, I like the fact that everyone has to be on the same version to collaborate with Revit. What I've always done (since AutoCAD R14 and Revit 2010) is to upgrade as soon as the new version is released, and have never run into serious issues from doing so. There are those who disagree with me, and there is already talk of not installing Revit 2013. I'll list below my points in the case for upgrading. Anyone have more to add, or any arguments against keeping current? Keep in mind we are on subscription, so the financial side is already taken care of.

New features/enhancements list.

No need (or ability) to convert from various file versions.

Reduced learning curve. This one is a big deal. I have trained people in transition from plain AutoCAD 2004 to ACA 2008, and it was a major hurdle for many. As a side bonus, it should keep people from getting stuck in a set way of working (I know some who still use a puck/tablet).

Is it feasible to work in *only* the current version? That is, how common is it to have projects in previous versions to accommodate consultants who aren't upgrading? We have even written upgrade policy into our contracts, but I don't want to miss out on projects just because of which version of Revit is being used.

[MikeJarosz]

While I was with a large firm, we had lots of custom programs and scripts. Upgrading to a new version meant testing every program. Eventually we settled on a schedule that skipped every other release.

I know people still working on Acad 2005. They have 2011 on their machine but won't use it because it's "so different".

I've told them I hope the job you're in lasts forever, because if you go hunting with only 2005 on your resume, you're going to end up flipping burgers.

[antman]

While I was with a large firm, we had lots of custom programs and scripts. Upgrading to a new version meant testing every program. Eventually we settled on a schedule that skipped every other release.

Our AutoCAD is highly customized and scripted as well, and that makes me extremely happy about how easy Revit is to upgrade (for now...).

[dkoch]

Unless your firm always holds the primary contract and you can dictate which version of Revit is to be used and when existing projects must upgrade to all other team members (or if you provide all services in-house, and never have outside consultants or other team members), it may be difficult to to have all projects in your office always on the same (current) version.

I believe my firm is starting new projects in 2012 (provided the project does not need to be done in a previous version based on agreement with other parties), but I am wrapping up a project that started in 2009 and migrated to 2010 and now 2011 over the course of the project. Unless the Owner asks for the final deliverables in 2012, I do not anticipate migrating the project to 2012 at this point. There are several other projects that were started in 2011 and will likely remain there. Our computer support folks are expecting to have to support multiple versions on an on-going basis.