Friday afternoon, a quarter past four. Two engineers are racing a deadline on the same machine: one is adjusting the frame, the other the guarding. Because the network drive is slow, both copied the project folder to their local disk that morning. Around five they copy their work back to the server, one just after the other. Monday morning the frame is back to square one: the last copy won. Nobody did anything strange, and yet half a day of work is gone.
As soon as a machine grows too big for one person, learning to collaborate on an Inventor assembly becomes a discipline of its own. One assembly quickly consists of hundreds of files referencing each other, and everything silently assumes a single engineer who can touch it all. With two or three people in the same machine, you only win with clear ground rules. In this article: how to split a machine into work areas, which rules to agree on for shared parts, and why folder structure and naming suddenly matter twice as much. Tooling such as Thundercad then takes the friction out of the daily switching.
Why parallel work goes wrong so quickly
Three mechanisms cause nearly all the misery. The first is the local copy, as above: once files live outside the shared source, chance decides which version survives. The second is doubly opened work: two people have the same file open in their own session, and only when saving does it turn out one of them has been working for nothing. The third is moving and renaming: what counts as tidying up for one person means broken references for the other at the next open.
None of the three is solved with carefulness or good intentions. You solve them with division: making sure two people rarely meet in the same file in the first place.
Split the machine into work areas with one owner each
The most important agreement is the division: cut the machine into subassemblies that each have exactly one owner. Frame, drive, transport, guarding and piping are logical boundaries on an average machine. The owner is the only one who changes anything inside his area; everyone else uses it as a given. An assembly structure that felt logical when you worked alone is rarely the structure three people can work in parallel with, so expect some restructuring first.
Four rules of thumb keep the division workable:
- A work area is what one person can oversee in this phase; better six small areas than three oversized ones.
- Keep the seams small: the fewer parts that appear in two areas, the less coordination every change costs.
- Fix the interfaces up front: connection dimensions, mounting patterns and reserved spaces are frozen the moment parallel work starts.
- The top-level assembly has one custodian; only the custodian merges work areas, and nobody else changes anything at that level.
Make the division visible in the structure itself, too. Give every subassembly a recognizable name that includes the work area, and keep the parts of an area together in that area's folder. That way everyone can tell from path and name whose territory something is, before a single file is opened.
The pleasant side effect: starting up becomes simple. With Batch Open you open all files of your subassembly in one go in the morning and continue right where you left off, without clicking through the entire machine first.
Shared parts: look, but do not touch
However well you divide, a few parts remain everyone's. The frame every module hangs on. The standard and library parts. The platforms where two work areas meet. For that category, stricter rules apply than for the rest:
- Library and standard parts are read-only for everyone. If a standard part does not fit, you replace it, you do not rebuild it.
- Shared manufactured parts have one owner, just like work areas. If you need a hole, slot or bracket added in someone else's part, you report it to the owner and the owner applies it.
- Changes to interfaces are never silent. One short message to all owners before you touch a frozen dimension, however small the change seems.
The second point especially chafes in practice, because it feels slower than just drilling that hole yourself. But that one private hole is exactly how a frame ends up full of surprises after three weeks of parallel work, surprises nobody can explain anymore.
Ground rules take discipline; tooling makes them sustainable. With Batch Open from Thundercad your entire work area is ready in one go, and with Quick save you park your complete session when another order cuts in.
Try 30 days freeFolder structure and naming suddenly count double
Working alone, you get away with private logic: after all, you know where everything is and what "plate_new_final" means. With three people in the same machine, every quirk becomes a tripwire. Searching then costs not only your time, but also the time of the colleague trying to guess your structure.
Three agreements catch most of it: one shared project file for the whole team, one workspace structure on the shared source with a fixed place per work area, and predictable file names following one agreed pattern. How to set up workspace, libraries and project file properly is covered in Order in your Inventor project folders: workspace, libraries and project file; for teams that article is not background reading but a precondition.
And the most important rule, after the Friday afternoon from the introduction: work happens on the source, not on local copies. If the network drive is too slow for that, then that is the problem to solve, not something to copy your way around.
When agreements are no longer enough
Ground rules scale up to a point. When the team grows, several machines run in parallel, or someone works remotely, there will always be a moment where two people cross paths anyway. For that situation there is a structural solution: Vault. You check files out before working in them and back in when you are done, with version history; the agreements that rely on trust above are then enforced by the system.
The division into work areas and the rules for shared parts remain the core even with Vault: a system enforces, but it does not divide. How to make Inventor and Vault work together smoothly is covered in Inventor + Vault: streamlining your workflow.
Frequently asked questions
Can two engineers really work on the same assembly at the same time?
In different subassemblies: yes, that works fine. In the same part or the same subassembly: no, and no agreement or system gets around that. Work one after the other, or split the part so each gets their own piece. The art is dividing the machine so that this situation becomes rare.
How do you keep the top-level assembly current without everyone working in it?
Appoint one custodian and agree on fixed moments when the work areas are merged, for example at the end of the day. In between, the rest of the team opens the top-level assembly only to look and measure, not to change. That single channel prevents most collisions at the top.
From what team size is Vault worth it?
There is no fixed threshold, but the signals are clear: things still occasionally go wrong despite good agreements, several machines run in parallel, or someone works remotely. Until then, work areas and discipline get you surprisingly far. If you want to remove the daily friction in the meantime, try Thundercad 30 days for free.