OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Call for Papers, edBPM11, 5th International Workshop on Event-Driven Business Process Management, collocated with BPM 2011

---------------------------------------------------------------------------------------------

Dear colleagues (with apologies for cross-posting),

 

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

 

«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.

 

Loosely coupled event-driven architecture for BPM provides important benefits:

 

• Responsiveness. Events can occur at any time from any source and processes respond to them immediately, whenever they happen and wherever they happen.

• Agility. New processes can be modeled, implemented, deployed, and optimized more quickly in response to changing business requirements.

• Flexibility. Processes can span heterogeneous platforms and programming languages. Participating applications can be upgraded or changed without breaking the process model.

 

 

TOPICS

 

Authors are invited to submit novel contributions in the above mentioned problem domain. Specifically, the relevant topics include, but are not limited to:

 

• Event-driven BPM: Concepts

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

• Design-time CEP and BPM

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.

• Run-time CEP and BPM

e.g. event pattern detection, BPEL and event processing, reasoning about unknown/ similar events

• Applications/ Use use cases for event-driven BPM

e.g. event-driven monitoring/ BAM , event-driven SLA monitoring, context-aware BPM

 

 

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.

 

 

SUBMISSION

 

The following types of submission are solicited:

• Long paper submissions, describing substantial contributions of novel ongoing work. Long papers should be at most 12 pages long.

• Short paper submissions, describing work in progress. These papers should be at most 6 pages long.

• Use case submissions, describing results from an edBPM use case. These papers should be at most 4 pages long.

 

 

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).

Papers can be uploaded via the workshop page on easychair, the address can be found on the workshop homepage.

Papers will be published in the postconference proceeding (Springer Verlag)

 

 

IMPORTANT DATES

 

Deadline paper submissions:  May 6, 2011

Notification of acceptance: June 2, 2011

Camera-ready papers: June 17, 2011

Workshops: August 29, 2011

 

 

ORGANISING COMMITTEE:

 

Dr. Nenad Stojanovic

FZI - Research Center for Information Technologies at the University of Karlsruhe

Germany

Nenad.Stojanovic@fzi.de

 

 

Dr. Opher Etzion

Senior Technical Staff Member,   Master Inventor

Event Processing Scientific Leader

IBM Research Lab in Haifa

OPHER@il.ibm.com

 

 

Prof. Dr. Adrian Paschke

Corporate Semantic Web, Free University Berlin, Germany and

RuleML Inc., Canada

paschke@inf-fu-berlin.de

 

 

Dr. Christian Janiesch

Senior Researcher

SAP Research Center Brisbane 

Australia

Christianc.Jjaniesch@sap.com

 

 

Additional information

 

A complete overview about relevant topics, detailed workshop information and contact addresses can be found on the workshop website http://icep-edbpm11.fzi.de

 

------------------------------------------------------------------------------------------------------------------------------------



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]