Network Deployment & Corporate Wi-Fi: coverage in São Leopoldo - RS

Boundaries defined before the cable

In a shared space, the project's first deliverable is not technical: it is the record of who answers for what. Which equipment belongs to which organization, which port serves which occupant, who administers the shared asset, and who authorizes changes to it.

That sounds bureaucratic right up until the first intervention. When the technician has a hand in the rack and there are three unidentified cables, the difference between a ten-minute maintenance job and a lost afternoon is precisely that record.

And there is the security consequence: in a shared rack with no defined boundary, one occupant's equipment is frequently reachable from another occupant's network. Not because anyone decided it should be — because a division was never made.

Logical separation when the physical layer is shared

When the link or the switch is shared, separation is done logically, with distinct segments per occupant and a policy that denies traffic between them by default. Each organization operates as if it had its own network, sharing only the path to the internet.

That also settles the bandwidth dispute, which is the most common complaint in these arrangements: with a cap per segment, one occupant's consumption stops degrading another occupant's work.

A lab is an environment with its own design

Wherever there is a lab — research, development, training — the requirements change on three fronts.

First, drop density: a lab bench usually needs more than one drop per position, because there is frequently more than one device per person, and some need to be connected simultaneously.

Second, isolation: it is the environment where things get installed, tested, and occasionally broken. It needs its own segment, with freedom inside and containment outside, so that an experiment cannot reach the administrative side.

Third, reconfiguration: labs change layout between projects. That calls for infrastructure with headroom and well-distributed drops, so the next build-out does not require construction work.

Classrooms and training rooms: predictable density

A classroom or training environment has a peculiar usage pattern: many simultaneous devices, all doing roughly the same thing at the same time, on a known schedule.

Sizing follows the capacity principle — more access points at lower power, each covering a smaller area, because the radio serves one device at a time and the queue grows with the number of connected clients. Turning up the power on a single access point makes things worse, by concentrating more devices on the same radio.

The aggravating factor in this environment is simultaneity: thirty people starting the same download in the same minute produces a spike that an environment with distributed usage never sees. It is worth accounting for that in both sizing and prioritization.

Turnover and what it demands of the network

An environment with heavy churn of people benefits from one design decision: individual authentication on the network, including the wireless network, instead of a shared password.

A shared Wi-Fi password in a high-turnover environment is, in practice, a public password — and changing it means reconfiguring every device belonging to everyone. With individual authentication, a departing person's access is revoked on its own, without affecting anyone else.

The sectors that drive demand in São Leopoldo

Services, industry, technology, and education make up the city's profile. Technology and education concentrate the labs, the training rooms, and the turnover. Industry calls for coverage across production areas and equipment isolation. Services firms need stable workstations, voice, and access to cloud systems.

How we run the deployment

It starts with a visit and an on-site survey, with the environment in use, and — in a shared space — with the mapping of boundaries: who occupies what, what is shared, who administers the shared asset.

The survey produces the design — segments per occupant and per environment type, cabled drops with headroom at the benches and at expansion positions, coverage sized for simultaneous devices in rooms used collectively, individual authentication, and a cap per segment.

Execution proceeds in stages, keeping the current environment running until validation, scheduled outside peak-use hours. Closeout includes testing every drop, verifying coverage and capacity with the real devices, and the documentation — including the boundary record, which is what sustains remote service within 45 minutes.