Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

04 / 09

Case file

04 · IT & Networking

Enterprise Wi-Fi.

Coverage you can measure, not just claim.

Wi-Fi 7 and Wi-Fi 6E enterprise wireless — Cisco, Aruba, Juniper Mist, Netgear — site-surveyed to the building's actual cell-edge SNR.

Enterprise Wi-Fi — representative visual (illustrative scene, not a project photograph)
Wi-Fi coverage: estimated versus surveyed
Wi-Fi coverage: estimated versus surveyed
AspectEstimated coverageSurveyed approach
Access-point placementFrom catalogue square-footagePredicted in Ekahau against the floor plan
ValidationAssumed at handoverHeat-map handover and post-install testing
Security policyDefault template802.1X / NAC to the organisation's actual policy

Educational comparison — not about any specific installer.

How we approach it

Wi-Fi planned for the building it serves

Reliable wireless comes from designing to the space and the way it is used, then keeping the network tuned as that use changes.

Designed to the space and use
Coverage intent is shaped around the building and its usage during design and BOQ / scope alignment. Detailed placement and topology stay in the design set, not on the page.
Verified on handover
Before handover the network is tested against the agreed intent, so what is delivered matches what was planned.
Tuned as use grows
Device counts and floor layouts shift over time; an AMC scope can include periodic wireless health checks and firmware upkeep so performance holds as the estate changes.

/ The discipline, in detail

How we approach enterprise wi-fi.

An access point's catalogue square-footage and a real building's coverage map are unrelated documents. We site-survey every deployment with Ekahau or AirMagnet, model the building's RF before the first AP is mounted, and place hardware to the actual cell-edge SNR your devices need. Roaming is tuned, channel plans are documented, and the controller is configured to the security and segmentation policy the organisation actually has — not the one pasted from a default template.

On record

Every enterprise wi-fi engagement is documented end-to-end — design, programming, commissioning, calibration — and handed over with the files our successors would need if we were never to return.

/ RF planning

Density before hardware

Access-point density and channel planning across floors — coverage is designed from client counts and walls, not from a catalogue page.

Enterprise Wi-Fi density topologyA three-floor mixed-AP-class Wi-Fi deployment. Wi-Fi 6 four-stream APs (Aruba AP25 class) sit in high-density public areas — lobby, conference hall, dining; Wi-Fi 5 APs (Aruba AP11 class) sit in lower-density guest zones — corridors, suites, back-of-house. Mesh backhaul on a managed Cisco backbone delivers seamless roam across all three floors with no dead zones. Channel assignment avoids co-channel interference between floors; per-floor PoE budgets are calculated on the L2 switch stack.Enterprise Wi-Fi · mixed-AP-class · attenuation-aware densityWi-Fi 6 in public density · Wi-Fi 5 in lower density · mesh backhaul · per-floor PoE budgetFloor 2 · VIP suites + protocol5 GHz · ch 36/52/100AP25AP25AP11AP11AP11AP11AP11AP11PoE budget · 248 WFloor 1 · Conference + meeting rooms5 GHz · ch 40/64/108AP25AP25AP25AP25AP11AP11AP11AP11AP11PoE budget · 248 WGround · Lobby + dining + reception5 GHz · ch 44/60/116AP25AP25AP11AP11AP11AP11AP11AP11PoE budget · 248 WAP-class density comparisonMixed-class vs uniform · attenuating structuresMixed-class (chosen)25 APs · 8× AP25 + 17× AP11· AP25 in lobby + conference + dining· AP11 in corridors + suites + back-of-house· Seamless roam · attenuation-awareUniform Wi-Fi 6 (over-provisioned)25 APs · 25× AP25· Cost penalty ≈ 2.4× without throughput gain in low-density zones· PoE budget escalates across the L2 stack· Marketing-led, not engineering-ledUniform Wi-Fi 5 (under-provisioned)25 APs · 25× AP11· Capacity collapses in lobby + conference at peak· Co-channel interference across high-density zones· Roaming feels sluggish on hand-offMixed AP-class density beats uniform deployment in attenuating structures — protocol-grade roam without over-provisioningChannel assignment avoids co-channel interference between floors; PoE budget calculated per L2 switch stack
Indicative density pattern — illustrative, not a project-specific plan; actual AP class, count and placement follow a site survey.

Diagrammatic view — a system planning illustration for design discussion, not a project drawing or live interface.

/ Sister services

The rest of it.

A serious brief usually crosses two or three of these. Read across the discipline — we deliver them as one contract.

/ Plan it right

Enterprise Wi-Fi — getting the brief right.

Common mistakes to avoid

  • Estimating access-point count from square footage instead of an RF survey — wall construction and ceiling height decide coverage, not floor area.
  • Designing for coverage when the real constraint is capacity — concurrent devices per area is what breaks Wi-Fi in dense offices, classrooms and hotels.
  • Mounting APs where the ceiling is convenient rather than where the RF model puts them, then wondering why roaming breaks between floors.
  • Leaving cabling and PoE budget out of the wireless design — every AP is also a cable run, a switch port and a power draw.
  • Running one flat SSID for staff, guests, cameras and devices with no segmentation policy behind it.

What to share before a quotation

  • Floor plans, with wall construction and materials noted where known.
  • The device population — concurrent users, device types and the applications that matter (voice, video, point-of-sale).
  • Existing switch infrastructure and its PoE headroom.
  • The security intent — guest access, 802.1X, and how cameras and IoT devices are segregated.
  • Coverage expectations for outdoor areas, lifts, stairwells and back-of-house.

/ Frequently asked

Enterprise Wi-Fi — what buyers ask first.

How many access points does a 10,000 sq ft office need?

A 10,000 sq ft office typically needs 6–14 access points, depending on wall density, ceiling height and the number of concurrent users per square foot. We do not estimate — we predict in Ekahau against the floor plan and validate on site.

How do you design a Wi-Fi network properly?

Through a predictive site survey using the actual building floor plans, then a post-install validation survey with a calibrated Wi-Fi analyser at every workstation. Access points are sited to actual cell-edge SNR, not to access-point catalogue square-footage. This is the single most important design decision and the one most often shortcut.

How many access points does a typical office floor need?

Roughly 1 AP per 1,500–2,500 sqft for office work, 1 per 800–1,200 sqft for high-density (boardrooms, classrooms, conference auditoria), 1 per 3,000–4,000 sqft for warehouse-low-density. The site survey adjusts these benchmarks to the actual building.

Aruba, Cisco or Mist (Juniper) for enterprise Wi-Fi?

Aruba CX and Mist are the two strongest premium choices — Mist's AI-driven optimisation is genuinely useful for large deployments; Aruba's policy-driven security model is a defining strength on the platform. Cisco Catalyst is the safe enterprise default. We deploy all three.

Should guest Wi-Fi be on the same APs as staff Wi-Fi?

Yes, but on separate SSIDs with VLAN-isolated traffic and a captive portal for guest. Multi-SSID on the same AP hardware is standard; running separate AP hardware for guest is a waste of capital that does not improve security beyond what proper VLAN segmentation already delivers.

How do you handle Wi-Fi roaming for mobile-heavy environments?

Through 802.11k, 802.11r and 802.11v fast-roaming features tuned in the controller. For voice-over-Wi-Fi (VoWiFi) and real-time location services, we tune RF coverage to ensure -65 dBm at every position so handoff doesn't drop calls. Hospital and warehouse deployments need this discipline; office deployments can be more relaxed.

Which Wi-Fi and switching brands does TechnoGuru work with?

On the wireless side we work with Netgear, HPE Aruba, Ruckus and Ubiquiti, with PoE switching sized to power the access points, cameras and phones on the same fabric. The family is chosen against the site type — corporate floor, hotel, warehouse — rather than fixed in advance. Final make and model follow the area, floor count, wall material, endpoint count and bandwidth reviewed during the survey.

Can the Wi-Fi and switching double as the backbone for CCTV and AV-over-IP?

A properly sized PoE switching and cabling layer can carry Wi-Fi, IP cameras and AV-over-IP on one structured backbone with VLAN separation, which is more maintainable than parallel networks. Whether it should depends on the endpoint count, the bandwidth per stream and the headroom required, so we size it from the drawings and a survey. We do not promise a throughput figure before the design is validated on site.

· Begin

Begin a
enterprise wi-fi
brief.

Tell us about the building, the timeline, and what success looks like a year after handover. We will reply within two working days with a written response, not a sales pitch.