Operational public municipal networks are beginning to appear in downtown city and even wider areas. I travel extensively and have been using these networks, but I haven’t been totally happy with my experiences. Poor performance and spotty coverage have been the biggest problems. Not all deployments are bad, but it’s surprising how many are not good. This is certainly not what everyone wants to hear, but it seems to be reality.

How do these problems arise? Part of it could be that implementers aren’t well-experienced yet in deploying city-wide Wi-Fi solutions. Implementation of a mesh Wi-Fi network is somewhat new, and the corresponding design and installation methods are much different than conventional in-building Wi-Fi systems. Also, while implementing the networks, most installers are focused on meeting deadlines. They certainly perform testing, but this is sometimes cut short when hurrying to satisfy a tight schedule. This results in problems that surface after the network becomes operational.

Regardless of the reasons, municipalities can’t afford the risk of an inadequate network, especially when they’ve fought long and hard with those objecting the deployment. Poor performance and spotty coverage will aggravate users and eventually draw resentment from the communities. If you think there were problems with those opposing the deployment during the acquisition phase, just wait till the system doesn’t work as expected, and those people will come back with a vengeance. That can be very damaging to the reputation of a municipality.

A way of preventing this potentially sensitive situation is that municipalities should be proactive and perform independent acceptance testing before agreeing that the system become operational. This is a series of tests that ensures the network meets all contracted requirements for items such as signal coverage, performance, and security after the network is fully installed and deemed ready by the implementer. Acceptance testing is an important part of the classical systems development lifecycle. Even though the implementer will likely be performing the design, installation and operational support, the responsibility for performing acceptance testing falls within the scope of the municipality.

I’m amazed, though, by how many municipalities that don’t perform acceptance testing. As a result, municipalities are incurring tremendous risk by giving the implementer all responsibility for ensuring that the system meets contracted requirements. If you’re a municipality deploying a city-wide wireless network, don’t subject yourself to the perils of incomplete testing. Take advantage of the checks and balances that acceptance testing is meant to provide.

Posted by Jim Geier

Jim Geier is an independent consultant and founder of Wireless-Nets, Ltd., a consulting firm assisting municipalities, enterprises, hospitals, airports, and equipment providers with the development and deployment of wireless networks. Jim is the author of several books, including Deploying Voice over Wireless LANs (Cisco Press), Wireless LANs (SAMS), Wireless Networks – First Step (Cisco Press), Wireless Networking Handbook (Macmillan), and Network Reengineering (McGraw-Hill).

Read more at: http://feeds.feedburner.com/~r/muniwireless/~3/63206008/1522.