 




<?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: CIOs&#8217; list of demands for public cloud providers</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/total-cio/cios-list-of-demands-for-public-cloud-providers/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/total-cio/cios-list-of-demands-for-public-cloud-providers/</link>
	<description>A SearchCIO.com blog</description>
	<lastBuildDate>Sat, 11 May 2013 17:51:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: GregBMe</title>
		<link>http://itknowledgeexchange.techtarget.com/total-cio/cios-list-of-demands-for-public-cloud-providers/#comment-577</link>
		<dc:creator>GregBMe</dc:creator>
		<pubDate>Fri, 24 Sep 2010 16:38:05 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/total-cio/?p=1536#comment-577</guid>
		<description><![CDATA[It is good that IT (and hopefully corporate) leadership is aware that deploying operational data to a platform is not simply &quot;fire and forget.&quot;  We know we are obligated to perform due diligence to some extent prior to engaging in activities that may affect our company and our customers, protecting the company and meeting compliance requirements. 

 I believe that our biggest challenge of moving to a vendor run cloud is different and less frequently addressed than the topics covered in the initial posting.
 The biggest impact of losing a cloud vendor (or for that matter a hosting vendor) on which you run large, critical operations is on business continuity*.   The promise of using hosted services/hosted platforms/cloud is that you can save big on people, energy, software, hardware….   Once we laid ‘em off and turned ‘em off we might be in a bit of a pickle to adapt and move our processes and applications to a new vendor-- even with some warning of a bankruptcy or significant change in architecture, applications, or offerings.  We need to plan for the effort and resources required to ensure business continuity and be able to decide when we need to act.   We need to monitor and communicate with our vendor to ensure we get a heads-up to that which will impact us, be prepared to assess the risk and, if necessary, find a solution.  This isn’t a one-time thing—it’s a continuing process based on situational awareness, risk, impact, and cost.]]></description>
		<content:encoded><![CDATA[<p>It is good that IT (and hopefully corporate) leadership is aware that deploying operational data to a platform is not simply &#8220;fire and forget.&#8221;  We know we are obligated to perform due diligence to some extent prior to engaging in activities that may affect our company and our customers, protecting the company and meeting compliance requirements. </p>
<p> I believe that our biggest challenge of moving to a vendor run cloud is different and less frequently addressed than the topics covered in the initial posting.<br />
 The biggest impact of losing a cloud vendor (or for that matter a hosting vendor) on which you run large, critical operations is on business continuity*.   The promise of using hosted services/hosted platforms/cloud is that you can save big on people, energy, software, hardware….   Once we laid ‘em off and turned ‘em off we might be in a bit of a pickle to adapt and move our processes and applications to a new vendor&#8211; even with some warning of a bankruptcy or significant change in architecture, applications, or offerings.  We need to plan for the effort and resources required to ensure business continuity and be able to decide when we need to act.   We need to monitor and communicate with our vendor to ensure we get a heads-up to that which will impact us, be prepared to assess the risk and, if necessary, find a solution.  This isn’t a one-time thing—it’s a continuing process based on situational awareness, risk, impact, and cost.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
