Industry Solution

Planning a Locally Deployed Sub-1G Team Network

Gateway placement, group structure and terminal allocation for sites with weak or no cellular coverage.

2026-07-288 min readKingNeed Application Team

Start from coverage, not from device count

A private network plan begins with the physical site. Draw the working area, mark the levels, walls and metal structures, and note where people actually spend time. A basement car park, a long pipe corridor and a hotel service corridor each produce a different propagation pattern, and the gateway position follows from that map rather than from the size of the order.

The second step is to identify the fixed point. Most teams have at least one location that never moves — a control room, an engineering office, a stage manager's desk. That position is usually the right place for the gateway, because it gives dispatch staff a wired connection to the rest of the site and keeps the network anchored.

Gateway placement and backhaul

Place the gateway as centrally as the site allows, with a clear path to the areas of heaviest use. In a tower, that is often a mid-level service room rather than the lobby. In a plant, it is the control room rack. In a venue, it is the backstage technical room. Avoid enclosing the unit in a metal cabinet; if a rack is required, leave the front and rear ventilation clear.

Backhaul matters more than many buyers expect. An Ethernet connection from the gateway to the site network gives the control desk a permanent audio position and keeps configuration local. Where Ethernet is not available at the ideal radio position, choose the second-best radio position with Ethernet over the best position without it.

Group and terminal allocation

Allocate terminals by function, not by department name. A department that performs two unrelated jobs — housekeeping floors and laundry, for example — may need two groups. A single gateway supports up to 32 terminals and 4 independent groups, so the plan should say which eight-person group maps to which function, and who can switch between groups during an incident.

Finally, plan the practical loop: where terminals charge, who swaps batteries at shift change, and where headsets are stored. These details decide whether the system is actually used on the second week, long after the installation visit.

  • Map working areas, levels and metal obstructions before selecting a gateway position.
  • Anchor the gateway at a fixed point with Ethernet backhaul.
  • Group by function, not by department name.
  • Plan charging, battery swap and headset storage as part of the deployment.

Need this planned for your site?

Send your working areas and team structure. We will reply with a deployment proposal and the technical details behind it.