Planning a pool for the fleet you have not bought yet

The hardest part of planning for robots is that the robots keep changing. The mobile robots a site evaluated on its last tour are already a generation old. The humanoids it is watching are not yet ready for a production shift. The pick arm vendor it likes may be bought by someone else before the contract is signed. An automation team asked to plan infrastructure for that fleet is being asked to plan for machines nobody has chosen.

A facility pool is the part of the plan that does not depend on the answer. It is sized to the building, serves any vendor, and runs whatever posture the site needs. The fleet can be decided later. The pool does not have to wait with it.

Plan around the building

A Czar is a sealed node in the facility's own rack. One Czar is a pool for a small floor. Several joined are a Czar Grid: one pool for the whole facility. The unit of planning is the floor or the building, not the robot, because the pool serves every robot on the facility's network regardless of what it is or who made it.

That changes the question the automation team has to answer. Instead of asking what compute each candidate robot needs, which no vendor will answer the same way, the team asks what the building is: how large a floor, how many areas, how much of the work will be perception and decisions that a robot cannot carry on board. Those are questions about the site, and the site can answer them now.

Stay vendor-neutral on purpose

The temptation when planning for a fleet is to standardize on one vendor and let that vendor's cloud be the brain. It is tidy at first and a trap afterward. Every working floor ends up with robots from more than one vendor, because no vendor makes every kind of robot and the best choice shifts.

A pool that serves every robot from any vendor removes the need to choose early. The mobile robots that arrive first use it. The pick arms that arrive next use the same one. The humanoids that arrive after a trial use it too, sharing the same perception model, the same record, and the same adaptation to the floor. No vendor's departure takes the pool with it, and no vendor's arrival requires a new one. The article on mixed-vendor fleets on one floor describes what that looks like once the fleet is in.

Decide posture per site, and expect to revise it

A site planning for an unknown fleet also does not know what it will want to connect to. Some future vendor's fleet software may run in the building and deserve a declared route. Another's may run in a cloud the site does not want to touch. Posture is a choice per site, not a different appliance, and within a site it is made route by route.

That means a site can install the pool air-gapped on the first day, with no path out and updates arriving as signed bundles carried in by media, and declare routes later as vendors are chosen and their systems are understood. Or it can begin connected to the warehouse system and the PLCs it already secures and leave the robot vendors undeclared until they exist. Nothing about the hardware changes when the declaration does. Connecting a vendor's fleet software to the pool covers how a route is declared.

One subscription that does not move with the fleet

The commercial shape matches the planning shape. A Grid is one subscription for the configured pool: hardware, platform license, and sustainment in one line, fixed for the term. More robots on the pool do not move it. A site that installs the pool before the fleet is chosen is not paying per robot for robots it has not bought; it is subscribing to a pool for the building, and the robots that join later join it.

There are two routes. Under Facility Direct, the building subscribes to the Grid itself. Under Czar Chassis, a robot vendor or integrator ships the same Grid under its own name with its fleet, so the customer receives one system. A site that plans the pool first and later chooses a vendor who ships Chassis has not planned wrong: it is the same Czar either way, and the two routes are described on how to buy and pricing.

Who to plan it with

A pool for an unknown fleet is still installed by known people. E31 Consulting puts Element 31 engineers on site to install the pool with the operator's automation team, its integrator, and whichever robot vendors are already present. The integrator in particular benefits from a pool that is in before the fleet is, because it gives every later vendor a shared surface to meet rather than a floor to fight over.

Design-partner intake is not yet open. For how the pool fits each of the three kinds of facility Element 31 talks about, see solutions, and for the full picture of what runs on the Grid, see the technology overview.