Submit Your Suggestions for Viewpoint Team

Yes Please make Revisions start at 0

Sam agreed much better than 6 months ago.  the drawing features are coming along nicely.  keep up the great work!

We have improved revision handling quite a bit over the last couple of releases - revisions now support alphanumeric characters and increment automatically in a number of ways - so if you edit one or more drawing sheets to be revision A, AA, A01, 0, etc, the next revision will automatically show up as B, AB, A02, 1, etc.

Soon we'll have a "Default Starting Revision" feature so you can define the starting revision all new sheets use and not need to edit it manually after upload.

NEED THIS IMMEDIATELY.  THIS IS COSTING US TIME AND MONEY 

also would like to see status of drawing.  like vista ex. AAN, R&R.  plus dates to mark sent out and received with a status.  currently there is a issued and received but received field must have an input.  if you issue the drawing you would receive it +14 days typical.  is this the intention to mark future?  

ability to set drawings to start with revision 0

agree need this ASAP

The ability to upload changed sheets without modifying the revision would be great. It's one of the last steps to make the drawings feature really functional.

Additionally, when Revision A, Revision 0, Revision 1 are uploaded in TEAM,  Revision 1 will default as Revision 3.  In order to change this, I would have to delete the old revisions in order to assign Revision 1 with its proper revision number.  It doesn't allow me to change it manually because it thinks that Revision 1 has already been uploaded.

Many projects start with Revision A, B, C, etc.. until it is issued for construction as Revision 0.  It would be nice to be able to name a revision with a letter.  Also, It would be nice to mark a revision as redlined.  For example, we may be working with Revision 2, when I red line Revision 2, it would be nice to rename it as Rev 2 -Redlined OR Revision 2R.  Then the official Revision 3 release would typically address the redline.

Oops, sorry about the extra posts

The Revision (Version) and Set (Revision source) should really match the official Version as issued by the designer rather than ANY revisions.  There are times when we need to revise a sheet other than an official Designer revision, so, keeping the Set as the source and the Revision being editable and custom is important.  There are times when a plan sheet is revised, but the official Version is the same. One example is DSA and OSHPOD jobs.  The designer's Version will the the 'submitted' one, but the one that comes back from DSA/OSHPOD needs to be the latest/greatest.  In this case the Set would be "DSA Approved" while the Revision would be the same as the Submitted one.

The Revision (Version) and Set (Revision source) should really match the official Version as issued by the designer rather than ANY revisions.  There are times when we need to revise a sheet other than an official Designer revision, so, keeping the Set as the source and the Revision being editable and custom is important.  There are times when a plan sheet is revised, but the official Version is the same. One example is DSA and OSHPOD jobs.  The designer's Version will the the 'submitted' one, but the one that comes back from DSA/OSHPOD needs to be the latest/greatest.  In this case the Set would be "DSA Approved" while the Revision would be the same as the Submitted one.

The solution is related to my other suggestion about being able to 'slipsheet' in a revised sheet without creating an official Revision.  For example, if I revise a sheet for reasons other than an official revision (Bluebeam bells/whistles, resetting hyperlinks, etc.) and we had the ability to upload a sheet to replace the current one rather than create a revision, that could partially solve the issue so we can keep it part of the same Set and Revision.

Understood Josh and I, admittedly, did confuse the two in our test project.  However, sometimes an individual Sheet gets change via an RFI response.  Or, there is also the possibility of a bad upload, adding Bluebeam bells/whistles to a sheet, etc. and, since there is no way to remove or choose to replace the sheet rather than revise it, having a custom revision number would be better.

Agree we need to provide some more customization around the revision field.  Its a bit too automatic right now.  

However, the 'Drawing Set' field is made for ASIs, Bulletins, etc.  When you upload a group of files, you can designate them as part of a 'Set'.  You can then create custom views by the Drawing Set field and it will find all drawings in that particular set, even if they've been superseded since.  As well as see which set each file was part of in the history of that particular sheet.  This is where you'd put ASI 1 for example, I've seen a few customers confuse this with Discipline.   We'll work to improve the UI here to explain this better.    

Yeah.  What he said!  Please see VPT-I-292, my feedback which is related to this.  Until this is updated, call it what it is, it is a Version Field renamed to Revision but this is not currently a "real" revision field. 

To add to this, the ability to designate the Revision (ASI 001, Bulletin 2, etc.) would be even better.