CAD Data Exchange That Does Not Destroy Your Geometry
CAD Data Exchange That Does Not Destroy Your Geometry
CAD data exchange is the silent tax on every multi-vendor machine project. The STEP file looks fine in the viewer, and then the flange face is missing, the hole pattern is 0.05 off, or the solid converts into a shell with a broken face. This article covers the practical CAD data exchange rules for machine builders who send and receive models every day.
Understand What Each Format Actually Carries
The format choice decides what survives the exchange. Each format has a purpose, and using the wrong one is the root of most geometry problems.
| Format | Carries | Best for |
|—|—|—|
| STEP | B-rep solid geometry | The default for mechanical exchange |
| IGES | Curves and surfaces | Legacy and surface-heavy exchange |
| Parasolid | Solid kernels and history | Same-kernel exchange, fastest and cleanest |
| STL | Faceted mesh | Visualization, 3D printing, not for machining |
| Native CAD | Full history and features | Only within the same CAD system |
STEP is the workhorse, but it carries geometry without the history. The receiving engineer gets a dumb solid, not the feature tree, so downstream edits are harder. That is the trade, and the designer should plan for it.
The STEP Settings That Matter
STEP export looks like one button, but the settings decide the quality. The common problems come from the export tolerance, the surface representation, and the units.
The practical export settings:
• Export the geometry with the same tolerance as the CAD system’s modeling tolerance, typically 0.01 mm or better.
• Check the units: a file exported in inches and read in millimeters is a part ten times too big.
• Use the AP214 or AP242 application protocol for mechanical parts; AP203 is older and surface-oriented.
• Verify the advanced face representation is included, so the receiving system can re-tessellate accurately.
• Export the exact geometry, not the tessellated display geometry.
A quick sanity check after export: open the file in a free viewer and measure the critical dimensions. A part that measures correctly in the viewer is a part that will mostly survive the real exchange.
What Goes Wrong in Practice
The failure modes of CAD exchange are predictable, and knowing them makes the review faster.
The common failures:
Missing faces or slivers: the export tolerance was too coarse, or the source model had poor surfaces.
Broken topology: the receiving kernel re-tessellates and the faces do not close.
Unit errors: the model is 25.4 times too big or too small.
Lost references: the receiving model has no mates or constraints, only bare geometry.
Faceted surfaces: the source exported tessellation instead of exact geometry.
The reviewing engineer should check the model integrity first: the volume, the face count, the hole positions, and the overall dimensions. A volume that matches the source within 1% is a model that exchanged cleanly.
The Exchange Procedure That Works
The reliable CAD exchange is a procedure, not a single export button.
The procedure:
Clean the source model: purge unused bodies, suppress small fillets if they cause trouble, fix the surfaces.
Export with the right settings and the right units.
Open the file in a neutral viewer and check the dimensions and the volume.
Import into the target system and run a geometry check tool.
Fix the broken features in the target system, with the source model as the reference.
Confirm the critical interfaces: bolt circles, mating faces, and datum features.
The last step is the one most teams skip. The exchange is not done when the file opens; it is done when the critical features match the source within tolerance.
Managing the Model Size
A large assembly exchanged as one STEP file is a monster: slow to open, hard to navigate, and likely to have a broken face somewhere deep inside.
The practical strategy:
• Exchange the interface-relevant geometry, not the full internal detail.
• Use a simplified or lightweight representation for the non-critical parts.
• Split the assembly into logical subassemblies and exchange them separately.
• Use the native format for same-CAD partners and STEP for the rest.
The goal is the minimum geometry that supports the decision at hand. A full-detail model of every bolt and spring is wasted bandwidth if the receiving team only needs the mounting envelope.
The Naming and Revision Convention
The CAD exchange is only as good as the file management around it. A file called “final_final_v3_really.step” is a reliability problem before anyone opens it.
The rules that prevent chaos:
• Use a consistent naming convention: project, part number, revision, date.
• Keep the revision in the file metadata and the filename.
• Include an assembly relationship document with the exchange, so the receiving team knows what mates to what.
• Version the exchange, and record the source CAD version in the notes.
• Keep the source and the exchanged model in the same folder tree, so the history is traceable.
A receiving engineer who can find the right revision and the source model is a receiving engineer who can fix the geometry. One who gets a file called “model.stp” with no context will rebuild the part from the drawing and introduce new errors.
When Native Exchange Is Better
STEP is the universal fallback, but it is not always the best. When the partner uses the same CAD kernel or the same CAD system, the native format wins.
The priority order for a clean exchange:
Same CAD system: native file, no exchange needed.
Same kernel (Parasolid to Parasolid): native kernel file, cleanest.
Different systems: STEP with careful settings, or a direct translator.
Legacy or surface work: IGES.
Visualization only: STL or a lightweight 3D PDF.
The designers who check the partner’s system before exporting save themselves the geometry repair session. The exchange format is a communication decision, and the first rule of communication is to use the language the other side understands.
The Translation Check: Curves and Surfaces
The geometry that survives a CAD exchange is the geometry that was clean in the source. The translator converts, but it cannot heal a bad surface, and a bad surface in the source becomes a broken face in the target.
The common source problems:
Sliver surfaces: long, thin faces that the kernel cannot re-tessellate reliably.
Gaps between faces: the source model has surfaces that do not meet exactly.
Tolerances tighter than the kernel can hold: the exchange rounds the numbers.
Degenerate edges: zero-length edges from trimmed surfaces.
Self-intersecting faces: rare, but fatal to the exchange.
The designer who fixes these in the source, before the export, saves the receiving engineer hours. The tools are in every CAD system: the surface analysis, the edge check, and the solid check. Run them before the export, not after the complaint.
Colors, Attributes, and the Meta Layer
The geometry is only half the exchange; the attributes are the other half. Colors, layer names, material properties, and custom attributes often carry the design intent that the bare geometry cannot express.
The practical rule: keep the attributes minimal and explicit.
• Use layers or colors for the functional groups: frame, moving, fixed, electrical, pneumatic.
• Export the material and the mass properties if the target system can read them.
• Do not rely on the attributes surviving every format; check the target system’s import mapping.
• Keep the critical information, like the surface finish and the heat treatment, in the drawing, not only in the model attributes.
A receiving engineer who opens a model with clean layers and a material assigned can start working. One who opens a model with everything on one layer and no material has to rebuild the context from the drawing.
The Coordinate System and the Origin
The origin and the orientation of the model decide how it lands in the target assembly. A model exported with the wrong origin lands offset, and the receiving engineer has to move it back.
The practical rules:
• Export the model in the assembly coordinate system, aligned to the machine datums.
• Set the origin on a feature that is easy to locate: a mounting face corner, a bore center, or a datum edge.
• Check the orientation before the export: the Z up, the Y forward, matching the target convention.
• Include the origin information in the exchange notes, so the receiving engineer can verify.
The designer who exports with the origin on the mounting corner saves the receiving engineer the “where is this supposed to go” puzzle. The puzzle is where errors enter the assembly.
The Archive and the Audit Trail
The CAD exchange is not a one-time event; it is part of the project record. The exchanged file, the source file, and the exchange notes should live together as an archive.
The archive rules:
• Keep the source model, the exported file, and the exchange log in the same project folder.
• Record the CAD version and the export settings in the log.
• Save the receiving engineer’s verification report.
• Keep the revision history, so the next exchange starts from the right version.
• Back up the archive with the project data, not on a personal drive.
The audit trail turns a geometry dispute into a solvable problem. Without it, the argument is “the file was wrong,” and nobody can prove anything.
The Practical Test: A Pilot Exchange
The exchange procedure is proven on a pilot, and the pilot is the cheapest insurance against a bad geometry at the critical deadline.
The pilot steps:
Pick one representative part: a part with the critical interfaces and the tricky surfaces.
Export it with the chosen settings and the units.
Import it into the target system and run the geometry check.
Compare the critical dimensions and the volume against the source.
Record the differences and adjust the settings or the procedure.
Repeat the pilot with a second part to confirm the fix.
The pilot takes an hour and saves the day before the full model exchange. The team that runs the pilot knows the settings, the pitfalls, and the verification steps before the real deadline, and the exchange stops being a gamble.
The pilot is also the training document: the engineer who runs it can write the exchange procedure for the rest of the team, with the real settings and the real check numbers.
The People Side of the Exchange
The CAD data exchange is a technical process with a people problem at the center. The two engineers on the ends of the file have different systems, different habits, and different definitions of done.
The people rules:
Talk to the receiving engineer before the export, and ask what they actually need.
Send the exchange notes with the file, not in a separate email that gets lost.
Answer the questions quickly: the receiving engineer stuck on a broken import is the bottleneck.
Agree on the naming and the revision convention before the project, not after the confusion.
Record the lessons from each exchange, and share them with the team.
The exchange is a collaboration, and the collaboration is built on the small courtesies: the clean model, the complete notes, the quick answer. The engineer who treats the exchange as a favor to the partner gets the cooperation back when the geometry needs repair.
The best exchange is the one that nobody remembers, because it just worked. The worst exchange is the one that needs a meeting, and the meeting is always about the people, not the file.
Conclusion
CAD data exchange is a communication process with rules, not a magic export button. The format, the settings, the model integrity, the procedure, the size, and the file management all decide whether the geometry survives.
Choose the format for the destination, export with the right settings and units, check the integrity in a viewer, run the import check in the target system, verify the critical features, and manage the files with a naming convention. The flange will line up, the holes will match, and the model will actually be usable on the other side.
