Overview
No single notation fits every job. BPMN models flow and exceptions. EPC shines for ARIS and SAP alignment. SIPOC frames boundaries fast. VSM exposes time and bottlenecks. UML/IDEF help with system and knowledge capture. DMN/CMMN separate decisions and case work. Journey/Blueprints connect experience to operations. Capability and data models anchor scope and information.
When to use which
Design & automation
BPMN for flow and exceptions; pair with DMN for decisions; use CMMN for case-driven work.
Scope & time
SIPOC for kickoff boundaries; VSM for lead time, queues, and takt/pull design.
SAP & repository
EPC/ARIS when syncing with SAP Solution Manager; keep BPMN for detailed logic if you automate.
BPMN 2.0 (flow & decisions hand-off)
Purpose
Precise flow: tasks, events, gateways, message flows, and lanes (roles). Executable detail for workflow and integration.
Use
- Design roles, handoffs, and exception paths
- Specify integration rules and automation tasks
Primary links
- Spec: OMG BPMN 2.0.2
- Overview: bpmn.org
Good practice
- Verb–noun names; one outcome per lane
- Model exceptions explicitly; avoid hidden rework
- Attach controls, data, and KPIs to steps
EPC & ARIS for SAP (IDS Scheer)
Purpose
EPC (event + function chains) is the core ARIS notation for business-readable flows; widely used with SAP.
Use
- Business storytelling and repository governance in ARIS
- Synchronize models to SAP Solution Manager 7.2 for configuration/testing traceability
Primary links
- ARIS for SAP Solutions: softwareag.com
- ARIS–SolMan sync overview: ARIS Community
- EPC background: ARIS / IDS Scheer
BPMN + EPC together
- Keep EPC as the business front door
- Link BPMN L3 for automation logic
- Externalize complex rules in DMN
SIPOC (scope & boundaries)
Purpose
Fast framing: Suppliers, Inputs, Process, Outputs, Customers. Good at kickoff.
Link
Checklist
- Trigger and outcome in one line
- 3–7 high-level steps
- Key inputs/outputs and owners
Value-stream mapping (time & bottlenecks)
Purpose
Quantify lead time, wait, WIP; design pull and takt. Shows where flow breaks.
Link
Capture
- Cycle and changeover time per box
- Queues and WIP; information flow
- Customer demand and takt
UML Activity (system behavior)
Purpose
System-level behavior flows for software design; complements business process models.
Link
Use
- Document service or component behavior under a process step
- Clarify async events and guards
IDEF0 (function decomposition)
Purpose
Top-down “what transforms what” with ICOM: Inputs, Controls, Outputs, Mechanisms.
Links
Use
- Scope and interface clarity before flow modeling
- Keep functions clean; do flow in BPMN/EPC
IDEF3 (scenario capture)
Purpose
Capture “how it actually happens” from SMEs—scenarios and object state transitions.
Link
Use
- Early discovery before BPMN/EPC detail
- Variant documentation without over-modeling
DMN (Decision Model & Notation)
Purpose
Decision requirements (DRD) and decision tables (FEEL). Externalize rules cleanly.
Links
Use with BPMN
- Call decisions from BPMN tasks
- Keep rules testable and reusable
CMMN (Case Management)
Use
- Investigations, clinical/legal cases, complex service exceptions
- Pair with BPMN for predictable sub-flows
Customer journey maps
Purpose
Narrative of user actions, thoughts, and feelings across channels over time.
Link
Bridge to process
- Turn touchpoints into backstage process changes
- Measure with on-time, first-contact-resolution, NPS/CSAT
Service blueprint
Purpose
Frontstage/backstage actions, support processes, evidence, and lines of interaction/support.
Link
Bridge to process
- Translate backstage steps into BPMN/Workflows
- Align staffing, knowledge, and SLAs with demand
Capability maps
Purpose
What the business must be able to do; independent of organization and systems. Use for strategy and funding.
Links
TOGAF overview and capability-based planning: The Open Group · Business Architecture Guild
Bridge to process
- Map processes to the capabilities they realize
- Heat-map by value, risk, cost to set priorities
Data / ER models
Purpose
Define entities and relationships that processes consume and produce; name sources and ownership.
Link
Bridge to process
- Attach data contracts to BPMN steps
- Ensure master/reference data has stewards and retention
Right level of detail
Executive view
One page: SIPOC + L2 BPMN + two VSM numbers (lead time, WIP). Focus on outcome and constraints.
Designer view
L3 BPMN with lanes, events, gateways, data, controls, KPIs; DMN tables for rules; CMMN for case paths.
Stop adding detail when…
- Steps repeat across lanes
- Names drift into team or system labels
- The main path is unclear in 30 seconds
Common errors
Mixing methods
Do not drop VSM icons into BPMN or bury SIPOC in notes. Link artefacts and keep each clean.
Role confusion
Swimlanes are roles, not teams or systems. Keep names stable across maps.
Invisible evidence
Show where records appear and who owns them. Avoid models that cannot support audit.
Tooling & templates
Repository principles
- One source of truth; stable IDs; naming rules
- Change calendar; review cadence; archive policy
- Role-based access and version history
What to require
- BPMN 2.0 export/import; DMN/CMMN support if needed
- Links to SOPs, controls, and data contracts
- Comment threads and traceability to releases
References
- OMG BPMN 2.0.2 — spec · overview
- DMN — spec
- CMMN — spec
- EPC/ARIS for SAP — Software AG · ARIS Community
- SIPOC — ASQ
- VSM — Lean Enterprise Institute
- APQC PCF — apqc.org
- IDEF0 — NIST FIPS 183
- IDEF3 — idef.com
- UML — OMG UML
- IDEF1X (ER) — NIST FIPS 184
- Service blueprints — NN/g
- Customer journeys — NN/g
Pick the right method. Link them. Keep one source of truth.
If you want starter templates and a linking guide, ask for a copy.