From Diagrams to Production via Process Orchestration

A presentation at WebSummit in November 2024 in Lisbon, Portugal by Samantha Holstine

Slide 1

Slide 1

From Diagrams to Production via Process Orchestration Masterclass WebSummit 2024

Slide 2

Slide 2

Who’s this Guy? ■ Sr. Developer Advocate @Camunda ■ From: Jacksonville, FL Jacob Plicque @DuvalKingJacob He/Him ■ Fun Fact: Loves Video Games, Huge Nerd, Tabletop RPG Fan (like Dungeons and Dragons) has a Dice Collection in the Thousands

Slide 3

Slide 3

Who am I? ■ Developer Advocate @ Camunda ■ Denver, CO, United States Samantha Holstine @sholstine620 she/her ■ Fun fact: I’m a dance fitness and studio rowing instructor in my free time

Slide 4

Slide 4

Agenda ■ Developers and Architects: a world apart? ■ How can Architects and Developers work together? ■ What is Process Orchestration? ■ How Process Orchestration fills the gaps between both roles

Slide 5

Slide 5

Slide 6

Slide 6

Developer

Slide 7

Slide 7

Example: Claim handling

Slide 8

Slide 8

Scenario 🗣 C Suite 😎 Architect 󰠁 Developer

Slide 9

Slide 9

What the world looks like today… Money Claim notification letter ERP Policy Management System Mainframe Customer Interaction System

Slide 10

Slide 10

10

Slide 11

Slide 11

“Spaghetti” architecture Grown over time Brittle of Lack ility b visi into o-end t end- sses e proc → Hard to innovate and transform

Slide 12

Slide 12

…but, you need to innovate and transform Pressure to innovate quickly Pressure to transform and future-proof

Slide 13

Slide 13

“Quick wins” become technical debt Reflex is to implement point solutions and local automations… Point solutions

Automations AI And now, also “Point Agents” AI More silos + technical debt!

Slide 14

Slide 14

Change is scary.

Slide 15

Slide 15

So what’s this Process Orchestration?

Slide 16

Slide 16

“ Process orchestration coordinates the various moving parts (or endpoints) of a business process, and even ties multiple processes together. Process orchestration helps you work with the people, systems, and devices you already have – while achieving even the most ambitious goals around end-to-end process automation. 16

Slide 17

Slide 17

Process Orchestration Task Automation Process Automation Automation Digitalization Digital Transformation Cloud Transformation

Slide 18

Slide 18

Task Automation Process Orchestration

Slide 19

Slide 19

Bus s P o s M e l Introducing BPMNan N ti Maintained spec Visualization Bridge communication ISO/IEC 19510 spec maintained by OMG (Object Management Group) Easily understand complex processes; no more spaghetti! Simplify discussions with stakeholders; unify design and implementation

Slide 20

Slide 20

Orchestration engine Durable state V1 Version 1 Version 2 Process definitions Scheduler

Slide 21

Slide 21

PO isn’t automatically entire process = Automated Engine executes an executable process model Orchestration! Engine communicates with IT Systems Engine decides with tasks/service calls Processes can be long-running and that’s ok!

Slide 22

Slide 22

From hard-wired to orchestrated… PROCESS ORCHESTRATION TASK AUTOMATION The “process” EXTERNALIZE THE PROCESS ERP CRM Mainframe Hard-wired spaghetti process ERP CRM Mainframe Orchestrated processes

Slide 23

Slide 23

The Power of Process Orchestration Visualize what’s actually happening What’s designed is exactly what is implemented and executed Business/IT speaking the same language Align business and IT using a common, standards-based model and language. Tame Complexity Via end to end orchestration across your Customer Journey Drive Home Business Outcomes Much easier to tie Biz/IT Value Conversation together

Slide 24

Slide 24

Ok that’s one E2E Process, where do we go now?

Slide 25

Slide 25

Strategic Process Orchestration (Optional) Validate Business Case with Process Tracking 1⃣ Locate E2E Process 2⃣ Define customer touch points 3⃣ Define Process Goals / Process KPIs 4⃣ Orchestrate Process and Continuously Improve 25

Slide 26

Slide 26

Claims example E-Mail Policy Domain Payment Domain Powered by Camunda as Orchestration layer Claims Domain DMN (Decision Engine) Customer Domain Legal Domain Docs Domain

Slide 27

Slide 27

So, how can I use this to drive value?

Slide 28

Slide 28

CTO CIO CFO (S)VPs Strategy focus (S)VPs Directors COO LoB leaders Directors Enterprise architects Product owners Operational focus Solution architects Business analysts Software engineers Subject matter experts Operations managers End users / clerks IT Business 28

Slide 29

Slide 29

Build strategic value at enterprise scale using process orchestration Strategic view / senior leadership Operational view / business domains Technical view / solution teams

Slide 30

Slide 30

Build strategic value at enterprise scale using process orchestration Strategic view / senior leadership Level 1 Business area ■ ■ Operational view / business domains Level 2 Customer journeys (outside-in view) Value streams (inside-out view) Level 3 Strategic end-to-end processes implements Vehicle insurance: Claims Vehicle accident Vehicle claim handling Claim handling implements uses Level 4 Business capabilities Executable BPMN might implement some business capabilities Technical view / solution teams Claim management Disbursement Claim approval uses implements Level 5 Integration capabilities Reusable connectors, executable BPMN used for technical integration flows Document extraction (relaying to AI)

Slide 31

Slide 31

Build strategic value at enterprise scale using process orchestration Foundation to innovate and to transform

Slide 32

Slide 32

Using process orchestration, build strategic value at enterprise scale Provide centrally to the organization ■ Platform & Accelerators ■ Enablement function

Slide 33

Slide 33

Adding a Process Orchestration platform as a technical capability will enable efficient solution creation Customer Omnichannel integration API End-to-end process orchestration (e.g. account opening) End-to-End Process API API Fraud Check Payment KYC Business capabilities (implemented via legacy systems, COTS, microservices, etc.) … As a Service Process Orchestration Logging and Monitoring Data Storage, DBs and MDM (Metadata) Event Streaming … Technical capabilities (enabling efficient solution creation)

Slide 34

Slide 34

Slide 35

Slide 35

Planning

Slide 36

Slide 36

Analysis

Slide 37

Slide 37

Design

Slide 38

Slide 38

Implementation

Slide 39

Slide 39

Testing

Slide 40

Slide 40

Maintenance

Slide 41

Slide 41

Claims Example REST Call Human Work via modern JS UI E-Mail gRPC API Powered by Camunda as Orchestration layer Claims Domain DMN (Decision Engine) Job-Worker Message Queue SOAP Call Home grown legacy Tasklist Camunda 8 out of the box connector

Slide 42

Slide 42

Enterprise Process Orchestration Platform

Slide 43

Slide 43

A centralized platform improves time to value for projects while maintaining agility Business capability Owned by solution team Led by the business domain Supported and enabled by CoE Delivery scope Process solution BPMN Solution team owns process model and glue code Deployed onto platform that is provided as a service Provided by CoE (aaS) Owned by solution team Process orchestration platform installation Technical capability State managed by the platform, isolated by tenants or cluster Platform state is owned by the solution team (runtime version, contained data, platform configuration, access control) Provisioned and managed as a service Enterprise scope (CoE) Owned by CoE Process orchestration platform provisioner Provisioning and management of process orchestration platforms

Slide 44

Slide 44

Typical project lifecycle Iterative development Discover Model Develop Continuous development Run Monitor → Define use case → Capture business objectives and define success metrics → Understand system landscape & process complexity → Define business case → Define technical approach → Define ownership and roles → Model as-is and to-be processes → Define concrete KPIs → Understand the E2E process but define iterations → Define the journey (tracking, human orchestration, step-by-step automation, …) → Link business and technical model → Detail the model with technical attributes → Set up solution project according to solution architecture → Write glue code → Use (and potentially build) connectors → Write tests → Operate solution in production → Implement change management → Continuously measure KPIs → Analyze problems and propose improvements → Report achieved value internally & externally Department leaders Process/product owners Subject matter experts Enterprise architects → Business/process analysts → Developers → Enterprise/IT architects → SMEs → Process/product owners → Developers → Enterprise/IT architects → Low-code developers → DevOps → Operations → Clerks → Process/product owners → Business analysts WHO → → → → TOOLS → → → → Whiteboard Miro Slides … → BPMN and collaborative tooling → Process orchestration platform → BPMN modeler → Integrated development environment (IDE) → Process orchestration platform (especially operations tooling) → Process orchestration platform (especially process intelligence tooling), BI tooling WHAT

Slide 45

Slide 45

Claims Example 😎 Architect 󰠁 Developer 🗣 C Suite

Slide 46

Slide 46

Slide 47

Slide 47

Enterprise Adoption Phases Business Value Successful adoption path’s deliver incremental business value and gradually increase process orchestration maturity to onboard more and more teams to the platform in a scalable operating model. Establish ■ Define goals, expected value, scope, and roadmap of your program ■ Sketch out adoption architecture (incl. CoE setup) ■ Set up platform ■ Deliver lighthouse project ■ Communicate achieved value Launch ■ Establish structured use case discovery process ■ Federate delivery and roll out use cases in multiple domains ■ Develop CoE ■ Mature platform (accelerators and reusable components) ■ Communicate value and share knowledge Process Orchestration Maturity Scale ■ Onboard further delivery teams ■ Pull+push principle for new use cases ■ Support additional use case categories ■ Enable further personas ■ Systematically track business value

Slide 48

Slide 48

Typical high-level adoption Roadmap Discover Q1 Vision & Motivation Deliver Q3 Q2 Scale Q4 Q1 Q2 Q3 Q1 Q4 Q2 Q3 Q4 Strategy Alignment Develop roadmap Structure Define operating model and team structure Build Center of Excellence Delivery Focus Enablement Focus Technology Setup Camunda as integrated platform Operations and Continuous Improvement Setup Refinement Design architecture and governance Build accelerators Solution Delivery Domain A Use Case 1 Use Case 2 Use Case 3 Domain B Use Case 1 Use Case 2 Discovery MVP Live MVP Discovery MVP Discovery Discovery Prod Live MVP Live Live Discovery MVP Discovery Prod Prod Prod Live MVP Prod Live Prod Measurement Continuous Value Tracking & Reporting 48

Slide 49

Slide 49

Let’s review 1 Visualize and Implement the Truth in Every Environment Not just Whiteboarding anymore 2 Business/IT on the same Page 3 Top Level Strategic Diagram first! Speaking the same language via BPMN and Process Orchestration Then model the business process, then dive deeper as long as you still have a business outcome in mind

Slide 50

Slide 50

Let’s review 1 Orchestration Hour and BPMN Battles! 2 Camunda Academy 3 Community Forum! Twitch.tv/orchestrationhour and https://www.youtube.com/@CamundaTeam Certification Program too! Join the convo with Biz folks, Devs, and Enterprise Architects!

Slide 51

Slide 51

Thank You samantha.holstine@camunda.com jacob.plicque@camunda.com https://www.linkedin.com/in/samantha-holstine-77598916b/ https://www.linkedin.com/in/fanaticgamer1986/ @SamanthaHolstine on GitHub @DuvalKingJacob on all the Socials