<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Mind The Gap</title>
	<link>http://www.esourcingforum.com/archives/2006/12/04/mind-the-gap/</link>
	<description>The source of information and best practices in strategic sourcing.</description>
	<pubDate>Fri, 04 Jul 2008 07:54:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Mark Usher</title>
		<link>http://www.esourcingforum.com/archives/2006/12/04/mind-the-gap/#comment-4010</link>
		<dc:creator>Mark Usher</dc:creator>
		<pubDate>Mon, 04 Dec 2006 18:14:17 +0000</pubDate>
		<guid>http://www.esourcingforum.com/archives/2006/12/04/mind-the-gap/#comment-4010</guid>
		<description>David, in general I agree with your definition re:difference between SRM and collaborative sourcing. My only caveat, based on my own experiences in engineered products sourcing, is the value of pre-award collaboration with supplier candidates to define innovative high level directional approaches to cost and value management in the respective commodity. Sometimes such evaluations are key in a type of "catch 22" situation where you need to get some of handle on which suppliers are likely to be effective in the full blown collaboration scenario.</description>
		<content:encoded><![CDATA[<p>David, in general I agree with your definition re:difference between SRM and collaborative sourcing. My only caveat, based on my own experiences in engineered products sourcing, is the value of pre-award collaboration with supplier candidates to define innovative high level directional approaches to cost and value management in the respective commodity. Sometimes such evaluations are key in a type of &#8220;catch 22&#8243; situation where you need to get some of handle on which suppliers are likely to be effective in the full blown collaboration scenario.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
