System anatomy · 05

Mobile platform and safe movement

Evaluate drive, braking, localisation, obstacle detection, battery and load interface as one moving system.

Evidence statusDeployment decision framework · site and workflow validation requiredLast reviewed: 14 August 2026
05

FUURAA thesis

Stopping performance is conditional on load, speed, floor, sensing and response latency.

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

Motion

Measure speed, steering, braking and stability across load states.

02

Perception

Challenge object size, reflectivity, occlusion and approach paths.

03

Safe state

Define behaviour after localisation, power or communication loss.

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

    What is the worst-case stopping distance?

  2. 02

    How is load shift detected?

  3. 03

    Which objects remain difficult to detect?

  4. 04

    Can the truck wait safely after a fault?

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

    Load-speed-floor test matrix

  2. 02

    Evidence package 2

    Detection and stopping results

  3. 03

    Evidence package 3

    Fault and safe-state verification

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.