<?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: Estimating the Benefits of MDM</title>
	<atom:link href="http://masteringdatamanagement.com/index.php/2010/02/23/estimating-the-benefits-of-mdm/feed/" rel="self" type="application/rss+xml" />
	<link>http://masteringdatamanagement.com/index.php/2010/02/23/estimating-the-benefits-of-mdm/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 21:34:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Lawrence Dubov</title>
		<link>http://masteringdatamanagement.com/index.php/2010/02/23/estimating-the-benefits-of-mdm/comment-page-1/#comment-1861</link>
		<dc:creator>Lawrence Dubov</dc:creator>
		<pubDate>Fri, 26 Feb 2010 21:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.initiate.com/?p=1398#comment-1861</guid>
		<description>Jackie,

I totally agree that departmental focus and acceptance are important.

Cost avoidance can be estimated in a number of ways. The most widely adopted method is thru

•	SLE is the single loss expectancy (expressed as the monetary value of the loss).
•	ARO is the annualized rate of occurrence.
•	ALE is the annualized loss expectancy.
Using these variables we can define the following expression for cost avoidance calculations:
ALE = SLE x ARO.

You will need to understand business process to estimate these parameters. 

That said, you have to keep in mind that a lot of effort can be spent to evaluate cost avoidance for multiple processes. If a business process involves, let&#039;s say 5 FTE&#039;s and after the MDM implementation you will be able to make it 4 FTE&#039;s, 1 FTE is not a huge saving on the budgetary scale typical for enterprise MDM implementations to justify too much time on quantifying cost avoidance. You don&#039;t want to overanalyze a process that may give you 35-40k annually in cost avoidance. You need something more substantial. Everything counts though! 

You may want to look for bigger economic impacts thru new revenue opportunities.

Thanks,
Larry</description>
		<content:encoded><![CDATA[<p>Jackie,</p>
<p>I totally agree that departmental focus and acceptance are important.</p>
<p>Cost avoidance can be estimated in a number of ways. The most widely adopted method is thru</p>
<p>•	SLE is the single loss expectancy (expressed as the monetary value of the loss).<br />
•	ARO is the annualized rate of occurrence.<br />
•	ALE is the annualized loss expectancy.<br />
Using these variables we can define the following expression for cost avoidance calculations:<br />
ALE = SLE x ARO.</p>
<p>You will need to understand business process to estimate these parameters. </p>
<p>That said, you have to keep in mind that a lot of effort can be spent to evaluate cost avoidance for multiple processes. If a business process involves, let's say 5 FTE's and after the MDM implementation you will be able to make it 4 FTE's, 1 FTE is not a huge saving on the budgetary scale typical for enterprise MDM implementations to justify too much time on quantifying cost avoidance. You don't want to overanalyze a process that may give you 35-40k annually in cost avoidance. You need something more substantial. Everything counts though! </p>
<p>You may want to look for bigger economic impacts thru new revenue opportunities.</p>
<p>Thanks,<br />
Larry</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jackie Roberts</title>
		<link>http://masteringdatamanagement.com/index.php/2010/02/23/estimating-the-benefits-of-mdm/comment-page-1/#comment-1856</link>
		<dc:creator>Jackie Roberts</dc:creator>
		<pubDate>Fri, 26 Feb 2010 20:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.initiate.com/?p=1398#comment-1856</guid>
		<description>Lawrence,
This is an excellent subject and I will enjoy reading the sequels of &quot;Estimating the Benefits of MDM&quot;. To add more complexity to quantitative (hard savings) and qualitative (soft savings) I find that if you are building the benefits model, you need to incorporate departmental focus. For instance within supply chain / purchasing  hard savings are easily documented for a reduction of duplicates records in the system or a reduction of suppliers that sell the same item permitting the buyer to negotiate a cost savings base of volume. A MDM solution benefit for a maintenance focus would be the &quot;right part, at the right time&quot; or a functional spare part identified as part of the data governance structure to minimize down time of a manufacturing line. How is a cost avoidance number estimated in this scenario?</description>
		<content:encoded><![CDATA[<p>Lawrence,<br />
This is an excellent subject and I will enjoy reading the sequels of "Estimating the Benefits of MDM". To add more complexity to quantitative (hard savings) and qualitative (soft savings) I find that if you are building the benefits model, you need to incorporate departmental focus. For instance within supply chain / purchasing  hard savings are easily documented for a reduction of duplicates records in the system or a reduction of suppliers that sell the same item permitting the buyer to negotiate a cost savings base of volume. A MDM solution benefit for a maintenance focus would be the "right part, at the right time" or a functional spare part identified as part of the data governance structure to minimize down time of a manufacturing line. How is a cost avoidance number estimated in this scenario?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garnie Bolling</title>
		<link>http://masteringdatamanagement.com/index.php/2010/02/23/estimating-the-benefits-of-mdm/comment-page-1/#comment-1791</link>
		<dc:creator>Garnie Bolling</dc:creator>
		<pubDate>Wed, 24 Feb 2010 23:51:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.initiate.com/?p=1398#comment-1791</guid>
		<description>Lawrence, I look forward to this thread. 

Bottom up and Economic Value evaluations have always played a pivotal role in large initiatives like MDM.  

What is your thought on the hybrid approach of the two methods ?  you said, &quot;here is no wall between qualitative and quantitative benefits.&quot;  In your opinion, has a hybrid approach worked ?  and is there a benefit in doing both evaluations, and presenting the &quot;value&quot; from both angles ? 

I see value in both evaluation methods, but can a mix of the two really help business leaders latch on to the message and take ownership, or will it only confuse the business, in that &quot;no matter which way you implement MDM, you will have benefits&quot;...in my experience, if every avenue of approach is beneficial, it has always stalled the momentum... because there is no clear path... 

Thanks again, and I look forward to your future posts.. always good to read your posts.</description>
		<content:encoded><![CDATA[<p>Lawrence, I look forward to this thread. </p>
<p>Bottom up and Economic Value evaluations have always played a pivotal role in large initiatives like MDM.  </p>
<p>What is your thought on the hybrid approach of the two methods ?  you said, "here is no wall between qualitative and quantitative benefits."  In your opinion, has a hybrid approach worked ?  and is there a benefit in doing both evaluations, and presenting the "value" from both angles ? </p>
<p>I see value in both evaluation methods, but can a mix of the two really help business leaders latch on to the message and take ownership, or will it only confuse the business, in that "no matter which way you implement MDM, you will have benefits"...in my experience, if every avenue of approach is beneficial, it has always stalled the momentum... because there is no clear path... </p>
<p>Thanks again, and I look forward to your future posts.. always good to read your posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://masteringdatamanagement.com/index.php/2010/02/23/estimating-the-benefits-of-mdm/comment-page-1/#comment-1764</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Wed, 24 Feb 2010 11:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.initiate.com/?p=1398#comment-1764</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by faropress: Reading Larry Dubov on Estimating the Benefits of MDM - http://bit.ly/bUGIhZ - #MDM (via @Initiate)...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post...</strong></p>
<p>This post was mentioned on Twitter by faropress: Reading Larry Dubov on Estimating the Benefits of MDM - <a href="http://bit.ly/bUGIhZ" rel="nofollow">http://bit.ly/bUGIhZ</a> - #MDM (via @Initiate)...</p>
]]></content:encoded>
	</item>
</channel>
</rss>

