Comments on: BPM TT 08: CEP augmenting BPMS for agility

By: Complex Event Processing (CEP) Blog » BPMI TT EU 08: setting expectations for BPMN 3.0

Tue, 11 Nov 2008 21:54:24 +0000

[...] move to Europe, and a chance to observe any differences in BPM expectations and takeup over the previous US event. TIBCO were here to host the round table on “Combining Event Processing with BPMS for [...]

By: Complex Event Processing (CEP) Blog » Business Rules Forum 2008: Upper Ontology for Events, Processes, States, Rules

Thu, 30 Oct 2008 09:40:28 +0000

[...] a fair point, but at TIBCO we would point to iProcess Conductor, and even BusinessEvents CEP being used to control iProcess [...]

By: BPM Think Tank 2008

BPM Think Tank 2008 — Wed, 15 Oct 2008 21:54:18 +0000

[...] fine for the first time out with this material. Others like Scott Francis BP3 & Paul Vincent Complex Events looked at the presentation from other perspectives. I figured it was low risk to try some new [...]

By: vincent

vincent — Thu, 09 Oct 2008 21:02:39 +0000

Thanks Alex - the Forrester PPT seems to take quite a holistic view of BPM - as in “everything can be called BPM”. TIBCO’s version is “BPM+”, but even we don’t claim that the source of all events is some other business process
I suspect they have a different view now.

On the single run-time: I guess that depends on your perspective. We have some customers using TIBCO BusinessEvents for process execution including workflows (indeed we use BE as our own state + workflow manager for decision management). However, we don’t *claim* that BE is a jack-of-all-trades system…

Cheers

By: Alex

Alex — Thu, 09 Oct 2008 08:07:42 +0000

No worries for the edits in my post - I was expecting it. I didn’t told the topic was newly addressed. f.e. Forrester wrote in 2006 “Remember that a BPMS must serve as the foundation for BEM or CEP capability” (see http://www.forrester.com/Events/Content/0,5180,1396,00.ppt)
and pointed out that CEP was a natural feature to be added in a BPMS for the next generation t o come.
I have no doubt Tibco has deployments on such a use case thru tailored, project by project, custom assembly of multiple products (yours or not), but I find it quite interesting that some actors are going after this approach in a more integrated way thru a single runtime approach.

By: vincent

vincent — Thu, 09 Oct 2008 02:36:21 +0000

Hi Alex - thanks for pointing out that at least one small open source player is trying the combined approach. I guess I should have qualified with statements like “with deployed applications” etc (which may or may not be true for the vendor you mention). Mark Proctor at DROOLS is trying to build something similar. More power to them (and you)!

FYI I think we’ve had customers combining TIBCO iProcess with TIBCO BusinessEvents (which of course is a loose coupling) since, er, well a few years now anyway. I’ll have to check!

I’d fully expect some other CEP vendors to have deployments with BPM systems too - just none I’m particularly aware of, and probably not vendor-level relationships just yet. Although I fully expect a few BPMS vendors to eventually “kick the tyres” with some independent CEP vendor.

PS: sorry for the gross edit of your post, but it came across as excessive hype - which we try and keep to a minimum even on TIBCO products. (For example, count the references to TIBCO iProcess, iProcessConductor, and even TIBCO BusinessEvents in the above blog entry! )

By: Alex

Alex — Wed, 08 Oct 2008 15:00:14 +0000

I of course meant “provides COTS BPMS + CEP”

By: Alex

Alex — Wed, 08 Oct 2008 14:55:08 +0000

CEP + BPM is taking shape and it’s good to see work is beeing done by a number of players in that area.
One such player [[has integrated the Esper CEP engine since Sept this year]]. [[Product details removed]]

It is also interesting to note some posts from [[another open source BPM vendor]] about their CEP target that is in a roadmap stage.

(sorry for the plugs)

[[Edited to remove spam-like promotions of another CEP suppliers' partners, which is inappropiate for the TIBCO CEP blog!]]