Transcript Agenda - IARIA

Semantic Management
of Business Processes
in the Future Internet
Presenters
•
•
•
Agata Filipowska (Poznan University
of Economics, Poland)
Dumitru Roman (STI Innsbruck, Austria)
Alexander Simov (Ontotext lab.,
Bulgaria)
at I-CENTRIC 2008
Sliema, Malta
October 26th, 2008
Acknowledgement & Copyrights
•
This material is based upon works supported by the EU under the
SUPER project (FP6 - 026850)
•
Material Preparation
– KMI: John Domingue, Barry Norton
– Poznan University: Agata Filipowska
– IAAS, University of Stuttgart: Dimka Karastoyanova, Jörg Nitzsche, Tammo van
Lessen, Zhilei Ma, Frank Leymann
– IDS Scheer: Sebastian Stein
– STI Innsbruck: Dumitru Roman, Michael Stollberg
– DERI Galway: Maciej Zaremba, Sami Bhiri, Armin Haller
– Ontotext: Marin Dimitrov
© by the SUPER project consortium
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
2
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
3
Introduction
Agata Filipowska, Poznan University of Economics
Querying the Process Space
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
5
The Critical IT / Process Divide
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
6
The Critical IT / Process Divide
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
7
What Are My Services?
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
8
What Are My Services?
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
9
What Are My Services?
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
10
Matching Activities and Port Types Based on Semantics
Semantic Web Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
11
Supporting Business Users Better
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
12
Matching Model Representations & Semantics
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
13
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
14
Business Process Management
Introduction
Agata Filipowska
BPM’s Parents and Definition
Office Automation
(since 1980)
SOA
(since 2000)
CSCW / Groupware /
Workgroup Systems
Business Objects
(since 2000)
Business Process Mngt.
(since 2000)
Workflow Systems
(since 1985)
Business
Process
Management
(BPM)
Business Process Modelling
(since 1990)
EAI
(since 1990)
Business Reengineering
(since 1990)
Continuous Improvements
(since 1990)
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
16
Enterprise Modelling
Enterprise Models:
“… a computational representation of the structure,
activities, processes, information, resources, people,
behavior, goals, and constraints of a business,
government, or other enterprises.”
Models
What
(Data)
How
(Function)
Where
(Network)
Who
(People)
When
Why
e.g.
UML Class
Diagram,
ER Model
e.g.
Function
Modeling
e.g.
Business
Logistics
System
e.g.
Workflow
Model
e.g.
Master
Schedule
e.g.
Business Plan,
Strategic Maps
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
17
Enterprise Model
License
Available
Get License
SYS
Purchase
Order
Received
Get
PurchaseOrder
SYS
Purchase
Order
Extracted
Send Content
& License
SYS
Load Content
SYS
© SUPER 25.04.2020
Purchase
Order
Satisfied
Content
Ready for
Download
I-CENTRIC, Malta 2008
18
Enterprise Model
License
Available
Get License
SYS
Purchase
Order
Received
Get
PurchaseOrder
SYS
Purchase
Order
Extracted
Send Content
& License
SYS
Load Content
SYS
Purchase
Order
Satisfied
Content
Ready for
Download
Cell Phone
Cell Phone
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
19
Enterprise Model
Customer
Content
Identifier
License
License
Available
Get License
Customer
SYS
Purchase
Order
Received
Get
PurchaseOrder
SYS
Purchase
Order
Extracted
Digital
Content
License
Send Content
& License
SYS
Load Content
SYS
Purchase
Order
Satisfied
Content
Ready for
Download
Cell Phone
Cell Phone
Content
Identifier
© SUPER 25.04.2020
Digital
Content
I-CENTRIC, Malta 2008
20
Enterprise Model
Customer
License
License
Service
Content
Identifier
License
Available
Get License
Customer
SYS
Purchase
Order
Received
Get
PurchaseOrder
SYS
Purchase
Order
Extracted
Digital
Content
License
Send Content
& License
SYS
Cell Phone
Interface
Service
Load Content
SYS
Content
Ready for
Download
Purchase
Order
Satisfied
Cell Phone
Interface
Service
Content
Library
Service
Cell Phone
Cell Phone
Content
Identifier
© SUPER 25.04.2020
Digital
Content
I-CENTRIC, Malta 2008
21
Enterprise Model
Customer
License
Sales
Department
License
Service
Content
Identifier
License
Available
Get License
Customer
SYS
Purchase
Order
Received
Get
PurchaseOrder
SYS
Purchase
Order
Extracted
Digital
Content
License
Send Content
& License
SYS
Cell Phone
Interface
Service
Load Content
SYS
IT Department
Content
Ready for
Download
Cell Phone
Interface
Service
Content
Library
Service
IT Department
Cell Phone
Purchase
Order
Satisfied
Cell Phone
Content
Identifier
© SUPER 25.04.2020
Digital
Content
Content
Provider
I-CENTRIC, Malta 2008
22
Enterprise Model
too complex
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
23
Enterprise Model
• possible abstraction layers are:
–
–
–
–
requirements definition
design specification
implementation specification
execution and run-time models
• possible views are:
–
–
–
–
–
organisational view
product view
data view (information architecture)
function and IT view
process view
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
24
Enterprise Model
• many different frameworks for enterprise architecture, e.g.:
–
–
–
–
–
Zachman Framework (very comprehensive)
ArchiMate (simplified version of Zachman)
ARIS (promoted by IDS Scheer)
TOGAF (strong IT focus)
IAF (promoted by Cap Gemini)
• currently many discussions around process design & execution, e.g.:
–
–
–
–
–
–
–
–
BPMN (notation for (IT oriented) business processes)
EPC (notation for business processes)
Petrinets (formalism often used for workflow modelling)
UML Activity diagrams
XPDL (execution language for process definitions)
BPEL (execution language for process definitions)
XLANG (execution language promoted by Microsoft)
...
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
25
Process Lifecycle
•
•
•
enterprise model evolves  lifecycle
based on general Deming cycle for continuous process
improvements
sometimes also named Shewhart cycle
1.
2.
3.
4.
Plan
Do
Check
Act
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
26
Summary
• BPM definition depends on your focus
• Enterprise Model describes all relevant aspects of your enterprise
• different stakeholders will have different views and information
needs
• lifecycle for the different parts of the Enterprise Model
• BPM is done for many different purposes, but SUPER focus on:
– business process design
– business process execution
– monitoring and analysis of execution
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
27
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
28
Business Process Management
Processes and Process Execution
Alexander Simov
BPM Applications
Business Experts’ Perspective: Processes
Querying the
Process Space
Manual Labor
Process
Implementation
IT Implementation Perspective
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
30
What is BPEL?
• BPM language/model
• Language to specify behaviour of business processes
• Executable and Abstract processes
–
–
Executable processes
– Executed within a compliant environment (portability)
Abstract processes
– Specify constraints of message exchange
– Provide “views” on internal processes
• Combination of graph-based language (IBM WSFL) and
calculus-based language (Microsoft XLANG)
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
31
BPEL Web Service composition
• BPEL process composes (uses) Web services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
32
Business Processes as Web services
• BPEL Process is also a Web service
– functionality in terms of WSDL port types and operations
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
33
Process Lifecycle within the Engine
Instantiation
Process
Definition
Deployment
Process
Instance
...
Execution via the
Navigator
BPEL
Document
Invocation and Management Framework
Receive*
Reply
BPEL Engine
* Receive may cause an Instantiation of a Process
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
34
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
35
Semantic Web Services
Dumitru Roman
Semantics for the WWW
Dynamic
Static
© SUPER 25.04.2020
UDDI, WSDL, SOAP
Semantic Web
Services
WWW
Semantic Web
URI, HTML, HTTP
RDF, RDF(S), OWL
Web Services
I-CENTRIC, Malta 2008
37
The Semantic Web
• next generation of the Internet (augmentation of the WWW)
• information has machine-processable and machineunderstandable semantics
• ontologies as base technology for semantic interoperability
semantic bridges
RDF
© SUPER 25.04.2020
OWL
ontology
ontology
ontology
Web
Appl.
XML
DB
I-CENTRIC, Malta 2008
38
Ontology Definition
conceptual model
of a domain
(ontological theory)
unambiguous
terminology definitions
formal, explicit specification of a shared conceptualization
machine-readability
with computational
semantics
© SUPER 25.04.2020
commonly accepted
understanding
I-CENTRIC, Malta 2008
39
Ontology Example
name
Concept
conceptual entity of the domain
Property
attribute describing a concept
Person
student
ID
Student
Axiom
research
field
isA – hierarchy
(taxonomy)
Professor
attends
Relation
relationship between concepts or
properties
email
holds
Lecture
lecture
no.
topic
coherency description between
Concepts / Properties / Relations
via logical expressions
holds(Professor, Lecture) =>
Lecture.topic = Professor.researchField
Instance
Ann memberOf student
name = Ann Lee
studentID = 12345
individual in the domain
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
40
Web Services & SOA
• Web Service = program accessible over the Web
• Service-Oriented Architecture (SOA):
– use Web services as basic building blocks
– dynamically find & invoke those Web services
that allow to solve a particular request
• Web Service Technologies:
1. WSDL
2. SOAP
3. UDDI
Web Service Description Language
XML data exchange protocol for the Web
registry for Web Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
43
The Web Service Usage Process
points to
WSDL
Repository
describes
find usable
Web Service
Consumer
Web
Service
SOAP
WS usage via message exchange
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
44
Deficiencies of WS Technology
• current technologies allow usage of Web Services
• but:
– only syntactical information descriptions
– syntactic support for discovery, composition and execution
=> Web Service usability, usage, and integration needs to be inspected
manually
– no semantically marked up content / services
– no support for the Semantic Web
=> initial Web Service Technology Stack failed to
realize the SOA Vision
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
45
Semantic Web Services
•
automate Web Service technologies by
1.
2.
•
integration with the Semantic Web
–
–
•
rich, formal annotation of Web Services
automated detection and execution of Web services
ontologies as data model
Web Services as integral part of the WWW
inference-based techniques for automated discovery,
composition, mediation, execution of Web Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
46
Semantic Web Services
a) Web Service Description Structure
b) Semantic Web Service Description Structure
Non-functional
Functionality
Interface
Web Service
Implementation
Web Service
Implementation
WS
(not of interest in Web
Service Description)
(not of interest in Web
Service Description)
WS
WS
Aggregation
Interface
XML
Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
Ontology
Ontology
47
Web Service Modeling Ontology (WSMO)
• Comprehensive Framework for SESA
Semantically Enabled Service-Oriented Architecture
– top level notions = SESA core elements
– conceptual model + axiomatization
– ontology & rule language
• International Consortium (mostly European)
– started in 2004
– 78 members from 20 organizations
– W3C member submission in April 2005
www.wsmo.org
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
48
WSMO Framework & Working Groups
Conceptual Model &
Axiomatization for SWS
www.wsmo.org
Formal Language for WSMO
Ontology & Rule Language
for the Semantic Web
© SUPER 25.04.2020
Execution Environment
for WSMO
I-CENTRIC, Malta 2008
49
WSMO Top-level Elements
(http://www.wsmo.org)
Objectives that a client may have
when consulting a Web Service
Provide the formally
specified terminology
of the information used
by all other
components
Semantic description of
Web
Services:
- Capability (functional)
- Interfaces (usage)
Connectors between components
with
mediation facilities for handling
heterogeneities
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
50
WSMO Ontologies
• Ontologies are the ‘data model’ throughout WSMO
– all WSMO element descriptions rely on ontologies
– all data interchanged in Web Service usage are ontologies
– Semantic information processing & ontology reasoning
• WSMO Ontology Language WSML
– conceptual syntax for describing WSMO elements
– logical language for axiomatic expressions (WSML Layering)
• WSMO Ontology Design
– Modularization:
– De-Coupling:
© SUPER 25.04.2020
import / re-using ontologies, modular approach
for ontology design
heterogeneity handled by OO Mediators
I-CENTRIC, Malta 2008
51
Ontology Specification
•
•
Non functional properties
Imported Ontologies
•
Used mediators
author, date, ID, etc.
importing existing ontologies
where no heterogeneities arise
OO Mediators (ontology import with
terminology mismatch handling)
Ontology Elements:
Concepts
Attributes
Relations
Functions
Instances
set of entities that exists in the world / domain
set of attributes that belong to a concept
define interrelations between several concepts
special type of relation (unary range = return value)
set of instances that belong to the represented ontology
Axioms
axiomatic expressions in ontology (logical statement)
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
52
The Web Service Modelling Language
(WSML)
•
–
–
–
–
•
WSML Core: efficiency and compatibility
WSML DL: decidability, open world semantics
WSML Rule: efficient existing rule engines
WSML Full: unifying language, theorem proving
Static
Aspects
Dynamic
Aspects
Languages for dynamics
–
•
WSML
Ontology / Rule Languages
WSML Full
Transaction Logic over ASMs
Mapping languages
–
–
WSML Rule
for dynamics (process mediation)
for data (data mediation)
WSML DL
WSML Core
RDF (S)
XML
Unicode
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
URI
53
WSMO/WSML – Some Modelling
Examples
■ Concept example
concept phoneNumber
nonFunctionalProperties
dc#description hasValue "concept of a
phone number"
endNonFunctionalProperties
countryCode ofType _string
areaCode ofType _string
number ofType _string
■ Sub-concept example
concept mobilePhoneNumber subConceptOf
phoneNumber
nonFunctionalProperties
dc#description hasValue "concept of a
mobile phone number"
endNonFunctionalProperties
mobileProvider ofType Provider
© SUPER 25.04.2020
• Relation example
relation hasRoute(ofType routeDescription, ofType route)
nonFunctionalProperties
dc#description hasValue "Relation that holds between
a route description and a route"
endNonFunctionalProperties
■ Instance example
instance myPhoneNumber memberOf phoneNumber
countryCode hasValue “43“
areaCode hasValue “664“
number hasValue “49322607“
■ Axiom example
axiom ValidInformationQuality
definedBy
forall {?x} (
?x memberOf informationQualityType
implies
?x[value hasValue “low“] or
?x[value hasValue “high“]).
I-CENTRIC, Malta 2008
54
WSMO Web Service Description
- complete item description
- quality aspects
- Web Service Management
- Advertising of Web Service
- Support for WS Discovery
Non-functional Properties
Capability
DC + QoS + Version + financial
functional description
client-service
interaction interface
for consuming WS
- external visible
behavior
- communication
structure
- ‘grounding’
Web Service
Implementation
WS
(not of interest in Web
Service Description)
WS
Interface
© SUPER 25.04.2020
WS
realization of
functionality by
aggregation
- functional
decomposition
- WS composition
Orchestration
I-CENTRIC, Malta 2008
55
Web Service Description - Example
webService _"https://asg-platform.org/AttractionBooking/MobtelPhoneLocationService"
nfp
dc#title hasValue "MobtelPhoneLocationService"
dc#publisher hasValue "Mobtel“
dO#informQualityType hasValue "high"
endnfp
importsOntology _"https://asg-platform.org/AttractionBooking/domainOntology.wsml"
capability MobtelPhoneLocationServiceCapability
sharedVariables {?P}
precondition
definedBy
?P memberOf dO#phoneNumber.
postcondition
definedBy
?L memberOf dO#location
and
dO#hasLocation(?P,?L).
interface MobtelPhoneLocationServiceInterface
choreography MobtelPhoneLocationServiceChoreography
stateSignature
in
dO#phoneNumber withGrounding
ssWSDL#wsdl.interfaceMessageReference(MobtelPhoneLocationServicePortType/doIt/In)
out
dO#location withGrounding
ssWSDL#wsdl.interfaceMessageReference(MobtelPhoneLocationServicePortType/doIt/Out)
transitionRules
forAll{?P} with (?P memberOf dO#phoneNumber) do
add(?L memberOf dO#location and dO#hasLocation(?P,?L))
endForall
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
56
WSMO Goals – Purpose
Abstraction Layer for Problem-oriented WS usage
Dynamic WS usage
Client
objective / problem to be solved
Start
client-system interaction
Goals
formal objective description
Web
Service
discovery, composition, mediation
Semantics / SWS
Ontology
SWS description
Goal
Goal
Web
Service
Mediator
Web
Service
execution
End
End
Web Services & Resources
WS
© SUPER 25.04.2020
Internet
I-CENTRIC, Malta 2008
57
Goal Templates and Goal Instances
Service-Side
Client-Side
Goal Template
service detection
functional
generic objective description
defines
Goal Instance
concrete input
Ontology
© SUPER 25.04.2020
Ontology
service usage
behavioral
instantiates
Client
Domain Knowledge
I-CENTRIC, Malta 2008
(Web) Service
Implementation
(not of interest here)
Ontology
Ontology
58
Automated Web Service Usage
Goal
buy train ticket in Germany
- origion: o, destination: d
- date-time: dt
Mediator
client interface
DB
Ticketing
design time
instantiates
goal instance with inputs:
o = Munich, d = Berlin
dt = 20070319-1030
runtime
executes
defines
Client
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
59
SWS Techniques
•
Discovery
find candidate WS to solve a Goal
•
Selection & Ranking
select best candidate / determine a priority list
•
Composition
combine several WS to solve a Goal
•
Behavioral Compatibility
ensure that interaction can take place
•
Mediation
resolve & handle possibly occurring heterogeneities
•
Execution
automatically invoke & consume WS to solve a Goal
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
60
Automated Goal Solving with SWS
GOAL
if: successful
else:
not solvable
submission
else: try other WS
uses
Data
Mediator
Process
Mediator
matchmaking
R with all WS
Discoverer
if: composition possible
if: usable
Selection &
Ranking
uses
Composer
Behavioral
Conformance
uses
Service
Repository
composition
(executable)
if: compatible
information lookup
for particular service
Executor
if: execution
error
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
61
WSMO Reference Implementation
WSMX - The Web Service Execution Environment
• A Service Oriented Architecture
• Reference implementation of SESA and WSMO
• open source (LGPL): http://sourceforge.net/projects/wsmx/
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
62
WSMX Design & Properties
• Middleware for Semantic Web Services
– Allow service providers focus on their business
• Environment for goal-based Web service usage
– Run-time binding of service requester and provider
• Flexible Service Oriented Architecture
– Add, update, remove components at run-time as needed
• Open-source to encourage participation
– Developers are free to use in their own code
• Formal execution semantics
– Unambiguous model of system behaviour
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
63
Other WSMO Tools
www.wsmo.org/tools
• WSML (Specification Language)
www.wsmo.org/wsml
– conceptual language for WSMO
– ontology language with several variants
• WSMO Editors:
– WSML editors + validation
– WSMO Studio
– WSMO Visualizer
• Ontology Technology:
– WSML Reasoner (for DL and LP)
– Ontology Management Suite
– Data Mediator (incl. Abstract Mapping Language)
all: Eclipse plugins & open source (LGPL licence)
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
64
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
65
Integration - SUPER Approach
Alexander Simov
The Critical IT / Process Divide
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
67
SUPER Main Approach
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
68
Semantic BPM Lifecycle
■ Modelling – add semantic
(ontological) annotations to business
processes
■ Configuration – map from the
business model to an executable
process specification
■ Execution – process execution with
discovery & composition of SWS
■ Analysis – monitor, analyse &
improve processes
© SUPER 25/04/2020
I-CENTRIC, Malta 2008
Modelling Stack
·
·
·
Making sense of a domain\problem
Communication tool
What is it all about?
·
·
·
·
Service
Booking
form
Flight data
Receipt
booking
request
Check
booking
request
Mrs. Miller
Call
center
Booking
request
checked
Service
Flight
disposition
Service
Alternative
flight
offer
Booking
request
Mrs. Walker
Create
flight
booking
Plane
ticket
Flight
booking
created
Client data
Offer
alternative
flight
Visualizing\specifying business process
Focus: Business Problem
Who does what, when, how and why?
Usually multiple layers
Mr. Green
·
·
·
·
Process execution specification
·
Formal, clearly specified grammar
·
Focus: Implementation
Which component is called when, how, by
whom with which data?
·
·
·
Web service encapsulation
Focus: Implementation
Which components can and should be
exposed how as services?
·
·
WS*
...
·
Implementation of components
·
·
Programming languages
...
Flight
disposition
Alternative
flight
offered
<process name="Mediation Example - Ordering BPEL Snippet - 1" suppressJoinFailure="yes" targetNamespace="...">
<sequence>
<receive name="Initial_Receive" createInstance="true"/>
<invoke name="Invoke_Check_Order_Consistency"/>
<switch>
<case condition="bpws:getVariableData('consistency', '') = 'OK'">
<flow>
<invoke name="Invoke_Update_Provisioning_Systems_Subprocess"/>
<invoke name="Invoke_CustomerReply_Confirmation_Note"/>
</flow>
</case>
<otherwise>
<invoke name="Invoke_CustomerReply_Rejection_Note"/>
</otherwise>
</switch>
<reply name="Final_Reply"/>
</sequence>
</process>
© SUPER 25.04.2020
·
·
·
·
Service
I-CENTRIC, Malta 2008
·
·
Solution maps
Mind maps
Ad-hoc modelling
techniques
...
·
·
·
Business Scenario Maps
Event-driven process
chains
Flowchart techniques
BPMN
...
BPEL
...
70
Semantic
Business Process
Modelling
Text
SBP Modelling
Text
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
71
SBP Configuration
Text
Text
Semantic
Business Process
Configuration
Text
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
72
Text
SBP Execution
© SUPER 25.04.2020
Semantic
Business Process
Execution
I-CENTRIC, Malta 2008
Text
Text
73
Semantic
Business Process
Analysis
Text
SBP Analysis
Text
Text
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
74
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
75
75
Integration - SUPER Approach
SUPER Ontology Stack
Agata Filipowska
Current Ontology Stack
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
77
Current Ontology Stack
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
78
UPO
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
79
Current Ontology Stack
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
80
BPMO
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
81
Current Ontology Stack
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
82
sBPEL
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
83
Current Ontology Stack
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
84
sRBE Analysis Process
RBE Ontology
I am interested in
an as-is analysis of
the supply chain
management
Scenario Ontology
Business Function Ontology
Business Question Repository
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
85
Ontology Stack
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
86
Organisational Cloud
D.1.2 and D.1.6
Organisational
Ontologies
E.g. YATOSP
Framework
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
87
Organisational Cloud
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
88
Organisational Structure Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
89
Business Roles Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
90
Organisational Units Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
91
Business Resources Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
92
Business Policies and Rules Ontology – work
in progress
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
93
BFO Purpose
• Business Functions Ontology (BFO)
– Provides domain-independent vocabulary.
– Introduces a robust taxonomy of organization-related functions.
• BFO aims at the precise categorization of functions and activities
taking place in an organization in order to enable and facilitate the
enterprise description on the process level.
• A Business Function is any functional area of / or related to an
enterprise e.g. Human Resources, Sales Management, etc.
• An Activity is unit of work identified with given business process e.g.
Block Sales Order, Change Sales Order, etc.
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
94
BFO Facts & numbers
• BFO is conceptually based on the SAP Business Maps Ontology:
–
More than 23000 instances.
–
–
2807 names for functions and activities were filtered out, in the second step 1578 were chosen.
More than 580 candidates were found irrelevant or in close synonymy to concepts already included.
• The final version of BFO consists of 32 axioms and 960 concepts
divided into 14 functional areas and their peer activity substructures:
► AssetManagement
► MasterDataManagement
► BusinessOpportunityManagement,
► ProductManagement
► CustomerManagement
► ProductProductionManagement
► FinanceManagement
► ProjectManagement
► GlobalTradeManagement
► RiskManagement,
► HumanResourcesManagement
► SupplyManagement
► MarketingManagement
► SalesAndDistribution.
■ The maximum depth of the taxonomical hierarchy is 5.
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
95
BFO Structure
• BFO consists of 2 parallel structures:
–
–
Function structure - reflects main functional areas of the company.
ActivityOrStep structure – reflects activities, steps or sub-phases that are conducted within the functions.
• ActivityOrStep is connected with proper Function via isSubPhaseOf
attribute.
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
96
Business Function Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
97
Business Strategy Ontology
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
98
Business Goals Ontology
• Business Goals Ontology provides a
standard set of properties and relations
used in modelling a hierarchy of
organisational business goals and enables
formal verification of goal specifications
• Business goal - state of the enterprise that
an action, or a given set of actions, is
intended to achieve
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
99
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
100
100
Integration - SUPER Approach
SUPER Architecture
Alexander Simov
Architecture: Structural Overview
SUPER Execution
Semantic
BPEL
Execution
Engine
SUPER Tooling
Semantic
Execution
Environment
Modelling
Tool
Monitoring &
Management
Tool
Semantic Service Bus
Analysis Tool
Deployment
Event Sink
Protocol Binder
SBP
Composition
SBP Process
Mediation
Business
Process Library
SBP Discovery
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
Transformation
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
102
Architecture: Tools
SUPER Execution
Semantic
BPEL
Execution
Engine
SUPER Tooling
Semantic
Execution
Environment
Modelling
Tool
Monitoring &
Management
Tool
Semantic Service Bus
Analysis Tool
Deployment
Event Sink
Protocol Binder
SBP
Composition
SBP Process
Mediation
Business
Process Library
SBP Discovery
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
Transformation
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
103
Architecture: Execution Environment
SUPER Execution
Semantic
BPEL
Execution
Engine
SUPER Tooling
Semantic
Execution
Environment
Modelling
Tool
Monitoring &
Management
Tool
Semantic Service Bus
Analysis Tool
Deployment
Event Sink
Protocol Binder
SBP
Composition
SBP Process
Mediation
Business
Process Library
SBP Discovery
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
Transformation
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
104
Architecture: Platform Services
SUPER Execution
Semantic
BPEL
Execution
Engine
SUPER Tooling
Semantic
Execution
Environment
Modelling
Tool
Monitoring &
Management
Tool
Semantic Service Bus
Analysis Tool
Deployment
Event Sink
Protocol Binder
SBP
Composition
SBP Process
Mediation
Business
Process Library
SBP Discovery
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
Transformation
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
105
Architecture: Repositories
SUPER Execution
Semantic
BPEL
Execution
Engine
SUPER Tooling
Semantic
Execution
Environment
Modelling
Tool
Monitoring &
Management
Tool
Semantic Service Bus
Analysis Tool
Deployment
Event Sink
Protocol Binder
SBP
Composition
SBP Process
Mediation
Business
Process Library
SBP Discovery
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
Transformation
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
106
Architecture: Semantic Service Bus
SUPER Execution
Semantic
BPEL
Execution
Engine
SUPER Tooling
Semantic
Execution
Environment
Modelling
Tool
Monitoring &
Management
Tool
Semantic Service Bus
Analysis Tool
Deployment
Event Sink
Protocol Binder
SBP
Composition
SBP Process
Mediation
Business
Process Library
SBP Discovery
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
Transformation
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
107
Architecture Behavioural Perspective: SBP
Deployment
BPEL4SWS
WSDL
Semantic Process
Artefacts Bundle
(SPAB)
WSMO
WSDL
WSMO Mediators
WSMO
Goals
Deployment
descriptor
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
108
Architecture Behavioural Perspective: SBP
Deployment
SUPER Execution
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
Modelling
SPAB
Tool
Semantic Service Bus
BPEL4SWS
WSDL
Deployment
WSMO
WSDL
WSMO
Goals
WSMO
Mediators
Business
Process Library
Semantic Web
Services
Repository
Deployment
Descriptor
Execution
History
SUPER Repositories
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
109
Architecture Behavioural Perspective: SBP
Execution
SUPER Execution
Semantic
BPEL
Execution
Engine
1 Execute
Task
Semantic
Execution
Environment
Web
Service
Event Sink
Protocol Binder
Business
Process Library
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
110
Architecture Behavioural Perspective: SBP
Execution
SUPER Execution
Semantic
BPEL
Execution
Engine
1 Execute
Task
Semantic
Execution
Environment
Web
Service
Event Sink
2 Discover and
Select Service
Protocol Binder
Business
Process Library
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
111
Architecture Behavioural Perspective: SBP
Execution
1 Execute
Task
SUPER Execution
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
Web
Service
Event Sink
2 Discover and
Select Service
Protocol Binder
3 Mediate
Data
Business
Process Library
Data Mediation
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
112
Architecture Behavioural Perspective: SBP
Execution
1 Execute
Task
SUPER Execution
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
Web
Service
2 Discover and
Select Service
4 Invoke Service
Protocol Binder
3 Mediate
Data
Business
Process Library
Data Mediation
Event Sink
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
113
Architecture Behavioural Perspective: SBP
Execution
1 Execute
Task
SUPER Execution
Semantic
BPEL
Execution
Engine
Semantic
Execution
Environment
Web
Service
2 Discover and
Select Service
4 Invoke Service
Protocol Binder
3/5 Mediate
Data
Business
Process Library
Data Mediation
Event Sink
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
114
Architecture Behavioural Perspective: SBP
Execution
1 Execute
Task
SUPER Execution
Semantic
BPEL
Execution
Engine
6
Semantic
Execution
Environment
Web
Service
Return Result
2 Discover and
Select Service
4 Invoke Service
Protocol Binder
3/5 Mediate
Data
Business
Process Library
Data Mediation
Event Sink
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
115
Architecture Behavioural Perspective: SBP
Execution
1 Execute
Task
SUPER Execution
Semantic
BPEL
Execution
Engine
6
Semantic
Execution
Environment
Generate Events
Web
Service
Return Result
2 Discover and
Select Service
4 Invoke Service
Protocol Binder
3/5 Mediate
Data
Business
Process Library
Data Mediation
Event Sink
Semantic Web
Services
Repository
Execution
History
SUPER Repositories
SBP Reasoner
SUPER Platform Services
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
116
Agenda
1. Introduction: The Need of Semantics in BPM
2. Business Process Management
■ Introduction
■ Process Execution with BPEL
3. Semantic Web Services
■ Introduction
■ SWS Technologies
4. Integration: The SUPER Approach
■ SUPER Ontology Stack
■ SUPER Architecture
5. SUPER Demonstration
© SUPER 25.04.2020
I-CENTRIC, Malta 2008
117
SUPER Demonstration
Alexander Simov
More information
• http://www.ip-super.org
• Contact person:
– Agata Filipowska
– [email protected]