The main characteristic to be aware of in these tools is that BE is primarily rule-based (using an embedded rule engine), whereas BW and iProcess are orchestration / flow engines. In BE we can use a state diagram to indicate a sequence of states which may define what process / rules apply, but this is really just another way of specifying a particular type of rules (i.e. state transition rules). The main advantages to specifying behavior as declarative rules are:

Handling complex, event-driven behavior and choreography Iterative development, rule-by-rule

The main advantages of flow diagrams and BPMN-type models are:

Ease of understanding (especially for simpler process routes)  Process paths are pre-determined and therefore deemed guaranteeable.

In combination these tools provide many of the IT capabilities required in an organization. For example, a business automation task uses BW to consolidate information from multiple existing sources, with human business processes for tasks such as process exceptions managed by iProcess. BE is used to consolidate (complex) events from systems to provide business information, or feed into or drive both BW and iProcess, and also monitors end-to-end system and case performance.