 <?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: Complex Event Processing: a technology evaluation check-list</title>
	<atom:link href="http://tibcoblogs.com/cep/index.php/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/</link>
	<description>Complex Event Processing (CEP)</description>
	<pubDate>Sat, 11 Feb 2012 22:10:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Vincent</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1152</link>
		<dc:creator>Paul Vincent</dc:creator>
		<pubDate>Thu, 26 Aug 2010 10:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1152</guid>
		<description>Thanks Keith - but we don't really want the TIBCO CEP blog comment system to be used to advertise other vendors' events!!! Nontheless, thanks for the invite and good luck.
Cheers</description>
		<content:encoded><![CDATA[<p>Thanks Keith - but we don&#8217;t really want the TIBCO CEP blog comment system to be used to advertise other vendors&#8217; events!!! Nontheless, thanks for the invite and good luck.<br />
Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Dunlop</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1150</link>
		<dc:creator>Keith Dunlop</dc:creator>
		<pubDate>Tue, 24 Aug 2010 21:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1150</guid>
		<description>Invitation to register for Sybase CEP Webinar on September 14th, 2010

...</description>
		<content:encoded><![CDATA[<p>Invitation to register for Sybase CEP Webinar on September 14th, 2010</p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Vincent</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1036</link>
		<dc:creator>Paul Vincent</dc:creator>
		<pubDate>Mon, 08 Mar 2010 23:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1036</guid>
		<description>Hi Tina: Thanks for the feedback:

- On "latency" and other performance metrics, of course everyone "has good performance" :). Then again, I didn't specify this was a "paper evaluation checklist" so although I should do a "software trial checklist" later I will add performance to the platform component of this list.

- I would map "application management" to "operations and management"; "impact analysis" / "auditability" map somewhat to verification and validation (see the earlier comment response to Hans and James...). On the other hand, it is up to end user organizations to assess their need here, so I will add that in under business interfaces.

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Tina: Thanks for the feedback:</p>
<p>- On &#8220;latency&#8221; and other performance metrics, of course everyone &#8220;has good performance&#8221; :). Then again, I didn&#8217;t specify this was a &#8220;paper evaluation checklist&#8221; so although I should do a &#8220;software trial checklist&#8221; later I will add performance to the platform component of this list.</p>
<p>- I would map &#8220;application management&#8221; to &#8220;operations and management&#8221;; &#8220;impact analysis&#8221; / &#8220;auditability&#8221; map somewhat to verification and validation (see the earlier comment response to Hans and James&#8230;). On the other hand, it is up to end user organizations to assess their need here, so I will add that in under business interfaces.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tina Groves</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1035</link>
		<dc:creator>Tina Groves</dc:creator>
		<pubDate>Mon, 08 Mar 2010 19:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1035</guid>
		<description>The criteria seems fairly complete though latency appears missing (implied in the scalability criteria?). I agree with Hans that capabilities related to application management such as impact analysis, auditability and so on warrant inclusion.  The scoring, as you say, is relative to the use case and, I would add, target environment.  "CEP Opportunity Analysis and Assessment" by IDC's Fleming and Silverstein (Dec 2008) does a nice job describing how priorities shift according to the use case.

Thanks for sharing.</description>
		<content:encoded><![CDATA[<p>The criteria seems fairly complete though latency appears missing (implied in the scalability criteria?). I agree with Hans that capabilities related to application management such as impact analysis, auditability and so on warrant inclusion.  The scoring, as you say, is relative to the use case and, I would add, target environment.  &#8220;CEP Opportunity Analysis and Assessment&#8221; by IDC&#8217;s Fleming and Silverstein (Dec 2008) does a nice job describing how priorities shift according to the use case.</p>
<p>Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Vincent</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1034</link>
		<dc:creator>Paul Vincent</dc:creator>
		<pubDate>Sun, 07 Mar 2010 22:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1034</guid>
		<description>Hi Hans, James: I would claim that "impact analysis" in Event Processing could be viewed as 2 different activities: 
- monitoring and prediction (what will happen downstream of incoming events) 
and 
- "what if" analysis of such monitoring and prediction (normally covered by "simulation" in CEP). 

The first (monitoring and prediction per se) is usually a pretty common CEP role. We are trying to predict what will happen based on event patterns occuring. Examples would be predicting electricity grid transformer failures, or manufacturing process quality test requirements (both TIBCO BusinessEvents use cases). I think the industry is at an early stage of providing "business tools" to handle the complexity of the development and specification of the temporal pattern logic required for CEP...  

The second, simulation, is "relatively easy" in simple use cases (like the test facilities in TIBCO BusinessEvents Decision Manager, and in many other BRMS tools), but likewise more difficult to achieve effectively for event sequences involving time and current state, especially for a business user. Indeed, outside of simple "event simulation" components in CEP tools, I'm not aware of any business suite that does this effectively today. Probably you would need to automate support for some technique like Combinatorial Testing. 

On the other hand, we do see occasions where test cases are generated by rules (and separate rules than those providing the CEP!) to try and provide good coverage - indeed this is used in some of the TIBCO BusinessEvents provided examples. Overall, test-based development and the use of techniques like event generators for testing I would consider as "best practices"!

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Hans, James: I would claim that &#8220;impact analysis&#8221; in Event Processing could be viewed as 2 different activities:<br />
- monitoring and prediction (what will happen downstream of incoming events)<br />
and<br />
- &#8220;what if&#8221; analysis of such monitoring and prediction (normally covered by &#8220;simulation&#8221; in CEP). </p>
<p>The first (monitoring and prediction per se) is usually a pretty common CEP role. We are trying to predict what will happen based on event patterns occuring. Examples would be predicting electricity grid transformer failures, or manufacturing process quality test requirements (both TIBCO BusinessEvents use cases). I think the industry is at an early stage of providing &#8220;business tools&#8221; to handle the complexity of the development and specification of the temporal pattern logic required for CEP&#8230;  </p>
<p>The second, simulation, is &#8220;relatively easy&#8221; in simple use cases (like the test facilities in TIBCO BusinessEvents Decision Manager, and in many other BRMS tools), but likewise more difficult to achieve effectively for event sequences involving time and current state, especially for a business user. Indeed, outside of simple &#8220;event simulation&#8221; components in CEP tools, I&#8217;m not aware of any business suite that does this effectively today. Probably you would need to automate support for some technique like Combinatorial Testing. </p>
<p>On the other hand, we do see occasions where test cases are generated by rules (and separate rules than those providing the CEP!) to try and provide good coverage - indeed this is used in some of the TIBCO BusinessEvents provided examples. Overall, test-based development and the use of techniques like event generators for testing I would consider as &#8220;best practices&#8221;!</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Vincent</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1033</link>
		<dc:creator>Paul Vincent</dc:creator>
		<pubDate>Sun, 07 Mar 2010 22:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1033</guid>
		<description>Hi Opher - thanks for the advice - yes, I will simplify this to just GVs (Global Variables) "etc" as there are many ways of doing a global context... 
Cheers</description>
		<content:encoded><![CDATA[<p>Hi Opher - thanks for the advice - yes, I will simplify this to just GVs (Global Variables) &#8220;etc&#8221; as there are many ways of doing a global context&#8230;<br />
Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1032</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Sat, 06 Mar 2010 14:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1032</guid>
		<description>Would you not say that impact analysis is highly dependent on the use case? Or is there a general kind of impact analysis that's not coming to my mind right now?</description>
		<content:encoded><![CDATA[<p>Would you not say that impact analysis is highly dependent on the use case? Or is there a general kind of impact analysis that&#8217;s not coming to my mind right now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1031</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Sat, 06 Mar 2010 01:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1031</guid>
		<description>Paul
A nice list but I think you are missing a key element in the business interface - impact analysis. Business users, in my experience, don't want to test or verify they want to see the impact of a potential change in business terms. 
JT</description>
		<content:encoded><![CDATA[<p>Paul<br />
A nice list but I think you are missing a key element in the business interface - impact analysis. Business users, in my experience, don&#8217;t want to test or verify they want to see the impact of a potential change in business terms.<br />
JT</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Opher Etzion</title>
		<link>http://tibcoblogs.com/cep/2010/03/04/complex-event-processing-a-technology-evaluation-check-list/comment-page-1/#comment-1030</link>
		<dc:creator>Opher Etzion</dc:creator>
		<pubDate>Fri, 05 Mar 2010 15:23:11 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=1155#comment-1030</guid>
		<description>Hi Paul.  Good work in collecting all criteria,  my main issue with scorecards that they are based on the assumption that there is a universal scoring,  as some of this criteria may or may not apply to certain application, also it is sometimes the case that an event processing system need hybrid of capabilities, and it is difficult to define exact scoring.  I believe that the way forward will be to apply a collection of building block that can easily work together so each customer can pick what it needs, and also extend without problem, as applications evolve. 

cheers,

Opher</description>
		<content:encoded><![CDATA[<p>Hi Paul.  Good work in collecting all criteria,  my main issue with scorecards that they are based on the assumption that there is a universal scoring,  as some of this criteria may or may not apply to certain application, also it is sometimes the case that an event processing system need hybrid of capabilities, and it is difficult to define exact scoring.  I believe that the way forward will be to apply a collection of building block that can easily work together so each customer can pick what it needs, and also extend without problem, as applications evolve. </p>
<p>cheers,</p>
<p>Opher</p>
]]></content:encoded>
	</item>
</channel>
</rss>

