<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: A Few Comments On Aberdeen&#8217;s SaaS Report</title>
	<atom:link href="http://stephensnexus.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://stephensnexus.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/</link>
	<description>Dave Stephens on technology and business trends</description>
	<lastBuildDate>Wed, 08 Dec 2010 23:20:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Impartial observer</title>
		<link>http://stephensnexus.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/#comment-743</link>
		<dc:creator><![CDATA[Impartial observer]]></dc:creator>
		<pubDate>Thu, 20 Jul 2006 01:23:53 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/#comment-743</guid>
		<description><![CDATA[I&#039;m more with Dave than the SaaS-only SRM camp, despite having worked for a vendor of a SaaS offering.  The very beauty of SaaS is that, to the end user, the experience of using the application&#039;s features reveals nothing about the underlying deployment model (hosted versus on-premise).  This de-coupling is the greatest power of SaaS.  For many corporations, their IT groups simply can&#039;t support another application deployment given workload, strategy, cost overhead, etc.  

The trade-off of SaaS is fewer integration options.  Fortunately for most procurement departments, they are working on the basics of SRM and don&#039;t require anything more than arms-length interfaces to deliver the benefits within reach.  Examples are supplier master sync, spend data load, purchase req creation, etc.

With procurement maturity, however, comes the tighter integration of procurement processes with other departmental functions.  ...And the need to touch THOSE departments&#039; systems in a meaningful way.  I don&#039;t think anyone is considering a SaaS sourcing solution with deep integration to a collaborative design/PLM system to support design-to-source cycles that run in days or weeks.  In that respect, the ERP vendors&#039; solutions will ultimately appear more attractive and will sit on-premise given IT&#039;s control of those systems.

Bottom line: the rate of procurement transformation will dictate the useful life of SaaS and how long it remains as the most common deployment model.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m more with Dave than the SaaS-only SRM camp, despite having worked for a vendor of a SaaS offering.  The very beauty of SaaS is that, to the end user, the experience of using the application&#8217;s features reveals nothing about the underlying deployment model (hosted versus on-premise).  This de-coupling is the greatest power of SaaS.  For many corporations, their IT groups simply can&#8217;t support another application deployment given workload, strategy, cost overhead, etc.  </p>
<p>The trade-off of SaaS is fewer integration options.  Fortunately for most procurement departments, they are working on the basics of SRM and don&#8217;t require anything more than arms-length interfaces to deliver the benefits within reach.  Examples are supplier master sync, spend data load, purchase req creation, etc.</p>
<p>With procurement maturity, however, comes the tighter integration of procurement processes with other departmental functions.  &#8230;And the need to touch THOSE departments&#8217; systems in a meaningful way.  I don&#8217;t think anyone is considering a SaaS sourcing solution with deep integration to a collaborative design/PLM system to support design-to-source cycles that run in days or weeks.  In that respect, the ERP vendors&#8217; solutions will ultimately appear more attractive and will sit on-premise given IT&#8217;s control of those systems.</p>
<p>Bottom line: the rate of procurement transformation will dictate the useful life of SaaS and how long it remains as the most common deployment model.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Stephens</title>
		<link>http://stephensnexus.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/#comment-721</link>
		<dc:creator><![CDATA[Dave Stephens]]></dc:creator>
		<pubDate>Tue, 18 Jul 2006 14:35:51 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/#comment-721</guid>
		<description><![CDATA[Tim&#039;s post is definitely worth a read to understand the mindset of SaaS-only vendors. And although my position may be untraditional, I continue to be supportive of the delivery goals of SaaS. SaaS offers convenience &amp; makes sense in many situations. However..

The fact that Tim says SaaS is &quot;just like&quot; open source when it comes to community is laughable. It just goes to show you how hard it is for traditional companies, wrapped in SaaS packaging, to understand the new paradigm of open source. Tim, open source means freely available source code &amp; customer-led development! Not offering computers, A/C, and uninterruptible power to customers...]]></description>
		<content:encoded><![CDATA[<p>Tim&#8217;s post is definitely worth a read to understand the mindset of SaaS-only vendors. And although my position may be untraditional, I continue to be supportive of the delivery goals of SaaS. SaaS offers convenience &amp; makes sense in many situations. However..</p>
<p>The fact that Tim says SaaS is &#8220;just like&#8221; open source when it comes to community is laughable. It just goes to show you how hard it is for traditional companies, wrapped in SaaS packaging, to understand the new paradigm of open source. Tim, open source means freely available source code &amp; customer-led development! Not offering computers, A/C, and uninterruptible power to customers&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Supply Excellence &#187; Dave Stephens Stirs On Demand Debate</title>
		<link>http://stephensnexus.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/#comment-719</link>
		<dc:creator><![CDATA[Supply Excellence &#187; Dave Stephens Stirs On Demand Debate]]></dc:creator>
		<pubDate>Tue, 18 Jul 2006 13:36:46 +0000</pubDate>
		<guid isPermaLink="false">https://procurement.wordpress.com/2006/07/11/a-few-comments-on-aberdeens-saas-report/#comment-719</guid>
		<description><![CDATA[[...] Last week, Procurement Central attempted to incite a new war over On Demand and Software as a Service (SaaS). ERP executive-turned-blogger-turned-open source evangelist Dave Stephens used the release of Aberdeen Group&#8217;s latest On Demand Supply Management Benchmark report to try to minimize the significance of On Demand and SaaS as merely a new flavor of application hosting.  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Last week, Procurement Central attempted to incite a new war over On Demand and Software as a Service (SaaS). ERP executive-turned-blogger-turned-open source evangelist Dave Stephens used the release of Aberdeen Group&#8217;s latest On Demand Supply Management Benchmark report to try to minimize the significance of On Demand and SaaS as merely a new flavor of application hosting.  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

