Test Scenario Builder

Turn “we need to test the robot” into a protocol an engineer can run and a reviewer can check: the conditions and obstacles, the acceptance criteria, the sensors and independent reference measurements they require, when to stop, and what the results cannot claim. The Evidence Record it would produce is generated alongside, with every result field pending until the test is run.

Runs in your browser · nothing is sent or stored · LAB-07

Neicrone test protocolNCR-P-······Dusk and wet-surface stop test

v1.0 · plan

System: Mobile robot / AMR
Environment: Logistics yard
Task: Trailer moves between gate and dock
Run matrix: 2 conditions × 2 obstacles · 10 runs each · 40 runs

01Conditions and obstacles

Wet surfaceLow light / duskStatic palletPedestrian dummy (crossing)

02Objectives and acceptance criteria

Metric	Acceptance	Reference measurement
Stop distance to obstacle	≤ 0.5 m	Surveyed markers or laser rangefinder
Path deviation (p95)	≤ 0.3 m	RTK-GNSS or total-station track

03Required sensors and independent references

· Pose (vehicle odometry)
· Time sync (PTP/NTP)
· Wheel odometry
· Camera
· LiDAR

⌖ Surface friction measurement
⌖ Lux meter
⌖ Surveyed markers or laser rangefinder
⌖ RTK-GNSS or total-station track

04Stop conditions

■ Operator e-stop on any uncommanded motion
■ Abort if a person enters the test zone outside a scripted crossing
■ Dummy only: no live pedestrian crossings
■ Abort if standing water exceeds the agreed depth
■ Abort the session if reference instruments lose time synchronisation

05Limitations

– Friction varies with water depth; record it per run.
– Light level changes across a session; log it per run.
– Results hold for this site, configuration and software version only.
– 10 runs per cell bounds the confidence of any rate metric; report intervals, not point values.