Deployment evaluation · 16

Mixed-traffic safety zone

Test crossings, blind corners, docks, falling loads, emergency routes and foreseeable pedestrian behaviour.

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

FUURAA thesis

Collision avoidance is one control inside a wider traffic and workplace safety system.

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

Separation

Use layout, barriers, timing and access control before sensing alone.

02

Interaction

Define right-of-way, yielding, alerts and uncertainty.

03

Incident

Preserve near-miss, stop and investigation evidence.

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

    Where can people be occluded?

  2. 02

    Are routes legible to visitors?

  3. 03

    Can a stopped robot block egress?

  4. 04

    How are near misses reviewed?

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

    Mixed-traffic risk and control map

  2. 02

    Evidence package 2

    Challenge-condition stopping results

  3. 03

    Evidence package 3

    Near-miss and corrective-action record

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.