Services / Wireless
Enterprise LAN & WLAN
Local area and wireless networks are designed together: switching and VLANs on the wire, access-point placement from survey or drawings, and segmentation that matches how the site actually operates.
- LAN
- Switching, VLANs, uplinks
- WLAN
- Coverage, capacity, roaming
- Segmentation
- Staff, guest and IoT
- Operations
- Baselines and reviews
How a typical LAN / WLAN engagement runs
Radio design and switching design are agreed before hardware is placed.
01
Assess the building
Drawings or a survey, client density, applications, existing plant and the segmentation the organisation needs.
02
Design and deploy
Switch and AP placement, VLANs, authentication and a cutover plan that keeps production traffic on a known path.
03
Operate
Channel, firmware and capacity reviews can be included in a managed service so the WLAN remains operable after handover.
Coverage complaints are often a design problem, not a radio problem
Dead zones, sticky roaming, guest traffic on the staff VLAN and PoE budgets that cannot feed the next camera or access point all show up as “the Wi-Fi is bad”. The fix is an estate that was sized for density, authentication and the applications that will run on it — not another consumer access point on an unmarked outlet.
Guessed access-point placement
Radios placed where an outlet happened to be will not match client density or wall construction.
Flat switching
Voice, cameras, guests and staff on one VLAN share congestion and broadcast domain with no isolation.
Unplanned PoE
Access points and cameras fail or brown-out when the switch budget was never part of the design.
No configuration baseline
Firmware and SSID policy that live only on the live controllers cannot be rebuilt after a failure.
How LAN and WLAN design sit on the cabling plant
The wired LAN is the distribution layer: access and aggregation switching, VLAN design, uplinks and the PoE that feeds access points and cameras. The WLAN is the radio layer on top of that plant. Enterprise wireless is designed to the technical, coverage, capacity, security and operational requirements of each environment — not to a default vendor catalogue.
Predictive or on-site surveys inform placement. Staff, guest and IoT SSIDs are isolated to the VLANs the security brief requires. Authentication (for example 802.1X) and guest onboarding are specified rather than left as an open PSK. Controller or cloud management is chosen to match what the organisation can operate.
Where an existing estate already standardises on a platform, Verico can work within that standard. UniFi and other enterprise wireless systems are examples of platforms already encountered — not a default architecture for every site.
Switching, wireless and the policy between them
Predictable coverage and a LAN that operations can change without taking the building down.
LAN switching and VLANs
Access and distribution switching, uplink architecture and VLAN design for user, voice, camera, guest and server traffic.
Wireless surveys
Predictive and on-site surveys so access-point counts and placement follow the building, not the nearest spare outlet.
Capacity and roaming
Density, channel plan and roaming behaviour sized for the client devices and applications that will use the WLAN.
Segmentation and authentication
Staff, guest and IoT SSIDs with isolation, and 802.1X or agreed guest onboarding where the brief requires it.
PoE and cabinet planning
Power budgets, stack or uplink capacity, and rack space treated as part of the same design as the radios.
Operational baselines
Firmware and configuration baselines so the estate can be rebuilt and reviewed after handover.
What handover includes
- VLAN and SSID documentation for the in-scope estate
- Access-point placement relative to the agreed design
- Switch inventory and PoE budget notes
- Management access handed through Verico Clientzone, not the public website
Multi-site environments
SSID policy, VLAN mapping and management can be standardised across branches while still allowing site-specific RF design.
Related capabilities
These are quoted separately unless the brief asks for a combined design. They sit on the same ICT estate.
- Network Infrastructure & Structured CablingCopper and fibre plant designed, labelled, tested and documented for enterprise buildings and campuses.Infrastructure — read more
- Internet & ConnectivityBusiness internet and site connectivity engineered around availability, routing and the rest of the ICT estate.Connectivity — read more
- CybersecurityNetwork-centric security controls aligned to the LAN, WAN, identity and the organisation’s operating constraints.Security — read more
- VoIP & IP-PBXIP telephony and IP-PBX platforms integrated with the LAN, numbering plan and the organisation’s call flows.Voice — read more
- Network MonitoringVisibility of links, devices and services so faults are found before users open a ticket — where the contract includes it.Operations — read more
- Servers, Infrastructure & Managed ICTOn-premises servers, switching and storage, with managed operations and a written service agreement where required.Infrastructure — read more
Common questions
Scope, handover and what is not implied by this page.
Do you always replace the existing wireless?
No. The current estate is assessed first. Some sites need a survey and a redesign; others need configuration, segmentation and documentation brought up to an operable standard.
Is a particular wireless vendor assumed?
No. Platforms are selected to the brief and to what the organisation can operate. Existing standards on the estate are respected where they are fit for the requirement.
Can guest wireless be isolated from staff?
Yes. Guest, staff and IoT SSIDs are designed with the VLAN and firewall policy the security brief requires.
Discuss LAN and WLAN design
Request a consultation for switching, VLANs and enterprise wireless sized to the building and the applications that will run on it.