Acceptance testing
These clauses make acceptance a pass or fail on the worst-case gap, measured with production vehicles at operating speed while the plant runs, against the outage budget derived from the machine builder's connection timeouts.
Acceptance is where the specification becomes evidence. These clauses run the test with the real vehicles, the full fleet, and the plant in production, long enough to catch the rare roam, and pass or fail on the worst gap against the outage budget. That budget comes from the connection timeouts the machine builder sets; the test measures against it and never changes it.
Your values
Type your values, or work them out in the requirements translator. Blanks you leave empty stay marked in the text.
10.1 Test in production conditions shall
Acceptance tests shall use production vehicles at their top operating speed, [Top operating speed] [Speed unit] for [Vehicle or machine], on their real routes, with the full fleet and normal plant traffic running, while the plant is in operation.
10.2 Long enough to catch the rare roam shall
The acceptance test shall run for at least [Test duration] hours of production, cover every route, and capture every roam and every gap in cyclic traffic rather than a sample.
10.3 Pass or fail on the worst gap shall
The test shall pass only if the longest gap in valid packets on every connection, across every vehicle and route, stays inside the outage budget of [Outage budget] ms. A single gap longer than the budget fails the test.
10.4 Count events per vehicle and shift shall
The test report shall state, per vehicle and per shift, the number of gaps longer than [Gap length to count as an event] ms and the number of disconnects with their reason codes, as well as their durations.
10.5 Failure paths tested and timed shall
Acceptance shall include, in a planned window, pulling an access point uplink, bouncing a switch port, making the primary authentication server unreachable, and restarting every wireless device at once, with each recovery timed against the outage budget and the time to the last device back recorded.
10.6 Retest after change shall
The route test shall be repeated after any change to infrastructure firmware, client firmware, security settings, the channel plan, the physical layout along a route, or the fleet size, and for every new vehicle model.
About this page
Built from 7 sources: 2 standards bodies and labs, 1 protocol owner or alliance, 1 research paper or thesis and 3 vendor documents. Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made
- First published
- Last updated
Change history (1)
- First published
Cite this page
Plain
Ben Rutter. "Acceptance testing." OT Wireless, published October 6, 2026, updated October 5, 2026. https://otwireless.com/clauses/acceptance-testing/
APA 7
Rutter, B. (2026, October 6). Acceptance testing. OT Wireless. https://otwireless.com/clauses/acceptance-testing/
BibTeX
@misc{rutter2026acceptancetesting,
author = {Rutter, Ben},
title = {{Acceptance testing}},
year = {2026},
howpublished = {\url{https://otwireless.com/clauses/acceptance-testing/}},
organization = {OT Wireless},
}