Geschäftsprozesse und Regeln - IBM · business goals and policies, ... –need to move beyond EAI through workflows ... – Combined BPMS/BRMS approach

© HSLU - JK

Geschäftsprozesse und Regeln

7 Szenarien einer möglichen Integration

Jana KoehlerHochschule Luzern

Lucerne University of Applied Sciences and Arts

[email protected]

© HSLU - JK

Gartner: “Organizations struggle with the interaction of rules and processes”

Jim Sinur: The Art and Science of Rules vs. Process Flows

Geschätsprozesse und Regeln - Jana Koehler2

© HSLU - JK

Many open Questions …

How relevant are these 7 scenarios?– Why 7? Should there be more or less?

Is the distinction of these scenarios helpful in a BPM project?

How can a scenario be implemented with today’s technology?

Where do industry standards for business process modeling and business rules stand?– BPMN (Business Process Model and Notation)– SBVR (Semantic Business Vocabulary and Rules)


© HSLU - JK

Case Study: Customer Billing

Increasingly flexible pricing methods– Time-dependent (airline fees)– Depending on customer segement/individual customer (insurance,

banking, telco)– Depending on purchase bundles and sales targets (telco, retail)

Increasingly complex computations, influenced by various business goals and policies, frequent change– High impact on customer satisfaction


© HSLU - JK Geschätsprozesse und Regeln - Jana Koehler5

General Drivers towards dynamic Process Solutions

Agility vs. Control – need to move beyond EAI through workflows– modern working environments: project-oriented &

knowledge-intensive & decision-driven

Intelligent Case Management– enable activities on the basis of the available information – support human-driven & rule-driven initiatives

• people decide when to perform a business function• business rules govern business conduct

© HSLU - JK

Scenario 1: Embedded Rules

Predefined process paths– Directly encoded into the process model– No explicit rules used in BPM solution– Rule-based decisions reflected in gateway logic


© HSLU - JK

Scenario 2: Explicit Navigation Rules

Explicit rules – Maintained in rule components managed by rules engine– Combined BPMS/BRMS approach– Change of rules separated from change of process


BPMN Rule Task

© HSLU - JK

Scenario 3: Complex Navigation and Analysis

Several rule sets with more fine-grained rules– Rules have broader access to the process context – Rule sets grow & change more often– Challenges in consistency and performance


© HSLU - JK

Scenario 4: Rule-Guided Behavior

Inter-Process Communication & packaged rule sets – Process interacts with rules observing much wider business

conditions– Rules at the ’metalevel’ encoding policies of process behavior– Rules steer process instances towards specific business goals



© HSLU - JK

Scenario 5: Rule-Driven Components

Dynamic composition of processes from predefined (process) components & directed by rulesRules no longer subordinate to processNo predefined end-2-end process flows, emerges at runtime



© HSLU - JK

Scenario 6: Rule-Driven Services

More fine-grained process/service components driven by rules

Processes dynamically configure themselves for every process instanceRule sets change dynamically, adjust to changing conditions at runtime without human interventionRequires learning capabilities to yield modified or new rules


Scenario 7: Fully Rule-Dynamic

© HSLU - JK

Summary – 4 Key Rule Patterns

(1) Embedded rules (Sc. 1)− Classic BPM solution, no explicit rules

(2) Explicit rule tasks (Sc. 2/3)− Integrated BPM/BRMS solution− (or embedded rule capabilities of BPM engines used)

(3) Rule guidance across process context (Sc. 4)− Rule computations communicated between processes

(4) Active & Learned Rules (Sc. 5/6/7)− Rules guide process compositions, e.g. as SCA components− Application-specific intelligence and machine learning


© HSLU - JK

Types of Rules


© HSLU - JK

http://www.bpmn-workshop.org

16 Geschätsprozesse und Regeln - Jana Koehler

Documents

Geschäftsprozesse und Regeln - IBM · business goals and policies, ... –need to move beyond EAI through workflows ... – Combined BPMS/BRMS approach