Networks & Wi-Fi
Coverage is a measurement, not an opinion.
Network complaints are usually reported as Wi-Fi complaints and are usually neither. They are a flat network with no segmentation, an access point count chosen from a floor plan rather than a survey, or a link with no monitoring on it. We measure first, because every one of those has a different fix and guessing between them is how an organization buys hardware that changes nothing.
- Coverage measured before and after
- SurveyedCoverage measured before and after
- Equipment, guest and corporate separated
- SegmentedEquipment, guest and corporate separated
- Every firewall rule has a stated reason
- DocumentedEvery firewall rule has a stated reason
Sounds like
You might recognise one of these.
The Wi-Fi drops in the warehouse and nobody can tell us why.
Everything is on one flat network, including the machines and the guest devices.
We find out the line is down when someone tells us they cannot work.
The last person who understood the firewall rules left two years ago.
What this includes
The work, specifically.
Not every engagement needs all of it. This is the range we cover and what each part is actually for.
Site survey and coverage design
Measured coverage and interference, including the places people actually work: racking aisles, cold stores, yards and stairwells. Access point placement follows the survey.
Segmentation
Separating corporate, guest, voice and equipment traffic so a compromised device in one does not have a path to the others.
Firewall and routing
Rules that are documented and reviewable, with the reason for each one recorded, so the next person does not inherit a ruleset nobody dares change.
Monitoring and alerting
Link, device and coverage monitoring that tells you before a user does, routed to a person who is expected to act on it.
Structured cabling and refresh
Specification and coordination of the physical layer, including the switch and cabling refresh nobody has budgeted for.
What you get
Deliverables, not documents.
- A survey with measured coverage and interference, before and after
- A documented network diagram, current as built
- A segmentation design with the reasoning for each boundary
- A reviewed firewall ruleset with per-rule justification
- Monitoring with alerts routed to named people
Shapes
How this usually runs.
Survey and network review
1–2 weeksMeasured coverage, the current topology drawn accurately, and what is actually causing the symptoms being reported.
Design and deployment
3–8 weeksSegmentation, hardware, cabling and cutover, scheduled around the times the operation can absorb it.
Monitored operation
OngoingMonitoring, firmware, rule changes and periodic re-survey as the building and the operation change.
Tooling
What we build it with.
No tool here was picked because it was new. Where we do reach for something novel, it is in one place, for a stated reason, and it is written down.
- Wireless
- Routing and switching
- Edge security
Proof
Where this has been done.
Questions
Networks, honestly.
Often not. The survey usually finds that placement, channel planning and segmentation account for most of the symptoms, and those are configuration. Where hardware genuinely is the limit we say which units and why, with the measurement behind it.
Yes, and carefully. Plant and control networks have constraints that office networks do not — some equipment will not tolerate a scan, let alone a reboot. Where the work crosses into control-network territory we bring in the OT and ICS practice from the cybersecurity division rather than improvising.
Cutovers are scheduled around when the operation can absorb them, and the plan says what happens if a step has to be reversed. For sites that genuinely cannot stop, we stage the change so each phase is independently reversible.
Often paired with
Next step
Tell us what’s breaking.
Forty-five minutes, no charge, no deck. We’ll tell you what we’d do, what it would likely cost, and whether you should be building this at all.