Scope boundary · 20

Fleet count is not comparable value

Separate deployed, active, available and task-capable robots, then bind counts to work, time and site definitions.

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

FUURAA thesis

A large installed-base number cannot establish utilisation, throughput, safety or customer value.

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

Population

Define robot types, software versions, sites and inclusion rules.

02

Activity

Report scheduled, operating, available and productive time.

03

Outcome

Connect units to comparable completed work and service levels.

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 exactly is counted?

  2. 02

    Over what period was it active?

  3. 03

    Are robot families and tasks comparable?

  4. 04

    What outcome did the fleet produce?

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

    Population and inclusion definition

  2. 02

    Evidence package 2

    Availability and utilisation distribution

  3. 03

    Evidence package 3

    Comparable work and service 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.