<?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: Emergency Radios That Still Don&#8217;t Communicate With Each Other 9 Years Later &amp; The Danger To Government Credibility With The Public</title>
	<atom:link href="http://incaseofemergencyblog.com/2010/09/20/emergency-radios-that-still-dont-communicate-with-each-other-9-years-later-the-danger-to-government-credibility-with-the-public/feed/" rel="self" type="application/rss+xml" />
	<link>http://incaseofemergencyblog.com/2010/09/20/emergency-radios-that-still-dont-communicate-with-each-other-9-years-later-the-danger-to-government-credibility-with-the-public/</link>
	<description>A Citizenâ€™s Eye View of Public Preparedness</description>
	<lastBuildDate>Mon, 16 Feb 2026 13:57:48 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gary Oldham</title>
		<link>http://incaseofemergencyblog.com/2010/09/20/emergency-radios-that-still-dont-communicate-with-each-other-9-years-later-the-danger-to-government-credibility-with-the-public/comment-page-1/#comment-81593</link>
		<dc:creator>Gary Oldham</dc:creator>
		<pubDate>Wed, 22 Sep 2010 16:44:40 +0000</pubDate>
		<guid isPermaLink="false">http://incaseofemergencyblog.com/?p=12805#comment-81593</guid>
		<description>Technology really has never been the issue. It&#039;s much more of a sandbox issue than anything else. There was - and is - nothing more interoperable than a pair of VHF or UHF radios on the same frequency. Doesn&#039;t matter who makes them, what feature sets they have, etc. In that scenario, though, spectrum limitations have been the issue.

P25 is touted as an interoperability standard. It&#039;s really a technical standard that doesn&#039;t preclude interoperability. What it does do is make more efficient usage of the limited RF spectrum.

I&#039;ve been dealing with interoperability issues since the late 70s when I first became a part of Project FIRESCOPE. We&#039;re still dealing with the same primary challenges in the interoperability area - human factors. Until everybody embraces ICS and NIMS and actually follows it (instead of simple lip service, saying &quot;we&#039;ll use it when the big one hits&quot;, continuing to use radio codes instead of clear text, etc., we&#039;ll never achieve interoperability. Instead, we&#039;ll continue to demonstrate that interoperability isn&#039;t nearly as important as continuing to do business the way we always have, despite an overwhelming preponderance of evidence proving that there IS a better way. I have several posts on this topic on my blog at www.wingineering.com. 

This is a huge issue, and the public safety community must face up to it, genuinely adopt all the tenets and practices of ICS and clear text, and understand the genuine greater good for ourselves and others that come from it. 

Technology or the lack thereof is not now and has never truly been the impediment to interoperability.</description>
		<content:encoded><![CDATA[<p>Technology really has never been the issue. It&#8217;s much more of a sandbox issue than anything else. There was &#8211; and is &#8211; nothing more interoperable than a pair of VHF or UHF radios on the same frequency. Doesn&#8217;t matter who makes them, what feature sets they have, etc. In that scenario, though, spectrum limitations have been the issue.</p>
<p>P25 is touted as an interoperability standard. It&#8217;s really a technical standard that doesn&#8217;t preclude interoperability. What it does do is make more efficient usage of the limited RF spectrum.</p>
<p>I&#8217;ve been dealing with interoperability issues since the late 70s when I first became a part of Project FIRESCOPE. We&#8217;re still dealing with the same primary challenges in the interoperability area &#8211; human factors. Until everybody embraces ICS and NIMS and actually follows it (instead of simple lip service, saying &#8220;we&#8217;ll use it when the big one hits&#8221;, continuing to use radio codes instead of clear text, etc., we&#8217;ll never achieve interoperability. Instead, we&#8217;ll continue to demonstrate that interoperability isn&#8217;t nearly as important as continuing to do business the way we always have, despite an overwhelming preponderance of evidence proving that there IS a better way. I have several posts on this topic on my blog at <a href="http://www.wingineering.com" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://www.wingineering.com');" rel="nofollow">http://www.wingineering.com</a>. </p>
<p>This is a huge issue, and the public safety community must face up to it, genuinely adopt all the tenets and practices of ICS and clear text, and understand the genuine greater good for ourselves and others that come from it. </p>
<p>Technology or the lack thereof is not now and has never truly been the impediment to interoperability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Wild</title>
		<link>http://incaseofemergencyblog.com/2010/09/20/emergency-radios-that-still-dont-communicate-with-each-other-9-years-later-the-danger-to-government-credibility-with-the-public/comment-page-1/#comment-81452</link>
		<dc:creator>David Wild</dc:creator>
		<pubDate>Tue, 21 Sep 2010 15:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://incaseofemergencyblog.com/?p=12805#comment-81452</guid>
		<description>There is an interesting Urgent Communications article in the current issue (http://urgentcomm.com/networks_and_systems/mag/disaster-communications-setup-201009/) about the gargantuan efforts needed to get communications working currently in a disaster area. It shouldn&#039;t be this hard. The NPSPAC national interoperability frequencies (maybe along with the NIFOG guide) were probably the most useful (and least expensive) of all the efforts, along with ad-hoc interoperability measures like bridges, but the pace have change has been so slow (and is in some ways now even worse - instead of vhf/uhf we now have to deal with vhf/uhf/700/800/p25/analog/wide/narrow</description>
		<content:encoded><![CDATA[<p>There is an interesting Urgent Communications article in the current issue (<a href="http://urgentcomm.com/networks_and_systems/mag/disaster-communications-setup-201009/" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://urgentcomm.com/networks_and_systems/mag/disaster-communications-setup-201009/');" rel="nofollow">http://urgentcomm.com/networks_and_systems/mag/disaster-communications-setup-201009/</a>) about the gargantuan efforts needed to get communications working currently in a disaster area. It shouldn&#8217;t be this hard. The NPSPAC national interoperability frequencies (maybe along with the NIFOG guide) were probably the most useful (and least expensive) of all the efforts, along with ad-hoc interoperability measures like bridges, but the pace have change has been so slow (and is in some ways now even worse &#8211; instead of vhf/uhf we now have to deal with vhf/uhf/700/800/p25/analog/wide/narrow</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott McPherson</title>
		<link>http://incaseofemergencyblog.com/2010/09/20/emergency-radios-that-still-dont-communicate-with-each-other-9-years-later-the-danger-to-government-credibility-with-the-public/comment-page-1/#comment-81448</link>
		<dc:creator>Scott McPherson</dc:creator>
		<pubDate>Tue, 21 Sep 2010 13:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://incaseofemergencyblog.com/?p=12805#comment-81448</guid>
		<description>Put this at or near the top of the (many) failures of DHS.  This is a national shame.</description>
		<content:encoded><![CDATA[<p>Put this at or near the top of the (many) failures of DHS.  This is a national shame.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
