Engineering teams collaborate. Their CAD systems don't.

Moving geometry isn't the same as sharing a design

CAD interoperability has traditionally focused on exchanging files and geometry between systems. That solves an important problem, but only part of it.

An intelligent CAD model contains more than its visible shape. It can contain features, parameters, dimensions, constraints, relationships, references, and other information describing how the design was constructed and how it is intended to behave.

When a design moves between different CAD environments, some of that intelligence may not survive in a form the receiving system can understand and continue to work with.

The geometry may arrive.

The design intelligence behind it may not.

Translation can turn an intelligent design into a representation

Consider a component designed parametrically in one CAD system. The original model may know that a hole is centered on a face, that its diameter is controlled by a parameter, that several features share a relationship, or that changing one dimension should cause other geometry to update.

After exchange into another CAD system, the receiving engineer may get geometrically accurate solids and surfaces without receiving those relationships in an equivalent, editable form.

The result can look like the same design while behaving very differently as an engineering model. That distinction matters when the next engineer needs to do more than view it.

They need to continue designing it.

Real engineering collaboration crosses organizational boundaries

This problem becomes particularly important when different CAD environments are unavoidable. A manufacturer may standardize on one system while a critical supplier uses another. A customer may require deliverables in its preferred environment. An acquired division may have years of engineering information in a different system. A product may pass through many organizations during its lifecycle.

Requiring everyone to adopt the same CAD platform is often impractical. So engineering organizations develop workflows around the differences: translations, derived models, recreated features, disconnected copies, manual comparisons, and repeated verification.

These workflows can enable exchange.

They do not necessarily create shared understanding of the design.

The challenge is bigger than file compatibility

The deeper question is not whether one CAD system can open information created by another. It is whether engineers using different CAD systems can continue to collaborate intelligently on the same design.

That requires preserving more than appearance. It means preserving enough of the meaning, relationships, and intent behind engineering information for another environment — and another engineer — to continue working with it.

From exchange toward collaboration

Engineering software has become extraordinarily capable within individual CAD environments. The opportunity now is to make collaboration across those environments more capable as well.

Sembyl is focused on that gap: moving beyond exchanging representations of engineering designs toward enabling intelligent design collaboration across CAD systems.

Interested in what we're building?

If cross-CAD collaboration is a real challenge in your organization, we'd like to hear from you.

Get in touch