CAD Interoperability Reference

Editability After CAD Exchange: Define the Outcome Before You Transfer

Wed, 02 Sep 2026 00:00:00 +0000

Editability After CAD Exchange: Define the Outcome Before You Transfer

“Editable” is too broad to select a safe CAD exchange route. A model that can be opened, measured, or moved is not necessarily a model whose sketches, constraints, feature relationships, or source-authoring decisions can be changed. Define the next change first; then choose a representation and test that representation against the change.

Choose a CAD Continuity Strategy: Native, Referenced, Converted, or Rebuilt

Wed, 02 Sep 2026 00:00:00 +0000

Choose a CAD Continuity Strategy: Native, Referenced, Converted, or Rebuilt

Choose the continuity strategy from the change and update relationship you need, not from the extension alone. The central decision is who owns the next change and whether changes made elsewhere must continue to arrive.

Feature Recognition and Reconstruction: Recovering Usable Design Control

Wed, 02 Sep 2026 00:00:00 +0000

Feature Recognition and Reconstruction: Recovering Usable Design Control

Recognition and reconstruction can make an imported shape easier to change, but neither should be described as extracting the original feature tree by default. Start by separating the received geometry from the authoring definition that may have produced it.

Validate Editability After Import: Change Tests, Update Tests, and Exit Criteria

Wed, 02 Sep 2026 00:00:00 +0000

Validate Editability After Import: Change Tests, Update Tests, and Exit Criteria

An imported model is editable only for the purpose and conditions that have been demonstrated. Build a small acceptance test around the required change, retain the route context, and test updates only when the workflow promises or needs them.

Coordinate Context in CAD and BIM Exchange: Units, Axes, and Transform Chains

Wed, 02 Sep 2026 00:00:00 +0000

Coordinate Context in CAD and BIM Exchange: Units, Axes, and Transform Chains

Coordinates are numbers. Their meaning comes from the contract around those numbers: the unit, axis convention, frame, origin, and transformations that relate one frame to another. A transfer can preserve valid geometry while changing its scale, orientation, or location if that context is omitted or interpreted differently.

Define a CAD Data Handoff Before You Export

Wed, 02 Sep 2026 00:00:00 +0000

Define a CAD Data Handoff Before You Export

An export request becomes useful only when the receiving job is explicit. “Export it as STEP” may identify a representation, but it does not say whether the recipient needs a watertight shape, an editable design, assembly identity, PMI, a manufacturing result, or simply a visual reference.

Define a Visual Handoff: What Must Survive Beyond the Mesh

Wed, 02 Sep 2026 00:00:00 +0000

Define a Visual Handoff: What Must Survive Beyond the Mesh

A visual handoff is successful when the receiving workflow can produce the intended result from the delivered scene. A mesh that opens, or a screenshot that looks similar, does not establish that the scene relationships, appearance resources, views, or motion survived.

Define an Acceptance Case for a CAD Exchange

Wed, 02 Sep 2026 00:00:00 +0000

Define an Acceptance Case for a CAD Exchange

“The file opened” is an observation. An acceptance case states whether the received data is usable for a named task, under a named exchange condition, with evidence that another person can inspect.

Exact Geometry, Tessellations, and Meshes: Choose the Representation That Can Carry the Required Shape

Wed, 02 Sep 2026 00:00:00 +0000

Exact Geometry, Tessellations, and Meshes: Choose the Representation That Can Carry the Required Shape

Choose an exchange representation from the information the receiving task must use. “The file opens” and “the object looks recognizable” are weak tests: neither tells you whether the receiver got exact surfaces, usable topology, an adequate approximation, or only a display mesh.

Format, Schema, Profile, Encoding, and Extension: What a File Label Does—and Does Not—Tell You

Wed, 02 Sep 2026 00:00:00 +0000

Format, Schema, Profile, Encoding, and Extension: What a File Label Does—and Does Not—Tell You

“It is a STEP file” or “the receiver supports IFC” is not yet an exchange specification. A useful compatibility description identifies what the representation means, which scope of the standard is in use, how it is encoded, what it depends on, and which direction the receiving product supports.

Manufacturing-Ready vs. Geometry-Only CAD Handoffs

Wed, 02 Sep 2026 00:00:00 +0000

Manufacturing-Ready vs. Geometry-Only CAD Handoffs

“Manufacturing-ready” has no useful meaning without a named downstream task. A file may contain an accurate shape for a CAM programmer, but not the process plan, machine context, or inspection information that another recipient needs. Treat readiness as a claim about a source, a transfer, a recipient, and an objective—not as a property guaranteed by a file extension.

Structure as Data: Why an Assembly Is More Than Its Parts

Wed, 02 Sep 2026 00:00:00 +0000

Structure as Data: Why an Assembly Is More Than Its Parts

An assembly can fail as a handoff even when every component opens and looks correct. The missing information may be the hierarchy that says which components form a subassembly, the occurrence that says where a reused part belongs, or the relationship that tells the receiver how the whole is organized.

CAD Interoperability Claims: Support, Conformance, Preservation, and Fitness for Purpose

Wed, 02 Sep 2026 00:00:00 +0000

CAD Interoperability Claims: Support, Conformance, Preservation, and Fitness for Purpose

“Supported,” “certified,” and “it opens” are useful signals, but they do not answer the same question. The risk is not that one statement is always false; it is that a narrow statement is reused as a blanket promise about a different operation, release, information layer, or downstream task.

CAD-to-CAM/CNC Handoffs: What Must Survive—and What May Be Regenerated

Wed, 02 Sep 2026 00:00:00 +0000

CAD-to-CAM/CNC Handoffs: What Must Survive—and What May Be Regenerated

A CAD-to-CNC exchange crosses more than one boundary. Design data may become CAM input, CAM data may become a controller-specific program, and a shop may add setup or machine context at each stage. An imported solid can be a useful starting point without carrying machining intent or executable output.

Georeferencing a BIM Exchange Without False Alignment

Wed, 02 Sep 2026 00:00:00 +0000

Georeferencing a BIM Exchange Without False Alignment

Georeferencing is the relationship between a model’s engineering or project coordinates and a coordinate reference system used to describe location. It is not just an origin offset. A BIM exchange can overlay another model in one viewer and still lack the information needed to reproduce its position in a different project, system, or tool.

Identity, Instances, and Configurations in a Design Handoff

Wed, 02 Sep 2026 00:00:00 +0000

Identity, Instances, and Configurations in a Design Handoff

Two occurrences can look identical and still mean different things. One may be the first use of a released component; another may be a second use of the same definition, a different configuration, or a replacement awaiting approval. If that context is reduced to unnamed geometry, a recipient may be unable to update, replace, audit, or retrieve the intended design.

Native, Neutral, and Derived Representations: Choose for the Next Job

Wed, 02 Sep 2026 00:00:00 +0000

Native, Neutral, and Derived Representations: Choose for the Next Job

The best representation is the one that carries the information the next task needs with an acceptable amount of translation risk. “Native,” “neutral,” and “derived” describe different exchange strategies; they are not quality rankings.

Scene Graphs, Composition, and Variants: What a Flattened Scene Can Change

Wed, 02 Sep 2026 00:00:00 +0000

Scene Graphs, Composition, and Variants: What a Flattened Scene Can Change

A visual scene is often a graph of relationships, not a folder of independent meshes. Parent transforms, instances, layer opinions, references, payloads, variants, overrides, and asset paths can all affect the scene a receiver resolves. Flattening may make delivery easier, but it changes which relationships remain available.

Test Exchange Packages: Compare What Must Survive

Wed, 02 Sep 2026 00:00:00 +0000

Test Exchange Packages: Compare What Must Survive

A useful exchange test is a small, representative experiment with a stated purpose. It includes the dependencies and context that the real handoff needs, records the source baseline, exercises the real transfer direction, and compares the information layers that the recipient cannot afford to lose.

Topology and Model Health: What Must Remain Connected and Valid After Exchange

Wed, 02 Sep 2026 00:00:00 +0000

Topology and Model Health: What Must Remain Connected and Valid After Exchange

Geometry describes shape; topology describes how pieces of that shape are connected and oriented. A transfer can preserve a recognizable outline while losing the connectivity or validity needed by the next operation.

Additive-Manufacturing Exchange Beyond the Mesh

Wed, 02 Sep 2026 00:00:00 +0000

Additive-Manufacturing Exchange Beyond the Mesh

A triangular mesh describes a surface, but an additive handoff may also need material assignments, lattice structure, production identity, support or machine context, slice data, and package relationships. Judge the exchange against the downstream build-preparation task and the receiver’s declared support—not against the presence of a .3mf suffix alone.

Build a Preservation Map for Design Data

Wed, 02 Sep 2026 00:00:00 +0000

Build a Preservation Map for Design Data

A design transfer does not preserve “the model” as one indivisible thing. It may preserve a shape while losing assembly identity, retain annotations as graphics without usable meaning, or create a visually convincing scene that no longer supports engineering edits. A preservation map makes those distinctions visible before a route is selected.

Conformance, Validation, and Fit for Purpose Are Different Claims

Wed, 02 Sep 2026 00:00:00 +0000

Conformance, Validation, and Fit for Purpose Are Different Claims

“Compatible” compresses several evidence questions into one word. A valid file may still lose the layer a recipient needs, and a scoped certification result may still leave the recipient’s actual task untested.

Define an IFC Exchange Scope: Release, Model View, and Purpose

Wed, 02 Sep 2026 00:00:00 +0000

Define an IFC Exchange Scope: Release, Model View, and Purpose

“Send an IFC” names a file family, not a complete exchange requirement. The recipient still needs to know which schema release, model-view scope, information layers, and downstream task the delivery must serve.

External References, Dependencies, and Portable Design Packages

Wed, 02 Sep 2026 00:00:00 +0000

External References, Dependencies, and Portable Design Packages

A design file is often the visible root of a larger dependency graph. Its useful meaning may depend on linked components, nested references, textures, project or search-path context, versioned documents, or external classification and library information.

Materials, Textures, UVs, and Shader Bindings in Visual Exchange

Wed, 02 Sep 2026 00:00:00 +0000

Materials, Textures, UVs, and Shader Bindings in Visual Exchange

Geometry can arrive intact while the surface appearance changes. The reason is that appearance is a chain of linked data: geometry exposes UV coordinates, a material points to textures or shader networks, texture objects select image resources and samplers, and the receiver interprets those relationships through a rendering context.

Mesh Fidelity: Triangles, Normals, UVs, and Resolution as Transferable Data

Wed, 02 Sep 2026 00:00:00 +0000

Mesh Fidelity: Triangles, Normals, UVs, and Resolution as Transferable Data

Triangle count is only one part of mesh fidelity. A receiving task may depend on vertex positions, triangle indices, primitive topology, normals, tangents, texture coordinates, colors, or application-specific attributes. Each can be present, omitted, regenerated, or interpreted differently.

Schemas, Application Protocols, Model Views, and Extensions: The Scope Inside the Format

Wed, 02 Sep 2026 00:00:00 +0000

Schemas, Application Protocols, Model Views, and Extensions: The Scope Inside the Format

“Supports IFC,” “opens STEP,” or “loads glTF” describes a family label. A useful exchange statement identifies the particular scope inside that family and what happens when the receiver encounters information outside it.

Accepting a Product Structure Transfer: Checks for Reuse, Update, and Archive

Wed, 02 Sep 2026 00:00:00 +0000

Accepting a Product Structure Transfer: Checks for Reuse, Update, and Archive

“The file imported successfully” is an event, not an acceptance decision. A transfer is acceptable only when the received structure supports the task for which it was delivered.

Cameras, Lights, and Animation: Define the Intended Viewing Result

Wed, 02 Sep 2026 00:00:00 +0000

Cameras, Lights, and Animation: Define the Intended Viewing Result

When the deliverable is an approved view, animation, review experience, or render, cameras, lights, and motion are data—not presentation details to reconstruct later. A format may serialize them while leaving important behavior to the receiving application. Define the intended result and test it in the named receiver.

Choose the Right Handoff Expectation: Delivery, Continued Work, Reference, Update, or Round Trip

Wed, 02 Sep 2026 00:00:00 +0000

Choose the Right Handoff Expectation: Delivery, Continued Work, Reference, Update, or Round Trip

The recipient’s ability to open a result does not tell you how the result is expected to behave afterward. A one-way deliverable, a linked reference, and a round trip have different requirements for identity, dependencies, editability, change detection, and acceptance.

Inspection-Ready Digital Handoffs: PMI, Plans, Resources, and Results

Wed, 02 Sep 2026 00:00:00 +0000

Inspection-Ready Digital Handoffs: PMI, Plans, Resources, and Results

Inspection is not only a question of whether a measurement system can open a shape. The recipient also needs to know what characteristics matter, how they are intended to be measured, which resources or templates apply, and where the results belong. An inspection-ready handoff therefore has a traceability problem as well as a geometry problem.

Make a CAD Handoff Reproducible

Wed, 02 Sep 2026 00:00:00 +0000

Make a CAD Handoff Reproducible

A reproducible handoff lets the recipient reconstruct the intended exchange conditions and repeat the relevant checks. It is more than placing the main model in a transfer folder: references, assets, versions, settings, purpose, and acceptance evidence can all change what the recipient receives.

Read, Write, Import, Export: Why Support Is Directional and Version-Bound

Wed, 02 Sep 2026 00:00:00 +0000

Read, Write, Import, Export: Why Support Is Directional and Version-Bound

“Supported” is an incomplete verb. A product may read a representation without writing it, open it without preserving its authoring semantics, or write a version that a particular receiver does not accept. Read support is not a reciprocal promise of write support.

Tolerances, Units, and Tessellation Settings: Control Geometric Precision at Export

Wed, 02 Sep 2026 00:00:00 +0000

Tolerances, Units, and Tessellation Settings: Control Geometric Precision at Export

Precision is not one number. A model’s kernel tolerance, a mesh’s surface deviation, a coordinate unit, a numeric representation, a point spacing, and a measurement uncertainty answer different questions. An exchange is controllable only when those questions are stated separately.

When Geometry Arrives but BIM Meaning Does Not

Wed, 02 Sep 2026 00:00:00 +0000

When Geometry Arrives but BIM Meaning Does Not

A model can display walls, slabs, equipment, and spaces while being unusable for the task that motivated the exchange. Visible geometry answers where surfaces are drawn. It does not necessarily answer what an object is, where it belongs in the project, which system it relates to, or which properties a recipient can rely on.

Control Updates and Round Trips Without Losing the Baseline

Wed, 02 Sep 2026 00:00:00 +0000

Control Updates and Round Trips Without Losing the Baseline

A successful first delivery does not establish that later exports, imports, or returns will preserve the same information. Control an update by keeping the accepted baseline, recording what changed, repeating the relevant checks, and classifying each difference.

Package and Test a Visual Scene Handoff

Wed, 02 Sep 2026 00:00:00 +0000

Package and Test a Visual Scene Handoff

A single file is not automatically a self-contained delivery. A visual scene can depend on sidecar buffers, images, referenced layers, payloads, shader resources, packages, resolver settings, or a receiver-specific feature set. Build a manifest, define the package boundary, and test the actual package in a clean destination context.

Scan-Derived Geometry and Point Clouds: Define the Accuracy and Downstream Handoff You Need

Wed, 02 Sep 2026 00:00:00 +0000

Scan-Derived Geometry and Point Clouds: Define the Accuracy and Downstream Handoff You Need

A scan handoff is more than a file containing many points. The recipient needs to know what was measured, how the datasets were aligned, how the representation was derived, and whether the remaining uncertainty is acceptable for the intended use.

Supplier Fabrication Packages: Defining a Usable Production Handoff

Wed, 02 Sep 2026 00:00:00 +0000

Supplier Fabrication Packages: Defining a Usable Production Handoff

A supplier package is usable when the recipient can identify the intended result, use the information required for its operation, regenerate only what has been assigned to them, and return evidence that remains linked to the authoritative design. No static list of files is complete for every fabrication job. Define the package from the operation, recipient, representation, and acceptance purpose.

Turn BIM Information Needs into Exchange Requirements with IDS

Wed, 02 Sep 2026 00:00:00 +0000

Turn BIM Information Needs into Exchange Requirements with IDS

“Include all information” is difficult to deliver and even harder to verify. A useful exchange requirement says which objects are in scope, which classifications and properties they need, what values or units are allowed, and which project purpose those requirements serve.

What a CAD Translator Actually Has to Do

Wed, 02 Sep 2026 00:00:00 +0000

What a CAD Translator Actually Has to Do

A translator is not a file-extension renamer. It must interpret one representation and produce a result in a different model, often with different validity rules, supported entities, units, attributes, and editing concepts.

Write an Interoperability Brief That Leads to Testable Acceptance

Wed, 02 Sep 2026 00:00:00 +0000

Write an Interoperability Brief That Leads to Testable Acceptance

An interoperability brief is a short record of what the exchange must accomplish and how the result will be judged. It gives a route researcher, supplier, or receiving team a question that is precise enough to investigate without pretending that the route is already proven.

Geometry Repair After Translation: Diagnose First, Change Deliberately

Wed, 02 Sep 2026 00:00:00 +0000

Geometry Repair After Translation: Diagnose First, Change Deliberately

Repair is an intervention, not a time machine. It may make an imported shape usable for one operation while changing boundaries, tolerances, internal structures, or the shape itself. Keep the original, record what changed, and validate the repaired result against the purpose.

One File, Many Forms: Containers, Packages, and External Resources

Wed, 02 Sep 2026 00:00:00 +0000

One File, Many Forms: Containers, Packages, and External Resources

“Send the file” is not a complete delivery instruction. A representation may be a text document, a binary encoding, a container with embedded parts, or an entry point into a larger set of referenced resources. The receiver needs to know which form is present and how its dependencies will be resolved.

Prepare CAD Data for Long-Term Retrieval and Reuse

Wed, 02 Sep 2026 00:00:00 +0000

Prepare CAD Data for Long-Term Retrieval and Reuse

Long-term preservation is a future acceptance problem. The goal is not merely to retain bytes, but to give a later reader enough representation, relationship, provenance, and process context to interpret the data for a stated purpose.

Use a BIM Reference Model Without Confusing It for an Editable Source

Wed, 02 Sep 2026 00:00:00 +0000

Use a BIM Reference Model Without Confusing It for an Editable Source

A reference model is useful when the recipient needs a bounded representation for coordination, review, or context. It is not automatically the source model, an editable authoring model, a complete BIM dataset, or an accepted project delivery.

Validate a Geometry Handoff: Compare Properties That Matter to the Receiving Task

Wed, 02 Sep 2026 00:00:00 +0000

Validate a Geometry Handoff: Compare Properties That Matter to the Receiving Task

Validation is a decision about a purpose, not a single green check. A model can pass a visual review and fail a boolean, or match volume while containing a local gap. Define the receiving task first, then choose checks that expose the failure modes that matter.

About This Reference

Fri, 04 Sep 2026 00:00:00 +0000

About This Reference

CAD Interoperability Reference is an independent technical publication about moving CAD and 3D design data between software ecosystems without losing sight of the work that follows the transfer.

The question behind the reference

“Can this application open that file?” is only the beginning of an exchange decision. The useful question is whether the received result contains the information the next task needs.

Privacy Policy

Fri, 04 Sep 2026 00:00:00 +0000

Privacy Policy

Last updated: September 4, 2026

This Privacy Policy describes the current data practices of CAD Interoperability Reference (the “Site”). It is written for this publication as it currently operates; it does not describe the practices of software vendors, standards organizations, hosting providers, or other sites linked from here.

Terms of Service

Fri, 04 Sep 2026 00:00:00 +0000

Terms of Service

Last updated: September 4, 2026

These Terms of Service apply to your use of CAD Interoperability Reference (the “Site”) and the information published on it. By visiting or using the Site, you agree to these terms. If you do not agree, please do not use the Site.