Deployment evaluation · 16

Energy and duty cycle

Count active work, waiting, warm-up, thermal limits, charging, battery exchange and restart within the real shift.

Evidence statusEngineering evidence framework · task and site validation requiredLast reviewed: 14 August 2026
16

FUURAA thesis

Battery runtime is not productive availability when the work system includes interruptions and support.

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

Energy

Measure by task, payload, terrain and state.

02

Thermal

Track derating, cool-down and environment.

03

Shift flow

Model charging, exchange, queue 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

    How much energy produces useful work?

  2. 02

    Which states consume hidden time?

  3. 03

    What changes with payload and terrain?

  4. 04

    Can charging preserve safe coverage?

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

    State-resolved energy trace

  2. 02

    Evidence package 2

    Thermal and derating record

  3. 03

    Evidence package 3

    Shift-level availability model

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.