From compute to operation
How hardware, Omniverse and shared models fit together, from the compute underneath physical AI to the industrial systems it is meant to improve.
Choose a reading path
Each path has its own starting point and sequence.
More in Platform & Industrial Systems
5 pieces not currently in a reading path.
Most Robot Policies Don't Need Tactile Input. The Test Is Whether Vision Can See What Decides the Task.
Years of MES work taught me where automation stops: at tasks whose decisive state cannot be written down or seen. Tactile input earns its place when it reveals that missing state; contact alone is not enough.
What Kind of Truth Does Your Digital Twin Need?
Every digital twin needs a usable digital starting point. CAD, LiDAR, photogrammetry and Gaussian splatting preserve different kinds of truth, so the representation should follow the decision. Part 1 of a three-part series.
What Industrial Maintenance Demands From Robot Capture
A refinery valve operation shows why robot capture should begin with the task: preserve the motion, contact, timing and measurements the policy will need.
A VLA Benchmark Is Not a Commissioning Package
Robot foundation models are getting better at handling situations they were not shown. That makes the old commissioning questions more important: where is the model valid, how do I know it has left that range, and what happens next?
NVIDIA's Hardware Line Looks Like a Catalog. It's One Architecture in Many Boxes.
People keep asking me a version of the same question: what NVIDIA hardware should I be thinking about for a digital twin, from a developer build at my desk all the way to production? I always had an answer but no clean model behind it, just a pile of product names, three of which are confusingly all called DGX. So I built the model I wanted: NVIDIA develops one architecture family a year and expresses it across many kinds of computer, from a gaming card to a liquid-cooled rack. These are my rough notes, in case you're coming at it from the software side and asking the same thing.
Is Physical AI the Next Level for MES? I Think It Is
MES was never really about running the machines. It was about improving the operation, and it was limited by how much had to be modeled by hand and decided by people. Physical and agentic AI can change that, but only if the plant's systems are joined through shared operational context.
I Built a Live USD Viewer That Never Launches Kit
A browser-based USD viewer, RTX-rendered server-side and streamed over WebRTC, built to see if the library-first pitch holds up under real interactivity.
Physical AI's bottleneck isn't the model anymore
We finally have models that can watch the physical world, reason about it, and predict what happens next. Walk a real automotive parts-kitting task through what they actually solve, and the thing still standing between a demo and a working line isn't a smarter model: it's the policy you have to train for your machine, and the system that keeps it trained.
You No Longer Need to Build an App to Use Omniverse
Kit and libraries used to be the same choice for building on Omniverse. They're not anymore, and that's a bigger change than it looks, with a real before/after from a Kit extension I built.
The Omniverse Licensing Change You Might Have Missed
Since May 2026, Omniverse is free for production, not just development. It's a clean, sensible change, but it landed quietly, and I keep meeting customers and partners who don't know it happened yet. The paid-production requirement is gone; the license and optional enterprise support remain.
Omniverse Is Not a Rendering Tool
From the industrial systems I know, rendering is only one part of Omniverse. The harder job is connecting source data, giving teams a shared context, and reusing it for visibility, simulation, optimization and Physical AI.