OCEB 2 Business Advanced key terms

An OMG standard that structures an enterprise's ends (goals, objectives) and means (strategies, tactics, business rules) so that process decisions can be traced back to explicit intent and assessed for consistency.

The documented, verifiable link between each process or process change and the enterprise goal or objective it serves, allowing prioritization, impact analysis, and later proof that intended value was realized.

A stable statement of what the enterprise can do, expressed independently of how it is performed, used to map processes to strategy and to decide where capability gaps require process redesign or investment.

The end-to-end sequence of activities that delivers a defined outcome to a customer, used to distinguish customer-visible value creation from supporting processes and to expose handoffs, delays, and waste.

The governed practice of inventorying all processes, classifying them by importance and maturity, and deciding where to invest, consolidate, retire, or leave unchanged within finite resources.

A structured scoring instrument that ranks candidate processes by criteria such as strategic impact, pain level, risk exposure, and feasibility, producing a defensible order of work for the BPM program.

A decision document quantifying expected benefits, costs, risks, and assumptions of a process initiative, including how benefits will be measured, so sponsors can approve, defer, or reject the investment.

The discipline of defining benefit measures before implementation and tracking them after go-live, so claimed improvements are confirmed, corrective action is triggered, and lessons feed the next cycle.

A comparison of the financial and non-financial gains attributable to a process change against its total cost, including design, technology, training, transition, and ongoing operating expense.

A staged framework describing increasing capability in process governance, modeling, measurement, and culture, used to set realistic improvement targets and select the next practice to institutionalize.

A central team providing methods, standards, tooling, coaching, and quality assurance to distributed process work, balancing economies of scale against the responsiveness of business-unit ownership.

The accountable role for a process's end-to-end design, performance, and change decisions, holding authority across functional boundaries and answerable for targets rather than for daily task execution.

The decision rights, roles, policies, and escalation paths that determine who may approve process changes, who monitors performance, and how conflicts between functions or programs are resolved.

A cross-functional body that reviews proposed process changes for impact on systems, compliance, training, and other processes, and authorizes or rejects them according to agreed criteria.

A process spanning from an initial trigger or customer request to a delivered outcome, crossing organizational units, whose performance cannot be optimized by any single department acting alone.

Local improvement of one department's activities that degrades overall flow, typically through larger batches, buffer stock, or handoffs shifted to another unit, producing gains locally and losses globally.

A BPMN model containing two or more pools, using message flows between pools to show how independent participants coordinate, while sequence flows remain confined within each participant's own process.

Swimlane constructs where a pool represents a participant or organization and lanes partition a pool by role or unit, clarifying responsibility without changing the underlying sequence of activities.

In BPMN, a dashed connector showing communication between separate participants in different pools; it cannot connect activities inside a single pool, which use sequence flows instead.

A model of expected interactions among multiple participants, showing ordered message exchanges and responsibilities from a global viewpoint rather than the internal steps of any single party.

A BPMN subprocess embedded in a process or subprocess that is not connected by sequence flow and is triggered by an event, enabling interruption or non-interruption of the enclosing scope.

An event attached to the edge of an activity that catches a trigger while that activity runs, either interrupting it or, when non-interrupting, spawning parallel paths without cancelling the original work.

A BPMN mechanism that reverses the effect of a completed activity when a later step fails, invoked through a compensation event and used to model business-level undo across long-running processes.

A design approach for distributed transactions in which each step has a compensating action, so partial failure is resolved by executing compensations in reverse order instead of relying on two-phase commit.

A deviation from the intended path caused by missing data, rule violation, system failure, or unusual input, requiring explicit handling, ownership, and measurement rather than undocumented workaround.

Examination of the most frequent, trouble-free execution route to establish baseline timing and cost, used as a starting point before analyzing variants, exceptions, and their relative frequencies.

Discovery and analysis of actual process behavior from system event logs, producing observed process models, variant frequencies, and bottlenecks that can be compared against the designed model.

Comparison of logged real-world behavior with a normative process model to identify deviations, quantify their frequency, and judge whether they represent violations, necessary variants, or model error.

A defined, repeatable measure of process behavior such as cycle time, first-pass yield, or cost per case, with an owner, target, data source, and review cadence tied to business objectives.

The total elapsed time from a customer request or trigger to delivery of the outcome, including waiting, queueing, and rework, as distinct from the hands-on work time within the process.

The cumulative cost of failures, rework, scrap, complaints, and inspection incurred because processes do not produce correct output first time, used to justify prevention-oriented improvement.

The percentage of cases completed correctly without rework, loop-back, or exception handling, a measure that exposes hidden effort that average cost or throughput figures tend to conceal.

A waste-reduction approach that identifies customer value, maps the value stream, removes non-value-adding steps and waiting, and pulls work at the pace of customer demand.

A data-driven improvement cycle of Define, Measure, Analyze, Improve, and Control, aimed at reducing variation and defects in existing processes and locking in gains through control plans.

An improvement approach holding that throughput is limited by a single bottleneck, so effort should identify that constraint, exploit and subordinate other work to it, then elevate and re-evaluate it.

Executable modeling of a process with arrival rates, resource capacities, and processing times to predict queue lengths, cycle times, and cost under alternative designs before committing to change.

The structured set of activities that prepares affected people for a process change, addresses resistance, aligns incentives and skills, and sustains new behavior after the project ends.

Systematic identification of parties affected by or able to influence a process change, mapping their interests, influence, and likely stance to plan tailored engagement and communication.

A diagnostic of an organization's capacity to absorb a process change, covering leadership commitment, capability, workload, past change history, and cultural receptiveness, performed before launch.

Active, visible support from senior leaders who legitimize a process change, resolve cross-functional conflicts, allocate resources, and reinforce expected behavior through decisions and communication.

The pattern over time in which user groups accept a new process, moving from innovators and early adopters to the majority and laggards, guiding where reinforcement effort is most needed.

Embedding regulatory and policy requirements into process design and controls from the outset, so evidence is generated as a by-product of normal execution rather than through later manual checks.

A safeguard built into a process, such as segregation of duties, authorization limits, or reconciliation, intended to prevent, detect, or correct errors and irregularities affecting process outputs.

A control principle that separates incompatible responsibilities, such as initiating, approving, and recording a transaction, so no single person can complete a sensitive action unchecked.

A retained, attributable record of who did what and when during process execution, sufficient to reconstruct a case, demonstrate compliance to an auditor, and support investigation of incidents.

Assessment of the consequences of a proposed process change across systems, data, roles, controls, training, contracts, and dependent processes, performed before approval to avoid unintended breakage.

A statement that governs or constrains business behavior, such as an eligibility condition or approval threshold, ideally defined once and applied consistently across processes and systems.

An OMG standard for modeling repeatable decisions separately from process flow, using decision requirements diagrams and decision tables so logic can be verified, reused, and changed independently.

A design goal in which a case is completed automatically from end to end without manual intervention, requiring clean data, encoded decision rules, and explicit handling of exceptions.

A named, reusable solution to a recurring control-flow or resource problem in process design, such as deferred choice or milestone, catalogued to support consistent modeling decisions.

A low-risk, low-cost process improvement deliverable in a short timeframe, used to build credibility and momentum for a BPM program before larger, slower structural changes begin.