Multi-CAD workplace

[mattpeneguy]

This should really be a huge red flag that you are going in the wrong direction from SE to SW! And to be honest this appears, on the surface, to be a process issue to some degree.

But if you haven’t heard SW and SE are both Parasolid software. So export the solid in Parasolid…then you really don’t have a translation. You are just opening a source file. As for drawings well, that has never worked- at least in this direction SW to SE…now if you want to go from SW to SE that is a totally different animal..did you know that SE will open and read the SW drawing file and totally recreate the drawing file in SE? Yep! So now you can open the SW solid in SE, apply parametrics if you want and have the drawing…and about those assy contraints…yep those get pulled into SE as well! See you are just going in the wrong direction.
The funny part is that SE is actually using the SW API tools to do all the work for the drawing and assy constraint “translations”!!

Makes sense considering Seimens owns the kernel and Dassault licenses it. That’s probably one of the reasons that SE has synchronous and SW doesn’t, too.

[bnemec]

This should really be a huge red flag that you are going in the wrong direction from SE to SW! And to be honest this appears, on the surface, to be a process issue to some degree.

Yeah, hind sight 20/20. The hook was pretty well set by the time things became obvious. There’s definitely process issues, main two are we didn’t know what process to use in the new system and users were/are so change saturated that they didn’t get all the new processes that we tried to lay out.

[m2shell]

Over the past 3 years I have been slowly transitioning from Solidworks for everything to AutoCad for all submittals and Solidworks for piece details & fabrication drawings.