TheSwamp

CAD Forums => CAD General => CAD Standards => Topic started by: M-dub on February 10, 2005, 08:43:57 AM

Title: Revision Cloud & Triangle Standards
Post by: M-dub on February 10, 2005, 08:43:57 AM
Just wondering what everyone uses as a standard for revision cloud & triangle layers.
There have been a few different practices here, but this what we currently (try) to use:
- All modifications to drawing are done on proper layer
- Revision Triangle block is inserted on layer "REV"
- Revision Cloud is created on layer "REV1", "REV2", etc.
- All triangles will be visible at all times (unless drawing gets too crowded, etc)
- Only the current revision cloud should be visible (on and thawed)

Anything to add / change?
Title: Revision Cloud & Triangle Standards
Post by: CADaver on February 10, 2005, 08:53:38 AM
Here, revision clouds and triangles for current revision only, both on layer REV.  
Previous revision clouds and triangles are deleted.
Title: Revision Cloud & Triangle Standards
Post by: M-dub on February 10, 2005, 09:07:45 AM
I don't mind that one. Actually, I prefer that, but for some reason, they want some form of historical tracking.  They can look at the Rev block (Dates, descriptions, etc), thaw the rev cloud to show where the changes occurred, then they can refer to the project file if more research is required.  Overkill, I know, but it goes back to the "That's how it's always been done around here." story.  Just because it's always been done doesn't make it right.
Title: Revision Cloud & Triangle Standards
Post by: jonesy on February 10, 2005, 09:09:07 AM
How would that work if the area of work was a large, irregular shape, that has only a minor modification. We tend to work on civil stuff and any modification, say to the depth of the excavation, may extend along a road for many metres. Would you put a plottable cloud around the whole area and why.  My thoughts were to put a revision triangle on a plottable layer, but the cloud on a non plot, so it is more a visual aid. Any comments on why or why not to do it this way
Title: Revision Cloud & Triangle Standards
Post by: M-dub on February 10, 2005, 09:21:49 AM
I think that our drawing disciplines call for different practices.  Yours might make sense for Civil, but in the Inst / Elect field, ours makes sense...or seems to anyway.

I forgot to mention, the clouds should be thawed when the drawing reaches 'As Built' status.  (Show clouds only during design and commissioning phases)
Title: Revision Cloud & Triangle Standards
Post by: Wyatt Earp on April 18, 2005, 03:29:06 PM
I agree with CADaver:

All my stuff goes on a Layer called _Rev. I keep all triangles (after Rev 0 - IFC) to allow for tracking of extras and so on. Clouds get modified to suit.

Cheers
Title: Revision Cloud & Triangle Standards
Post by: CADaver on April 18, 2005, 03:31:51 PM
Quote from: Wyatt Earp
I agree with CADaver:
Be careful with that, it could get you in trouble  :lol:
Title: Revision Cloud & Triangle Standards
Post by: BAshworth on April 18, 2005, 03:39:23 PM
Our standard is to create two layers for each revision. REV#_CLOUD and REV#_DELTA.  Cloud layers are colors that end in 2, delta layers are colors that end in 4. (for plot style reasons.)

We turn off the cloud layers for earlier revisions, and only plot the clouds for the current delta.

We have to do this because our revisions are based off of the architects scheduling, and they don't always go in order.  (ie. Delta 4 will sometimes go out before Delta 3)
Title: Revision Cloud & Triangle Standards
Post by: MP on April 18, 2005, 03:41:21 PM
Quote from: Wyatt Earp
I agree with CADaver ...

Adjusting scorecard.
Title: Revision Cloud & Triangle Standards
Post by: CADaver on April 18, 2005, 03:43:15 PM
Quote from: MP
Quote from: Wyatt Earp
I agree with CADaver ...

Adjusting scorecard.
I gotta see this scorecard someday.
Title: Revision Cloud & Triangle Standards
Post by: jwisherd on April 18, 2005, 04:49:15 PM
We call our revisions addendums, so our layers are named
Addendum-1  4-17-05
Every set of addendums gets a revision layer with the issue date as part of the name, for tracking purposes.
Title: Revision Cloud & Triangle Standards
Post by: David Hall on April 19, 2005, 09:14:37 AM
We use 2 layers: Anno-Revs for the clouds, and Anno-Text for the rev delta.  We remove old clouds and deltas when the job is "As Built"
Title: Revision Cloud & Triangle Standards
Post by: whdjr on April 19, 2005, 09:55:46 AM
We make a secondary file with a revision date in the filename and cloud the revision that way we have two seperate files, one original unchanged and one revised file.
Title: Re: Revision Cloud & Triangle Standards
Post by: Royalchill on November 02, 2005, 01:25:08 PM
Looks like your doing it right to me. We do the same  :lol:
Title: Re: Revision Cloud & Triangle Standards
Post by: glee on November 02, 2005, 03:24:13 PM
- All modifications to drawing are done on proper layer
- Revision Triangle block is inserted on layer "REV"
- Revision Cloud is created on layer "REV1", "REV2", etc.
- All triangles will be visible at all times (unless drawing gets too crowded, etc)
- Only the current revision cloud should be visible (on and thawed)
We do it somewhat similar. 

Keeping the triangles has somewhat to do with certain permitting agencies requiring that they know how many revisions or addendums you have carried out.  Since their level of trust for people in the AEC field being somewhat small to non existent.  This way when they review your drawings, they can track changes since the original permit set was issued (that way you can't try to slip one over them).
The other factor is for public bid jobs.  Since a bunch of addendums can sometimes be issued during the bid process it helps contractors keep track of the changes, especially if they did not receive an addendum.  This way it keeps a level playing field. 
Say, contractor A did not receive addendum #2 and is blissfully unaware, then when addendum#3 appears, they note the triangles for #2 and scream blue murder at the architect or in todays' world, the reprographics company trying to make a few more bucks by pretending they know how to run public bids and hosting drawings on their web site. 
Title: Re: Revision Cloud & Triangle Standards
Post by: Murphy on November 03, 2005, 05:43:33 AM
I agree with CADaver too!!  :-o

We bind all xrefs and save a copy of that submitted set so that at any time we can go back and plot that exact drawing. Makes life a lot easier then having to try and figure out what exactly changed 3 revs ago on a drawing that is constantly updated.
Title: Re: Revision Cloud & Triangle Standards
Post by: jwisherd on June 16, 2006, 03:47:46 PM
When we do revisions, we call them   Revision-1--06-16-06    (or whatever the date of the revision is) this allows us to triangle and bubble changes in that revision, also a memo of changes that took place in that revision lives in the file, so we can determin when a change was made, and  what it affected.
Title: Re: Revision Cloud & Triangle Standards
Post by: Bob Wahr on June 16, 2006, 04:06:49 PM
We do it close enough to exactly the M-dub does that it's not worth pointing out the differences.
Title: Re: Revision Cloud & Triangle Standards
Post by: Greg B on June 16, 2006, 04:20:19 PM
We are still working on a standard for the office, but since I'm the one that does most of the revisions and bubbles I've done the following.

Created a layer called Revision #X (X being the revision number, well duh huh?)
Make revision cloud and triangle white - heavy lineweight in our office

When a new revision is made, turn the old revision to a light grey color (very light lineweight) and make new Layer Revision #X and make that white.
Title: Re: Revision Cloud & Triangle Standards
Post by: hendie on June 19, 2006, 04:03:48 AM
I don't mind that one. Actually, I prefer that, but for some reason, they want some form of historical tracking.  They can look at the Rev block (Dates, descriptions, etc), thaw the rev cloud to show where the changes occurred, then they can refer to the project file if more research is required.  Overkill, I know, but it goes back to the "That's how it's always been done around here." story.  Just because it's always been done doesn't make it right.

Mike,
when you finally get Adept ~ it keeps an automatic revision of every document change. It even keeps an audit trail for each doc telling you who signed it out and when, and who signed it back in and approved it ~ very useful stuff.
The previous revisions can be accessed easily if required and you can do comparisons if need be.
Title: Re: Revision Cloud & Triangle Standards
Post by: Bryco on June 19, 2006, 09:56:32 AM
Does everyone do the clouds in paperspace?
Title: Re: Revision Cloud & Triangle Standards
Post by: Bob Wahr on June 19, 2006, 11:44:15 AM
No.  We do the clouds where the revision is.  Paper Space revisions get clouded in pspace and mspace revs in mspace.
Title: Re: Revision Cloud & Triangle Standards
Post by: CADaver on June 19, 2006, 01:04:07 PM
Does everyone do the clouds in paperspace?
Yes, clouds are annotation, all annotation is in PS.
Title: Re: Revision Cloud & Triangle Standards
Post by: M-dub on June 19, 2006, 01:36:48 PM
Mike,
when you finally get Adept ~

It should be soon.  A PO has been issued!  :-D
Title: Re: Revision Cloud & Triangle Standards
Post by: Greg B on June 19, 2006, 01:48:39 PM
It should be soon.  A PO has been issued!  :-D

That's right...you get anything AutoCrap you get "POo".
Title: Re: Revision Cloud & Triangle Standards
Post by: hendie on June 20, 2006, 10:11:14 AM
Mike,
when you finally get Adept ~

It should be soon.  A PO has been issued!  :-D

Mike,
Synergis have just released our case study ~ http://www.synergis-adept.com/ top of the page on the left
*edited* oops I should mention that it is the WL Gore & Associates Case study