Back to Guides

SimReady Assets, OpenUSD, and Physical AI

SimReady Assets for Industrial Digital Twins and Physical AI

A practical guide to turning CAD, BIM, 3D, and scan data into SimReady industrial assets that carry geometry, semantics, physics, behavior, and data bindings for simulation and Physical AI workflows.

SimReady Assets for Industrial Digital Twins and Physical AI

Why industrial assets need a new level of readiness

Many industrial teams already have CAD files, BIM models, scans, 3D scenes, and digital twin visualizations. Those assets are useful for design review, remote collaboration, training material, and executive communication. Physical AI raises the bar because the asset must participate in computation.

A production line, cleanroom, warehouse, robot cell, or packaging station has to carry more than appearance. It needs real scale, stable coordinates, object identity, semantic labels, physics assumptions, behavior rules, process state, and links to operational data. When those layers are prepared together, the asset becomes usable for simulation, robot training, synthetic data, layout validation, process rehearsal, and AI agent reasoning.

NVIDIA describes SimReady as a framework for simulation-ready 3D assets and digital twins built on OpenUSD. The practical value for industrial teams is clear: move asset libraries from visual content toward reusable digital objects that can be simulated, validated, and governed.

What makes an asset SimReady

In industrial work, a SimReady asset should be evaluated through several layers:

LayerWhat should be prepared
Geometry and scaleAccurate dimensions, origin, orientation, units, level of detail, and spatial boundaries
Materials and appearanceMaterials, textures, lighting behavior, reflectivity, transparency, and surface categories
Physical propertiesCollision geometry, mass, friction, density, joints, constraints, motion range, and safety clearances
SemanticsEquipment class, part role, functional area, process role, asset ID, and relationship to the operational twin
Behavior logicState transitions, start and stop rules, faults, recovery steps, interlocks, routes, and interaction conditions
Data bindingsPLC signals, sensor values, alarms, work orders, MES context, energy data, and inspection records
Validation recordsSource files, version, owner, assumptions, quality checks, simulation findings, and approval notes

This structure helps simulation teams understand how an object behaves, robotics teams understand what can be learned from it, and operations teams trace results back to real assets.

Why behavior logic matters

Physics properties describe how an object moves, collides, rotates, slides, or responds to force. Industrial operations also depend on process rules and business state. A machine starts, waits, stops, alarms, recovers, blocks an upstream station, or releases material according to control logic and operating procedures.

FactVerse Designer uses behavior trees and scenario logic to express those operating rules. A packaging machine, conveyor, robot station, cleanroom zone, or utility asset can carry state transitions, trigger conditions, process timing, and interaction rules. That makes the asset useful for process simulation, operator training, robot collaboration, safety rehearsal, exception handling, and Physical AI planning.

The most useful industrial asset is a digital object with properties, behavior, and constraints. It can appear in a factory scene, participate in a simulation, provide labels for synthetic data, and remain connected to operational records.

The DataMesh workflow

  1. Collect source assets - Bring together CAD, BIM, 3D, scan data, drawings, equipment records, process documents, and control-system context.
  2. Normalize the scene - Align scale, coordinates, hierarchy, naming, object identity, location, and version rules in FactVerse.
  3. Add industrial semantics - Attach equipment class, process role, functional area, asset ID, upstream and downstream relationships, documents, and owner information.
  4. Prepare physics context - Define collision geometry, mass, friction, joints, motion constraints, access areas, robot zones, and safety boundaries where simulation requires them.
  5. Author behavior logic - Use Designer to define state transitions, operating steps, interlocks, faults, recovery paths, route rules, and scenario variants.
  6. Connect operating data - Use Data Fusion Services when a scenario needs PLC signals, sensor values, alarms, work orders, production state, energy context, or inspection history.
  7. Prepare the OpenUSD path - Use the FactVerse Adaptor for NVIDIA Omniverse to carry scene structure, metadata, behavior context, and asset preparation into OpenUSD and Omniverse workflows.
  8. Validate and govern - Review rendering, physics, behavior, labels, scenario coverage, and downstream simulation results before adding assets to a reusable library.

The workflow turns a modeling project into an asset program. Each object gains a clear owner, data lineage, quality state, and reuse path.

What a SimReady asset library enables

For large industrial organizations, the long-term asset base is a library of reusable operational objects:

  • Packaging equipment with cycle time, state, upstream and downstream relationships, fault logic, physical boundaries, and process behavior.
  • Robot workcells with work envelope, safety zones, sensor layout, grasp targets, task sequences, and coordination rules.
  • Conveyors and material flow assets with direction, speed, blocking rules, handoff logic, route state, and data bindings.
  • Cleanrooms and controlled environments with equipment layout, access paths, airflow constraints, maintenance routes, energy context, and risk rules.
  • Warehouse zones with racks, aisles, pallets, staging areas, mobile equipment paths, and logistics process state.

When assets are standardized, objectized, behavior-rich, and physics-aware, teams can reuse them across production planning, factory modification, training, robotics adoption, exception drills, energy analysis, and AI training.

Role in Physical AI and world models

Physical AI systems need high-quality digital worlds. These worlds need space, objects, semantics, physics, behavior, process state, and data. SimReady assets provide the reusable production material for those environments.

For robotics, the difference shows up in training and validation quality. A robot can train on visual data, but industrial tasks often require invisible context as well: temperature, pressure, vibration, equipment status, work order state, safety zones, and process constraints. FactVerse can carry that context into the twin, while Omniverse, PhysX, Newton, and related simulation workflows can support rendering, physics, sensor simulation, and robotics evaluation.

This makes SimReady asset preparation a foundation for synthetic data generation, robot task rehearsal, factory layout planning, process validation, and AI agent workflows.

Practical use cases

  • Production-line and packaging process validation: test equipment layout, material handoff, operator access, robot interaction, and process timing before physical changes.
  • Synthetic data generation: generate labeled RGB, depth, segmentation, pose, trajectory, and scene-state data from assets with semantic and physical context.
  • Robotics simulation: prepare workcells, mobile routes, safety zones, manipulation targets, and process rules for downstream simulation environments.
  • Factory and warehouse planning: compare line layouts, logistics routes, buffer areas, storage layouts, and material-flow assumptions.
  • Operator training and exception rehearsal: use behavior-rich assets to rehearse start-up, shutdown, fault response, maintenance steps, and safety procedures.
  • Facilities and energy analysis: connect assets, zones, meters, and operating states so facility teams can evaluate scenarios with clearer source context.

Governance checklist

  • Source files, owners, licensing, and version history are recorded.
  • Units, scale, coordinates, origin, and orientation are validated.
  • Asset identity matches the operational twin and enterprise asset records.
  • Semantic labels follow a controlled vocabulary for equipment, zones, parts, and process roles.
  • Physics assumptions are documented with the simulation goal they support.
  • Behavior logic has named states, triggers, timing, faults, and recovery paths.
  • Data bindings include source system, unit, timestamp, refresh rule, and quality status.
  • Simulation results can trace back to asset version, scene version, assumptions, and reviewer.

The review process should treat assets as engineering artifacts. A useful SimReady library has quality gates, owners, versioning, and a path for continuous improvement.

Public references

NVIDIA's SimReady overview, SimReady specification, and SimReady FAQ provide the public technical background for simulation-ready assets built on OpenUSD.

NVIDIA's Omniverse page describes Omniverse as libraries and microservices for industrial digital twins and Physical AI simulation applications.

The FactVerse and NVIDIA Omniverse announcement and GTC 2025 showcase show DataMesh's public direction for simulation digital twins, OpenUSD workflows, and Physical AI preparation.