Reading method · 04

Define operating modes

Make production, collaborative operation, teaching, setup, maintenance, fault response and restart distinct and observable.

Evidence statusEngineering decision framework · application validation requiredLast reviewed: 13 August 2026
04

FUURAA thesis

Risk often changes more between modes than between robot models.

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

State model

Name permitted motion, speed, energy, access and safeguarding in each state.

02

Transitions

Control who can change modes, from where, with which indication and confirmation.

03

Abnormal states

Include sensor loss, blocked paths, dropped parts, restart and recovery.

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 an operator identify the current mode at a glance?

  2. 02

    Which transitions can initiate unexpected motion?

  3. 03

    What access is permitted during troubleshooting?

  4. 04

    How is a safe state verified before restart?

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 transition diagram

  2. 02

    Evidence package 2

    Access, indication and authorisation test results

  3. 03

    Evidence package 3

    Observed recovery 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.