5 Steps to Create SimReady Assets for Robotics with Frontier AI Models

NVIDIA published a five-step workflow for converting CAD assets into SimReady OpenUSD assets for robotics simulation, using an ABB Robotics YuMi robot as the worked example and GPT-6 Astra as one frontier AI model that can write Python code to call NVIDIA Omniverse libraries at each stage. The steps cover STEP-file conversion, appearance validation, physics configuration, SimReady validation, and a final pick-and-place task with both arms and grippers in NVIDIA Isaac Sim, guided by SimReady Foundation specifications and agentic NVIDIA skills such as the CAD-to-SimReady skill. NVIDIA notes that assets can look correct yet fail in simulation when collision geometry, joints, mass, or friction properties are missing or wrong.

Preparing CAD assets for robotics simulation requires more than converting geometry to OpenUSD https://www.nvidia.com/en-us/glossary/openusd/ : developers must configure and validate materials, collision geometry, joints, and other physics properties before testing robot behavior. NVIDIA Omniverse libraries https://developer.nvidia.com/omniverse , guided by SimReady Foundation https://nvidia.github.io/simready-foundation/ specifications and agentic NVIDIA skills https://github.com/NVIDIA/skills , provide a structured workflow for converting and validating simulation ready SimReady https://www.nvidia.com/en-us/glossary/simready/ assets. Frontier AI models can assist developers at each stage by interpreting reference materials and calling Omniverse tools on their behalf, reducing manual preparation. This post walks through how to prepare an ABB Robotics YuMi robot https://campaigns.cobots.abb/cobots-general-en-us/ for simulation using the SimReady Foundation and NVIDIA Omniverse tools, with GPT-6 Astra as one example of a frontier AI model that can assist with the process. The workflow covers five steps: STEP-file conversion, appearance validation, physics configuration, SimReady validation, and a final pick-and-place task with both arms and grippers in NVIDIA Isaac Sim https://developer.nvidia.com/isaac/sim . What Is SimReady and Why Does It Matter for Simulation? SimReady defines requirements for preparing OpenUSD assets for specific simulation use cases. Developers select a SimReady profile for their intended use and validate the asset against its requirements. Profile-specific checks validate the asset’s structure, materials, and physics properties, then flag issues for developers to fix and recheck. A robot model can look correct but still fail in simulation if it is missing simulation properties. For example, missing collision geometry can allow objects to pass through its gripper and incorrect joints can prevent coordinated motion. Simulation properties like mass and friction directly affect whether a grasp remains stable. The following technologies and tools support this workflow: - OpenUSD https://developer.nvidia.com/openusd represents geometry, assembly structure, materials, and simulation properties in a common asset representation. - SimReady Foundation https://github.com/nvidia/simready-foundation provides specifications and validation guidance for preparing simulation-ready assets. - NVIDIA Omniverse libraries https://developer.nvidia.com/omniverse provide capabilities that developers and agents can use to convert, inspect, and prepare OpenUSD content. - NVIDIA Isaac Sim https://developer.nvidia.com/isaac/sim provides the environment for configuring physics and testing robot behavior. - NVIDIA Omniverse AI Agent skills https://developer.nvidia.com/omniverse such as CAD-to-SimReady skill https://github.com/NVIDIA/skills/tree/main/skills/omniverse-cad-to-simready guide agents through asset conversion, material and physics assignment, and validation. SimReady Robotics Workflow: An ABB YuMi Robot Example This walkthrough demonstrates the five-step SimReady workflow using an ABB Yumi robot https://www.abb.com/global/en/areas/robotics/products/robots/collaborative-robots/dual-arm-yumi . GPT-6 Astra is used here as one example of a frontier AI model that can help write Python code to call NVIDIA Omniverse libraries at each stage, but the workflow can be applied across many models and robot systems. The example uses both arms and grippers, configured during the workflow. Cubes and a Sharpie marker were used as demonstrations in step 5. Camera-based perception can be added in a separate workflow. Before you begin: - Install Isaac Sim https://docs.isaacsim.omniverse.nvidia.com/6.0.0/installation/download.html - Create a folder inside the Isaac Sim directory and name it ‘reference’, we will use this reference folder to hold the relevant assets for the workflow. - Add the robot specifications https://search.abb.com/library/Download.aspx?DocumentID=9AKK106354A3254&LanguageCode=en&DocumentPartId=&Action=Launch , STEP https://search.abb.com/library/Download.aspx?DocumentID=9AKK106930A6607&LanguageCode=en&DocumentPartId=&Action=Launch files, and reference images https://media-d.global.abb/is/image/abbc/overview image yumi dual arm:1x1-L and videos <https://media-d.global.abb/is/content/abbc/ABB Dual Arm YuMi Product Film-5SEC Intro Module -Download MP4 in this folder details below in the table - Install your frontier AI model - In this workflow example, we used GPT-6 Astra https://developers.openai.com/api/docs/models/gpt-6-astra . - In this workflow example, we used - Launch Codex CLI in your Isaac Sim directory - It is important to launch Codex inside the Isaac Sim directory so that the agent can find the necessary skills which will be needed in the workflow. In this workflow example, we used Isaac Sim 6.1 and Codex CLI and launched Isaac Sim in windowed mode. Use the following example prompt in your active Codex CLI to start Isaac Sim: The remote Python server in Isaac Sim enables your agent to ‘talk’ via Python to your live Isaac Sim application. Confirm that the connection works before continuing. At each step, adapt the sample prompt to your task in your frontier AI agent, then review simulation results and validation feedback to identify issues and refine the asset. 1. Import the robot from the STEP files As the first step in this workflow, we will import the robot from the STEP files in the reference folder. For this example, provide the following inputs in the reference folder within the Isaac Sim directory: | Sample Input | Purpose | | ABB Robotics YuMi robot STEP files https://search.abb.com/library/Download.aspx?DocumentID=9AKK106930A6607&LanguageCode=en&DocumentPartId=&Action=Launch . | Source geometry for conversion to OpenUSD. | | Reference images and videos from ABB Robotics. This sample workflow uses the linked ABB Robotics video <https://media-d.global.abb/is/content/abbc/ABB Dual Arm YuMi Product Film-5SEC Intro Module -Download MP4 and image https://media-d.global.abb/is/image/abbc/overview image yumi dual arm:1x1-L . | Guide the asset’s appearance and material assignments. | | SimReady Foundation https://nvidia.github.io/simready-foundation/ specification repositoryNote: Isaac Sim 6.1 is also packaged with simready-foundation-tier-core | Supply robot requirements, related skills, and validation guidance. | | CAD-to-SimReady skill https://github.com/NVIDIA/skills/tree/main/skills/omniverse-cad-to-simready | Provide guidance for CAD conversion, material and physics assignment, and SimReady validation. | Table 1. Sample inputs and their purposes for preparing the YuMi robot for simulation Note: Isaac Sim 6.1 is packaged with simready-foundation-tier-core. Ask the agent to to use the supplied inputs to guide conversion to OpenUSD and import into Isaac Sim. Sample prompt: https://github.com/NVIDIA/skills/tree/main/skills/omniverse-cad-to-simready https://github.com/NVIDIA/skills/tree/main/skills/omniverse-cad-to-simready and import the robot into Isaac Sim. Make sure you also import both grippers and position them at the correct mounting points on the robot’s arms. NVIDIA Skills used: omniverse-cad-to-simready, omniverse-cad-to-usd, and isaac-sim-remote Check before continuing: The robot asset is imported and available for inspection. The task and supplied requirements are understood, and missing information is identified. 2. Match the visual appearance The next step is to inspect the imported robot to confirm that expected materials and textures are present and loaded correctly. Compare the asset with the supplied ABB images and videos to check scale, orientation, and part placement. Ask the agent to add or refine materials and textures using these references. Sample prompt: Assumptions: The agent visually matches the robot’s materials by adjusting colors, metallic response, and roughness while preserving the CAD geometry and mounting transforms. The material settings were visual estimates, without measured material reconstruction or AI-generated textures. NVIDIA Skills used: isaac-sim-remote, usd-pipeline Check before continuing: The robot has the expected scale, orientation, parts, and appearance. Any missing materials, textures, or other visual discrepancies are documented. 3. Configure physics properties At this stage, the OpenUSD asset contains the robot’s visual geometry, but joints, rigid bodies, and collision geometry have not yet been configured. Ask the agent to configure and validate the physics properties for both arms and grippers. The datasheet https://search.abb.com/library/Download.aspx?DocumentID=9AKK106354A3254&LanguageCode=en&DocumentPartId=&Action=Launch we have in the reference folder will be used by the agent to make sure the joint ranges and speed limits match the simulated robot. If manufacturer data is incomplete, you can ask the agent to identify missing parameters and check technical manuals or available URDF robot descriptions for the exact model. Where mass properties remain unavailable, estimate them from geometry using documented density or mass-distribution assumptions, following NVIDIA’s mass-property guidance https://docs.omniverse.nvidia.com/kit/docs/omni physics/latest/dev guide/rigid bodies articulations/rigid bodies.html . For example, when not given enough context, we observed the agent pulling a public URDF for the robot and used that to identify the correct axes for joints and the zero configuration. Sample prompt: Check joint definitions, axes and limits, mass and inertia, collision geometry, base mounting, and gripper motion. The initial pose may vary. Figure 4. YuMi poses after physics configuration Simulation assumptions in this workflow: - Joint configuration: The agent retrieved a public URDF for the robot and used it to identify joint axes and the zero configuration. - Per-link masses: Estimated from STEP geometry volumes and normalized to manufacturer-specified totals: 38 kg for the robot and 0.28 kg for each gripper. - Centers of mass and inertia: Calculated assuming solid parts of uniform density; internal motors, gearboxes, and wiring were not modeled individually. - Contact properties: Assumed static friction of 0.8, dynamic friction of 0.6, and zero restitution. - Collision geometry and appearance: Convex collision shapes, surface roughness, and material response were approximated. - Calibration: These parameters were not calibrated against physical YuMi measurements. NVIDIA Skills used: usd-articulation, physics-simulation, isaac-sim-validator, isaac-sim-remote Check before continuing: Joints move around the expected axes and within their limits. Base mounting and gripper motion behave as configured. Estimated properties and any validation failures are documented. 4. Validate the SimReady properties The next step is to validate the robot’s OpenUSD asset against the SimReady requirements for the intended simulation task. Ask the agent to run the selected SimReady Foundation checks, review the findings, and revise the asset as needed. Sample prompt: Find the SimReady asset validation for a robot, and apply the SimReady schema https://github.com/nvidia/simready-foundation https://github.com/nvidia/simready-foundation to the usd file, use any related skills in that repo. Validation results in this workflow: - SimReady Foundation: The YuMi asset’s units, asset dependencies, geometry, materials, rigid bodies, joints, drives, and articulation were checked against SimReady Foundation requirements. - Isaac Sim asset checks: Verified scale, orientation, part placement, gripper mounting, material coverage, and resolved texture dependencies via validation engine inside Isaac Sim. - Mass and inertia: All 21 rigid bodies had positive masses and physically admissible inertia tensors; runtime values matched authored values. - Joints: Checked axes, frames, limits, drives, finger mimic behavior, and fixed-base mounting. - Runtime behavior: Tested arm and gripper motion, contact, release, and collisions along the tested trajectories. These checks validated the simulation implementation. They did not establish agreement with real-world robot dynamics or collision safety across every possible pose. Figure 5. YuMi asset in Isaac Sim after visual, physics, and SimReady validation steps Check before continuing: The sequence meets the agreed acceptance criteria and the selected SimReady checks pass. Tuning changes, estimated properties, and any unresolved failures are documented. 5. Final task for robotic simulation Run a final validation in Isaac Sim, combining the visual, physics, and SimReady checks with a pick-and-place task. Example 1: Cube pick-and-place Ask the agent to add color targets and a box to the test scene and define the target locations and color metadata, matching color targets are selected using scene metadata. Sample prompt: Run the complete grasp, lift, hold, transfer, and release sequence. Use scene metadata to select the matching color target for each cube. Also test placement into the box. Check scale, orientation, part placement, materials, textures, joint axes and limits, collision geometry, and gripper behavior. Run the selected SimReady Foundation validation checks. Simulation assumptions: - We assumed dimensionless contact-friction coefficients of 0.8 static and 0.6 for dynamic. The grasp tests passed with these settings, but the coefficients were not measured or calibrated against the physical finger–object contact. - This example uses 45 mm, 40 g test cubes and the simulation assumptions described in Step 3. Demonstrated pick-and-place results: - Completed cycles: Both arms and grippers completed four pick-and-place cycles in total during a 122.2-second physics simulation. - Task sequence: Each arm grasped its cube, lifted it, held it for two seconds, transferred it, and released it onto its matching color target. Each arm then picked up its cube again and placed it inside the box. - Contact behavior: Finger contact and friction carried the cubes, without attachment joints, kinematic holds, or direct cube-pose updates during simulation. - Acceptance criteria: All cycles passed the defined grasp, hold, transfer, release, and placement criteria. - Recording: The MP4 and GIF were generated from this simulation. Figure 6. YuMi pick-and-place simulations with colored cubes and target markers Example 2: Pick-and-place with an image-derived object A separate demonstration used a Sharpie marker created from a reference image to have the agent create a 3D asset which the robot will pick up. - Simulation assumptions: Agent estimated the dimensions of the marker as 140mm and a 10 gram mass with the center of mass at the geometrical center of the Sharpie. Collision geometry was approximated with cylinder geometry for the cap, barrel and rear plug. - Demonstrated results: YuMi’s gripper lifted the marker from the tabletop and released it into a blue tray in Isaac Sim. Figure 7. YuMi picking and placing a Sharpie marker modeled from a reference image in Isaac Sim Successful simulation tests demonstrate behavior under the tested conditions. Results may vary depending on the frontier AI model and prompt used. NVIDIA Skills used: manipulation-ik, physics-simulation, isaac-sim-validator, isaac-sim-remote, isaac-sim-rendering Try the Workflow SimReady Foundation and NVIDIA Omniverse tools help developers turn CAD files and reference materials into assets they can configure, validate, and test in simulation. Use OpenUSD, SimReady Foundation, and NVIDIA Omniverse tools and skills to prepare assets for your robotics simulation tasks. The YuMi walkthrough provides one example of the SimReady robotics workflow using GPT-6 Astra as the frontier AI model. To adapt the approach to another robot or frontier AI model, confirm access to the required tools and skills, supply the relevant reference materials, and repeat the asset and task validation. Results may vary with the model, reasoning effort, and prompts used. Try the ABB Robotics sample workflow - Start with the SimReady Foundation https://nvidia.github.io/simready-foundation/ repository and CAD-to-SimReady skill https://github.com/NVIDIA/skills/tree/main/skills/omniverse-cad-to-simready to guide asset preparation. - The ABB Robotics YuMi robot https://www.abb.com/global/en/areas/robotics/products/robots/collaborative-robots/dual-arm-yumi STEP file, reference video <https://media-d.global.abb/is/content/abbc/ABB Dual Arm YuMi Product Film-5SEC Intro Module -Download MP4 and image https://media-d.global.abb/is/image/abbc/overview image yumi dual arm:1x1-L are available to follow along with this walkthrough. Learn More - Explore robotics simulations with Isaac Sim https://developer.nvidia.com/isaac/sim and Isaac Lab https://developer.nvidia.com/isaac/lab . - Learn to assemble OpenUSD scenes through the free OpenUSD learning path https://docs.nvidia.com/learn-openusd/latest/index.html . - Learn robotics and digital twin skills through the free physical AI courses https://docs.nvidia.com/learning/physical-ai/index.html . Join us at NVIDIA GTC Berlin https://www.nvidia.com/en-eu/gtc/ on October 20–22, 2026, to explore the latest developments in physical AI and robotics https://www.nvidia.com/en-eu/gtc/sessions/physical-ai-and-robotics/ and connect with developers, researchers, and industry leaders.