Thanks for this nice and interesting video Could you please recommend best practice in the following upload non-native Vault project to Vault scenario: Nowadays we have a bunch of old projects outside Vault with the same folder structure than the ones we are nowadays checking in since we had Vault installed back in 2018. This means that under a parent folder for the project, both types have a folder for assemblies, a second for parts, and a third for drawings. The only difference in their file structure is a folder in the old projects where commercial pieces were being placed every time we needed it. In that way, the very same standard piece could be found in the same folder of those several old projects. At the present time, most of these parts are still valid in new projects, but since Vault has the chance to reuse recurrent pieces by building a library with them, we place them from a library folder tree into new assemblies. If we would make up our mind to proceed to check-in most relevant non-vaulted projects into Vault to improve their reusability, we would find each time, an average of 500 occurrences from 80 standard pieces that nowadays keep the same name in the library and could be located by a more or less deep browsing. Estimation for an average of pieces that would find their names changed nowadays and need to be pointed manually in the library could round 150 occurrences from 30 different pieces each time. Do you think Autoloader would prove in this scenario a better tool for this purpose than Vault Server Check-in project tool from Inventor file menu? What would be the differences in doing that with one or the other way? Thanks a lot for your wise advice and help.
Hi Ramon, We are going to go ahead and reach out to you via email to help answer your question! Look out for an email from our Lifeline team soon! Best, KETIV Team
Thanks for this nice and interesting video
Could you please recommend best practice in the following upload non-native Vault project to Vault scenario:
Nowadays we have a bunch of old projects outside Vault with the same folder structure than the ones we are nowadays checking in since we had Vault installed back in 2018. This means that under a parent folder for the project, both types have a folder for assemblies, a second for parts, and a third for drawings. The only difference in their file structure is a folder in the old projects where commercial pieces were being placed every time we needed it. In that way, the very same standard piece could be found in the same folder of those several old projects. At the present time, most of these parts are still valid in new projects, but since Vault has the chance to reuse recurrent pieces by building a library with them, we place them from a library folder tree into new assemblies.
If we would make up our mind to proceed to check-in most relevant non-vaulted projects into Vault to improve their reusability, we would find each time, an average of 500 occurrences from 80 standard pieces that nowadays keep the same name in the library and could be located by a more or less deep browsing. Estimation for an average of pieces that would find their names changed nowadays and need to be pointed manually in the library could round 150 occurrences from 30 different pieces each time.
Do you think Autoloader would prove in this scenario a better tool for this purpose than Vault Server Check-in project tool from Inventor file menu?
What would be the differences in doing that with one or the other way?
Thanks a lot for your wise advice and help.
Hi Ramon,
We are going to go ahead and reach out to you via email to help answer your question! Look out for an email from our Lifeline team soon!
Best,
KETIV Team
@@KETIVTechnologies Thanks, I will.
Please do Vault Basic and Plant 3D uploads.
Great suggestion, we'll look into doing those!