<?xml version="1.0"?>
<!-- RSS generated by Radio UserLand v8.2.1 on Tue, 12 Sep 2006 05:40:23 GMT -->
<rss version="2.0">
	<channel>
		<title>Doug Chandler&apos;s Wireless Weblog</title>
		<link>http://radio.weblogs.com/0112720/</link>
		<description>Novice blogger; Guru Radio Dude.</description>
		<language>en-us</language>
		<copyright>Copyright 2006 Doug Chandler</copyright>
		<lastBuildDate>Tue, 12 Sep 2006 05:40:23 GMT</lastBuildDate>
		<docs>http://backend.userland.com/rss</docs>
		<generator>Radio UserLand v8.2.1</generator>
		<managingEditor>dchandler@utah.gov</managingEditor>
		<webMaster>dchandler@utah.gov</webMaster>
		<category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category> 
		<cloud domain="radio.xmlstoragesystem.com" port="80" path="/RPC2" registerProcedure="xmlStorageSystem.rssPleaseNotify" protocol="xml-rpc"/>
		<ttl>60</ttl>
		<item>
			<description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT face=Verdana,Geneva,Arial,Helvetica,Sans-Serif color=darkblue size=5&gt;TIC Plan Exercise&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Verdana,Geneva,Arial,Helvetica,Sans-Serif&gt;On August 24, 2006, the State of Utah fulfilled it&apos;s requirement to exercise it&apos;s Tactical Interoperable Communication Plan (TIC-Plan).&amp;nbsp;&amp;nbsp;Homeland Security has&amp;nbsp;pre-defined a number of cities as &quot;Urban&amp;nbsp;Areas&quot;.&amp;nbsp;&amp;nbsp;In order to&amp;nbsp;continue&amp;nbsp;eligibility for Homeland&amp;nbsp;Security grant funding for 2006, each&amp;nbsp;state&amp;nbsp;with one of these Urban Areas was required to write a TIC Plan.&amp;nbsp; Any state without a&amp;nbsp;pre-defined &apos;Urban Area&apos; was to identify their&amp;nbsp;own.&amp;nbsp; Utah selected Salt Lake County.&amp;nbsp; After making the May 2006 deadline, we were informed that in order to be eligible for 2007 funding, we were required to complete a Full Scale Exercise of the TIC Plan.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Verdana&gt;The exercise was highly successful for many reasons, but the most contributing factor has been the support and participation of people who care about public safety communication.&amp;nbsp; I was priviledged to attend a conference in Washington this last May where Secretary Chertoff was the keynote speaker.&amp;nbsp; Chertoff pointed out something that I think those of us in the industry are quick to forget.&amp;nbsp; Interoperability is about people, not technology. I think we too often lose focus on the ultimate goal of communication when we turn solely to technology and the vendors that peddle it to solve our problems.&lt;/FONT&gt;&lt;/P&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2006/09/11.html#a20</guid>
			<pubDate>Tue, 12 Sep 2006 05:34:24 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=20&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2006%2F09%2F11.html%23a20</comments>
			</item>
		<item>
			<description>&lt;P&gt;&lt;B style=&quot;mso-bidi-font-weight: normal&quot;&gt;&lt;FONT color=darkblue&gt;&lt;FONT size=5&gt;Establishing a New Communications Site&lt;?xml:namespace prefix = o ns = &quot;urn:schemas-microsoft-com:office:office&quot; /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/B&gt;&lt;/P&gt;
&lt;P&gt;Last July, several local, state, and federal agencies met with the Forest Service to discuss a proposal to establish a new communications facility in &lt;?xml:namespace prefix = st1 ns = &quot;urn:schemas-microsoft-com:office:smarttags&quot; /&gt;&lt;st1:place w:st=&quot;on&quot;&gt;&lt;st1:PlaceName w:st=&quot;on&quot;&gt;Kane&lt;/st1:PlaceName&gt; &lt;st1:PlaceType w:st=&quot;on&quot;&gt;County&lt;/st1:PlaceType&gt;&lt;/st1:place&gt;.&amp;nbsp; The proposed site would be located on Forest Service property, in the vicinity of both &lt;st1:PlaceName w:st=&quot;on&quot;&gt;Bryce&lt;/st1:PlaceName&gt; &lt;st1:PlaceName w:st=&quot;on&quot;&gt;Canyon&lt;/st1:PlaceName&gt; &lt;st1:PlaceType w:st=&quot;on&quot;&gt;National Park&lt;/st1:PlaceType&gt;, and the &lt;st1:place w:st=&quot;on&quot;&gt;&lt;st1:PlaceName w:st=&quot;on&quot;&gt;Grand&lt;/st1:PlaceName&gt; &lt;st1:PlaceName w:st=&quot;on&quot;&gt;Staircase&lt;/st1:PlaceName&gt; &lt;st1:PlaceType w:st=&quot;on&quot;&gt;National Monument&lt;/st1:PlaceType&gt;&lt;/st1:place&gt;.&amp;nbsp; We finally received&amp;nbsp;a contract from the Forest Service&amp;nbsp;in&amp;nbsp;December.&amp;nbsp;The document required $15,000 to cover the Environmental Assessment (EA).&amp;nbsp; We quickly identified the funding and notified the Forest Service to move ahead as soon as possible.&amp;nbsp; We were then notified that the cost would &lt;EM&gt;really&lt;/EM&gt; be $30,000, and we would have to do our own visual assessments and 2&apos; topographic map layout.&amp;nbsp; &lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P&gt;I recognize that communication sites are not necessarily a beautiful addition to the natural vista of the forest (unless you&apos;re a wireless geek like me), but it also strikes me as unethical to allow public access to hike and explore in these remote areas, while simultaneously ensuring that emergency public safety communications cannot occur when someone gets hurt or lost.&amp;nbsp; We can (and do) take steps to ensure&amp;nbsp;the impact is as minimal as possible when we establish communication sites, but some level of impact must be made.&amp;nbsp; Sites must be high and as unobstructed as possible to provide useable coverage.&amp;nbsp; &lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P&gt;In this case, the Forest Service seems to be doing everything it can to stop the proposed site from happening, rather than looking at all options and weighing the alternatives.&amp;nbsp; Most of the 100+ communications sites that exist around this state are on Forest Service or BLM property.&amp;nbsp; I&apos;ve never been involved with a more negative response to a proposed request than this one.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;It will be interesting to see how much higher the price creeps as we move forward.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2006/01/10.html#a19</guid>
			<pubDate>Tue, 10 Jan 2006 18:58:43 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=19&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2006%2F01%2F10.html%23a19</comments>
			</item>
		<item>
			<description>&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;FCC Chairman &lt;A href=&quot;http://www.fcc.gov/commissioners/powell/&quot;&gt;Michael K. Powell&lt;/A&gt; &lt;A href=&quot;http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-256206A1.doc&quot;&gt;resigned&lt;/A&gt; today. He was definitely the most active FCC chairman that I&apos;ve seen in my brief 20 years of radio experience. &lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;?xml:namespace prefix = o ns = &quot;urn:schemas-microsoft-com:office:office&quot; /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;In the &lt;A href=&quot;http://uwin.utah.gov/techcommittee/techcommittee.html&quot;&gt;UWIN Technology Steering Committee&lt;/A&gt; meeting today, it became apparent to me that we frequently spend our time arguing over technologies (trunking vs conventional)&amp;nbsp;and frequencies&amp;nbsp;(150 MHz vs 700 MHz vs 800 MHz), when we should be concentrating on funding.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;In 1993, Governor Leavitt formed a task force to address public safety radio interoperability issues in Utah. It was determined that all public safety agencies should move to a single frequency spectrum, and that spectrum should be 800MHz.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;The &lt;A href=&quot;http://www.ucan800.org/&quot;&gt;Utah Communications Agency Network (UCAN)&lt;/A&gt; was formed by the legislature in 1997 to make this happen. &lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;More than a decade later, we have not only failed to migrate to a single frequency spectrum, but in rolling out a new 800MHz system we effectively added yet another layer of insulation from statewide interoperability. Everyone is arguing about which spectrum is &amp;#145;superior&amp;#146; by way of coverage, available technologies, limitations, costs and so on.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;But I am convinced that the fly in the ointment is the funding mechanism.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;The UCAN network relies almost exclusively on user fees.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;The various VHF systems in the state are funded either by the Department of Public Safety, user fees, or individual cities and counties.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;There will be no movement towards a single spectrum until the central infrastructure is funded by a single source.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;South Dakota, Wyoming, Montana, Virginia, and other states have successfully rolled out statewide networks after receiving funding that is overseen by their state legislatures.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;Even federal grant monies require state oversight for successful deployment across county boundaries.&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2005/01/21.html#a18</guid>
			<pubDate>Sat, 22 Jan 2005 05:09:59 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=18&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2005%2F01%2F21.html%23a18</comments>
			</item>
		<item>
			<description>&lt;P&gt;&lt;FONT color=darkblue&gt;&lt;FONT size=5&gt;Floods and Blizzards Make Wireless Challenging&lt;/FONT&gt;&lt;BR&gt;&lt;/FONT&gt;This last week has seen a great deal of turmoil for Utah&apos;s public safety communications&amp;nbsp;&lt;BR&gt;infrastructure.&amp;nbsp; While floods were keeping &lt;A href=&quot;http://www.washco.state.ut.us/&quot;&gt;Washington County&lt;/A&gt; busy, four of their five mountaintop communications sites went down due to heavy snowfall. &lt;A href=&quot;http://www.utah.gov/governor/&quot;&gt;Governor Huntsman&apos;s&lt;/A&gt; first &lt;A href=&quot;http://execdocnews.utah.gov/archives/000515.html&quot;&gt;Executive Order&lt;/A&gt; was to declare Washington County a disaster area.&amp;nbsp;&amp;nbsp;Working through &lt;A href=&quot;http://publicsafety.utah.gov/&quot;&gt;DPS&lt;/A&gt;, State &lt;A href=&quot;http://its.utah.gov/productsservices/radioshop/index.html&quot;&gt;ITS Wireless Services Group&lt;/A&gt; assisted Washington County with the restoration of their communications sites.&lt;/P&gt;
&lt;P&gt;The heavy snowfalls took out power lines to five state communications sites. These sites are located all over the state, so the storm was not limited to a small geographic region. The Logan Peak outage was by far the most critical because the back-up generator failed to run.&amp;nbsp; With the exception of Logan Peak, I was proud of the fact that while neighboring communications facilities were dropping like flies all over the state, the ITS facilities were operating.&amp;nbsp; This is due to the high-standards that our technicians&amp;nbsp;maintain our sites to.&amp;nbsp; We loosely follow &lt;A href=&quot;http://www.motorola-wls.com/Dynamic/Course_Description.asp?number=ANT001-CD&amp;amp;CourseKey=125&quot;&gt;Motorola&apos;s R-56 Site Standards&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;The next problem is refueling the generators that have been running for the last week to ten days.&amp;nbsp; Our local helicopter vendor is not authorized to long-line propane, so we are requesting the assistance of the &lt;A href=&quot;http://www.globalsecurity.org/military/agency/army/arng-ut.htm&quot;&gt;Utah National Guard&lt;/A&gt;.&amp;nbsp; Last year they came to our rescue, and we need them again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2005/01/16.html#a17</guid>
			<pubDate>Mon, 17 Jan 2005 05:54:43 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=17&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2005%2F01%2F16.html%23a17</comments>
			</item>
		<item>
			<description>&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&lt;STRONG&gt;&lt;FONT color=darkblue size=5&gt;Navajo Nation I.T. Meeting&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;I met with several I.T. representatives of the &lt;A href=&quot;http://www.navajo.org/&quot;&gt;Navajo Nation&lt;/A&gt; earlier today.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;They are attempting to consolidate interest, cooperation and funding for several I.T. projects in support of I.T. infrastructures within the Nation.&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;?xml:namespace prefix = o ns = &quot;urn:schemas-microsoft-com:office:office&quot; /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;They know what their needs are, but more importantly, they have a clear understanding of what their limitations are.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;Today, I.T. is primarily available to more than 200,000 Navajo citizens a 110 &lt;A href=&quot;http://www.nndcd.org/chapters.html&quot;&gt;Chapter Houses&lt;/A&gt; where &lt;A href=&quot;http://www.onsatnet.com/&quot;&gt;On-Sat&lt;/A&gt; satellite service provides connectivity to the Internet, Email etc.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;The Nation no longer wishes to be dependant on vendors, but wants to act as their own I.S.P., to include backbone infrastructure such as microwave, fiber, etc. &lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;They have initiated a six-step solution that will result in a comprehensive RFP, which will address their IT needs.&lt;SPAN style=&quot;mso-spacerun: yes&quot;&gt;&amp;nbsp; &lt;/SPAN&gt;The first step, identification of existing networks and needs, has already been delivered via a proposal from &lt;A href=&quot;http://www.optegra.net/&quot;&gt;Optegra Networks Solutions Inc.&lt;/A&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;&lt;SPAN style=&quot;FONT-SIZE: 12pt; FONT-FAMILY: &apos;Times New Roman&apos;; mso-fareast-font-family: &apos;Times New Roman&apos;; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA&quot;&gt;The State of Utah continues to work closely with the Navajo Nation to find common, interoperable solutions. Several action items have been developed, including co-developing a communications site at &lt;A href=&quot;http://navajomountain.nndes.org/&quot;&gt;Navajo Mountain&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2005/01/04.html#a16</guid>
			<pubDate>Tue, 04 Jan 2005 20:00:01 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=16&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2005%2F01%2F04.html%23a16</comments>
			</item>
		<item>
			<description>&lt;body bgcolor=&quot;#FFFFFF&quot;&gt;
&lt;p&gt;&lt;font color=&quot;#0000FF&quot; size=&quot;5&quot;&gt;Wireless Interoperability Solutions Are Anything 
  But... &lt;/font&gt;&lt;/p&gt;
&lt;p&gt;Every time a vendor releases another &apos;Wireless Interoperability&apos; solution, 
  we move further away from interoperability. Why? Because interoperability solutions 
  have one thing in common: they are all proprietary! (Hello?&amp;#133;McFly!) &lt;/p&gt;
&lt;p&gt;The Florida State Technology Office has just contracted with Motorola for their 
  new &lt;a href=&quot;http://www.motorola.com/mediacenter/news/detail/0,,4939_4227_23,00.html&quot;&gt;Motobridge&lt;/a&gt; 
  IP Interoperability Solution. The State of Utah is using the Motorola &lt;a href=&quot;http://www.motorola.com/LMPS/RNSG/trunking/alt.htm#omnilink&quot;&gt;Omni-Link&lt;/a&gt; 
  solution to connect dispatch centers across the state together. There are dozens 
  of solutions available from dozens of vendors. I&apos;m sure most, if not all of 
  them are great, but they are still PROPRIETARY. The list of interoperability 
  projects is almost as endless as the amounts of money poured into them. &lt;/p&gt;
&lt;p&gt;The &apos;open-standards&apos; horses left the wireless barn years ago. There will probably 
  never be another common band, using common modulation schemes, trunking protocols, 
  etc. Even VOIP solutions require proprietary hardware and software to coordinate 
  routing, traffic priority, etc. &lt;/p&gt;
&lt;p&gt;I think we&apos;ll see the next opportunity to migrate towards a more central solution 
  when &lt;a href=&quot;http://www.safecomprogram.gov/&quot;&gt;SAFECOM&lt;/a&gt; and/or &lt;a href=&quot;http://www.apcointl.org/&quot;&gt;APCO&lt;/a&gt; 
  rollout VOIP standards. They are both working on them.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;/body&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2004/12/17.html#a15</guid>
			<pubDate>Fri, 17 Dec 2004 23:08:04 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=15&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2004%2F12%2F17.html%23a15</comments>
			</item>
		<item>
			<description>&lt;p&gt;&lt;b&gt;&lt;font size=&quot;4&quot; color=&quot;#0000CC&quot;&gt;Utah&apos;s Public Safety Wireless Situation&lt;/font&gt;&lt;/b&gt;&lt;br&gt;
  (According to Doug)&lt;/p&gt;&lt;p&gt; &lt;b&gt;1. Expansion &apos;Disincentive&apos;:&lt;/b&gt;&lt;br&gt;
  The reason 800MHz expansion outside the Wasatch Front isn&apos;t happening is because 
  there is a negative incentive (is that a real term?) for rural areas to join. 
  If you are the sheriff of Wayne County and operate a $500 radio on a system 
  funded by the state (no fees), why would you want to join a system where the 
  radio now costs thousands, the fees are heading toward $25/user/month, and unless 
  more sites are developed, the coverage will decrease. There is no conspiracy 
  out there. There is a cash flow reality. It works well in the Wastach Front 
  because of the density of users which makes an obvious financial case for trunking. 
&lt;/p&gt;
&lt;p&gt;Quick analogy:&lt;br&gt;
  a. You start a business with 5 employees, so you lease 5 phone lines. &lt;br&gt;
  b. You start a business with 5,000 employees. Do you lease them each a phone 
  line, or do you issue extentions and have them share a few dozen &apos;trunked&apos; lines? 
  Rural Utah is the 5 employee business, and we are trying to sell them the 5 
  phone lines at the 5,000 line trunked cost (oh, and by the way, the new expensive 
  phone lines only work if you&apos;re standing in certain spots in your office). &lt;/p&gt;
&lt;p&gt;&lt;b&gt;2. Money Drives Technology - Not Necessarily Interoperability: &lt;/b&gt;&lt;br&gt;
  As long as rates determine who joins, Utah will never have a single public safety 
  communications system. The Wasatch Front users will never fund the lesser populations 
  by paying the higher rates necessary to build infrastructure in rural areas. 
  Period. Finito. The End. I recently spoke at the Bio-Terrorism conference in 
  South Dakota. My topic was: &quot;Communication - A Success Story&quot;. South Dakota 
  has just rolled out a statewide Narrowband VHF trunking system that has a single, 
  uniform, statewide user fee: $0.00/user/month/forever. That was not a type-o. 
  I meant &lt;i&gt;zero&lt;/i&gt;. They even used grant monies to supply 10,000 radios to 
  all state, city, and county public safety agencies. The last I heard, they were 
  going to supply 600+ radios to the federal agencies in their state. If I&apos;ve 
  peaked your interest, read CommTech&apos;s (formerly A.G.I.L.E.) case study of South 
  Dakota: &lt;a href=&quot;http://www.agileprogram.org/ntfi/case_sdakota3.html&quot;&gt;&lt;a href=&quot;http://www.agileprogram.org/ntfi/case_sdakota3.html&quot;&gt;http://www.agileprogram.org/ntfi/case_sdakota3.html&lt;/a&gt;&lt;/a&gt; 
  &lt;br&gt;
  Just who has the real success story to tell? Utah needs to regroup in a very 
  basic way and re-think funding mechanisms. If Utah wants statewide interoperability, 
  user fees must not exist (not even teeny tiny ones). This means current funding 
  (VHF, UCAN, OmniLink -all of it) needs to pushed back toward the legislature 
  where it can be added to and invested in a system that gets written up as a 
  case study in CommTech. &lt;/p&gt;
&lt;p&gt;Utah has a solid tax base, strong political leadership, and good technologists. 
  We&apos;re suffering from the lack of a single vision that everyone can get behind 
  and own. The technology and the grant money are doing more damage than good. 
  I don&apos;t care if we do it VHF, UHF, 800, 700, VOIP, or mental telepathy, but 
  let&apos;s do one plan. That plan may be a combination of technologies, but it should 
  be ONE PLAN.&lt;/p&gt;</description>
			<guid>http://radio.weblogs.com/0112720/2004/10/02.html#a14</guid>
			<pubDate>Sat, 02 Oct 2004 23:39:25 GMT</pubDate>
			<comments>http://radiocomments2.userland.com/comments?u=112720&amp;amp;p=14&amp;amp;link=http%3A%2F%2Fradio.weblogs.com%2F0112720%2F2004%2F10%2F02.html%23a14</comments>
			</item>
		</channel>
	</rss>
