BPMN — Business Process Model and Notation

OMG standard graphical notation for business processes. The canonical modelling language in BPM; the Fundamentals textbook devotes chapters 3 and 4 to it.

Core elements

Flow objects

Events — start / intermediate / end; typed (message, timer, error, signal, escalation, compensation).
Activities — tasks, sub-processes, call activities; typed (user, service, script, send, receive, business rule).
Gateways — XOR (exclusive), AND (parallel), OR (inclusive), event-based.

Connecting objects

Sequence flows, message flows, associations.

Swimlanes

Pools — participants.
Lanes — internal roles/units.

Artefacts

Data objects / data stores
Annotations

Advanced topics (ch. 4)

Events — message, temporal, racing, racing-with-choice.
Exceptions — internal, external, boundary, non-interrupting, event sub-processes, compensation.
Business rules — referenced out to frameworks/dmn.

Executable BPMN (ch. 10)

Raised to executable status by specifying data types, data mappings, service tasks, user tasks, script tasks, rule invocations, and error handling.

Role in APM

BPMN is an operational specification language per sources/2026-calvanese-agentic-bpm-manifesto: it tells agents how to act. APM adds a normative layer on top via frames.

LLM-assisted BPMN authoring

Recent work treats BPMN models as mutable structures edited via LLMs through a constrained set of operations rather than regenerated as XML each turn. See concepts/llm-assisted-process-modelling for the architectural pattern (structured intermediate representation + atomic editing functions + schema-validation retry loop) and Licardo et al. 2026 (BPMN Assistant) for a concrete implementation. Frontier models (GPT-5.1, Claude 4.5 Sonnet) reach parity in direct-XML and JSON-IR formats; open-weight models (DeepSeek V3, Llama 3.3 70B) need the structured intermediate to be reliable.

When to choose BPMN over flowcharts

For automation projects, the answer is almost always BPMN — its token semantics, gateway typology, executable extensions, and tool ecosystem are the only path to a workflow-engine-deployable model. See syntheses/bpmn-in-automation-projects for the full decision matrix, hybrid-usage pattern (flowcharts in scoping → BPMN in design/execution → text for stakeholder validation), and LLM-era cost-shift analysis.

frameworks/cmmn · frameworks/dmn · concepts/process-aware-information-system · concepts/llm-assisted-process-modelling · concepts/neuro-symbolic-bpm · syntheses/bpmn-in-automation-projects · syntheses/bpmn-modelling-practical-guide