OT Wireless
Search/Menu

Search the field guide, causes, requirements, and glossary

Readiness assessment

How ready is your plant to run mobile equipment on Wi-Fi? Answer what you can. Every gap links to the page that explains it.

Requirements

Do you know the timeout of every connection that crosses the wireless link, from the controller or vehicle configuration rather than a default?
For each vehicle type, do you know what it does when it loses the network, how long it waits first, and how it recovers?
Do you know every flow each vehicle sends and receives, its rate, and which of it is control?
Do you have each vehicle maker's published network requirements, such as signal, latency, loss, and roaming support, on file?
Is there a named owner outside the network team for each vehicle's safety functions, reaction times, and stopping behavior?

Design

Is control traffic kept off the channels that carry bulk transfers such as firmware updates, video, and log uploads?
Do the channels that carry control traffic avoid DFS channels, or do you have a tested plan for a radar event?
Is the same fast-roaming method enabled on the network and confirmed working on every client model?
Is control traffic marked, and does the marking survive every hop from the controller to the radio and back?
Have you limited the number of SSIDs broadcast on the channels that carry control traffic?
Are automatic channel and power changes turned off, or held to planned windows, on the radios that serve vehicles?
Did the survey account for racking, moving machinery, and other metal that changes position during production?
Have you confirmed that each vehicle's antennas keep a clear path to the access points in every load state?
If you plan to use 6 GHz, have you confirmed that each vehicle's radio supports it and which power class your access points will run?
Do you know the key rotation, session timeout, and reauthentication timers on the network, and what each does to a vehicle?

Validation

Have you measured the worst-case roam, not the average, on each client model under your production security settings?
Did acceptance testing use the real vehicles at their real operating speed?
Have you tested with the racks and staging areas at peak inventory?
Have you tested with the full fleet, or at least the share that runs at peak, active at the same time?
Does the measured worst-case outage fit inside every connection's outage budget with margin to spare?
Do you retest coverage and roaming after layout, racking, or line changes in a wireless area?

Operations

Do you monitor signal, retries, roams, and disconnects per area and per vehicle, with alerts when they drift?
Do wireless firmware upgrades and configuration changes go through change control, outside production, with a rollback plan?
Do you keep a spectrum plan that lists every wireless system and emitter in the plant and the channels each one uses?
Do you detect neighboring networks and rogue access points on your control channels and act on what you find?
Is there an enforced policy on personal hotspots and phones in production areas?

Incident response

When a vehicle drops, is there a written triage process that says what to check first?
Are the wireless, vehicle, and fleet manager logs kept long enough to investigate a drop, on one synchronized clock?
Can you start an over-the-air capture near the affected area soon after a drop is reported?
Do the controls and network teams have an agreed way to escalate a drop to each other, with named contacts?

Your result

0 of 30 answered. Answer a question to see a score.

  • RequirementsNot answered
  • DesignNot answered
  • ValidationNot answered
  • OperationsNot answered
  • Incident responseNot answered

A self-check, not a certification, an audit, or a safety evaluation. The score counts your own answers against questions the site's pages explain; it does not test your network.

Your answers stay in this browser and in the link. Weighting: each question counts 1 to 3 toward its area, by how directly it bears on keeping vehicles connected. Yes scores 1, partly 0.5, and no or don't know 0.