I'm looking into setting up an active BOM for my production team using items of manufactured and purchased parts of the final assembly. Other posts such as the one listed below, by my understanding, mention the file and item revisions are mutually exclusive.
This is a point of concern from our managers as we would have to create duplicate parts to bypass existing revisions, ensuring the revision downstream an assembly to its parts are on the same revision.
https://forums.autodesk.com/t5/vault-forum/file-revision-to-item-revision/td-p/10626079
We have assemblies and parts on separate revision cycles, so its possible for several parts to be used across multiple product lines and not require dedicated parts for different products at differing revisions. Our philosophy is to make as many universal parts as possible, then create parts tailored to our separate customers.
However, we enter situations where several assemblies using similar parts are at different revisions, but those common parts are set at the same revision across each assembly. To that end, it may take several separate part revisions before we deem an update to an entire assembly necessary.
Given that we also want to curate all BOMs exclusively within the Vault, what would be the best approach for revision cycles? As my team uses Vault Pro 2022, have any updates allowed syncing between file and item revision states? Otherwise, would we need to re-examine our internal documentation lifecycles?
