Hello
I would like to know if it is possible to work with 2 companies on the same assembly considering that some assemblies will be created by Solidworks and others by Inventor?
How should we proceed?
Thank you for your comments
Kind regards
Marc
Hello
I would like to know if it is possible to work with 2 companies on the same assembly considering that some assemblies will be created by Solidworks and others by Inventor?
How should we proceed?
Thank you for your comments
Kind regards
Marc
@m.hervigo Welcome
The most important thing is to structure well who is the master's degree. In other words, who is the integrator.
For example, if in the master assembly everyone can add or modify freely, it's a guaranteed mess.
You have to be sure to always work at the assembly level because if one works at the assembly level and the other supplies the part, there are strict rules to be respected. (cf. the notion of reserved space in aviation or for the automobile, the dimension system refers to a single point located on the vehicle.
The files of a 2020 version on the one hand and the 2023 version on the other and I'm not talking about the conversion for the integration (neutral or non-neutral files, etc...).
I experimented with this on a big project and I still have hair growing inside my head. In the end, everyone moved to SW.
From what I saw on the forum, many of our colleagues have given up on having two software programs because they are too complicated. They will explain this to you very well.
Kind regards
Hello;
I urge you to take a look at the discussion of our colleague @OBI_WAN:
I share @Zozo_mp opinion (even without a medal), you have to define a context, rules, and an extremely rigorous working environment to share designs between two different software.
Kind regards.
I mostly have the impression that it does extra work. You won't be able to have both types of native files in the same assembly (unless I'm mistaken?)
This will force you to play STEP and file not up to date
Hello
Normally with 3DInterconnect on the SW side no need to do step, SW opens the native directly.
In theory, an update of the native file can update the file imported into SW (while remaining on the same native file).
The example shown in systematics in SW's demos on this subject is on a crankcase containing batteries for a prosthetic arm if I don't make a mistake.