Imagine a situation many organizations face: two teams — operations and sales — are working on the same complaint handling process, but each understands it completely differently. Operations see an escalation path, sales see customer contact. The lack of a common language causes delays, misunderstandings, and frustration on both sides. This is exactly when BPMN 2.0 enters the scene — a notation that gives organizations a universal, graphical way of describing processes, understandable to both business people and technical teams.
BPMN (Business Process Model and Notation) version 2.0 is an international standard managed by the Object Management Group (OMG), used worldwide for documenting, analyzing, and automating business processes. In this article, we’ll progress from basic notation elements, through modeling techniques, to specific tools and practical applications.
Quick navigation
- What is BPMN 2.0 and why has it become a standard?
- What are the basic elements of BPMN notation?
- What are events in BPMN and what roles do they play?
- How do decision gateways work in process models?
- How does BPMN describe workflow and communication?
- What benefits does process modeling in BPMN bring?
- Which tools support modeling in BPMN 2.0?
- What is the relationship between BPMN, DMN, and CMMN?
- Where does BPMN find practical business applications?
- How do EITT trainings help build BPM competencies?
What is BPMN 2.0 and why has it become a standard?
BPMN 2.0 is a graphical notation for presenting business processes in the form of readable diagrams. It was developed to create a common communication language between business analysts, operational managers, IT architects, and programmers. Previous approaches — verbal descriptions, procedure tables, or informal flowcharts — often led to ambiguity. BPMN eliminates this problem through strictly defined semantics for each graphical element.
The BPMN 2.0 standard was adopted by ISO as norm ISO/IEC 19510:2013, confirming its international recognition. Unlike earlier versions, BPMN 2.0 introduced formal execution semantics — meaning that a BPMN diagram can be not only an analytical document but also a direct basis for automatic process execution by a BPM engine.
The key advantage of BPMN over other notations (such as EPC, UML Activity Diagrams, or flowcharts) lies in combining three characteristics: it’s simple enough for non-technical people to read, precise enough to serve as a technical specification, and formal enough to enable running processes in IT systems based on it.
Why organizations choose BPMN:
- Universal language understandable to business and IT
- International standard (ISO/IEC 19510:2013)
- Ability to directly execute models through BPM engines
- Rich set of graphical elements covering complex scenarios
- Wide availability of tools (open-source and commercial)
What are the basic elements of BPMN notation?
BPMN 2.0 notation is based on four main categories of graphical elements: flow objects, connecting objects, swimlanes, and artifacts. Each of these elements plays a specific role in the process model and allows presenting different aspects of organizational operations.
Flow objects are the backbone of every BPMN diagram. They include three fundamental types: events, activities, and gateways. These elements define what happens in the process, when it starts and ends, and how decisions are made.
Connecting objects determine the sequence and method of communication between process elements. Sequence flow defines the order of activity execution, message flow models information exchange between participants, and association connects artifacts with flow elements.
Swimlanes — pools and lanes — allow assigning responsibility for specific activities to particular people, teams, or systems. A pool represents a process participant (e.g., an organization or system), and lanes within a pool divide it into organizational units or roles.
Artifacts, such as data objects, text annotations, and groups, add context to the model without directly affecting the process flow. Thanks to them, the diagram becomes more readable and informative.
| Category | Element | Symbol | Description |
|---|---|---|---|
| Flow objects | Start event | Circle with thin line | Indicates where the process begins |
| Flow objects | Intermediate event | Circle with double line | Represents something that happens during the process |
| Flow objects | End event | Circle with thick line | Indicates process completion |
| Flow objects | Activity (task) | Rounded rectangle | Unit of work to be performed |
| Flow objects | Subprocess | Rounded rectangle with ”+” marker | Complex activity containing internal flow |
| Flow objects | Gateway | Diamond | Decision point or flow branching |
| Connecting objects | Sequence flow | Solid line with arrow | Determines the order of activity execution |
| Connecting objects | Message flow | Dashed line with arrow | Models information exchange between pools |
| Swimlanes | Pool | Large rectangle with header | Represents a process participant |
| Swimlanes | Lane | Division within pool | Assigns responsibility to a role or team |
| Artifacts | Data object | Document icon | Presents data used or produced by an activity |
| Artifacts | Annotation | Open rectangle with dashed line | Additional comment to a diagram element |
What are events in BPMN and what roles do they play?
Events are one of the most important and most elaborate elements of BPMN notation. They represent something that “happens” during the process — it can be a start moment, arrival of a message, expiration of a deadline, occurrence of an error, or a signal from an external system. BPMN 2.0 defines dozens of event types, grouped according to three criteria: position in the process (start, intermediate, end), nature (throwing or catching), and trigger (message, timer, error, signal, compensation, and others).
Start events determine how the process is initiated. This can be a simple manual start (start event without trigger), arrival of a message from another participant, passage of time (e.g., daily at 8:00 AM), or fulfillment of specific business conditions.
Intermediate events can be placed in the main process flow or on the boundary of an activity (boundary events). A boundary event allows defining a reaction to an exceptional situation — for example, if the activity “Wait for customer response” is not completed within 48 hours, a timer event on the boundary of this activity can trigger an alternative escalation path.
End events indicate how the process or process path is completed. Besides simple completion, BPMN defines end events with message (sending notification), error (completion with problem signaling), signals, or compensation (reversing effects of previous activities).
| Event type | Trigger | Application example |
|---|---|---|
| Start — message | Email, order arrival | Order handling process triggered by customer order |
| Start — timer | Time schedule | Report generation daily at 6:00 AM |
| Start — signal | Broadcast from another process | Audit process initiation after “end of quarter” signal |
| Intermediate — timer (boundary) | Deadline expiration | Escalation when customer doesn’t respond within 48h |
| Intermediate — error (boundary) | Exception occurrence | Payment error handling in purchase process |
| Intermediate — message (in flow) | Waiting for message | Waiting for delivery confirmation from supplier |
| End — message | Sending notification | Sending order fulfillment confirmation |
| End — error | Completion with error | Credit application rejection |
| End — termination | Immediate completion | Cancellation of entire process |
How do decision gateways work in process models?
Gateways are BPMN elements responsible for controlling process flow. They allow branching paths (divergence) and merging them again (convergence). Each gateway type implements different logic, allowing precise mapping of even very complex business rules.
The exclusive gateway (Exclusive Gateway, marked with “X” symbol) is the most commonly used type. It works like a question with one correct answer — the flow follows exactly one of the available paths, based on a logical condition. It’s the equivalent of the “if-else” statement in programming. For example: “Does the order value exceed 10,000 PLN?” — if yes, the path leads to manager approval, if not — to automatic fulfillment.
The parallel gateway (Parallel Gateway, marked with ”+” symbol) activates all outgoing paths simultaneously, without conditions. In merge mode, it waits for completion of all incoming paths. It’s indispensable everywhere activities can (or must) be performed concurrently — for example, simultaneous document verification and creditworthiness check.
The inclusive gateway (Inclusive Gateway, marked with “O” symbol) is a combination of both above — it can activate one or more paths simultaneously, depending on conditions. In merge mode, it waits for completion of those paths that were activated. It’s useful when several conditions can be met simultaneously.
The event-based gateway (Event-Based Gateway) is a special gateway type where path selection depends on which event occurs first. For example: a process can wait either for customer response (message event) or for expiration of a 7-day deadline (timer event) — whichever of these events happens earlier determines the further process course.
| Gateway | Symbol | Logic | Typical application |
|---|---|---|---|
| Exclusive (XOR) | Diamond with “X” | Exactly one path | Simple yes/no decision |
| Parallel (AND) | Diamond with ”+“ | All paths simultaneously | Parallel activities |
| Inclusive (OR) | Diamond with “O” | One or multiple paths | Non-exclusive conditions |
| Event-based | Diamond with circle | Path depends on first event | Waiting for one of many events |
| Complex | Diamond with star | Custom logic | Advanced merging scenarios |
How does BPMN describe workflow and communication?
Modeling flow in BPMN 2.0 occurs at several levels: within a single process, between process participants, and at the choreography level (interactions between organizations). This multi-level architecture allows creating models with varying degrees of detail — from general end-to-end process overview to detailed technical specification.
At the lowest level, sequence flow connects flow objects (activities, events, gateways) within one pool. Specific rules apply when drawing these connections — for example, sequence flow cannot cross pool boundaries, and each activity must have at least one incoming and one outgoing connection (except for start and end events).
Message flow serves to model information exchange between different pools — that is, between separate process participants. This is a key element in modeling inter-organizational processes, such as supply chain, complaint handling with external partner involvement, or cooperation between company departments treated as independent units.
BPMN 2.0 also introduces the concept of choreography diagram, which focuses on the sequence of interactions between participants without entering internal details of each. This diagram type is particularly useful in the context of system integration and API design, where the most important aspect is the order and content of exchanged messages.
Subprocesses constitute a mechanism for hierarchical organization of models. A complex activity can be “opened” as a separate diagram with its own flow, events, and gateways. This keeps the main process diagram readable, while details are available at a lower level — which is particularly valuable in large organizations where processes encompass dozens or hundreds of activities.
What benefits does process modeling in BPMN bring?
The first and most frequently mentioned benefit is improved communication between departments. When the order handling process is described in BPMN, the sales department, logistics, finance, and customer service see exactly the same sequence of activities. There’s no room for interpretation — each diagram element has unambiguous meaning defined in the standard.
Modeling in BPMN facilitates identification of bottlenecks and inefficiencies. The process diagram allows visually locating places where work stops, where unnecessary approval loops occur, activity duplications, or missing exception handling paths exist. This is the first step toward business process optimization, which leads to measurable time and cost savings.
Another benefit is the ability to standardize and document processes for quality management systems (ISO 9001), internal audits, and compliance purposes. BPMN models constitute living, updateable documentation that replaces static procedure descriptions and allows faster onboarding of new employees.
From a technological perspective, BPMN 2.0 forms a bridge between business analysis and implementation. A process model created by an analyst can be directly imported into a BPM engine (such as Camunda, Flowable, or Activiti) and run as a working workflow. This eliminates the costly stage of “translating” business requirements into technical specification.
Modeling in BPMN also supports making informed decisions about automation. The diagram clearly shows which activities are performed manually, which can be automated, and which require human decision. This allows the organization to prioritize automation investments where they will bring the greatest return.
Which tools support modeling in BPMN 2.0?
The choice of BPMN modeling tool depends on organizational needs — from simple process documentation, through team collaboration, to full automation and monitoring. The market offers both free open-source solutions and advanced commercial platforms.
Camunda Modeler is a free desktop tool dedicated to creating BPMN 2.0, DMN diagrams, and Camunda forms. Its biggest advantage is direct integration with the Camunda engine — a model created in the Modeler can be immediately deployed for execution. The tool is intuitive, lightweight, and works well both for learning BPMN and in professional automation projects.
SAP Signavio (formerly Signavio Process Manager) is an enterprise-class platform for process modeling, analysis, and management. It offers cloud-based team collaboration, process repository, simulations, variance analysis (process mining), and integration with SAP systems. It’s particularly popular in large organizations that need central management of process architecture.
Bizagi Modeler is a free desktop tool with a clear interface and rich library of BPMN elements. It enables exporting diagrams to graphic formats, PDF, and Word. The extended version (Bizagi Automation Server) allows process automation. Bizagi is often recommended as a tool for learning BPMN thanks to its user-friendly interface.
bpmn.io is an open-source JavaScript library (behind Camunda Modeler) that enables embedding a BPMN editor in web applications. It’s frequently used by development teams to build their own process modeling tools.
| Tool | Type | Cost | Best for |
|---|---|---|---|
| Camunda Modeler | Desktop, open-source | Free | Modeling + automation (Camunda) |
| SAP Signavio | Cloud, enterprise | Commercial | Central process management in large companies |
| Bizagi Modeler | Desktop | Free (Modeler) | Learning BPMN, process documentation |
| bpmn.io | Web library, open-source | Free | Embedding BPMN editor in applications |
| ARIS | Cloud/Desktop, enterprise | Commercial | Corporate architecture, governance |
| Lucidchart | Cloud, SaaS | Freemium | Quick diagrams, team collaboration |
| draw.io (diagrams.net) | Cloud/Desktop | Free | Simple diagrams, informal modeling |
What is the relationship between BPMN, DMN, and CMMN?
BPMN 2.0 doesn’t operate in isolation — it’s part of the OMG standards ecosystem for business process management, also including DMN (Decision Model and Notation) and CMMN (Case Management Model and Notation). Each of these standards addresses a different aspect of organizational work, and together they create comprehensive frameworks for modeling complex business scenarios.
DMN (Decision Model and Notation) serves to model and automate business decisions. While BPMN describes “what to do and in what order,” DMN answers the question “how to make a decision at a given point in the process.” Typical example: in the BPMN diagram there’s an activity “Assess customer creditworthiness” — the logic of this assessment (score thresholds, criteria weights, decision tables) is defined in the DMN model. BPM engines such as Camunda support both standards, enabling seamless integration of processes and decisions.
CMMN (Case Management Model and Notation) concerns case management — situations where the work course is not fully predetermined and depends on knowledge worker decisions. An example is handling a complex insurance claim, where the order of activities may change depending on circumstances. CMMN complements BPMN where rigid, sequential process flow doesn’t reflect work reality.
In practice, many organizations use BPMN as the main modeling standard, DMN for formalizing decision rules, and CMMN in selected areas (e.g., customer service, incident management). Integration of these three standards allows creating a coherent operational picture of the organization.
| Standard | Application | Example |
|---|---|---|
| BPMN 2.0 | Process flow (activity sequence) | Order handling process from placement to delivery |
| DMN | Business decision logic | Decision table for creditworthiness assessment |
| CMMN | Case management (flexible flow) | Handling complex insurance claim |
Where does BPMN find practical business applications?
BPMN 2.0 finds application wherever an organization needs to understand, document, or automate its processes. The scope of applications is very broad — from initial process analysis, through digital transformation, to building workflow systems based on BPM engines.
In the context of digital transformation, BPMN forms the foundation for mapping “as-is” (current) processes and designing “to-be” (target) processes. Before an organization invests in new IT systems, it’s worth presenting on BPMN diagrams how processes work today and how they should look after changes. This allows conscious decision-making about the scope and priorities of transformation.
In the financial sector, BPMN is used to model credit processes, compliance (KYC/AML), settlements, and complaint handling. Precise process documentation in BPMN is often required by regulators and auditors.
In manufacturing and logistics, BPMN diagrams model supply chain processes, order management, quality control, and returns handling. Particularly valuable is modeling inter-organizational processes involving suppliers, carriers, and customers — where BPMN pools naturally represent different participants.
In IT and DevOps, BPMN supports modeling ITSM processes (incident, change, problem management), CI/CD processes, and new employee onboarding. Process models integrate with tools such as Jira, ServiceNow, or monitoring systems.
In public administration, BPMN is used to document administrative procedures, e-services, and document workflows. Process standardization in BPMN facilitates e-government system implementation and improves transparency of office operations.
Regardless of industry, BPMN works wherever the process involves many participants, requires decisions, exception handling, or IT system integration. The more complex the process, the greater value its formal modeling brings.
How do EITT trainings help build BPM competencies?
Effective process modeling in BPMN requires not only notation knowledge but primarily analytical thinking skills, identifying process boundaries, defining appropriate detail levels, and collaborating with stakeholders from different departments. These are competencies most effectively built through practical training led by experienced experts.
EITT specializes in developing business process management competencies, offering open and closed trainings covering BPMN 2.0, BPM tools (including Camunda), Lean and Six Sigma methodologies, and change management in the context of process optimization. Training programs combine theory with intensive practical workshops where participants model real processes from their own organizations.
With a network of over 500 experts, over 2500 completed trainings, and average participant rating of 4.8/5, EITT provides access to practitioner knowledge — people who implement BPM solutions daily in organizations of various sizes and from different industries. BPMN trainings at EITT are designed so participants leave with concrete skills they can apply at work the very next day.
Whether an organization is just beginning its process modeling journey or planning BPM engine implementation and workflow automation — properly selected training allows avoiding typical mistakes, accelerating the project, and building internal competencies that will pay dividends for years.
Business process modeling in BPMN 2.0 is an investment that brings benefits at many levels: from better communication between departments, through identification of optimization areas, to the possibility of process automation in BPM engines. This standard connects the worlds of business and technology, offering a common language that eliminates misunderstandings and accelerates digital transformation. The key to success, however, lies not in the tool itself but in the competencies of the people who apply it — which is why building knowledge in BPMN and more broadly conceived process management should be one of the priorities of every organization striving for operational excellence.
Read also
- How to Get Familiar with BPMN: A Review of Business Process Modeling Tools
- Business Process Mapping — From Analysis to Optimization
- Data Modeling with UML: Key to Better Information Management in Your Company
Develop your skills
Want to deepen your knowledge in this area? Check out our training led by experienced EITT instructors.
➡️ Understanding business process modeling with BPMN 2.0 — EITT training
Frequently Asked Questions
Do I need a technical background to learn BPMN 2.0 notation?
No, one of the key advantages of BPMN 2.0 is that it was designed to be readable by both business and technical people. Business analysts, operational managers, and process owners can learn the core notation elements relatively quickly, while technical teams can leverage the same diagrams for implementation and automation purposes.
What is the difference between a BPMN diagram used for documentation and one used for process automation?
A documentation-level BPMN diagram focuses on readability and capturing the general flow of activities, often omitting technical details. An executable BPMN diagram includes additional attributes such as service task configurations, data mappings, and error handling definitions that allow a BPM engine like Camunda to run the process automatically.
How many BPMN elements do I need to know to start modeling processes effectively?
For most business process documentation needs, you can start with about 10-15 core elements: start and end events, tasks, exclusive and parallel gateways, sequence flows, pools, and lanes. As your modeling maturity grows, you can gradually incorporate more advanced elements like intermediate events, subprocesses, and message flows.
Can BPMN be used together with other standards like DMN or UML?
Yes, BPMN 2.0 is designed to work alongside DMN (Decision Model and Notation) for modeling business decision logic and CMMN for flexible case management. Many organizations use BPMN for process flow, DMN for decision tables at specific process points, and UML for system architecture, creating a comprehensive modeling ecosystem.