<?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: Data Warehouse&#8230; Process Warehouse?</title>
	<atom:link href="http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/</link>
	<description>A Blog about Enterprise BPM and Business Process Improvement by the folks at BP3</description>
	<lastBuildDate>Sun, 12 Feb 2012 05:30:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tweets that mention Process for the Enterprise » Blog Archive » Data Warehouse… Process Warehouse? -- Topsy.com</title>
		<link>http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/comment-page-1/#comment-945</link>
		<dc:creator>Tweets that mention Process for the Enterprise » Blog Archive » Data Warehouse… Process Warehouse? -- Topsy.com</dc:creator>
		<pubDate>Tue, 24 Nov 2009 17:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1394#comment-945</guid>
		<description>[...] This post was mentioned on Twitter by Scott Francis, bp3 bpm. bp3 bpm said: Blog Post: Data Warehouse... Process Warehouse? http://bit.ly/71kDIn [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Scott Francis, bp3 bpm. bp3 bpm said: Blog Post: Data Warehouse&#8230; Process Warehouse? <a href="http://bit.ly/71kDIn" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/71kDIn?referer=');">http://bit.ly/71kDIn</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Francis</title>
		<link>http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/comment-page-1/#comment-944</link>
		<dc:creator>Scott Francis</dc:creator>
		<pubDate>Tue, 24 Nov 2009 17:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1394#comment-944</guid>
		<description>Cliff- 
thanks for the update - I think the new branding on Performance Server to &quot;Performance Data Warehouse&quot; is good, and overdue!  Glad to hear Lombardi is going to be investing substantially in it because it really is the key to unlocking interesting business process improvements.  

Of course, Process Warehouse is event simpler :) And use of the term &quot;data warehouse&quot; implies certain data warehouse functionality that may need to be adopted or incorporated along the lines of a pure data warehouse. Thx for the clarification, looking forward to more on that subject.</description>
		<content:encoded><![CDATA[<p>Cliff-<br />
thanks for the update &#8211; I think the new branding on Performance Server to &#8220;Performance Data Warehouse&#8221; is good, and overdue!  Glad to hear Lombardi is going to be investing substantially in it because it really is the key to unlocking interesting business process improvements.  </p>
<p>Of course, Process Warehouse is event simpler :) And use of the term &#8220;data warehouse&#8221; implies certain data warehouse functionality that may need to be adopted or incorporated along the lines of a pure data warehouse. Thx for the clarification, looking forward to more on that subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Francis</title>
		<link>http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/comment-page-1/#comment-4642</link>
		<dc:creator>Scott Francis</dc:creator>
		<pubDate>Tue, 24 Nov 2009 17:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1394#comment-4642</guid>
		<description>Cliff- 
thanks for the update - I think the new branding on Performance Server to &quot;Performance Data Warehouse&quot; is good, and overdue!  Glad to hear Lombardi is going to be investing substantially in it because it really is the key to unlocking interesting business process improvements.  

Of course, Process Warehouse is event simpler :) And use of the term &quot;data warehouse&quot; implies certain data warehouse functionality that may need to be adopted or incorporated along the lines of a pure data warehouse. Thx for the clarification, looking forward to more on that subject.</description>
		<content:encoded><![CDATA[<p>Cliff-<br />
thanks for the update &#8211; I think the new branding on Performance Server to &#8220;Performance Data Warehouse&#8221; is good, and overdue!  Glad to hear Lombardi is going to be investing substantially in it because it really is the key to unlocking interesting business process improvements.  </p>
<p>Of course, Process Warehouse is event simpler :) And use of the term &#8220;data warehouse&#8221; implies certain data warehouse functionality that may need to be adopted or incorporated along the lines of a pure data warehouse. Thx for the clarification, looking forward to more on that subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cliff Vars</title>
		<link>http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/comment-page-1/#comment-942</link>
		<dc:creator>Cliff Vars</dc:creator>
		<pubDate>Tue, 24 Nov 2009 16:59:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1394#comment-942</guid>
		<description>Scott - Thanks for another good post. You&#039;re right that Lombardi is already tracking process performance and usage in a warehouse-type model with the Performance Server. It has actually been re-branded as the Performance Data Warehouse in Teamworks 7 to better reflect and communicate to the market what it does, and we at Lombardi intend to push that message. In addition Lombardi continues to invest in this area, from easier ways to track process information to providing better ways to expose the information for consumption.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; Thanks for another good post. You&#8217;re right that Lombardi is already tracking process performance and usage in a warehouse-type model with the Performance Server. It has actually been re-branded as the Performance Data Warehouse in Teamworks 7 to better reflect and communicate to the market what it does, and we at Lombardi intend to push that message. In addition Lombardi continues to invest in this area, from easier ways to track process information to providing better ways to expose the information for consumption.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cliff Vars</title>
		<link>http://www.bp-3.com/blogs/2009/11/data-warehouse-process-warehouse/comment-page-1/#comment-4641</link>
		<dc:creator>Cliff Vars</dc:creator>
		<pubDate>Tue, 24 Nov 2009 16:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1394#comment-4641</guid>
		<description>Scott - Thanks for another good post. You&#039;re right that Lombardi is already tracking process performance and usage in a warehouse-type model with the Performance Server. It has actually been re-branded as the Performance Data Warehouse in Teamworks 7 to better reflect and communicate to the market what it does, and we at Lombardi intend to push that message. In addition Lombardi continues to invest in this area, from easier ways to track process information to providing better ways to expose the information for consumption.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; Thanks for another good post. You&#8217;re right that Lombardi is already tracking process performance and usage in a warehouse-type model with the Performance Server. It has actually been re-branded as the Performance Data Warehouse in Teamworks 7 to better reflect and communicate to the market what it does, and we at Lombardi intend to push that message. In addition Lombardi continues to invest in this area, from easier ways to track process information to providing better ways to expose the information for consumption.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

