CAD Interoperability Reference

Moving a design between software ecosystems is not just a question of whether one application can open a file. The useful result depends on what survives the handoff: shape, topology, product structure, design intent, engineering meaning, spatial context, visual data, or manufacturing information.

Use this reference to plan an exchange around the work that follows it. Frame the decision as:

source environment → transfer mechanism or representation → destination environment → information that must survive → downstream objective → validation evidence

Use that frame in three passes: name the source, representation, destination, and downstream task; identify which information layers are required, useful, or acceptable to lose; then define the evidence that will show the received result is fit for that task.

Read compatibility claims carefully

An application opening or importing a file proves only that some part of the representation was accepted. It does not by itself show that the required geometry, structure, semantics, dependencies, editability, or downstream behavior survived.

Before relying on a route, check four boundaries:

• Direction and context: Is the source, destination, transfer direction, product release, profile, or translator context stated?
• Information scope: Which layers are preserved, transformed, omitted, or still unknown?
• Package completeness: Are linked files, external references, units, coordinates, appearances, or other dependencies part of the handoff?
• Acceptance evidence: What will you inspect or test in the destination, and what result is sufficient for the next task?

This keeps a format or support statement from being mistaken for proof of a usable exchange.

Start with what must survive

Choose the information layer that matters most to the next task:

• Preservation strategy — Define requirements, distinguish compatibility from usefulness, and set evidence and acceptance criteria.
• Geometry, topology, and mesh fidelity — Assess exact shape, tessellation, topology, and geometric health.
• Product structure, identity, and references — Plan for assemblies, instances, configurations, identifiers, external links, and dependencies.
• Editability and design intent — Set realistic expectations for features, parameters, constraints, histories, and direct editing.
• Engineering semantics and documentation — Preserve or verify PMI, annotations, drawings, materials, metadata, and classifications.
• Spatial context and BIM exchange — Check units, axes, transforms, coordinate systems, BIM schemas, model views, and information requirements.
• Visual scenes and asset exchange — Account for scene graphs, appearances, textures, cameras, animation, composition, and asset dependencies.
• Manufacturing, fabrication, and quality handoffs — Plan exchanges for CAM/CNC, additive work, fabrication, metrology, inspection, and quality data.

Then choose the exchange path

Once the required information is clear, examine the representation and route:

• Formats, profiles, and translators — Understand schemas, profiles, extensions, encodings, versions, and translator behavior.
• Ecosystem routes and collaborative exchange — Compare bounded direct, neutral, and mediated routes for a stated source, destination, and objective.
• Transfer failures and recovery — Diagnose missing dependencies, conversion failures, data-layer loss, and acceptance failures without assuming that repair restores lost meaning.

Finish with validation

An import that completes is not necessarily a successful handoff. Use validation to compare the received result with the purpose it must serve. Check the relevant geometry, structure, semantics, coordinates, visual assets, manufacturing data, version context, and dependencies. For important exchanges, define what evidence will be retained so another person can reproduce, inspect, or retrieve the result later.

The final category, Validation, Exchange Control, and Long-Term Reuse, covers acceptance checks, reproducible delivery packages, round trips, conformance context, archival, retrieval, and reuse.

Task journeys

Use the following paths when the immediate goal is clear:

• Continue editing a model: preservation strategy → geometry, structure, editability, and engineering semantics → formats and translators → ecosystem route → validation.
• Deliver design data to a supplier: preservation strategy → geometry, structure, and engineering semantics → formats and translators → ecosystem route → validation.
• Prepare CAM, fabrication, or additive work: preservation strategy → geometry, engineering semantics, and manufacturing handoff → formats and translators → ecosystem route → validation.
• Coordinate BIM or spatial data: preservation strategy → structure, engineering semantics, and spatial context → formats and translators → ecosystem route → validation.
• Render or exchange visual assets: preservation strategy → geometry, structure, and visual scenes → formats and translators → ecosystem route → validation.
• Recover from a bad transfer: transfer failures and recovery → affected information layer → formats and translators or ecosystem route → validation.
• Preserve data for later reuse: preservation strategy → affected information layers → formats and translators or ecosystem route → validation.

This portal treats technical support, standards conformance, observed preservation, retained editability, and practical usefulness as different claims. A route is useful only when its result is adequate for the destination task.

About this reference

Read about this reference to see how the portal handles exchange claims, scope, uncertainty, and independence. The Terms of Service describe the conditions for using the site, and the Privacy Policy explains its current approach to website requests, browser-side search, and technical delivery data.