The Power Of Event Chapter 2

Chapter 2Managing the Electronic Enterprise in the Global Event Cloud

[email protected]

Topics covered in this Chapter

● The global event cloud● How enterprises operate in the global event cloud● Management process - going beyond workflow● Autonomous parallel, asynchronous process● The electronic enterprise● Treating the exceptional situation as normal● Enabling the human to control the electronic enterprise● Technology demands for managing the electronic

enterprise

2.1 How the Global Event Cloud Forms 1/2

● The Open Enterprise○ Their boundaries become blurred.○ The enterprise is becoming open to permit the

event traffic it needs to pursue its collaboration.● The Global Event Cloud

○ a "cloud" of events rather than a "stream" because

the event traffic is not, in most cases, nicely organized.

2.1 How the Global Event Cloud Forms 2/2

● The Electronic Enterprise○ "Event driven"

■ whatever tools and applications are used to automate business and enterprise management processes,

■ those tools and applications rely on receiving

events to monitor the progress of a process and issuing events to initiate its next stage.

2.2 Operating in the Global Event Cloud 1/3

● Enterprise management processes today typically consist of a large number of linear workflows like this one, loosely strung together and nested one inside another.

● In carrying out this simple linear workflow, the boundaries of enterprise are crossed by outgoing and incoming events many times. ProcessOrder

1. New Order

2. Select Vendor

3. Pick, Pack, and Ship Product

4. Billing


Spare Part Query

Terminate Instance

Select Product

Ship Reqeust

GL QueryInvoice Print

Ship Quote

Ship Order

Invoice PrintSerice

Requeset

Valid ServiceProcess Order

1. New Order

2. Select Vendor


4. Billing

Process ActivitiesValid Order When a valid order is

received, select the vendor with the lowest price.

When a vendor is selected, send a ship order to the vendor's warehouse.

When a UPS routing number is received, terminates the process.

Process RulesGlobal Event Cloud

Select Vendor

Vendor Selected

Ship Order

Product Shipped

Terminate Instance


● In Figure the ProcessOrder workflow is on the left, the global event cloud in the center, and the rules that drive the workflow process are on the right.

● The rules that drive the process are "reactive rules".● These events that drive the workflow process are

transported back and forth between the activities and the workflow rules engine by the enterprise IT layer.

The process is event driven.

2.3 Going Beyond Workflow 1/2

● To enter the world of global Internet marketplace decision making, business and management process must meet the reduced time scales and increased situational complexities that will be involved.

● The management processes of the electronic enterprise will be built to optimize their execution times.

● They soon will be parallel, asynchronous processes.

2.3 Going Beyond Workflow 2/2

● 3 key tech for Autonomous Parallel Processing:○ Enterprise management processes will

■ Be completely automated and event driven.■ Execute in parallel.■ Make decision and communicate asynchronously.

○ The human will be taken out of the loop to make all the activities in the process fully autonomous.

○ The human will be kept in control over the processes by being provided with■ Personalized, real-time viewing to make decision■ On-the-fly modifiable process rules, including exceptional

situation handling, to modify and control processes.

2.4 Parallel and Asynchronous Processes 1/4

● The SelectVendor process is expanded into a set of subprocesses that exectue in parallel and asynchronously.

● All subprocesses can be executing at the same time.ProcessOrder

1. New Order

2. Select Vendor


4. Billing


Spare Part Query

Select Product

Ship Reqeust

GL Query

Invoice Print

Ship Quote

Ship Order

Invoice PrintSerice

Requeset

Valid Service

Global Event Cloud

Valid Order

Submit RFQs when a valid order is received

Accept bids for three hours.

Send ship order to selected vendor.

Process Rules

RFQ1

RFQ2

Bid1

Bid2

Ship Order

RFQ3

Submit RFQs to vendors with 90% ship

to promise history

Timing Event

Select vendor with lowet priceBid3

Asynchronous Action

Asynchronous Action


● The patterns of events the rule engine creates and reacts to are much more complex than in the case of linear workflow.

● Rules trigger on sets of events (not single events), execute in parallel, and output sets of events.

● Rules will trigger on a set of events only if the events match a specified pattern and the context in which the events are received is the right one.


● Technology demands for achieving parallel, asynchronous processes include:○ Scalable complex event pattern matching, taking into

account the context or state at the time of a match○ The ability to reuse the data in sets of events that

match a rules pattern in the creating of new events.● We need a capability to match complex event patterns

in the global event cloud. These patterns are needed to trigger reactive rules.

2.5 On-the-Fly Process Evolution 1/3

● We cannot expect to design our processes to foresee or react to every situation. We will need to adjust them frequently by changing their responses to a situation or to recognize a new situation.

● On-the-fly evolution means the ability to modify a process without halting the rules engines or disrupting the execution of other processes


Spare Part Query

Select Product

Ship Reqeust

GL Query

Invoice Print

Ship Quote

Ship Order

Invoice PrintSerice

Requeset

Valid Service

Global Event Cloud

Valid Order




Process Rules

RFQ1

RFQ2

Bid1

Bid2

Ship Order

RFQ3


to promise history

Timing Event


Submit RFQs to all qualified vendors

Modified Rule

Asynchronous Action

Asynchronous Action

Select first bid under $300

Modified Rule


● Technology demands for controlling and modifying electronic processes are○ Real-time, personalized viewing of activity at every

level in the enterprise.○ On-the-fly process modification○ Simulation of processes before going live

2.6 Exceptions Must Be First-Class Citizens in Process Design 1/3

● If a process fails to behave in a given situation as specified or meets a situation for which it has no specification, it is said to have encountered an exception.

● So, the process design technology should let us design normal processing and exceptional processing in the same way.


● However, there are some distinguishing problems in dealing with exceptions○ We must be made aware of their presence in real

time.○ We must be able to find out what causes them

● We need a diagnostic capability to uncover the subprocesses and events that are causally related to an exceptional situation, and their subprocesses, and so on, and the state of each subprocesses all the way down the causal chain.


Spare Part Query

Select Product

Ship Reqeust

GL Query

Invoice Print

Ship Quote

Ship Order

Invoice PrintSerice

Requeset

Valid Service

Global Event Cloud

Valid Order




Process Rules

RFQ1

RFQ2

Bid1

Bid2

Ship Order

RFQ3


to promise history

Timing Event


If no vendor is selected within

three hours, submit bids to vendors with a

75% ship to primise history.

If no vendor is selected from

vendors with 75% ship to primise

history, send alert to purchasing

manager.

ExceptionRule

2.7 Summary: Managing the Electronic Enterprise

● An ability to design and deploy event-driven parallel and asynchronous processes that can recognize complex event situations in the global event cloud

● Process simulation as part of the design phase, before going live

● On-the-fly modifiable processes● Design for handling exceptional situations as an integral

part of prcess desgin● Real-time, drill-down, event-based diagnostics, utilizing

event causality relationships, applicable to process behavior

The Power Of Event Chapter 2

Technology

Transcript of The Power Of Event Chapter 2