organizing the business process management …a business process consists of a set of activities...
TRANSCRIPT
Organizing the Business Process ManagementSpace
Mathias Weske
EMISA'2007 Keynote | Mathias Weske
2
People
Real-World Example
■ FP6 IP on Service composition platform
■ Detailed project plan
■ Sub projects dealing with
□ Architecture
□ Case Studies
□ Processes
□ Semantics
□ Methodologies
EMISA'2007 Keynote | Mathias Weske
3
Sub Project Presentation 1
EMISA'2007 Keynote | Mathias Weske
4
Sub Project Presentation 2
EMISA'2007 Keynote | Mathias Weske
5
Sub Project Presentation 3
EMISA'2007 Keynote | Mathias Weske
6
Observations
■ People tend to centralize own experiences and goals
■ Especially prominent in domains
□ with complex structures
□ broad coverage
□ where disciplines meet
■ … like Business Process Management !
□ Several communities are involved, with different backgrounds and experiences
□ Complex and diverse issued need to be solved, fromorganizational to technological
EMISA'2007 Keynote | Mathias Weske
7
Characterizing BPM
■ Background and Motivation
□ Products are provided through activities a company performs
□ Cost effective and rapid improvement of products is a competitive advantage
□ Information Systems play an increasingly important role in fulfilling these activities
■ Sample Business Processes
□ Ordering Processes, e.g., in online shops
□ Claim handling of insurance companies
□ Request for quotation process
EMISA'2007 Keynote | Mathias Weske
8
Business Process
■ A business process consists of a set of activities that are
□ performed in coordination
□ in an organizational and technical environment.
■ These activities jointly realize a business goal.
■ Each business process is enacted by a single organization, but it may interact with business processes performed by other organizations.
Res
elle
r
EMISA'2007 Keynote | Mathias Weske
9
EMISA'2007 Keynote | Mathias Weske
10
People Challenge
■ The BPM community consists actually of a set of relatedcommunities, characterized by different
□ Terminology
□ Goals
□ Educational background
■ Common understanding between these communities isimportant
EMISA'2007 Keynote | Mathias Weske
11
Strategy and Goals
■ Enterprise level businessstrategy
■ Goals to realize thestrategy
□ Broken down to subgoals, etc.
□ Realize what needs to be realized, not how
EMISA'2007 Keynote | Mathias Weske
12
Organizational Business Processes
■ Coarse granularity
■ Described textually
■ Input and output behaviour
■ Responsibilities
■ Organized in Process Landscape
EMISA'2007 Keynote | Mathias Weske
13
Process Landscape
EMISA'2007 Keynote | Mathias Weske
14
Organizational Business Process
Customer Processes:
Order Management Process, After-Sales Service Process
Process Results:
Integrated and completely tested innovative product with complete documentation
Supplier Processes:Product Planning Process,Innovation Process
Process Inputs: Requirements Document,Project Plan, Budget Plan,Prototypes
Type: Development ProjectFrom: Requirements To: Rollout
Responsible Process Manager: Dr. Myers
Process Name: Product Development Process
EMISA'2007 Keynote | Mathias Weske
15
Operational Business Processes
■ Activities and execution constraints between them
■ No information on technicaland organizationalexecution environment
■ Described using graphicalnotations, often semi-formal ones
EMISA'2007 Keynote | Mathias Weske
16
Operational Business Process
■ Different approaches are available to realize thisprocess, ranging from manual to automatedinvolving software systems
EMISA'2007 Keynote | Mathias Weske
17
From Functions to Processes
EMISA'2007 Keynote | Mathias Weske
18
Process Meta ModelProcess Model
Node Edge
Event Model
Activity Model
Gateway Model
Process Instance
Node Instance
1
*
1*
1*
2 1..*
1
1..*
1
2..*
Event
Activity Instance
Gateway Instance
1*
1*
1*
EMISA'2007 Keynote | Mathias Weske
19
Sample Process Model
AnalyzeOrder
SimpleCheck
AdvCheck
N1 N2 N3
N4
N5
N6N7
Initial event model
Final event model
EMISA'2007 Keynote | Mathias Weske
20
Execution Semantics
■ Activity instances behavior described by state transitiondiagram
■ State transitions represented by events
EMISA'2007 Keynote | Mathias Weske
21
Events and States
EMISA'2007 Keynote | Mathias Weske
22
Process Instances
e1
Initialization of activity instances and gateway instances
i2 i3 i4 i6 e2 b2 t2 b3 t3 s5 e4 b4 t4 b6 t6 n7
Occurrence of start event
AnalyzeOrder SimpleCheck Occurrence of end event
Skipping AdvCheck(n5)
DecisionGateway
n1
EMISA'2007 Keynote | Mathias Weske
23
Implemented Business Processes
■ Contain information on thetechnical and organizational execution environment
□ Realization in silicoby workflow or servicecomposition technology
□ Realization in vivoby policies and procedures
EMISA'2007 Keynote | Mathias Weske
24
Implementing Activities
EMISA'2007 Keynote | Mathias Weske
25
System Workflows
■ Characterization
□ Process activities realized entirely by softwarefunctionality
□ No user interactions in system workflows
□ System workflows solve the EAI integration problem, at least process integration
□ Explicit process representation provides betterunderstanding of the process integration logic
□ Higher flexibility, since changes to the process modelare immediately used by the process engine
■ Remark
□ Adapters that hide data heterogeneity are required
EMISA'2007 Keynote | Mathias Weske
26
System Workflow
EMISA'2007 Keynote | Mathias Weske
27
Human Interaction Workflows
■ Characterization
□ User interactions during process enactment
□ System activities also present
□ Organizational information required for assigningknowledge workers to process activities
□ Specific graphical user interfaces for process participantsrequired (work lists)
□ Integration of applications with specific user interfaces
EMISA'2007 Keynote | Mathias Weske
28
Human Interaction Workflow
EMISA'2007 Keynote | Mathias Weske
29
Conceptual Model
Business Process
Workflow
Human Interaction WorkflowSystem Workflow
System Activity
Activity
User Interaction Activity Manual Activity
EMISA'2007 Keynote | Mathias Weske
30
Process Choreographies
■ Enterprises collaborate to achieve their business goals
■ Value chains are high level organization of B2B ormultiparty collaborations
■ These collaborations also need to be embedded in theoverall picture
EMISA'2007 Keynote | Mathias Weske
31
■ The term choreography indicates the absence of a central agent that controls the activities in the business processes involved. The interaction is only achieved by sending and receiving messages.
■ This situation is similar to dancers who need to agree on a common choreography before the show starts. During the performance, however, each dancer behaves autonomously but in line with his or her part in the choreography.
Process Choreographies
EMISA'2007 Keynote | Mathias Weske
32
Buy
erR
esel
ler
Sample Process Choreography
EMISA'2007 Keynote | Mathias Weske
33
Formal aspects in process choreographies
■ Agree on global interactions
■ Create behavioral interfaces for the partners
■ Use these as starting point for process implementations
EMISA'2007 Keynote | Mathias Weske
34
Scenario – Behavioral InterfacesBuyerAuctioning ServiceSupplier
!participation_req ?participation_req
!rec_reject!rec_accept
pr
a
r
pr
?reject?accept !accept!reject
?rec_accept?rec_rejectrr
ra
br
ba
!reject!accepta
r?accept?reject
ba
br
ra
rr
!notify ?notifyn n
EMISA'2007 Keynote | Mathias Weske
35
ImplementationAlternatives
EMISA'2007 Keynote | Mathias Weske
36
ERP System SCM System
Enterprise Application Integration
CRM System
Buy
er Place Order
Receive Invoice
Receive Products
Settle Invoice
Service Layer
EAI Adapter
Data
Enterprise Applications
Enterprise Application Integration
Service Interfaces
System Workflows / Composite
Applications
Human Interaction Workflows
Business-to-Business
Processes
Overall Picture
EMISA'2007 Keynote | Mathias Weske
37
Conclusions
■ BPM area is broad, complex and different communitiesare involved
■ Common understanding is required for fruitfulcollaboration
■ Formal analysis requires abstraction from domainconcepts – but it is useful to design processes
■ Software plays an important role to provide flexible enactment environments
■ Adequate tooling can contribute to development of thefield
EMISA'2007 Keynote | Mathias Weske
38
Textbook on BPM, bpm-book.com
1. Introduction
2. Evolution of Enterprise Systems Architectures
3. Business Process ModellingFoundation
4. Process Orchestrations
5. Process Choreographies
6. Properties of Business Processes
7. BPM Architectures
8. Business Process Methodology
EMISA'2007 Keynote | Mathias Weske
39