It is not possible currently to have an assembly that points to older revisions of constituent parts/subassemblies even though the Vault itself can handle this. The result is very inefficient and error-prone configuration management. It is just version tracking without any control over product configuration and revisions.

It is important to be able to manage BOMs and Product Structure *over time* instead of assemblies and drawings always pointing toward the latest Vault "version" of their constituents.

For example, if I want to pull up an accurate assembly snapshot from two years ago (with the structure as it existed at that point in time) it is very difficult without creating new assembly model files for every revision. The same is true for drawings.

By default, assembly models and drawings should point toward specific vault versions of the models with the ability to update to any other version (or the latest) if the user wishes. Making Alibre aware and able to point to specific Vault versions of files would *greatly* enhance its utility.