Proposed EPTS Steering Committee Reorganization
Following up to my earlier posts on Event Processing Technical Society (EPTS) related topics, I am proposing a draft reorganization of the EPTS Steering Committee. The current EPTS Steering Committee was structured as follows:
| # | Industry | Primary EPTS-Related Technology | Comments |
| 1 | Software Company | Event Stream Processing / Continuous Query | Vendor |
| 2 | Software Company | Event Stream Processing / Continuous Query | Vendor |
| 3 | Software Company | Event Stream Processing / Continuous Query | Vendor |
| 4 | Software Company | Event Stream Processing / Continuous Query | Vendor |
| 5 | Software Company | Event Stream Processing / Continuous Query | Vendor |
| 6 | Software Company | Rete Rules Engine + Continue Query Engine | Vendor |
| 7 | Technology Analysis / Convention Host | Research Notes, Presentations, White Papers | Vendor |
| 8 | Independent Consultant | CEP Promotion, CEP Web Site Sponsorship, CEP Evangelism | Vendor |
| 9 | To Be Confirmed | To Be Confirmed | Vendor |
| 10 | To Be Confirmed | To Be Confirmed | Vendor |
Discussion:
The current EPTS Steering Committee (SC) does not represent the art-and-science of event processing. All SC members are vendors and all but two of the SC members are software vendors, all but one of these software sellers are selling very similar products, event stream processing / continuous query engines. There is one industry analyst (a vendor). There is only one independent consultant, evangelist (another vendor). There are no end users or other industry segments represented on the SC. In a nutshell, the EPTS is composed of vendors, most of which are software vendors selling very similar products.
I propose that the event processing community at-large would be better represented and served if the EPTS SC was reorganized, something like this:
| # | Industry | Primary EPTS-Related Technology | Comments |
| 1 | Software Company | Event Stream Processing / Continuous Query | Vendor |
| 2 | Telecommunications | Network Management | End User |
| 3 | Financial Services | Security and Risk Management | End User |
| 4 | Software Company | Neural and/or Bayesian Networks | Vendor |
| 5 | Software Company | Rules Engine | Vendor |
| 6 | Military / Government | Data and Sensor Fusion / CEP | End User |
| 7 | Transportation | Operations Research | End User |
| 8 | Independent Consultant | CEP Promotion, CEP Web Site Sponsorship, CEP Evangelism | Vendor |
| 9 | NPO | Event Processing Standards | End User |
| 10 | Open | Open | End User |
The above list could certainly be improved and refined. It is just a first draft. However, as readers can see, instead of being a society that is managed by vendors with a single, dominate software technology, the society shifts to one where various industries and technologies are more equally represented. The majority of the SC members in my proposed reorganization would be end users, not vendors.
Your comments and suggestions are warmly appreciated.
Paul Vincent says:
Thursday, December 25, 2008 at 12:54am
Hi Tim – Happy Holidays!
Do you think end-users would have any interest in a technology advocacy group like EPTS? Do you have any such end-users already in EPTS in mind?
Cheers
Tim Bass says:
Thursday, December 25, 2008 at 9:35pm
Hi Paul,
Happy Holidays to you!
There are many interested end users if the EPTS leadership would simple reach out to them, offering them a dominate seat at the steering committee table, versus the small software vendor group with similar products.
I think my recommendations are solid. However, I don’t think EPTS leadership will do the right thing and build a true “event processing technical society” that represents the true state-of-the-practice for event processing.
However, it is professionally responsible to point out that the EPTS Steering Committee is advocating for a very narrow segment of the full spectrum of event processing technologies; and paying minimal respect and due process to the prior many decades of event processing technologies and expertise.
Yours sincerely, Tim