BPM Concepts and the Process Lifecycle
What this domain tests
OCEB 2 Fundamental expects precise BPM vocabulary: what a business process is, how processes are classified, and how the lifecycle phases relate and feed one another.
Core concepts
- A business process is a repeatable, end-to-end set of coordinated activities that turns inputs into outputs of value for a customer. It has a trigger, a defined outcome, an owner and measures.
- Process types: core (customer-facing, revenue-generating), support (enabling, e.g. IT help desk), management (planning, risk, governance).
- The functional view organises work by department; the process view organises it by value delivery across departments. BPM strengthens the process view without abolishing functions.
- Lifecycle (common six-phase form): process identification, process discovery (as-is modelling), process analysis, process redesign (to-be), process implementation, process monitoring and controlling. Monitoring loops back into identification and discovery.
Worked example
A retailer prioritises purchase-to-pay in process identification because it is high-volume and carries late-payment penalties. Discovery interviews yield an as-is model. Analysis finds invoice matching split across three teams. Redesign consolidates matching into a shared service. Implementation deploys a workflow; monitoring tracks cycle time and feeds a new priority into the next loop. Reasoning: each phase consumes the previous phase's artefact, and monitoring restarts the cycle rather than ending it.
Traps that cost marks
Confusing discovery (documenting what is) with analysis (diagnosing why). Treating monitoring as a terminal step. Equating BPM with workflow automation, which ignores strategy, architecture and governance.