revisions

[maior]

Hello everyone
I wanted to know how you handle the revisions with inventor and vault?
The only "revision" property goes a little tight because (not being used to it) I have 50 versions in rev. 0 then I have to change the rev. to the single component but also to all the assemblies that make it.... and then I lose the head....
It would seem more appropriate to make a "salva copy with name" and indicate in the file a revision index (e.g. ghyd_0 to ghyd_1) and to replace in the assemblies the component. .

Can it be right?
thank you for your answers.

never
firewood

 

[davide75]

I do not use the vault but usually at the axieme do not give a revision index if I have pieces that have been revised.if in the bom I have the code at most I make recall the revision of the component them, otherwise seriously you are not behind us

 

[Peppe]

Hello everyone
I wanted to know how you handle the revisions with inventor and vault?
The only "revision" property goes a little tight because (not being used to it) I have 50 versions in rev. 0 then I have to change the rev. to the single component but also to all the assemblies that make it.... and then I lose the head....
It would seem more appropriate to make a "salva copy with name" and indicate in the file a revision index (e.g. ghyd_0 to ghyd_1) and to replace in the assemblies the component. .

Can it be right?
thank you for your answers.

never
firewood

I used to do that, but... After a while you can't really stay behind it.
so the detail always has the same code and the revision index I put it on the table.... other important thing I think is to quantify the importance of the revision itself, i.e. if the changes are of little account (increasing a hole, moving holes for various errors or other minor modifications) I proceed with the revision, while if the changes are more substantial (change shape, addition or removal of parts) I create a new code. the rule would be: "if the detail in revision is perfectly interchangeable with the previous revision is feasible otherwise new code... "
p.s. I do not use vault, but I know for certain that this program creates copies of files/tables every time you make certain modifications, so you always have your own history of the parts and their tables.

 

[Avoplus]

the vault does not manage the "revisions", but the "versions" (i.e., at each release of the file, creates a copy). on the one hand, this is convenient because you have the impression of having the historical of the project; on the other hand, there is an "uncontrolled" increase of the indexes (inappropriately revised) of the files, with problems of disk space and management of the "obsolete".
Until we used the vault, we also adopted a method similar to that of peppe (i.e. index of manual review).

to be able to use the index provided by the vault (admitted and not allowed that it is acceptable to be with a general set with xxx revisions...), only approved revisions should be released.
p.s.
my personal opinion is that it is not advisable because, too often, inventor files require to be updated without apparent reasons (type bolted connections, adaptive parts, derivatives, i-parts...) and every update is equivalent to a cycle of extraction-release. . .