Revisions, reissues, pricing sets, deltas, etc 5

[AaronMcD]

I can't seem to figure out a good way to do this, and the architects always seem to do it differently, or have no standard at all.
For these questions, assume the set is a single product, i.e. any revision or issue applies to the set as a whole and all title blocks.

1) What goes into the list of issued sets in the title block? There are usually pricing sets, a permit set, possible permit re-issue sets or response to comments, more pricing sets, a construction set, and further revision. Do you just add a new line to the title block for each issue, or something else?
Example - would it look something like this, or would pricing sets be removed from the title block?
1-2-2019 Pricing Set
3-4-2019 Pricing Set
5-6-2019 Issued for Permit
6-7-2019 Plan Review Response
7-8-2019 Pricing Set
9-10-2019 Construction Set
10-11-2019 Revisions
1-2-2020 Revisions
2-3-2020 Revisions
3-4-2020 Revisions

2) Which sets get deltas? On the one hand, we need clouds for any changes to the construction set, but on the other hand, we need clouds for any changes submitted to the building department. This creates a kind of conflict. Plan Review Response seems like it should be delta 1, since it is the first revised set issued to the building department. But then does the next pricing set also get a delta? I don't think pricing sets should have deltas. Perhaps freeze clouds and deltas for pricing purposes? And then the construction set, which seems like it should have no deltas, but it will need clouds for the building department.
The construction set may not even go straight to the building department. Perhaps the second revision set after construction gets to the building department. Do you just turn on multiple delta numbers for the next submitted set?

http://www.hellodwell.design

 

[EngineeringEric]

I see multiple versions as well. One large project kept track of everything before construction, but wiped the slate clean with the Final Construction set which completely matched the pricing set (supposedly).

Personally, i don't like revisions or clouds or deltas until there is a sealed set. All sets before have progress print (whatever state its at) and not for construction where the seal goes. my projects aren't huge stadiums or hundreds of A/E sheets.

 

[dauwerda]

Coming from a heavy industrial (consulting) background where architects are typically not involved, I am used to seeing the following:

Start with revision A as the initial set that is formally issued to client for review.
Any comments/changes are captured in the next set, Rev B, with changes clouded and is again formally issued to client for review. This continues for as many revisions as necessary until no more changes are required. Each revision set has the new changes clouded with the revision delta (old clouds and deltas are removed). Note, only formal issues get changes clouded, there may be multiple back and fourths with the client on a drawing between formal revisions.

The issue for construction set is then created with the final approved set by removing all clouds and deltas and starting over at rev 0 (all Lettered revisions are removed from the title block at this time). Ideally this is also what is issued for permit, however sometimes it ends up being a lettered issued for permit set with all clouds removed.

Any changes after the IFC set are numbered sequentially and clouded. So, rev 1 would have all the changes clouded. If rev 2 is required, the rev 1 clouds are removed and rev 2 clouds are added, and so on.

I am used to title blocks that have room for showing the history of 4-6 revisions, so if you run out of room, you always keep the original but delete the next oldest revisions. So, you may end up with a tile block showing the revision history for: Rev 0, Rev 4, Rev 5, Rev 6 (current revision).


I'll also add that I feel that clouds are very important to highlight changes (before IFC's are issued) when working with multiple groups. That way, it takes much less time for all parties to look at a new set of drawings and find the changes that may effect them and their own efforts on the project.

 

[SlideRuleEra]

I'll endorse every suggestion that dauwerda has made. For design / review / bid / construction of our (owner) electric generating stations, we, together with our consultants, used that system and it works as intended. This was for thousands of drawings, from all disciplines (civil / structural, electrical, mechanical, etc.), issued to over 100 stand-alone contracts on a single project, and a total time span of about 4 years / project.

http://www.SlideRuleEra.net

 

[JLNJ]

We have a client whose title blocks track “revisions” and “issued for” separately. This way you can track revisions and contract changes separately.

I have also a seen Ad-xx to track addendums and then Bn-xx to track bulletins.

 

[JoelTXCive]

I work a large regional firm and surprisingly, there is no consistency across the company. Our projects are heavy civil and usually do not have an architect involved.

My group follows a procedure similar to dauwerda's, BUT once we get to the Issue for Construction (IFC) set and start making revisions, we leave the old deltas on the sheet. So, revision #1 gets deltas and clouds. Then, when we issue revision #2, we remove revision #1's clouds, but leave the old deltas. Only the current revision gets clouds.

I'm not sure why we do this, it was that way when I started and I have just kept it up. Having the old deltas on the sheets does help me remember the history of revisions for projects that drag on for years (or projects that stop and start).

 

[dik]

dauwerda is the one I'm used to, except the revision box is enlarged to show all revisions. Letter revisions up to RFC documents. Also documents are 'Released for Construction', etc. not 'Issued for Construction' (Released, not Issued, for some nebulous legal reason which I failed to grasp) and revision triangles and balloons are contained on the appropriate layer... S-ANNO-REV1, S-ANNO-REV2, etc. and turn the layers on and off... old delta triangles are not shown.


Dik