Industrial Wi-Fi Network Design and Deployment

Wi-Fi is the workhorse of industrial mobility: AGVs, cranes, forklift terminals, tablets, and maintenance tools all run on it — and industrial environments are the hardest places to make Wi-Fi work: metal structures, moving machinery, RF noise, and applications that cannot tolerate a dropped packet. Industrial Wi-Fi design is an RF engineering discipline: survey, channel planning, roaming design, and validation against the real applications. The office-grade "install an access point, hope for the best" approach fails in plants within days.

Design from the Applications

Wi-Fi design starts with the traffic, not the coverage map:

• Client types and numbers — AGVs need deterministic, fast roaming; tablets need throughput; sensors need low power; cameras need bandwidth. Each application class has its own design driver.
• Roaming requirements — the killer requirement in plants: an AGV crossing cell boundaries must roam without losing its control session. Design for the client's roaming behavior (fast roaming, 802.11r) and test the handover with the real device.
• Latency and reliability budgets — which applications tolerate what? A forklift terminal tolerates a 500 ms hiccup; an AGV control link may not. The design budget per application class sets the coverage overlap and channel strategy.
• Throughput per area — machine data collection areas, camera areas, and office areas have different density needs; the design places APs by load, not by grid.

The RF Environment

Plants distort radio in specific ways:

• Reflections and multipath — metal racks, tanks, and machines reflect signals; coverage is not signal strength but signal quality (SNR, not RSSI alone). A plant Wi-Fi survey measures data rates and retries, not just bars.
• Absorption and shadowing — liquids, dense storage, and concrete block signals; forklift traffic changes the RF picture minute to minute (a truck full of liquid between the AP and the client).
• Interference — other 2.4 GHz users (Bluetooth, microwaves, neighboring plants), and the plant's own machinery (VFDs, welders, motors) generating broadband noise; a spectrum analysis is part of every survey.
• Channel planning — 2.4 GHz offers 3 non-overlapping channels (1/6/11), 5 GHz far more; the plan assigns channels to minimize co-channel interference in the overlap zones, with power levels tuned to the cell size (not max power).

Architecture and Equipment

• Industrial APs — rated for the environment (temperature, dust, vibration, mounting on machines), with the mounting and antenna options (directional for aisles, omni for open areas).
• Controllers and management — centrally managed APs (controller or cloud-managed) with the roaming, security, and monitoring features; standalone APs in a plant are a maintenance burden and a security gap.
• Segmentation — the Wi-Fi is part of the plant network design: separate SSIDs/VLANs per trust level (plant OT devices, guest, IT), with the traffic policies per zone (see the IP/VLAN design article).
• Security — WPA2/WPA3-Enterprise with per-user/device identity (802.1X), rogue AP detection, and the wireless monitoring integrated with the OT monitoring (see the cybersecurity articles); the wireless is an attack surface, not just a convenience.
• Backhaul — the APs' wired uplinks are engineered like the wireless (cabling per the industrial cabling article); a wireless network on a flaky wired backbone is a two-story failure.

The Deployment Process

1. Site survey — spectrum analysis + predictive design + on-site measurement with the real client types; the survey report is the design's evidence.
2. Install and commission — AP placement per the survey, channels and power configured, security enabled, and the network integrated with the plant's VLANs.
3. Validate with the applications — the acceptance test runs the real applications (AGV roam test, tablet throughput, sensor onboarding) along the real paths; a coverage map is not the acceptance test, the applications are.
4. Operate and review — monitoring (client counts, retries, roaming failures, AP health) with alerts; periodic re-survey (the plant changes: new machines, moved racks, new clients); the annual review keeps the design honest.

Summary

Industrial Wi-Fi is designed from the applications up: client classes and roaming needs define the coverage and channel plan; the RF reality (reflections, interference, moving shadowing) is measured, not assumed; and the deployment is validated with the real applications on the real paths. Manage the APs centrally, segment and secure the SSIDs, monitor continuously, and re-survey as the plant changes. In a plant, Wi-Fi is an industrial system — engineer it like one.

Primary references and further reading

Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.

• OASIS — MQTT 5.0 specification
• Modbus Organization — Protocol specifications
• Eclipse Foundation — Sparkplug 3.0 specification