No tape on the floor, no reflectors on the racking, no civil works. The installation is a survey, a map, a mission build and a safety test — and the same five steps every time.
Below is what each step is, roughly how long it takes, and who is doing the work.
Timings are typical for a single-application deployment on one floor. Fleet size, WMS integration and door or lift control are what push a project from two weeks toward four.
Someone walks the route with a laser measure. Aisle widths, doorway clearances, ramp gradients, floor surface, charging position, network coverage and the places where people and forklifts cross. The output is a measured plan, not an impression.
The robot is driven or drives the route once and builds the map itself. Keep-out zones — glazing, mesh, dock edges — are marked at this stage, while somebody is standing in front of them and can point at the problem.
Pickup points, drop points, routes, traffic rules and handshakes are assembled as nodes in the Code-Less editor. No code, but it is still engineering: the sequence has to survive a station being blocked, a load being wrong, and a person standing in the aisle.
Stop distances measured, fields tested at each speed, the actual load carried — not a demo box. Emergency stop, obstacle intrusion, and recovery from a blocked lane. This is the step that produces a signed acceptance document.
Operators are trained on the exception paths, not the happy path. Spares are handed over, the support channel opens, and the first weeks are watched. The floor should not notice the day the robot started.
The Code-Less Monitor is the live view of the floor: every robot, the step it is executing, and the step before it. If a robot stops, this is where you find out why — not from a phone call an hour later.
Each mission is a node graph. The monitor shows them running side by side, so a stalled branch is visible as a stalled branch rather than a lower number.
Current step, step type, sequence, coordinates, last completed step. Enough to tell "waiting at a station" apart from "stuck".
Log lines name the action and the target — checking a stack, docking a pick. Written for the person on the floor, not only for the engineer.
Deployments slip for boring reasons. Every one of these has delayed a project; none of them is a robot problem, and all of them are cheaper to find during the survey than during go-live.
A two-week install is not a two-week promise. It is what the five steps take when the survey was honest and the integrations were scoped early. When they were not, the schedule says so before the purchase order, not after.
Before a fleet size, before a quote — a walk of the route and a measured plan. Everything after that is arithmetic.