Brett Adcock

And they basically, like, they can run, uh, like, four hours or so, five hours, and when they need to charge, another robot knows that, steps in, steps behind the robot, say, and gets ready for work.

The robot then backs off.

The robot swaps in spot, like, in the next, like, 10 seconds, it's doing work again.

So we can run that now in 24 seven shifts where they're talking to each other, all autonomous, no humans, or you can go to bed, whatever.

And they're running that shifts all day and all night.

And we do it across multiple use cases now at the office in 24 seven shifts.

And it's just like, we're running them hard.

We do a few things.

We have a logistics use case

that we run in 24-7 shifts constantly.

We really like it.

It's done with a neural net.

It's moving packages around.

And it's a really good use case.

We like it.

And I want to run it for months and have failures.

And we see failures right now.

And most of it's in software.

The robot gets to some spot where it feels unsafe, doesn't know what to do, and it'll stop for a little bit.

And if the robot's not on the line for a couple minutes, we call out a failure, and we're not happy with it.