Why this matters. Digital business processes are cross-functional, software-driven sequences of value-creating activities. The Bitkom definition is clear — industry practice rarely is. The most common false start: selecting a BPMS before the process model fits the ERP backbone. The result is digitalised islands sitting next to a stable but unused ERP.
Three layers — three responsibilities
Digital business processes cannot be reduced to one software layer. They live across three interlocking layers, each with its own ownership.
-
Strategy layer: which processes exist at all, who owns them, how they evolve. Owner: the executive board with a BPM function.
-
Model layer: how processes are modelled — BPMN 2.0 for flows, DMN 1.1 for decision logic. Owner: the process owner.
-
Execution layer: where processes run — ERP, workflow engine, RPA, BPMS. Owner: IT and business jointly.
BPMN 2.0 plus DMN 1.1 — the modelling tandem
BPMN 2.0 models the sequence of activities — who does what when. Forrester measures 30 to 50 percent productivity gains in back-office work. DMN 1.1 models the decision logic — which rule triggers which action. Using BPMN without DMN buries business rules inside software configurations that nobody can find when the rule changes.
-
When BPMN alone suffices: simple, linear flows with no complex branching rules.
-
When DMN becomes essential: as soon as business rules change more often than the process sequence — price approvals, credit limits, sign-off thresholds.
-
ISO link: both standards deliver auditable artefacts for ISO 27001, ISO 9001 and German GoBD requirements.
Where BPMS initiatives actually fail
A Hessian plant manufacturer with around 320 employees commissioned a BPMS project for order handling. The BPMS was implemented, workflows were configured, models were drawn — but the link to the ERP stayed as a set of point-to-point interfaces. Eight months later there were two stock worlds: the one in the BPMS and the one in the ERP. The executive board no longer received consolidated reporting because the two systems fought over data ownership.
In practice, one question decides outcomes: is the ERP backbone stable and integrated before the BPMS initiative starts — or is the BPMS being asked to plug gaps the ERP left open. A methodical ERP selection resolves this backbone question; without it, the BPMS becomes a shadow data world.
What to do next
If you want to set up digital business processes cleanly:
-
Separate the three layers — strategy, model, execution — with named ownership for each.
-
Model in BPMN 2.0 plus DMN 1.1 — decision logic does not belong in software configurations.
-
Resolve the ERP backbone question before selecting a BPMS — not in parallel, not afterwards.
If you want to walk through these three layers on a concrete initiative, we will sit through the backbone logic with you in twenty minutes — before any BPMS RFP is written.
FAQ
Cross-functional, software-driven sequences of value-creating activities (Bitkom). They cover strategy, model and execution — not just the running software. Digital business processes are not the same as digital tools in use.
BPMN 2.0 models the sequence — who does what when. DMN 1.1 models the decision logic — which rule triggers which action. Business rules configured only in software get lost when the rule changes. With DMN they stay auditable and portable.
The ERP backbone. A BPMS asked to plug gaps in the ERP becomes a shadow data world. Resolve the backbone first, then decide where the BPMS complements the orchestration — typically where the ERP's own workflow functions are too rigid.