How many parts can one assembly hold before it starts to hurt? A hard maximum does not exist: Inventor will still open a flat list of eight hundred parts just fine. The real question is what it costs you. What began as a tidy machine of fifty parts has grown, through extra work, options and customer wishes, into a browser you scroll through for three screens to find a single plate.
At that point, splitting an assembly into subassemblies in Inventor is no longer cosmetic surgery, it is maintenance on your own working speed. In this article you will read which signals tell you it is time, where the logical places to cut are, and how to restructure after the fact with as little damage as possible to references and drawings, with occasional help from a toolbox like Thundercad.
The signals that it is time to split
An oversized flat assembly announces itself. The most recognisable signals:
- Opening and saving take minutes, and everyone plans their coffee break around them.
- The model browser is one long, unsorted list: searching via the filter bar beats scrolling, and new colleagues cannot find anything.
- Every change, however small, forces the complete assembly to recompute. Editing a bolt pattern feels like holding the whole machine hostage.
- Two engineers cannot work on the project at the same time, because everything hangs off one file.
- The general assembly drawing has become unmanageable: one view with eight hundred items and a parts list that no longer fits on any sheet.
Mind you: slowness alone is no proof that you should split. An assembly can also crawl because of heavy parts, import debris or needless detail. Rule that out first; how to track down the real culprits is covered in Slow Inventor model? How to find the real culprits. If the structure itself turns out to be the brake, read on here.
Logical places to cut
Splitting does not start in Inventor but on paper: where are the natural boundaries of this machine? In practice there are three usable cutting lines, and they do not exclude each other:
- By module or function. Frame, drive, platform, cladding, control cabinet. This is the layout engineers recognise fastest and the one that enables reuse: the drive module of this project becomes the starting point of the next one.
- By build order. Whatever the shop floor welds, assembles or pre-assembles as one unit is a natural subassembly. The fitter then sees the same chunks in the browser as on the workbench.
- By purchasing unit. Whatever you outsource or buy as a whole, such as a complete railing or a hydraulic set, deserves its own branch. The boundary in the model then coincides with the boundary in the order.
Which cut wins? Choose the layout that follows tomorrow's work. If changes and reuse will happen per module, split per module. If everything revolves around the sequence on the shop floor, follow that. One warning belongs here: your assembly structure will reappear one to one as the levels of your BOM, and work preparation looks at that differently than engineering does. We deliberately leave that side of the trade-off out of scope; for that, read Your assembly structure is your BOM structure: build it deliberately. Here we keep our eyes on the model and its performance.
Restructuring starts with an overview of hundreds of files at once. With the toolbox you open, close and park complete work sessions in one action, even in the middle of a rebuild like this.
Try 30 days freeRestructuring after the fact with minimal damage
The safest route is restructuring within the same assembly: create a new subassembly in its place in the tree and move existing parts into it with the demote or restructure function, instead of cutting parts out and placing them again in a new file. When you move things within the same assembly, file references stay intact and drawing views of individual parts simply keep working.
Still, the operation is not free, and it is better to know this up front than to discover it afterwards:
- Constraints on moved parts can break once they cross the new group boundary. Expect to redo a share of them per module, or pin modules down first with a temporary grounding.
- Adaptive relations and patterns that run straight through the new structure deserve a check beforehand: note where they live before you start shuffling.
- Drawings of the top-level assembly can lose views that hung on the old browser order. Open them right after each step, not at the end of the day.
So work in small, verifiable steps: one module at a time, save in between, check the drawings, next module. Park your work in progress first, for instance with Quick save from Thundercad, which stores your complete work session and restores it later exactly as it was: a much calmer way to rebuild. And when you are done, verify the whole tree in one round by using Batch Open to open all files of the assembly at once; broken references then report themselves immediately instead of weeks later at a colleague's desk.
When you are better off not splitting
Splitting is a tool, not a goal. Skip it for a one-off project that will never open again after delivery: the investment will not pay back. Do not do it right before a deadline or a release, because the repaired constraints and verified drawings need time. And do not do it purely for the BOM layout: that can be steered with views and settings without rebuilding the model.
Also watch out for the overcorrection: nesting too deep. Give every bracket its own subassembly and from then on you click through six levels to reach any part, while the shop floor cannot find anything anymore. Three to four levels are enough for most machines; go deeper only if the machine itself is built that way.
Keeping the new structure healthy
A restructure only lasts with a few simple habits. New parts land in the module where they belong, not 'just quickly' at the top level, because ten times 'just quickly' is a new flat list. Every module has an owner who keeps their branch tidy. And at every project meeting, one glance at the browser is enough to see whether the agreement is still alive.
Frequently asked questions
Will I lose constraints when restructuring?
Some, yes. Constraints that stay within a module usually survive the move just fine; relations that cross the new group boundary can break. So restructure module by module and check after every step, and the repair work stays limited to a handful of relations each time.
Do I have to redo my drawings?
Usually not. Views of individual parts and of subassemblies you move within the same assembly keep working. Only the drawing of the top-level assembly needs attention: check views, sections and item balloons right after each restructuring step, and a broken view is a matter of minutes instead of a search.
Does splitting also help against a slow model?
Partly. After splitting you can suppress modules or load them simplified, and that makes a noticeable difference when opening and editing. But if the slowness lives in heavy imported files or leftover debris, it simply moves along into the new structure. If you want to tackle both sides, you can try the clean-up and management tools of Thundercad free for 30 days.