Change Revision Scheme from Alpha to Numerical Mid Lifecycle

[Anonymous]

Hi All,

Our company has the practice of developing designs using alphabetical revision scheme (A,B,C etc.) and then releasing to production on 01 and continuing numerically from this point onward. 

I've been trying to set this up in Vault Professional by using two revision schemes and using the Change Revision command to switch between Development and Production schemes.

My current workflow is to quick change a revision to allow editing and then use change revision to set the new revision scheme as shown below. By default my 3D files in this category are set to follow the Development revision scheme which follows alphabetical revisions upon entering Vault.
changing revision scheme from alpha to numerical

This seems to work well and following revisions follow the new numbering scheme no problem.

Note the additional quick change state I had to use between released rev B and rev 01 to allow me to change the revision number. If possible I would like to find a way to remove this step.  

Example of revision scheme change after release

Now lets say I want to add a new part to the production assembly (in this case a cross brace) it will first be assigned an alphabetical revision as previously. 

New part created as revision A as expected

As with the previous parts changing the revision scheme to production gives me a numerical 01 initial release for the part. 

changing new part revision shceme

When trying to release the main assembly Vault highlights restrictions stating that the new file is not the latest and will not let me release it at that revision. 

Restriction after revision change stops me from relaseing the assembly with the new part

Is this workflow possible to achieve in Vault or have I just gone about it the wrong way. I would appreciate any info you may have. 

Thanks,

Ash
  

[Anonymous]

Hi Ash, 

I want to be clear I understand your problem. It sounds like you have a Released file, which you then move to Quick Change in order to move to the new revision scheme, which seems to work as expected. But when you go to add a new component to the mix and assign the numerical revision automatically, it gives you version issues and won't allow you to proceed with the Release. Am I understanding this correctly?

[Anonymous]

Yes that is correct. The numerical revision for the new part is assigned manually as all parts follow the alphabetical scheme by default for our category.  

[Anonymous]

Have you tried Getting the file once the revision scheme has changed? Vault does appear to be giving you that unexpected revision warning- it might be necessary in order to move the lifecycle state. Synchronizing the file's properties might be another way to go as well- I know I frequently have to do this when I updated revisions manually.

[Anonymous]

Yeah, I've tried opening it and getting the latest revision of parts directly from Inventor. Once I change the revision manually it continues to look for the previous one, which it will never find as it was changed. 

In terms of file properties I have the Vault revision mapped to the Inventor iProperty so unless I use 'Update Properties' in Inventor or 'Synchronise Properties' in Vault I'll get a non compliance that prevent me from releasing the files anyway.