Make a SimReady Asset#
This page expands the answer to How do I make a SimReady asset?.
Start with the asset’s intended use and an applicable SimReady profile and version. Author or convert the source content to OpenUSD, supply the required structure, properties and relationships, and check conformance using compatible validation tools. Correct reported failures and validate again; prepare a runtime-specific variant when the target workflow requires one. Consult the versioned profile and workflow documentation for supported features, tools and preparation steps.
Robotics Assets#
For example, robotics assets, including props, robots, and articulated agents, can follow this workflow.
Start with your source content (URDF [Unified Robot Description Format], MJCF [MuJoCo XML Format], CAD, or directly-authored USD) and target one of the existing robotics Profiles (refer to Do I need to implement every SimReady requirement? for the full list). The workflow:
Convert to USD: Import from URDF (using the URDF Importer Extension), MJCF, or CAD (using the CAD Converter Extension or application connectors). Each format has a documented conversion path.
Choose a target Profile: For example,
Prop-Robotics-Neutralfor physics-ready props,Robot-Body-Neutralfor articulated robots. Your Profile determines which Features your asset must satisfy.Validate against the Profile: Run SimReady Foundation’s rules framework to check every Requirement in the Profile. Each failure traces to the exact USD property at fault (for example, “missing
CollisionAPIon rigid shape,” “joint hierarchy incorrect”).Fix and iterate: Address validation failures in the source content, converter settings, or post-conversion tools (Scene Optimizer). Re-validate until clean.
Adapt for specific runtimes: If you need a runtime-specific variant (such as PhysX SDK SDF colliders for Omniverse Isaac Sim), use Feature Adapters to convert from a base (Neutral) Profile to a runtime Profile. Only the delta is applied.
CAD-to-SimReady Assets#
For example, CAD-to-SimReady assets for digital twins and AI factories can follow this workflow.
For facility equipment (racks, coolant distribution units [CDUs], chillers, building infrastructure), the workflow is a multi-stage content iteration cycle:
CAD Conversion: Transform CAD files (STEP, JT, Creo, DGN, and so on) to USD using the GUI or CLI tools. Key decisions: instancing, UV generation, unit handling.
Validation: Run the Asset Validator to identify quality and compliance issues (standalone or inside Omniverse Kit).
Optimization: Apply Scene Optimizer presets: stage metrics normalization (meters, Z-up), mesh cleanup, decimation, material optimization, hierarchy deduplication.
Metadata: Add vertical-specific simulation properties (semantic labels, equipment specs, thermal/electrical parameters) as structured USD layers composed into the main asset.
Connection Points: Define facility connection interfaces (piping, electrical, airflow) using named geometry prims.
Final Validation: Re-validate the complete, composed asset against the target Profile’s requirements.
In these examples, source conversion rarely produces a perfect USD representation. Plan to iterate across source fixes, converter settings, and post-conversion tooling.
Resources#
SimReady Foundation documentation covers the specification framework, validation rules, Feature Adapters, and sample assets for robotics Profiles.
The VFI Guide documents the CAD content iteration cycle (conversion, validation, optimization, assembly).
The SimReady Standardization Workflow is the process for contributing new domain specifications. It is relevant if your domain’s Profile does not yet exist.