Sunday, August 14, 2011

Question for those with projects spanning multiple versions of Revit... What strategy has been employed - (1) Upgrade to the latest (assuming all participants are willing/able) or (2) pick a version and stick with it for the duration of the project?

(Knock on wood… )
Revit really hasn't had significant issues with upgrading large projects in the past 3 releases(2009, 2010, 2011). I hope 2012 will be as painless.

For anyone planning to maintain a stake in the industry- Autodesk's subscription option is a no-brainer. And- If everyone is on subscription - then it is a limited issue to keep every project current to the latest release.

Some adopt 'wait till the first patch is released' – which seems be about half way through the release cycle these days; but personally- I would rather test and upgrade ASAP so the new features in the new releases can be leveraged.

Autodesk seems to have done a great deal more R&D as well as substantial beta development for Revit... So where this was an issue with stuff being broken before, they have been pretty good about not releasing junk that is broken or prone to blow up.

In 2009 and converting between previous versions I have seen sheets get mangled, some content in views drop out- like annotations, match lines disappear. And occasionally we have had the “Cannot delete non editable worksets” when purging after an upgrade, forcing manual purging.

One suggestion for upgrading- If you create a set full of plans, sections, elevation sheets and exported schedules- you can compare the PDFd sheets immediately after upgrading using tools like Bluebeam PDF Revue Document compare. It will highlight any changes in the sheet sets rather effectively.

Combine this with some key template content when starting projects and you have a well armored solution to utilize for upgrades…


No comments:

Post a Comment