<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Generation of Low-Cost Municipal Networks</title>
	<atom:link href="http://www.muniwireless.com/2010/03/18/new-generation-of-low-cost-municipal-networks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.muniwireless.com/2010/03/18/new-generation-of-low-cost-municipal-networks/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-generation-of-low-cost-municipal-networks</link>
	<description>Citywide WiFi, smart grid, enterprise wireless, public safety, mobile apps</description>
	<lastBuildDate>Sun, 12 Feb 2012 01:38:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Marshall Brown</title>
		<link>http://www.muniwireless.com/2010/03/18/new-generation-of-low-cost-municipal-networks/#comment-40902</link>
		<dc:creator>Marshall Brown</dc:creator>
		<pubDate>Fri, 09 Apr 2010 09:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.muniwireless.com/?p=12800#comment-40902</guid>
		<description>Dear Rory,


You and I understand municipal Wi-Fi differently.  I still want it to be &#039;all things to all people,&#039; meaning that the goal should be the creation of a single infrastructure over which all uses, public and private, for a &#039;community intranet&#039; would be supported.  

True, it is easier said than done.  But there are economies of scale with building a single infrastructure to deliver education, health, and civic information, public safety, electrical monitoring.   I think both Larry Karisny, and Craig Settles, recently with columns here would agree with me on this -- the municipal network is a local infrastructure of dumb pipes over which any type of service can run, with smart devices on the edge (that leverage cloud computing).

Mesh has its limitations.  It cannot support multimedia -- VOIP, Video -- very well.  A muni-mesh network should not have public traffic on it.  But mesh is well suited, as you know, to public safety because it offers an inexpensive footprint, is redundant, self-healing. 

I use a point-to-multipoint solution using the gear of a company called Altai Technologies.  With the Altais I can serve out a lot of video to a lot of simultaneous users.  This is what people want in their public spaces.   At the same time, the network can also support the kinds of municipal services you mention, with the Altai supporting mesh segments, providing them with backhaul.

Since you have elected a mesh system, that means that you as you note be mounting on light poles.  That can be extremely costly.  In NYC,the light poles are leased to you for $500 a month in prime areas by one of six franchise holders.  If you happen to select a light pole that is somehow defective -- in backhaul or in terms of power -- you have to assume the cost of repairing that lightpole, which after permits, the bucket truck, closing off the street for a time, can run you $70,000.   

An extreme example, but my point is that if you can at all avoid having to install in multiple sites, do so.  With mesh, unfortunately, you need to.  Point to Multipoint -- central wireless hubs on key community buildings feeding small repeaters sitting in a window a mile or more away.  You can even bill by each of four SSIDs on the repeater.

As for charging for the service, even something nominal, the watch out here would be that as soon as you start charging for something, you must assume customer service and support costs.  If you just charge $5 a month, you may lose money.

If the only choice is mesh, then we need to pare back how we define municipal wireless.  If its not, then a single infrastructure can support all IP based services in a community.</description>
		<content:encoded><![CDATA[<p>Dear Rory,</p>
<p>You and I understand municipal Wi-Fi differently.  I still want it to be &#8216;all things to all people,&#8217; meaning that the goal should be the creation of a single infrastructure over which all uses, public and private, for a &#8216;community intranet&#8217; would be supported.  </p>
<p>True, it is easier said than done.  But there are economies of scale with building a single infrastructure to deliver education, health, and civic information, public safety, electrical monitoring.   I think both Larry Karisny, and Craig Settles, recently with columns here would agree with me on this &#8212; the municipal network is a local infrastructure of dumb pipes over which any type of service can run, with smart devices on the edge (that leverage cloud computing).</p>
<p>Mesh has its limitations.  It cannot support multimedia &#8212; VOIP, Video &#8212; very well.  A muni-mesh network should not have public traffic on it.  But mesh is well suited, as you know, to public safety because it offers an inexpensive footprint, is redundant, self-healing. </p>
<p>I use a point-to-multipoint solution using the gear of a company called Altai Technologies.  With the Altais I can serve out a lot of video to a lot of simultaneous users.  This is what people want in their public spaces.   At the same time, the network can also support the kinds of municipal services you mention, with the Altai supporting mesh segments, providing them with backhaul.</p>
<p>Since you have elected a mesh system, that means that you as you note be mounting on light poles.  That can be extremely costly.  In NYC,the light poles are leased to you for $500 a month in prime areas by one of six franchise holders.  If you happen to select a light pole that is somehow defective &#8212; in backhaul or in terms of power &#8212; you have to assume the cost of repairing that lightpole, which after permits, the bucket truck, closing off the street for a time, can run you $70,000.   </p>
<p>An extreme example, but my point is that if you can at all avoid having to install in multiple sites, do so.  With mesh, unfortunately, you need to.  Point to Multipoint &#8212; central wireless hubs on key community buildings feeding small repeaters sitting in a window a mile or more away.  You can even bill by each of four SSIDs on the repeater.</p>
<p>As for charging for the service, even something nominal, the watch out here would be that as soon as you start charging for something, you must assume customer service and support costs.  If you just charge $5 a month, you may lose money.</p>
<p>If the only choice is mesh, then we need to pare back how we define municipal wireless.  If its not, then a single infrastructure can support all IP based services in a community.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

