Interesting to see James Taylor’s comment on “Decisions Matter in Complex Event Processing”. “Decision Management” [*1] is orthogonal to “event processing type”, where the latter could be continuous complex event processing through to simple event processing in BPM and workflows. Decision Management applies equally to CEP, to BPM, and to SOA, and is particularly useful in application areas where the decisions need to be controlled and changed by the “business”. Some of these technologies will come with built-in decision management, and some will rely on plug-in 3rd-party rule engines and BRMS components (although maybe less so for low-latency CEP).
In CEP, you would typically use Decision Management to maintain the actions resulting from discovery of complex business-level events – e.g. “Impact Assessment” decisions and associated actions.
 “Decision Management” does not really have a fully agreed technology definition yet, but basically covers the externalization of process decisions to enable business users to maintain them. It is usually considered a generalization of BRMS.
Typical features for Decision Management applications include:
- Business User Interface: usually some kind of GUI and appropriate easy-to-use interface such as a decision table
- Management Application: some kind of workflow to support the end-user roles, rights and controls for modifying and deploying decisions
- Metadata: information like authorship and owner information, change logs, policy references, and so forth.