An inference pool for an automotive plant

An automotive plant is already one of the most automated buildings there is. The body shop is arms behind fences. The paint shop is sealed and robotic. General assembly runs to a takt, with vision systems checking fits and PLCs holding every interlock. None of that needs an inference pool, and none of it should be touched by one.

What the plant is adding now is a different class of machine. Humanoids and mobile manipulators are coming onto the floor for the work that stayed manual because it was too varied to fix: kitting parts into sequence racks, delivering kits line-side, handling the odd component that changes shape every model year. Those robots are general-purpose, and they lean on perception and decision models they cannot carry. The pool is for them.

Beside the line, not inside it

The first thing a controls engineer wants to know is where the pool sits in relation to the line. The answer is beside it. Czar is installed in the plant's own rack, inside the plant segment, and serves inference to robots over the plant's own network. It has no role in the PLC scan. It does not gate a station. The existing vision inspections keep running on the systems that already run them.

The humanoid that walks a kit to a station gets its perception and its next decision from the pool. The station's interlock does not know or care that the pool exists. If the pool fails, the humanoid stops, exactly as the robot vendor designed it to stop. The line continues.

Kitting and sequencing

Kitting is a recognition problem repeated all shift long across parts that look alike. Is this the left-hand bracket or the right-hand one, is this harness the variant for the trim level being built, is the kit complete before it leaves the supermarket. On-board models handle the common cases. The pool handles the lookalikes, the parts with a new supplier's finish, and the kit that has one item missing.

Sequencing adds a decision layer: which kit goes next, where the rack is, whether the aisle is clear. The pool serves those decisions to mobile manipulators from any vendor, inside each robot's latency budget. The plant's execution system remains the source of the build sequence. The pool reads from it over a declared route and serves the robots what they need to act on it.

This plant's parts, this plant's light

Perception models that arrive knowing what a bracket looks like still need to learn what this plant's bracket looks like under this plant's lights, on this plant's racks, with this plant's suppliers' finishes. Substrate adapts the models on the pool using the plant's own captures. The captures stay on the plant's hardware, the adapted weights stay on the pool, and nothing goes to a vendor's cloud.

Every adapted model is evaluated and recorded before it serves a robot. When a model year changes and the parts change with it, the plant adapts again, on its own footage, and the record shows which version served which shift.

The plant segment and posture

Plants are connected sites, with the connections drawn carefully. The pool belongs inside the plant segment, and Local Bridge permits only the routes the plant declares: the robot vendors' fleet software and the execution system, usually, and nothing else. Egress is denied by default. Camera feeds from the floor, task records, and model weights stay on the operator's hardware inside the operator's network.

A plant that wants a stricter posture for a particular area, perhaps a prototype build shop, can run that area's Czar air-gapped, with updates carried in as signed bundles. It is the same appliance with a different posture. Posture is a decision per site, not a different machine.

Tasks, roles, and the record

Site tasks for the humanoids and mobile manipulators are authored in Agency Studio and bounded: which zones, what speeds, what distances from people and from the line, which stops. A named role approves a task before it runs, and every run is recorded and replayable. The plant's safety officer gets a record to read rather than a demonstration to watch.

The commercial form is one subscription for the configured Grid, in one line, fixed for the term. Adding more humanoids to the pool does not move it. For a wider view of pools in manufacturing, see Solutions for manufacturing. For the practical steps of commissioning beside an existing control system, see Bringing a pool into a plant that already runs PLCs and vision.