Reading method · 04

Service modes and authority

Separate autonomous service, teleoperation, setup, charging, maintenance, fault response and emergency handling.

Evidence statusService decision framework · site and user validation requiredLast reviewed: 14 August 2026
04

FUURAA thesis

People need to know what the robot is doing, who controls it and what happens next in every mode.

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

Modes

Name permitted motion, sensing, recording and remote access.

02

Authority

Assign who can dispatch, pause, override, restart and update.

03

Transitions

Make mode changes observable during faults and hand-offs.

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 a bystander identify the state?

  2. 02

    When does remote control begin?

  3. 03

    Who may restart after contact?

  4. 04

    What happens when the network is lost?

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

    Mode and authority diagram

  2. 02

    Evidence package 2

    Access and override records

  3. 03

    Evidence package 3

    Fault and restart drills

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.