Enabling BPM Through Technology

Copyright Kemsley Design Ltd., 2007

Enabling BPM Through Technology

Sandy Kemsley

Kemsley Design Ltd.

[email protected]

www.column2.com


Agenda

The evolution of BPM BPM and SOA: together, but different Emerging BPM standards The impact of Web 2.0 on BPM The future of BPM


The Evolution of BPM


BPM: In the beginning

Integration of two main functionalities:Human-facing workflowEnterprise application integration

(system-to-system) Custom coding for integration Rudimentary modeling and

management tools


BPM Suite

"Integration-focused" BPM"Pure-play" BPM

Workflow(person-to-person)

EAI(system-to-system)

Business activitymonitoring

Process governanceProcess simulation

B2Bi

extend

extendlight-weight EAI

(OEM)rudimentary

workflow (build)

Business rulesProcess modelling

extend exte

ndAdministrative BPM Collaborative BPM Embedded BPM


BPM Market Fragmentation

Fragmented by vendor speciality:Integration-focusedHuman-centricRules-based

Fragmented by application:Collaborative/ad hocCase managementProduction workflow


BPM now

Essential infrastructure for process-oriented organizations

Many new tools as part of the package: Process modeling Business rules Monitoring and analytics Simulation and optimization Web services integration

Copyright Kemsley Design Ltd., 2007Source: Gartner BPMS Magic Quadrant 2006


BPM and SOA


BPM and SOA defined

BPM:Management practiceTools for automating processes

SOA:Architectural philosophyDesign standards-based services to

access system functionality


BPM and SOA

Service A Service B Service C

Service D Service E

LegacySystem

DatabaseERP

System

ProcessStep 1

ProcessStep 2

ProcessStep 3

ProcessStep 4



BPM and SOA together

BPM is the “killer app” for SOA; SOA is the enabling infrastructure for BPMSOA alone only allows you to design

and build a set of servicesBPM alone would require custom

coding for each system integration BPM + SOA orchestrates people and

services into a business process


BPM Standards


BPM notation standards

Shared vision andcommunication between stakeholders

Easy transition between tools for users

BPMN (Business Process Modeling Notation)


BPM interchange standards

Import/export of process models Evolving landscape of standards:

XPDL (XML Process Definition Language)

BPEL (Business Process Execution Language)

BPDM (Business Process Definition Metamodel)


The Impact of Web 2.0 on BPM


What is Web 2.0?

Web as platform Harnessing collective intelligence Data as the next “Intel Inside” End of the software release cycle Lightweight programming models Software above the level of a single

device Rich user experience


Key Web 2.0 characteristics

Tagging/folksonomies User-created content and collaboration Network effect Zero-footprint rich user interface (AJAX) Content syndication Software as a service Web mashups


Why do we care aboutWeb 2.0? It changes how people participate

User-generated content Collaboration Tagging/bookmarking RSS feeds and content syndication Mashups

It increases user expectations Better user experience Shorter development time

It turns IT into a commodity


Enterprise 2.0

Web 2.0 software/techniques in enterprise context, behind and across the firewall

What’s being used: Wikis Blogs Social bookmarking Content syndication AJAX


How Web 2.0 Will Impact BPM: User View Process tagging/folksonomies User-created processes/mashups Process collaboration (including external):

Modelling Design Execution Management

Rich user interfaces




How Web 2.0 Will Impact BPM: IT View

Process syndication for management and visibility

Software as a service Lightweight integration models Interoperable processes


Issues with Web 2.0 and BPM

Corporate cultureDecentralized content administrationContent policingConstantly changing softwareUser participation levelsInter-departmental information sharing

Support and SLAs


The Future of BPM


What’s Next?

Improvements to BPMSSoftware as a service with SLACollaborative process modelingProcess instance taggingRSS feeds of processes

(instances/queues) to portalsBrowser-based process design and

managementProcess data available for mashing up


What’s Next?

Changes to implementation and cultureAllow users direct access to BPMS

toolsReduce over-customisationEncourage tagging and collaboration


Questions?

Sandy Kemsley

Kemsley Design Ltd.

[email protected]

www.column2.com

Enabling BPM Through Technology

Technology

evolution of bpm bpm

bpm soa

impact bpm

future of bpm

system integration bpm

soa defined bpm

bpm notation standards

bpm workflow person