2019-04-19 04:15 PM - last edited on 2022-10-04 02:25 PM by Oleksandra Vakariuk
2020-06-02 06:30 PM
2021-05-22 01:12 PM
2021-05-25 12:46 AM
2021-09-12 11:29 PM - last edited on 2021-09-13 09:44 PM by Laszlo Nagy
In my experience, you can track revisions two general ways: by issuance (transmittal, change ID) or by number of revision per sheet. We call the revision number the “delta.” So Delta 01, 02, 03, 04, etc.
I prefer the latter method as it more accurately depicts the number of changes specific to a given sheet which is all code officials or contractors care about. I may have 50 drawings in say Addendum 02, but whereas the plans may be on Delta 02, elevation sheet revisions may be on Delta 01. If we tracked the same Addendum by change ID, then plans and elevations would both be on Delta 02 and give the impression that there were prior changes on the elevations which wouldn’t be true.
The sheet method is also a throwback to when we used paper exclusively in the field. Prior deltas would serve as overlay “targets” and we would literally cut and paste new revisions over the old ones. The sheet method also suggests its better to place revision graphics on the layouts (paper space) rather than in the view (model space) since the same view may serve as a background on multiple sheets and could have different deltas.
But you all should do what works for you, it boils down to how you prefer to track revisions and manage time in coordinating between your staff and your consultants.
I was looking for an answer to the initial question to this thread though and I couldn’t find one. We use the Book Settings, prepare Transmittals and use Change Manager and the Change Tool to generate our clouds and deltas. When it’s time for another revision set, we typically turn off clouds but leave prior deltas on by toggling to the “marker head” only setting in the Change Tool.
I concur with Eric a couple comments above: The problem is if I ever wanted to turn the old cloud back on to check on prior changes, it doesn’t keep the original cloud shape. And if we tried to manage all the prior revision graphics using layer settings, turning off a revision layer turns off both cloud and marker head which violates our intent to keep all prior deltas on. Is there a work around for this to archive the revision clouds on prior changes, preferably using the Change Tool?