Semantic Business Process Management

(1)

Lecture

Semantic Business Process Management

Prof. Dr. Adrian Paschke

Corporate Semantic Web (AG-CSW)

Institute for Computer Science, Freie Universitaet Berlin [email protected]

http://www.inf.fu-berlin.de/groups/ag-csw/

Arbeitsgruppe

(2)

Overview

 Semantic Business Process Management

 Retrospective of the SBPM course

(3)

Semantic Business Process Managment

SBPM

 Ontology-based BPM

 Rule-based BPM (intelligent BPM)

 Event-driven BPM

ist mit Ontologien oder mit Regeln oder Event basiert Semantic BPM...

(4)

Ontologies in Business Process Modeling

Ontology

Semantic-enriched

Business Process

Model

(5)

Semantic Extension of Information Entities in BPMN

 Utilize corporate or domain ontology concepts to define

information flow on a non-technical conceptual level suitable for

business process experts

 due to formal nature consistent link between the business or

conceptual level and underlying technical information models can be derived

 formal domain information models are foundation for semantic

mediation between heterogeneous conceptualizations used by

different organizations or domains

Erweitern der Business Model mit semantischen Daten, damit Bedeutung erhalten wird

diese Entity

benutzt das Data Object Partner

Hier sieht man was "Partner" alles besitzt (auf semantischer Ebene)

man kann Gleichheit zwischen Konzepten finden und Mappings

zwischen Vorkabularen erzeugen

jeder Partner in einem Prozess kann eigene Vokabulare verwenden und mit Links /

Verbindungen können diese übersetzt werden

2 Mgl. BPMN zu erweitern:

grafische Notation direkt erweitern (z.B. mit ODM Metamodell)

zusätzliche Pointer in eine Ontologie

(6)

SBPM: Homogenous Integration of Rules in BPMN 2.0 – Option 1

Mit Regeln BPMN erweitern => stärkere Condition Language für die Gateways (Entscheidungspunkte) vorteil: man kann im BPMN Modell die direkten Entscheidungsregeln sehen

nachteil: weniger ausdrucksstark, man kann nur bestimmte Bedingungen angeben, keine komplexe entscheidungs logik selbe

Diskussion gilt

für

Ontologie Erweiterung

(7)

SBPM: Heterogeneous Integration of Rules in BPMN 2.0 – Option 2

andere Mgl. Regeln in BPMN einzufügen

> externe Pointer auf Regeln

Vorteile: kann komplexe entscheidungslogik einfügen

Nachteil: schwieriger zu verstehen, muss diese Regeln in externe Datei nachlesen und die Sprache davon verstehen

(8)

Semantic Business Process Execution with Semantic Web Services

Business Processes

Enterprise Application Components

Services

Hardware

Web Service Application Service Using

Application

Semantic WSDL

ITSM (Rules) ITSM (Rules)

Semantic SLA Non-functional

Properties Response Time Delay / Availability Resource Utilization

Functionality Guarantees Pricing /Policies Rights & Obligations

Escalation Service

Customer/User Service Provider

Business

Vocabulary (Ontologies) Business

Vocabulary (Ontologies)

Semantic Web Service

•OWL-S (former DAML-S),

•WSDL-S

•RBSLA

•SAWSDL

•SWWS / WSMF

•WSMO / WSML

•Meteor-S

•SWSI

•…

Approaches

auf Execution Level: Semantic Web Service

embed SWS in Enterprise

(9)

Rules-enabled BPEL Application

BPEL run-time

(Business Rules

BRMS

Management System)

events, facts

results

CEP Logic Reaction

Logic

Decision Logic

Constraints

Rule Inference Service

Rule

Repositories

Vocabularies / Semantic Ontology

Models

Rule Interchange Ontology /

Model Mapping

Rule-based BPEL (Semantic BPEL)

BPEL mit Regeln

(10)

BPEL + Rules

Rules engines can be invoked as a Semantic Decision / Inference Service from a BPEL process.

 Dynamic processing

 Intelligent routing

 Validation of policies within process

 Constraint checks

 Ad-hoc Workflow

 Policy based task assignment

 Various escalation policies

 Load balancing of tasks

 Business Activity Monitoring

 Alerts based on certain policies and complex event processing (rule-based CEP)

 Dynamic processing based KPI reasoning

BPEL Process Manager and Rules together enable agile and adaptive business processes

BPEL läuft zusammen mit Regeln,

kann als Web Service definiert werden => benutzt Rule Engine

ein Task ausgeführt, je nach Entscheidungslogik wird Aufgabe delegiert

wie wird ein Event / Fehler gefeuert / wohin geleitet

(11)

Rule Inference Service - Usage

1. Create Decision Service

 Select Rule Connection

 Create service based on interaction pattern.

 Select input and output facts / events

2. Invoke rules from Process

 Call rule inference service

 Map BPEL variables to input and output facts (results)

3. Most common patterns include

 Execute function (stateless)

 Assert-Execute-Watch (stateless)

 Assert, Assert …. Execute, Watch (stateful)

Kommunikationsstil:

loose gekoppelt oder

auch entkoppelt mit Events

(12)

Rule-based BPEL – How To Do It?

1. Create a rule inference service with rule repository

 Create semantic interface description of the inference service

2. Create a new Inference Service Partnerlink

 Choose a rule connection

 Choose an interaction pattern and parameter bindings

3. Add a Decide Activity

 Bind BPEL variables to parameters of partnerlink

Semantic Einfügen: bei 1. die semantische Schnittstelle gleich nehmen

(13)

Orchestrated BPEL + Choreography Rule Workflow

Rules-enabled BPEL Application

BPEL run- time

BRMS

(Business Rules Management

System)

events , facts

results

CEP Logic Reaction

Logic Decision

Logic Constraints

Rule Inference Service

% receive query and delegate it to another party rcvMsg(CID,esb, Requester, acl_query-ref, Query) :-

responsibleRole(Agent, Query),

sendMsg(Sub-CID,esb,Agent,acl_query-ref, Query), rcvMsg(Sub-CID,esb,Agent,acl_inform-ref, Answer), ... (other goals)...

sendMsg(CID,esb,Requester,acl_inform-ref,Answer).

• Rules can be used to implement choreography workflows as subprocesses in the BPEL flow

• Workflows might span several communicating (messaging) rule inference services

Entscheidungslogik innerhalb der BPEL Engine

(14)

Example:

Rule Responder Project

http://responder.ruleml.org

(15)

15

Example BPEL + Ontology:

sBPEL Ontology of the SUPER Project

Semantic Execution Environment

1 Execute Task

Semantic BPEL Execution

Engine SUPER Execution

(16)

What it missing for SBPM?

Process / Event / State / Action Ontologies

 The ability to interchange semantic models across major BPM & BRMS vendors would dramatically increase the market for reusable, enterprise-

relevant knowledge.

 The lack of ontology for events, processes,

states, actions, and other concepts that relate to change over time limits rules or logic that govern processes or react to events to implementations rather than declarative knowledge

 Knowledge modeling / representation should be

integrated into the context of BPM and CEP

(17)

What is missing for SBPM?

Rules and Processes

 Integration is loose and inadequate

 Rules have no visibility to process or state

 Decisions are isolated from processes

 Governance of processes by rules is not addressed

 Definition of processes by logic is not addressed

 no precise logical semantics in e.g. BPMN

 no declerative representation, only static syntactical flow descriptions

 Logical and business rules are 2 ^nd class citizens

 Knowledge management is denigrated

 Rules are merely implementation

(18)

Semantic BPM: easier & better

 Each (graphical) syntax concept in a BPM model is using an ontology concept that references the semantics of it

 Processes have causality and roles

 Semantic inferences result in findings

 inferences are performed by inference agents/services

 The object / result of inference are process

knowledge

(19)

Semantic CEP: easier & better

 Managing state becomes much simpler

 a plane is no longer flying after it lands

 a plane begins flying when it takes off

 Knowing that events and processes occur

 allows when (and where) to be understood

 a landing starts when a plane approaches

 CEP becomes simpler with a BRMS

 that understands aggregates over time

 that understands tense wrt states and processes

(20)

Summary – Key Benefits of SBPM

 Semantic Business Process Management = combination of Corporate

Semantic Web technologies, such as rules, events and ontologies, with BPM

 Goals

 enhanced automation in discovery, configuration and composition of appropriate process components, information objects, and services

 automated mediation between different heterogeneous interfaces and abstraction levels

 targeted complex queries on the process space and flow

 much more agile business process management.

 Key benefits:

 Complementary technologies: semantic technologies + ITSM/BPM technologies

 BPMN-BPEL for orchestration of services, systems, people & partners

 Rules focus on decision making and policies

 Rules can be used to integrate choreography sub-workflows in orchestrated BPEL processes

 Declarative specification of constantly changing business policies and regulations

 Enables business users to participate in business processes

 Modify and apply new rules without redeploying processes

 Centralized policy management across the organization

(21)

Retrospection of the SBPM course

(22)

Goals

 „ The assumption behind Business Process

Management (BPM) is, that the uniqueness of an enterprise lies in the way how it manages and executes its business processes.“

 Deepen the knowledge about BPM in

combination with modern Corporate Semantic technologies

 Methods, Technologies, Standards and Tools

in SBPM

(23)

Lecture 1: Introduction BPM

(24)

Lecture 2: Modeling with UML

(25)

Lecture 3:

Business Process Management Standards

BPMN 2.0

Source: Martin Bartonitz/Saperion

BPEL 3.0

BPDM 1.1

(26)

Lecture 4: Interworkflows with BPEL

(27)

Lecture 5: Semantic Computing I

Ontologies - OMG Ontology Definition Metamodel

(28)

<owl:SubClass owl:name="Person">

<owl:super> <Class "Animal"/></owl:super>

<owl:restriction>

<owl:property resouce="hasParent">

<owl:range>

<owl:Class owl:ID="Person"/>

</owl:range>

</owl:property>

</owl:restriction>

<owl:restriction>

<owl:property resource="hasFather”

exactly=“1"/>

</owl:restriction>

</owl:SubClass>

Lecture 6: Semantic Computing II

Ontologies - W3C Web Ontology Language 2

OWL

(29)

Lecture 7+8: Semantic Computing III & IV

Business Rules / Web Rules / Event/Actions

Users employ rules to express what they want, the responsibility to interpret this and to decide on how to do it is delegated to an

interpreter Represent knowledge in a way

that is understandable by ‘the business’, but also executable

by rule engines, thus bridging the gap between business and

technology

ILog IRL

Blaze

SRL Prova

PRR RuleML ^RIF

SBVR

(30)

Lecture 9: Semantic Web Services

Business Processes

Application Components

Services

Hardware

Web Service Application Service Using

Application

Semantic WSDL

Contract / SLA Management Contract / SLA

Management

Semantic SLA Non-functional

Properties Response Time Delay / Availability Resource Utilization

Functionality Guarantees Pricing /Policies Rights & Obligations

Escalation Service

Customer/User Service Provider

Business

Vocabulary Business

Vocabulary

Semantic Web Service

•OWL-S (former DAML-S),

•WSDL-S

•RBSLA

•SAWSDL

•Super

•SWWS / WSMF

•WSMO / WSML

•Meteor-S

•SWSI

•…

Approaches

(31)

Lecture 10: Semantic Complex Event Processing

(32)

Lecture 11: Summary & Outlook "Advanced

Agile Semantic Business Process Management"

Rules-enabled BPEL Application

BPEL run- time

BRMS

(Business Rules Management

System)

events , facts

result s

CEP Logic

Reaction Logic

Decision Logic Constraints

Rule Inference Service

Rule Repositories

Vocabularies / Semantic Ontology

Models

Rule Interchan

ge Ontology /

Model Mapping

(33)

12: Final Exam

 Written Exam

 Monday, July 11th, 2pm

 90 minutes

(34)