Classes / Fleet & Robotics class / Rover Ops Department
Rover Ops Track: Autonomy, Field Maintenance and Drones · Module 4 of 4 · about 30 min
Running a fleet remotely
Remote fleet roles can involve planning, monitoring and assistance when a machine stops, requests help or approaches unsupported conditions. The actual role and system design determine whether assistance, direct control or another response is appropriate. We do not assume every remote operator can instantly take over every autonomous machine.
Remote work is still site work. Operators need to know the site rules, the traffic plan and how a machine behaves so they can tell a sensor glitch from a real hazard. Many fleets keep people out of autonomous zones entirely, and anyone entering must be tracked and authorized.
Communication delay and loss affect remote capability. The actual system needs its approved lost-link fallback appropriate to the task, which can include safe stopping for a ground system. That example is not a universal aircraft or machinery command. A clear display does not establish current scene information or instant response.
The job is part dispatcher, part mechanic and part data analyst. Good operators log every intervention with what happened and why, because those records help engineers fix the software.
We distinguish remote assistance from a guaranteed ability to take over instantly. A camera image has a capture time, the operator needs time to interpret it and a command needs time to reach the machine. A clear image can still be stale. The actual approved lost-link behavior depends on the system and task; we do not apply one ground-vehicle stop command to every airborne or industrial machine.
Worked example, fictional constant-speed timing model: video delay is one second, operator response is one second and command delay is one second. At two meters per second, the machine travels six meters before the response begins, ignoring all other effects. That is not a stopping distance: braking, actuation, uncertainty and conditions remain unassessed. These invented numbers are not a safe operating limit.
A handoff records mode, current observations, known faults, active restrictions and unresolved actions. An old all-clear cannot establish current conditions after a change. People entering an autonomous operating area need the actual authorized traffic and energy-control arrangements, not confidence that a remote operator can always see or stop everything.
Practice, on paper: we calculate a new timing model and review an invented shift handoff. Our self-check separates response delay, stopping performance and actual operational permission. We issue no control command, enter no operating zone and set no speed limit.
Sources
Module quiz
10 questions, 8 correct to pass. You'll see what you missed and why, and you can retake it.