Your SlideShare is downloading. ×
0
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
D2 5   Building Virtual Enterprise Based On Existing Workflow Technologies
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

D2 5 Building Virtual Enterprise Based On Existing Workflow Technologies

477

Published on

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

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Adam Mickiewicz University Building Virtual Enterprise based on existing workflow technologies Rafał Renk WfMC Forum Poland 2007 BPM In Practice October 8-9th, Poznań, Poland
  • 2. A genda <ul><li>What is VISP? </li></ul><ul><li>Why VISP? </li></ul><ul><li>VISP Virtual Enterprise </li></ul><ul><li>Processes in VISP </li></ul><ul><li>High Level Architecture </li></ul><ul><li>VISP and SOA </li></ul><ul><li>General Technical Architecture </li></ul><ul><li>Summary </li></ul>
  • 3. Basic project information <ul><ul><li>Project participants: </li></ul></ul><ul><ul><ul><li>Perceval (Belgium) </li></ul></ul></ul><ul><ul><ul><li>Telscom (Switzerland) </li></ul></ul></ul><ul><ul><ul><li>Eozen (Luxembourg) </li></ul></ul></ul><ul><ul><ul><li>Valtech (France) </li></ul></ul></ul><ul><ul><ul><li>UAM (Poland) </li></ul></ul></ul><ul><ul><ul><li>Eworx (Greece) </li></ul></ul></ul><ul><ul><ul><li>FhI Fokus (Germany) </li></ul></ul></ul><ul><ul><ul><li>Mobiltek (Poland) </li></ul></ul></ul><ul><ul><ul><li>WUT (Romania) </li></ul></ul></ul><ul><ul><ul><li>ICCS (Bulgaria) </li></ul></ul></ul>Project name: VISP (Virtual ISP) Project type: Specific Targeted Research Project Start date: November 1, 2005 D uration: 32 months Total budget c.a. : 3,5 mln € More information: www.visp-project.org
  • 4. What is VISP <ul><li>VISP is an IST FP6 Research and Development project whose objective is to develop a software platform enabling a cluster of SMEs to collaborate and operate as a single business entity , in multiple dynamic business models , for the automated production of tailored ISP solutions adapted to local business needs </li></ul>
  • 5. Why - Where does it come from? <ul><li>LLU didn&apos;t really succeeded for small ISPs </li></ul><ul><ul><li>Access infrastructure still closed to these ISPs for scalability reasons. </li></ul></ul><ul><ul><li>Cost structure often directly proportional to the area size to be covered. </li></ul></ul><ul><ul><li>Small ISPs don&apos;t have the customer density but have to cover all areas. </li></ul></ul><ul><ul><li>Constrained by reselling wholesale services of incumbent operators. </li></ul></ul><ul><li>Struggle to lower prices on typical added-value services </li></ul><ul><ul><li>E.g. e-mail, hosting, DNS, firewall, backup, etc. </li></ul></ul><ul><ul><li>Some are becoming expensive to provide: spam filtering, regulation, etc. </li></ul></ul><ul><ul><li>These services are monolithic and easy to compete with. </li></ul></ul><ul><li>Solution: try to differentiate by offering tailored services </li></ul><ul><ul><li>SMEs are more flexible than large companies. </li></ul></ul><ul><ul><li>SMEs are stronger at local business </li></ul></ul>
  • 6. Why service tailoring in particular? <ul><li>Two ways to reach profitability according to Porter </li></ul><ul><ul><li>Commoditize the services and go as quickly to the right as possible. </li></ul></ul><ul><ul><li>To play in a niche market: almost infinite number of small players. </li></ul></ul>Market Share Profitability Small players Big players Niche markets, exceptional services, premium price Commodity services (mass market), lower prices, use efficiency of scale VISP: niche market of tailored services The famous Michael Porter&apos;s curve Challenge: getting bigger but not getting more profitable Challenge: specializing but not getting more profitable
  • 7. What means service tailoring? 1) Select available ISP service like VoIP 2) Decompose ISP service into reusable parts 3) Compose new ISP service from the available parts – Service tailoring ( orchestration ) T oo many services (parts) to be done alone: cluster of partners ! VISP Service Architect
  • 8. What is a VISP Virtual Enterprise ? Community or Virtual Enterprise Internal trading (economic models, new workflows) <ul><li>Partners are independent organisations (SMEs) with their own business objectives and strategies. </li></ul><ul><li>Business and technical workflows are required inside of the cluster with a common unique portfolio of services . </li></ul><ul><li>Every partner can sell services offered by all others and each new partner makes the Virtual ISP more attractive, stronger and resilient . </li></ul><ul><li>Ally : entity whose products and/or services help to enhance the demand of the cluster. </li></ul><ul><li>Supplier : entity from which the cluster or any other entity obtains goods, services or information. </li></ul>VISP cluster Supplier 1 Supplier 2 Supplier 3 Ally 1 Ally 2 Customer 1 Customer 2 Customer 3 Partner 1 Partner 3 Partner who is itself a cluster External trading (business model, classical Supply Chain Management and workflows)
  • 9. <ul><li>Automating as much as possible - t ranslation of BPMN diagrams into executable BPEL </li></ul>Business and Technical processes
  • 10. High level architecture
  • 11. Main technical choices - SOA <ul><li>BPMN and BPEL </li></ul><ul><ul><li>process modeling and execution </li></ul></ul><ul><li>WebServices </li></ul><ul><ul><li>« KISS » inside – SOAP over HTTP </li></ul></ul><ul><ul><ul><li>With WS-Addressing </li></ul></ul></ul><ul><ul><li>« Business ready » outside </li></ul></ul><ul><ul><ul><li>WS-ReliableMessaging </li></ul></ul></ul><ul><ul><ul><li>WS-Security </li></ul></ul></ul><ul><ul><ul><li>WS-Notification </li></ul></ul></ul><ul><li>Services </li></ul><ul><ul><li>Data repositories </li></ul></ul><ul><ul><li>Mediation with Network elements and ERPs </li></ul></ul>
  • 12. SOA Principles during Service Instantiation in VISP 2) Request orchestrated ISP service 1) Announce available ISP service building blocks 3) Discover , select and configure appropriate ISP service building blocks 4) Consume instantiated ISP service 5) Superwise and reconfigure ISP service building blocks VISP Customer VISP Mediator &amp; Controller VISP Partners
  • 13. General t echnical architecture
  • 14. Summary <ul><li>VISP is a project whose objective is to develop a software platform enabling a cluster of SMEs to collaborate and operate as a single business entity </li></ul><ul><li>Problems with openning telecommunication market for small ISP </li></ul><ul><li>Service tailoring (decomposition) </li></ul><ul><li>Intersection of two worlds: workflow and telecom technologies. </li></ul><ul><li>Two platforms: modelling and execution </li></ul><ul><li>VISP uses BPMN nad BPEL </li></ul><ul><li>VISP is based on SOA </li></ul>
  • 15. Thank you! Any questions?

×