3D Digital Double Control & Simulation Center — bRRAIn Docs

NVIDIA OpenUSD-based simulation control for digital twins of physical sites, processes, and fleets.

3D Digital Double Control & Simulation Center

A control surface for digital twins. Build, run, and reason about 3D digital doubles of your physical sites, processes, and fleets — backed by NVIDIA OpenUSD scenes — with bRRAIn's reasoning loop in the seat.

What it does

A digital double is a high-fidelity 3D model of something physical (a factory floor, an oil rig, a warehouse, a city block, a vehicle, a robot, a room) that stays in sync with the real-world state via telemetry feeds. The Simulation Center lets you:

  • Compose double scenes from OpenUSD asset libraries.
  • Connect real-world telemetry into the scene (IoT sensors, control PLCs, vision feeds).
  • Simulate what-if scenarios on the double without affecting the real system.
  • Reason with bRRAIn's Handler over the scene state.
  • Act by sending commands back through control integrations.

Use cases

  • Factory ops planning ("what if we add a third packing line here?").
  • Real-time fleet position visualization across an operations center.
  • Safety incident pre-mortem rehearsal.
  • Operator training in a high-fidelity but consequence-free environment.
  • Predictive-maintenance simulation against current sensor state.

Installing

Per-organization subscription with metered compute for live simulation. Requires GPU compute to render scenes interactively; we coordinate provisioning with AI Cloud Provisioner if you've got that installed.

After install:

  • A new app surface mounts under your Console.
  • A 3D viewport opens with a starter scene.
  • The first-time wizard guides you through importing your first asset.

Scenes

A scene is a USD composition of:

  • Static geometry (buildings, equipment, terrain).
  • Dynamic actors (vehicles, robots, people).
  • Material and lighting setup.
  • Behavior layers — physics, AI agents, sensor data overlays.

Import from OpenUSD libraries, your CAD pipeline, or upload custom assets. Cesium for geospatial baselayers is supported.

Telemetry binding

Each dynamic actor in the scene can be bound to:

  • A live integration feed (MQTT, Kafka, OPC UA, ROS, vendor-specific PLC bridge).
  • A bRRAIn record stream.
  • A simulated source (for training and what-if).

Bindings are visual — drag a telemetry source onto an actor. The actor's pose, state, and telemetry overlay then track the source.

Simulation modes

  • Live mirror — the double tracks the real world in real time.
  • Replay — load a recorded telemetry window and step through.
  • What-if — branch from a recorded state and explore alternative trajectories.
  • Synthetic — fully simulated; no real-world binding.

Handler reasoning

The bRRAIn Handler can be addressed against the current scene state:

"Where is robot R-7 right now and is it on schedule?" "Show me where line 2 was last week at this time." "Project the next 30 minutes assuming intake stays at current rate."

Responses are grounded in the scene's current snapshot plus your Vault's broader context.

Action integrations

For binding back to physical systems, the extension supports common control integrations:

  • ROS / ROS2 publish-subscribe.
  • OPC UA write.
  • Modbus TCP write.
  • MQTT publish.
  • Vendor-specific PLC bridges.

Action commands route through your standard policy and approval gates. Certain action classes require explicit human approval before execution — typical for any command with safety implications.

Multi-user

Multiple operators can share a scene simultaneously. Each sees the others' avatars and can hand off control points. Useful for ops centers and for distributed incident response.

VR / AR support

Scenes render to VR headsets (Quest, Vive, Index) and to AR glasses (Vision Pro, HoloLens) via the AR & VR Control Center extension when installed.

Scopes required

  • Read and write in the extensions/digital-double zone.
  • Access to telemetry integrations you wire up.
  • Action permission on control integrations (with approval gates by default).
  • GPU compute for live rendering.

Where to next