Business Process Management (BPM) is the discipline of modelling, executing, monitoring and continuously improving end-to-end business processes. BPM combines methodology (process notation, governance, improvement cycles) with tooling (modelling environments, process automation engines, monitoring dashboards). For ERP-bearing organisations, BPM sits adjacent to the ERP — the ERP encodes the operational data and transactions; BPM orchestrates the workflows and human steps across systems.
BPMN — the standard notation
The Business Process Model and Notation (BPMN) standard, maintained by the OMG (Object Management Group), is the dominant graphical notation for business processes. BPMN 2.0 (in force since 2011) defines symbols for activities, events, gateways, swimlanes, message flows and data objects — readable by business stakeholders, executable by BPM engines. Modern BPM tools (Camunda, Signavio, ARIS, Bizagi, Bonita) use BPMN 2.0 as native format. The standard is technology-neutral: a BPMN diagram from one tool is broadly readable in another, though execution semantics depend on the engine. For DACH mid-market, Camunda (Berlin-headquartered, open-source-with-enterprise tier) is the most-deployed BPM engine.
Leading BPM platforms
Camunda Platform 8 — modern cloud-native BPM with strong DACH presence. Open-source core with commercial Enterprise tier. Signavio (SAP-owned since 2021) — cloud BPM and process-discovery, integrated with SAP S/4HANA. ARIS (Software AG) — comprehensive enterprise BPM with long DACH history. Bizagi, BonitaSoft, Appian, Pega BPM — further enterprise platforms. Microsoft Power Automate — low-code workflow automation popular in DACH through Microsoft 365 bundling. Open source: Camunda Community, Activiti, Flowable, jBPM. For mid-market with selective process-automation needs, Camunda or Microsoft Power Automate are the most common starting points; enterprises with mature BPM programmes often centralise on ARIS or Signavio for documentation plus Camunda for execution.
BPM versus RPA versus process mining
Three adjacent disciplines often confused but complementary. BPM: designs and executes intended processes, with explicit workflow definitions and human-task orchestration. RPA: automates UI-based interactions with applications, typically replacing manual data entry. Process mining: discovers actual process flows from event logs, comparing them to intended designs. Together: process mining reveals what really happens; BPM defines what should happen; RPA automates the routine human steps that BPM-orchestrated workflows still require. Mature process-improvement programmes apply all three iteratively.
ERP integration
BPM and ERP integrate in two directions. BPM orchestrates ERP transactions: a complex multi-system workflow (e.g., new customer onboarding involving credit check, master-data creation in CRM and ERP, contract generation, training delivery) is modelled and executed in the BPM engine, calling ERP APIs at the relevant steps. ERP triggers BPM workflows: ERP events (large purchase requisition, exception in production, customer complaint) trigger BPM-managed approval or follow-up workflows. The integration uses REST APIs, webhooks or event-streaming. Mid-market ERP products increasingly include lightweight BPM capability natively (Microsoft Power Automate in Dynamics 365, weclapp Workflow Builder, NetSuite SuiteFlow); dedicated BPM platforms remain valuable for complex cross-system orchestration.
Do we need dedicated BPM software or is the ERP's built-in workflow enough?
For workflows entirely inside the ERP, the built-in workflow engine usually suffices. For workflows spanning multiple systems (ERP, CRM, e-commerce, HR, document management), dedicated BPM platforms offer better orchestration, monitoring and governance. Threshold: above 10 cross-system workflows with significant complexity, BPM investment pays back.
Is Camunda still relevant in 2026?
Yes, very much. Camunda Platform 8 (cloud-native, microservice-friendly) is a leading choice for new BPM projects in DACH and globally. The combination of open-source roots, enterprise-grade capabilities and BPMN 2.0 standards compliance positions it strongly. Major DACH enterprises (Deutsche Bahn, Lufthansa, Sparkassen) operate large Camunda deployments.
How does BPM relate to ERP customisation?
BPM is often the right place for workflows that would otherwise be ERP customisation. Keeping workflow logic in a BPM engine outside the ERP core protects the ERP from customisation that breaks at upgrades. The clean-core principle (see customising) explicitly recommends moving workflow logic to side-by-side BPM or low-code platforms.
