Hotel WiFi & Network Case Study: 500 Rooms, 383 APs

When the engineering team for a 500-room hotel in Central Africa sat down to design the WiFi and network backbone, they were not solving a theory problem. They were solving a practical one: how do you give every guest, in a building with a rooftop revolving restaurant and a basement control room, internet that actually works — when the nearest network engineer is a plane ride away?

This is the story of how that network was designed: 383 access points mapped floor by floor, a three-tier switching architecture, PoE powering everything over one cable, cloud management standing in for a local IT team, and 90 days of surveillance footage stored on a single embedded storage unit.

The Project: 18 Floors, 500 Rooms, Zero Local IT

The hotel — the same 18-story project covered in our floor-by-floor ELV design case study — is finishing construction and opening next year. The building mixes transient guest rooms, suites, penthouses, offices and a rooftop revolving restaurant, each with different network demands.

The constraints were real:

• 500 rooms and public areas need reliable WiFi, not “best effort” coverage
• CCTV and IPTV share the same building infrastructure and must not interfere
• No local IT department — the maintenance model has to work remotely
• Unreliable terrestrial internet — the WAN itself cannot be taken for granted

The design that came out of those constraints is worth studying because every number in it is real.

The Access Point Plan: 383 APs, Three Types

The network starts with Wi-Fi 6 access points in three physical forms, chosen for three different jobs:

The full bill of materials — 383 access points in total — breaks down floor by floor:

Two decisions in this table tell the real story:

1. Guest room floors are wall-plate heavy. Floors 1–6 carry roughly 10–14 wall-plate APs per floor — one per room zone. Transient guests do not roam; they sit in the room, so per-room coverage beats long-range ceiling units.
2. The rooftop revolving restaurant gets 10 dedicated APs. A moving, glass-walled, crowded venue is one of the hardest WiFi environments in any building. It is also where guests take photos and post reviews. The AP count reflects that.

Simulated Before Installed: 2.4G and 5G Coverage Maps

Every floor of the design includes simulated signal diagrams for both 2.4 GHz and 5 GHz — done before installation, not after complaints.

The simulations caught three things that a “just put an AP every 25 meters” approach would have missed:

• Coverage holes behind thick walls in bathrooms and corridor corners
• Channel overlap between neighboring APs — the classic 5 GHz problem where more APs actually make things worse
• Capacity hot spots — the ground-floor restaurant at breakfast, the lobby at check-in — where client density exceeds what a single radio can serve

Each diagram also shows the weak-current rooms (floor telecom closets) that anchor the cabling. The AP positions were checked against where cable could actually run, so the coverage plan never left the drawing board.

The Backbone: Core, Aggregation, Access

Behind the APs is a three-tier switching architecture sized for the building’s 70-meter height:

• Core switch — a chassis unit with redundant power supplies and dual control modules, sitting in the basement control room. If a power supply or control card fails, the network stays up.
• Aggregation switches — 48-port units with 10G uplinks, one per group of floors.
• PoE access switches — cloud-managed units in each floor telecom closet that power and connect the APs and cameras.

The fiber backbone runs between floors, so a failed link on one floor cannot take out the floors above. For a hotel where an outage means guests checking out, this is the difference between a bad day and a catastrophe.

One Cable for Power and Data: The PoE Story

Power over Ethernet is how 383 APs and the camera network get fed without a second cable run. The design uses the full modern PoE range:

Three PoE features were specified because the hotel cannot afford a technician visit for every hiccup:

1. PoE watchdog — the switch detects a hung camera or AP and power-cycles just that port. The system heals itself in minutes.
2. Loop protection — a misconnected cable that would loop the network is detected and blocked instead of taking down a floor.
3. Perpetual PoE — devices stay powered during switch firmware upgrades, so maintenance never reboots the whole camera system at 3 AM.

Cloud Management: The Remote IT Department

This is the design decision that makes the project viable in Central Africa. Every switch, router, AP and camera is cloud-managed — registered to a cloud platform where the operator configures and monitors the entire property from one dashboard.

What that means in practice:

• Guided setup in about five minutes per device group — no command-line configuration, no on-site specialist required
• Remote troubleshooting down to the minute — locate a dead camera, view a live snapshot, restart the device or its switch port remotely
• One-click port restart — the most common hotel-network fix (“just reboot it”) becomes a remote action

For a property where the nearest engineer may be hundreds of kilometers away, cloud management is not a nice-to-have. It is the maintenance plan.

90 Days of Video, One Storage Unit

The surveillance side of the network has its own storage requirement: the CCTV design calls for 90-day retention. The solution is an embedded video storage (EVS) unit — a 48-bay appliance that absorbs the full retention window in one rack unit:

• Capacity: supports 20 TB enterprise drives across 48 bays
• Redundancy: RAID 0/1/5/6/10/50/60 plus N+M clustering — a failed drive or node does not lose footage
• Performance: dual CPU, 16 GB RAM (expandable), handling over a thousand camera channels
• Direct stream storage: cameras write straight to the storage appliance, with no forwarding media server in between — fewer components, fewer failure points, lower cost

The storage and the intelligent video surveillance servers sit in the 13th-floor office area — physically isolated from guest WiFi, per the project’s four-network isolation rule (CCTV, IPTV, office, guest WiFi each on their own network).

What This Case Teaches

1. AP type follows room type. Wall-plate for guest rooms, high-density ceiling for open spaces, outdoor for the terrace — not one model everywhere.
2. Simulate before you install. 2.4G and 5G coverage maps on every floor caught holes and interference before a single cable was pulled.
3. Design for remote operation. Cloud management and PoE watchdog turned “wait for a technician” into “self-heals in minutes.”
4. Redundancy is non-negotiable. Dual power and control modules on the core, fiber between floors, RAID and N+M on storage.
5. Isolate the networks. Guest WiFi, CCTV, IPTV and office each on separate switches and links — the cheapest security in the building.

Build the Same Network for Your Hotel

Every number in this case study — the 383 APs, the per-floor table, the switch architecture, the storage sizing — came from a real bill of materials for a real 500-room project. If you are building or upgrading a hotel, send us your floor plan and room count, and we will turn it into a complete WiFi, switching and storage package, quoted and itemized.

👉 Contact our sourcing team or see how our product sourcing service works.