<?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: Guest commentary: Philadelphia network flop points to failure of corporate franchise model</title>
	<atom:link href="http://www.muniwireless.com/2008/05/16/philadelphia-network-points-to-failure-of-corporate-franchise-model/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.muniwireless.com/2008/05/16/philadelphia-network-points-to-failure-of-corporate-franchise-model/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=philadelphia-network-points-to-failure-of-corporate-franchise-model</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: JAMES CARLINI</title>
		<link>http://www.muniwireless.com/2008/05/16/philadelphia-network-points-to-failure-of-corporate-franchise-model/#comment-34035</link>
		<dc:creator>JAMES CARLINI</dc:creator>
		<pubDate>Thu, 29 May 2008 19:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.muniwireless.com/?p=7753#comment-34035</guid>
		<description>RORY HITS THE NAIL ON THE HEAD

Let&#039;s get right to it - you need REAL engineering and infrastructure consultants, not self-proclaimed experts that think they know what they are doing - when they don&#039;t.

If you really knew network engineering - all of it, not just wireless, you would understand that WiFi might not be the right choice to cover a large metropolitan area.

As I said in one of my articles - just because you built a Lionel railroad in your basement doesn&#039;t mean that you can now become the Chief Infratructure Engineer for the Burlington Northern.  The same applies to network infrastructure.  A couple of successful WIFi implementations in some coffee shops do not translate  into undetstanding network topographies for major metropolitan areas.  Read and learn:

http://carliniscomments.com/archives/146-WIFI,-WIMAX-EVOLUTION.html

http://carliniscomments.com/archives/131-WIFI-is-NOT-THE-UNIVERSAL-SOLUTION.html

James Carlini</description>
		<content:encoded><![CDATA[<p>RORY HITS THE NAIL ON THE HEAD</p>
<p>Let&#8217;s get right to it &#8211; you need REAL engineering and infrastructure consultants, not self-proclaimed experts that think they know what they are doing &#8211; when they don&#8217;t.</p>
<p>If you really knew network engineering &#8211; all of it, not just wireless, you would understand that WiFi might not be the right choice to cover a large metropolitan area.</p>
<p>As I said in one of my articles &#8211; just because you built a Lionel railroad in your basement doesn&#8217;t mean that you can now become the Chief Infratructure Engineer for the Burlington Northern.  The same applies to network infrastructure.  A couple of successful WIFi implementations in some coffee shops do not translate  into undetstanding network topographies for major metropolitan areas.  Read and learn:</p>
<p><a href="http://carliniscomments.com/archives/146-WIFI,-WIMAX-EVOLUTION.html" rel="nofollow">http://carliniscomments.com/archives/146-WIFI,-WIMAX-EVOLUTION.html</a></p>
<p><a href="http://carliniscomments.com/archives/131-WIFI-is-NOT-THE-UNIVERSAL-SOLUTION.html" rel="nofollow">http://carliniscomments.com/archives/131-WIFI-is-NOT-THE-UNIVERSAL-SOLUTION.html</a></p>
<p>James Carlini</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rory Conaway</title>
		<link>http://www.muniwireless.com/2008/05/16/philadelphia-network-points-to-failure-of-corporate-franchise-model/#comment-34011</link>
		<dc:creator>Rory Conaway</dc:creator>
		<pubDate>Sun, 25 May 2008 17:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.muniwireless.com/?p=7753#comment-34011</guid>
		<description>All of the municipal Wi-Fi systems failed because there was no real RF analysis done and no statement of work.  Expectations were never defined.  Therefore any financial model based on that technical information was never going to be accurate.  Throw in a failure of marketing to know how to really use the network and it just gets worse.

1) Let&#039;s start with the idea that everybody needs ubiquitous coverage through their house.  That was never going to happen regardless of what the radio manufacturers said. Make the expectations more realistic.  We solved that problem 5 years ago and will now be releasing it into the cities we worked with.

2) Move forward to the concept that you need a $1200-$5000 access point with mesh.  The reality is that most of the radios used $150 modules from Ubiquiti with mesh software.  There were many variations but that was the reality.  It&#039;s now 5 years later and equipment that is far less expensive is now available using the same modules.  That alone drops the capex by a factor of 3 or more.

3) We need mesh.  Wrong.  You could use mesh or WDS and saw no difference in performance.  That fact it was mesh just added to the cost.  How about just monitoring your network and dynamically making changes to support additional bandwidth or equipment failure.  

4) You need multiple radios per access point.  Sure, if you had high bandwidth needs.  However, what about just adding additional backhaul in areas of high congestion and reducing the hops as, and here is the financial kick in the pants, &quot;your revenue in an area increases to cover the Capex cost!&quot;.  Profitability, what a concept!

5) Mesh redistibutes paths based on load making it more efficient.  B.S.!  Not every mesh manufacturer implemented that feature and the reality is, who cares.  Go back to my previous statement.

6) Make the access points multi-radio and multi-frequency to increase efficiency.  Here&#039;s my point to that.  Another stupid idea.  Drives up costs of equipment that doesn&#039;t get evenly distributed across the applications it&#039;s being used for financially.

Most of these are common sense that should be applied to any radio deployment.  However, they were apparently missed when Earthlink, Metrofi, MobilePro, and others were blowing through tens of millions of dollars of their investors money.  Next time hire real RF engineers instead of network engineer lackey&#039;s who think they have some clue about RF trained by the very corporations trying to sell you equipment.  An RF engineer could have told you that your expectations of performance were never realistic.  And if anybody listens to these consultants like Jonathan Balco and Civitium who never installed an AP in their life, you get what you deserve.</description>
		<content:encoded><![CDATA[<p>All of the municipal Wi-Fi systems failed because there was no real RF analysis done and no statement of work.  Expectations were never defined.  Therefore any financial model based on that technical information was never going to be accurate.  Throw in a failure of marketing to know how to really use the network and it just gets worse.</p>
<p>1) Let&#8217;s start with the idea that everybody needs ubiquitous coverage through their house.  That was never going to happen regardless of what the radio manufacturers said. Make the expectations more realistic.  We solved that problem 5 years ago and will now be releasing it into the cities we worked with.</p>
<p>2) Move forward to the concept that you need a $1200-$5000 access point with mesh.  The reality is that most of the radios used $150 modules from Ubiquiti with mesh software.  There were many variations but that was the reality.  It&#8217;s now 5 years later and equipment that is far less expensive is now available using the same modules.  That alone drops the capex by a factor of 3 or more.</p>
<p>3) We need mesh.  Wrong.  You could use mesh or WDS and saw no difference in performance.  That fact it was mesh just added to the cost.  How about just monitoring your network and dynamically making changes to support additional bandwidth or equipment failure.  </p>
<p>4) You need multiple radios per access point.  Sure, if you had high bandwidth needs.  However, what about just adding additional backhaul in areas of high congestion and reducing the hops as, and here is the financial kick in the pants, &#8220;your revenue in an area increases to cover the Capex cost!&#8221;.  Profitability, what a concept!</p>
<p>5) Mesh redistibutes paths based on load making it more efficient.  B.S.!  Not every mesh manufacturer implemented that feature and the reality is, who cares.  Go back to my previous statement.</p>
<p>6) Make the access points multi-radio and multi-frequency to increase efficiency.  Here&#8217;s my point to that.  Another stupid idea.  Drives up costs of equipment that doesn&#8217;t get evenly distributed across the applications it&#8217;s being used for financially.</p>
<p>Most of these are common sense that should be applied to any radio deployment.  However, they were apparently missed when Earthlink, Metrofi, MobilePro, and others were blowing through tens of millions of dollars of their investors money.  Next time hire real RF engineers instead of network engineer lackey&#8217;s who think they have some clue about RF trained by the very corporations trying to sell you equipment.  An RF engineer could have told you that your expectations of performance were never realistic.  And if anybody listens to these consultants like Jonathan Balco and Civitium who never installed an AP in their life, you get what you deserve.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

