<?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: ERP shouldn&#8217;t do talent</title>
	<atom:link href="http://www.successfactors.com/blogs/business-execution/erp-shouldnt-do-talent/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.successfactors.com/blogs/business-execution/erp-shouldnt-do-talent/</link>
	<description>Execution is the Difference.</description>
	<lastBuildDate>Thu, 04 Feb 2010 07:42:47 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Doubledubs</title>
		<link>http://www.successfactors.com/blogs/business-execution/erp-shouldnt-do-talent/comment-page-1/#comment-62</link>
		<dc:creator>Doubledubs</dc:creator>
		<pubDate>Fri, 27 Jan 2006 22:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://10.50.0.97/wordpress/workforce-performance/index.php/erp-shouldnt-do-talent/#comment-62</guid>
		<description>Max, I&#039;ve been trying to decide on agreeing or disagreeing with this post.  Since I can&#039;t decide, I&#039;ll do neither.

We&#039;re at a wonderful place with technology.  In the early 90&#039;s, you had to depend on some pretty bad interface mechanisms if you didn&#039;t want to have a single ERP.  Recruiting and other systems like performance or payroll were barely integrated at all.  Then we got more sophisitcated and at least systems started talking to each other in the mid-90&#039;s.

Today, with web services, you can find the best in class solitions for every part of the HR technology market and (if the applications are up to W3C standards) hook everything together real time and fairly seamlessly.

I&#039;m not going to say that centralized single database is dead.  However, It&#039;s a whole lot easier to have SAP as a central repository, but also have apps like SuccessFactors all providing a single view of the organization for decision support.</description>
		<content:encoded><![CDATA[<p>Max, I&#8217;ve been trying to decide on agreeing or disagreeing with this post.  Since I can&#8217;t decide, I&#8217;ll do neither.</p>
<p>We&#8217;re at a wonderful place with technology.  In the early 90&#8217;s, you had to depend on some pretty bad interface mechanisms if you didn&#8217;t want to have a single ERP.  Recruiting and other systems like performance or payroll were barely integrated at all.  Then we got more sophisitcated and at least systems started talking to each other in the mid-90&#8217;s.</p>
<p>Today, with web services, you can find the best in class solitions for every part of the HR technology market and (if the applications are up to W3C standards) hook everything together real time and fairly seamlessly.</p>
<p>I&#8217;m not going to say that centralized single database is dead.  However, It&#8217;s a whole lot easier to have SAP as a central repository, but also have apps like SuccessFactors all providing a single view of the organization for decision support.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
