OT Wireless
Search/Menu

Search the field guide, causes, requirements, and glossary

Start here

Pick the line that sounds like you. Each path is a few pages, in the order that makes them easiest to read.

You run enterprise Wi-Fi, and the plant floor is new

What changes when the client is a robot and a missed packet stops a line.

  1. What OT is, what its Wi-Fi carries, and why the pass mark changes.
  2. Why the plant treats a short drop as a stop.
  3. The one number your design answers to.
  4. What the vehicle does when your network goes away.
  5. Why prioritization is not a reservation.
  6. The disconnect causes, by family.
  7. Turn a vehicle and its timeouts into a wireless spec.

You are a controls engineer, and Wi-Fi is new

How the radio behaves, in terms of the timeouts and I/O you already know.

  1. From RPI and watchdogs to a roam time.
  2. Network terms, each tied to an OT concept you know.
  3. What the black channel does and does not cover.
  4. What to put in writing before the network goes in.
  5. Work out your own outage budget.

You manage a plant that runs mobile equipment

The risks, the questions to ask, and where the plant stands.

  1. What a drop costs, and why it is not rare.
  2. Score how ready the plant is, area by area.
  3. What a vendor should commit to.
  4. One-page cards for the floor and the meeting.
  5. Short essays on what goes wrong and why.

Something is dropping right now

Capture the evidence, narrow the cause, and check it against the budget.

  1. What to capture before the evidence rolls over.
  2. Describe the symptoms, get the likely causes.
  3. How each cause presents and how to confirm it.
  4. Which gaps actually break the connection.

Ticks are saved in this browser only, so you can pick up where you left off. Nothing is sent anywhere.