1. Event-Driven Business Process Management
Reference Model, Reference Architecture, Business Processes and Internet Services,
Domain Specific Reference Models for Event Patterns and Use Cases
Development of an edBPM-Platform

2. Agenda The forecast of edBPM for the next decades
edBPM – a combination of two disciplines: Business Process Management (BPM) and Complex Event Processing (CEP)
A reference model for edBPM – how its components work together
edBPM-enhancements of the NEXOF-Reference Architecture
edBPM-enhancements of modeling and execution standards
Domain-specific standards for Notification Event Architectures
Standardising Event Processing Languages
Domain-specific reference models for use cases and event patterns
edBPM-based software solutions and products

3. The forecast of ED-BPM for the next decades
The forecast of Prof. David Luckham…
… we need skilled people at least up to 2050…
… we are only at the end of the period of Simple CEP

4. The forecast of ED-BPM for the next decades
The warning of Roy Schulte (VP of Gartner) since 2006…
…we won‘t have enough skilled people who would be able to do all the jobs and projects
The statement of Prof. Mani Chandy/California Techical University at the Gartner Event Processing Summit 2007…
…The work of IT during the next twenty years will be to complete the evolution of business processes from sequences of slow-moving, disjointed applications to more responsive end-to-end, event-based straight-through flows of action.

5. Managing and monitoring of processes and services mean ...
representation of the effects of system availabilities and -disturbances
monitoring of time-critical bottleneck factors and transaction control
Business Activity
Monitoring
Workflow
Management
process and system- linked emergency and disturbance management
transparency over integrated represented processes
integration of external processes and services
integration of external processes and services
monitoring of
SLA-compliance

6. Processes and services communicate via a global event cloud
event cloud with thousands of events per sec…
passwdchange
account login
event patterns and complex event processing…
new auto pay
account login
deposit
withdrawal
new auto pay
transfer
logout
enquiry
deposit
account login
activity history
Sensor 1
account balance
logout
enquiry
passwdchange
account login
new auto pay
enquiry
account login
deposit
withdrawal
new auto pay
transfer
account login
logout
enquiry
deposit
activity history
Sensor 2
logout
…e.g. above a bank
The important steps: 1. Redesign the business processes for SOA and BPM 2. Make a SOA, identify services, build WSDL-interfaces… 3. Precise description of patterns of events
4. Detecting patterns in the event cloud
5. Abstraction of complex event pattern instances to higher level events

7. The Event Cloud and the „Event Tornado“ Additional events are needed for modeling an interservices communication, for BAM and for a sufficient Business Insight
startedService_6
startedService_7
startedService_4
Today‘s existing event cloud and the IT-blindness
exitService_4
startedService_5
exitService_5
exitService_6
startedService_8
exitService_8
exitService_7
startedService_1
Low level events without semantics
exitService_1
startedService_2
exitService_2 …
BusinessProcess1
startedService_3
exitService_3
We all know the event cloud of low level events without any semantics, indroduced by Prof. David Luckham some years ago.
For our goal we have to enrich that cloud dramatically by additional events. That events, already mentioned, are generated either in the middleware resp. the BPEL engine resp. the ESB or as in our present case the interceptors are responsible for the event generation.
We call this the event tornado, which is blowing up the cloud heavily.
Visualization of the processed/correlated events via Business Activity Monitoring …
BusinessProcessn … 7

8. services and their events
The Challenge and the Principle of ED-BPM – Reference Model
Enterprise cockpit
Workflow
Modeler
realize scenario process instances
set parameters
Domain specific reference models for event patterns
Event
Modeler
Monitor / Analyze / Act
Workflow Engine
based on BPEL
workflows
Model ^=
Scenario
„unus mundus“-
Internet
services and their events
CEP Engine „special“ SQL resp. other languages
analyse history…
AppServer
Event
Store
What is special for the BPM/BAM/CEP perspective?
I guess, we‘ve a threefold challenge: first is the technology challenge, second is the multichanneling challenge and third is the challenge which is caused by SOA.
This slide (I‘m not the greatest desktop publisher!!) shall show the principle how a BPM/BAM/CEP platform could work, e.g. for NextGeneration Instant CreditSystems:
So, we‘ve the grey things, which concern the workflow resp. the BPM stuff,
and we‘ve the blue things, which concern the BAM and the CEP components.
I‘m quite sure that we‘ll have 2 different kinds of people: the workflow modelers or business analysts and the event modelers.
The models of business processes and event scenarios are deployed into a middleware platform, e.g. into an AppServer, which is responsible for high availability, limitless scalability, grid computing, failover, transparency of heterogeneous infrastructures and so on…
The workflow model, e.g. for a credit loan process, is executed by a BPEL based workflow engine, as a component deployed to the AppServer.
So, if a credit offer is completed, there will be generated a low level event…
Further, we need special so called adapters for each type of low level events, e.g. an RFID-adapter, an adapter for a Pub/sub-topic, for database commits and so on, e.g. we need special adapters for the completion of a credit offer and for filtering payments events.
Now, we‘ve the Rules Engine and we can define by a special language or tool what shall happen with the low level events, building higher business level events. The rules engine and the code of the rules are also deployed into the AppServer.
At last we can calculate as an ACTION the pott, as the result of the formula offer rates minus bank rates , real time, depending on the paramters which were set in the rules…
And at last we can show all the stuff in an Enterprise cockpit: the pott, offer rates, the current profit, performance of all the instances of the credit process and so on…
Normalized events, build business level events
IF … AND … FOLLOWED BY… WITHIN… ACTION
Adapters e.g. RFID, topics of Pub/Sub, …
e.g. JMS pub/sub
e.g. payments
show BAM- view, trigger a BP, change BP-flow…
Low Level Event Streams
e.g. GPS-signal
e.g. Traffic Message Controls
e.g. Weather Forecast
e.g. RFID …

9. NEXOF-RA enhanced by ED-BPM

10. Categorizing of ED-BPM use cases
Development of a taxonomy
Process type
Process instance
Action type
{list of domain specific processes}
{new, running, all}
{instantiate, stop, continue, terminate, change, new define}
Example: Use Case „Fraud-Management“ in the Banking-Domain
According to the reference model of edBPM-based Fraud-Management, we describe a simple example of the process
“Withdraw” in connection with a potential event pattern of fraud and related processes in order to exemplify the
edBPM principle:
An instance of a transaction process is started in the case of withdrawing at a certain ATM.
A lot of process instances of the same type are instantiated in a more or less short/certain timeframe at different ATM’s.
Each process step generates an event, if so of different event types (JMS publish/subscribe, special ATM-banking event type according to the banking standard “<…> ”
The global event cloud is analyzed in real-time by the CEP-system and optionally by some “intelligent” components like discriminant analysis and neural networks. A suspicious event pattern is detected because the login-data respectively the card is used more than once and at different locations in a timeframe whereas a service is called in order to check the probability that the same customer could use the same card at the different locations.
…< see BPM09 paper >
 [TE1]Tbd

11. discriminant analysis event filtering, enriching, correlating
A reference model of edBPM-based fraud management – Software solutions, products
fraud management processes
. . .
Real-time BAM, statistics…
alert
alert
alerts
. . .
output evaluation
neural network
needed to filter unkown suspicious event patterns
feed forward step
trigger fraud management process
input: current and historic discriminant values
fraud suspicious
not fraud suspicious
preclassification
needed to reduce the amount of suspicious event patterns
discriminant analysis
decision tree
known suspicious event patterns:
CEP-engine
needed to process thousands of events per sec
event filtering, enriching, correlating
. . .
adapter for event type-1
adapter for event type-n
suspend transaction process
event cloud
. . .
instance-1
transaction processes
. . .
e.g. ATM‘s in Tokyo, Rome, Munich
. . .
instance-n
e.g. Internet banking

12. Modelling of the use cases
Typical workpackages before implementing PoC’s:
SOA-appropriate BP-modeling of the use cases per domain
Event-modeling of the use cases and instrumenting process steps and services for an appropriate event generating
Definition of BAM-views per use case
Description of reference models per use case according to the edBPM/DoReMoPat-pattern framework

13. edBPM-enhancements of standards, e.g. WS-BPEL
Pattern 1: Stop one or more running processes upon event
This pattern solves the cases ? and ? of para This could be achieved by using the fault handling mechanism available in WS-BPEL In order to activate the corresponding fault handler we can the use event handler that is activated by a complex event occurrence. The event handler throws a fault that stops all the currently running activities. A strong benefit of using loosely coupled event-driven solution is the ability to stop any number of running processes upon a single event: all the processes subscribed to this event will be affected. This is opposed to a ‘conventional’ peer-to-peer approach that would require explicit sending a request to each one of the processes that should be stopped.
Pattern 2: Start a new process instance upon event
This pattern solves the cases ? and ? of para Standard WS-BPEL allows starting a new process instance upon an incoming message (via the receive element). We extend the receive element with the ability to specify an event name or an event pattern instead of a message. In order to activate a new process instance the enhanced receive version could be used. If there are several possible events or messages that should start the same process the pick element can be used in a similar manner.
Pattern 3: Activate a task or a process in the absence of the expected event within some time period
This pattern solves the cases ? and ? of para The absence of some event is an event pattern by itself. It can be specified in an event processing language and detected by an event processing system. Therefore, this pattern is a special case of the above one (start a new process upon event).
Pattern 4: Suspend a process and resume upon event
This pattern solves the cases ? and ? of para This pattern can be implemented using one of the synchronous BPEL constructs, i.e. receive or pick. For this specific use case (‘fraud’) pick is preferable because it allows handling time out situations, that is what happens if the ‘false positive’ decision is never made.
Pattern 5: Start a process modification/adaptation upon event
This pattern solves case 10 of para 3.2. The pattern can be implemented using the enhanced version of the event handler mechanism. The event handler is activated upon an instance of the specified trigger event (e.g. ‘Too Many False Positives’). The enclosed activity can modify the BPEL variable that participates in ‘fraud detection’ pattern calculation, or submits an update request to the event processing system. If the case requires modifying the workflow, the workflow adjustment could be considered as a separate process that is started upon this event. As soon as the new process version is available, it will be activated. The process and possible issues of activating a modified process in presence of an older version of the process is out the scope of this paper.
Master thesis Alex Kofman Technion University Haifa
. . .

14. Domain-specific Notification Event Architectures – Existing and future standards
“Common Postal Address” Architecture of NEALogistics
Customer Event Domain Model of NEARetail
Model of the “AccountTransactionEvent” of NEAFinance
Tracking Event Architecture
Order Event Architecture

15. Proposal for contributing to NESSI Software+Services Platform
NESSI platform consists of nine working groups:
Open Source 
Services Sciences
Security, Trust and Dependability
Software Engineering
User Services Interactions
Business Process Management
Semantic Technologies
Service Engineering
Service Oriented Infrastructure
NESSI also founded a SME-working group.
NESSI has 3 "Committees" for the main foci "Future Internet",
"Standardisation" und "Strategic Research Agenda (SRA)".
We already contribute

16. Dissemination

17. The business modeler and the event modeler – different qualifications not in personal union
A proposal for a curriculum of a new international Master course of study “Event-Driven Business Process Management”
Description: Curriculum together with required credits and examinations
Certificate: Master of Science
Programme Duration: Four Semesters (120 credits/cr)
Mastercourse-EDBPM-v02.doc

18. The business modeller and the event modeller – different qualifications not in personal union
Concept:
The course consists of the fields of study Business Process Management, Complex Event Processing, Business Activity Montoring included Business Intelligence and Data Warehousing, Computer Networks, Messaging as well as several application disciplines like Algorithmic Trading, Supply Chain Management in the retail domain, fraud detection in the banking and insurance domain etc. All courses are completed with course-related tests and Credits (cr) according to European Credit Transfer System (ECTS) are awarded. All courses are given in English and are designed as distance learning/eLearning courses.

19. Dissemination and Previous Work Examples of last contributions to conferences
edBPM/DoReMoPat at FP7-ICT Proposers' Day 2009, January 22, Budapest
edBPM exhibition SSOKU st European Conference on Software Services and SOKU technologies, Brussels, January 13 – 14, 2009
edBPM-Workshop ServiceWave 2008, Madrid, December 10 – 13, 2008
8th edBPM Expert Meeting Regensburg, Germany, December 8 – 10, 2008
Rainer v. Ammon, Andreas Hehmann Mainz, Germany, October 7 - 9, "Event-Driven Business Process Management Taking the Example of Hamburger Sparkasse" EDBPM-Haspa.ppt Rainer v. Ammon, Christoph Emmersberger, Florian Springer, Christian Wolff Vienna, September , 2008 FIS 2008 / 1st International Workshop on Complex Event Processing for Future Internet - Realizing Reactive Future Internet - "Event-Driven Business Process Management and its Practical Application Taking the Example of DHL" FIS08_AmmonSpringer.pps Rainer v. Ammon New York/Stamford, September , th EPTS symposium "Proposal for a new Master course of study - Event-Driven Business Process Management" EDBPM-mastercourse.ppt Adrian Paschke, Rainer v. Ammon Irsee Monastery, Bavaria, Germany, July , 2008 Focus Group for EuroPLoP 2008 Domain-specific Complex Event and Rule Patterns Agenda for the focus group... 19 19

20. Thanks for your attention!