Revision Numbering

Revision Numbering

Anonymous
Not applicable
13,890 Views
29 Replies
Message 1 of 30

Revision Numbering

Anonymous
Not applicable

I'm trying to get our revision numbering to work as per our usual numbering system in AutoCAD, ie. P1, P2 etc. then T1, T2 etc. and finally C1, C2 etc.

P= Preliminary

T=Tender

C=Contract

 

This is a similar format many companies use in the UK.

 

We are using BDS 2016 but I can't seem to find a way to achieve this.

Accepted solutions (1)
13,891 Views
29 Replies
Replies (29)
Message 21 of 30

markcpduffy
Explorer
Explorer

Judy,

 

Could you tell me if i can achieve the following sequence - 1.0,1.1,1.2 etc., then 2.1,2.2,2.3 etc., then 3.1,3.2,3.3 then 4.1,4.2 etc going up as each revision goes through an change verification. This is what i am trying to achieve with a specific CDE. It upgrades the first number every time it has been reviewed by the client and uploaded to begin again in a review process.  I can only go up to 2.1,2.2 etc. and  cannot go to 3.0 or above with modifying both the numeric & alphanumeric sequencing. Do you thin you can help?

0 Likes
Message 22 of 30

LeeUUSLM
Contributor
Contributor

This article worked for me .... 

 

https://infinitebim.com/bs1192-revisions-revit/

0 Likes
Message 23 of 30

angelica.rodriguez.3d
Advocate
Advocate

This is NOT a solution to the problem, you can only have two series of revisions and as soon as you have to move from using P1, P2, P3 and T1, T2, T3 revisions to  C1, C2, C3 the system breaks.

We need a robust system  from within revit that allows more than two series of revisions. It has to allow at least Preliminary,Tender, Construction, Construction Record and more series.

Message 24 of 30

Atafs
Enthusiast
Enthusiast

This works when all drawings reach the same revision! but in reality they never do. you may need to revise i.e. the ground floor plan not the first floor.

0 Likes
Message 25 of 30

andre.baros
Participant
Participant

I would like to point out that this is not just an international issue.  I've never seen this work in the US either, and it remains a limitation on us imposed by Revit.

 

The point of a revision schedule is to track changes in a set of drawings for both internal and external audiences.  Sometimes projects progress in a clear linear fashion and the revisions can be tracked in a linear fashion with perfect alignment between the internal tracking and the external tracking... I haven't been lucky enough to work on such a unicorn in over a decade.

 

In reality, our documentation is contained in multiple parallel and overlapping drawing sets.  Revisions, together with sheets in general, need an system setting for "set of drawings"  These can be client vs jurisdiction vs contractor.  They may be design vs production.  They may be by phase.  We need to be able to specify that certain sets of revisions are grouped together and others are grouped together differently according to both the internal tracking and external tracking.  For example, in every jurisdiction I have ever worked in, they only want to see permit related revisions, and return the drawings if you show revisions for other audiences.  In some cases we have multiple overlapping jurisdiction which each only want to see their own revisions.

In revision schedules, this is vaguely tracked by the text field "issued to" which can contain the information, but can't be used for sorting, filtering, or leveraged for any other aspect of the project views or sheets.

 

Plug-in and Dynamo provide work arounds for some aspects of this, but at the end of the day there is no work around which doesn't involved Bluebeam or some version of deleting things, un-doing and deleting a different set of clouds for a different audience.  We've all created parameters to work around each different aspect of the problem, but none of those can talk to the revision schedule and revision schedules are insulated from our creative work arounds so we're stuck.

 

Please fix this, it remains an issue.

Message 26 of 30

ToanDN
Consultant
Consultant

@andre.baros wrote:

 

Please fix this, it remains an issue.


It has been fixed since Revit 2022.

 

ToanDN_0-1674069677879.png

 

0 Likes
Message 27 of 30

RobDraw
Mentor
Mentor

@andre.baros wrote:

The point of a revision schedule is to track changes in a set of drawings for both internal and external audiences. 


This is about revision schedules on sheets. Just wanted to state that before I started so we are on the same page.

 

Why would you track revisions that did not change the sheet that the schedule is on? Just had to throw that one out there.

 

The OP and a whole lot of other people are using a revision schedule for what I call issuances or milestone submissions. Revisions are accompanied by clouds and tags. Issuances often don't. (Your standards may vary.) If you can implement a separate schedule for these submissions and use the revision schedule for revisions only, your problem may go away.

 


@andre.baros wrote:

In reality, our documentation is contained in multiple parallel and overlapping drawing sets.


That is quite atypical for most of the rest of us and is probably better off solved with a robust documentation platform. I can't see how Revit can handle this as the model is basically a snapshot in time and cannot handle parallel states without some sort of trickery/workarounds(s).

 


@andre.baros wrote:

Please fix this, it remains an issue.


Go to the IDEAS forum and be heard.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
Message 28 of 30

andre.baros
Participant
Participant

I see what is available in 2022, we can now have more than one system.  We are no longer limited to numerical or alphanumeric.  I need to be able to specify which system prints on a specific sheet... a filter for temporary visibility control.

 

We have a lot (most projects) which are going through pricing changes while simultaneously going through the permit process.   I wish it wasn't true, but the places I'm working can take months to permit a project and we can't just sit on our hands during that time.  Most commonly, the permit set is also sent out to bid.  We are tracking bidding changes with revisions and we are tracking permit changes with revisions.  Unfortunately the city rejects the drawings if we include revisions which don't apply to permit comments.  The problem doesn't go the other way, our bidders need to see both sets of revisions.

 

This is one specific scenario which has come up on several different projects in several different cities in the last few weeks.  In the past I've had the same issue during the simultaneous concept level pricing and the entitlement process.  Over the years, I've had other groups only want to see the revisions they requested for their tracking process even though we're tracking other revisions for other reasons.

 

I was trying to avoid creating a new item, but will go ahead and do that.

 

Thanks for the reply,

0 Likes
Message 29 of 30

RobDraw
Mentor
Mentor

@andre.baros wrote:

We are tracking bidding changes with revisions and we are tracking permit changes with revisions.  Unfortunately the city rejects the drawings if we include revisions which don't apply to permit comments.  The problem doesn't go the other way, our bidders need to see both sets of revisions.


You don't mention using clouds and/or tags to indicate "revisions". Maybe you don't need a "Revision" schedule but rather a separate "Issues" schedule. If you are truly trying to track two separate sets of revisions to the model and drawing sets with having to exclude revisions to the bid set, I don't see how that can work from the point of view of the model. If this is strictly an annotation exercise for the title block, it's probably easier to use graphic schedules of some sort rather than trying to work with the limitations of Revit's revision schedule. It could be quite easy to swap out schedules for printing purposes.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 30 of 30

andre.baros
Participant
Participant

Thanks for the thoughts.  Everything is clouded and tagged, a current work around is to have a "live" titleblock with the revision schedule and a "fake" titleblock for the city which has a dummy schedule.  We can turn on and off the clouds and tags no problem.

 

My frustration came from seeing teams dealing with this by printing and then "cleaning things up" in Bluebeam.  It's such a basic level of visibility control, but locked into the revision system which sees user control as a path to error (which it's hard to argue with) but too inflexible.