Preservation Strategy and Interoperability Maps

“Can you send the model?” is not yet an interoperability requirement. A useful handoff names the source and destination, the transfer route under consideration, the information that must survive, and the work the recipient must perform afterward.

What this category covers

Use this category to turn an informal exchange request into a decision that can be researched and tested. It gives you a common vocabulary for:

• the source environment, destination environment, direction, and transfer mechanism;
• the information layers that may matter, from shape and structure to editability, semantics, visual data, and manufacturing information;
• the difference between a support statement, conformance evidence, an observed preservation result, retained editability, and fitness for a stated purpose; and
• the continuity you actually need: a one-way delivery, continued work, a reference, an update path, or a round trip.

The category is deliberately a decision framework. It does not claim that a named format, translator, or product pair preserves a layer without route-specific evidence.

Articles

Read the articles in this order when planning a valuable exchange:

1. Define a CAD Data Handoff Before You Export turns “send the model” into a bounded source-to-destination question.
2. CAD Interoperability Claims: Support, Conformance, Preservation, and Fitness for Purpose explains what different kinds of compatibility evidence establish.
3. Build a Preservation Map for Design Data identifies the information layers the receiving task cannot afford to lose.
4. Choose the Right Handoff Expectation: Delivery, Continued Work, Reference, Update, or Round Trip separates one-time delivery from continuity and repeat-exchange expectations.
5. Write an Interoperability Brief That Leads to Testable Acceptance gives you a reusable requirement record for route research and later validation.

A useful starting question

Before choosing a file or translator, complete this sentence:

From [source environment and release], transfer [representation or mechanism] to [destination environment and release] so the recipient can [specific operation] while preserving [required information layers]. Loss of [permitted information] is acceptable only if [acceptance evidence] confirms the result.

If you cannot fill in one of those fields, record it as an unknown. An unspecified requirement should not quietly become an assumption about compatibility.