RESOURCES
Humanoids, mobile robots, and arms from more than one vendor, served from one pool.
Articles in Robot Fleets
- Robot Fleets
Planning a pool for the fleet you have not bought yet
The robots a site will eventually run have not been chosen, and some have not been built. A facility pool is planned around the building, so the fleet decision can wait without the infrastructure waiting with it.
· 4 min read
- Robot Fleets
Adapting models on the floor's own captures
A general model has never seen your floor. Substrate fine-tunes the shared model on captures taken in the building, on the pool, evaluates the result, and keeps the weights where the captures were taken.
· 4 min read
- Robot Fleets
Tasks that hand work from one vendor's robot to another's
A real job on a floor crosses vendors: one robot carries, another picks, a third places. Agency Studio lets the site author that job as one task, bounded and approved, with every handoff on the record.
· 4 min read
- Robot Fleets
A robot that stops, not one that guesses
The most important design decision in a facility pool is what happens when it does not answer. The answer is that the robot does what it would have done without the pool, which is to stop or to use its own model.
· 4 min read
- Robot Fleets
Teleoperation and the facility pool
Teleoperation is how a person steps in when a robot cannot decide. A facility pool does not replace that person. It changes how often they are needed, where their session goes, and what the floor learns from it.
· 4 min read
- Robot Fleets
A new item learned once, not once per vendor
On a floor with robots from several vendors, a new item has to be taught to each vendor's model separately. A shared pool learns it once, on the site's own captures, for every robot on the floor.
· 4 min read
- Robot Fleets
Connecting a vendor's fleet software to the pool
A connection between the pool and a vendor's fleet software is a decision the site makes, route by route. Here is how that decision is made, what it allows, and what it never allows.
· 4 min read
- Robot Fleets
What a robot vendor keeps when a site adds a pool
A vendor's first question about a facility pool is usually what it takes away. The answer is nothing the vendor built. Here is the list of what stays the vendor's, and what the vendor gains.
· 4 min read
- Robot Fleets
Why safety stays on the robot
A facility pool serves perception and decisions. It never serves the stop. Here is why that line is drawn where it is, and what it means for the vendor, the safety officer, and the floor.
· 4 min read
- Robot Fleets
Mixed-vendor fleets on one floor
Most working floors run robots from more than one vendor, each with its own cloud, its own model, and its own idea of the building. One facility pool serves all of them without asking any vendor to give anything up.
· 4 min read
- Robot Fleets
Vision-language-action models on a facility pool
Vision-language-action models are the models too large to carry and too urgent to send away. A facility pool is where they fit, with the robot's own controller still holding the last word on motion.
· 4 min read
- Robot Fleets
Pick arms and the unfamiliar item
A pick arm is excellent at the items it has seen and hesitant at the ones it has not. A facility pool gives the arm a larger model to ask, and a way to learn the new item without sending it anywhere.
· 4 min read
- Robot Fleets
Mobile robots and shared perception
Every mobile robot on a floor sees the same aisles with its own eyes and its own small model. A facility pool lets the fleet share one larger view of the building it works in.
· 4 min read
- Robot Fleets
Serving humanoids from the rack, not the backpack
A humanoid can only carry so much compute. The models that make it useful on a working floor belong in the building's rack, close enough to answer in time and inside the site's own network.
· 5 min read