April 27, 2009 By Andy Opsahl
Given the implosion of the national municipal Wi-Fi craze, what should local governments that are still seeking some form of municipal broadband do next? The good news is they don't have to start from scratch. Not all the municipal-broadband efforts of the past few years failed:
Where many highly publicized wireless failures -- like those in Philadelphia and San Francisco -- went wrong was relying on vendors' promises to build free networks in exchange for Wi-Fi transmitter space on city streetlights, towers and other assets. Vendors hoped the networks would create a bonanza of consumer broadband subscriptions that would pay for the installation costs.
Industry wisdom appears to have boiled down to this: Cities can't treat municipal-broadband networks like trendy clothes. As peer pressure to install municipal Wi-Fi networks grew, cities became convinced they needed municipal Wi-Fi to be "cutting edge."
Instead, successful municipal wireless networks fulfill specific community needs. Municipal broadband hasn't worked for every city, but for the ones in which it does, the advantages can be transformational.
Given the failures of municipal networks aimed at providing commercial services, like in-home broadband subscriptions, one might assume government shouldn't try offering them. However, city and county networks that sell commercial broadband can work in areas that vendors won't serve. For example, Bristol, Va., recently became the only U.S. city named in the New York-based Intelligent Community Forum's Top Seven Intelligent Communities of 2009, in recognition of the city's municipal-broadband network. Bristol Virginia Utilities (BVU), a public utility, runs the fiber-based network, which provides telephone, cable television and broadband services to 65 percent of the city. The fiber powers free Wi-Fi at the local mall and government buildings. Many citizens also use the network for Wi-Fi in their homes, said Wes Rosenbalm, president and CEO of the BVU.
Photo: Bristol, Va., has an advanced fiber-to-the-home network that provides free Wi-Fi access to residents and has lured businesses to the area.
"For various reasons, 35 percent of the population does not have our services. In some cases, that's because it's an apartment building that we're not allowed into -- things of that nature. A fiber-optic overbuild of 65 percent penetration is impressive. They usually run in the 30 to 35 percent range," Rosenbalm said. In addition, all commercial buildings in Bristol can access the network.
The utility funded the network with bonds and federal grant money. The project cost $21 million. Rosenbalm expects the network to pay for itself in 12 to 15 years. One could argue the investment has already paid off because the network enticed technology companies Northrop Grumman and CGI to open business there. "They brought 700 jobs that paid an average salary of $50,000," Rosenbalm said. "Our average salary is somewhere in the neighborhood of $20,000."
Bristol's network succeeded where many municipal-broadband projects failed because the city was responding to a genuine need rather than desire for a novelty, Rosenbalm said. Bristol couldn't get a major vendor to build
You may use or reference this story with attribution and a link to
http://www.govtech.com/pcio/Municipal-Broadband-Efforts-Succeed-Despite-Wi-Fi.html
A key point to keep in mind is that most of the "muni" failures were not muni at all, but rather failures of private companies offering services within a city. In truth, most of these builds were/are no more "MuniWifi" than the services offered by Comcast are part of a "MuniCable" system. Simply put, we need a better terminology for WiFi services offered by a private sector company within a locale. MuniWifi is not it.
A key point to keep in mind is that most of the "muni" failures were not muni at all, but rather failures of private companies offering services within a city. In truth, most of these builds were/are no more "MuniWifi" than the services offered by Comcast are part of a "MuniCable" system. Simply put, we need a better terminology for WiFi services offered by a private sector company within a locale. MuniWifi is not it.
A key point to keep in mind is that most of the "muni" failures were not muni at all, but rather failures of private companies offering services within a city. In truth, most of these builds were/are no more "MuniWifi" than the services offered by Comcast are part of a "MuniCable" system. Simply put, we need a better terminology for WiFi services offered by a private sector company within a locale. MuniWifi is not it.
A key point to keep in mind is that most of the "muni" failures were not muni at all, but rather failures of private companies offering services within a city. In truth, most of these builds were/are no more "MuniWifi" than the services offered by Comcast are part of a "MuniCable" system. Simply put, we need a better terminology for WiFi services offered by a private sector company within a locale. MuniWifi is not it.
I agree with Peter. The failure was the cost of deployment, the expectations, and the lack of a realistic business plan. Our company has been redesigning that for the last few years and are now deploying systems that cost 1/10 or less than the cost of the older systems while providing up to 4 times the bandwidth or more. Hopefully others are now deploying similiar designs.
I agree with Peter. The failure was the cost of deployment, the expectations, and the lack of a realistic business plan. Our company has been redesigning that for the last few years and are now deploying systems that cost 1/10 or less than the cost of the older systems while providing up to 4 times the bandwidth or more. Hopefully others are now deploying similiar designs.
I agree with Peter. The failure was the cost of deployment, the expectations, and the lack of a realistic business plan. Our company has been redesigning that for the last few years and are now deploying systems that cost 1/10 or less than the cost of the older systems while providing up to 4 times the bandwidth or more. Hopefully others are now deploying similiar designs.
I agree with Peter. The failure was the cost of deployment, the expectations, and the lack of a realistic business plan. Our company has been redesigning that for the last few years and are now deploying systems that cost 1/10 or less than the cost of the older systems while providing up to 4 times the bandwidth or more. Hopefully others are now deploying similiar designs.