BPMN: Past, Present, and Future - BPM 2012bpm2012.ut.ee/wp-content/uploads/2012/03/keynote-white.pdf · BPMN Design Guidelines: Complexity Business Process, by their nature, can include

Stephen A. White – IBM: BPM Architect

6 September 20126 Sep e be 0

BPMN:Past, Present, and Future

Editable Text Editable Text Editable Text

© 2012 IBM Corporation

Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future

ConclusionsConclusions

© 2012 IBM Corporation2

Source: If applicable, describe source origin

Applied Process Modeling1

Ordering Office Supplies


1Scott Adams, Journey to Cubeville: A Dilbert Book, 1998, ISBN-13: 978-0-8362-6745-7

What is BPMN?

BPMN is a graphical notation for defining Business Processes

Receive Supply Check Supply Deny

Complain About Supply

Request Cabinet Request Requester


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future




Origins of BPMN

The Business Process Management Institute (BPMI—now a part of the OMG) developed an XML process execution language and realized the need for a graphical representation – there were many proprietary

t tinotations– August, 2001, the Notation Working Group is formed, with 35 companies,

organizations, or individuals. More than Ten Years Ago!

BPMN 1 X BPMN 1.X– May, 2004, the BPMN 1.0 specification was released to the public.– February, 2006, BPMN 1.0 was adopted as an OMG standard– January 2008, BPMN 1.1 became available, significant changesJanuary 2008, BPMN 1.1 became available, significant changes– January 2009, BPMN 1.2 became available, minor changes

BPMN 2.0– January 2011 BPMN 2 0 became available


January 2011, BPMN 2.0 became available

BPMN 3.0?6

The Vision for BPMN

The BPMN will provide businesses with the capability of understanding their internal and external business procedures with a graphical notation and will give organizations the ability to communicate these procedures in

t d d 1a standard manner.1


1"BPMN Fundamentals," BPMI Presentation, April, 2002

BPMN Development Drivers

M t b t bl d bl b thMust be acceptable and usable by the business community for general process modeling

C fli ti

Must be able to generate executable processes from a BPMN Model (through a

Conflicting Requirements!

processes from a BPMN Model (through a combination of graphical elements and supporting information (attributes))

BPMN is intended to be Methodology Agnostic

– Resulting in some redundancyMethodologies ill gi e g idance as to the


– Methodologies will give guidance as to the purpose and level of detail for modeling

– BPMN is as complex as it needs to be. Just use what you need…8

BPMN Design Guidelines: Complexity

Business Process, by their nature, can include complex behavior. Yet, most users desire a simple notation and supporting methodologies

– But they often complain when some behavior cannot be modeled.

There is no real solution, only an approach, e.g.:–Use a basic, familiar flow-chart structure

• Reuse familiar shapes where possible (e.g., rectangular activities, decision diamonds, etc.)

–Create a small set of core elements–Create variations of the core elements to introduce complexity.

S f th i ti t i d f i l d li• Some of the variations are not required for simple modeling–Don’t surface all Process characteristics in the notation

• Leave some information as details found in dialog boxes, for example


example

BPMN’s future may include even more complexity: see below.9

BPMN and BPM

BPMN is a subset of BPM– BPMN is a language for defining Process behavior– BPM requires other languages and technologies to be operational

• Data Resources Rules User Interfaces etcData, Resources, Rules, User Interfaces, etc

BPMN should not be confused with BPM technology applications and constraints– E.g., BPM Lifecycles


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future



BPMN and its Use Today

BPMN has been a successful standard– End user organizations and governments are consistently

standardizing on BPMN

Currently, there are about 70 companies that have implementations of BPMN– 45 companies or so implement BPMN 1.X– 25 companies or so implement BPMN 2.0

This is based on vendor reporting– No conformance tests existNo conformance tests exist


Relationship to other OMG Standards

UML:– Mappings have been done between UML and BPMN and published as articles

SoaMLS C– Initial mappings have been done between SoaML and BPMN Collaborations

– Nothing published at this point

Case Management Modeling Notation (CMMN)CMMN till i– CMMN still in progress

– A CMMN model can invoke a BPMN Process


Agenda

Introduction

BPMN past

BPMN tBPMN presentBPMN Diagrams

BPMN Elements

BPMN Innovations

BPMN Conformance Levels

BPMN future

Conclusions


BPMN Diagrams

BPMN has four types of diagrams–Process–Collaboration

C ti–Conversation–Choreography


Process Diagram

A Process shows the sequence of Activities performed by an organization

Request Hold

Send Hold Reply

Hold

Two Weeks

Get Book Status

Receive Book

Request

Book ison Loan

Send On Loan Reply

Cancel Request

DeclineHold

BookWait for Response

Book is Available

Send

Hold

One Week


Checkout Book

Send Checkout

Reply

Collaboration

Collaborations show the

Customer

OrderConfirmation Shipment Collaborations show the

interaction, through Message Flow, between Participants (Pools) A Handle Order

Manufacturer

Order p

Rejection

Participants (Pools)–Pools can be black-

box or contain a Process Send Rejection

to CustomerCapacity not

Available

Capacity & Parts Available

A

Can FulfillOrder?

Handle Order

Some Parts Unavailable

Order Arrives

to CustomerAvailable

Capacity OK, Parts Mustbe Ordered

PartsProcured

Procure Parts

AProcured

Supplier

PartResponse

PartRequest

PartRequest

PartResponse

Bidder


Choreography

A Choreography process interactions between two or more Participants

Extends Collaboration with the flow of the interactions and is more scalable

Order Confirmation

Customer

Manufacturer

Deliver Order

Customer

Manufacturer

YesA

Order Confirmation Shipment

Order Request

Customer

Manufacturer

Order Rejection

Customer

Manufacturer

Can FulfillOrder?

No

YesNo

Order Confirmation

PartRequest

p

Procure Parts

Manufacturer

Supplier

Capacity OK, Parts Mustbe Ordered

A

YPart Auction

Manufacturer

Rejection

Request

PartRequest

All PartsAvailable?

All PartsObtained?


No A

YesPart Auction

Bidder

PartResponse

PartResponse

Conversation

Conversations logicallyDelivery

NegotiationsSupplierRetailer

Conversations logically group the Message Flow of a Collaboration

–Creating a higher-levelDelivery / Dispatch

PlanShipment ScheduleConsignee

Creating a higher level view

Delivery / Dispatch Plan

Delivery / Dispatch Plan Carrier Planning

Delivery Monitoring

ShipperConsolidator Plan

Clearance Monitoring

Coverage Clearance Pre-

ShipperConsolidatorCarrier

(Land, Sea, Rail, or Air)

NotificationNotification

Truck Breakdown Provision

Arrival/Pickup Confirmation

Traffic Optimization Guidance

Breakdown Service

Locative Service

InsuranceCustoms/Quarantine


Agenda

Introduction

BPMN past


BPMN Elements

BPMN Innovations


BPMN future

Conclusions


Process Diagram Elements


BPMN 2.0 Elements

Events

Flow Objects

Activities

G tGateways

Swimlanes me

Swimlanesam

eN

am


Nam

e Na

Nam

e

Full List of BPMN 2.0 Elements

Task Sub-Process (Collapsed)

Sub-Process (Expanded)Call (Process)

TransactionSequence Flow

ConditionalSequence Flow

D f lt

Event Sub-Process

(Message)

Event Sub-Process (Non-Interrupting

Message)

Sub-Process (Expanded)

User Task

Service Task

Call (Global User Task)

Start Event

Send Task

~Ad Hoc Sub-

Process

Loop Activity

Multi-Instance Activity

Message Start Event

TimerStart Event

Signal Start Event

Conditional Start Event

Message Flow

Association

Data Association

DefaultSequence Flow

Multiple Start Event

Parallel Multiple Start Event

Error Start Event

(Event Sub-Process)

Escalation Start Event

(Event Sub-Process)

Error Start Event

(Event Sub-Process)

Event Sub-Process (Timer)

Event Sub-Process (Error)


Timer)

Event Sub-Process

Event Sub-Process (Non-interrupting

E l ti )

Receive Task

Activity

Link Event(Catch)

MessageIntermediate Event(Catch/Boundary)

TimerIntermediate Event(Catch/Boundary)

ErrorIntermediate Event

(Boundary)

SignalIntermediate Event(Catch/Boundary)

ConditionalIntermediate Event(Catch/Boundary)


(Non-InterruptingEvent Sub-Process)



Message Start Event


TimerStart Event


Signal Start Event






CompensationIntermediate Event

(Boundary)

MultipleIntermediate Event(Catch/Boundary)


Receive Task

(Initiate Process)

(Escalation) Escalation)

Event Sub-Process

(Compensation)

Event Sub-Process

(Conditonal)


Conditional)

EscalationIntermediate Event(Non-Interrupting

Boundary)

Compensation Activity

CancelIntermediate Event

(Boundary)

End Event

ManualTask

Business Rule Task

Script Task

Call (Global Manual Task)

Call (Global Business Rule

Task)

Call (Global Script Task) Message

End EventTerminateEnd Event

Link Event(Throw)

SignalEnd Event

MessageIntermediate Event

(Throw)

MessageIntermediate Event(Non-Interrupting

Boundary)

TimerIntermediate Event(Non-Interrupting

Boundary)

ErrorEnd Event


Boundary)

EscalationIntermediate Event

(Throw)

EscalationEnd Event

SignalIntermediate Event(Non-Interrupting

Boundary)

SignalIntermediate Event

(Throw)

ConditionalIntermediate Event(Non-Interrupting

Boundary)


(Throw)

CompensationEnd Event

MultipleIntermediate Event(Non-Interrupting

Boundary)

MultipleIntermediate Event

(Throw)



Boundary)

Event Sub-Process (Signal)


Singal)

Event Sub-Process (Multiple)


Multiple)

Event Sub-Process (Parallel

Multiple)

Event Sub-Process (non-interrupting Parallel Mulitple) Cancel

End Event

Data Object

Text Annotation

Data Store

Group

Data Input Data Output

Exclusive Gateway

Parallel Gateway

Inclusive Gateway

Event Gateways

ConversationLink

Conversation

Call Conversation(Global Conversation)

Sub-Conversation

Call Conversation(Collaboration)

Data Object(Collection)


Agenda

Introduction

BPMN past


BPMN Elements

BPMN Innovations


BPMN future

Conclusions


BPMN Innovations, e.g.,

Boundary Intermediate Events

tient Send Doctor

RequestIll

Receive Appt. Send Symptoms

Receive Prescription

Pickup

Send Medicine Request

Receive Medicine

Pa

cept

ioni

st

1) I want to see doctor

Send Availability Request

Receive Doctor

Availability

Illness Occurs

Send Booking Send Appt.

5) Go see doctor

6) I feel sickReceive

Prescription Preparation

p

8) Pickup your medicine and you can leave

Receive Medicine Request

9) need my medicine

10) Here is your medicine

Receive Doctor

RequestSend Medicine

e

Provide Medicine Pools, Lanes, and Message Flow

Rec

Doc

tor

2) Are you available?

Send Doctor Availability

3) I'm available4) I'll book you

Receive Booking

Receive Symptoms

Receive Availability Request

Send Prescription Preparation

7) Prepare this medicine

Send Prescription

Pickup

Doc

tor’s

Offi

ce

Order[Approved] Fulfill OrderData

Data Input

Message Flow

Separation of data and control flow

[ pp ]

Order Approved?

Review and Approve Order

Fulfill OrderOutput

© 2012 IBM Corporation25 Order[Rejected]

Reject Order

Agenda

Introduction

BPMN past


BPMN Elements

BPMN Innovations


BPMN future

Conclusions


Descriptive Conformance Level

S b ProcessSub-Process (Expanded)

Call (GlobalTask

User Task

Sub-Process (Collapsed)

Call (Global Task)

Call (Process)

Sequence Flow

Service Task

GroupSequence Flow

Message Flow

A i ti

Data Association

Start Event

End Event

Message Start Event

MessageEnd Event

TimerStart Event

TerminateEnd Event

Group

Association

Data Object

Text Annotation Data

Store

End Event End Event

Exclusive Gateway

Parallel Gateway


Analytic Conformance Level

Poo

l

Lane

neLa


Common Executable Conformance LevelUser Task

Service

Sub-Process (Collapsed)

Sub-Process (Expanded)Call (Global

Task)

Service Task Call (Process)

Loop Activity

Start Event Message Start Event

Exclusive Gateway

Parallel Message Timer ErrorE t


Sequence Flow

Parallel Gateway


MessageI t di t E t

TimerIntermediate Event

(Catch)


(Boundary)

Event Gateway

Sequence Flow

Data Association

End Event MessageEnd Event

TerminateEnd Event



Intermediate Event(Throw)


Data Object

Text Annotation

Data Association


Full Conformance Level

Task Sub-Process (Collapsed)

Sub-Process (Expanded)Call (Process)

TransactionSequence Flow


D f lt

Event Sub-Process

(Message)


Message)

Sub-Process (Expanded)

User Task

Service Task

Call (Global User Task)

Start Event

Send Task

~Ad Hoc Sub-

Process

Loop Activity


Message Start Event

TimerStart Event

Signal Start Event


Message Flow

Association

Data Association




Error Start Event

(Event Sub-Process)


(Event Sub-Process)

Error Start Event

(Event Sub-Process)

Event Sub-Process (Timer)

Event Sub-Process (Error)


Timer)

Event Sub-Process


E l ti )

Receive Task

Activity

Link Event(Catch)


TimerIntermediate Event(Catch/Boundary)


(Boundary)

SignalIntermediate Event(Catch/Boundary)

ConditionalIntermediate Event(Catch/Boundary)





Message Start Event


TimerStart Event


Signal Start Event







(Boundary)



Receive Task

(Initiate Process)

(Escalation) Escalation)

Event Sub-Process

(Compensation)

Event Sub-Process

(Conditonal)


Conditional)


Boundary)

Compensation Activity

CancelIntermediate Event

(Boundary)

End Event

ManualTask

Business Rule Task

Script Task

Call (Global Manual Task)

Call (Global Business Rule

Task)

Call (Global Script Task) Message

End EventTerminateEnd Event

Link Event(Throw)

SignalEnd Event

MessageIntermediate Event

(Throw)

MessageIntermediate Event(Non-Interrupting

Boundary)

TimerIntermediate Event(Non-Interrupting

Boundary)

ErrorEnd Event


Boundary)

EscalationIntermediate Event

(Throw)

EscalationEnd Event

SignalIntermediate Event(Non-Interrupting

Boundary)

SignalIntermediate Event

(Throw)

ConditionalIntermediate Event(Non-Interrupting

Boundary)


(Throw)



Boundary)

MultipleIntermediate Event

(Throw)



Boundary)

Event Sub-Process (Signal)


Singal)

Event Sub-Process (Multiple)


Multiple)

Event Sub-Process (Parallel

Multiple)

Event Sub-Process (non-interrupting Parallel Mulitple) Cancel

End Event

Data Object

Text Annotation

Data Store

Group


Exclusive Gateway

Parallel Gateway

Inclusive Gateway

Event Gateways

ConversationLink

Conversation

Call Conversation(Global Conversation)

Sub-Conversation

Call Conversation(Collaboration)

Data Object(Collection)


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future




The Vision for BPMN

The BPMN will provide businesses with the capability of understanding their internal and external business procedures with a graphical notation and will give organizations the ability to communicate these procedures in

t d d 1a standard manner.1


1"BPMN Fundamentals," BPMI Presentation, April, 2002

BPMN Vision vs. Business Process Types

There is a wide range of Business Process types that are required for normal operations of most organizationsp g

–BPMN has focused on the more controlled, prescriptive types of internal Processes

–External Processes modeled through Collaboration, Conversation, and Choreography

Note that Adaptability is different from the range of Business Process typesyp


Areas of BPMN Future Work

There are two areas where future work can be applied to BPMN:–Case Management–Service Level modeling

Service Case


Service Level

Case Management

Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future

Collaboration Choreography and ConversationCollaboration, Choreography, and Conversation

Metamodel Changes

Case ManagementCase Management

Service Level Modeling

Conclusions



Collaboration, Choreography, and Conversation

No current plans for significant changes to these three diagrams

Need more vendor/customer experience and feedback


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future


Metamodel Changes



Conclusions



Potential Metamodel Changes

Separate Ad Hoc Processes for better Case Management support

Inherent Support for element substitution– Allows different levels of detail based on single model

f– Allows local variations of detail based on single model


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future


Metamodel Changes



Conclusions



Case Management

Case Management is a hot topic in BPM

Not all business have the same understanding of what Case Management is or how it works

–Sometimes a case involves mainly straight-through prescriptive Processes, with some trouble-shooting

–Sometimes a case involves mainly free-form descriptive Processes

A simple technical description: Case Management is a bridge between Content and Process

–This presentation focuses on the Process (behavior) aspect of CaseThis presentation focuses on the Process (behavior) aspect of Case Management


Case Management and BPMN

BPMN 2.0 has incomplete support for Case Management–BPMN mainly defines “Prescriptive” Processes – those Processes that

have a well-defined Sequence FlowB t BPMN d id f “D i ti ” P Th Ad H–But BPMN does provide for “Descriptive” Processes – The Ad Hoc Sub-Process

• Additional Descriptive Process types and behavior are required

The OMG is developing a Case Management Modeling Notation (CMMN) standard

–It is focused on a specification for tools that specialize in free-from C M t b h iCase Management behaviors


Some Descriptive Process Behaviors/Requirements

Milestones – e.g., a Case state lifecycle

New types of Events– E.g., the Case state (lifecycle) changes, document updates, etc

Pre-conditions, dependencies

Skipping, interrupting, resuming Activities

Addi A ti iti ( d h ) Adding Activities (ad hoc)


Other Factors

Changing the Process at runtime (E.g., adding new Tasks)–The line between design-time and run-time is blurred

• Pre-built library Activities can be added to an ongoing ProcessN l d fi d A ti iti b dd d t i P• Newly defined Activities can be added to an ongoing Process

–Run-time factors should be built into the notation

Additional Security constraints


Potential Case Management Notations

No Activity allowed Between

Case

Milestone


BPMN Ad Hoc Process

When BPMN 1.0 was first developed, there was an understanding that Descriptive Processes were an important part of the process landscape.

–However, the initial focus of BPMN was to create a business process d li l f b i l th t ld l b t d bmodeling language for business people that could also be executed by

the available BPMSs.

The Ad Hoc Process was included in BPMN as a placeholder that provides many of the capabilities required for modeling Descriptive Processes.

–It is expected as BPMN evolves, the Ad Hoc Process will evolve to h dl ll C M t P i thandle all Case Management Process requirements

–We can note that the Ad Hoc Sub-Process is probably a misnomer


Ad Hoc Process Example

There is no pre-defined Sequence Flow

Activities can occur in any order Write a Book Chapter

yor any frequency

Research the Topic Write Text

Edit Text

Generate Graphics Include

Graphics in Text

Organize References

Finalize Chapter


Issues

Are there Case Management Activities (behaviors) that do not apply to BPMN?

BPMN Case Management Notations have yet to be definedg y–Notation will be defined in the CMMN specification (OMG)


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future


Metamodel Changes



Conclusions




There are some BPM tools that provide modelers of executable BPMN models with additional modeling capabilities for modeling the execution details of Tasks

These details include the sequence of steps or user interface screens in a service (sometimes called screen flow)


What is Service Level Modeling?

The layout of these models looks very similar to standard BPMN Processes, but they are not, at this point, BPMN Processes

– They have different semantics and visualizations

S S ? Should they be treated as Sub-Processes?– Maybe a specialized type of Sub-Process?– A series of Sub-Tasks?


Service Level Model Example


Service Level Model Semantic Requirements

Some of the characteristics of service flow models include (for example):–No Lanes. They exist fully within the lane of their parent Task.–Only one Start Event. This Start Event does not have a trigger. Control

i l d f th t T kis always passed from the parent Task.–There are no parallel paths.–Gateways are allowed.

They can nest lower level Service Flow models–They can nest lower level Service Flow models


Issues/Questions

Are they Sub-Processes?–In a sense they are specialized Sub-Processes–But should they be depicted that way?

W ld it b di t ti t b i l ?–Would it be a distraction to business people?–They are more appropriate for IT modelers?

Semantics of the User Events in a Service Level–They don’t interrupt Activity in normal sense–They represent a normal completion of the Activity

• E.g., through clicking of a screen button

User Event notation: User (like a User Task) or a button icon–Can also be used for Case Management Processes


Agenda

Introduction

BPMN past

BPMN tBPMN present

BPMN future




Conclusions

BPMN has made an impact in the BPM market and with end user organizations

–More than 70 process modeling tools use BPMN

There is more work to be done–BPMN 2.0 is not the final version

Areas of potential BPMN work include: Areas of potential BPMN work include:–Collaboration, Choreography, and Conversation–Metamodel changes–Case Management behaviorCase Management behavior–Service Level behavior


Documents

BPMN: Past, Present, and Future - BPM 2012bpm2012.ut.ee/wp-content/uploads/2012/03/keynote-white.pdf · BPMN Design Guidelines: Complexity Business Process, by their nature, can include