Folder structure for Inventor with cloud based Vault and a few custom libraries

[Niels__J]

Hi there,
I tried posting this in the Vault forum, but I'm not getting any answers, so I'll give a shot here. 

I'm trying to get my head around a reasonable folder structure for the use of Inventor with Vault (Basic).
At the moment we're seven people working on a shared network drive (both settings and part files), but we're moving to a cloud-based Vault, and we'd like to be completely free of any links to the server. We're using one project file for everything, and devide our designs by folders with consecutive numbers/names.

We have a few homemade libraries for content center, materials and appearances. These will be updated from time to time, so I makes sense to have them in the Vault so updates to them are automatically spread to all users.
We also have a few supplier libraries, but they don't change, so I don't see a point in having them in the Vault, when you can put a copy on each local computer.
The same goes for the standard content center libraries (DIN, ISO, JIS&GB, etc.) and the standard libraries for appearances and materials.

Appearance and Materials libraries I can point to in the ProjectFile, but the content center libraries are fixed to one (1!) place. Why??
The whole idea with Vault and a local working folder, is to speed up things by minimizing network traffic and keep as much as possible local. Or have I misunderstood something?

In the attached picture, I've tried to get an overview of the folder structure.
The purple lines are for standard libraries, and eg. Unistrut. I think they should go to the default installation path, and not the Vault. The same goes for the RAL_Colors appearance library and the Structual Steel EN10025 materials. They can all be copied to all computers, as they won't change regulary.

Our custom materials and custom content center gets updated regulary, so it makes sense to put them in the Vault.

I've talked to our reseller about the lack of meaning with just one location for the content center libraries (set in Application Options, not in ProjectFile), but they suggested I talk to Autodesk.

As for the folder structure, I can't seem to get a answer either. Not from the reseller, and not from the internet. I've found plenty of threads here, on Reddit, and on various other sites - all with the same question - but none with a usable answer. This article here is just p*ssing on people looking for answers.
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/What-is-a-good-dir...

How hard can it be (for Autodesk) to provide a simple overview of a folder structure for all the stuff pointed to in the Project File (or app. settings) ??
We're hardly the only 5-10 people company, using Inventor/Vault with only a few extra libraries.

Am I over-thinking it, and trying to understand something that I really don't need to understand in order to just use the programs?

Can anyone confirm/deny my thoughts, or give me a better solution?

[swalton]

Remember that the Vault project file defines the entire Inventor directory structure.  The filestore on the Vault server is the True Copy of all files.  The local workstation file is a working copy that can be deleted without any affect on the True Copy.

If you check-in a model with dependencies, Vault will pull in of those dependencies.  Everything for the design needs to be in the scope of the Vault Project File.

You will not be able to store library files outside of Vault.  You will not be able to store content center part files outside of Vault.  You can use a local install of the Content Center databases, but once the instance files are used in a parent that is checked into Vault, they will go too.  Check system performance to see if your setup works better with local or Vault content center databases. 

iParts and iAssemblies will be the same way.  If a parent consumes one of the member files, Vault will pull in the member and the Factory.  

Model States are a bit weird.  My understanding is that Vault must be configured to use Items to see the difference between Model States in a single file.  Since Items are only available in Vault Professional, you may want to spin up a test environment if Model States are a key part of your design process.

We like storing custom material and appearance libraries in Vault.  We also store all Style Libraries and Template files in Vault.  We store external ilogic rules in Vault too.

You are free to create new Project Files that do not link to Vault, but sharing that data with different users becomes difficult.

[ihayesjr]

@Niels__J 

Please review: Vault Help | Setup Vault with Inventor | Autodesk

[Niels__J]

Hi Steve,

Thank you for your answer. I'm not trying to be rude, but you're not really answering my question(s). I'm beginning to think that something gets lost in translation, or my ability to formulate the questions have gone AWOL.  

In another thread I've asked about Model State, but not in this thread.  

I know the Project File defines most of what is going on, and that you can set it up in a thousand ways, but I'm yet to see anyone actully posting a simple folder structure that will work for 95% of Inventor/Vault user.  I've posted a picture of ideas and thoughts in the first post. In this post I've slimmed it as much as I can.

Is THIS the way forward - for my company and pretty much everyone else - or is there a better way?

I don't mind storing the default content center databases(/libraries) outside the Vault. In fact, I'd love to, in order to minimize network traffic and maximize traffic on each users computer. We only have one or two custom CC-libraries, and they need to be in the Vault, as they are updated regulary.  The same goes for the material og appearance libraries. We're trying to move away from a physical server, so stuff should either be in the Vault or in the default installation files of Inventor. 

I hope this clarifies my questions/concerns even more. 

[ihayesjr]

@Niels__J 

Did you review the Help topic I just posted? It is a simple way to get started using Vault Basic with Inventor.

Your folder structure in the last image seems overly complicated. Also, you will not be using network shares with Vault. Everything will be stored in Vault and pulled into the user's local workspace on their machine.

Leave the Inventor Application Options at their default locations, which are on the File tab. They will not be used with this setup.

Here is a suggestion.

>Workfolder

      > Designs -> This is where all of the projects or designs your team creates go. In the Inventor project, this will be the Workspace setting.

      > Content Center Files -> This is the folder for the Inventor Standard Content Center files (DIN, ISO, JIS&GB, etc.)

      > Libraries -> This folder can be used for you custom library components and purchased components.

      > Design Data -> This is for the Inventor Design Data files the team will use. 

      > Templates -> This is for the Inventor Templates the team will use.

Everything else will be located in sub-folders under this structure.

[RajSchmidt]

I agree with @ihayesjr except for one point: I do not recommend using library paths in connection with Vault (except the CC files, obviously.)

Components in libraries are write-protected by Inventor mechanisms, which will override Vault. If you consider moving to Vault Professional at any time this will spell lots of trouble.