Vault General Discussion

Vault General Discussion

Reply
Employee
alan.ho
Posts: 63
Registered: ‎08-02-2007
Message 11 of 15 (1,398 Views)

Re: Vault 2012 Revision Table Integration

09-16-2011 04:01 PM in reply to: mdurst

Hi mdurst,

 

The Vault Revision Table was intended to display only released revision data.

Therefore in your example, Rev C would not show the Change Description, Engr Approved By and Date simply just because it is still in the Work in Progress state. One of the reasons why this was impletmented in such a way is because these properties may be subjected to changes prior to release.

 

We still allow the display of the Revision C row so our users can tag revision balloons to them or add values (which are not mapped to those in the Vault). But however if Revision C is skipped for release, this row will be deleted in the next Revision Table update as it doesn't fulfil the released criteria. 

 

The command inside Inventor and the Job Processor is essentially doing the same thing with the same rules. The only difference between them is that the Job Processor acts on the file upon a trigger (on the releasing of the file) whereas the command in Inventor performs the update anytime during WIP. You can have Inventor mimick the same behavior for released files if you have sufficient rights to act on released files.



Alan Ho
User Experience Designer
Cloud Platforms
Autodesk, Inc.
Employee
alan.ho
Posts: 63
Registered: ‎08-02-2007
Message 12 of 15 (1,386 Views)

Re: Vault 2012 Revision Table Integration

09-16-2011 04:16 PM in reply to: mdurst

Hi mdurst,

 

There are some pretty stiff rules that the Vault Revision Table is employing:

  • Displaying only released data (which I stated in my previous post).
  • Displaying only the first released revision data (that is if you have multiple revisions of the same letter that are re-released, only the first released version will be retained for display)

Unfortunately, there is no way to override (or relax) these rules as of now.

I hear your feedback and will escalate this to our Product Managers for their review.

 

Meanwhile, hang in there.



Alan Ho
User Experience Designer
Cloud Platforms
Autodesk, Inc.
Distinguished Contributor
jeff_jordan
Posts: 128
Registered: ‎05-10-2011
Message 13 of 15 (1,336 Views)

Re: Vault 2012 Revision Table Integration

10-28-2011 08:21 AM in reply to: alan.ho

The following is our desired workflow, and as of now, I have not been able to configure Vault to properly manage this workflow.  The problem comes during the release state and how Vault populates the revision block on the drawing.

 

To Create New
     1. Create new part file
     2. Design part (sketch, extrude, etc…)
     3. Save the part file
     4. Add the file to vault
          a. Vault assigns the .ipt file to the Engineering Category.
          b. Lifecycle rules and revision rules are then applied to the file
               i. State: Work in Progress
     5. Continue design work (periodically syncing with Vault)
     6. Finalize design
          a. Populate iProperties
          b. Create Drawings (iProperties are brought forward from the part and copied to the drawings iProperties)
     7. Save the drawing file (same name as part file)
     8. Add the drawing to Vault
     9. Release part/drawing for fabrication
          a. Vault automatically populates the revision title block on the drawing
               i. REV column with “–“ to represent initial release*
               ii. APPROVED column with the person’s name that released the drawing
               iii. DATE column with the date it was released
               iv. COMMENT column with default value from drop down list, “INITIAL RELEASE”
          b. .dwf is created

 

To Revise
     1. Change state to “Work in Progress”
     2. Make Change
     3. Change state to “Released”
          a. Vault automatically populates the revision title block on the drawing with a new row
               i. REV column with “A“ to represent new release*
               ii. APPROVED column with the person’s name that released the drawing
               iii. DATE column with the date it was released
               iv. COMMENT column with comments from drop down list or typed at time of release, “REDUCED SLOT TO 3mm”
          b. .dwf is created

 

*Our revision scheme is set up as follows: -, A, B, C, etc…  The reason we use “-“ is because we don’t document in the title block who drew the drawing.  Instead, we automatically track who released the drawing in the revision block.  This name can be used to ask questions about the design because whoever released the drawing would know enough about the design to answer these questions, or able to direct the question to the appropriate person.  The revision block also keeps a history of who released the drawing in what revision.  If you want to know who drafted the drawing, you can search the properties in vault.  We want fabricators to call the person who released the drawing if there are questions, and NOT the drafter.  There is a good chance the drafter wouldn’t have a clue if a tolerance can be modified or if an obround can be modified to fit a standard punch.

 

REV to us means that a design and its respective drawing have been released in a new form, fit or function.  The rev bump occurs at the time of release (instead of Vaults default setup…from released to WIP).  The thought behind this is that we don’t want to demarcate a revision until the changes are made.  Not BEFORE the changes are made as Vault’s default.

 

We are also trying to automate as much as possible, with automatic population of the revision block.  All of the information exists in Vault when a design is released, but for some reason, this information can’t easily be extracted to automatically populate the revision block!

Autodesk Product Design Suite 2012 (Inventor 2012 Pro SP1, Vault 2012 Pro Update 1)
Windows 7, 64-bit
Intel Core i7
8GB
Nvidia Quadro FX 3800M
Distinguished Contributor
jeff_jordan
Posts: 128
Registered: ‎05-10-2011
Message 14 of 15 (1,308 Views)

Re: Vault 2012 Revision Table Integration

11-02-2011 10:50 AM in reply to: Andy.Spivey

Andy.Spivey wrote:

You can create a job processor user (with a strict password) and add them to the released lifecycle state to grant them access.  This will also allow you create a DWF file for a released file

 

Reference - http://crackingthevault.typepad.com/crackingthevault/2011/05/file-locked-when-releasing-a-file.html



Doesn't this mean that the Vault Revision Table would show "Job Processor" in the Approved Column?

Autodesk Product Design Suite 2012 (Inventor 2012 Pro SP1, Vault 2012 Pro Update 1)
Windows 7, 64-bit
Intel Core i7
8GB
Nvidia Quadro FX 3800M
Distinguished Contributor
jeff_jordan
Posts: 128
Registered: ‎05-10-2011
Message 15 of 15 (1,303 Views)

Re: Vault 2012 Revision Table Integration

11-02-2011 02:44 PM in reply to: jeff_jordan

Just ran the experiment...As Alan mentioned in his rule two above, "Displaying only the first released revision data" will make it so that the Revision Table shows the user that releases the file.  The job server is not recorded here.

 

The job server actually works well...for the most part.  It's slow though...I've decreased the time it takes to look for work to 1 minute (the lowest value I think) by editing a line in the file C:\Program Files\Autodesk\Vault Professional 2012\Explorer\JobProcessor.exe.config to <add key ="PeriodInMinutes" value="1" />

 

The .dwf was updated and reflected the correct rev number, description, date and approver.

 

A potential drawback would be that the Job Server leaves (overwrites your comment) a little note in the vault comments, "Revision table updated by Job Server."

 

Fortunately releases aren't everyday sort of things. 

 

It would be nice if we could also request the job server to create .pdf, .igs, .stp, and so forth.  It would also be nice to have an option to keep the drawing revision and part revision at the same level.  I cant see a time when our drawings would ever be at a different rev state than the part.  In fact, we want all of the information to flow from the part.  The drawing is just a 2-D, paper way of expressing the part!  In my opinion, all information should originate in the part....but I'm getting off topic.

 

There has got to be a better way of doing this that doesn't REQUIRE a job server...considering the job server requires a license to run the job.

Autodesk Product Design Suite 2012 (Inventor 2012 Pro SP1, Vault 2012 Pro Update 1)
Windows 7, 64-bit
Intel Core i7
8GB
Nvidia Quadro FX 3800M
Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Need installation help?

Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.

Announcements
New button for Platinum & Gold Subscription customers
Gold & Platinum Subscription customers can alert Autodesk if they require assistance with their forum post

Manufacturing Community
The Manufacturing Community provides additional access to tips, tutorials, blogs and networking with peers.