<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Southeastern Asterisk Radio Networks &#187; Emergency Response</title>
	<atom:link href="http://searn.asteriskradio.net/blog/archives/category/emergency-response/feed/" rel="self" type="application/rss+xml" />
	<link>http://searn.asteriskradio.net/blog</link>
	<description></description>
	<lastBuildDate>Fri, 22 Jan 2010 13:59:30 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>711 TRS</title>
		<link>http://searn.asteriskradio.net/blog/archives/2009/05/03/711-trs/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2009/05/03/711-trs/#comments</comments>
		<pubDate>Sun, 03 May 2009 06:45:49 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/?p=99</guid>
		<description><![CDATA[Do you know what 711 TRS is?
711 is the nationwide telephone number for accessing Telephone Relay Service (TRS).    TRS permits persons with a hearing or speech disability to use the telephone system via a text telephone (TTY) or other device to call persons with or without such disabilities.

Making TRS Calls
If you want [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Do you know what 711 TRS is?</strong></p>
<p><strong>711 is the nationwide telephone number for accessing Telephone Relay Service (TRS)</strong>.    <em>TRS permits persons with a hearing or speech disability to use the telephone system via a text telephone (TTY) or other device to call persons with or without such disabilities.</em></p>
<p class="lavender">
<p class="lavender"><strong>Making TRS Calls</strong></p>
<p class="factsbody"><span id="more-99"></span><em>If you want to call someone using TRS, use your TTY, or dial 711 on your telephone, and you will automatically be connected to a TRS operator. If you’re a TRS user traveling out of state and want to make a call, there is no longer a need to learn the state’s TRS provider’s telephone number.  Just dial 711. It’s fast, functional, and free.</em></p>
<p class="factsbody"><em>The 711 code is not just for use by persons with disabilities. Both voice and TRS users can initiate a call from any telephone, anywhere in the United States, without having to remember and dial a seven or ten-digit access number. For persons who have been using TRS for years, the convenience of dialing three digits is obvious.</em></p>
<p class="factsbody"><em>711 dialing access does not work for Video Relay Service (VRS) or Internet Protocol (IP) Relay calls, because such calls are initiated through the Internet. Hearing persons initiating a VRS or IP Relay call may do so by calling a provider’s 800 number.</em></p>
<p class="factsbody">
<p class="lavender" align="left"><strong>Dialing 711 From A Private Branch Exchange</strong></p>
<p class="factsbody"><em>FCC rules require all telephone companies (including wireline, wireless, and payphone providers) that operate private branch exchanges (PBXs) to implement three-digit 711 dialing for access to TRS. A PBX is a private telephone system within an organization that switches calls between internal users and allows users to share a certain number of external phone lines. PBX operators are required to modify their equipment to enable 711 dialing to ensure that everyone benefits from abbreviated dialing and consumers have easy access to TRS.</em></p>
<p class="factsbody"><em>Callers from locations served by PBXs may be required to dial 9 or another prefix before entering the 711 code or placing an outside call. The FCC encourages PBX operators to work with telephone companies and TRS providers to facilitate 711 dialing for users.</em></p>
<p class="factsbody"><em>The FCC recently determined that providers of interconnected Voice over Internet Protocol (VoIP) service also must offer 711 abbreviated dialing.</em></p>
<p class="factsbody">
<p class="lavender"><strong>911 and 711</strong></p>
<p class="factsbody"><em>Dialing 911 is the most familiar and effective way Americans have to find help in an emergency. The Americans with Disabilities Act (ADA) requires all Public Safety Answering Points (PSAPs) to provide direct, equal access to their emergency response services for people with disabilities who use TTYs or other devices. Therefore, in the event of an emergency, TTY users should call 911 directly, and not make a TRS call via 711.</em></p>
<p class="factsbody">
<p class="factsbody"><strong>Why is 711 TRS important to us?</strong></p>
<p class="factsbody">As a communications resource we need to be ready to handle traffic that may need to be delivered to a person that may have hearing or speech.  Via 711 TRS we will be able to deliver messages in a more timely fashion when the situation arises.   We also need to let people know that the service exists.</p>
<p class="factsbody">
<p class="factsbody"><strong>Additional Relay Services</strong></p>
<p class="factsbody">IP Relay &#8211; Internet Protocol Relay</p>
<p class="factsbody">VRS -Video Relay Service</p>
<p class="factsbody">
<p class="factsbody">
<p class="factsbody"><strong>Information Resources</strong></p>
<p class="factsbody"><a title="711 Telephone Relay Service" href="http://711service.com/" target="_blank">711 Telephone Relay Service for the Deaf</a></p>
<p class="factsbody"><a title="Dial 711 for Telecommunications Relay Service (TRS)" href="http://www.fcc.gov/cgb/consumerfacts/711.html" target="_blank">FCC Dial 711 for Telecommunications Relay</a></p>
<p class="factsbody"><a title="i711.com - Relay &amp; Beyond | Text and Video Relay Services" href="http://www.i711.com/" target="_blank">i711.com</a></p>
<p class="factsbody"><a title="Internet Relay Service for Deaf and Hard of Hearing" href="http://www.ip-relay.com" target="_blank">ip-relay.com</a></p>
<p class="factsbody">
<p class="factsbody">
<p class="factsbody">
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2009/05/03/711-trs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ARMAD 2009</title>
		<link>http://searn.asteriskradio.net/blog/archives/2009/04/12/armad-2009/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2009/04/12/armad-2009/#comments</comments>
		<pubDate>Sun, 12 Apr 2009 22:16:35 +0000</pubDate>
		<dc:creator>w4wwm</dc:creator>
				<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[amateur radio]]></category>
		<category><![CDATA[appreciation]]></category>
		<category><![CDATA[military]]></category>
		<category><![CDATA[support]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/?p=98</guid>
		<description><![CDATA[It&#8217;s time again for Amateur Radio Military Appreciation Day (ARMAD) on 23 May 2009, here in Madison/Huntsville, AL.  We will be setting up at a new site this year.  When more information come available we will announce the site location.
The Asterisk Amateur Radio Network will be join with the Drake State Technical College [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s time again for Amateur Radio Military Appreciation Day (ARMAD) on 23 May 2009, here in Madison/Huntsville, AL.  We will be setting up at a new site this year.  When more information come available we will announce the site location.</p>
<p>The Asterisk Amateur Radio Network will be join with the Drake State Technical College Amateur Radio Club promoting the use of amateur radio along with giving thanks and appreciation to our men and women who have served and who are serving now in the Arm Forces.  This will be a great day for all to come out and support the troops on a job that continues to be at the fore front of our mission for the country and the world.<span id="more-98"></span></p>
<p>We hope to have HF/VHF/UHF radio system setup for operations. Making contact to other ARMAD or any amateur radio stations. We will also use VoIP systems such as Asterisk, IRLP and Echolink for those who would like to call in. There is also a special IRLP reflector for all IRLP station to call into. This IRLP reflector is experimental node 0011.  This is a special IRLP reflector and you will need to make sure your IRLP node are setup to make the call into.  More information will be put out on these special parameters in a few days. So stay tune.</p>
<p>For Asterisk call in, one can call in on AST node 2048, this way you will be able to talk to IRLP and echolink nodes alike. For Echolink nodes one can call in on the Kansas Reflector, node 44445 and W4WWM-L, node 54572. Any of these connections will be fine.  We would also like to try something new. We will have a control Ham Radio operator standing by for third party calls. This way we can also show the power of Asterisk PBX. So look for more special information on how this will happen here on this site.</p>
<p>Anyway we will look for all to come out and support this great day for ARMAD and to make radio contacts using our hobby, amateur radio to communicate.  73 and Stay tune for more info!</p>
<p>Will / W4WWM</p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2009/04/12/armad-2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OPS Site</title>
		<link>http://searn.asteriskradio.net/blog/archives/2009/04/12/ops-site/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2009/04/12/ops-site/#comments</comments>
		<pubDate>Sun, 12 Apr 2009 18:59:55 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[emergency]]></category>
		<category><![CDATA[ESF-2]]></category>
		<category><![CDATA[ESF-7]]></category>
		<category><![CDATA[gis]]></category>
		<category><![CDATA[mapping]]></category>
		<category><![CDATA[operations]]></category>
		<category><![CDATA[resource]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/?p=97</guid>
		<description><![CDATA[ALERTradio ERC &#124; Operations web site is operational.

The purpose of the ALERTradio ERC &#124; Operations web site is to have a centralized location for information related to active events and incidents in the primary service areas of ALERTradio ERC.   Also information regarding support requests will be presented.
Future additions will include Resource Location Service (RLS) based [...]]]></description>
			<content:encoded><![CDATA[<p><a title="ALERTradio ERC | Operations" href="http://ops.alertradio.net" target="_blank">ALERTradio ERC | Operations</a> web site is operational.</p>
<p><span id="more-97"></span></p>
<p>The purpose of the <a title="ALERTradio ERC | Operations" href="http://ops.alertradio.net" target="_blank">ALERTradio ERC | Operations</a> web site is to have a centralized location for information related to active events and incidents in the primary service areas of ALERTradio ERC.   Also information regarding support requests will be presented.</p>
<p>Future additions will include Resource Location Service (RLS) based on the project MAR-D.   If anyone has experience working with GIS integration please contact us via <a title="ALERTradio ERC | InfoQuest" href="http://www.alertradio.net/infoquest.php" target="_blank">InfoQuest</a> so we can find out what would be the best way to map the locations of available resources as well as determine nearest resource availability.</p>
<p>ALERTradio ERC &#8211; <em>It&#8217;s all about being ready!</em></p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2009/04/12/ops-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DARN is near</title>
		<link>http://searn.asteriskradio.net/blog/archives/2008/12/09/darn-is-near/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2008/12/09/darn-is-near/#comments</comments>
		<pubDate>Tue, 09 Dec 2008 19:46:18 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[RF Gateways]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/?p=96</guid>
		<description><![CDATA[The Digital Analog Radio Network is near.
DARN defined as to mend by weaving thread across a gap that is what is being done.   Those that want to see flexibility will go with the DARN approach, as a improvement while there will be others that find it to be just annoyance.    DARN definitely fits the new [...]]]></description>
			<content:encoded><![CDATA[<p>The Digital Analog Radio Network is near.</p>
<p>DARN defined as <em>to mend by weaving thread across a gap</em> that is what is being done.   Those that want to see flexibility will go with the DARN approach, as a improvement while there will be others that find it to be just annoyance.    DARN definitely fits the new Digital Analog Radio Networks.</p>
<p>Sometimes logic can indeed be simple (send in most potentially linkable exchange).</p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2008/12/09/darn-is-near/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dynamic Paths</title>
		<link>http://searn.asteriskradio.net/blog/archives/2008/06/21/dynamic-paths/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2008/06/21/dynamic-paths/#comments</comments>
		<pubDate>Sat, 21 Jun 2008 15:15:18 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/2008/06/21/dynamic-paths/</guid>
		<description><![CDATA[Just like other living things there are good and bad times for dynamic paths that are taken.
 One can opt to be static yet knowing dynamic paths will move you.
&#160;

What does this mean to those that work in the area of emergency response?
Be flexible with the methods that are used, yet maintain the basic standards [...]]]></description>
			<content:encoded><![CDATA[<p align="center"><em>Just like other living things there are good and bad times for dynamic paths that are taken.</em></p>
<p align="center"> <em>One can opt to be static yet knowing dynamic paths will move you.</em></p>
<p align="center">&nbsp;</p>
<hr color="gold" width="50%" />
<p>What does this mean to those that work in the area of emergency response?</p>
<p>Be flexible with the methods that are used, yet maintain the basic standards that allow a incident operation to be conducted safely. Standards which remain static can be used as a basis for operation integrity and also represent a road map to a successful mission.</p>
<p>Standard Operation Procedures provide the static portion for operational planning yet they should also be dynamic so that when new methods are presented they can be placed into the Standard Operation Procedures as soon as possible.</p>
<p>Every situation, every incident is different, thus the need for being dynamic in operational style.    At times incidents will take place that are not amongst the normal operational situations.   This indeed is one of the times that we need to be dynamic in readiness and response.</p>
<p>Flexibility is a key ingredient to readiness and the &#8220;all hazard&#8221; approach to  emergency response and planning.</p>
<p>As a organization which path are you opting for:  static or dynamic flexibility?</p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2008/06/21/dynamic-paths/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Key Words used in Voice Operations</title>
		<link>http://searn.asteriskradio.net/blog/archives/2008/03/12/key-words-used-in-voice-operations/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2008/03/12/key-words-used-in-voice-operations/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 19:27:45 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/2008/03/12/key-words-used-in-voice-operations/</guid>
		<description><![CDATA[
KEY WORDS USED IN VOICE OPERATION
The following words should be used by all  voice operators  during an emergency or exercise. Note that all  use of jargon or &#8220;Q&#8221; signals is STRICTLY PROHIBITED. All voice communication  must be done in plain language ONLY. Please observe the following key words.  Typically, most communicators [...]]]></description>
			<content:encoded><![CDATA[<p><font size="2"></p>
<h4>KEY WORDS USED IN VOICE OPERATION</h4>
<p>The following words should be used by all  voice operators  during an emergency or exercise. Note that all  use of jargon or &#8220;Q&#8221; signals is STRICTLY PROHIBITED. All voice communication  must be done in plain language ONLY. Please observe the following key words.  Typically, most communicators use these words every day however, if you are not in  the habit of using them then please be mindful of them when using voice during  an event or incident operation.</font><span id="more-57"></span><font size="2"></p>
<table border="1">
<tr>
<td>AFFIRMATIVE</td>
<td>&#8220;Yes&#8221; or &#8220;Permission granted&#8221;</td>
</tr>
<tr>
<td>ALL AFTER</td>
<td>&#8220;Repeat all your transmission after &#8230;. &#8220;</td>
</tr>
<tr>
<td>ALL BEFORE</td>
<td>&#8220;Repeat all your transmission before &#8230;. &#8220;</td>
</tr>
<tr>
<td valign="top">BREAK</td>
<td>&#8220;I wish to stop your transmission&#8221; Also used at the end of address and        at end of text in message handling to enable repeats to be requested. Also        used to terminate message with one station and start message to another        during the same transmission. For instance, &#8220;Thank-you VE3ZZZ for your        report. BREAK VE3AAA are you ready to copy?&#8221;</td>
</tr>
<tr>
<td valign="top">BREAK BREAK</td>
<td>(Double break) This is used when a station has very time critical        emergency traffic that must be passed on frequency. Stations hearing a        double break must relinquish the frequency immediately to the calling        station.</td>
</tr>
<tr>
<td valign="top">CLEAR</td>
<td>&#8220;Transmissions to this station completed&#8221; This station is now free to        establish communication with another station.</td>
</tr>
<tr>
<td>CORRECT</td>
<td>&#8220;You are ____&#8221; or &#8220;That is ______&#8221;.</td>
</tr>
<tr>
<td>DISREGARD</td>
<td>&#8220;The transmission was in error. Disregard it.</td>
</tr>
<tr>
<td>FIGURES</td>
<td>&#8220;Following numerals are to be copied as a group.&#8221;</td>
</tr>
<tr>
<td>FROM</td>
<td>&#8220;This is station &#8230;&#8221;</td>
</tr>
<tr>
<td>GO AHEAD</td>
<td>&#8220;Begin sending.&#8221; Used the same as &#8220;Over&#8221;.</td>
</tr>
<tr>
<td>INITIAL</td>
<td>&#8220;A single letter or initial follows.&#8221;</td>
</tr>
<tr>
<td>I SPELL</td>
<td>&#8220;I will spell the next word&#8221;</td>
</tr>
<tr>
<td>NEGATIVE</td>
<td>&#8220;Not received&#8221; or &#8220;No&#8221;</td>
</tr>
<tr>
<td>OUT</td>
<td>&#8220;End of transmission. No response expected&#8221;</td>
</tr>
<tr>
<td>OVER</td>
<td>&#8220;End of Transmission. Awaiting your response&#8221;</td>
</tr>
<tr>
<td>READ BACK</td>
<td>&#8220;Repeat entire message&#8221;</td>
</tr>
<tr>
<td>ROGER</td>
<td>&#8220;Have received last transmission&#8221; (Does NOT mean AFFIRMATIVE)</td>
</tr>
<tr>
<td>SAY AGAIN</td>
<td>&#8220;Repeat last transmission&#8221;</td>
</tr>
<tr>
<td>STAND BY</td>
<td>&#8220;I will monitor&#8221; or &#8220;Please monitor&#8221;</td>
</tr>
<tr>
<td>THIS IS</td>
<td>&#8220;This is station &#8230; &#8220;</td>
</tr>
<tr>
<td>VERIFY</td>
<td>&#8220;Verify entire message with addresses&#8221;</td>
</tr>
<tr>
<td>WILCO</td>
<td>&#8220;I will comply&#8221; or &#8220;Will do&#8221;</td>
</tr>
</table>
<p><em>Eg: The boss wants  to know if you have handed in the log sheets.<br />
- AFFIRMATIVE: Yes, I&#8217;ve  handed them in.<br />
- WILCO: No, but I will hand them in now.<br />
- ROGER: I  copied the message. I&#8217;ll ask someone in charge.<br />
- YES: So, what else does he  want to know?</em></font></p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2008/03/12/key-words-used-in-voice-operations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What if? A short list to readiness.</title>
		<link>http://searn.asteriskradio.net/blog/archives/2007/10/16/what-if-a-short-list-to-readiness/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2007/10/16/what-if-a-short-list-to-readiness/#comments</comments>
		<pubDate>Wed, 17 Oct 2007 00:05:35 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/2007/10/16/what-if-a-short-list-to-readiness/</guid>
		<description><![CDATA[What if? That is the question often asked as a starting point to preparedness. Ask yourself, what if we loose all electricity, a tower site, Telco, microwave or network infrastructure, our ability to recharge radio batteries? What if we have a lack of fuel for our back up generators and emergency response vehicles or a [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">What if? </span>That is the question often asked as a starting point to preparedness. Ask yourself, what if we loose all electricity, a tower site, Telco, microwave or network infrastructure, our ability to recharge radio batteries? What if we have a lack of fuel for our back up generators and emergency response vehicles or a lack of basic life supporting essentials? While this is an extremely short list, answering such questions before an emergency is a proven way to ensure our success during an emergency.</span></span></p>
<p><span id="more-40"></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Work together</span>.  </span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">Working together is the key to communications interoperability. Develop your partnerships, mutual aid agreements, standard operating procedures and the availability of resources (equipment reserves) in your locality, region and state.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Know your contacts</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  Know your mutual aid points of contacts and all methods to contact them, cellular, telephone, email, text messaging, fax, etc.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Train and practice</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  Training and Practice are two key essentials to ensure all personnel are familiar with communications interoperability procedures and equipment.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Test regularly</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  Conduct regular testing of all communications infrastructure to include the availability of service and support, proper radio programming and the sharing of mutual aid and common frequencies throughout your region.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Know the proper procedures</span>. </span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"> Embrace and incorporate the procedures of the Incident Command System and the National Incident Management System into your emergency operations plans.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Have available resources</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  Develop resource list and adopt private &#8211; public partnerships in advance to be able to seamlessly obtain assistance. Many agencies have recently reached out to Amateur Radio Groups for communications assistance; their resources and expertise can be extremely helpful.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Designate a communications leader</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  During a response, designate a communications officer to oversee and coordinate communication and interoperability resources as they arrive and deploy.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Follow basic procedures</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  To avoid confusion and multiple interoperability patches some basic gateway activation procedures should be followed. They include: requesting authorization for an interoperability patch with participating agency before establishing a patch; utilize plain English transmissions during an interoperability patch and all radio transmissions should identify the agency along with the unit identifier when patching multiple agencies or public safety disciplines.</span></span><br />
<span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold"></span></span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif"><span style="font-weight: bold">Take inventory</span>.</span></span></p>
<p><span style="font-size: 15pt"><span style="font-family: 'Verdana',sans-serif">  When preparing for mutual aid assistance be sure to inventory your available interconnect cables to ensure you have the proper cables for the area or region where you are going to deploy. Likewise, ensure all mutual aid simplex frequencies are preprogrammed into your radios and have available radio programming software and personnel trained to conduct programming if required.</span></span><span> </span></p>
<p style="text-align: right"><span style="font-size: 8pt">http://www.jps.com/page/view/208</span></p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2007/10/16/what-if-a-short-list-to-readiness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>National Incident Management System (NIMS)</title>
		<link>http://searn.asteriskradio.net/blog/archives/2007/10/01/national-incident-management-system-nims/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2007/10/01/national-incident-management-system-nims/#comments</comments>
		<pubDate>Mon, 01 Oct 2007 14:45:28 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Emergency Response]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/2007/10/01/national-incident-management-system-nims/</guid>
		<description><![CDATA[While most emergency situations are handled locally, when there&#8217;s a major incident help may be needed from other jurisdictions, the state and the federal government. NIMS was developed so responders from different jurisdictions and disciplines can work together better to respond to natural disasters and emergencies, including acts of terrorism. NIMS benefits include a unified [...]]]></description>
			<content:encoded><![CDATA[<p>While most emergency situations are handled locally, when there&#8217;s a major incident help may be needed from other jurisdictions, the state and the federal government. NIMS was developed so responders from different jurisdictions and disciplines can work together better to respond to natural disasters and emergencies, including acts of terrorism. NIMS benefits include a unified approach to incident management; standard command and management structures; and emphasis on preparedness, mutual aid and resource management.</p>
<p><span id="more-39"></span></p>
<p>Fact Sheet: NIMS Essential Standards List (<a href="http://www.fema.gov/pdf/emergency/nims/fact_sheet_standards.pdf" target="_blank">PDF</a> 19KB)</p>
<p><em>NIMS Basic</em>: Concepts and Principles, Systems and Processes</p>
<p>The <em>NIMS Basic</em> series describes the concepts and<br />
principles, systems and processes, responsibilities and required<br />
capabilities associated with the major components of the National<br />
Incident Management System. The series consists of nine guides to NIMS<br />
components, as follows:</p>
<ul>
<li>NIMS Introduction and Overview (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_introduction_and_overview.pdf" target="_blank">PDF</a> 54KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_introduction_and_overview.txt" target="_blank">TXT</a> 20KB)</li>
<li>Command and Management (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_command_and_management.pdf" target="_blank">PDF</a> 112KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_command_and_management.txt" target="_blank">TXT</a> 52KB)</li>
<li>Preparedness (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_preparedness.pdf" target="_blank">PDF</a> 57KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_preparedness.txt" target="_blank">TXT</a> 22KB)</li>
<li>Resource Management (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_resource_management.pdf" target="_blank">PDF</a> 53KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_resource_management.txt" target="_blank">TXT</a> 18KB)</li>
<li>Communications and Information Management (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_communications_and_information_management.pdf" target="_blank">PDF</a> 38KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_communications_and_information_management.txt" target="_blank">TXT</a> 15KB)</li>
<li>Supporting Technologies (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_supporting_technologies.pdf" target="_blank">PDF</a> 37KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_supporting_technologies.txt" target="_blank">TXT</a> 10KB)</li>
<li>Ongoing Management and Maintenance (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_ongoing_management_and_maintenance.pdf" target="_blank">PDF</a> 44KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_ongoing_management_and_maintenance.txt" target="_blank">TXT</a> 14KB)</li>
<li>Incident Command System (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_incident_command_system.pdf" target="_blank">PDF</a> 132KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_incident_command_system.txt" target="_blank">TXT</a> 64KB)</li>
<li>Resource Typing (<a href="http://www.fema.gov/pdf/nims/NIMS_basic_resource_typing_system.pdf" target="_blank">PDF</a> 95KB, <a href="http://www.fema.gov/txt/nims/NIMS_basic_resource_typing_system.txt" target="_blank">TXT</a> 13KB)</li>
</ul>
<p>NIMS Smart Practices (<a href="http://www.fema.gov/pdf/emergency/nims/nims-smart-practice.pdf" title="PDF of NIMS Smart Practices document">PDF</a> 22KB, <a href="http://www.fema.gov/txt/emergency/nims/nims-smart-practice.txt" title="Tex?t of NIMS Smart Practices document">TXT</a> 6KB)</p>
<p>National Emergency Responder Credentialing System (<a href="http://www.fema.gov/pdf/emergency/nims/credentialing.pdf" title="PDF version of Hospital Emergency Incident Command System">PDF</a> 17KB, <a href="http://www.fema.gov/txt/emergency/nims/credentialing.txt" title="Text version of Hospital Emergency Incident Command System">TXT</a> 3KB)</p>
<p>Credentialing FAQs (<a href="http://www.fema.gov/pdf/emergency/nims/credent_faq.pdf" title="PDF version of Hospital Emergency Incident Command System">PDF</a> 48KB, <a href="http://www.fema.gov/txt/emergency/nims/credent_faq.txt" title="Text version of Hospital Emergency Incident Command System">TXT</a> 10KB)</p>
<p>Federal Preparedness Grant Programs (<a href="http://www.fema.gov/pdf/emergency/nims/federal_prep_grant_prog.pdf" title="PDF version of Hospital Emergency Incident Command System">PDF</a> 25KB, <a href="http://www.fema.gov/txt/emergency/nims/federal_prep_grant_prog.txt" title="Text version of Hospital Emergency Incident Command System">TXT</a> 5KB)</p>
<blockquote><p>This information was provided by federal departments and<br />
agencies to the NIMS Integration Center regarding their preparedness<br />
funding programs with state and local entities, including cooperative<br />
agreements, memorandums of understandings, grants and contracts. We are<br />
making this preliminary list available to help state and local entities<br />
identify funding streams that may be affected in connection with NIMS<br />
implementation requirements. This should not be considered a definitive<br />
list of federal preparedness grants and agreements.</p></blockquote>
<p>NIIMS-NIMS Comparison (<a href="http://www.fema.gov/txt/emergency/nims/NIIMS-NIMSComparison.txt" title="Text version of NIIMS - NIMS Comparison">TXT</a> 5KB)</p>
<p>Institutionalizing the Use of ICS (<a href="http://www.fema.gov/pdf/emergency/nims/institutionalizing_ics.pdf" title="PDF version of Terms and Definitions: Institutionalizing the Use of ICS">PDF</a> 44KB, <a href="http://www.fema.gov/txt/emergency/nims/institutionalizing_ics.txt" title="Text version of Terms and Definitions: Institutionalizing the Use of ICS">TXT</a> 2KB)</p>
<p>NIMS and the Incident Command System (<a href="http://www.fema.gov/txt/emergency/nims/nims_ics_position_paper.txt" title="Text version of NIMS and the Incident Command System">TXT</a> 26KB)</p>
<p>This paper is intended to provide an historical perspective<br />
on the development of ICS, explain how NIMS ICS works, describe how it<br />
is different from previous systems, and discuss the future of NIMS ICS<br />
training.</p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2007/10/01/national-incident-management-system-nims/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Emergency Operations &#8211; Regulations</title>
		<link>http://searn.asteriskradio.net/blog/archives/2007/09/20/emg-ops/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2007/09/20/emg-ops/#comments</comments>
		<pubDate>Fri, 21 Sep 2007 00:26:51 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/2007/09/20/emg-ops/</guid>
		<description><![CDATA[Emergency Operations &#8211; Regulations regarding radio communications.
A station in, or within 50 nautical miles of Alaska may transmit emissions J3E and R3E on the channel at 5.1675 MHz (assigned frequency 5.1689 MHz) for emergency communications. The channel must be shared with stations licensed in the Alaska-Private Fixed Service. The transmitter power must not exceed 150 [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Emergency Operations &#8211; Regulations regarding radio communications.</strong></p>
<p>A station in, or within 50 nautical miles of Alaska may transmit emissions J3E and R3E on the channel at 5.1675 MHz (assigned frequency 5.1689 MHz) for emergency communications. The channel must be shared with stations licensed in the Alaska-Private Fixed Service. The transmitter power must not exceed 150 W PEP. A station in, or within 92.6 km of, Alaska may transmit communications for tests and training drills necessary to ensure the establishment, operation, and maintenance of emergency communication systems.<br />
<span id="more-74"></span><span id="more-38"></span><br />
<strong>AMATEUR RADIO</strong><br />
Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=97&amp;SECTION=401" title="Click here for PDF version">97</a>.<a href="http://www.hallikainen.com/FccRules/2007/97/401" title="Click here for HTML version">401</a> Operation during a disaster. A station in, or within 92.6 km (50 nautical miles) of, Alaska may transmit emissions J3E and R3E on the channel at 5.1675 MHz (assigned frequency5.1689 MHz) for emergency communications. The channel must be shared withstations licensed in the Alaska-Private Fixed Service. The transmitter powermust not exceed 150 W PEP. A station in, or within 92.6 km of, Alaska maytransmit communications for tests and training drills necessary to ensure the establishment, operation, and maintenance of emergency communicationsystems.</p>
<p>[ <a href="http://fr.hallikainen.org/?vol=71&amp;page=66465">71 FR 66465</a> , Nov. 15, 2006]</p>
<p>——</p>
<p>Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=97&amp;SECTION=403" title="Click here for PDF version">97</a>.<a href="http://www.hallikainen.com/FccRules/2007/97/403" title="Click here for HTML version">403</a> Safety of life and protection of property. No provision of these rules prevents the use by an amateur station of any means of radiocommunication at its disposal to provide essentialcommunication needs in connection with the immediate safety of human life and immediate protection of property when normal communication systems are<br />
not available.</p>
<p>——-</p>
<p>Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=97&amp;SECTION=405" title="Click here for PDF version">97</a>.<a href="http://www.hallikainen.com/FccRules/2007/97/405" title="Click here for HTML version">405</a> Station in distress. (a) No provision of these rules prevents the use by an amateur station in distress of any means at its disposal to attract attention, make known itscondition and location, and obtain assistance.</p>
<p>(b) No provision of these rules prevents the use by a station, in the exceptional circumstances described in paragraph (a) of this section, of any means of radio communications at its disposal to assist a station in distress.</p>
<p>——</p>
<p><strong>GMRS</strong></p>
<p>Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=95&amp;SECTION=143" title="Click here for PDF version">95</a>.<a href="http://www.hallikainen.com/FccRules/2007/95/143" title="Click here for HTML version">143</a> Managing a GMRS system in an emergency. (a) The stations in a GMRS system must cease transmitting when the station operator of any station on the same channel is communicating an emergencymessage (concerning the immediate protection of property or the safety of someone’s life).</p>
<p>(b) If necessary to communicate an emergency message from a station in a GMRS system, the licensee may permit:</p>
<p>(1) Anyone to be the station operator (see  Sec. <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=95&amp;SECTION=179" title="Click here for PDF version">95</a>.<a href="http://www.hallikainen.com/FccRules/2007/95/179" title="Click here for HTML version">179</a>); and</p>
<p>(2) The station operator to communicate the emergency message to any radio station.</p>
<p>——</p>
<p><strong>Public Safety / Industrial Business</strong></p>
<p>Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=90&amp;SECTION=407" title="Click here for PDF version">90</a>.<a href="http://www.hallikainen.com/FccRules/2007/90/407" title="Click here for HTML version">407</a> Emergency communications. The licensee of any station authorized under this part may, during a period of emergency in which the normal communication facilities are disrupted as aresult of hurricane, flood, earthquake or similar disaster, utilize such station for emergency communications in a manner other than that specified in the station authorization or in the rules and regulations governing the operation of such stations. The Commission may at any time order the discontinuance of such special use of the authorized facilities.</p>
<p>[ <a href="http://fr.hallikainen.org/?vol=49&amp;page=36376">49 FR 36376</a> , Sept. 17, 1984]</p>
<p>——</p>
<p>Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=90&amp;SECTION=411" title="Click here for PDF version">90</a>.<a href="http://www.hallikainen.com/FccRules/2007/90/411" title="Click here for HTML version">411</a> Civil defense communications. The licensee of any station authorized under this part may, on a voluntary basis, transmit communications necessary for the implementation of civildefense activities assigned such station by local civil defense authorities during an actual or simulated emergency, including drills and tests. The Commission may at any time order the discontinuance of such special use of the authorized facilities.</p>
<p>[ <a href="http://fr.hallikainen.org/?vol=49&amp;page=36376">49 FR 36376</a> , Sept. 17, 1984]</p>
<p>——</p>
<p>Sec.  <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=90&amp;SECTION=417" title="Click here for PDF version">90</a>.<a href="http://www.hallikainen.com/FccRules/2007/90/417" title="Click here for HTML version">417</a> Interstation communication. (a) Any station licensed under this part may communicate with any other station without restriction as to type, service, or licensee when thecommunications involved relate directly to the imminent safety-of-life or property.</p>
<p>(b) Any station licensed under this part may communicate with any other station licensed under this part, with U.S. Government stations, and with foreign stations, in connection with mutual activities, provided that where the communication involves foreign stations prior approval of the Commission must be obtained, and such communication must be permitted by the government that authorizes the foreign station. Communications by Public Safety Pool eligibles with foreign stations will be approved only to be conducted in accordance with Article 5 of the Inter-American Radio Agreement, Washington, DC, 1949, the provisions of which are set forth in Sec. <a href="http://frwebgate.access.gpo.gov/cgi-bin/get-cfr.cgi?TITLE=47&amp;TYPE=PDF&amp;YEAR=2005&amp;PART=90&amp;SECTION=20" title="Click here for PDF version">90</a>.<a href="http://www.hallikainen.com/FccRules/2007/90/20" title="Click here for HTML version">20</a>(b).</p>
<p>[ <a href="http://fr.hallikainen.org/?vol=43&amp;page=54791">43 FR 54791</a> , Nov. 22, 1978, as amended at  <a href="http://fr.hallikainen.org/?vol=62&amp;page=18933">62 FR 18933</a> , Apr. 17, 1997]</p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2007/09/20/emg-ops/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PSKmail &#8211; Another Emergency Response Tool</title>
		<link>http://searn.asteriskradio.net/blog/archives/2007/09/04/pskm/</link>
		<comments>http://searn.asteriskradio.net/blog/archives/2007/09/04/pskm/#comments</comments>
		<pubDate>Tue, 04 Sep 2007 19:44:56 +0000</pubDate>
		<dc:creator>OPS</dc:creator>
				<category><![CDATA[Communications]]></category>
		<category><![CDATA[Emergency Response]]></category>

		<guid isPermaLink="false">http://searn.alertradio.net/blog/2007/09/04/pskm/</guid>
		<description><![CDATA[ PSKmail as described on http://pskmail.wikispaces.com/
PSKmail is a narrow band mail delivery system for use by amateur radio hams via short wave (HF) communication. It is only available for Linux (it is time to change to Linux anyway&#8230;). Unlike PACTOR, it does not use a special controller, you just need a computer with a sound [...]]]></description>
			<content:encoded><![CDATA[<p> PSKmail as described on <a href="http://pskmail.wikispaces.com/" title="PSKmail Home Wiki" target="_blank">http://pskmail.wikispaces.com/</a></p>
<p>PSKmail is a narrow band mail delivery system for use by amateur radio hams via short wave (HF) communication. It is only available for Linux (it is time to change to Linux anyway&#8230;). Unlike PACTOR, it does not use a special controller, you just need a computer with a sound card. PSKmail uses Fldigi in PSK125 mode.</p>
<p>PSKmail has a client/server architecture. Unlike Packet Radio (Q15X25) the PSKmail protocol only allows 1 connected client at the time. Bandwidth (3dB) is 129 Hz!!!</p>
<p>The PSKmail client is written in GTK2 perl. At this moment the applications is a Mailbox (port 24) allowing down/upload of mail from the internet, and downloading information from the web (ASCII text only), position update and station-to-station messaging via APRS(port26) and chat mode (TTY, port 87).</p>
<p><em><strong>Version 0.4 has enhancements for emergency communications. This means that even if the internet backbone is down, you will still be able to send messages and files from client to client.</strong></em></p>
<p>Pskmail now also works together with EVOLUTION and other Linux mail clients. You can then use the mail integrator you are used to (any mbox compatible system).</p>
<p>There&#8217;s a <a href="http://pskmail.wikispaces.com/live_distro" title="PSKLive  - LiveCD http://pskmail.wikispaces.com/live_distro" target="_blank">PSKLive (LiveCD) </a>available to test with.  The LiveCD allows one to operate the programs without accessing the hard drive on their computer.</p>
<p>As for Technicians &#8230; the 10m Band is the place we can use PSKmail on HF.</p>
<p><font size="5"><font face="Arial" size="-1"><span style="font-size: 12px"><font size="5"><strong><font size="4">28.000 &#8211; 28.300 MHz: CW, RTTY/Data&#8211;<br />
<font color="#ff0000">Maximum power 200 watts PEP</font></font></strong></font></span></font></font></p>
<p>Be interesting to find out what kind of coverage is available.</p>
<p align="right"><a href="http://www.sitescollide.com/Podcast/A9E57300-1599-41DF-A399-558B23EE4DDF_files/SCR014.mp3" title="Interview Audio Regarding PSKmail" target="_blank">Interview Audio Regarding PSKmail</a></p>
]]></content:encoded>
			<wfw:commentRss>http://searn.asteriskradio.net/blog/archives/2007/09/04/pskm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
<enclosure url="http://www.sitescollide.com/Podcast/A9E57300-1599-41DF-A399-558B23EE4DDF_files/SCR014.mp3" length="8859271" type="audio/mpeg" />
		</item>
	</channel>
</rss>
