Scope boundary · 19

Remote operation is not hidden autonomy

Disclose route teaching, live driving, supervisory attention, intervention, remote services and retrieval labour.

Evidence statusField mission framework · task, terrain and site validation requiredLast reviewed: 15 August 2026
19

FUURAA thesis

Remote operation may be the correct architecture, but it creates different workload, communications and authority requirements.

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

Mode

Label manual, assisted, supervised, autonomous and recovery phases separately.

02

Labour

Count monitoring, driving, diagnosis, dispatch, data review and training.

03

Dependency

Record radio, network, map, dock, cloud, vendor and local support.

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

    Who acts during every mission phase?

  2. 02

    How often does autonomy request help?

  3. 03

    What service fails with the network?

  4. 04

    How is human error measured?

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

    Phase-by-phase autonomy disclosure

  2. 02

    Evidence package 2

    Human-time and intervention ledger

  3. 03

    Evidence package 3

    Dependency and outage test

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.