Linked assembly

[Nejc.Leban]

Hi everyone,

I am searching for a solution for creating a linked or derived assembly with multiple components, let's call them Original and Derived. The Original assembly would be created first, consisting of multiple components. Then at a certain point, I would decide that I need a similar assembly, which would contain the same components as the Original assembly, except for those I choose to remove or add to the Derived assembly. Let's say I have Part1, Part2 and Part3 in Original assembly. I would like the Derived assembly to contain Part1 and Part2, but add a new Part4 instead of Part3. Also, adding new parts later to the Original assembly, they would also be included in the Derived assembly, unless I remove them.

Is something like this possible?

Thanks to anyone taking the time to provide a solution.

Best regards,

Nejc

[kacper.suchomski]

Model States / iLogic variants?

[johnsonshiue]

Hi! Two approaches. You may save the original assembly as a new assembly. You may do whatever you like that the new assembly. It can be inserted back to the original assembly as a subassembly.

Another approach is a bit exotic but it should work also. It is to leverage the associative STEP import. Basically, you hide or suppress certain components and then export it as STEP. Rename it so that it does not conflict with the original assembly. Next, import the STEP file as a reference back to the original assembly.

When there is a need to "update", you may simply export the assembly again to the STEP. The original assembly will update.

Many thanks!

[Nejc.Leban]

Thanks @kacper.suchomski 

I'll give it a try using Model states, haven't used that before. I will need some time, but I'll let you know if it worked the way I want it to.

@johnsonshiue I think you might have misunderstood what exactly my problem is. I need to create a drawing and BOM for both assemblies. If I insert the new assembly into the original as subassembly, some parts will be duplicates and the parts that I only want in the new assembly will also be in the original assembly.

[johnsonshiue]

Hi! To avoid double-counting, you may set the linked assembly to Reference. Certainly, if you want more granular control of BOM structure for individual components, the STEP reference import approach will not work.

Many thanks!

[Nejc.Leban]

Hi Johnson.

Yeah, I could set it as reference, but why would I insert the new file as a subassembly then in the first place?

The original has 3 parts. I want those 3 parts in the original, but in the new assembly, I would like to replace one of the parts with a new part. Then if I change one of the other 2 parts in the original, I would also like them to change in the new assembly. Or, if I add a new part to the original, I would also like it to exist in the new assembly.

Why insert the new assembly as reference in the original? I don't understand the workflow. 

Thanks.