Missions

A mission is a single task assigned to a robot, created from a reusable mission template.

What it is

Rover Nexus separates what a task is from when and to whom it runs:

A mission template defines the task: its parameters, the robot capabilities it requires, and an optional area or feature it applies to. Templates are reusable, so you design a task once and run it many times.
A mission is a template that has been dispatched to a robot.

Dispatch. Assign a template to a specific robot or to any capable robot in the fleet. Rover Nexus matches the template's required capabilities against each robot before sending it.
Timing. Run a mission now, or schedule it:
One-time at a future date and time
Recurring, either on chosen days (a Weekly Schedule) or at a repeating interval
Prerequisites. A template can declare thresholds (such as minimum battery, fuel, or GPS quality) that gate execution. If a robot doesn't meet them, the mission won't run on it. Maximum thresholds are also supported (useful for "go recharge" style tasks that should only run when a robot is actually low).
Sequencing. Mission templates are steps in the fleet's single operation. A template can run freely, only after a different mission, or only after one of several named mission templates. Templates can also be marked as valid starting points and ordered by priority. This lets managers build multi-step processes without creating separate operation objects.
Live tracking. Once running, a mission reports status (accepted, running, paused, blocked, completed, failed, and so on) so operators can follow progress.