|
active
Joined: Mon, Jul 26, 2010
1 Posts
No Rating |
I've worked in revit now for about a dozen or so projects, give or take and have had to work with it's revision system eiter for permit comments or just simply some small isolated changes for various reasons. I've just recently encountered my first need for a heavily revised project in Revit and I can't help but wonder that there has to be a better way than my current process. As an example let's say I have a office suite that has been issued out with a revision #1 already, now the client wants to make a change on the fly to the program. Remove 8 adjacent individual offices and combine them into one larger conference room wih a galley. In the past my workflow in say CAD would have been something like, make the changes to the plan (delete/add walls, doors, windows, retag partitions, fix dims, etc) cloud them, next go on to the ceiling plan sheet - update and cloud, next update the door schedule perhaps with new/deleted/changes and cloud, you get the picture - manual coordination and cloud as processed. Now given that same example in Revit, I open my plan view and make the new design changes (update walls, doors, tags, dimensions, room parameters etc) and cloud the plan view. From there I find Revit to be a bit of a double edge sword, given it's dynamics with it's live changes. Meaning I now have to know what I or one of my team members have changed and go back to each isolated view(s) that have already been changed and track down what has been updated that needs clouding say the door schedule changes or to make sure and catch that west wall that use to be painted gyp that is now wall covering etc...
Sure one could argue you would have to manually handle it in CAD so how is that different now? And that is true but atleast I have the benefit of seeing the old/new as it becomes updated and not here I clouded the floor plan now go cloud everything else in your 80 sheet set with new changes already in place. Yea I can track it down but I would hope Revit would help me in this regard as opposed to a step actually backwards in my opinion. If I were to take the same example above and expand upon it even further in scale I can help but think how quickly it would become a complicated tracking process.
I can certainly appreciate how Revit helps tremendously with coordination in a project. And granted in this example, your views would be updated with the new information but it is difficult to rest assured that you have accurately conveyed attention to all of those changes in your documents.
I suspect someone may chime in with the idea that I should change my process, to not make all the changes at once and track it that way but sometimes it's not that simple nor is that approach always the most efficient. But I am open to changing my process depending on what that entails  So, I am curious as to your suggestions, please feel free to share your tips
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
 |
Revit is a growing experience.
We have done many projects over the last 6 1/2 years and although this may seem like a problem, it really isn't. It just demands that all of your staff pays attention and follow through.
When you change a model element, you have track it down in all sheeted views and flag accordingly. And if you do this, you will be amazed at how many times you will find that this process leads you to other elements that need your attention that you never would have thought about in CAD.
BTW - You are far better off to cloud on sheets rather than in views.
|
Search