Lecture Semantic Business Process Management
Transcription
Lecture Semantic Business Process Management
Arbeitsgruppe 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/ Overview Semantic Business Process Management Retrospective of the SBPM course Semantic Business Process Managment SBPM Ontology-based BPM Rule-based BPM (intelligent BPM) Event-driven BPM Semantic BPM... ist mit Ontologien oder mit Regeln oder Event basiert Ontologies in Business Process Modeling Ontology Semantic-enriched Business Process Model Semantic Extension of Information Entities in BPMN Erweitern der Business Model mit semantischen Daten, damit Bedeutung erhalten wird Hier sieht man was "Partner" alles besitzt (auf semantischer Ebene) 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 man kann Gleichheit technical information models can zwischen Konzepten finden und Mappings be derived zwischen Vorkabularen erzeugen diese Entity benutzt das Data Object Partner formal domain information models are foundation for semantic jeder Partner in einem mediation between heterogeneous Prozess kann eigene conceptualizations used by Vokabulare verwenden und mit Links / different organizations or domains Verbindungen können diese 2 Mgl. BPMN zu erweitern: grafische Notation direkt erweitern (z.B. mit ODM Metamodell) zusätzliche Pointer in eine Ontologie übersetzt werden vorteil: man kann im BPMN Modell die direkten Entscheidungsregeln sehen nachteil: weniger ausdrucksstark, man kann nur bestimmte Bedingungen angeben, keine komplexe entscheidungs logik SBPM: Homogenous Integration of Rules in BPMN 2.0 – Option 1 selbe Diskussion gilt für Ontologie Erweiterung Mit Regeln BPMN erweitern => stärkere Condition Language für die Gateways (Entscheidungspunkte) Vorteile: kann komplexe entscheidungslogik einfügen Nachteil: schwieriger zu verstehen, muss diese Regeln in externe Datei nachlesen und die Sprache davon verstehen SBPM: Heterogeneous Integration of Rules in BPMN 2.0 – Option 2 andere Mgl. Regeln in BPMN einzufügen > externe Pointer auf Regeln Semantic Business Process Execution with Semantic Web Services auf Execution Level: Semantic Web Service embed SWS in Enterprise Semantic Web Service Service Customer/User Service Using Application Service Provider Semantic WSDL Web Service Application Semantic SLA Business Vocabulary (Ontologies) ITSM (Rules) Approaches Non-functional Properties Response Time Delay / Availability Resource Utilization Functionality Guarantees Pricing /Policies Rights & Obligations Escalation Business Vocabulary (Ontologies) Business Processes Enterprise Application Components Services ITSM (Rules) •OWL-S (former DAML-S), •WSDL-S •RBSLA •SAWSDL •SWWS / WSMF •WSMO / WSML •Meteor-S •SWSI •… Hardware Rule-based BPEL (Semantic BPEL) BPEL mit Regeln Rules-enabled BPEL Application events, facts BRMS (Business Rules Management System) Ontology / Model Mapping Vocabularies / Semantic Ontology Models CEP Logic results Reaction Logic Decision Logic Constraints BPEL run-time Rule Inference Service Rule Interchange Rule Repositories BPEL + Rules BPEL läuft zusammen mit Regeln, kann als Web Service definiert werden => benutzt Rule Engine Rules engines can be invoked as a Semantic Decision / Inference Service from a BPEL process. Dynamic processing Intelligent routing ein Task ausgeführt, Validation of policies within process Constraint checks je nach Entscheidungslogik wird Aufgabe delegiert Ad-hoc Workflow Policy based task assignment Various escalation policies wie Load balancing of tasks wird ein Event / Fehler gefeuert / wohin geleitet 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 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 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 Orchestrated BPEL + Choreography Rule Workflow • Rules can be used to implement choreography workflows as subprocesses in the BPEL flow • Workflows might span several communicating (messaging) rule inference services Rules-enabled BPEL Application events BRMS (Business Rules , facts Management System) CEP Logic results Reaction Logic Decision Logic Constraints BPEL runtime 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). Entscheidungslogik innerhalb der BPEL Engine Example: Rule Responder Project http://responder.ruleml.org Example BPEL + Ontology: sBPEL Ontology of the SUPER Project SUPER Execution Semantic BPEL Execution Engine 1 Execute Task Semantic Execution 15 Environment 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, enterpriserelevant 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 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 2nd class citizens Knowledge management is denigrated Rules are merely implementation 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 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 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 Retrospection of the SBPM course 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 Lecture 1: Introduction BPM Lecture 2: Modeling with UML Lecture 3: Business Process Management Standards BPDM 1.1 BPMN 2.0 BPEL 3.0 Source: Martin Bartonitz/Saperion Lecture 4: Interworkflows with BPEL Lecture 5: Semantic Computing I Ontologies - OMG Ontology Definition Metamodel Lecture 6: Semantic Computing II Ontologies - W3C Web Ontology Language 2 <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> OWL 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 SBVR PRR RuleML RIF ILog Blaze IRL SRL Prova Lecture 9: Semantic Web Services Semantic Web Service Business Processes Service Customer/User Service Using Application Service Provider Semantic WSDL Web Service Application Application Components Semantic SLA Business Vocabulary Contract / SLA Management Non-functional Properties Response Time Delay / Availability Resource Utilization Functionality Guarantees Pricing /Policies Rights & Obligations Escalation Business Vocabulary Contract / SLA Management Approaches •OWL-S (former DAML-S), •WSDL-S •RBSLA •SAWSDL •Super •SWWS / WSMF •WSMO / WSML •Meteor-S •SWSI •… Services Hardware Lecture 10: Semantic Complex Event Processing Lecture 11: Summary & Outlook "Advanced Agile Semantic Business Process Management" Rules-enabled BPEL Application events , facts BRMS Ontology / Model Mapping (Business Rules Management System) Vocabularies / Semantic Ontology Models CEP Logic Reaction Logic result s Decision Logic Constraints BPEL runtime Rule Inference Service Rule Interchan ge Rule Repositories 12: Final Exam Written Exam Monday, July 11th, 2pm 90 minutes