Release items from different projects in one workflow or when changing items - do it once for everywhere it is used and release across everything its associated with

[aaron37SWJ]

Like most modern manufacturing companies, we try our best to standarise parts/assemblies so we can use these in multiple projects, spare parts, assemblies, sub-assemblies to keep inventory, storage space and stock levels down to avoid un-necessary costs to the business. We would really like to see a function where we can run a workflow to change all assemblies where-used at once. It is a massive inconvenience to have to run a workflow on every project that a part or assembly is linked too, ideally we would just check a box in the where used list to update all the linked projects and assemblies at once. 

If there is a way to do this already could you please point me in the direction of the help pages.

Thanks 

[andreja.schneider]

Hi @aaron37SWJ,

could you give us more information about your use case. Would you maybe like to update item versions in all projects to latest revision in the system, all at once? Or would you like it to only to update from development to released version?

Best regards,

Andreja Schneider

[aaron37SWJ]

@andreja.schneider your first example is what we mean for part of my suggestion, I know it gives you the little exclamation warning mark stating that the item isn't the latest version on assemblies you haven't updated but you have to go into every project and assembly and update them manually. All at once would be a lot better and save a lot of time.

The other part of this suggestion is when you send one assembly for release that shares common parts with another assembly from a different project you have to wait until sign off on the first before you can send the second assembly off for release, ideally, we could add the second assembly to the same workflow so everything gets released at the same time with no downtime or additional workflows.

For example, shopping in a big department store, imagine having to pay for the goods in each section separately before moving into the next section. Instead we just collect all the goods we need (in our cart) and make one transaction at the end.

Hope this helps

Thanks

Aaron

[andreja.schneider]

Hi @aaron37SWJ ,

since your suggestion might impact large number of assemblies in different conditions, would it be helpful to have a copy button next to assembly in item's where used tab? Impacted children can be loaded in right details within CR, user can review the where used and decide which impacted assemblies to additionally copy and then paste to same opened CR.

Best regards,

Andreja Schneider

[aaron37SWJ]

Hey @andreja.schneider,

I think that would work, it definitely sounds like the right direction. It is quite the challenge documenting requests when you can visualize how it could possibly work, it's getting that visualization to paper that is hard. How would it work with assemblies already in the released state? 

It gets a bit complicated when you have the same part used over 4 or 5 assemblies sometimes even more, all you want to do is update that part/item and that change to follow through into all where-used assemblies in one go without having to move all the parents to development then back to release.

From our process model, when changing a single item, that item is the only item that goes through a major revision change, all parent items go through a minor revision change due to the nature of how Upchain works its hierarchy. 

I hope that makes some sort of sense.

Thanks

Aaron

[andreja.schneider]

Hi @aaron37SWJ ,

maybe would be worth your time to check out our effective date BOM functionality https://help.autodesk.com/view/UPCHN/ENU/?guid=UC_ProjectManagement_pm_projects_pm_effectivity_fltr_.... If you configure your projects to a future date (e.g. December 31, 2024), your effective date BOM filter would always show all the latest item version in the system of all the children, without the need to update the parent assembly (unless you want to, of course). Please review available help documentation and maybe have a trial project set up to check how it behaves in regards to your required process.

Best regards,

Andreja Schneider