What we measure

These synthetic examples show measurements derived from robot-published information and declared context. The independent record brings together robot, facility, camera, and operator information while preserving the sources and limitations of each observation.

Reported, never judged.

Available measurements depend on the streams the fleet publishes, the capture scope, and the quality of the record.

1 · People and proximity

How close do robots get to people?

Closest approaches

What we observe: robot position and person position as published by the fleet.
What we derive: estimated distance between published robot and person positions, distribution over time, and event frequency.
What we do not claim: whether the published person position exactly matched physical reality, or a certified protective separation distance.

Speed while people are present

What we observe: published robot speed and person-presence signals in the same time window.
What we derive: speed distributions and time spent above a configured limit while people are reported present.
What we do not claim: that every person was detected, or that a measured speed was appropriate for the situation.

16 of 25 close approaches were under the 0.50 m rule; the closest recorded separation was 0.12 m on AMR-03 at Walkway Crossing on 12 Aug., sample record, synthetic data — Product preview · synthetic test data

Closest published separation, sample record, synthetic data — Product preview · synthetic test data

2 · Zones and operating behavior

16 exceedances of the 0.80 m/s policy occurred at Walkway Crossing; AMR-14 accounted for 6, Shift 3 for 7, and the highest recorded speed was AMR-15 at 1.11 m/s for 13 s on 12 Aug., sample record, synthetic data — Product preview · synthetic test data

Recorded speed across this moment, sample record, synthetic data — Product preview · synthetic test data

Zone exceedances

What we observe: published robot position and speed, alongside the declared zone boundaries and limits.
What we derive: where, how often, and for how long recorded motion exceeded the configured zone limit.
What we do not claim: that the configured boundary or limit matched conditions on the floor.

Exposure by zone and operating context

What we observe: published motion, location, and available shift or person-presence context.
What we derive: hours of motion and event rates by zone or operating context, with the denominator stated.
What we do not claim: that different zones or shifts are directly comparable without accounting for their operating context.

3 · Control integrity

Do robots do what they were told?

Commanded vs actual motion

What we observe: published motion commands and reported motion, aligned within the available clock accuracy.
What we derive: the size, duration, and frequency of differences between commanded and reported motion.
What we do not claim: why a difference occurred, or that reported motion is an independent physical measurement.

Stop-response latency

What we observe: a published stop command and the subsequent reported motion.
What we derive: elapsed time until reported motion meets the stated stop threshold, with timing limits disclosed.
What we do not claim: a certified braking time, or that a command reached the controller when it was recorded.

Robots kept moving after a stop command 4 times; the longest recorded delay before stopping was 1.60 s on AMR-09 at Dock 4 on 22 Aug., sample record, synthetic data — Product preview · synthetic test data

4 · Safety systems

Where do protective stops concentrate?

Protective-stop frequency

What we observe: protective-stop state transitions published by the fleet.
What we derive: stop counts and rates over recorded operating time, using a stated event definition.
What we do not claim: that each stop indicates a hazard, or that every protective stop was published.

Protective-stop concentration by location

What we observe: published protective-stop events and robot positions at those times.
What we derive: counts and rates by location, highlighting where recorded stops cluster.
What we do not claim: why stops cluster there, or that the location itself is problematic.

98 of 212 AMR protective stops occurred at Walkway Crossing, with AMR-03 accounting for the most (31) and Shift 2 accounting for 61., sample record, synthetic data — Product preview · synthetic test data

Protective stops · place × shift, sample record, synthetic data — Product preview · synthetic test data

5 · Change over time

What changed after a software update?

Before / after software updates

What we observe: published software versions or declared update times, plus recorded fleet behavior.
What we derive: changes in measurements across stated before/after windows, using the same rules and exposure basis.
What we do not claim: that the software update explains the observed difference.

Behavior drift over time

What we observe: the same published streams across successive periods, with configuration and coverage noted.
What we derive: trends in separation, speed, stops, and motion differences under consistent measurement definitions.
What we do not claim: that a trend will continue, or that it reflects a change in safety.

Humanoid 03 recovered stability 43 times across 398 autonomous task hours, with the largest concentration (26) in the Case-transfer cell., sample record, synthetic data — Product preview · synthetic test data

What changed, and what happened after?, sample record, synthetic data — Product preview · synthetic test data

6 · Record quality

AMR-22’s mission/task-state source was absent for 18 minutes on 24 Aug, from 14:12 to 14:30 UTC., sample record, synthetic data — Product preview · synthetic test data

Completeness ratio

What we observe: received messages and available sequence or timing information within the declared capture scope.
What we derive: the recorded share of the expected stream, where an expectation can be established; the denominator is stated.
What we do not claim: a completeness percentage for streams whose expected volume cannot be established.

Gaps and missing streams

What we observe: breaks in sequence or timing, and expected streams absent from the captured record.
What we derive: gap windows, affected streams, and measurements limited by missing data.
What we do not claim: what happened during a gap, or whether missing data reflects the robot, network, or capture process.

Work with us

See what your fleet already publishes.

Start with the streams your fleet exposes. Together, we can establish which measurements the record supports.

Request a pilot

What we measure

How close do robots get to people?

Closest approaches

Speed while people are present

Findings

16 of 25 approaches were under the 0.50 m separation rule.

Findings

AMR-15 at Walkway Crossing

Zone exceedances

Exposure by zone and operating context

Do robots do what they were told?

Commanded vs actual motion

Stop-response latency

Findings

Where do protective stops concentrate?

Protective-stop frequency

Protective-stop concentration by location

Findings

46% of protective stops at Walkway Crossing · 12% of motion hours · 3.85×

What changed after a software update?

Before / after software updates

Behavior drift over time

Findings

What changed, and what happened after?

Findings

Completeness ratio

Gaps and missing streams

See what your fleet already publishes.