<?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: Selecting SaaS Business Intelligence: A Response to Forrester Analyst Boris Evelson</title>
	<atom:link href="http://blog.pivotlink.com/2009/10/selecting-saas-business-intelligence-a-response-to-forrester-analyst-boris-evelson/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pivotlink.com/2009/10/selecting-saas-business-intelligence-a-response-to-forrester-analyst-boris-evelson/</link>
	<description></description>
	<lastBuildDate>Thu, 20 May 2010 19:41:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Kasabian</title>
		<link>http://blog.pivotlink.com/2009/10/selecting-saas-business-intelligence-a-response-to-forrester-analyst-boris-evelson/comment-page-1/#comment-17</link>
		<dc:creator>Dave Kasabian</dc:creator>
		<pubDate>Tue, 17 Nov 2009 15:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pivotlink.com/?p=129#comment-17</guid>
		<description>Dyke,
Boris did start a great thread and there are certainly lots of opinions on this topic.  One thing I would stress is the balance between Wayne&#039;s comment on time to deployment and Boris&#039; on architecture.  Selecting a solution that is quick to deploy but can&#039;t scale to meet other internal requirements could result in the enterprise deploying multiple SaaS BI solutions to meet each specific need.  This is a problem that has plagued on-premise BI customers, some research shows clients average 5 on-premise BI solutions and as many as 17.  SaaS BI customers should learn from that mistake and select a solution that can be deployed quickly but also be applied to other business needs as they arise.</description>
		<content:encoded><![CDATA[<p>Dyke,<br />
Boris did start a great thread and there are certainly lots of opinions on this topic.  One thing I would stress is the balance between Wayne&#8217;s comment on time to deployment and Boris&#8217; on architecture.  Selecting a solution that is quick to deploy but can&#8217;t scale to meet other internal requirements could result in the enterprise deploying multiple SaaS BI solutions to meet each specific need.  This is a problem that has plagued on-premise BI customers, some research shows clients average 5 on-premise BI solutions and as many as 17.  SaaS BI customers should learn from that mistake and select a solution that can be deployed quickly but also be applied to other business needs as they arise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne Eckerson</title>
		<link>http://blog.pivotlink.com/2009/10/selecting-saas-business-intelligence-a-response-to-forrester-analyst-boris-evelson/comment-page-1/#comment-14</link>
		<dc:creator>Wayne Eckerson</dc:creator>
		<pubDate>Tue, 27 Oct 2009 20:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pivotlink.com/?p=129#comment-14</guid>
		<description>Boris offers many good evaluation criteria. I would add that prospective buyers should investigate how much consulting time and work is required to get the BI application up and running. One big value proposition for SaaS BI vendors is that they offer very fast deployment times, which is true. But if you want to dimensionalize the data, add hierarchies for drill down and navigation, manage slowly changing dimensions, or transform data for quality or integration reasons it may take longer than advertised.</description>
		<content:encoded><![CDATA[<p>Boris offers many good evaluation criteria. I would add that prospective buyers should investigate how much consulting time and work is required to get the BI application up and running. One big value proposition for SaaS BI vendors is that they offer very fast deployment times, which is true. But if you want to dimensionalize the data, add hierarchies for drill down and navigation, manage slowly changing dimensions, or transform data for quality or integration reasons it may take longer than advertised.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
