Semantic Management of Business Processes in the Future Internet at I-CENTRIC 2008 Sliema, Malta...
-
Upload
edgar-gardner -
Category
Documents
-
view
213 -
download
0
Transcript of Semantic Management of Business Processes in the Future Internet at I-CENTRIC 2008 Sliema, Malta...
Semantic Management
of Business Processes
in the Future Internet
at I-CENTRIC 2008
Sliema, Malta
October 26th, 2008
Presenters
• Agata Filipowska (Poznan University of Economics, Poland)
• Dumitru Roman (STI Innsbruck, Austria)
• Alexander Simov (Ontotext lab., Bulgaria)
© SUPER 19.04.23 2I-CENTRIC, Malta 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 19.04.23 3I-CENTRIC, Malta 2008
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 19.04.23 11I-CENTRIC, Malta 2008
Matching Activities and Port Types Based on Semantics
Semantic Web Services
© SUPER 19.04.23 14I-CENTRIC, Malta 2008
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 19.04.23 16I-CENTRIC, Malta 2008
BusinessProcess
Management(BPM)
Office Automation(since 1980)
Workflow Systems(since 1985)
CSCW / Groupware /Workgroup Systems
EAI(since 1990)
Business Reengineering(since 1990)
Continuous Improvements(since 1990)
Business Process Modelling(since 1990)
Business Process Mngt.(since 2000)
Business Objects(since 2000)
SOA(since 2000)
BPM’s Parents and Definition
© SUPER 19.04.23 17I-CENTRIC, Malta 2008
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.”
What (Data)
How (Function)
Where (Network)
Who (People)
When Why
Models 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 19.04.23 18I-CENTRIC, Malta 2008
Enterprise Model
PurchaseOrder
ReceivedSYS
GetPurchaseOrder
PurchaseOrder
Extracted
SYS
Load ContentContent
Ready forDownload
SYS
Get License LicenseAvailable
SYS
Send Content& License
PurchaseOrder
Satisfied
© SUPER 19.04.23 19I-CENTRIC, Malta 2008
PurchaseOrder
ReceivedSYS
GetPurchaseOrder
Cell Phone
PurchaseOrder
Extracted
SYS
Load ContentContent
Ready forDownload
SYS
Get License LicenseAvailable
SYS
Send Content& License
PurchaseOrder
Satisfied
Cell Phone
Enterprise Model
© SUPER 19.04.23 20I-CENTRIC, Malta 2008
PurchaseOrder
ReceivedSYS
GetPurchaseOrder
Cell Phone
Customer
PurchaseOrder
Extracted
SYS
Load ContentContent
Ready forDownload
SYS
Get License LicenseAvailable
SYS
Send Content& License
PurchaseOrder
Satisfied
DigitalContent
Customer License
DigitalContent
License
Cell Phone
ContentIdentifier
ContentIdentifier
Enterprise Model
© SUPER 19.04.23 21I-CENTRIC, Malta 2008
PurchaseOrder
ReceivedSYS
GetPurchaseOrder
Cell Phone
Customer
PurchaseOrder
Extracted
SYS
Load ContentContent
Ready forDownload
SYS
Get License LicenseAvailable
SYS
Send Content& License
PurchaseOrder
Satisfied
DigitalContent
Customer License
DigitalContent
License
Cell Phone
Cell PhoneInterfaceService
ContentIdentifier
ContentIdentifier
ContentLibraryService
LicenseService
Cell PhoneInterfaceService
Enterprise Model
© SUPER 19.04.23 22I-CENTRIC, Malta 2008
PurchaseOrder
ReceivedSYS
GetPurchaseOrder
Cell Phone
Customer
PurchaseOrder
Extracted
SYS
Load ContentContent
Ready forDownload
SYS
Get License LicenseAvailable
SYS
Send Content& License
PurchaseOrder
Satisfied
DigitalContent
Customer License
DigitalContent
License
Cell Phone
Cell PhoneInterfaceService
ContentProvider
ContentIdentifier
ContentIdentifier
ContentLibraryService
LicenseService
SalesDepartment
Cell PhoneInterfaceService
IT DepartmentIT Department
Enterprise Model
© SUPER 19.04.23 24I-CENTRIC, Malta 2008
• 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
Enterprise Model
© SUPER 19.04.23 25I-CENTRIC, Malta 2008
• 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)– ...
Enterprise Model
© SUPER 19.04.23 26I-CENTRIC, Malta 2008
Process Lifecycle
• enterprise model evolves lifecycle• based on general Deming cycle for continuous process
improvements• sometimes also named Shewhart cycle
1. Plan
2. Do
3. Check
4. Act
© SUPER 19.04.23 27I-CENTRIC, Malta 2008
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 19.04.23 28I-CENTRIC, Malta 2008
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 19.04.23 30I-CENTRIC, Malta 2008
BPM Applications
Business Experts’ Perspective: Processes
IT Implementation Perspective
Process Implementation
Querying the Process Space Manual Labor
© SUPER 19.04.23 31I-CENTRIC, Malta 2008
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 19.04.23 32I-CENTRIC, Malta 2008
BPEL Web Service composition
• BPEL process composes (uses) Web services
© SUPER 19.04.23 33I-CENTRIC, Malta 2008
Business Processes as Web services
• BPEL Process is also a Web service– functionality in terms of WSDL port types and operations
© SUPER 19.04.23 34I-CENTRIC, Malta 2008
* Receive may cause an Instantiation of a Process
BPEL Document
BPEL Engine
Process Definition
Execution via the Navigator
Process Instance
...Deployment
Instantiation
Process Lifecycle within the Engine
Invo
catio
n an
d M
ana
ge-
men
t F
ram
ewor
k
Receive*
Reply
© SUPER 19.04.23 35I-CENTRIC, Malta 2008
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 19.04.23 37I-CENTRIC, Malta 2008
WWWURI, HTML, HTTP
Semantic WebRDF, RDF(S), OWL
Dynamic Web ServicesUDDI, WSDL, SOAP
Static
Semantic WebServices
Semantics for the WWW
© SUPER 19.04.23 38I-CENTRIC, Malta 2008
• next generation of the Internet (augmentation of the WWW)
• information has machine-processable and machine-understandable semantics
• ontologies as base technology for semantic interoperability
RDF OWL XML DBWebAppl.
ontology ontology ontology
semantic bridges
The Semantic Web
© SUPER 19.04.23 39I-CENTRIC, Malta 2008
Ontology Definition
formal, explicit specification of a shared conceptualization
commonly accepted understanding
conceptual model of a domain
(ontological theory)
unambiguous terminology definitions
machine-readability with computational
semantics
© SUPER 19.04.23 40I-CENTRIC, Malta 2008
Concept conceptual entity of the domain
Property attribute describing a concept
Relation relationship between concepts or properties
Axiom coherency description between Concepts / Properties / Relations via logical expressions
Instance individual in the domain
Person
Student Professor
Lecture
isA – hierarchy (taxonomy)
name email
studentID
researchfield
topiclecture
no.
attends holds
holds(Professor, Lecture) =>Lecture.topic = Professor.researchField
Ann memberOf student name = Ann Lee studentID = 12345
Ontology Example
© SUPER 19.04.23 43I-CENTRIC, Malta 2008
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 Web Service Description Language
2. SOAP XML data exchange protocol for the Web
3. UDDI registry for Web Services
© SUPER 19.04.23 44I-CENTRIC, Malta 2008
The Web Service Usage Process
Repository
ConsumerWeb
Service
WSDL
SOAP
find usable Web Service
WS usage via message exchange
points to
describes
© SUPER 19.04.23 45I-CENTRIC, Malta 2008
• 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
Deficiencies of WS Technology
© SUPER 19.04.23 46I-CENTRIC, Malta 2008
Semantic Web Services
• automate Web Service technologies by 1. rich, formal annotation of Web Services
2. automated detection and execution of Web services
• integration with the Semantic Web – 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 19.04.23 47I-CENTRIC, Malta 2008
Web ServiceImplementation(not of interest in Web Service Description)
Interface
Functionality
WS
WS
Non-functional
WS
Aggregation
Web ServiceImplementation(not of interest in Web Service Description)
Ontology Ontology
XML
Ontology
Interface
a) Web Service Description Structure b) Semantic Web Service Description Structure
Semantic Web Services
© SUPER 19.04.23 48I-CENTRIC, Malta 2008
• 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
Web Service Modeling Ontology (WSMO)
© SUPER 19.04.23 49I-CENTRIC, Malta 2008
WSMO Framework & Working Groups
Conceptual Model & Axiomatization for SWS
Formal Language for WSMO
Ontology & Rule Language for the Semantic Web
Execution Environment for WSMO
www.wsmo.org
© SUPER 19.04.23 50I-CENTRIC, Malta 2008
Objectives that a client may havewhen consulting a Web Service
Provide the formallyspecified terminologyof the information usedby all other components
Semantic description of WebServices: - Capability (functional)- Interfaces (usage)
Connectors between components withmediation facilities for handling heterogeneities
WSMO Top-level Elements
(http://www.wsmo.org)
© SUPER 19.04.23 51I-CENTRIC, Malta 2008
• 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: import / re-using ontologies, modular approach
for ontology design – De-Coupling: heterogeneity handled by OO Mediators
WSMO Ontologies
© SUPER 19.04.23 52I-CENTRIC, Malta 2008
• Non functional properties author, date, ID, etc.
• Imported Ontologies importing existing ontologies where no heterogeneities arise
• Used mediators OO Mediators (ontology import with terminology mismatch handling)
Ontology Elements:Concepts set of entities that exists in the world / domain
Attributes set of attributes that belong to a concept
Relations define interrelations between several concepts
Functions special type of relation (unary range = return value)
Instances set of instances that belong to the represented ontology
Axioms axiomatic expressions in ontology (logical statement)
Ontology Specification
© SUPER 19.04.23 53I-CENTRIC, Malta 2008
The Web Service Modelling Language (WSML)
• Ontology / Rule Languages– WSML Core: efficiency and compatibility
– WSML DL: decidability, open world semantics
– WSML Rule: efficient existing rule engines
– WSML Full: unifying language, theorem proving
• Languages for dynamics – Transaction Logic over ASMs
• Mapping languages– for dynamics (process mediation)
– for data (data mediation)
URIUnicode
XML
RDF (S)
WSML Core
WSML DLWSML Rule
WSML Full
Static Aspects
Dynamic Aspects
WSML
© SUPER 19.04.23 54I-CENTRIC, Malta 2008
WSMO/WSML – Some Modelling Examples
■ Concept exampleconcept phoneNumber nonFunctionalProperties dc#description hasValue "concept of a
phone number" endNonFunctionalProperties countryCode ofType _string areaCode ofType _string number ofType _string
• Relation example relation hasRoute(ofType routeDescription, ofType route) nonFunctionalProperties dc#description hasValue "Relation that holds between
a route description and a route" endNonFunctionalProperties
■ Axiom example axiom ValidInformationQuality definedBy forall {?x} ( ?x memberOf informationQualityType
implies ?x[value hasValue “low“] or
?x[value hasValue “high“]).
■ Instance exampleinstance myPhoneNumber memberOf phoneNumber countryCode hasValue “43“ areaCode hasValue “664“ number hasValue “49322607“
■ Sub-concept exampleconcept mobilePhoneNumber
subConceptOf phoneNumber nonFunctionalProperties dc#description hasValue "concept of a
mobile phone number" endNonFunctionalProperties mobileProvider ofType Provider
© SUPER 19.04.23 55I-CENTRIC, Malta 2008
Web ServiceImplementation(not of interest in Web Service Description)
Capability
functional description
WS
WS
- Advertising of Web Service- Support for WS Discovery
client-service interaction interface for consuming WS - external visible behavior- communication structure - ‘grounding’
realization of functionality by aggregation- functional decomposition - WS composition
Non-functional Properties
DC + QoS + Version + financial
- complete item description- quality aspects - Web Service Management
WS
Orchestration
WSMO Web Service Description
Interface
© SUPER 19.04.23 56I-CENTRIC, Malta 2008
Web Service Description - Example
webService _"https://asg-platform.org/AttractionBooking/MobtelPhoneLocationService"nfp
dc#title hasValue "MobtelPhoneLocationService"dc#publisher hasValue "Mobtel“dO#informQualityType hasValue "high"
endnfpimportsOntology _"https://asg-platform.org/AttractionBooking/domainOntology.wsml"capability MobtelPhoneLocationServiceCapability
sharedVariables {?P}precondition
definedBy ?P memberOf dO#phoneNumber.
postconditiondefinedBy
?L memberOf dO#location and dO#hasLocation(?P,?L).
interface MobtelPhoneLocationServiceInterfacechoreography 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 19.04.23 57I-CENTRIC, Malta 2008
WSMO Goals – Purpose
client-system interaction
discovery, composition, mediation
Client objective / problem to be solved
Goalsformal objective description
Semantics / SWS
Ontology SWS description
Mediator
Web Services & Resources
WS Internet
execution
End
Start
Web Service
GoalGoalWeb
Service
Web Service
End
Abstraction Layer for Problem-oriented WS usage Dynamic WS usage
© SUPER 19.04.23 58I-CENTRIC, Malta 2008
Goal Templates and Goal Instances
Client
Goal Templategeneric objective description
Goal Instanceconcrete input
instantiates
defines
(Web) ServiceImplementation
(not of interest here)
functional
beh
avioral
service detection
Client-Side Service-Side
Domain Knowledge Ontology OntologyOntology Ontology
service usage
© SUPER 19.04.23 59I-CENTRIC, Malta 2008
Automated Web Service Usage
Client
Goal
buy train ticket in Germany- origion: o, destination: d- date-time: dt
client interface
goal instance with inputs: o = Munich, d = Berlindt = 20070319-1030
defines
instantiates
design time
runtime
executes
DB Ticketing
Mediator
© SUPER 19.04.23 60I-CENTRIC, Malta 2008
SWS Techniques
• Discoveryfind candidate WS to solve a Goal
• Selection & Ranking select best candidate / determine a priority list
• Compositioncombine several WS to solve a Goal
• Behavioral Compatibilityensure that interaction can take place
• Mediationresolve & handle possibly occurring heterogeneities
• Executionautomatically invoke & consume WS to solve a Goal
© SUPER 19.04.23 61I-CENTRIC, Malta 2008
Automated Goal Solving with SWS
GOAL
Discoverer
BehavioralConformance
Data Mediator
ProcessMediator
Executor
if: usableif: composition possible
uses
matchmaking R with all WS
composition (executable)
uses
submission
if: compatible
if: successful
if: executionerror
information lookup for particular service
else: not solvable
Service Repository
uses
Selection &Ranking
Composer
else: try other WS
© SUPER 19.04.23 62I-CENTRIC, Malta 2008
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 19.04.23 63I-CENTRIC, Malta 2008
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 19.04.23 64I-CENTRIC, Malta 2008
Other WSMO Toolswww.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 19.04.23 65I-CENTRIC, Malta 2008
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 19/04/23 I-CENTRIC, Malta 2008
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 19.04.23 70I-CENTRIC, Malta 2008
· Solution maps· Mind maps· Ad-hoc modelling
techniques· ...
· Making sense of a domain\problem· Communication tool· What is it all about?
· Visualizing\specifying business process· Focus: Business Problem· Who does what, when, how and why?· Usually multiple layers
· Business Scenario Maps· Event-driven process
chains· Flowchart techniques· BPMN· ...
PlaneticketServicePlaneticketPlaneticketService
Alternativeflightoffer
ServiceAlternative
flightoffer
Alternativeflightoffer
ServiceBookingrequestServiceBookingrequestBookingrequestService
BookingformService
Bookingform
BookingformService
Receiptbookingrequest
Receiptbookingrequest
Checkbookingrequest
Checkbookingrequest
Bookingrequestchecked
Bookingrequestchecked
Callcenter
Callcenter
Flightdisposition
Flightdisposition
Flightdisposition
Flightdisposition
Offeralternative
flight
Offeralternative
flight
Createflight
booking
Createflight
booking
Flightbookingcreated
Flightbookingcreated
Alternativeflight
offered
Alternativeflight
offered
Flight dataFlight data
Client dataClient data
Mrs. MillerMrs. Miller
Mrs. WalkerMrs. Walker Mr. GreenMr. Green
<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>
· Process execution specification· Formal, clearly specified grammar· Focus: Implementation· Which component is called when, how, by
whom with which data?
· BPEL· ...
· Web service encapsulation· Focus: Implementation· Which components can and should be
exposed how as services?
· WS*· ...
· Implementation of components · Programming languages· ...
Modelling Stack
© SUPER 19.04.23 72I-CENTRIC, Malta 2008
SBP ConfigurationText Text
Text
Semantic Business Process
Configuration
© SUPER 19.04.23 73I-CENTRIC, Malta 2008
SBP ExecutionText Text
Text
Semantic Business Process
Execution
© SUPER 19.04.23 74I-CENTRIC, Malta 2008
SBP Analysis Text Text
Text
Semantic Business Process
Analysis
© SUPER 19.04.23 75I-CENTRIC, Malta 2008 75
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 19.04.23 85I-CENTRIC, Malta 2008
Scenario Ontology Business Function Ontology
RBE OntologyI am interested in
an as-is analysis of the supply chain
management
sRBE Analysis Process
Business Question Repository
© SUPER 19.04.23 87I-CENTRIC, Malta 2008
Organisational Cloud
E.g. YATOSP Framework
D.1.2 and D.1.6 Organisational Ontologies
© SUPER 19.04.23 94I-CENTRIC, Malta 2008
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 19.04.23 95I-CENTRIC, Malta 2008
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 sub-structures:
■ The maximum depth of the taxonomical hierarchy is 5.
© SUPER 19.04.23 96I-CENTRIC, Malta 2008
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 19.04.23 99I-CENTRIC, Malta 2008
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 19.04.23 100I-CENTRIC, Malta 2008 100
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 19.04.23 102I-CENTRIC, Malta 2008
SemanticBPEL
ExecutionEngine
SBPComposition
SemanticExecution
Environment
ModellingTool
Monitoring & Management
ToolAnalysis Tool
SUPER Execution SUPER Tooling
SBP ProcessMediation
SBP Discovery Data Mediation
SBP Reasoner Transformation
SUPER Platform Services
SUPER Repositories
Deployment
Event Sink
Protocol Binder
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Semantic Service Bus
Architecture: Structural Overview
© SUPER 19.04.23 103I-CENTRIC, Malta 2008
SemanticBPEL
ExecutionEngine
SBPComposition
SemanticExecution
Environment
SUPER Execution
SBP ProcessMediation
SBP Discovery Data Mediation
SBP Reasoner Transformation
SUPER Platform Services
SUPER Repositories
Deployment
Event Sink
Protocol Binder
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Semantic Service Bus
ModellingTool
Monitoring & Management
ToolAnalysis Tool
SUPER Tooling
Architecture: Tools
© SUPER 19.04.23 104I-CENTRIC, Malta 2008
SBPComposition
ModellingTool
Monitoring & Management
ToolAnalysis Tool
SUPER Tooling
SBP ProcessMediation
SBP Discovery Data Mediation
SBP Reasoner Transformation
SUPER Platform Services
SUPER Repositories
Deployment
Event Sink
Protocol Binder
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Semantic Service Bus
SemanticBPEL
ExecutionEngine
SemanticExecution
Environment
SUPER Execution
Architecture: Execution Environment
© SUPER 19.04.23 105I-CENTRIC, Malta 2008
SemanticBPEL
ExecutionEngine
SemanticExecution
Environment
ModellingTool
Monitoring & Management
ToolAnalysis Tool
SUPER Execution SUPER Tooling
SUPER Repositories
Deployment
Event Sink
Protocol Binder
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Semantic Service Bus
SBPComposition
SBP ProcessMediation
SBP Discovery Data Mediation
SBP Reasoner Transformation
SUPER Platform Services
Architecture: Platform Services
© SUPER 19.04.23 106I-CENTRIC, Malta 2008
SemanticBPEL
ExecutionEngine
SBPComposition
SemanticExecution
Environment
ModellingTool
Monitoring & Management
ToolAnalysis Tool
SUPER Execution SUPER Tooling
SBP ProcessMediation
SBP Discovery Data Mediation
SBP Reasoner Transformation
SUPER Platform Services
Deployment
Event Sink
Protocol Binder
Semantic Service Bus
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Architecture: Repositories
© SUPER 19.04.23 107I-CENTRIC, Malta 2008
SemanticBPEL
ExecutionEngine
SBPComposition
SemanticExecution
Environment
ModellingTool
Monitoring & Management
ToolAnalysis Tool
SUPER Execution SUPER Tooling
SBP ProcessMediation
SBP Discovery Data Mediation
SBP Reasoner Transformation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Deployment
Event Sink
Protocol Binder
Semantic Service Bus
Architecture: Semantic Service Bus
© SUPER 19.04.23 108I-CENTRIC, Malta 2008
BPEL4SWS
WSDL
Deploymentdescriptor
WSMO Mediators
WSMOGoals
WSMO WSDL
Semantic ProcessArtefacts Bundle
(SPAB)
Architecture Behavioural Perspective: SBP Deployment
© SUPER 19.04.23 109I-CENTRIC, Malta 2008
SemanticBPEL
ExecutionEngine
SemanticExecution
Environment
ModellingTool
SUPER Execution
SUPER Repositories
Deployment
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Semantic Service Bus
BPEL4SWS WSDLDeploymentDescriptor
WSMOMediators
S P A B
WSMOGoals
Architecture Behavioural Perspective: SBP Deployment
WSMOWSDL
© SUPER 19.04.23 110I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Architecture Behavioural Perspective: SBP Execution
SemanticExecution
Environment
1 Execute Task
SemanticBPEL
ExecutionEngine
SBP Reasoner
Protocol Binder
Web Service
Event Sink
SUPER Execution
© SUPER 19.04.23 111I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
Architecture Behavioural Perspective: SBP Execution
SemanticExecution
Environment
1 Execute Task
2
SemanticBPEL
ExecutionEngine
SBP Reasoner
Protocol Binder
Discover and Select Service
Web Service
Event Sink
SUPER Execution
© SUPER 19.04.23 112I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
SemanticExecution
Environment
1 Execute Task
2
SemanticBPEL
ExecutionEngine
SBP Reasoner
3 MediateData
Protocol Binder
Discover and Select Service
Web Service
Event Sink
SUPER Execution
Architecture Behavioural Perspective: SBP Execution
© SUPER 19.04.23 113I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
SemanticExecution
Environment
4 Invoke Service
1 Execute Task
2
SemanticBPEL
ExecutionEngine
SBP Reasoner
3 MediateData
Protocol Binder
Discover and Select Service
Web Service
Event Sink
SUPER Execution
Architecture Behavioural Perspective: SBP Execution
© SUPER 19.04.23 114I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
SemanticExecution
Environment
4 Invoke Service
1 Execute Task
2
SemanticBPEL
ExecutionEngine
SBP Reasoner
3/5 MediateData
Protocol Binder
Discover and Select Service
Web Service
Event Sink
SUPER Execution
Architecture Behavioural Perspective: SBP Execution
© SUPER 19.04.23 115I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
SemanticExecution
Environment
4 Invoke Service
1 Execute Task
2
6
SemanticBPEL
ExecutionEngine
SBP Reasoner
3/5 MediateData
Return Result
Protocol Binder
Discover and Select Service
Web Service
Event Sink
SUPER Execution
Architecture Behavioural Perspective: SBP Execution
© SUPER 19.04.23 116I-CENTRIC, Malta 2008
Data Mediation
SUPER Platform Services
SUPER Repositories
Business Process Library
Semantic WebServices
Repository
ExecutionHistory
SemanticExecution
Environment
4 Invoke Service
1 Execute Task
2
6
SemanticBPEL
ExecutionEngine
SBP Reasoner
3/5 MediateData
Return Result
Protocol Binder
Discover and Select Service
Web Service
Event Sink
SUPER Execution
Generate Events
Architecture Behavioural Perspective: SBP Execution
© SUPER 19.04.23 117I-CENTRIC, Malta 2008
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