System anatomy · 08

Field support and turnaround

Count transport, setup, batteries, charging, cleaning, decontamination, updates, spares and trained people.

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

FUURAA thesis

Availability belongs to the operating system around the robot, not the battery specification alone.

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

Deploy

Measure unload, inspect, configure, map, connect and authorise time.

02

Sustain

Track energy, spares, consumables, software, calibration and operator shifts.

03

Turnaround

Measure retrieval, cleaning, decontamination, repair, recharge and evidence upload.

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

    How many people close one mission?

  2. 02

    What is productive time per shift?

  3. 03

    Which failure waits for vendor support?

  4. 04

    Can contaminated equipment be recovered safely?

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

    Deployment and turnaround time study

  2. 02

    Evidence package 2

    Support-resource bill

  3. 03

    Evidence package 3

    Availability and maintenance ledger

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.