<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Human Element in Identity Resolution</title>
	<link>http://identityresolutiondaily.com/473/the-human-element-in-identity-resolution/</link>
	<description>All About Identity and Entity Resolution</description>
	<pubDate>Sat, 11 Feb 2012 19:00:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Dan Nicollet</title>
		<link>http://identityresolutiondaily.com/473/the-human-element-in-identity-resolution/#comment-625</link>
		<author>Dan Nicollet</author>
		<pubDate>Mon, 23 Feb 2009 23:02:05 +0000</pubDate>
		<guid>http://identityresolutiondaily.com/473/the-human-element-in-identity-resolution/#comment-625</guid>
		<description>Agree with you 100% Bob.  

I was chatting with Ed Alburn from DataDelta about this very subject this last Friday.  His company evaluates data matching engines and data resolution solutions as a third party consultancy using advanced software he has developed throughout his 20y+ career at IBM and other enterprise software vendors and users.  So many users tend to expect that the value is 100% in good or bad software automation and so many vendors promise these sorts of pies in the sky very easily.  Ed reports that most of the time he manages to prove to his customers (data matching software users) that much of the work of automating their business processes needs to start among their own people (not the vendors) by asking them simple questions like: "what is a good match for this query?" and showing how different people, functions, divisions within their organizations have totally different answer to that question.  

In fact, "single view" or master data is all about uncovering that conflict of views of data across the organization: a combination of different meanings, representations, and uses for the same data.  The system can streamline the problem if knows where it lies.  Software can then be configured and maintained with that knowledge from the start.  Data governance and stewardship processes then need to be created to maintain that smooth ride to the never ending finish line.  

Our job as software vendors is to make that possible by providing the engagement methodologies, the technical facilities, and the performance to make it all possible.</description>
		<content:encoded><![CDATA[<p>Agree with you 100% Bob.  </p>
<p>I was chatting with Ed Alburn from DataDelta about this very subject this last Friday.  His company evaluates data matching engines and data resolution solutions as a third party consultancy using advanced software he has developed throughout his 20y+ career at IBM and other enterprise software vendors and users.  So many users tend to expect that the value is 100% in good or bad software automation and so many vendors promise these sorts of pies in the sky very easily.  Ed reports that most of the time he manages to prove to his customers (data matching software users) that much of the work of automating their business processes needs to start among their own people (not the vendors) by asking them simple questions like: &#8220;what is a good match for this query?&#8221; and showing how different people, functions, divisions within their organizations have totally different answer to that question.  </p>
<p>In fact, &#8220;single view&#8221; or master data is all about uncovering that conflict of views of data across the organization: a combination of different meanings, representations, and uses for the same data.  The system can streamline the problem if knows where it lies.  Software can then be configured and maintained with that knowledge from the start.  Data governance and stewardship processes then need to be created to maintain that smooth ride to the never ending finish line.  </p>
<p>Our job as software vendors is to make that possible by providing the engagement methodologies, the technical facilities, and the performance to make it all possible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

