<?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>GrayBear Resources Group &#187; mission-critical</title>
	<atom:link href="http://www.graybearcorp.com/tag/mission-critical/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.graybearcorp.com</link>
	<description>Telecom Cost Recovery</description>
	<lastBuildDate>Mon, 04 Oct 2010 16:32:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>RIM Outage, Why Your Company Should Not Delay</title>
		<link>http://www.graybearcorp.com/rim-outage-why-your-company-should-not-delay/</link>
		<comments>http://www.graybearcorp.com/rim-outage-why-your-company-should-not-delay/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 16:41:47 +0000</pubDate>
		<dc:creator>Benny</dc:creator>
				<category><![CDATA[Annoyances]]></category>
		<category><![CDATA[Blog]]></category>
		<category><![CDATA[Catastrophe]]></category>
		<category><![CDATA[Disruptive Forces]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[contingency plan]]></category>
		<category><![CDATA[mission-critical]]></category>
		<category><![CDATA[outage]]></category>
		<category><![CDATA[RIM]]></category>

		<guid isPermaLink="false">http://www.graybearcorp.com/?p=258</guid>
		<description><![CDATA[Reasearch In Motion&#8217;s (RIM) Blackberry network had yet again another outage effecting users of it&#8217;s smartphone devices.   For those who rely on the Blackberry this could be have been anything from slightly annoying to a major issue depending on each user&#8217;s reliance on the phone. RIM is hardly the only network that has been effected [...]]]></description>
			<content:encoded><![CDATA[<p>Reasearch In Motion&#8217;s (RIM) Blackberry network had yet again another outage effecting users of it&#8217;s smartphone devices.   For those who rely on the Blackberry this could be have been anything from slightly annoying to a major issue depending on each user&#8217;s reliance on the phone.</p>
<p>RIM is hardly the only network that has been effected by technical or physical glitches.  ALL networks have been down from time-to-time and thus effecting millions from being able to access critical information or relay important data.</p>
<p>However, as we grow more and more dependent upon our communications services and especially mobile devices ALL companies need to start planning for the inevitable today.</p>
<p>So how do you plan for such outages?</p>
<p>Some companies we work with have a contingency plan that they&#8217;ve put into place for  <em>some</em> instances.  The larger the company, the more apt they are to have those plans in place.  Major corporations especially are typically good at making sure should their critical communications services such as an emergency contact line, toll-free numbers and multiple carriers with separate entrances into a building have been planned for.</p>
<p><strong>But what about the less than mission-critical applications?</strong></p>
<p>Are other departments within your organization building up a dependency on seemingly unimportant aspects of your communications infrastructure?  Say for example marketing has built an application for a smartphone that relays time-sensitive information back to sales for inventory management.  Sure it&#8217;s important and you know that it&#8217;s critical, but what IF the carrier that hosts that application suddenly disappears?  Or critical text messages you assumed where stored on your phones actually were kept on the network and they&#8217;re all lost?</p>
<p>You MUST find the weaknesses within your network first and plan for all contingencies else you&#8217;ll find out in the long run that you have  a headache you never planned for.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.graybearcorp.com/rim-outage-why-your-company-should-not-delay/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

