When doing a copy design on a large project, it is very difficult to know what parts need to be copied. You either have to be very familiar with the project or first go into inventor and manually create a list of parts that need to be in the copy design.
I would like to be able to choose the parts that need to be copied from a graphics window first (where I can see the parts in the context of the assembly), then have a chance to name them. I know that we get a preview of the part in the copy design (well sometimes) dialog, but that is not always enough to tell the difference in the parts.
We found a terrible limitation of Vault regarding Folder security. If you define a folder security to deny access to a group of user, this groups can even found files in this folder because the file lifecycle give this right.
This limitation has no sense. If the folder deny access to a group of users, all files in this folder must be denied too.
Actually, the only workaround I found is to create a specific lifecycle for files in this folder but this became very complicated.
How Vault must works: ACL on a files must be a combination of all ACL show example in attach.
Would like to see drawing compare added back into Vault. This was part of Design Review several years ago and it allowed you to overlay two .idw's and it would identify the differences. This was removed in about the 2008/2009 release of Vault/Design Review. It was similar to the BOM compare. And...it did work. We often need to compare the .idw's attached to an item from one revision to another. We lost alot when this feature left.
Currently, so I am told, there is no integration between Item properties and those in File Store on the same object.
Example: A file in File Store is at Revision 0, you assign it to an Item in the Item Master. In Item Master change the revision (manually or through an ECO or Lifecycle change), and push that revision out to the CAD file (idw or ipt etc). Make changes to the CAD file, save and check back in to Vault. The file in File Store is still at Rev 0, though the ITEM is at Rev 1.
Linked with this, the Vault Revision Table.... pulls it's Revision value from the File Store value... so if it's not in sync with Item Master... it becomes a useless tool.
When it is being sold as the integration point for Vault, the Item Master is inadequate.
First, lifecycles for items should be as configurable as for files. If you use the system as intended and control the lifecycle of the file through the item, you are severely constricted.
Items should assume the properties of the files that created them, or they should be easily called through the API.
Given the possibility that an item could be created before the CAD representation exists, there needs to be an ability to attach a CAD file as a representation of an item after the item has been created (this is also a huge hurdle if a company converts a product from 2D to 3D).
Document item types should exist so that external applications can reference and control files that don't represent parts.
OR do away with the item master and integrate the BOM capabilities (for 2D and 3D) of item master into the file interface and do away with item master altogether.
This would probably help with any plm integration, PLM360 included.
When I want to relinquish ownership of a file(s) and uncheck this box, I often don't want to apply it to all the files, but because there is not other method at this point but to go into the vault and regain ownership of the files that you want. In this case I have a factory file that I am checking in certain members and want to release ownership of, but not the parent factory file. I would like to see this option be able to select which files to apply this to.