OCEB 2 Business Advanced cheat sheet

Strategy-to-process traceability rule: every core process on the process architecture must map to at least one enterprise goal or strategic objective; unmapped processes are candidates for consolidation, outsourcing, or retirement.

Process hierarchy tiers (typical): Level 1 process group / value chain, Level 2 process, Level 3 sub-process, Level 4 activity, Level 5 task-step. Governance and ownership are assigned at Level 1-2; measurement at Level 2-3.

Value chain (Porter) separates primary activities (inbound logistics, operations, outbound logistics, marketing and sales, service) from support activities (firm infrastructure, HR, technology development, procurement).

Process classification frameworks such as APQC PCF provide a neutral cross-industry reference taxonomy used to benchmark and to anchor an organization-specific architecture.

Goal decomposition: enterprise goal -> critical success factor -> key performance indicator -> process performance indicator -> operational metric. Each lower level must be causally defensible against the level above.

Resource alignment test: for each process improvement initiative, record required capability, headcount, budget, and IT change; initiatives without an assigned owner and funded capacity are deferred, not started.

Process ownership model: process owner is accountable for end-to-end performance and design; functional manager is accountable for resource supply and competence; separating these avoids conflicting KPIs.

Maturity reference: CMMI process maturity levels 1 initial, 2 managed, 3 defined, 4 quantitatively managed, 5 optimizing; BPMM (OMG) adds an explicit level 0 absent and emphasizes organizational business process maturity.

Portfolio decision rule: prioritize initiatives by (strategic impact x feasibility) or weighted scoring; a common formula is priority = (goal contribution weight x benefit) / (cost x risk exposure).

BPMN 2.0 gateway semantics: exclusive (XOR) takes exactly one path; inclusive (OR) takes one or more paths whose conditions hold; parallel (AND) takes all paths; event-based gateway waits for the first occurring event and is a race, not a decision.

Compensation differs from error handling: an error boundary event interrupts and routes the token to exception handling, while compensation triggers the compensating handler of already-completed activities and does not interrupt the normal flow.

Event sub-process is not connected by sequence flows, is triggered by its start event, and can interrupt or not interrupt the enclosing scope; a boundary event is attached to the activity boundary and always has a host activity.

Token simulation rules: an AND split creates one token per outgoing flow; an AND join waits for a token on every incoming flow; an XOR join passes each arriving token immediately; an OR join waits only for the branches actually activated.

Choreography models interaction between two or more participants with message exchange, no central orchestrator; collaboration uses pools and message flows, and a black-box pool hides internal process detail.

Data modeling in BPMN: data objects are artifacts with no control-flow effect; data stores persist across instances; data input and data output associations connect to activities; property definitions support data state.

Model quality criteria: syntactic correctness, semantic validity, completeness relative to the modeling purpose, and pragmatic quality (understandability) measured by error rates in comprehension tests.

Soundness (van der Aalst) requires: every process instance has an option to complete, no dead tasks, and no leftover tokens at completion; relaxed soundness permits specified alternative termination.

Decomposition guideline: a sub-process should be extracted when it has a stable interface, is reused, or exceeds roughly 15-20 flow objects on one diagram; excessive nesting harms comprehension.

Program versus project: a BPM program is an ongoing organizational capability with a lifecycle (identify, design, implement, monitor, optimize); projects are temporary and deliver specific process changes.

Center of excellence roles typically include BPM lead/sponsor, process owners, process architects, method experts, and BPM analysts; a federated model distributes execution to business units with central standards.

Governance bodies: steering committee sets portfolio priorities and resolves escalations; process council coordinates cross-functional design; architecture board enforces modeling and repository standards.

Maturity roadmap instruments: capability assessment against a maturity model, process portfolio inventory, skills matrix, and a method handbook defining notation, templates, and review gates.

Benefit realization requires a baseline measurement before change and a defined measurement window after; unmeasured baselines make ROI claims unverifiable.

Risk categories in BPM programs: scope creep across the process portfolio, method dilution by decentralized teams, tool-repository divergence, key-person dependency, and change fatigue.

Value reporting: distinguish efficiency metrics (cycle time, cost per instance, first-time-right) from effectiveness metrics (customer satisfaction, compliance rate, revenue influence).

Repository governance rule: one authoritative model version per process, mandatory metadata (owner, version, status, linked goals), and a defined review-approval workflow before publication.

Program KPI examples: share of core processes modeled and approved, share of process KPIs with active targets, number of process owners formally appointed, cycle time of the model change request.

Kotter's eight steps: urgency, guiding coalition, vision, communicate, empower and remove barriers, short-term wins, consolidate gains, anchor in culture; skipping steps undermines sustainment.

Lewin's model: unfreeze, change, refreeze; refreezing is where process standards, training, and performance metrics are institutionalized.

ADKAR (Prosci) is an individual-change model: Awareness, Desire, Knowledge, Ability, Reinforcement; the change succeeds only when each element is achieved per affected group.

Resistance analysis: classify by source (information deficit, competence gap, incentive conflict, identity threat) because the intervention differs - communication, training, incentive redesign, or participation.

Stakeholder mapping uses power/interest quadrants: high power-high interest manage closely; high power-low interest keep satisfied; low power-high interest keep informed; low power-low interest monitor.

Readiness assessment dimensions: sponsorship commitment, capacity for change alongside operations, history of change success, and clarity of the future-state role impact.

Communication planning rule: message content, audience segment, channel, frequency, and sender are specified per stakeholder group; line managers deliver role-specific impact messages.

Adoption measurement: use behavioral indicators (system usage, workaround frequency, exception rate) rather than satisfaction surveys alone; lagging business KPIs confirm realization later.

Training design follows task analysis of the to-be process; competence is verified by assessment or supervised execution, not attendance.

Three lines model: first line owns and manages risk in the process; second line provides compliance and risk oversight; third line is internal audit, independent of management.

Control types: preventive (approval, segregation of duties, mandatory field), detective (reconciliation, exception report), corrective (escalation, remediation); design versus operating effectiveness are tested separately.

Segregation of duties rule: no single role should combine initiation, authorization, custody, and recording of a transaction; conflicts are detected by a rules matrix over role assignments.

Process compliance by design embeds controls in the workflow (gateway checks, four-eyes approval, audit trail) rather than relying on after-the-fact inspection.

Regulatory examples relevant to process design: SOX internal control over financial reporting, GDPR purpose limitation and data minimization, Basel operational risk, ISO 9001 process approach and documented information.

Evidence and audit trail: each control needs a defined evidence artifact, retention period, and reviewer; a control without retrievable evidence is not auditable.

Risk assessment formula: risk exposure = likelihood x impact; residual risk is assessed after existing controls and compared to the defined risk appetite.

Assurance mapping avoids duplication: link each control objective to the assurance provider (management self-assessment, compliance function, internal audit) and record coverage gaps.

Lean seven wastes: overproduction, waiting, transport, over-processing, inventory, motion, defects; cycle time reduction targets waiting and handoffs first.

Little's Law: average work in process = throughput x average cycle time (WIP = TH x CT); to halve cycle time at constant throughput, halve WIP.

Six Sigma DMAIC: define, measure, analyze, improve, control; process capability indices Cp = (USL - LSL) / 6 sigma and Cpk = min(USL - mean, mean - LSL) / 3 sigma.

A sigma level of 6 corresponds to 3.4 defects per million opportunities; DPMO = (defects / (units x opportunities per unit)) x 1,000,000.

Theory of Constraints: identify the constraint, exploit it, subordinate everything else, elevate it, then repeat; improving a non-constraint does not increase throughput.

Process mining event-log perspectives: control-flow (conformance and discovery), organizational (handover networks), case (variants), and time (bottlenecks); conformance checking compares log to model via fitness and precision.

Variants analysis: the share of cases following the standard path indicates process standardization; high variant counts often signal unclear rules or missing system support.

BPM lifecycle (Dumas et al.): process identification, discovery, analysis, redesign, implementation, monitoring and controlling; redesign patterns include elimination, parallelization, specialization, and automation.

Automation decision rule: automate tasks that are high-volume, rule-based, and stable; keep judgment-intensive or low-volume variants manual until standardization is proven.