SUPER

  • http://www.ip-super.org/



SUPER – Introductory Demo/Video



SUPER

  • SUPER = Semantics Utilized for Process management within and between Enterprises (SUPER)
  • The major objective of SUPER was to raise Business Process Management (BPM) to the business level, where it belongs, from the IT level where it mostly resides now. 
  • This objective requires that BPM is accessible at the level of semantics of business experts



Business Process and Business Process Management

  • “A business process or business method is a collection of related, structure activities or tasks that produce a specific service or product for a particular customer or customers.”
  • “Business process management (BPM) is a management approach focused on aligning all aspects of an organization with the wants and needs of clients. It is a holistic approach that promotes business effectiveness and efficiency while striving for innovation, flexibility, and integration with technology”


Business process in a company

  • Business Processes
    • ... drive all company‘s activities 
    • ... represent the core assets of a company
    • ... give decision makers control over the company’s activities
    • ... deliver services faster and more efficiently to the customer
    • ... allow a company to react to changing market conditions



The critical Business / IT Divide



  • SUPER approach to address the critical Business / IT Divide



SUPER – How Semantics Help

  • Semantic technology improves the utility of BPM by creating a semantic "glue" between different layers, artefacts and models
  • Links between business artefacts help to keep the "big picture" and to improve the overall understanding of complex relationships and interdependencies
  • By unifying the vocabulary and explicating differences in a structured way, semantics support the understanding of business people and technicians


SUPER – Scientific objectives

  • Construction and assessment of technological framework for Semantic Business Process Management (SBPM)
  • Acquiring new generic languages suited for representation of processes, different  process models and goal description having in mind all aspects of system behaviour (e.g. costs, dependencies, constraints, other data flows, time limitations)
  • Creation of automated annotation techniques of already existing BPs, their fragments,  IT components, etc
  • Development of process query tools
  • Adjustment existing reasoners to the specific needs of SUPER
  • Elaboration of industrial-strength mediation procedures for automated coupling between business and IT perspectives
  • Augmentation of SWS foundations on the basis of new experiences obtained from their deployment to large-scale test environments


SUPER – Technical objectives

  • Building horizontal ontologies in aim to annotate both complete BPs and their fragments
  • Assembling vertical ontologies for the chosen implementation domain
  • Complete inventory of tools supporting every stage of SBPM


SUPER Ontology Stack




SUPER Ontology Stack (cont')




WSMO



SUPER Ontology Stack (cont')



Business Domain Ontologies

  • Business Functions Ontology – describes functions carried out within the company (e.g. marketing, finance, HR
  • Business Process Resources Ontology – describes tangible and abstract resources required
  • Business Roles Ontology – roles in the organization (e.g. Designer, Process Modeler, IT Expert, CEO)
  • Business Modeling Guidelines Ontology – generic business policies and rules for domains like law, finance, etc.


SUPER Ontology Stack (cont')



SUPER Ontology Stack (cont')

  • Upper-Level Process Ontology (UPO) represent high-level concepts for Business Process Modelling. It is the top-level ontology in SUPER, used as the unifying ontology for other ontologies
  • Business Process Modelling Ontology (BPMO) represent high-level business process workflows. BPMO has a bridging purpose between the business level and the execution level of processes
  • Semantic Event-driven Process Chains notation Ontology (sEPC) aims to support the annotation (automatic or semi-automatic) of process models created with EPC tools


SUPER Ontology Stack (cont')



SUPER Ontology Stack (cont')

  • Semantic Business Process Modeling Notation Ontology (sBPMN) formalises the core subset of BPMN graphical notation
  • Semantic BPEL Ontology (sBPEL) extends the BPEL ontology with a SWS based interaction model.
  • Behavioral Reasoning Ontology (BRO) allows for reasoning over the behaviours of business processes using WSML axioms
  • Events Ontology (EVO) is a reference model for capturing logging information utilised both by the execution engines (SBPELEE and SEE) and by the analysis tools



SUPER Architecture



SUPER Architecture (cont')


  • The central component of the architecture is the Semantic Service Bus (SSB) which provides a communication infrastructure for the SUPER components. Components communicate over the bus by sending and receiving normalized messages.
  • SUPER Tooling comprises tools to support different phases of the Semantic Business Process (SBP) lifecycle:

    • SBP Modeling Tool - used during the design time for SBP modeling

    • SBP Monitoring and Management Tool provides an up-to-date picture over the SBP and Semantic Web services (SWS) execution state and provides simple management functionality

    • SBP Analysis Tool is used for Process Mining and Reverse Business Engineering (RBE) purposes

  • SUPER Repositories are used for storing artefacts which are produced, utilized and exchanged by the the SUPER components

    • SBP Library stores artefacts which are created during process modelling, i.e. process models, process fragments, and process mediators

    • SWS Repository stores artefacts related to Semantic Web services

    • Execution History stores the audit trail of the executed process instances



SUPER Architecture (cont')


  • SUPER Platform Services comprise the basic services which provide their functionalities for all SUPER tools and components
    • Transformation Services translate among different formats of SUPER artifacts

    • SBP Mediation resolves heterogeneity problems between different business processes

    • Data Mediation is responsible for handling ontology level heterogeneitie

    • SBP Composition combines services and processes in order to implement activities of the process, where activities can be implemented by one or more services

    • SBP Discovery finds SBP candidates fulfilling criteria specified as WSMO Goals

    • SBP Reasoner provides process behavioural logic-based inference engine capable of reasoning with SUPER ontologies

  • SUPER Execution comprise two execution environments/engines:

    • Semantic BPEL Execution Engine is a BPEL 2.0 compliant process engine, which supports the extensions of BPEL4SWS and is integrated into the Semantic Service Bus (SSB)

    • Semantic Execution Environment (SEE) enables discovery, selection, mediation, invocation and interoperability between Semantic Web services (SWS). SEE is a middleware operating on WSMO descriptions enabling flexible interaction between Service Requesters and Service Providers



SUPER Methodology Framework

 The SUPER methodology is a set of phases, methods and techniques to perform activities using SUPER technologies. Like a traditional BPM methodology, the SUPER methodology owns a proper business process “life cycle”, that is enriched with the semantic connotation of the overall SUPER framework.



 


Semantic Business Process Modelling

 
  • Semantic Business Process Modelling (SBPM) is the first step of the SUPER Life Cycle
  • SBPM is concerns with a streamlined, comprehensive, and easy- to-use representative model of the real enterprise business processes
  •  Development of the Business Processes 
  • Model based on the Business Process 
  • Modelling Ontology (BPMO)
  • Use of a Semantic Process 
    Modelling Environment
    • WSMO Studio
    • Integrated BPMO Editor


Example: TID Prototype




TID Modelling – Demo/Video

 


Benefits of SUPER Modelling

  • Business Process Modelling Notation (BPMN) independence (BPMO representation)
  • Discovery of existing Business Processes exploiting the semantic information
    • Search on specified Business Function, Domain and Patterns
    • Search on specified Business Goals, KPIs and Business Rules
  • Automatic validation and simulation of the BPM
  • Better readibility of models through a clear semantic


BPMO Editor Demo/Video



Semantic Business Process Configuration

  • Semantic Business Process Configuration (SBPC) is the second phase of the SUPER SBP Life Cycle. It uses the outputs of the SBP Modeling phase and provides inputs for the third phase, the Semantic Business Process Execution
  • During this phase Modelled Business 
  • Processes are configured


Semantic Business Process Configuration (cont')

Semantic Business Process Configuration steps:

  • Derive sBPEL from BPMO
    • This step enables the translation from the BPMO instance (coming from the SBP Modeling phase) to an sBPEL ontology
  • Search for possible SWS
    • This step consist in discovery of SWS. Even if the services will be executed in the SBP Execution phase, an early service discovery could be extremely useful to reduce the effort of the service selection before the execution



Semantic Business Process Configuration (cont')

  • Examine potential data mismatches
    • In this step data have to be examined to identify potential data mismatches.
  • Define data mappings and mediatiors
    • If potential data mismatches are identified in the previous step interface mappings and data mediators have to be created
  • Validate and refine the process
    • In this step the process is validate and potentially refined. The validation is seen as a sort of “compiler” that checks the correctness of the semantic process description before the execution of the process.


Semantic Business Process Execution

  • Modeled and configured Semantic Business Processes are executed
  • Execution history for SBP Analysis is produced
  • Automates business activities
  • Minimizes time-to-offer
  • Supports
    • Execution of semantic BPEL processes (BPEL4SWS)
    • Discovery and execution of Semantic Web Services (SWS)


Semantic Business Process Execution Scenario



Semantic Business Process Execution Scenario (cont')

  • Step 1: A user initiates the semantic BPEL process by sending a service request through the Semantic Service Bus to Semantic BEPEL Execution Engine (SBPELEE ).
  • Step 2: SBPELEE delegates the invocation of SWS to Semantic Execution Environment (SEE) by passing the WSMO Goal to it. 
  • Step 3: SEE queries the SWS repository to discover the desired SWS.
  • Step 4: SEE invokes the selected SWS.
  • Step 5: SEE returns the result of “Achieve Goal” to SBPELEE.
  • Step 6: After the process execution has been finished, the result is returned to the user.
  • During the execution, execution events are published to Execution History for persistence and to the Monitoring Tool for tracking process executions.


Example: Nexcom Customer Order Management Process

 



Benefits from SUPER SBP Execution

  • Nexcom Use case requirements addressed by the SUPER SBP Execution phase
    • Supplier matching supported by Semantic Web Service discovery and invocation from within semantic business processes
    • Allows for more flexible traffic routing
    • Automates supplier matching and traffic routing process taking into account all existing suppliers
    • Minimizes time-to-offer


SBP Execution Demo/Video




Semantic Business Process Analysis

  • Analysis of executed processes
  • Support of various analysis goals
    • Overview over process usage
    • Detect business exceptions
    • Detect technical exceptions
    • Compare As-Is with To-Be
  • Analysis methods
    • Semantic Process Mining
    • Semantic Reverse Business Engineering



Semantic Reverse Business Engineering (RBE)

Scenario based analysis with predefined content to ensure continuous business improvement
  • As-Is-Analysis
    Provide details and statistics about executed processes
  • Exception analysis
    Focus on business exceptions (deviation from the standard processes) 
  • Standardisation & Harmonisation
    Check compliance of processes between organisational units or with predefined guidelines
  • User & Role analysis
    Check user and role behaviour and authorizations



Scenario Based Analysis



Scenario Based Analysis

  • The business user who wants to perform a specific analysis needs to select the relevant business questions (BQ). If we had just a few questions, this operation could be performed manually. But since we deal with a rich set of BQs, we need a smarter way to select them. 
  • Therefore the business user has just to select the relevant concepts within the SUPER ontologies (e.g., he wants to perform an exceptional analysis, within the sales processes)
  • In this way, the analysis tool is able to automatically select the BQs annotated with those concepts.
  • These Business Questions are either directly executed on the execution history repository or “brought” to the process mining environment.

    This is dependent on the question. Some business questions can directly be answered (RBE approach), some business questions can only be answered using process mining.

  • Once the respective queries (either triggered by the Business Question repository directly or by the Process Mining environment) are executed on the Execution history repository the query results are formatted and aggregated for the business user.



Analysis Results

  • Get overview about system usage
  • Find out exceptions within process flow
  • Check conformance to defined Process model
  • Find bottlenecks
  • Get basis information to apply 6-sigma methodology



SBP Analysis Demo/Video



SUPER Demo/Video





Creator: sidraaslam

Contributors:
-


Licensed under the Creative Commons
Attribution ShareAlike CC-BY-SA license


This deck was created using SlideWiki.