 <?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: CEP and the alphabet soup (Part 3): BAM !</title>
	<atom:link href="http://tibcoblogs.com/cep/index.php/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/feed/" rel="self" type="application/rss+xml" />
	<link>http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/</link>
	<description>Complex Event Processing (CEP)</description>
	<pubDate>Wed, 17 Mar 2010 20:49:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 2nd Generation SOA = EDA + CEP? &#187; TIBCOâ€™s Complex Event Processing Blog</title>
		<link>http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/comment-page-1/#comment-65</link>
		<dc:creator>2nd Generation SOA = EDA + CEP? &#187; TIBCOâ€™s Complex Event Processing Blog</dc:creator>
		<pubDate>Thu, 29 Nov 2007 00:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/#comment-65</guid>
		<description>[...] SOA gives the ability to specify services that can be used synchronously or asynchronously. They will tend to be orchestrated as part of a BPM process; more complex services may require a specific event-driven choreography [2]. Some advanced SOA architectures even give you features like service virtualization. But for the most part, SOA is associated with BPM and sequential human-oriented procedural services. One of the themes of the CEP industry is that IT systems don&#8217;t need to work like that, especially for large-scale real-time automation tasks where necessarily the human-is-not-in-the-loop. This is where EDA and CEP come into play, dealing with asynchronous and complex events and their associated patterns. One use case for this is obviously Business Activity Monitoring (keeping track, automatically, of the relevant Key Performance Indicators or KPIs). [...]</description>
		<content:encoded><![CDATA[<p>[...] SOA gives the ability to specify services that can be used synchronously or asynchronously. They will tend to be orchestrated as part of a BPM process; more complex services may require a specific event-driven choreography [2]. Some advanced SOA architectures even give you features like service virtualization. But for the most part, SOA is associated with BPM and sequential human-oriented procedural services. One of the themes of the CEP industry is that IT systems don&#8217;t need to work like that, especially for large-scale real-time automation tasks where necessarily the human-is-not-in-the-loop. This is where EDA and CEP come into play, dealing with asynchronous and complex events and their associated patterns. One use case for this is obviously Business Activity Monitoring (keeping track, automatically, of the relevant Key Performance Indicators or KPIs). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CEP as sauce for alphabet soup (Part 8): MDM &#187; TIBCOâ€™s Complex Event Processing Blog</title>
		<link>http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/comment-page-1/#comment-25</link>
		<dc:creator>CEP as sauce for alphabet soup (Part 8): MDM &#187; TIBCOâ€™s Complex Event Processing Blog</dc:creator>
		<pubDate>Fri, 20 Jul 2007 02:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/#comment-25</guid>
		<description>[...] As can be seen above (diagram courtesy of the TIBCO CIM [*2] team), MDM plays a role in general process automation, analytics, and reporting. So one can envisage where CEP plays in the BAM, BPM and BI spaces to suggest changes to master data, which may (or may not) need manual verification within an MDM workflow, depending on the compliance rules and corporate procedures in place&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] As can be seen above (diagram courtesy of the TIBCO CIM [*2] team), MDM plays a role in general process automation, analytics, and reporting. So one can envisage where CEP plays in the BAM, BPM and BI spaces to suggest changes to master data, which may (or may not) need manual verification within an MDM workflow, depending on the compliance rules and corporate procedures in place&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Decision Management and CEP &#187; TIBCOâ€™s Complex Event Processing Blog</title>
		<link>http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/comment-page-1/#comment-24</link>
		<dc:creator>Decision Management and CEP &#187; TIBCOâ€™s Complex Event Processing Blog</dc:creator>
		<pubDate>Fri, 20 Jul 2007 02:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/#comment-24</guid>
		<description>[...] Back to James&#8217; book: I was intrigued to see how a rules + analytics specialist referenced CEP and Event Stream Processing. CEP is mentioned in relation to Business Activity Monitoring (covered earlier in this blog here) in the &#8220;EDM and the IT Department&#8221; chapter, whereas ESP (under the moniker &#8220;Stream-Processing Engines&#8221;) is covered under the &#8220;Data and Analytics&#8221; chapter. The latter section is interesting because the authors clearly separate the idea of stream processing / event identification, and the subsequent analysis stage (via an &#8220;analysis engine&#8221;) using temporal rules, calculations, aggregations etc. This is describing a subset of CEP, so perhaps one can one infer that a CEP engine is effectively an event-processing + real-time analytics engine [*2]? Interesting food for thought. [...]</description>
		<content:encoded><![CDATA[<p>[...] Back to James&#8217; book: I was intrigued to see how a rules + analytics specialist referenced CEP and Event Stream Processing. CEP is mentioned in relation to Business Activity Monitoring (covered earlier in this blog here) in the &#8220;EDM and the IT Department&#8221; chapter, whereas ESP (under the moniker &#8220;Stream-Processing Engines&#8221;) is covered under the &#8220;Data and Analytics&#8221; chapter. The latter section is interesting because the authors clearly separate the idea of stream processing / event identification, and the subsequent analysis stage (via an &#8220;analysis engine&#8221;) using temporal rules, calculations, aggregations etc. This is describing a subset of CEP, so perhaps one can one infer that a CEP engine is effectively an event-processing + real-time analytics engine [*2]? Interesting food for thought. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CEP as sauce the alphabet soup (Part 5): BPEL &#187; TIBCOâ€™s Complex Event Processing Blog</title>
		<link>http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/comment-page-1/#comment-19</link>
		<dc:creator>CEP as sauce the alphabet soup (Part 5): BPEL &#187; TIBCOâ€™s Complex Event Processing Blog</dc:creator>
		<pubDate>Mon, 25 Jun 2007 09:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2007/05/22/cep-and-the-alphabet-soup-part-3-bam/#comment-19</guid>
		<description>[...] However, more usefully one could use CEP to do BAM on a BPEL-defined process. This would require the BPEL engine to make internal events aware to the CEP engine, of course, but would be useful for monitoring and control, especially if the process definitions are provided by a 3rd party or business partner. [...]</description>
		<content:encoded><![CDATA[<p>[...] However, more usefully one could use CEP to do BAM on a BPEL-defined process. This would require the BPEL engine to make internal events aware to the CEP engine, of course, but would be useful for monitoring and control, especially if the process definitions are provided by a 3rd party or business partner. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
