Major project revisions set up

[rkc]

Does anybody have a methodology that works well when a project requires major revisions? I've already backed up the original documents to CD as a fixed point in the project.

[david_peterson]

Sure, there's that E key on the upper right hand side of the key board. Usually when I get major revisions it seem to be easier to hit the E key followed by the A key followed by Enter.

Are you looking more for how to handle clouds and such or just tracking? We ususally don't start clouding until after CD's have been issued for construction.

[rkc]

Yeah, sometimes....Really just looking for ADT project management ideas to keep track of everything, and not get xrefs messed up. Inevitably we will end up at some point going back because the owner will say "I thought that was still in the project" or some other selective memory. Thanks in advance

[david_peterson]

Then what you are doing sounds fine. Copy and re-name the project (in a different set of folder) for starters. We've tried a few things in the past, most had to deal with layering. I've heard of some poeple trying to accomplish this wih divisions, but I'm not sure that's the best idea.
For layering, we'd cloud what was change, and name that layer with the date and who reqested the change. ie S-anno-revs-070123-"consultant/owner/engineer/architect" (pick one). We used the consultants or Arch firm name. At least this way when they come back with more changes to the same thing, you can at least be sure how changed it. You may never know the why.

[Steve_Bennett]

A last resort to think about is if you are on subscription, Vault is free which will version your files and keep back ups of them (I think). If you decide to go this route GET HELP BEFORE installing and understand fully what you are getting into. Vault latches onto EVERYTHING on your computer and network and is very picky about what you do once it is installed. Data Management at its finest...