Sunday, October 10, 2010

More on the OMG event processing symposium in the capital market area

Back home,  looking at some notes I have taken in the OMG EP meeting in NYC last week.  Here are some of these notes:

  • The host was Credit Suisse, so we had an opening talk of Eric Newcomer, who told us about Credit Suisse, and also told us that his title was changed from CTO to Chief Architect, since the problem is not evaluation of technology, but coping with the complexity of the systems.  
  • W. Roy Schulte
  •  Roy Schulte (Gartner) gave the first keynote talk.   He set the tone of other speakers as classifying event processing as analytics (which is the current hot buzzword),  he said (this is a slight variation about his previous classification) that event processing have three levels: the simple event processing, which we always done, the BPM + state machine which have some event-driven functionality, and the analytics event processing - AKA CEP or ESP, i.e. providing aggregations and pattern matching.  On the financial market front he said that while the original EP applications have been in the front office, it is now getting to the middle and back office in various application areas.   He also sees that the future of inter-systems integrations will be in using events.   On EP as part of analytics he also talked on the BI classification -- descriptive (BAM systems),  predictive (pattern matching is a way to define predictive) and prescriptive (which is still mostly futuristic).    There are also three ways to deliver event processing:  Basic engine,  EP platform (which includes tools for management, debug etc..) and packaged applications  (this classification is not new).

    Thomas Sulzbacher
  • Thomas Sulzbacher, CEO of Starview, talked about his product. He started his talk by saying that he took a flight from SFO to NYC in order to arrive into the conference, and in order to execute the flight, there were 12M  event-driven decisions required, most of them automatic. 

      David Parker
    • David Parker, from Sybase, An SAP company, as he repeatedly reminded us, also classified event processing as part of the analytics solutions of Sybase.  The interesting insight he provided (from Sybase internal sources) is how they view the distribution of the EP market:   42% Finance Sector, 14% government, 11% services, 8% telecommunication 8% healthcare and life sciences, 6% production, 4% retail, 3% education, 2% energy and utilities.     It is interesting to see if other vendors have different perspectives, especially what analysts have to say, since no analyst has produced such a detailed distribution so far.

      Colin Clark
    • Colin Clark, whom I met first time, talked and demoed his cloud event processing solution, that does indexing, clustering. classification, summarization and anomaly detection.  He came along with his business partners that made a draw among the participants that provided them business cards,  and gave some gifts -- I think it was iPad.   

    Dr. John BatesThese talks were all before lunch - after lunch I did not take notes anymore;  there were two talks - one by John Bates, interesting as always, given us concentration of incidents in the financial markets area, among other things, and the last talk (before mine) was Matt Meinel from Informatica (came from the acquisition of  29West).

    Matt Meinel



    Anonymous said...

    Hello Opher,

    I found an interesting comment in your blog where you cite John Bates: " (...) interesting as always, given us concentration of incidents in the financial markets area (...)".

    Can you provide us with a little more detailed information on those incidents?

    Another question is, if it is necessary to cover those incidents by things we called previously "Incident Object" or if it is simply a set of rules without keeping a context. Has John Bates made any comments around that?

    Best regards,


    Opher Etzion said...

    In incidents I meant cases where there has been some negative impact of trading programs, like the one earlier this year in which testing of a trading program got by mistake to production and sent orders in unusually high amount that almost crashed the stock market. I did not document all the examples.


    Anonymous said...


    I'd rather want to distinguish two characteristics when describing "(...) cases where there has been some negative impact (...)".

    1. A state without any timely duration
    2. A state with timely duration

    The first one might be represented via a more or less complex sequence of rules whereas the second one needs from my perspective an object representation.

    Best regards,