<?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: Global Processes and Business Rules</title>
	<atom:link href="http://tynerblain.com/blog/2007/09/25/global-processes-and-business-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/09/25/global-processes-and-business-rules/</link>
	<description>Software product success.</description>
	<lastBuildDate>Fri, 12 Mar 2010 01:42:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/09/25/global-processes-and-business-rules/comment-page-1/#comment-158307</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sat, 29 Sep 2007 03:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/09/25/global-processes-and-business-rules/#comment-158307</guid>
		<description>Thanks James, I appreciate the insight.  As our current project evolves, I look forward to exploring this more!

Thanks also for the link to the case study.  I especially like the spider-graph in the full case study pdf.</description>
		<content:encoded><![CDATA[<p>Thanks James, I appreciate the insight.  As our current project evolves, I look forward to exploring this more!</p>
<p>Thanks also for the link to the case study.  I especially like the spider-graph in the full case study pdf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://tynerblain.com/blog/2007/09/25/global-processes-and-business-rules/comment-page-1/#comment-157488</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Thu, 27 Sep 2007 01:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/09/25/global-processes-and-business-rules/#comment-157488</guid>
		<description>Scott
You make a lot of good points. Indeed, when organizations are managing rules they face the same issues. Should I have standard rules and then local (or state or regional) overrides? Should I manage some sets of rules as completely independent sets across countries? Can I share some rules across multiple countries? Are there rules that MUST be shared? and so on.
There is no one right answer for this. Proper management of rules, particularly the details of production rules that execute in systems, requires a repository approach with versioning, audit trails and structure to allow appropriate management by decision, by country, by line of business etc. The business-friendly nature of rules helps regardless, but proper management really helps.
In general I think that a separate focus on decisions and on the rules behind those decisions makes it much more possible to use standard processes and outsourced processes while retaining differentiation (as I discussed &lt;a href=&quot;http://www.bpminstitute.org/articles/article/article/business-rules-and-resisting-the-commoditization-of-process.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. One example that comes to mind is Air Products, who found that having a single SAP instance for all their worldwide businesses could be confining but that decision management with business rules was an effective tool for injecting differentiation and localization. There&#039;s a case study &lt;a href=&quot;http://www.edmblog.com/weblog/2006/08/a_case_study_ru.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.
See you in Orlando!
JT
&lt;a href=&quot;http://www.ebizq.net/blogs/decision_management&quot; rel=&quot;nofollow&quot;&gt;My ebizQ blog&lt;/a&gt;
&lt;a href=&quot;http://www.smartenoughsystems.com&quot; rel=&quot;nofollow&quot;&gt;Author of Smart (Enough) Systems&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Scott<br />
You make a lot of good points. Indeed, when organizations are managing rules they face the same issues. Should I have standard rules and then local (or state or regional) overrides? Should I manage some sets of rules as completely independent sets across countries? Can I share some rules across multiple countries? Are there rules that MUST be shared? and so on.<br />
There is no one right answer for this. Proper management of rules, particularly the details of production rules that execute in systems, requires a repository approach with versioning, audit trails and structure to allow appropriate management by decision, by country, by line of business etc. The business-friendly nature of rules helps regardless, but proper management really helps.<br />
In general I think that a separate focus on decisions and on the rules behind those decisions makes it much more possible to use standard processes and outsourced processes while retaining differentiation (as I discussed <a href="http://www.bpminstitute.org/articles/article/article/business-rules-and-resisting-the-commoditization-of-process.html" rel="nofollow">here</a>. One example that comes to mind is Air Products, who found that having a single SAP instance for all their worldwide businesses could be confining but that decision management with business rules was an effective tool for injecting differentiation and localization. There&#8217;s a case study <a href="http://www.edmblog.com/weblog/2006/08/a_case_study_ru.html" rel="nofollow">here</a>.<br />
See you in Orlando!<br />
JT<br />
<a href="http://www.ebizq.net/blogs/decision_management" rel="nofollow">My ebizQ blog</a><br />
<a href="http://www.smartenoughsystems.com" rel="nofollow">Author of Smart (Enough) Systems</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
