Exporting Model Tree Folders in a STEP File

[morbanTWYUB]

In my searching on the forums I couldn't find an example that specifically deals with this issue. As the title suggests, I'm wondering if it is possible to export a file folder from the model tree as part of a step file to keep sub-components more organized in the assembly.

We typically use content center to add in hardware (bolts, nuts, washers, dowels, etc.) to our models so we have a record of them as part of the BOM. As part of a top level assembly, that can be a lot of part files, so we group them in a new folder created in the model tree. While this helps with the organization for our native inventor files, we have customers asking us to "clean up" the main assembly by grouping all these hardware components together.

Our path forward so far has been to have a separate sub assembly for all the hardware components, but this can cause problems with constraints and top level BOM structure. This is doable, but is a lot of work to simply export a file for our customers to look at. For clarity, we have also tried exporting a file without hardware for their approval and the first comment we get is how we are missing hardware from the assembly. 

Does anyone know of a simple way to accomplish this sort of task or are we in the territory of more complicated things like adaptive parts/constraints and ilogic?

Any help is much appreciated! 

[Gabriel_Watson]

Simply create Model States where you Suppress an entire folder that has certain types of components. You can export a model state by activating it and the usual Export > CAD Format (STP). At least that is the easy way I can think of doing so.

[morbanTWYUB]

That sounds like it would remove the hardware from view when we export the step file. That sounds like it would work for us, making it easy to have the hardware visible or not, but that's not what our customer is requesting.

The dilemma is that they want the hardware visible in the step file, but all collected together so when they open it (in Solidworks, I believe) they don't have a lot of "orphaned" hardware components in their assembly to scroll through.

It certainly sounds like this is as tricky of an issue as we originally thought.

[Gabriel_Watson]

I see. Well, my solution then would be to first simplify all the hardware/purchased components into a single IPT, then add this IPT (named as "substitute") to your "SUPPRESSED HARDWARE" Model State.

For that, you need to start a new part, pick "Derive" and select your "HARDWARE ONLY" Model State on the original assembly, then BREAK LINK to the original assembly, and save your substitute part. Finally, add this part to your SUPPRESSED HARDWARE Model State in the original assembly. Remove it from the BOM as needed, but leave it unsuppressed for visual reference.