<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.E-MailFormatvorlage18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.E-MailFormatvorlage19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.E-MailFormatvorlage20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.E-MailFormatvorlage21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.E-MailFormatvorlage22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US>---------------------------------------------------------------------------------------------<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Dear colleagues (with apologies for cross-posting),<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>you are invited to submit papers for the 5th International Workshop on Event-Driven Business Process Management to be held alongside the Busines Process Management Conference on August 29th 2011 in Clermont-Ferrand, France<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>«Event-Driven Business Process Management» (EDBPM) is an enhancement of Business Process Management (BPM) by new concepts of Service Oriented Architecture (SOA), Event Driven Architecture (EDA), Software as a Service (SaaS), Business Activity Monitoring (BAM) and Complex Event Processing (CEP). In this context, BPM means a software platform which provides companies the ability to model, manage, and optimize these processes for significant gain. As an independent system, CEP is a parallel running platform that analyses and processes events. The BPM- and the CEP-platform correspond via events which are produced by the BPM-workflow engine and by the – if distributed –- IT services which are associated with the business process steps. Also events coming from different event sources in different forms can trigger a business process or influence the execution of the process or a service, which can result in another event. Even more, the correlation of these events in a particular context can be treated as a complex, business level event, relevant for the execution of other business processes or services closing the loop of insight-to-action. A business process – arbitrarily fine or coarse grained – can be seen as a service again and can be “choreographed” with other business processes or services, even between different enterprises and organisations.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Loosely coupled event-driven architecture for BPM provides important benefits: <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>• Responsiveness. Events can occur at any time from any source and processes respond to them immediately, whenever they happen and wherever they happen. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Agility. New processes can be modeled, implemented, deployed, and optimized more quickly in response to changing business requirements. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Flexibility. Processes can span heterogeneous platforms and programming languages. Participating applications can be upgraded or changed without breaking the process model. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>TOPICS<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Authors are invited to submit novel contributions in the above mentioned problem domain. Specifically, the relevant topics include, but are not limited to:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>• Event-driven BPM: Concepts<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>e.g. role of event processing in BPM, business events: types and representation, vent stream processing in business processes, process event processing in CEP, data- and event-driven business processes, event and process interaction patterns <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Design-time CEP and BPM<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>e.g. modelling modelling events in human-oriented tasks, semantics/ontologies for event-driven BPM, BPMN and event processing, interaction modelling of process model and event processing network.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Run-time CEP and BPM<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>e.g. event pattern detection, BPEL and event processing, reasoning about unknown/ similar events <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Applications/ Use use cases for event-driven BPM<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>e.g. event-driven monitoring/ BAM , event-driven SLA monitoring, context-aware BPM<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The Workshop is planned as a full-day event, including a keynote, paper presentations, lightning talks, demos, posters, and a moderated, open discussion with the clear goal of agreeing upon a research roadmap for event-driven Business Process Management research, by taking into account new challenges, described earlier.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>SUBMISSION<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The following types of submission are solicited: <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Long paper submissions, describing substantial contributions of novel ongoing work. Long papers should be at most 12 pages long. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Short paper submissions, describing work in progress. These papers should be at most 6 pages long.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>• Use case submissions, describing results from an edBPM use case. These papers should be at most 4 pages long.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Papers should be submitted in the new LNBIP format (http://www.springer.com/computer/lncs?SGWID=0-164-7-487211-0). Papers have to present original research contributions not concurrently submitted elsewhere. The title page must contain a short abstract, a classification of the topics covered, preferably using the list of topics above, and an indication of the submission category (Long Paper/ Short Paper / Use case).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Papers can be uploaded via the workshop page on easychair, the address can be found on the workshop homepage.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Papers will be published in the postconference proceeding (Springer Verlag)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>IMPORTANT DATES<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Deadline paper submissions: May 6, 2011<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Notification of acceptance: June 2, 2011<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Camera-ready papers: June 17, 2011<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Workshops: August 29, 2011<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>ORGANISING COMMITTEE:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Dr. Nenad Stojanovic <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>FZI - Research Center for Information Technologies at the University of Karlsruhe<o:p></o:p></span></p><p class=MsoNormal>Germany<o:p></o:p></p><p class=MsoNormal>Nenad.Stojanovic@fzi.de<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dr. Opher Etzion<o:p></o:p></p><p class=MsoNormal><span lang=EN-US>Senior Technical Staff Member, Master Inventor<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Event Processing Scientific Leader<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>IBM Research Lab in Haifa<o:p></o:p></span></p><p class=MsoNormal>OPHER@il.ibm.com<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Prof. Dr. Adrian Paschke <o:p></o:p></p><p class=MsoNormal><span lang=EN-US>Corporate Semantic Web, Free University Berlin, Germany and <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>RuleML Inc., Canada<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>paschke@inf-fu-berlin.de<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Dr. Christian Janiesch<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Senior Researcher<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>SAP Research Center Brisbane <o:p></o:p></span></p><p class=MsoNormal>Australia<o:p></o:p></p><p class=MsoNormal>Christianc.Jjaniesch@sap.com<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Additional information<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>A complete overview about relevant topics, detailed workshop information and contact addresses can be found on the workshop website http://icep-edbpm11.fzi.de<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal>------------------------------------------------------------------------------------------------------------------------------------<o:p></o:p></p></div></body></html>