<?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: e-RFx Best Practices and Associated Benefits</title>
	<atom:link href="http://www.esourcingforum.com/archives/2009/03/25/e-rfx-best-practices-and-associated-benefits-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.esourcingforum.com/archives/2009/03/25/e-rfx-best-practices-and-associated-benefits-2/</link>
	<description>The source of information and best practices in strategic sourcing.</description>
	<lastBuildDate>Fri, 13 Aug 2010 15:09:47 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: GRAILLOT Brice</title>
		<link>http://www.esourcingforum.com/archives/2009/03/25/e-rfx-best-practices-and-associated-benefits-2/comment-page-1/#comment-11432</link>
		<dc:creator>GRAILLOT Brice</dc:creator>
		<pubDate>Fri, 27 Mar 2009 14:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.esourcingforum.com/?p=14361#comment-11432</guid>
		<description>Hi,

All benefits mentioned above are true, but maybe a little bit theoretical.
In the real life, due to user-adoption, most of time I have noticed that only basic functionalities were used by buyers.
In this case, your eRFx tool may becomes a mailbox for procurement  ...   ;-(

In order to take all benefits from eRFx you need to invest in change management and to help buyers to use advanced functionalities. This way, you can reduce your sourcing cycle time, increase collaboration between team members and suppliers and so on ...
Otherwise, just forget it.

Take care,</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>All benefits mentioned above are true, but maybe a little bit theoretical.<br />
In the real life, due to user-adoption, most of time I have noticed that only basic functionalities were used by buyers.<br />
In this case, your eRFx tool may becomes a mailbox for procurement  &#8230;   ;-(</p>
<p>In order to take all benefits from eRFx you need to invest in change management and to help buyers to use advanced functionalities. This way, you can reduce your sourcing cycle time, increase collaboration between team members and suppliers and so on &#8230;<br />
Otherwise, just forget it.</p>
<p>Take care,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bertrand Maltaverne</title>
		<link>http://www.esourcingforum.com/archives/2009/03/25/e-rfx-best-practices-and-associated-benefits-2/comment-page-1/#comment-11430</link>
		<dc:creator>Bertrand Maltaverne</dc:creator>
		<pubDate>Thu, 26 Mar 2009 13:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.esourcingforum.com/?p=14361#comment-11430</guid>
		<description>Hi,

A few comments from a user satisfaction survey we ran internally that was related to our eRFx tool and that actually reinforce this post.

No1 benefit perceived by users = Centralized Repository, as highlighted in the post. Everything being in 1 single location, you get better tracking/management/retrieval of information. Not talking about enabling analytics.

No1 challenge = get suppliers to answer via the tool so &quot;communication  with suppliers&quot; is key!

Keep the good work!</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>A few comments from a user satisfaction survey we ran internally that was related to our eRFx tool and that actually reinforce this post.</p>
<p>No1 benefit perceived by users = Centralized Repository, as highlighted in the post. Everything being in 1 single location, you get better tracking/management/retrieval of information. Not talking about enabling analytics.</p>
<p>No1 challenge = get suppliers to answer via the tool so &#8220;communication  with suppliers&#8221; is key!</p>
<p>Keep the good work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
