<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Silver Creek Systems</title>
	<atom:link href="http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 08:38:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Silver Creek Systems Acquired by Oracle &#171; Hub Designs Blog</title>
		<link>http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/#comment-2380</link>
		<dc:creator><![CDATA[Silver Creek Systems Acquired by Oracle &#171; Hub Designs Blog]]></dc:creator>
		<pubDate>Tue, 05 Jan 2010 04:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=1030#comment-2380</guid>
		<description><![CDATA[[...] first profiled Silver Creek in April 2009, and my first hunch that they might end up getting acquired by Oracle came with the announcement [...]]]></description>
		<content:encoded><![CDATA[<p>[...] first profiled Silver Creek in April 2009, and my first hunch that they might end up getting acquired by Oracle came with the announcement [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Power</title>
		<link>http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/#comment-1911</link>
		<dc:creator><![CDATA[Dan Power]]></dc:creator>
		<pubDate>Fri, 15 May 2009 14:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=1030#comment-1911</guid>
		<description><![CDATA[Thanks for the great comment, Martin - and for pointing out how Silver Creek&#039;s DataLens handles the difficult scenarios that come up when dealing with product data.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the great comment, Martin &#8211; and for pointing out how Silver Creek&#8217;s DataLens handles the difficult scenarios that come up when dealing with product data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Boyd</title>
		<link>http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/#comment-1910</link>
		<dc:creator><![CDATA[Martin Boyd]]></dc:creator>
		<pubDate>Thu, 14 May 2009 22:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=1030#comment-1910</guid>
		<description><![CDATA[Preston,

As you obviously know, inadequate information is a common problem in product data.  In some cases all the information you need is right there in the record and just has to be extracted and standardized - and the DataLens System has world-leading capabilities in that regard.  However in many cases the data has significat &#039;holes&#039; in it.  In this case the DataLens System has a couple of alternatives;

1) Data can be extracted from external data sources and used to enrich the target record.  The DataLens System can pull data frm any external source, legacy system, subscription feed etc.  Differently fotmatted/standrdized information is not a problem ans the DataLens System can extract and transform it as part of the operation.  

2) If no electonic information is availbale at all, product records will be flagged as exceptions and sent ot the Governance Studio which is a dedicated interface for data stewards/product specialists to interact directly with the data and enter missing pieces of information.  It is even posible to direct these exceptions to external contractors (such as India-based services that can fill-in the gaps - typically at a much lower cost than if the had to work on the whole record)

Product data is notoriously messy and even the best automation cannot create something out of nothing, however the DataLens System is built from the ground up to deal with these issues and provides a great set of efficient workarounds.  No matter the approach you take, you are likely to have a much more cost-effective result than with the traditional altrenatives.

- Martin Boyd,  Silver Creek Systems]]></description>
		<content:encoded><![CDATA[<p>Preston,</p>
<p>As you obviously know, inadequate information is a common problem in product data.  In some cases all the information you need is right there in the record and just has to be extracted and standardized &#8211; and the DataLens System has world-leading capabilities in that regard.  However in many cases the data has significat &#8216;holes&#8217; in it.  In this case the DataLens System has a couple of alternatives;</p>
<p>1) Data can be extracted from external data sources and used to enrich the target record.  The DataLens System can pull data frm any external source, legacy system, subscription feed etc.  Differently fotmatted/standrdized information is not a problem ans the DataLens System can extract and transform it as part of the operation.  </p>
<p>2) If no electonic information is availbale at all, product records will be flagged as exceptions and sent ot the Governance Studio which is a dedicated interface for data stewards/product specialists to interact directly with the data and enter missing pieces of information.  It is even posible to direct these exceptions to external contractors (such as India-based services that can fill-in the gaps &#8211; typically at a much lower cost than if the had to work on the whole record)</p>
<p>Product data is notoriously messy and even the best automation cannot create something out of nothing, however the DataLens System is built from the ground up to deal with these issues and provides a great set of efficient workarounds.  No matter the approach you take, you are likely to have a much more cost-effective result than with the traditional altrenatives.</p>
<p>- Martin Boyd,  Silver Creek Systems</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Power</title>
		<link>http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/#comment-1869</link>
		<dc:creator><![CDATA[Dan Power]]></dc:creator>
		<pubDate>Thu, 23 Apr 2009 17:57:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=1030#comment-1869</guid>
		<description><![CDATA[Hi Preston, 

With regard to Product MDM, I think there are going to be some situations where an automated engine like Silver Creek&#039;s DataLens is going to be able to handle it, and then there will be exceptions that the engine can&#039;t handle that will have to be routed to a data steward in the business, who may have to research the situation further and then update/correct the product master data. So if things can&#039;t be imputed or calculated from other attributes, old fashioned human research is definitely needed. 

Best regards --- Dan]]></description>
		<content:encoded><![CDATA[<p>Hi Preston, </p>
<p>With regard to Product MDM, I think there are going to be some situations where an automated engine like Silver Creek&#8217;s DataLens is going to be able to handle it, and then there will be exceptions that the engine can&#8217;t handle that will have to be routed to a data steward in the business, who may have to research the situation further and then update/correct the product master data. So if things can&#8217;t be imputed or calculated from other attributes, old fashioned human research is definitely needed. </p>
<p>Best regards &#8212; Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preston</title>
		<link>http://hubdesignsmagazine.com/2009/04/13/silver-creek-systems/#comment-1868</link>
		<dc:creator><![CDATA[Preston]]></dc:creator>
		<pubDate>Thu, 23 Apr 2009 17:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=1030#comment-1868</guid>
		<description><![CDATA[Dan, we spoke on the phone about a month ago. In regard specifically to product data for MDM, any comments on the ability of automated solutions such as Silver Creek&#039;s to deal with the issue of inadequate attributes? In other words what is to be done if the existing descriptions in various fields do not contain all the information necessary for the parsing engine to populate the appropriate attribute fields? What do you see as the appropriate interplay between automated solutions such as DataLens and subject matter expertise-based manual solutions?]]></description>
		<content:encoded><![CDATA[<p>Dan, we spoke on the phone about a month ago. In regard specifically to product data for MDM, any comments on the ability of automated solutions such as Silver Creek&#8217;s to deal with the issue of inadequate attributes? In other words what is to be done if the existing descriptions in various fields do not contain all the information necessary for the parsing engine to populate the appropriate attribute fields? What do you see as the appropriate interplay between automated solutions such as DataLens and subject matter expertise-based manual solutions?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

