ZebIQ Technology

// INSIGHTS

Building a venue network for outdoor and tented events

6 min read

A tent has no ceiling to mount to, no building earth to bond to and no power you did not bring yourself. Outdoor builds in India and the UAE fail on weather, dust and generator power long before they fail on RF. We plan an outdoor venue network as a temporary utility: weatherproof enclosures, protected cable routes, surge and earthing, bonded uplinks, and systems that keep working when the link and the DG set both drop.

Ground truth

A three-day tented conference on the outskirts of a tier-2 city has a different problem list to a convention centre. There is no structured cabling. There is no building earth. The nearest fibre termination may be 900 metres away. Power comes from a DG set that a contractor will refuel at an unpredictable moment. Temperatures swing twenty degrees between afternoon and pre-dawn, and condensation forms inside any box that was sealed shut in the heat.

RF outdoors is more forgiving in one way and less in another. There are fewer walls, so coverage travels further. Interference travels just as far. Free-space propagation is the enemy of channel reuse. We drop transmit power, stay at 20MHz channel width, and aim directional and patch antennas inward at seating, registration and F&B zones instead of hanging omnis that broadcast across the whole ground.

Monsoon changes the whole plan. Water gets into cable joints, mud swallows ground runs, and a lightning strike near an unprotected mast takes out a switch port and everything behind it. In the UAE the equivalent pressures are heat and humidity. An enclosure in direct July sun reaches internal temperatures that shorten the life of every power supply inside it.

What we measure

IP67
minimum enclosure rating for any AP or switch living outside a tent
6-10 seconds
typical DG changeover gap that every switch must ride through on UPS
INR 4-12 lakh
indicative three-day outdoor build across two or three zones

Field kit

Enclosures that breathe

Outdoor APs and switches go into IP67 enclosures with breather glands, mounted out of direct sun. A fully sealed box with no breather traps humid air and drips onto the board at 05:00.

Surge, earthing, lightning

Every mast, camera pole and outdoor AP feed gets an inline surge arrestor and a dedicated earth spike or pit. It is the cheapest insurance on an outdoor site and the first line deleted when a budget is squeezed.

Fibre between zones, copper inside them

Zones are linked with armoured fibre and each zone gets its own PoE switch with a sized power budget. Copper stays under 90m and inside the tent, which removes both the distance limit and most surge paths.

Bonded uplinks on separate carriers

We bond two or three links, fibre where the lead time allows plus cellular on different networks, with automatic failover. A single tower congested by 4,000 attendees is a predictable failure, not a surprise.

How the build runs

  1. Recce with a power and earth audit

    We walk the ground with the DG and tent contractors, mark cable routes, earth points and mast positions, and test each carrier's signal at the actual coordinates rather than trusting a coverage map.

  2. Trench, ramp and label

    Cable routes are trenched or ramped before stall build begins, never after. Every run is labelled at both ends, because at 02:00 in the rain nobody traces an unlabelled drum.

  3. Power first, network second

    The core and every PoE switch sit on UPS sized for at least 20 minutes, downstream of the DG changeover. We force a deliberate changeover and watch what reboots before the first guest arrives.

  4. Soak test through a night

    The network stays up overnight under synthetic load with monitoring running. At first light we open enclosures to check for condensation, insects and heat marks. A fault found at 04:00 is far cheaper than one at 11:00.

What usually goes wrong

Power is the first cause of an outdoor network failing, not RF. A DG changeover of six to ten seconds reboots every switch that is not on UPS, and an access point then takes another two to three minutes to boot and re-form its uplink. Add a load-shedding event during the keynote and the network appears dead for five minutes for reasons that have nothing to do with wireless. The second cause is a single-carrier uplink. Four thousand attendees congest the same tower, and the cellular link that tested at 60 Mbps on the recce delivers 3 Mbps at peak.

Then there is the honest limit. Last-mile fibre into an unserviced area outside a tier-2 city takes three to six weeks and sometimes does not arrive at all. If you approach us ten days out, plan on bonded cellular and design the event software to tolerate it. Dust storms and 45C afternoons kill unshaded switches. Tent contractors drive stakes through a cable run you buried the previous day. And a captive portal on an outdoor guest SSID with an intermittent WAN is worse than no WiFi at all, because devices sit in a redirect loop instead of failing cleanly.

Common questions

Can you run a tented event with no fibre at all?

Yes, and it is common. Bonded cellular across two or three carriers with automatic failover covers most of what an event needs, provided the critical systems are offline-first. Check-in, signage, menus and lead capture run from LAN-origin services with local DNS, so they do not care whether the WAN is up. Payments and live streaming are the two workloads that genuinely need internet, and we size the uplink for those alone.

How much does an outdoor venue network cost?

For a three-day tented event across two or three zones, a realistic range is INR 4 to 12 lakh. It moves with AP count, fibre length, mast and enclosure work, and how many nights of on-site staffing you want. Surge protection, earthing and UPS are usually 10 to 15 percent of that, and they are the parts we will not strip out to hit a number.

What about monsoon or a sandstorm during the event?

We design for it rather than hope. Enclosures rated IP67, cable joints raised off the ground and sealed, masts guyed and earthed, and spare APs and injectors sitting on the IT desk. We also agree a documented degraded mode in advance: which systems keep running on LAN only, and which we shut down deliberately so the rest stays stable.