Although several folks in TIBCO had used the term “visual analytics” to try and describe what TIBCO Spotfire does, as opposed to merely reporting on views of data, the analysts have continued to position Spotfire as a “BI” tool. But now, the Spotfire marketing folk are starting to use the term “Spotfire Analytics” to better describe the positioning of the product, especially with the combination of S+ and Miner predictive analytics capabilities.

How does this affect TIBCO Complex Event Processing users? Not one jot, of course. Spotfire remains the preferred analytic tool for visualising the event data in a TIBCO BusinessEvents backing store (a.k.a. the “event warehouse”) and comparing that data with other sources. Using Spotfire you can identify new patterns that can then be used to update rules, queries and decisions in a TIBCO BusinessEvents application - or indeed, execute an S+ or Miner analytics model against the incoming events in either a regular, or special purpose, event processing agent.

Forrester’s James Kobelius made some interesting comments on the proposed buy-out of IDS Scheer - known for their high level process modeling tool Aris - by SoftwareAG. Such as:

“What’s most exciting, and potentially differentiating, about the Software AG/IDS Scheer BI portfolio is the combination of CEP with mashup and an in-memory architecture to support truly real-time, interactive analytics. In other words, Software AG/IDS Scheer could take a page out of the book of another SOA full-stack vendor: TIBCO and its Spotfire product group. “

Unfortunately the IDS Scheer BAM solution (which does not claim to be a Complex Event Processing solution) is OEMed - making full integration and exploitation more difficult. Otherwise, we agree, this could have had some potential to catch up with TIBCO.

Possibly more interesting to the event processing community is IDS’ alternative to value chain models - their event-driven process chain. Mostly this has been replaced by BPMN diagramming in modern process modeling environments, but nonetheless could still provide a useful high-level notation… perhaps SoftwareAG will propose it as a standard somewhere?