3DInterconnect is a SOLIDWORKS technology that allows users to easily open non-native SOLIDWORKS files. It was introduced in 2017 and has changed how we can communicate between teams using various CAD applications. For example, you might work with a vendor that uses Autodesk or Siemens products and want to design in context to those CAD files. In the past, users had to request CAD-neutral formats like STEP or IGES to communicate back and forth. Now, communication is more seamless and those files can be left in the native format. Here, we are focusing on data exchange within the 3DEXPERIENCE Platform.
Imported CAD with 3DEXPERIENCE
It is recommended to leave the 3DInterconnect import checked on as seen below. I set the option to not “Create 3D Interconnect links”. Let’s look at what this does:
SOLIDWORKS Import options for 3DInterconnect
I downloaded a bearing from McMaster-Carr in the neutral STEP format. As seen in the SOLIDWORKS FeatureManager Design Tree on the left, the SOLIDWORKS part icon looks normal; having just a simple yellow block.
Imported non-SOLIDWORKS bearing without link
After saving to 3DEXPERIENCE, both files (the assembly it was inserted into and the ball bearing itself) will be shown as up to date in 3DEXPERIENCE.
Keeping 3DInterconnect Links
For the next scenario, I checked “Create 3DInterconnect links” in the same system options discussed previously. If this is enabled, SOLIDWORKS FeatureManager Design Tree shows a green left-facing arrow indicating a live link to the referenced file. Ultimately, if the referenced file updates then we can pull those updates into our SOLIDWORKS window without having to create a new file.
Imported non-SOLIDWORKS bearing with link
If the option to “Create 3DInterconnect links” is left checked in the System Options, it would be recommended to break before saving. This can be done by right-clicking the file in the SOLIDWORKS FeatureManager Design Tree.
Break Links for 3DInterconnect
Had we left the live link with 3DInterconnect (indicated by the green arrow in the feature tree) we could run into some issues. After we delete the imported file from the local cache or if a different user on a another computer opens up the assembly, SOLIDWORKS would have to deal with locating the file references.
If the live link with 3DInterconnect is left on the ball bearing is not seen by 3DEXPERIENCE. An end user would only see an orange floppy disk icon with no PLM information attached. Additionally, the “File>Find References” command reveals the original path of the object. These are all indicators that the referenced file is not handled properly in 3DEXPERIENCE.
SOLIDWORKS Find References
Addressing Multi-CAD Formats with 3DEXPERIENCE
Handling multiple CAD formats in 3DEXPERIENCE can be tedious but it could be made simpler by understanding how to treat the import engine handles external references. By breaking the link to the source object, once the user uploads to 3DEXPERIENCE the platform controls the neutral CAD format. This means the link on the non-SOLIDWORKS file on the local user’s computer is no longer in control.
To learn more about migration into 3DEXPERIENCE or other cloud functionality register for one of our upcoming training classes here.
