<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Master Data Management Resource Guide</title>
	<atom:link href="http://www.mdmsource.com/weblog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mdmsource.com/weblog</link>
	<description>Resource Listing Weblog</description>
	<lastBuildDate>Tue, 02 Feb 2010 14:30:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>An Introduction to the Master Data Management Reference Architecture</title>
		<link>http://www.mdmsource.com/weblog/an-introduction-to-the-master-data-management-reference-architecture-2/</link>
		<comments>http://www.mdmsource.com/weblog/an-introduction-to-the-master-data-management-reference-architecture-2/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 12:00:59 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=182</guid>
		<description><![CDATA[A technical Resource that presents the concept of an MDM Reference Architecture as an integral tool in successful MDM implementations. From the Resource:
&#8220;The MDM Reference Architecture is an industry- and product-agnostic reference architecture that supports implementing the multiple methods of use (collaborative, operational, analytical) for MDM and multiple implementation styles (registry, coexistence, transaction style). It [...]]]></description>
			<content:encoded><![CDATA[<p>A technical Resource that presents the concept of an MDM Reference Architecture as an integral tool in successful MDM implementations. From the Resource:</p>
<p><em>&#8220;The MDM Reference Architecture is an industry- and product-agnostic reference architecture that supports implementing the multiple methods of use (collaborative, operational, analytical) for MDM and multiple implementation styles (registry, coexistence, transaction style). It enables the ability to design business solutions incorporating MDM capabilities.&#8221;</em></p>
<p>Resource: <a href="http://www.mdmsource.com/redirect.php?url=http://www.ibm.com/developerworks/db2/library/techarticle/dm-0804oberhofer/index.html?ca=drs-">An Introduction to the Master Data Management Reference Architecture</a></p>
<p>Source: Martin Oberhofer and Allen Dreibelbis, IBM</p>
<p>MDM Governance Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-tips-best-practices.html">Master Data Management Best Practices</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/an-introduction-to-the-master-data-management-reference-architecture-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Master Data Management &#8211; What is it?: Dow&#039;s Master Data Management Business Processes</title>
		<link>http://www.mdmsource.com/weblog/master-data-management-what-is-it-dows-master-data-management-business-processes-2/</link>
		<comments>http://www.mdmsource.com/weblog/master-data-management-what-is-it-dows-master-data-management-business-processes-2/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 13:19:07 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=194</guid>
		<description><![CDATA[Master Data Management Defined: MDM is a set of disciplines, technologies, and solutions used to create and maintain consistent, complete, contextual and accurate business data for all stakeholders (users, and applications) across and beyond the enterprise.
Resource: Dow&#8217;s Master Data Management Business Processes &#124; PDF
Source: Jim Whyte, Dow Chemical
MDM Governance Resource Guide Section: Master Data Management [...]]]></description>
			<content:encoded><![CDATA[<p>Master Data Management Defined: MDM is a set of disciplines, technologies, and solutions used to create and maintain consistent, complete, contextual and accurate business data for all stakeholders (users, and applications) across and beyond the enterprise.</p>
<p>Resource: <a href="http://www.americanchemistry.com/s_chemitc/doc.asp?cid=1681&amp;did=6541">Dow&#8217;s Master Data Management Business Processes</a> | PDF</p>
<p>Source: Jim Whyte, Dow Chemical</p>
<p>MDM Governance Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-defined.html">Master Data Management &#8211; What is it?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/master-data-management-what-is-it-dows-master-data-management-business-processes-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Master Data Management Benefits</title>
		<link>http://www.mdmsource.com/weblog/master-data-management-benefits-master-data-management-2/</link>
		<comments>http://www.mdmsource.com/weblog/master-data-management-benefits-master-data-management-2/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 12:10:08 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=184</guid>
		<description><![CDATA[&#8220;An MDM layer enables companies to realize internal efficiencies by reducing the cost and complexity of processes that use master data (through fewer code clashes, less data duplication, better control over business processes, and so on). It reduces manual translation and analysis to improve repeatability and speed to insight. An MDM layer improves the ability [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;An MDM layer enables companies to realize internal efficiencies by reducing the cost and complexity of processes that use master data (through fewer code clashes, less data duplication, better control over business processes, and so on). It reduces manual translation and analysis to improve repeatability and speed to insight. An MDM layer improves the ability to share, consolidate, and analyze business information quickly, both globally and regionally. And it makes it possible to rapidly assemble new, composite applications (software that combines the elements of a business activity in a coordinated application and user interface) out of accurate master information and reusable business processes. Other MDM benefits include increased revenue (for example, from providing more accurate and comprehensive information to the right customers at point of sale) and regulatory compliance.&#8221;</p>
<p>Resource: <a href="http://www.mdmsource.com/redirect.php?url=http://www.dbmag.intelligententerprise.com/story/showArticle.jhtml?articleID=167100925">Master Data Management</a></p>
<p>Source: Daniel Druker and Robert Rich, IBM Database Magazine</p>
<p>MDM Governance Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-benefits.html">Master Data Management Benefits</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/master-data-management-benefits-master-data-management-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Four Signs of Bad Data</title>
		<link>http://www.mdmsource.com/weblog/four-signs-of-bad-data/</link>
		<comments>http://www.mdmsource.com/weblog/four-signs-of-bad-data/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 12:00:42 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=246</guid>
		<description><![CDATA[Four signs of bad data:
1) Discrepancies: duplicates and obsoletes have crept in swelling the inventory size above the expected level.
2) Items are difficult to find: trouble locating the right item. Even suppliers can&#8217;t locate them with the given information.
3) More non-contract spend: they can&#8217;t be located here, so go get them at expensive off-contract price.
4) [...]]]></description>
			<content:encoded><![CDATA[<p>Four signs of bad data:</p>
<p>1) Discrepancies: duplicates and obsoletes have crept in swelling the inventory size above the expected level.<br />
2) Items are difficult to find: trouble locating the right item. Even suppliers can&#8217;t locate them with the given information.<br />
3) More non-contract spend: they can&#8217;t be located here, so go get them at expensive off-contract price.<br />
4) Spend is out of control: Many invoices from suppliers do not match to POs.</p>
<p>Source: Krishna Shastry, Grihasoft</p>
<p>MDM Governance Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-tips-best-practices.html">Master Data Management Best Practices</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/four-signs-of-bad-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Master Data Management Best Practices: Seven Master Data Management Best Practices</title>
		<link>http://www.mdmsource.com/weblog/master-data-management-best-practices-seven-master-data-management-best-practices-2/</link>
		<comments>http://www.mdmsource.com/weblog/master-data-management-best-practices-seven-master-data-management-best-practices-2/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 12:11:46 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=187</guid>
		<description><![CDATA[A review of best practices gathered from five enterprises who have successfully deployed MDM. While a bit topical, the guidance is sound. The best practices:
1. Get business involved &#8212; or in charge.
2. Allow ample time for evaluation and planning.
3. Have a big vision, but take small steps.
4. Consider potential performance problems.
5. Institute data governance policies [...]]]></description>
			<content:encoded><![CDATA[<p>A review of best practices gathered from five enterprises who have successfully deployed MDM. While a bit topical, the guidance is sound. The best practices:</p>
<p>1. Get business involved &#8212; or in charge.<br />
2. Allow ample time for evaluation and planning.<br />
3. Have a big vision, but take small steps.<br />
4. Consider potential performance problems.<br />
5. Institute data governance policies and processes.<br />
6. Carefully plan deployment.<br />
7. Consider the transition plan.</p>
<p>Resource: <a href="http://searchsap.techtarget.com/news/article/0,289142,sid21_gci1219185,00.html">Seven Master Data Management Best Practices</a></p>
<p>Source: Hannah Smalltree, SearchCIO.com</p>
<p>MDM Governance Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-tips-best-practices.html">Master Data Management Best Practices</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/master-data-management-best-practices-seven-master-data-management-best-practices-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No Data Left Behind: Federal Student Aid A Case History</title>
		<link>http://www.mdmsource.com/weblog/no-data-left-behind-federal-student-aid-a-case-history-2/</link>
		<comments>http://www.mdmsource.com/weblog/no-data-left-behind-federal-student-aid-a-case-history-2/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 14:00:42 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=249</guid>
		<description><![CDATA[A detailed look at the US Department of Education&#8217;s Enterprise Data Management project, including project objectives, business drivers, architecture and much more. From the Resource:
&#8220;EDM is a service to the business with the following goals: Support the improvement of enterprise analytics and Decrease the cost of and improve the quality of new development projects Focus [...]]]></description>
			<content:encoded><![CDATA[<p>A detailed look at the US Department of Education&#8217;s Enterprise Data Management project, including project objectives, business drivers, architecture and much more. From the Resource:</p>
<p><em>&#8220;EDM is a service to the business with the following goals: Support the improvement of enterprise analytics and Decrease the cost of and improve the quality of new development projects Focus on data as an enterprise asset.&#8221;</em></p>
<p>Link to Resource: <a href="http://www.mdmsource.com/redirect.php?url=http://www.dama-ncr.org/Library/2008-03-11NoDataLeftBehind.ppt">No Data Left Behind: Federal Student Aid A Case History</a> | PowerPoint Presentation</p>
<p>Source: Holly Hyland &amp; Lisa Elliott, US Department of Education</p>
<p>MDM Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-case-studies.html">Master Data Management User Scenarios and Success Stories</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/no-data-left-behind-federal-student-aid-a-case-history-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Content Data ROI Issues</title>
		<link>http://www.mdmsource.com/weblog/content-data-roi-issues-2/</link>
		<comments>http://www.mdmsource.com/weblog/content-data-roi-issues-2/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 13:00:43 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=247</guid>
		<description><![CDATA[According to a report prepared by industry consultants A.T. Kearney, bad data leads to a host of corporate problems:
1- Companies lose approximately $40 billion, or 3.5% of sales, each year because of supply chain information inefficiencies.
2- Nearly 30% of the item data in catalogs used by retailers and manufacturers is incorrect. Correcting those errors costs [...]]]></description>
			<content:encoded><![CDATA[<p>According to a report prepared by industry consultants A.T. Kearney, bad data leads to a host of corporate problems:</p>
<p>1- Companies lose approximately $40 billion, or 3.5% of sales, each year because of supply chain information inefficiencies.<br />
2- Nearly 30% of the item data in catalogs used by retailers and manufacturers is incorrect. Correcting those errors costs between $60 and $80 each.<br />
3- Nearly 60% of all invoices generated have errors; each invoice error costs enterprises from $40 to $400 to reconcile.<br />
4- 43% of all invoices result in some form of deduction.<br />
5- New product rollouts take an average of four weeks-in large part because of inefficient and error-prone approaches for exchanging and updating new item attributes in buyer and seller systems.</p>
<p>Link to Resource: <a href="http://www.bytemanagers.com/ROI_d.asp?Id=60">Content Data ROI Issues</a></p>
<p>Source: A.T. Kearney</p>
<p>MDM Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-data-stats.html">Master Data Management &#8211; Data and Stats</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/content-data-roi-issues-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enterprise Data Management Optimization</title>
		<link>http://www.mdmsource.com/weblog/enterprise-data-management-optimization-2/</link>
		<comments>http://www.mdmsource.com/weblog/enterprise-data-management-optimization-2/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 12:00:33 +0000</pubDate>
		<dc:creator>MDMSOURCE</dc:creator>
				<category><![CDATA[MDMSOURCE]]></category>

		<guid isPermaLink="false">http://mdmsource.com/weblog/?p=251</guid>
		<description><![CDATA[As part of a deep, technical and incredibly well-crafted presentation on Enterprise Data Management, the author looks at the performance implications of supporting Centralized MDM vs. distributed repositories for MDM. From the Resource:
&#8220;Factors that require evaluation during planning Master Data Store: Hub vs. Spoke, Data Volumes, Data Volatility (frequency of changes), Data Timeliness, Query Volatility [...]]]></description>
			<content:encoded><![CDATA[<p>As part of a deep, technical and incredibly well-crafted presentation on Enterprise Data Management, the author looks at the performance implications of supporting Centralized MDM vs. distributed repositories for MDM. From the Resource:</p>
<p><em>&#8220;Factors that require evaluation during planning Master Data Store: Hub vs. Spoke, Data Volumes, Data Volatility (frequency of changes), Data Timeliness, Query Volatility (% of ad hoc queries), Query Complexity, Cross Functionality, and User Concurrency.&#8221; See Slide 37 and be sure to read the speakers notes for additional MDM insights.&#8221;</em></p>
<p>Link to Resource: <a href="http://www.mdmsource.com/redirect.php?url=http://regions.cmg.org/regions/stlcmg/files/Download/Presentations_2008-02/St%20Louis%20CMG%20Enterprise%20Data%20Management%20Optimization%20February%2012%202008.ppt">Enterprise Data Management Optimization</a> [8MB PowerPoint Presentation]</p>
<p>Source: Dr. Boris Zibitsker, BEZ Systems</p>
<p>MDM Resource Guide Section: <a href="http://www.mdmsource.com/master-data-management-tips-best-practices.html">Master Data Management Best Practices</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.mdmsource.com/weblog/enterprise-data-management-optimization-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
