Skip to content

Operation Types

When you create an operation, you start by choosing a preset — a ready-made step structure for a common kind of job. The preset decides what you'll fill in next: a haul job asks for queue, load, and dump locations; a coverage job asks for fields; and so on.

Pick the preset that matches the work you want done.

Haul Job

A cyclical pickup → transport → dump job. Robots stage at a queue, load, drive a route to the dump location, drop their load, then return and repeat.

Use it for material movement — hauling, spoil removal, or any load-and-dump cycle that runs continuously.

You'll set a queue location, an optional load location, the routes to and from the dump, and the dump location. You can cap how many robots wait at a location and set a minimum spacing so they don't crowd.

Series of Routes

A sequence of stops that robots run in order, starting from a queue. Each step is a route or a location the robot visits.

Use it for guided tours, multi-stop deliveries, inspection rounds, or any ordered run.

You'll add the steps in order and, for each one, choose its location and an optional limit on how many times it runs.

Charge / Refuel

Sends robots to one of several chargers or fuel stations. Each station is used by one robot at a time and shows as occupied while in use.

Use it to keep the fleet topped up. Pair it with a Min Battery or Min Fuel prerequisite so that only robots that actually need a top-up are sent.

You'll list the charging or fuelling stations the robots can use.

Field Rows Coverage

Covers one or more field areas. Each field is claimed by a single robot and marked complete when it's fully covered.

Use it for mowing, spraying, seeding, sweeping, or any area-coverage work. Add several fields to split the work across the fleet — each robot takes a field.

You'll list the field areas to cover.

Advanced

Builds an operation step by step when none of the presets fit. You configure each step's location and behavior individually, and you can add final steps that only run at the end of the job (for example, parking or cleanup).

Use it for custom jobs that mix step types or need fine control.

None (blank operation)

Saves a placeholder operation with no work attached. Use it to reserve a named operation you'll build out later.