BPMN:
The open standard for process and agentic orchestration
Twenty years ago, BPMN solved the translation problem between business and engineering. Today, as AI agents enter mission-critical operations, it’s the foundation that keeps them safe and accountable: one diagram, one audit trail, one model that business can read and orchestration engines can run.
What is BPMN?
Business teams document processes in slides. Engineers build them in code. Within months the two drift apart, and no one is certain which version is real. BPMN was designed to close that gap permanently.
BPMN (Business Process Model and Notation) is the ISO-ratified open standard for modeling and executing business processes (ISO/IEC 19510:2013), maintained by the Object Management Group (OMG). A BPMN diagram is simultaneously a visual that any stakeholder can read and an XML specification that an orchestration engine can run. The process the business approves is exactly what happens in production.
That dual nature (human-readable and machine-executable) is what makes BPMN uniquely suited to the AI era. Generative tools can produce a process model from a natural language description. Agents can read the diagram to understand their own context. Every step, whether run by code, an agent, or a person, lands in the same audit trail. One notation, from design to compliance.
- What is BPMN?
- Why BPMN matters more in the age of AI
- One source of truth from design to production
- The business case for BPMN
- The basic elements of BPMN
- BPMN and AI agents
- What users say about BPMN
- BPMN vs. proprietary alternatives
- Camunda’s BPMN expertise: 15+ years at the OMG
- Frequently asked questions
- Books, training, and references
- Get started with BPMN
Why BPMN matters more in the age of AI
Most enterprises now have AI agents in pilot. Very few have AI agents in production at scale. The difference is not the model; it’s the orchestration layer underneath. BPMN is what closes that gap.
A shared language for business and IT
When operations and engineering work from the same diagram, change requests don’t get lost in translation. BPMN was designed for this exact handoff and is the only modeling language with two decades of refinement behind it.
Deterministic guardrails for non-deterministic agents
Agents reason. Processes are accountable. BPMN lets you wrap agent reasoning in must-follow operating procedures (approvals, thresholds, escalations) that execute every time, no matter what the agent decides.
Built-in auditability
Every step of a BPMN process is captured automatically. When a regulator asks why something happened, or when an agent behaves unexpectedly, you have the full trace. No extra instrumentation, no reconstruction from logs.
Portability so your processes outlive your tools
Models, frameworks, and AI vendors will change. With BPMN as your process layer, your end-to-end logic doesn't need to be rebuilt every time the technology underneath shifts. Your processes survive the transitions.
Coverage of the full automation spectrum
Straight-through processing for predictable steps. Agent reasoning for exceptions. Human work for judgment calls. BPMN expresses all three in a single coherent model, so you don’t end up with parallel “AI processes” that drift.
A 20-year ecosystem you can hire from
More than 100 BPMN tools exist. Universities teach it. Consulting partners specialize in it. BPMN talent is widely available, not locked behind one vendor’s certification track.
The business case for BPMN
BPMN is technical. Its value isn't. Operations leaders who have introduced BPMN-based orchestration consistently see four outcomes that show up directly on a business case.
Faster change without breaking what works
Visual processes can be reviewed, adjusted, and redeployed without rewriting code in three different systems. Operations teams stop waiting on engineering for every business rule change. IT stops being the bottleneck.
Lower cost per case
When the same model that designs a process also runs it and reports on it, you stop paying for redundant tools and the consultants who reconcile them. End-to-end orchestration consolidates the stack.
Audit-ready by default
Regulators ask why something happened. With BPMN, the answer is the diagram plus the execution log. There is no separate "compliance documentation" project. Every run is its own evidence trail.
Continuous optimization, not one-time deployments
Every process execution generates performance data that surfaces bottlenecks, SLA gaps, and where automation delivers the most value. You improve every quarter, without stopping operations to make changes.
One source of truth from design to production
Most modeling languages are documentation that someone has to translate into code. BPMN is different: a single BPMN file is both a visual diagram and an XML specification. The picture you discuss with the business is the executable artifact your engine runs.
That single source of truth removes the most expensive failure mode in process automation: drift between what the business thinks is happening and what the system actually does. With BPMN on Camunda, what you design is what runs, what runs is what's monitored, and what's monitored is what gets optimized.
It also means BPMN is uniquely suited to AI. Generative tools can draft executable processes from natural language, agents can read the model to understand context, and humans can see exactly what the agent is participating in — all without leaving the diagram.
The basic elements of BPMN
BPMN's notation is intentionally compact. A handful of element families covers everything from a five-step approval to a multi-week claims process spanning thirty systems. Once you recognize these shapes, you can read most BPMN diagrams without training.
Events
Things that happen: a process starts, a message arrives, a timer fires, an error is thrown.
Tasks
Units of work: service tasks call APIs, user tasks ask people, business rule tasks invoke a decision.
Gateways
Decisions and parallelism: split, merge, or wait. Exclusive, parallel, inclusive, and event-based.
Sequence flows
Arrows showing the order of steps. Conditional flows route work based on data.
Pools and lanes
Who does what: separate participants (customer, system, agent) into their own swim lanes.
Subprocesses
Reusable, expandable groups of steps. Includes ad-hoc subprocesses, the foundation of in-platform AI agents.
Boundary events
Exception handling attached to a step (timeouts, errors, escalations). The way real-world processes recover.
Message flows
Communication between participants in different pools, across systems, organizations, or agents.
BPMN and AI agents: Orchestrating reasoning with rules
Agents introduce a new kind of step: one that decides what to do based on context. BPMN provides the surrounding structure that makes those decisions safe, both from outside the agent and from inside it.
Agents as participants in a larger process
A BPMN process treats an agent like any other participant: a service, a person, a system. The agent gets called when it’s needed, returns its result, and the process decides what comes next. Sequencing, escalations, retries, and human handoffs are governed by the model, not the agent.
Enforceable steps between reasoning and action
For agents built natively in Camunda using BPMN ad-hoc subprocesses, must-follow operating procedures sit between the agent's reasoning (the LLM) and its action (the tool call). When the agent decides to send an email or issue a refund, a BPMN fragment can force a policy check, an approval, or a fraud screen first. This approach is covered by a US patent pending.
What users say about BPMN
From banks to retailers to public-sector agencies, the same themes come up: alignment between business and IT, processes that match reality, and the speed that comes with a shared visual language.
“Thanks to the introduction of Camunda, the professionally documented process now 100% corresponds to the technical reality. Most questions regarding the process can be instantly answered by a quick look at the BPMN diagram.”
Zalando · Read the case study →
“Our business process owners joined us for the BPMN training and enjoyed it so much that they all stayed on to complete the developer training. We’ve also established a BPMN tribe.”
Helsana · Read the case study →
“Thanks to BPMN, we were able to develop and map our processes in interdisciplinary workshops, involving both subject matter experts as well as software engineers. The visual process language has helped us simplify communication between developers and domain experts.”
Bank11 · Read the case study →
“Camunda has enabled Deutsche Telekom IT to visualize complex logic in one place, easily align human and automated tasks, and use the same language for business and development with BPMN.”
Deutsche Telekom · Read the case study →
BPMN versus proprietary alternatives
Some vendors prefer their own modeling language, usually because it locks customers in. Here’s how BPMN compares to the alternatives most enterprises encounter.
| BPMN | Proprietary low-code suites | Code-only orchestrators | |
|---|---|---|---|
| Open standard | Yes. ISO/IEC 19510, OMG-maintained | No. Vendor-owned notation | No. Code constructs only |
| Readable by business teams | Yes. Designed for business and IT collaboration | Sometimes. Limited to vendor’s UI conventions | No. Process logic lives in code and JSON |
| Tool and talent portability | 100+ tools support BPMN; talent widely available | Locked to vendor; certifications don’t transfer | Locked to engine-specific SDK |
| Native human task support | First-class via user task element | First-class within the suite | No. Must be built from scratch |
| Coverage of advanced patterns | Compensation, parallel branches, escalation, ad-hoc. All native. | Limited; requires custom code at the edges | Available but engineer-only |
| Agent governance from outside and inside | Yes, via BPMN and ad-hoc subprocess (Camunda) | Outside-only; brittle when agents act | Outside-only; no business-readable model |
| Audit trail without extra instrumentation | Yes. Every step recorded automatically | Within the suite; brittle across systems | Logs only; no end-to-end process view |
Camunda’s BPMN expertise: 15+ years at the OMG
Most vendors adopt BPMN. Camunda helps shape it. Our founders co-authored the most widely read book on BPMN, our team participates in the OMG working groups that maintain the standard, and our platform implements the deepest BPMN coverage of any orchestration engine on the market.
An open standard, championed by an independent company
BPMN is owned by no single vendor. That’s the point, and that’s why Camunda has invested so deeply in the standard rather than building a proprietary alternative. Open standards protect customers from lock-in, expand the talent pool, and give the ecosystem a shared foundation that survives any one company’s product decisions.
Camunda has been an active contributor to the OMG’s BPMN and DMN working groups for over 15 years. Our engineers have helped refine the specifications, expand coverage of advanced patterns, and most recently extend BPMN’s expressiveness to the new world of AI agents through ad-hoc subprocess patterns now used by enterprises in production.
What our BPMN authority means for you
The deepest BPMN coverage on the market
Camunda implements the BPMN elements most other engines skip: compensation, dynamic parallel execution, message correlation, time-based escalation, and ad-hoc subprocesses for agents. All native, no workarounds.
BPMN coverage docs →Standards leadership in the agentic era
As AI agents enter business processes, Camunda is leading the work to extend BPMN to govern them, both from the outside (as participants) and from the inside (as enforceable steps within agent reasoning).
How Camunda orchestrates agents →A community you can hire from
Camunda Academy, the OMG-certified OCEB program, our partner network, and an active open-source community mean BPMN talent, and Camunda talent, is widely available rather than gated by one vendor.
Browse Camunda Academy →Frequently asked questions
Quick answers to the questions we hear most often from line-of-business leaders, architects, and developers evaluating BPMN-based orchestration.
What does BPMN stand for?
BPMN stands for Business Process Model and Notation. It is a graphical standard for modeling and executing business processes, maintained by the OMG and ratified as ISO/IEC 19510:2013.
Is BPMN still relevant in the age of AI agents?
Yes, more than ever. AI agents introduce non-deterministic behavior into business processes. BPMN provides the deterministic backbone of sequencing, escalation, approval, and audit that makes agent behavior safe and accountable in production. BPMN is the open standard for agentic orchestration.
What is the difference between BPMN and a flowchart?
A flowchart is a drawing. A BPMN diagram is also an executable specification: the same model that humans read is the source of truth that an orchestration engine runs. BPMN has precise semantics for events, gateways, subprocesses, and exception handling that ordinary flowcharts lack.
Is BPMN open source?
BPMN itself is an open standard, not software. The specification is freely available from the OMG. Camunda offers an open source BPMN modeler (Camunda Modeler) and runs BPMN on the Camunda orchestration platform.
Do I need to be a developer to use BPMN?
No. BPMN was designed so that business analysts, operations leaders, and developers can read the same diagram and agree on what it means. Business teams typically design and refine processes; developers and architects add the technical attributes that make the diagram executable.
Does BPMN replace decision logic and business rules?
No. BPMN handles the flow of work: what happens, in what order, by whom. Complex business decisions belong in DMN (Decision Model and Notation), the OMG companion standard. Camunda supports both natively. The combination gives you flexible processes with reusable, auditable decisions.
Can BPMN handle long-running processes?
Yes. BPMN was designed for processes that run for minutes, hours, days, or months. Camunda’s underlying engine, Zeebe, is built specifically for long-running, durable orchestration of business processes and multi-agent processes, including processes that span weeks of underwriting or months of fulfillment.
Is BPMN compatible with AI agent frameworks like LangChain or CrewAI?
Yes. Camunda orchestrates agents from any framework (LangChain, CrewAI, Microsoft Copilot, Salesforce Agentforce, custom-built) as participants in a BPMN process. BPMN sits above agent frameworks and governs how they participate in end-to-end work. Camunda also supports building agents natively in BPMN using ad-hoc subprocesses, with enforceable governance between agent reasoning and tool calls.
How is BPMN different from RPA?
RPA automates individual tasks at the screen level. BPMN orchestrates end-to-end processes that may invoke RPA bots as one of many step types. RPA is a Swiss Army knife for individual interactions; BPMN is the conductor that coordinates everything (bots, APIs, AI agents, and humans) into a complete business outcome.
Will my BPMN models run on a different engine if I switch vendors?
The notation will. The execution attributes (the technical bindings to a specific engine) typically don’t transfer. The same is true for SQL across database vendors. The right way to think about portability: your process design and your team’s skills are vendor-independent. The implementation is platform-specific. Choose a vendor whose philosophy and engine you can live with for the long term.
What is Camunda’s role in BPMN?
Camunda has been a contributor to the BPMN standard at the OMG for over 15 years. Our co-founders Jakob Freund and Bernd Ruecker contributed to the BPMN 2.0 specification and authored Real-Life BPMN, the most widely used BPMN book in the world. Camunda’s platform implements one of the deepest BPMN coverages of any orchestration engine, including patterns most vendors skip. We are currently leading the work to extend BPMN for AI agents.
How do I get started with BPMN?
The fastest path: download Real-Life BPMN for the methodology, open Camunda Modeler (free, open source) to draw your first process, and try Camunda’s free trial to deploy and run it. Most teams have a working orchestrated process in less than a day.
Books, training, and references
Camunda has spent two decades documenting how to use BPMN well. Here’s where to start, depending on your role.
Real-Life BPMN, 4th edition
By Jakob Freund and Bernd Ruecker. The definitive practitioner’s guide, by Camunda’s founders. Covers BPMN, DMN, the Camunda House framework, and how to introduce BPMN across your organization.
Get the book →Practical Process Automation
By Bernd Ruecker. The technical companion: orchestration patterns, microservices coordination, error handling, and how BPMN works at the engine level.
Get the book →Enterprise Process Orchestration
By Bernd Ruecker and Leon Strauch. For executives and transformation leaders: the strategic case for orchestration, organizational adoption patterns, and the role of BPMN in the AI-powered enterprise.
Get the book →BPMN and DMN courses
Free and certification-track courses on Camunda Academy for business analysts, developers, and architects. Aligns with the OMG OCEB certification program.
Browse courses →