Below are some guidelines for file transfer. JBM® utilizes SolidWorks as its primary CAD tool. Fortunately this package is very versatile and able to handle most formats.

Drawings: Leave in the format the original system uses. For AutoCAD this is the .DWG format. If for some reason this does not work try .DXF. In most cases .DXF is less likely to work than the original drawing format.

3D Models: Leave in the format the original system uses. If this does not work use .SAT if software is ACIS based or .STEP if originating software is Parasolid based. If the originating software format did not work and no one knows the base geometry “kernel”, use .STEP for the first choice.

It may take a couple of tries (or more) the first time CAD software programs attempt to communicate. The customer has likely been through it before. Often five minutes on the phone with the customer will avoid many hours spent cleaning up a bad transfer. One key to customer satisfaction is that we document the format used for successful transfer so future communication goes even smoother.

Data Exchange Table
2D DXF/DWG In and Out for Revisions 12, 13, 14, and 2000 of AutoCAD
STEP In and Out for AP203, In for AP214
IGES In and Out
STL Out (for rapid prototyping)
ACIS (*.SAT) In and Out
X_B (Parasolid Binary) In and Out using the Parasolid Kernel file format.
X_T files In and Out using the Parasolid Kernel file format.
VDAFS (*.VDA) Input and output
TIF image Output
Pro/Engineer files* Input
Unigraphics files Input
Mechanical Desktop files Input
Autodesk Inventor Part Files Input
SolidEdge Part Files Input
XML Files Output
CGR Files Output
VRML Out for the Web

* Pro/Engineer (ProE) releases 200i2 (version 20) and beyond must use STEP for 3D models and DWG for 2D drawings. SolidWorks cannot use the later version Pre/E native output because it is encrypted.