System anatomy · 08

Fleet, teleoperation and operations

Design dispatch, remote assistance, charging, updates, maintenance, incident review and retirement as one operating layer.

Evidence statusEngineering evidence framework · task and site validation requiredLast reviewed: 14 August 2026
08

FUURAA thesis

A robot that needs support is not incomplete; a support system that is invisible and unmeasured is.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

Fleet state

Track configuration, location, task and health.

02

Remote authority

Control identity, session, latency and handback.

03

Lifecycle

Govern update, maintenance, incident and retirement.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    Can every intervention be attributed?

  2. 02

    What happens on link loss?

  3. 03

    How are configuration differences controlled?

  4. 04

    Which support load limits scale?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    Fleet configuration register

  2. 02

    Evidence package 2

    Remote-session audit record

  3. 03

    Evidence package 3

    Support and lifecycle ledger

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.