Multi setup project management

[friesendrywall]

I have a project that has 14 cam setups on 6 parts.  I am finding this rather cumbersome at this point, and wondered if anyone has any tips or ideas how to manage this better with the current state of fusion.

Issues I face:

#1. Manage tools->All->Documents->Current Project lists all tools from all jobs with no sort capability.  If there was a way to use a single part from this assembly in another file I could separate them that way, but I don't find a way to do this.

#2.  Hiding or showing a part for different cam ops indicates a need to save, thus yet another version increment.

#3.  This doesn't seem very orderly to me, there could be folders for each part instead of all the parts under one folder.

#4.  Splitting up all these parts to separate files would segment the cam properly, but cad would be a real pain.

https://forums.autodesk.com/t5/ideastation-request-a-feature-or/tool-renumber-by-setup-or-multiple-s...

[LibertyMachine]

I agree that it's messy as can be and chaotic

I don't often work with large assemblies, but when I have, I found this worked well, and something you might want to adopt:

Link the components. Create each individual component and link it into one file. When you are doing your CAM, open up the file that holds that item. With that, you won't have to deal with all the other components and their related CAM stuff

[friesendrywall]

What do you mean by link?  Same as insert into design?

Is there a way to work on the components as a whole in that method, or each component then has to be designed outside of the complete unit?

[LibertyMachine]

Yes, "Insert into Design".

To my understanding, it has to be worked on outside the design. I agree, not efficient. My comfort/knowledge level of assemblies is better than novice, but not by a large margin.

I'm interested in seeing some workflow ideas from Autodesk. @al.whatmough, do you think we could get some solid examples of large assembly file management and how to muddle through on the CAM side? Maybe something @curtis.chan, @xander.luciano or @lars_christensen even?

[Steinwerks]

I tried to make a workflow that makes sense but you can't remove components from the overarching component file when you insert it into another file, so making a separate "assembly" for a single linked component doesn't work, although it SHOULD and would be the best way to do this IMO.

If one starts with a large assembly there doesn't seem to be a way to split out individual pieces at all. It sucks because it creates these lumbering constructs instead of nimble pieces that can be updated as needed via linking them to the original.

[LibertyMachine]

Than perhaps what is needed (in addition to current methods) is also what they (devs) plan on bringing to us to make for easier handling of large assemblies when CAM is concerned?