Presentation is loading. Please wait.

Presentation is loading. Please wait.

D10.2 SUPER Showcase.

Similar presentations


Presentation on theme: "D10.2 SUPER Showcase."— Presentation transcript:

1 D10.2 SUPER Showcase

2 Showcase presentation outline
Introduction to the project General business introduction: today problems, challenges and opportunities for improvement Brief introduction to SUPER methodology and, at a very high level, architecture and ontology stack Business (Telco) scenarios for each of the methodology step, in which to underline: Business view Technological challenge SUPER solution Business impact Next steps/objectives of the project TODO before delivering: - Notation consistency/homogeneity (some notations were not explicitly defined before using them, e.g. BPM; upper-case/lower-case, e.g. Web Services vs. Web service) - Graphical consistency/homogeneity (e.g. the specific SUPER Life Cycle pictures with one box pointed out) - “Balance” consistency/homogeneity (e.g., are the SWS slides too many?) - Outline slides © SUPER

3 1. Introduction to the project
[2-3 slides] [IDS/SAP/Hanival] short overview of the project and consortium, introduction to the high level objectives

4 SUPER Research Project
EU funded research project (FP6 – ) started April 2006 3 years duration part of the European Semantic Systems Initiative (ESSI) cluster based on several past projects like SEKT, DIP, SWWS, and IBROW 19 educational and industrial partners [provided by Sebastian] © SUPER

5 SUPER Consortium [provided by Sebastian]
Maybe it’s better the slide with the “clustered” partners? © SUPER

6 SUPER’s objectives Framework for semantic Business Process Management
Bring BPM to the utter business experts, away from the pure technical view Intelligent and flexible reaction to change Integration of heterogeneous Business Processes Mediation inside and between organisations [provided by Sebastian] © SUPER

7 2. General business introduction
[5-6 slides] [SAP/Hanival] today problems, challenges and opportunities for improvement

8 Global Business Context and Problems (1/3)
Imaginable growth of information and automation New business opportunities that the information society offers, e.g. service world, e-Commerce Increase of competitiveness, many new market entrants and a challenging regulatory environment Increase of B2B relationships between companies to bundle more elaborated services Customers demand higher service integration and adaptation to their needs Fusions and alliances, country specific regulatory aspects, company internal re-organizations Shorter time-to-market for new products Demand for agile, dynamic processes [provided by Bernhard] © SUPER © SUPER 8 8 8 8

9 Global Business Context and Problems (2/3)
Emergence of a global knowledge-networked innovation economy: The emergence of a global knowledge-networked innovation economy tremendously changes the way in which business is conducted, resulting in rapid technological changes, shrinking product life cycles and enforcing a strong global competition. Increasing global competition and customer demand: Due to the increasing competition as well as an increase in customer independence and demand, companies of every size are shifting from being suppliers of products to suppliers of complex system solutions solving customer problems and needs by providing complete customer solutions through tightly integrated innovation value chains. [provided by Simone] © SUPER © SUPER 9 9

10 Global Business Context and Problems (3/3)
Optimization of Cost-performance ratio: Companies are facing an increasing financial pressure and are required to optimize their cost-performance ratio. As a result, they focus on their core competences and serve their customer demand through tightly-integrated networks of partners and suppliers, leveraging the specialized core competencies of each member within a demand-driven global supply chain. Demand for: - Modularity, reuse and agility of business processes (enabled by service oriented architectures) - Any application supporting “Speed to market” - as the main driver today’s business - Effective alignment of business and IT strategies [provided by Simone] © SUPER © SUPER 10 10

11 Major Business Requirements
Global process automation Team process automation Fast and flexible new product innovation processes Customer intimacy Predictive business actions and processes Risk-safe compliance systems Modularity, reuse and agility of business processes Effectively aligning business and IT strategies Speed to market as the main driver of today’s business Transition to SOA and SOA-compatibility of new technologies [provided by Bernhard and Laurent] © SUPER © SUPER 11 11

12 Main Target Market The Enterprise Application software market – a giant with high global revenues [provided by Bernhard and Laurent] [Forrester Research] The Future Of Enterprise Software, June 2006 © SUPER 12 12

13 Business Process Management Systems (BPMS) Categories
Integration-centric BPMS Human-centric BPMS [provided by Laurent] [Forrester Research] The Future Of Enterprise Software, June 2006 © SUPER © SUPER 13

14 Market relevance of Business Process Management (BPM) solutions
Customers choose BPM to increase flexibility, efficiency and to optimize processes, for modeling, simulation and monitoring Strategic features for a successful BPM product: strong focus on implementation time, usability, lifecycle completeness (also monitoring and analysis!) BPM solutions are chosen at the moment: To extract fragments of existing processes from heterogeneous legacy systems to achieve higher integration To counteract internal weaknesses, i.e. due to lack of visibility and monitoring for processes (e.g. due to Mergers & Acquisition) By visionaries looking for a competitive advantage BPM solutions will be chosen in the near future To concentrate on and enhance the core processes of the enterprise To improve agility and flexibility in the very dynamic context of joint-venture businesses [provided by Bernhard] © SUPER © SUPER 14 14 14 14

15 3. Brief introduction to SUPER methodology, architecture and ontology stack
[4-5 slides] [Cefriel/DERI-Innsbruck] 4 phases of the methodology (without technical details) Use of semantics and a rough idea of architecture and ontologies

16 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. [provided by Irene] © SUPER

17 SUPER Methodology MULTI-DOMAIN Others SOLUTIONS MAPS The SUPER Methodology can be applied to a specific domain (like in telco companies) as well as to generic or multiple domains (like any business described in SAP Solution Maps) SPECIFIC DOMAIN YATOSP-eTOM Others The top and bottom layers in the SUPER methodology are: Strategic Semantic Business Process Management, which deals with all the elements related to a company from a strictly strategic and organizational point of view Ontological Foundation layer, which describes how SUPER artifacts are transformed and "lifted" to semantic elements: it is the SUPER Set of Ontologies for Business Process Management [provided by Irene] © SUPER

18 SUPER Methodology lifecycle
Semantic Business Process Execution, is the execution of the BPs modeled and configured in the previous phases and, by the use of semantic technologies, enables the run-time resolution of semantic goals, as well run-time service discovery and composition Semantic Business Process Analysis, by the use of semantic information about BPs, enables a better understanding of context and concepts, allowing for automated matching and inference functionality in process discovery, conformance checking, process extension and in business question answering Semantic Business Process Modelling, strictly linked to the Ontological Foundation, permits the ontological representation of business processes, which in turn enables advanced functionalities (specifications mapping automation, process querying, process fragment reuse, etc.) Semantic Business Process Configuration enables the semi-automated mapping between high-level BP specifications and executable BPEL4SWS specifications and the integration of BPEL with Semantic Web Services [provided by Irene] © SUPER

19 WSMO – Semantics for SUPER
Aims: „ontologize“ the BPM Life Cycle enable BPM technologies to deal with Semantic Web Services increase flexibility by lifting BPM technologies to the level of goal patterns The Web Service Modelling Ontology WSMO a comprehensive framework for semantically enabled SOA 4 top level notions: ontologies, Web Services, goals, mediators provides axiomatization, specification language, and a reference implementation Use of WSMO technologies in SUPER describe process data on the basis of ontologies flexible Web Services invocation via Goals process activity realized as WSMO Goal dynamic discovery / composition / execution of necessary Web Services at runtime use WSMO mediators to resolve heterogeneities [provided by Michael] © SUPER

20 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 elements Semantic description of Web Services: Capability (functional) Interfaces (usage) [provided by Michael] Connectors between components with mediation facilities for handling heterogeneities © SUPER 20

21 WSMO Web Service Description
Capability functional description Advertising of Web Service Support for WS Discovery Non-functional Properties DC + QoS + Version + financial complete item description quality aspects Web Service Management client-service interaction interface for consuming WS external visible behavior - communication structure - ‘grounding’ realization of functionality by aggregation functional decomposition WS composition Web Service Implementation (not of interest in Web Service Description) WS [provided by Michael] WS WS Choreography --- Service Interfaces --- Orchestration © SUPER

22 Goal-driven Web Service Usage
(1) Abstraction Layer for Problem-oriented WS Usage (2) Dynamic WS Usage client-system interaction discovery, composition, mediation Client objective / problem to be solved WSMO Goals formal objective description Semantics / SWS Ontology SWS description Mediator Web Services & Resources WS Internet execution [provided by Michael] © SUPER

23 SWS Usage Process GOAL Discoverer Data Mediator Composer Selection &
if: successful else: not solvable submission matchmaking R with all WS else: try other WS uses Discoverer Data Mediator if: composition possible if: usable Composer Selection & Ranking uses Service Repository Process Mediator Behavioral Conformance uses composition (executable) [provided by Michael] if: compatible information lookup for particular service Executor if: execution error © SUPER

24 From Syntactic to Semantic BPEL
WS XML BPEL Process sBPEL Process SWS Environment discovery composition mediation execution WSMO Goal Ontology Mediator dynamic detection at runtime b) Semantic BPEL Process a) BPEL Process [provided by Michael] © SUPER 24

25 SUPER Architecture Structural Perspective
[provided by Irene] © SUPER

26 SUPER Ontology Stack [provided by Irene] © SUPER

27 Benefits Explicate Semantic Meaning of Data & Models
Semantic Coherency of Information among several levels of BPM Higher Flexibility for Web Service usage Automated Handling of Potential Heterogeneities Make process definitions better understandable [provided by Michael] © SUPER

28 4. Business scenarios (focused on Telco) for each of the methodology step
[20-25 slides in total, 5-6 slides for each step] [coordinated by TP] Business scenarios (focused on Telco) for each of the methodology step, in which to underline: (i) Business view, (ii) Technological challenges, (iii) SUPER solution (from the business point of view)

29 Telco Business Scenarios Context
Telco business scenarios (Use Cases) provide through each step of SUPER life cycle give usage example of SUPER Starting point QoS in DSL (VoIP) (Nexcom) DAM Searching & Downloading (TID) QoS in DSL (VoIP) (Nexcom) [provided by Ewelina] DSL (VoIP) Fulfilment (TP) CRM & Fulfilment (eTel) QoS: Quality of Service; DAM: Digital Asset Management; VoIP: Voice over IP; CRM: Customer Relationship Management © SUPER

30 4a. Modelling [contribution from Isoco]

31 Semantic Business Process Modelling
First step of the SUPER Life Cycle 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 [provided by Laurent] © SUPER 31

32 Modelling Requirements and Methodology
Business Process Model based on: Company specific Business Function and Domain Ontologies Semantic Web Services and Goals Business Process Model sources are: Business Analyst implicit knowledge and studies (business questions, Key Performance Indicators (KPIs), business outcomes, etc.) Analysis reports created in an eventual previous Semantic Business Process (SBP) Analysis phase Several modelling methodology are possible: Start business process modelling from scratch Modify existing semantic business processes Annotating non-semantic business processes Re-use process patterns previously modeled [provided by Laurent] © SUPER

33 Example: TID Prototype
[provided by Laurent] © SUPER

34 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, Business Domain and Business 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 [provided by Laurent] Adding ? Screencast: © SUPER

35 4b. Configuration [contribution from TP]

36 Semantic Business Process Configuration
Modelled Business Processes are configured Functions supported Mapping of semantic BPEL processes (BPEL4SWS) Integration of BPEL with SWS SUPER functionalities used Task and process composition (SBP Composition) SWS and process fragment discovery (SBP Discovery) Semantic Business Process Repository [provided by Ewelina] © SUPER

37 Example: SBP Configuration Scenarios
CRM & Fulfilment (eTel) DSL Fulfilment (TP) [provided by Ewelina] Customer Order Request © SUPER

38 Configuration Requirements
Each subsystem (its functionalities) represented by Semantic WS’s (SWS) Each SWS described by the ontology BPMO process composition Task Composition implements each BPMO task with a combination of WS Consistency Checking finds and removes bugs in the overall process Use of SUPER Ontologies Mapping BPMO into executable BPMO – all tasks bound to existing WS Domain ontologies specify how WS affect the world – basis for combining WS and for checking/fixing the process [provided by Ewelina] © SUPER

39 Benefits of SUPER Configuration
Binding process to company IT infrastructure Coming from general process model to its concrete realisation Bridging the gap between business process analyst and IT professional [provided by Ewelina] © SUPER

40 4c. Execution [contribution from USTUTT]

41 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) [provided by Zhilei] © SUPER

42 Semantic Business Process Execution Scenario
SUPER Tooling During the execution, execution events are published to Execution History for persistence and to the Monitoring Tool for tracking process executions. A user initiates the semantic BPEL process by sending a service request through the Semantic Service Bus to SBPELEE. 1 SBPELEE delegates the invocation of SWS to SEE by passing the WSMO Goal to it. 2 After the process execution has been finished, the result is returned to the user. 6 SEE queries the SWS repository to discover the desired SWS. 3 SEE returns the result of “Achieve Goal” to SBPELEE. 5 Monitoring Tool SEE invokes the selected SWS. 4 Semantic Web Service (SWS) Request Service 1 6 Return Result 4 Invoke Service 2 Achieve Goal Semantic Service Bus (SSB) 5 Return result to engine 3 Discover Service [provided by Zhilei] 1. A user initiates the semantic BPEL process by sending a service request through the Semantic Service Bus to SBPELEE. 2. SBPELEE delegates the invocation of SWS to SEE by passing the WSMO Goal to it. 3. SEE queries the SWS repository to discover the desired SWS. 4. SEE invokes the selected SWS. 5. SEE returns the result of “Achieve Goal” to SBPELEE. 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. Semantic BPEL Execution Engine (SBPELEE) Semantic Execution Environment (SEE) Semantic Web Services Execution History SUPER Execution Environment SUPER Repositories © SUPER 42

43 Example: Nexcom Customer Order Management Process
Customer uses a client application to start the Nexcom process 1 6 1 6 Nexcom process is deployed as a semantic BPEL process [provided by Zhilei] 2 5 Supplier Supplier Supplier Supplier exposes its process as SWS. © SUPER 43

44 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 [provided by Zhilei] Screencast: © SUPER

45 4d. Analysis [contribution from IBIS]

46 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 Business Process Analysis Semantic Business Process Modelling [provided by Stefan] Semantic Semantic Business Process Business Process Execution Configuration Prerequisite for continuous improvement © SUPER

47 Semantic Process Mining
Process Perspective Case Perspective Organizational Perspective Semantic auditing Use semantic information to check for properties in logs Semantic control-flow mining Use semantic information to support different levels of abstraction in the mined models Semantic organizational mining Automatically derive the teams and groups in the organization based on task similarity Semantic performance analysis Use semantic information to check for Service Level Agreements (SLAs), throughput times, bottlenecks etc. How? When? Who? [provided by Stefan] © SUPER

48 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 How do I get the relevant information to redesign and improve my business processes? [provided by Stefan] © SUPER

49 Scenario Based Analysis
RBE Ontology Business Function Ontology I am interested in all exceptions of the sales process Exception Analysis Sales Process How many sales orders were cancelled? Which sales orders are locked for further processing? The query results are formatted and aggregated for the business user Business questions are executed on the Execution History Repository (log file) either directly or through Process Mining Only business questions semantically assigned to Exception Analysis and to the Sales Process are to be selected [provided by Stefan] The business user who wants to perform a specific analysis needs to select the relevant business questions. 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. [Click] Therefore the business user has just to select the relevant concepts within the SUPER ontologies (e.g., he wants to perform an exceptional analysis [click], within the sales processes [click] In this way, the analysis tool is able to automatically select the BQs annotated with those concepts [click]. These Business Questions are either directly executed on the execution history repository or “brought” to the process mining environment. [Click] 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. [Click] How many sales orders are delayed? Business Question Repository Where are the bottlenecks in the sales process? Execution History Repository Analysis Results Process Mining © SUPER © SUPER 49

50 Analysis Results Get overview about system usage
How many sales orders were cancelled? 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 Which sales orders are locked for further processing? [provided by Stefan] © SUPER

51 5. Business impact [6-7 slides] [Hanival/SAP]
Evaluation of the impact SUPER can have on business, in terms of costs reduction, improved efficiency, shortened time-to-market, etc.

52 SUPER Unique Selling Proposition
Semantically enriched Business Process Mgmt: SUPER bridges the gap between Business experts and IT experts in setting up new products and processes SUPER provides a new set of integrated BPM tools for Modelling Automated Composition of Processes SUPER uses Semantics to gain a new level of automation for the modelling and configuration of business processes SUPER tools are based on open standards to guarantee independence from particular vendors [provided by Bernhard] © SUPER 52 52

53 SUPER Unique Selling Proposition
Economic advantages lower development costs and shorter time-to-market for new services and products Target Group Business Users Global players SMEs and government agencies [provided by Bernhard] © SUPER 53 53

54 Business Impact Better process monitoring leading to more transparency
Faster reactions to emergency situations (technical problems, market requirements…) Optimization of CRM, customer analysis, market analysis Flexible product design and management Design: SUPER offers the opportunity to create new products out of a library of existing processes - in short time, without involving IT resources and without additional costs Flexible product provisioning: technical realization of business processes can be changed without redesigning the process itself Enabling the user to rapidly implement and test business processes [provided by Bernhard] © SUPER © SUPER 54

55 Competitive Impact Shorter Time to Market Agile Enterprises
Clear cost savings in terms of ROI (Return of Invest), DCF (Discounted Cash Flow) and FTE (Full times Equivalent) [provided by Bernhard] © SUPER © SUPER 55

56 Business Opportunities
Improved service discovery & matching in existing products Ontology modelling support and semantic search for existing BPM products R&D and consultancy services for early adopters Creation of custom components for the alignment of existing products with recent SWS and BPM standards Introduction of semantic BPM solutions to heterogeneous service landscapes [provided by Bernhard] © SUPER © SUPER 56

57 6. Next steps/objectives of the project
[1-2 slides] [SAP/Hanival] Some details on the following steps, the deployment in real settings, etc.

58 Next steps SUPER will continue identifying and leveraging the potential of semantics in order to: enable the business user to utilize semantics in the frame of BPM, improve productivity of business processes and increase levels of quality, SUPER Use Case WPs contribute to these issues by helping organizations to understand how a Semantically Enabled Business Process Management enables an agile response to recent business changes [provided by Simone] © SUPER


Download ppt "D10.2 SUPER Showcase."

Similar presentations


Ads by Google