Population
Define robot types, software versions, sites and inclusion rules.
Scope boundary · 20
Separate deployed, active, available and task-capable robots, then bind counts to work, time and site definitions.
FUURAA thesis
Engineering map
Each layer states the boundary to establish and the evidence needed for the next decision.
Define robot types, software versions, sites and inclusion rules.
Report scheduled, operating, available and productive time.
Connect units to comparable completed work and service levels.
Verification questions
Each question needs an object, conditions, denominator, threshold and accountable decision owner.
What exactly is counted?
Over what period was it active?
Are robot families and tasks comparable?
What outcome did the fleet produce?
Evidence to preserve
A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.
Population and inclusion definition
Availability and utilisation distribution
Comparable work and service record
Scope boundary
Vendor fleet disclosures may combine different robots, sites, definitions and time windows.
This is an engineering reading and decision framework; it does not replace application-specific risk assessment, conformity work, procurement acceptance or professional advice.
Sources and evidence status
Source dates and review status remain visible; external sources open in a new tab.
Defines exchange of order and status data between a central master control and mobile robots in intralogistics.
Enables AMRs from different vendors to share basic capability, location and operating-status information in a common environment.