The Warehouse Wi-Fi Upgrade
A mid-sized distributor runs three warehouses on a single flat network. Barcode scanners on the picking floor lose connection for 10-40 seconds several times an hour, forcing operators to rescan and slowing throughput. The IT manager proposes replacing all access points with a newer standard and adding a second internet circuit. A network assessment shows: 60+ access points at high power, all on the same channel plan, with overlapping coverage; the corporate office and warehouses share one VLAN; a legacy inventory application broadcasts discovery traffic continuously; and the picking-floor scanners roam between access points roughly every 20 seconds as operators walk aisles. The proposed hardware refresh costs $140,000. The assessment report notes that channel overlap and excessive transmit power are the most common causes of roaming delays in dense environments.
1. Assess whether the hardware refresh and second circuit address the observed symptoms. What should be done first?
Read the worked answer
The symptoms are consistent with roaming and interference problems on a poorly designed radio plan, not with insufficient or outdated hardware. The assessment names the likely causes directly: every access point on the same channel plan with overlapping coverage and high transmit power. High power makes clients cling to a distant access point until the signal collapses, then force a slow reconnection - exactly the 10-40 second dropouts described, and exactly the cadence of a scanner roaming every 20 seconds.
A second internet circuit addresses WAN capacity and redundancy. The failures occur on the local wireless link, before traffic reaches the internet, so the circuit would not fix them. The hardware refresh might help incidentally, but replacing 60 access points without changing the channel plan, power settings, or roaming configuration would reproduce the same design on new radios.
Do first: a proper site survey, a non-overlapping channel plan per band, reduced transmit power with minimum signal thresholds for roaming, and 5 GHz preference for scanners. Also isolate the inventory application's broadcast traffic on its own VLAN, since flat-network broadcast storms add to airtime contention. These are configuration changes, not purchases.
2. The IT manager argues the refresh is justified anyway because the hardware is aging. How should leadership weigh that argument, and what decision criteria would you set?
Read the worked answer
Aging hardware is a legitimate consideration, but it is a separate decision from the outage problem and should be evaluated on its own merits rather than smuggled in as the fix.
Criteria to set:
- Root cause addressed? Score each option on whether it removes a named cause from the assessment. Configuration remediation scores high; circuit addition scores low; refresh scores neutral-to-unknown until the design is corrected.
- Measurable outcome. Define success as scanner disconnects per shift and rescan rate, measured before and after. Require a baseline.
- Cost per unit of improvement. Compare the $140,000 refresh against a modest configuration effort. If configuration alone recovers most throughput, the refresh can be deferred or staged.
- Lifecycle evidence. Ask for actual end-of-support dates, failure rates, and firmware support status. "Aging" without data is an opinion.
- Sequencing risk. Correcting the design first means the refresh, when it happens, is deployed against a known-good plan - reducing the chance of repeating the problem.
Recommendation: fund the survey and configuration work now with a defined success threshold; approve the refresh on a lifecycle schedule if the evidence supports it, but decouple the two approvals so each is judged on its own case.