OCEB 2 Business Intermediate: Process Landscape and Process Architecture

This domain tests how processes are organized into a coherent architecture, from enterprise landscape down to detailed subprocesses, and how that architecture connects strategy to execution.

Levels of architecture

Process architecture organizes processes at multiple levels. Level 0 is the process landscape, a high-level map of process groups. Level 1 groups related processes; level 2 shows end-to-end process models; level 3 details subprocesses and activities. A process map communicates scope and relationships; a process model adds control flow, roles and data. Architecture principles include customer orientation, end-to-end ownership, separation of core and support, and traceability from strategy to execution.

Reference models

Reference models such as APQC's Process Classification Framework and SCOR provide generic hierarchies and terminology. They are adapted, not copied blindly. Architecture must show interfaces, handoffs and shared services.

Worked example

A retailer's level 0 landscape shows plan, source, make, deliver, return, and enabling processes. Level 1 under deliver includes order management, warehousing and transport. Level 2 models order fulfillment end to end across sales, warehouse and finance. Level 3 details pick, pack and dispatch. Reasoning: each level serves a different audience; executives need the landscape, analysts need level 2 and level 3.

Traps

Do not model detailed BPMN at landscape level. Do not mix levels in one diagram. Avoid architecture that mirrors the org chart rather than value creation. Do not omit support and management processes. A landscape without owners and interfaces is decorative, not actionable.