Prosero Effective business process outsourcing Innovation Day 2007 – October 29, 2007, Berlin
SOA and business process management <ul><li>SOA is the key emerging architecture for enterprise software infrastructure </...
Why SOA? <ul><li>Key benefits of SOA </li></ul><ul><li>Access applications across the net </li></ul><ul><li>Less dependenc...
SOA and business process outsourcing <ul><li>Leverage IT expertise </li></ul><ul><li>expertise in vertical industry proces...
Business process outsourcing for SMEs <ul><li>Small and medium enterprises </li></ul><ul><li>Do not have the infrastructur...
Challenges to enable effective business process outsourcing High cost of  BP customization High cost of  business expertis...
The Prosero mission <ul><li>Make it possible to </li></ul><ul><ul><ul><li>Model </li></ul></ul></ul><ul><ul><ul><li>Custom...
Overview <ul><ul><li>SOA and Business Process Management </li></ul></ul><ul><ul><ul><li>Enterprise applications  and Servi...
M ore processes in less time… what’s the catch? <ul><li>High similarity </li></ul><ul><li>Many very similar processes for ...
The Prosero landscape Roles and activities Prosero Semantic Repository Portal Modeling Runtime <ul><li>Runtime analysis of...
The Prosero methodology Key activities and tools Prosero Tools Support Customer & Analyst <ul><li>Define the scope of the ...
The Prosero methodology   Repository-based end to end process support SAP 1 Microsoft Oracle SAP 2 Web service repository ...
Overview <ul><ul><li>SOA and Business Process Management </li></ul></ul><ul><ul><ul><li>Enterprise applications  and Servi...
The Prosero solution Eclipse Modeling Tools Runtime Monitoring Web Portal Prosero Semantic Repository
The Prosero solution Semantic repository Reference Model Repository Customer Model Repository Web Service Repository Eclip...
The Prosero repository <ul><li>3 levels of models </li></ul><ul><li>Reference Models: Industry-standard best-practice mode...
The Prosero repository: a business process ontology  Terminology and relations <ul><li>The Prosero Repository is a rich We...
The Prosero portal <ul><li>The Prosero Web portal gives access to the Prosero repository and articulates the workflow of t...
Repository-based modeling tools <ul><li>The Prosero modeling tools provide: </li></ul><ul><ul><li>BPMN modeling of process...
Context specialization <ul><li>Register a new customer into Prosero </li></ul><ul><li>A new customer repository is created...
Matching and BPEL generation <ul><li>The analyst customizes a BPMN process model that refers to: </li></ul><ul><li>Referen...
Non functional properties and intelligent preference management <ul><li>Prosero defines an ontology to capture: </li></ul>...
Business process verification and exception management <ul><li>Customer BP models are derived from well-defined reference ...
Overview <ul><ul><li>SOA and Business Process Management </li></ul></ul><ul><ul><ul><li>Enterprise applications  and Servi...
Key Prosero innovation <ul><li>Define the business process outsourcing task as a semantic web service application </li></u...
The Prosero team <ul><li>At Ben Gurion University T-Laboratories </li></ul><ul><li>Dr Michael Elhadad (Project Manager) </...
Upcoming SlideShare
Loading in …5
×

Presentation (on Prosero)

266
-1

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
266
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Presentation (on Prosero)

  1. 1. Prosero Effective business process outsourcing Innovation Day 2007 – October 29, 2007, Berlin
  2. 2. SOA and business process management <ul><li>SOA is the key emerging architecture for enterprise software infrastructure </li></ul><ul><li>Software as a service revolution </li></ul><ul><li>Reusable software components accessible through the net </li></ul><ul><li>Uniform technical standards ensure inter-operability </li></ul><ul><li>Composite applications are easily deployed (BPEL) </li></ul>© Vitria
  3. 3. Why SOA? <ul><li>Key benefits of SOA </li></ul><ul><li>Access applications across the net </li></ul><ul><li>Less dependency on a single software provider </li></ul><ul><li>Mix and match best-of-breed components </li></ul><ul><li>Bill per usage </li></ul><ul><li>Applications are easily aligned with best-practice business process models </li></ul>SAP Microsoft Oracle Order Discover Fulfil Invoice SAP
  4. 4. SOA and business process outsourcing <ul><li>Leverage IT expertise </li></ul><ul><li>expertise in vertical industry process maps (supply chain, eTom, OAGIS) </li></ul><ul><li>available IT, networking, hardware and virtualized server platforms </li></ul><ul><li>expertise in off-the-shelf software solutions (SAP, Oracle, ERP, CRM) </li></ul><ul><li>Deploy customer business process </li></ul><ul><li>on high added-value infrastructure </li></ul>GUI Composite Application IT Infrastructure Software expertise Networking and provisioning expertise Business modeling expertise Customer SAP Microsoft Oracle Order Discover Fulfil Invoice SAP
  5. 5. Business process outsourcing for SMEs <ul><li>Small and medium enterprises </li></ul><ul><li>Do not have the infrastructure required to deploy complex CRM and ERP solutions </li></ul><ul><li>Do not have the expertise required to design industry standard business process applications </li></ul><ul><li>Lose the benefits of the SOA/BPM agility/business fit </li></ul><ul><li> SMEs need BPO – BUT… </li></ul><ul><li>Modeling customized business processes for a customer is expensive </li></ul><ul><li>Deploying and provisioning processes according to the customer SLO is risky </li></ul><ul><li>Configuring SAP, Microsoft or Oracle packages is complex </li></ul>
  6. 6. Challenges to enable effective business process outsourcing High cost of BP customization High cost of business expertise Non-functional properties complexity Semantic mismatch 3 4 2 1 <ul><li>Given a source best-practice BP model, any customization requires business AND technical expertise </li></ul><ul><li>Mapping specific customer requirements to BP modifications is difficult </li></ul><ul><li>Software as a service is billed according to usage </li></ul><ul><li>SLO and SLA must be un-ambiguous and easy to monitor </li></ul><ul><li>Tradeoffs among SLOs is difficult to express and translate into runtime and deployment decisions </li></ul><ul><li>Best-practice industry Solutions are expressed in abstract terms </li></ul><ul><li>SOA components rely on concrete data types and operations </li></ul><ul><li>Mapping best-practice solutions to heterogeneous SOA components fails due to terminological differences </li></ul><ul><li>Capturing best-practice industry solutions is complex </li></ul><ul><li>Industry standards ( e.g. , eTOM, OAGIS) are broad, deep and evolve fast </li></ul><ul><li>Need tools and methodology to make such expertise reusable </li></ul>
  7. 7. The Prosero mission <ul><li>Make it possible to </li></ul><ul><ul><ul><li>Model </li></ul></ul></ul><ul><ul><ul><li>Customize </li></ul></ul></ul><ul><ul><ul><li>Deploy </li></ul></ul></ul><ul><ul><ul><li>Monitor </li></ul></ul></ul><ul><ul><ul><li>Maintain </li></ul></ul></ul><ul><li>hundreds of high-quality business processes* for hundreds of SME customers with less resources </li></ul><ul><ul><ul><li>Analyst time </li></ul></ul></ul><ul><ul><ul><li>Developer time </li></ul></ul></ul><ul><ul><ul><li>Administrator time </li></ul></ul></ul><ul><li>* Catch: these processes are very similar to each other </li></ul>
  8. 8. Overview <ul><ul><li>SOA and Business Process Management </li></ul></ul><ul><ul><ul><li>Enterprise applications and Service Oriented Architecture </li></ul></ul></ul><ul><ul><ul><li>Business process customization </li></ul></ul></ul><ul><ul><ul><li>Challenges </li></ul></ul></ul><ul><ul><li>The Prosero methodology </li></ul></ul><ul><ul><li>Prosero features </li></ul></ul><ul><ul><ul><li>Repository-based modeling </li></ul></ul></ul><ul><ul><ul><li>Matching and BPEL generation </li></ul></ul></ul><ul><ul><ul><li>Non-functional properties and intelligent preference management </li></ul></ul></ul><ul><ul><ul><li>Business process verification </li></ul></ul></ul><ul><ul><ul><li>Exception management </li></ul></ul></ul><ul><ul><li>Key innovation </li></ul></ul>
  9. 9. M ore processes in less time… what’s the catch? <ul><li>High similarity </li></ul><ul><li>Many very similar processes for many customers </li></ul><ul><li>Each process has small delta from the other </li></ul><ul><li>Most of the steps remain are mapped to existing well understood off-the-shelf services </li></ul><ul><li>Focus on customization </li></ul><ul><li>Start from few well understood reference models </li></ul><ul><li>Maintain repository of reusable patterns </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul><ul><li>xxx </li></ul>Step 2 Step 1 Step 3 Step 4 <ul><li>Step 1.1 </li></ul><ul><li>SAP </li></ul><ul><li>Step 2.1 </li></ul><ul><li>SAP </li></ul><ul><li>Step 1.2 </li></ul><ul><li>SAP </li></ul><ul><li>Step 1.3 </li></ul><ul><li>SAP </li></ul><ul><li>Step 3.3 </li></ul><ul><li>Oracle </li></ul><ul><li>Step 2.3 </li></ul><ul><li>Oracle </li></ul><ul><li>Step 2.2 </li></ul><ul><li>SAP </li></ul><ul><li>Step 2.3 </li></ul><ul><li>Microsoft </li></ul><ul><li>Step 4.1 </li></ul><ul><li>SAP </li></ul><ul><li>Step 3.1 </li></ul><ul><li>Oracle </li></ul><ul><li>Step 4.3 </li></ul><ul><li>SAP </li></ul><ul><li>Step 2.4 </li></ul><ul><li>SAP </li></ul>Customer 1 Customer 2 Customer 3
  10. 10. The Prosero landscape Roles and activities Prosero Semantic Repository Portal Modeling Runtime <ul><li>Runtime analysis of process execution </li></ul><ul><li>Verification of SLOs </li></ul><ul><ul><li>Matches the customized BPMN model into an executable BPEL orchestration. </li></ul></ul><ul><li>Finalizes mediators and GUI forms for human activities. </li></ul>Customer Business Process Analyst Enterprise Monitoring Developer <ul><li>Defines the requirements for a customized business process </li></ul><ul><li>Capture customer-specific terminology </li></ul><ul><li>Defines key service level objectives (SLO) </li></ul><ul><li>Captures the specific context of the customer </li></ul><ul><li>Creates a customized version of a customer repository: enterprise data model, activities </li></ul><ul><ul><li>Models a custom BP model for the customer in BPMN and Core Components </li></ul></ul>
  11. 11. The Prosero methodology Key activities and tools Prosero Tools Support Customer & Analyst <ul><li>Define the scope of the process </li></ul><ul><li>Find closest existing reference model from the Prosero repository </li></ul><ul><li>Specialize the reference model to the customer context </li></ul>Analyst <ul><li>Customize the reference model </li></ul><ul><li>Define a specialized data model </li></ul><ul><li>Define a specialized BPMN model </li></ul><ul><li>Capture SLO and preferences </li></ul>Developer <ul><li>Match the BPMN model to a BPEL orchestration / SOA services </li></ul><ul><li>Fine-tune data mediators </li></ul><ul><li>Deploy BPEL </li></ul>Administrator <ul><li>Monitor BP runtime execution </li></ul><ul><li>Enforce SLA </li></ul>Prosero Portal Prosero Modeler Prosero Repository
  12. 12. The Prosero methodology Repository-based end to end process support SAP 1 Microsoft Oracle SAP 2 Web service repository Reference model repository Order Discover Fulfil3 Invoice Customer model repository SAP n Customize Data Mediator Analyst & Customer Customized business process (BPMN) Reference business process (BPMN) Automatically generated XSL data mediator Match Executable business process (BPEL) Developer Administrator GUI Form Automatically generated GUI form Order Discover Fulfil Invoice Order SAP 1 Discover Human Task Fulfil Oracle Invoice SAP 2
  13. 13. Overview <ul><ul><li>SOA and Business Process Management </li></ul></ul><ul><ul><ul><li>Enterprise applications and Service Oriented Architecture </li></ul></ul></ul><ul><ul><ul><li>Business process customization </li></ul></ul></ul><ul><ul><ul><li>Challenges </li></ul></ul></ul><ul><ul><li>The Prosero methodology </li></ul></ul><ul><ul><li>Prosero features </li></ul></ul><ul><ul><ul><li>Repository-based modeling </li></ul></ul></ul><ul><ul><ul><li>Matching and BPEL generation </li></ul></ul></ul><ul><ul><ul><li>Non-functional properties and intelligent preference management </li></ul></ul></ul><ul><ul><ul><li>Business process verification </li></ul></ul></ul><ul><ul><ul><li>Exception management </li></ul></ul></ul><ul><ul><li>Key innovation </li></ul></ul>
  14. 14. The Prosero solution Eclipse Modeling Tools Runtime Monitoring Web Portal Prosero Semantic Repository
  15. 15. The Prosero solution Semantic repository Reference Model Repository Customer Model Repository Web Service Repository Eclipse Modeling Tools Runtime Monitoring Web Portal Prosero Semantic Repository
  16. 16. The Prosero repository <ul><li>3 levels of models </li></ul><ul><li>Reference Models: Industry-standard best-practice models </li></ul><ul><li>Customer Models: Customized models for specific customers – derived from reference models </li></ul><ul><li>Web Service Models: Metadata description of actual operations and data types from SOA components (SAP, Oracle) </li></ul><ul><li>3 types of models </li></ul><ul><li>Organizational Structure: Business units, roles, chart </li></ul><ul><li>Data Objects: Enterprise-wide data objects according to the UMM Core Components methodology </li></ul><ul><li>Process Models: Activities, data and control flow </li></ul>Order Discover Fulfil Invoice S S-NW P1 P Q A F A Sales Prod Finances QA Enterprise
  17. 17. The Prosero repository: a business process ontology Terminology and relations <ul><li>The Prosero Repository is a rich Web of Knowledge: </li></ul><ul><ul><li>All levels of the Prosero Repository are tagged by uniform terminology </li></ul></ul><ul><ul><li>Reference Models are tagged by customer context relevance </li></ul></ul><ul><ul><li>Models in the customer repository are linked to the reference models from which they are derived </li></ul></ul><ul><ul><li>Concrete service descriptions and data-types from the Web Service repository are tagged by terminology and linked to reference models </li></ul></ul><ul><li>Key repository maintenance activities: </li></ul><ul><ul><li>Terminology extraction and alignment </li></ul></ul><ul><ul><li>Context specialization </li></ul></ul><ul><ul><li>Model matching </li></ul></ul><ul><ul><li>Service lifting </li></ul></ul>
  18. 18. The Prosero portal <ul><li>The Prosero Web portal gives access to the Prosero repository and articulates the workflow of the stakeholders </li></ul><ul><li>Customers, analysts, developers and administrators can: </li></ul><ul><ul><li>Search the repository </li></ul></ul><ul><ul><li>Browse models </li></ul></ul><ul><ul><li>Trigger key workflow operations (create customer, create process, specialize context, refine models, match models) </li></ul></ul><ul><ul><li>Activate modeling and development tools in context </li></ul></ul>Prosero Repository Prosero Web Service Gateway Prosero Modeler
  19. 19. Repository-based modeling tools <ul><li>The Prosero modeling tools provide: </li></ul><ul><ul><li>BPMN modeling of process models </li></ul></ul><ul><ul><li>Data modeling according to the UMM Core Components methodology (UML Profile) </li></ul></ul><ul><ul><li>Organizational structure modeling </li></ul></ul><ul><ul><li>Preference modeling for SLO specification </li></ul></ul><ul><li>All tools are directly linked: </li></ul><ul><ul><li>To the Repository with full metadata depth </li></ul></ul><ul><ul><li>Inter-linked </li></ul></ul><ul><ul><li>Developed on the popular Eclipse GMF Framework </li></ul></ul>Prosero Repository Prosero Web Service Gateway
  20. 20. Context specialization <ul><li>Register a new customer into Prosero </li></ul><ul><li>A new customer repository is created </li></ul><ul><li>The customer repository includes: </li></ul><ul><ul><li>Organizational structure </li></ul></ul><ul><ul><li>Data model </li></ul></ul><ul><ul><li>Activities and key processes </li></ul></ul><ul><li>The customer repository is derived from the reference repository through the operation of context specialization </li></ul><ul><li>Context specialization </li></ul><ul><li>Select the most relevant data objects and activities from the reference model </li></ul><ul><li>Filter inside the objects the elements and fields that are not relevant to the customer context </li></ul><ul><li>Algorithm relies on terminology and context tagging – uses tree alignment technology </li></ul><ul><li>Example: </li></ul><ul><li>The UMM-CCTS Order data object contains about 8,000 distinct elements </li></ul><ul><li>When filtered by context specialization – we can trim it to between 500 and 1,000 distinct elements </li></ul>
  21. 21. Matching and BPEL generation <ul><li>The analyst customizes a BPMN process model that refers to: </li></ul><ul><li>Reference activities </li></ul><ul><li>Reference data-objects </li></ul><ul><li>Prosero translates the BPMN process into an executable BPEL process: </li></ul><ul><li>For each reference activity, a concrete Web Service is selected </li></ul><ul><li>Input and output data objects are mapped to concrete data types </li></ul><ul><li>XSL data mediators are generated to adapt data objects as needed </li></ul><ul><li>Human Tasks (according to BPEL4People WS-HumanTask spec) are generated </li></ul><ul><li>GUI forms for the input of the Human Tasks are generated </li></ul>BPMN to BPEL Matcher Order Discover Fulfil Invoice
  22. 22. Non functional properties and intelligent preference management <ul><li>Prosero defines an ontology to capture: </li></ul><ul><li>Service level objectives for activities in BP models </li></ul><ul><li>Non functional properties for services </li></ul><ul><li>Prosero preference models capture: </li></ul><ul><li>Tradeoffs between SLOs </li></ul><ul><li>An efficient decision algorithm to select the most appropriate service for a target SLA </li></ul>
  23. 23. Business process verification and exception management <ul><li>Customer BP models are derived from well-defined reference models </li></ul><ul><li>Reference models are enriched BPMNs that specify: </li></ul><ul><li>Mandatory activities </li></ul><ul><li>Cardinality constraints on activities and data objects </li></ul><ul><li>Pre and post conditions for key activities </li></ul><ul><li>Innovative algorithms exploit this knowledge: </li></ul><ul><li>To verify that a customized BP remains compliant with its origin reference model </li></ul><ul><li>To detect missing error handling in the process model </li></ul>
  24. 24. Overview <ul><ul><li>SOA and Business Process Management </li></ul></ul><ul><ul><ul><li>Enterprise applications and Service Oriented Architecture </li></ul></ul></ul><ul><ul><ul><li>Business process customization </li></ul></ul></ul><ul><ul><ul><li>Challenges </li></ul></ul></ul><ul><ul><li>The Prosero methodology </li></ul></ul><ul><ul><li>Prosero features </li></ul></ul><ul><ul><ul><li>Repository-based modeling </li></ul></ul></ul><ul><ul><ul><li>Matching and BPEL generation </li></ul></ul></ul><ul><ul><ul><li>Non-functional properties and intelligent preference management </li></ul></ul></ul><ul><ul><ul><li>Business process verification </li></ul></ul></ul><ul><ul><ul><li>Exception management </li></ul></ul></ul><ul><ul><li>Key innovation </li></ul></ul>
  25. 25. Key Prosero innovation <ul><li>Define the business process outsourcing task as a semantic web service application </li></ul><ul><li>Prosero semantic repository architecture: </li></ul><ul><li>Terminology management based on computational linguistic technology </li></ul><ul><li>Context specialization (filter and trim reference models according to customer context) </li></ul><ul><li>Service lifting (Match WSDL metadata with repository knowledge and tag service accordingly) </li></ul><ul><li>Process matching </li></ul><ul><li>Tree alignment technology applicable on large-scale XSD documents (10s of thousands of elements) </li></ul><ul><li>Non-functional properties preference models </li></ul><ul><li>Select the most appropriate services based on complex combination of SLOs </li></ul><ul><li>BPM validation </li></ul><ul><li>Check compliance of customized BPM wrt to reference model </li></ul><ul><li>Identify missing error handling </li></ul>
  26. 26. The Prosero team <ul><li>At Ben Gurion University T-Laboratories </li></ul><ul><li>Dr Michael Elhadad (Project Manager) </li></ul><ul><li>Prof Mira Balaban </li></ul><ul><li>Prof Ronen Brafman </li></ul><ul><li>Prof Mike Codish </li></ul><ul><li>Prof Eyal Shimony </li></ul><ul><li>Dr Arnon Sturm </li></ul><ul><li>Dr Yael Netzer </li></ul><ul><li>Dr Meni Adler </li></ul><ul><li>Aviram Dayan (Team Leader) </li></ul><ul><li>Pavel Ackerman </li></ul><ul><li>Ziv Ben-Eliahu </li></ul><ul><li>At T-Labs Berlin </li></ul><ul><li>Maximilian Ahrens (Project Manager) </li></ul><ul><li>At TUB Berlin </li></ul><ul><li>Dr Marten Schoenherr </li></ul><ul><li>Oliver Holschke </li></ul><ul><li>Christian Schroepfer </li></ul><ul><li>Philipp Offermann </li></ul><ul><li>Nassim Biadsy </li></ul><ul><li>Nadav Hoze </li></ul><ul><li>Roy Kass </li></ul><ul><li>Dvir Ofek </li></ul><ul><li>Yonatan Schichel </li></ul><ul><li>Shay Zakov </li></ul><ul><li>Moshe Zazon </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×