An application is not a category of robot — it is a loop that starts somewhere, ends somewhere, and has to close every time without a person walking the route. These four close cleanly. Each one is written up with the model that runs it, the perception it needs, and what breaks it.
A line-side station runs out of cartons on a rhythm the line sets, not the warehouse. The loop is store → station → empty return, and it has to arrive before the station is empty, not after somebody calls for it.
The operator stays at the station. The replenishment run becomes a mission with a schedule, and the schedule is the thing being optimised — not the robot's speed.
| Typical model | X13 — 600 kg, 950 × 650 mm, 2.0 m/s |
| Perception | Dual LiDAR 360°; ToF where operators reach into the lane |
| What it replaces | Replenishment walking and the "we're out" phone call |
| Install | 2 weeks, one floor |
Someone parks a cage in the drop zone. The mission needs a defined exception — wait, reroute, or escalate — agreed before go-live.
Counting moves rewards a busy robot. Counting on-time deliveries rewards a line that never stopped.
Distance, demand and shift length give a fleet estimate with the arithmetic shown.
The most common pallet task in a plant is not stacking. It is moving a loaded pallet from one place to another on the same floor — dock to staging, staging to production, production to dispatch.
That is a horizontal job, and it does not need a forklift, a licence, or an operator sitting in an aisle waiting for a gap.
| Typical model | PX33 — 1,500 kg, 120 mm lift, 2,182 mm aisle |
| If it also stacks | FX33 — 1,500 kg to 2,000 mm lift |
| Perception | 4× LiDAR + ToF; shrink-wrap reflections tested with the real load |
| Install | 2–3 weeks depending on dock integration |
A missing deck board means the forks enter at an angle. The acceptance test uses your pallet pool, not a new pallet from the demo room.
2,182 mm is the rated aisle for the PX33. A measured aisle at 2,100 mm is a different project, and the survey finds it on day one.
Pallets per hour, distance and payload give a fleet estimate with the arithmetic shown.
Pickers walk to the rack, find the line, walk back. Most of that time is walking. Goods-to-person inverts it: the rack comes to a fixed station and the picker stays where the light is good and the scanner is mounted.
The gain is not robot speed. It is that picking time stops including travel time — and the station becomes a place you can measure.
| Typical model | X13 or X22 with a shelf or tote carrier |
| Perception | Dual LiDAR + ToF — shelf overhang and pick faces are real geometry |
| What it replaces | Travel time inside the pick cycle |
| Install | 3 weeks — the pick station usually has to be rebuilt |
Add robots until the picker is the bottleneck, then stop. Beyond that point you are buying queueing, not throughput.
Measured at the station, with a real picker and real stock — not a robot library figure.
Lines per hour and travel distance give a fleet estimate with the arithmetic shown.
When the storage has to be dense, the aisles are narrow and the bodies have to be small. The S130 is 710 × 510 mm for exactly this: tote and bin transport where a full-size platform physically will not fit.
High move counts, short distances, and a packing bench that never waits. This is the loop where throughput per square metre is the number that matters.
| Typical model | S130 — 60 kg, 710 × 510 mm, 3.0 m/s |
| Perception | LiDAR + ToF; narrow-lane clearance is the binding constraint |
| What it replaces | Walking between dense storage and the packing bench |
| Install | 2 weeks |
Cracked totes and inconsistent stack heights. The gripper or conveyor interface has to tolerate your worst tote, not your best.
Dense storage only pays if the move count is high. A slow loop in a tight aisle is expensive floor space.
Totes per hour and aisle length give a fleet estimate with the arithmetic shown.
Every deployment starts with a single workflow. Proven numbers on one loop fund the next, and the same platform, software and Fleet Manager carry across — because the body changes and the intelligence does not.
Pick the highest-cost workflow. Pilot a small fleet on a defined lane.
Throughput, on-time and labour against the baseline you measured first.
Extend the same fleet to pallet transport, goods-to-person and put-away.
One interface, WMS and ERP integrated, no per-robot licence.
Tell us the workflow and the floor. We will tell you which body runs it, what it needs to see, and how long it takes to install.