<?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: Retail and MDM</title>
	<atom:link href="http://blogs.gartner.com/andrew_white/2008/12/02/retail-and-mdm/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/andrew_white/2008/12/02/retail-and-mdm/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Thu, 22 Sep 2011 13:59:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Andrew White</title>
		<link>http://blogs.gartner.com/andrew_white/2008/12/02/retail-and-mdm/comment-page-1/#comment-121</link>
		<dc:creator>Andrew White</dc:creator>
		<pubDate>Fri, 19 Jun 2009 14:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/andrew_white/?p=84#comment-121</guid>
		<description>Hi John, thanks for the post.  I wish retailers really &quot;got MDM&quot;.  Certainly retailers have a great need; many have grown via acquisition and rarely spend the time or money rationalizing systems, processes, or data.  The average tenure of the CIO in retail is a lot shorter than for their supplier/partners so the level of &quot;planning&quot; remains much more short tern, tactical, or granular.

I have seen some activity, perhaps most, on &quot;in-bound&quot; product and related data from suppliers; some on &quot;out-bound&quot; multi-channel integration, and much less &quot;enterprise&quot; oriented to connect the other two to the rest of the business.  Also, too many business applications - and BI providers - maintain &quot;master data&quot; (or say they do) when in fact they don&#039;t; they master application specific data that may or may not include a reference to master data.  This clouds the issue for many immature MDM program managers.

Price is a nasty little problem.  Price is not always &#039;master data&#039; in that there are different ways in which price is defined and managed.  For some firms there is a standard price which can be managed as if it were master data; for others it is a derived piece of data that does not exist until an order is placed; so the definition of the price can be treated as master data but the actual observation is not.  This makes for a good dialog with the business.  With agreement, progress can be made.  

Retail and how it works (or doesn&#039;t) with their suppliers is a real fertile ground for learning about why MDM is needed, and why it is so hard to achieve.  There are tons of politics, culture, technology, and processes barriers.  

I am seeing interest in retail again, post economic down turn, so hope springs eternal.</description>
		<content:encoded><![CDATA[<p>Hi John, thanks for the post.  I wish retailers really &#8220;got MDM&#8221;.  Certainly retailers have a great need; many have grown via acquisition and rarely spend the time or money rationalizing systems, processes, or data.  The average tenure of the CIO in retail is a lot shorter than for their supplier/partners so the level of &#8220;planning&#8221; remains much more short tern, tactical, or granular.</p>
<p>I have seen some activity, perhaps most, on &#8220;in-bound&#8221; product and related data from suppliers; some on &#8220;out-bound&#8221; multi-channel integration, and much less &#8220;enterprise&#8221; oriented to connect the other two to the rest of the business.  Also, too many business applications &#8211; and BI providers &#8211; maintain &#8220;master data&#8221; (or say they do) when in fact they don&#8217;t; they master application specific data that may or may not include a reference to master data.  This clouds the issue for many immature MDM program managers.</p>
<p>Price is a nasty little problem.  Price is not always &#8216;master data&#8217; in that there are different ways in which price is defined and managed.  For some firms there is a standard price which can be managed as if it were master data; for others it is a derived piece of data that does not exist until an order is placed; so the definition of the price can be treated as master data but the actual observation is not.  This makes for a good dialog with the business.  With agreement, progress can be made.  </p>
<p>Retail and how it works (or doesn&#8217;t) with their suppliers is a real fertile ground for learning about why MDM is needed, and why it is so hard to achieve.  There are tons of politics, culture, technology, and processes barriers.  </p>
<p>I am seeing interest in retail again, post economic down turn, so hope springs eternal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John G</title>
		<link>http://blogs.gartner.com/andrew_white/2008/12/02/retail-and-mdm/comment-page-1/#comment-119</link>
		<dc:creator>John G</dc:creator>
		<pubDate>Wed, 17 Jun 2009 06:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/andrew_white/?p=84#comment-119</guid>
		<description>MDM should be natural to retail when it comes to pricing. E.g. how does Walmart get prices to the stores? Specifically retailers that have different prices depending on location/rent etc.</description>
		<content:encoded><![CDATA[<p>MDM should be natural to retail when it comes to pricing. E.g. how does Walmart get prices to the stores? Specifically retailers that have different prices depending on location/rent etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boyd Dimmock</title>
		<link>http://blogs.gartner.com/andrew_white/2008/12/02/retail-and-mdm/comment-page-1/#comment-77</link>
		<dc:creator>Boyd Dimmock</dc:creator>
		<pubDate>Fri, 06 Mar 2009 17:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/andrew_white/?p=84#comment-77</guid>
		<description>I share your interest in Retailer&#039;s need for better data management and have seen some recent activity where a retailer is getting significant advantage from implementing a strategy around single view of data.  The initiative requires moving data out of it&#039;s silos where the same data exists in different forms.  I think the key to success is having the IT leaders and the Business leaders develop a common vision for the project. Usually this involves recogniziing both the added business value as well as the cost savings of managing too many data repositories.  
 
It also helps to find some of the leading industry vendors who do &quot;get it&quot; and are developing solutions that both consolidate departmental data, deduplicate the data, as well as aggregates and syndicates data with internal and external data sources.  Then the data becomes truly valuable for actionable merchandising decisions.</description>
		<content:encoded><![CDATA[<p>I share your interest in Retailer&#8217;s need for better data management and have seen some recent activity where a retailer is getting significant advantage from implementing a strategy around single view of data.  The initiative requires moving data out of it&#8217;s silos where the same data exists in different forms.  I think the key to success is having the IT leaders and the Business leaders develop a common vision for the project. Usually this involves recogniziing both the added business value as well as the cost savings of managing too many data repositories.  </p>
<p>It also helps to find some of the leading industry vendors who do &#8220;get it&#8221; and are developing solutions that both consolidate departmental data, deduplicate the data, as well as aggregates and syndicates data with internal and external data sources.  Then the data becomes truly valuable for actionable merchandising decisions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

