2. Welcome!
Jakob Freund is CEO of camunda, author of the bestselling book
'Real-Life BPMN' and a regular speaker at BPM conferences. His
passion is the big picture of scaling up business models by well-
defined and automated business processes, using BPMN as the
common language for Business and IT.
5. Some references outside D.A.CH.
Financial
Industry
Regulatory
Authority
USA
Sony DADC
New Media
Solutions
USA
National
Centre for
Vocational
Education
Research
Australia
Allianz
Indonesia
Insurances
Indonesia
6. BPMN with camunda BPM
Analyst / Developer User Operator
Modeler Tasklist / Your UI Cockpit
Engine
camunda BPM platform
7. Camunda BPM Community Day
Robert Parker, Australia Post: Order management using camunda BPM
This presentation will describe our order management architecture and in particular
order fulfilment processes using Camunda BPM technology. A number of business
requirements leading to design challenges will be presented, along with the benefit of
using BPM to realise solutions and the corresponding business benefits. In addition,
some key technical challenges, solution options, and resulting solution design
decisions and implications will be presented.
Also:
• Camunda @ 1&1 Internet
• Grails
• OSGi
• Elastic Search
• Advanced Mocking
• Upcoming Features
Thursday, September 18 | Berlin
http://network.camunda.org/meetings/32
9. „Executable BPMN process models…
Are always complex and detailed.“
Are a refinement of business driven process models.“
Should be created and maintained by IT alone.“
Three common mistakes
15. Retrieve the user that should be assigned to a user task based on
complex business logic
Notify that user by email about the pending task
Track KPI in external System after the usertask has been completed.
Track KPI after the issue has been reviewed
I want to:
see: BPMN 2.0 by Example, OMG
17. 100% Model-driven approach (Anti-Pattern)
Retrieve the user that
should be assigned to a
user task based on
complex business logic
Notify that user by
email about the pending
task
Track KPI in
external System
after the usertask
has been
completed
Track KPI after the
issue has been
reviewed
21. The Listener in Detail
1. Retrieve Assignee‘s Email
2. Create Email with Deep Link
3. Send Email
22. Keeping the diagram easy-to-read
• Retrieve the user that should be
assigned to a user task based on
complex business logic
• Notify that user by email about the
pending task
Track KPI in external
System after the usertask
has been completed
Track KPI after the
issue has been
reviewed
23. Activities that are (really) relevant for the business side
Activities I want to monitor explicitly
Activities where I can benefit from the process engine‘s capabilities
Requirements that just need to be implemented
In BPMN: As much as necessary, as little as possible
24. „Executable BPMN process models…
Are always complex and detailed.“
Are a refinement of business driven process models.“
Should be created and maintained by IT alone.“
Three common mistakes
25. The big Mistake
Level 3 („executable process model“)
is a refinement of Level 2
(„Operational Process Model“)!
27. The new „camunda-house“
Strategic
Process Model
Operational Process Model
human
process flow
technical
process flow
• Manual Control Flow
• Work Description
• User Experience
• Interaction Flow
• Collaboration between User
and System
• quick overview
• logically-abstract
• Precise
description
• Physically-
concrete
• Automated control
flow
• Code
31. „Executable BPMN process models…
Are always complex and detailed.“
Are a refinement of business driven process models.“
Should be created and maintained by IT alone.“
Three common mistakes
32. Executable Process Model = Technical (Process) Flow
Strategic
Process Model
Operational Process Model
human
process flow
technical
process flow
35. The technical flow must be developed in a collaboration
User
Analyst
Developer
Problems,
Needs,
Priorities...
Feasibiltiy,
Efforts, ...
Ideas,
Roadmaps,
Costs...
To-Be Processes,
Requirements, ...
Strategic
Process Model
Operational Process Model
human
process flow
technical
process flow
36. How to discover a „good“ process analyst?
Hard Skills
• BPMN
• Technical Understanding
(How dows a process
engine work?)
• Business Domain
Understanding
Soft Skills
• Readiness of mind
• ability to communicate
• Analytical Mind
• Empathy
37. Typical PoC-Workshop (5 days)
Process
Design
Process
Execution
Live
Demo
Design: 2 Days
• To-Be-Process Design
• Business Departments, IT-Architects,
Software Developers
Conclusion: 0.5 Days
• Prototype Live Demo
• Lessons Learned
• All Stakeholders
• Developing a Process Application Prototype
• IT Architects, Software Developers
Implementation: 2.5 Days
38. „Executable BPMN process models…
Are always complex and detailed.“
Are a refinement of business driven process models.“
Should be created and maintained by IT alone.“
Three common mistakes
43. Transpareny: We get an understanding of how we work – sth. That used to be
buried in legacy applications.
Up-To-Date-Documentation: When we just document our processes, it‘s hard
to keep them up to date. Now the docs are necessarily up to date, because
they represent what‘s actually running.
Shorter Development Cycles: The camunda-approach is very good fit for
modern paradigms such as agile collaboration. There is a way better
communication between business and IT that dramatically increases
development cycles.
Reduced Programming Efforts: BPMN is a very powerful language for process
execution, and a BPMN process engine therefore brings a good number of
features that we would otherwise need to code ourselves (Examples: Wait
States)
What you see is what you run: For the first time we now really say what‘s
currently happening, because we get a real-time view on our source code the
moment it‘s being executed!
What customers say about BPMN / camunda BPM
44. Typical PoC-Workshop (5 days)
Process
Design
Process
Execution
Live
Demo
Design: 2 Days
• To-Be-Process Design
• Business Departments, IT-Architects,
Software Developers
Conclusion: 0.5 Days
• Prototype Live Demo
• Lessons Learned
• All Stakeholders
• Developing a Process Application Prototype
• IT Architects, Software Developers
Implementation: 2.5 Days
