Exchange SimReady Assets#

This page expands the answer to How do I exchange my SimReady assets with other USD-based systems?.

Meaningful interchange requires producing and consuming tools to agree on the names, types, units, relationships and meaning of the data, using compatible schemas or documented mappings. OpenUSD can preserve data that a tool does not interpret, but carrying that data alone does not establish that the receiving tool can use it correctly. Use specifications and profiles supported by both sides of the workflow.

Composition#

USD’s composition model is the foundation.

  • Metadata and schema properties ride along with assets without requiring consuming systems to understand all of them.

  • A system that does not know about SimReady schemas can still load and render the geometry. A system that does can consume the simulation metadata.

  • This is precisely why structured schemas matter: a cable_params: float4[] blob rides along too, but no consuming system can do anything with it. Named, typed properties (like tensileStrength: double) are what make interchange meaningful.

Conceptual Data Mapping#

Conceptual data mapping enables the bridge.

  • When exchanging assets between USD and other ecosystems (glTF, FBX, URDF, IFC, and so on), conceptual data mapping documents how data translates between formats.

  • This is what makes SimReady a “standard of standards” rather than a replacement.

Supported Interchange#

Tools implementing compatible schemas and agreed mappings can exchange the domain data those contracts cover. Use the relevant versioned profile, schema and mapping documentation to identify supported properties, implementation requirements and conversion limits.

The SimReady Standardization Workflow is the process for contributing domain specifications.