Key points
Every industrial site already pays for its dead zones, whether or not anyone has put a number on them. The options for reducing that cost fall into two kinds. More Wi-Fi and private LTE or 5G add coverage, each with its own spectrum, devices and operating model. A device mesh changes what happens in the places coverage still does not reach, by letting the apps on nearby devices pass work to each other directly.
Dead zone cost per shift
A dead zone costs the minutes people spend waiting for a signal or walking back to one, multiplied by how many people are affected and how often it happens, plus the rework when records entered late turn out wrong or duplicated. No published figure fits your site, so count it from your own shifts, the way estimating the cost of downtime does for an outage.
The cost hides in ordinary work:
- Waiting for a signal. A picker, inspector or technician who cannot submit a scan or a reading stands still, walks to coverage, or writes it down to enter later.
- Idle handoffs. When every assignment, sign-off or release goes through a cloud service, two workers standing next to each other still wait for a round trip neither of them needs. A forklift waits for a release, a crew waits for a permit to show as approved.
- Paper and re-entry. Work recorded on paper during a gap has to be typed in again, and some of it is typed wrongly.
- Conflicting work. Two devices that cannot see each other’s updates send two people to the same job, or move the same pallet twice.
For each process, write down how often a gap interrupts it, how long the interruption lasts, how many people wait, and what it costs to fix the records afterwards. That per-shift figure is what each option below should be judged against, not its coverage map.
Wi-Fi, private 5G and device mesh compared
Wi-Fi, private 5G and a device mesh solve different problems. Wi-Fi and private cellular networks are infrastructure that give devices a path to the site network. A device mesh is software that lets devices work with each other over whatever links they have.
| More Wi-Fi | Private LTE or 5G | Device mesh | |
|---|---|---|---|
| What it is | Access points cabled to the site network | Small cells plus a core network, which can sit entirely on site | Software in the apps that lets nearby devices relay for each other |
| Spectrum | Unlicensed 2.4, 5 and 6 GHz bands, with no protection from interference | Licensed or shared spectrum, which depends on the country; in the US, CBRS at 3550-3700 MHz | The devices’ own Bluetooth LE and Wi-Fi radios |
| Devices that can use it | Anything with a Wi-Fi radio | Devices that support the band and hold credentials for the network | Devices running an app built with the mesh software |
| Who runs it | Site IT or a managed service provider | The site, an integrator, or a mobile operator | The team that builds the app |
| When the controller or core is unreachable | Depends on the design; a cloud-managed network can keep running on its last configuration | The core handles access, mobility and sessions, so it has to be reachable; CBRS radios also depend on their Spectrum Access System | There is no central controller; devices keep exchanging data while they are in range of each other |
| What it cannot do | Reach places with no access point, or guarantee clean spectrum | Serve devices without band support or credentials, or reach places with no small cell | Carry bulk traffic, give general network access, or bridge distances no device covers |
Extra Wi-Fi for indoor coverage
More Wi-Fi is enough when the work happens in places you can cover with access points, the devices already have Wi-Fi, and occasional interference is tolerable. It reuses the network skills and equipment most sites already have, and it needs no new device credentials.
Newer generations help in busy buildings. The Wi-Fi Alliance describes Wi-Fi 6 as adding OFDMA, which shares a channel among many devices, and target wake time, which saves battery, and says it performs better in dense environments and IoT deployments. Wi-Fi 6 also brought Wi-Fi into the 6 GHz band alongside 2.4 and 5 GHz.
Two limits remain. Wi-Fi uses unlicensed spectrum, and in the United States the FCC’s Part 15 rules say such devices have no right to any frequency and must accept interference from other users. And Wi-Fi only exists where access points do, so yards, outdoor rows, vehicles and the far ends of a building stay gaps unless someone installs and powers more radios there.
How the network is managed also matters when the internet drops. Cisco Meraki, for example, documents that its access points keep running on their last known configuration if they lose the management cloud, and that user traffic flows to its destination on the LAN without passing through that cloud. Other vendors and controller designs behave differently, so ask.
Private LTE and 5G for industrial sites
Private LTE or 5G pays off when a site needs things Wi-Fi does not offer: spectrum protected from interference, control over exactly which devices may join through SIM or similar credentials, and one managed network for people and machines that move across the site. When the FCC created the Citizens Broadband Radio Service in 2015, it wrote that manufacturers, utilities and other large industries could build private wireless broadband networks to automate processes that need some interference protection and are not appropriately outsourced to a commercial cellular network.
What you take on in return:
- Spectrum rules. They vary by country. In the US, CBRS has three tiers. Incumbents, such as federal radar systems, are protected from CBRS users. Priority Access Licenses, each a 10 MHz channel in one census tract for three years, are assigned by auction. General Authorized Access is allowed by rule across the band, as a low-cost entry point similar to unlicensed access, but gets no interference protection from other CBRS users. A Spectrum Access System authorises every radio by location and frequency before it transmits.
- A core network. 3GPP’s 5G system has core functions that manage access and mobility, sessions and user data. For a standalone non-public network, 3GPP describes a deployment where all of those functions sit inside the organisation’s premises, separate from the public network. Someone has to run and maintain that core.
- Device support. A device must support the band the network uses and hold credentials for it. 3GPP introduced network identifiers to identify and select these networks, and onboarding so devices can obtain credentials. Not every phone or handheld will qualify, so check every model.
- Standards that keep moving. 3GPP formally specified non-public networks in Release 16, and added industrial IoT and low-latency work in Releases 16 and 17. Equipment and devices support different releases.
A private cellular network is still infrastructure. Its radios, power and core can fail, and it has edges like any other network.
Device mesh alongside Wi-Fi or 5G
A device mesh helps wherever coverage ends or a central service is slow or unreachable, because it lets the apps on nearby devices exchange work directly. It is not another network to install. It runs inside the apps on handhelds, phones, tablets and gateways.
That changes the cost in the per-shift sum above:
- Handoffs between nearby people no longer wait on a round trip. An assignment, a sign-off or an inspection result can go from one device to the next over Bluetooth LE or a direct Wi-Fi link while both are in range.
- Work done in a gap moves toward coverage. A device in a dead zone can pass its records to a neighbour, such as a vehicle terminal or another handheld, that carries them on, as store and forward does. The warehouse and yard version of this describes the same pattern.
- An outage of the internet link does not stop local work, as long as the devices and the site network that remain can carry it.
A mesh also has limits. It carries only the application’s own data, its reach depends on devices being near each other, and it is not built for bulk traffic. The system of record still decides conflicts that need an authority.
Combining Wi-Fi, private 5G and device mesh
Most sites combine them by job: Wi-Fi where it is cheap to install, private cellular where the site needs protected spectrum and managed mobility, and a device mesh in the apps so the remaining gaps and failures cost less. A typical order of work:
- Measure the per-shift cost of gaps for each process, as above, and map where they happen.
- Fill the cheap gaps with Wi-Fi inside buildings where access points can be cabled and powered.
- Consider private LTE or 5G for large outdoor areas, moving equipment, or processes that need interference protection, after checking spectrum rules and device support.
- Build the apps to keep working across any gap that is left, with local storage, an outbox, and device-to-device handoff, and test them with each network switched off in turn.
- Keep one system of record that accepts records once they arrive, and give every record an ID so a retried upload is applied once.
The order matters because each step reduces what the next has to cover. No network design removes the need for step 4, since every network has an edge and a way to fail.
Offline Protocol as a software device mesh
Offline Protocol is a device mesh in software, not a network you install. Its SDK runs inside apps on iOS and Android phones and handhelds, and on Linux, macOS and Windows gateways through its Python package. It lets those devices discover each other, exchange end-to-end encrypted messages and shared records, and call services on each other over Bluetooth LE, Wi-Fi peer streams, the site LAN even when that LAN has no internet, and an internet relay. Its DORS component scores the available paths and moves traffic between them as conditions change, and a message relays across several devices or waits in a queue until a path to its recipient appears.
It does not replace Wi-Fi or private 5G, adds no spectrum, and carries only the app’s own data. It works over whichever site network you choose, and in the gaps between networks. Its docs make one point every buyer should test: switching off the internet proves the workflow does not need the cloud only if the path that remains actually carries it.