wmayer wrote: ↑
Wed Nov 25, 2020 11:19 am
... Assembly2, Assembly3 and Assembly4. How do they handle this?
In general they've done the "copy an internal bit from one file and paste that bit into another file", with or without link to the original file.
This is all good and well since that must work as well, but, and this is a big but! (pun intended
To make the whole eco system to work as intended we must also add relative positioning of the whole part-file
(via the separate assy-file principle) AND a PDM-system management (= external database file-juggling).
The two-file principle opens up for these features to be fulfilled.
Relative positioning via the separate assy-file ensures the function for the tiny project as well as for the humongous project spanning several decades and multi continent cooperation as well as storing the relative positions solely in the database.
Just remember that the PDM-system itself is not part of this discussion.
Tiny projects will only use assy-files for relative positioning.
Assy-files will also be used for keeping all part-files together for e.g. casted parts where the mould consists of a lot of moulds as for engine blocks. Or welded parts where every plate is a separate part and every weld is a separate part as well. This usage will make the assy-file work/be utilized as a part-file. For this use case one just denote the assy-file with a part number intsead the part file.
The assy-file will/can also contain positioning dependent sectioning/interfacing data of the constituent parts/assys. E.g. cross sections where multiple sheet metal meet. You can ofcourse add other features as well, only your imagination sets the limits.
So the assy-file can and will have several end usage scenarios.
Big and long lasting projects will utilize some PDM-system with the special feature of storing relative positions in the database in conjunction with the file-juggling.