Creo Unite lets those engineers simply open the specific SolidWorks parts and assemblies needed without translating them. Your Creo engineers now need to add those SolidWorks parts into their assemblies, but don’t want to go through the expensive, painful, and largely redundant process of translating the entire part catalog to Creo all at once. The PTC guys were kind enough to help me understand the market segmentation: these products are for anyone who needs to a) consolidate heterogeneous CAD data into a single system or, b) collaborate in real time in a multi-CAD environment.Ī) You’re a manufacturing company using Creo, and you’ve just acquired a company that uses SolidWorks. (I’ll leave it to the ADSK posse to fill us in in the comments below.) Who cares? Still, by viewing the video above along with a few others, it seems the workflow is pretty much identical. Having only just discovered the An圜AD thingy from Autodesk, I haven’t yet spoken with them about the details. Creo Unite is ostensibly the same product as SolidWorks 3D Interconnect, but about three years earlier. I also thought that editing non-native parts would be non-associative, but that turned out to be incorrect as well. At first, I thought that Creo Unite might lack BREP-level mating for non-native components, but it turns out that it does.

Turns out it’s almost identical to the new SolidWorks offering, at least for CATIA, NX, and SolidWorks files (Inventor and Solid Edge files are only partially supported by Unite).

So, I spent an hour on the phone this morning with Gavin Quinlan at PTC to clear up the details on Creo Unite.

Creo unite