Skip to content

302 templates · page 3 of 4

Operations & Ops diagram templates

Incident response, hiring, procurement, support, triage.

  • Pareto — Rail Delay Minutes by Cause

    Delay minutes attributed by cause across a commuter route's autumn period against the spring one, computing that 5 of 11 causes carry 80.9% of 34,500 minutes and that leaf-fall adhesion displaced signalling power supply from the vital few.

    Pareto chart
  • RBD — Potable Water Pumping Station

    Annual availability of a district pumping station with a two-of-three duty pump set, showing the 11 kV incomer as the weakest block on site and the rising main as an unavoidable series element.

    Reliability block diagram
  • Queueing Network — Mass Vaccination Centre

    Saturday clinic taking 240 arrivals an hour through registration, clinical screening, twelve vaccination booths and a seventy-seat observation bay, solving to a 20-minute stay with screening, not the booths, as the constraint.

    Queueing network
  • Queueing Network — Container Terminal Night Shift

    Ninety-six trucks an hour through gate, yard crane, a three-desk customs inspection bay with only ten places and four quay cranes, showing the gate rather than the quayside sitting at the 80% ceiling.

    Queueing network
  • Swimlane — Sepsis Six Pathway

    Cross-functional flow of the one-hour sepsis bundle across triage nurse, emergency doctor, pathology and pharmacy, including the escalation loop when lactate returns above four.

    Swimlane process
  • Kanban — Hospital Estates Maintenance

    Reactive and statutory estates work for an acute site, with a WIP-limited works column, permit-to-work waiting state and the ventilation and medical-gas jobs that carry statutory deadlines.

    Kanban board
  • PERT — Refinery Unit Turnaround

    Shutdown network for a catalytic reformer turnaround from feed-out and nitrogen purge through catalyst change and vessel inspection to reinstatement, with the reactor internals on the critical path.

    PERT / CPM network
  • Fishbone — Short-Notice Train Cancellations

    Root-cause analysis of short-notice cancellations on a commuter route, grouped by traincrew, fleet, infrastructure, planning, information and external causes.

    Fishbone (Ishikawa)
  • Cold-Chain Temperature Excursion (Vaccine Depot)

    How a depot quarantines, assesses and dispositions a vaccine pallet after a 2-8 C excursion alarm.

    Mermaid
  • Refinery Turnaround Schedule (Crude Unit)

    A 24-day crude unit shutdown from feed cut to feed-in, with inspection findings driving the repair scope.

    Mermaid
  • ATM Cash Replenishment Cycle (PlantUML)

    Forecast-driven ATM replenishment with a two-person cassette swap and a cash difference investigation branch.

    PlantUML
  • Airframe Serviceability States (PlantUML)

    A narrow-body aircraft's serviceability states including deferred defects under the MEL, AOG recovery and long-term storage.

    PlantUML
  • Network Operations Topology (D2)

    Access, metro aggregation and core layers of a fixed-line network with the alarm path from telemetry to a field truck roll.

    D2
  • Primary Substation and Feeders (D2)

    A 132/33 kV primary substation with twin transformers, a normally open bus coupler and four feeders including a dual-fed hospital.

    D2
  • Medicine Distribution and Verification (Graphviz)

    Active ingredient through QP release, wholesalers and pharmacy dispense, with serialisation decommissioning and the recall return path.

    Graphviz (DOT)
  • Contact Centre Forecast vs Actual (Plotly)

    Half-hourly offered calls against forecast with the rostered agent line on a second axis, exposing the mid-morning under-staffing.

    Plotly
  • Midnight Bed Occupancy by Ward (Vega-Lite)

    A week of midnight occupied beds stacked by ward, showing the Monday and Tuesday peak that drives escalation-area opening.

    Vega-Lite
  • On-Time In-Full by Carrier (Vega-Lite)

    Ninety days of OTIF by carrier with bars turning red below the 92 percent contractual floor that triggers a service review.

    Vega-Lite
  • Two-Week-Wait Referral Pathway (Sankey)

    A quarter of lower gastrointestinal urgent referrals splitting between straight-to-test and clinic-first, down to 164 cancers diagnosed.

    Sankey flow
  • Inbound Goods Receipt Discrepancy (Swimlane)

    What happens between carrier, receiving, buyer and accounts payable when a delivery does not match the advance shipping notice.

    Swimlane process
  • Planned Substation Outage Board (Kanban)

    A week-32 substation outage board with WIP limits, a blocked relay upgrade and the two critical-path tasks tagged.

    Kanban board
  • Ward Nursing Workforce (System Dynamics)

    Trainee, registered and bank staffing stocks with the reinforcing loop where vacancies raise workload, which raises turnover.

    System dynamics (stock & flow)
  • Excalidraw — Incident Timeline Sketch for a Post-Mortem

    The timeline a post-mortem starts from, drawn on a whiteboard: from the deploy that shrank the database connection pool at 13:02 to recovery at 13:51, with the alert, page, diagnosis and rollback in between and the phase durations underneath — 7, 5, 17 and 20 minutes, adding to 49 minutes of customer impact. Illustrative values.

    Excalidraw
  • Word Cloud — Contributing Factors Across 38 Incident Post-Mortems

    Contributing factors tagged in 38 blameless post-mortems for an online retailer's platform over 2025: 137 tags, with "config change" (17) and "missing alert" (15) the most common. Most incidents carry three or more factors — the cloud is a prompt for the reliability review, not a root cause. Illustrative values.

    Word Cloud
  • Flame Graph — Django Checkout Endpoint (py-spy, wall clock)

    A 2,800-sample py-spy profile of POST /checkout/ under load: 45.8% of wall time is waiting on PostgreSQL, and the single widest tower is the promotions engine re-querying the database for every basket line (23.4%) — an N+1 the fix for which is one prefetch. The payment gateway call (19.1%) is network wait the service cannot shorten. Illustrative values.

    Flame Graph
  • On-Call Pages per Day — Payments SRE Rota, 2025

    Every page that woke the payments platform's primary on-call engineer in 2025: 569 pages over 252 days, with release days (Tuesday and Thursday) visibly darker, the ledger-migration incident week in mid-March peaking at 8 pages on Monday 17 March, the Black Friday surge and the quiet of the December change freeze. Illustrative values.

    Calendar Heatmap
  • Marimekko — Hospital Operating Expenditure by Division and Cost Type

    A £600m acute hospital revenue budget split by division (column width, % of the budget) and cost type (share within each division): pay is about £360m (60%) of the whole, surgery's supplies share is more than double medicine's, and the corporate column, which includes estates, is the only one dominated by non-pay. Illustrative values.

    Marimekko / Mosaic
  • Waterfall — Scope 1 and 2 Emissions Bridge, 2019 Baseline to 2025

    A manufacturer's scope 1 and 2 emissions from an 18,400 tCO₂e 2019 baseline to 13,060 tCO₂e in 2025 (-29.0%): four decarbonisation projects remove 9,270 t, while production growth and a new site add back 3,930 t — the honest bridge that separates what the projects achieved from what growth gave back. Market-based scope 2. Illustrative values.

    Waterfall Chart
  • Waterfall — Elective Waiting-List Bridge Over a Financial Year

    Why a hospital's referral-to-treatment waiting list moved from 41,850 to 42,700 pathways over the year: 52,300 referrals arrived, 48,300 pathways were closed by treatment and 3,150 by validation, so activity ran 4,000 short of demand before validation and the list still grew. The operational planning view of demand against capacity. Illustrative values.

    Waterfall Chart
  • Bullet Graphs — Emergency Department Performance Scorecard

    Five monthly measures for a hospital emergency department, each phrased so higher is better and drawn against its standard: 71.8% of patients seen within four hours against a 78% target, 84% of ambulance handovers inside 30 minutes, triage within 15 minutes for 91%, and 96.4% of patients not leaving before being seen. Illustrative values.

    Bullet / KPI
  • Bullet Graphs — IT Service Desk Monthly KPIs

    An IT service desk's month on one page: first-contact resolution 68% against a 75% target, 93.1% of incidents resolved within SLA, CSAT 4.4 out of 5, 88% of calls answered within 60 seconds and 92% knowledge-article coverage of resolved tickets — every measure phrased so that more is better. Illustrative values.

    Bullet / KPI
  • Security — STRIDE risk matrix

    A typed threat model rendered as a risk matrix. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Reliability — FMEA risk ranking

    A typed FMEA worksheet whose risk priority numbers are computed. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Supply — single-origin coffee chain

    A typed supply network rendered as a flow map. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Quality — process capability (Cp / Cpk)

    Process capability study whose indices are computed from the subgroups that were actually measured, not copied off the SPC terminal. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Quality — measurement system analysis (gauge R&R)

    Gauge R&R for the instrument the capability study depends on — because a Cpk computed with an unfit gauge is a number about the gauge. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Engineering — 2^k factorial design of experiments

    A 2^3 full factorial on a laser weld, with the main effects and the interaction computed FROM the run matrix by selector rather than typed out of the analysis package. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Reliability — growth model (Crow-AMSAA)

    Reliability growth on a fielded fleet, fitted as a non-homogeneous Poisson process with a power-law intensity — Crow-AMSAA, IEC 61710. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Reliability — Weibull life data with suspensions

    Weibull life data analysis on a small population with censoring — seven failures and five units still running. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Operations — time study with confidence intervals

    A direct time study that reports how precise it is, which is the part normally missing. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Supply — inventory policy (EOQ, safety stock, service level)

    An order policy stated as the four numbers that actually run it: how much to order, when to order it, how much to hold against variability, and what that costs per year. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Reliability — FMECA with computed criticality

    A FMECA, not an FMEA: every mode carries a criticality computed from the failure rate of the item it sits on, as well as the risk priority number the team scored. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Systems — availability of a redundant supply

    Availability of a redundant essential supply, as a reliability block diagram with the arithmetic attached to the blocks. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Operations — energy balance for a production line

    An energy balance over one hour of steady production, written so that the closure error is visible rather than absorbed. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Supply — Cold Chain Despatch

    A cold-chain despatch cascade, from pallets released at the plant to pallets signed for at the hospital dock. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Supply — Manufacturing Yield Cascade

    A production yield cascade for one week of assembly. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Reliability — Field Failure Cohort

    A field-failure cohort for one hardware fleet: units shipped, then registered, then followed for twenty-four months, with every unit that left the cohort attributed to a named failure mode. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Security — Alert Triage Funnel

    A detection-to-containment funnel for one quarter, with the threat model the detections were written from sitting beside it. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Reliability — design FMEA for a medical device

    Design FMEA for a volumetric infusion pump: failure modes ranked by risk priority number (severity × occurrence × detection), each mitigation's residual RPN recomputed from its target ratings, linked to the ISO 14971 risk file. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Security — STRIDE threat model for an LLM agent

    STRIDE threat model for a customer-support LLM agent that reads tickets and can call refund and account tools: each threat placed on a 5 × 5 likelihood-by-impact matrix, with the controls that mitigate it and their coverage. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Supply — battery pack supply and service network

    Supply network for an electric-vehicle battery pack from component suppliers through pack assembly to the vehicle line and the service network, with lead time and logistics cost on every link and capacity at every node. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Research workspace threat model

    Review cross-project access, shared-device sessions, export links and bulk imports in a research workspace, and who owns each control; ordinal scores and coverage are illustrative assumptions. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Webhook ingestion threat model

    Review forged, replayed, out-of-order and flooded events in webhook ingestion, and who owns each control; ordinal scores and coverage are illustrative assumptions. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • AI tool-execution threat model

    Review injected instructions, cross-tenant retrieval, unapproved actions and unbounded recursion in AI tool execution, and who owns each control; ordinal scores and coverage are illustrative assumptions. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Field data collection threat model

    Review stolen devices, impersonated submissions, tampered offline records and sync overwrites in field data collection, and who owns each control; ordinal scores and coverage are illustrative assumptions. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Operational asset platform threat model

    Review spoofed sensors, command privilege abuse, telemetry gaps and gateway overload on an asset platform, and who owns each control; ordinal scores and coverage are illustrative assumptions. Typed FlowScript for threat modelling. Keywords: threat model, STRIDE, risk matrix, security.

    FlowScript
  • Digital asset handover FMEA

    Trace digital asset handover failures, from duplicate identifiers to missing maintenance evidence, from cause to effect and mitigation; compare ordinal risk priorities without interpreting them as probabilities. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Research data release FMEA

    Trace research data release failures, from use outside the permitted purpose to retained sensitive values, from cause to effect and mitigation; compare ordinal risk priorities without interpreting them as probabilities. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Order recovery FMEA

    Trace order recovery failures, from duplicate fulfilment to a false completion message, from cause to effect and mitigation; compare ordinal risk priorities without interpreting them as probabilities. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Assay workflow FMEA

    Trace assay workflow failures, from sample misidentification to pseudoreplication, from cause to effect and mitigation; compare ordinal risk priorities without interpreting them as probabilities. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Service release FMEA

    Trace service release failures, from backward incompatibility to an alert blind spot, from cause to effect and mitigation; compare ordinal risk priorities without interpreting them as probabilities. Typed FlowScript for reliability engineering. Keywords: FMEA, failure mode, RPN, reliability.

    FlowScript
  • Battery recovery and disposition network

    Separate safe triage, qualification for reuse and material recovery destinations. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Recovered construction material network

    Model test and segregation points before assigning recovered components to a new project. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Perishable food rescue network

    Expose quality checks, short handling windows and alternative disposition paths. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Critical spare-parts resilience network

    Compare alternative sourcing and repair loops without claiming the diagram is a logistics optimiser. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Field sample custody network

    Keep custody handovers, archive retention and disposal as distinct routes. Typed FlowScript for supply chains. Keywords: supply chain, logistics, network, supplier.

    FlowScript
  • Availability model — payments API across three AZs

    Reliability block diagram of a regional payments API — Route 53, ALB, 2-of-3 AZ stacks, Aurora storage with a hot-standby writer and a third-party card processor — solving to 99.938% steady-state availability and naming the ALB and the processor as the two blocks that cap it.

    Reliability block diagram
  • Error budget policy — freeze, waiver and window roll

    The error budget policy of a 99.9%/30-day service as a finite state machine — healthy, watch, exhausted, time-boxed VP waiver and window roll — with the guard on every transition, for the SRE and product owner who have to sign it.

    State machine (FSM)
  • Sev-1 paging escalation — Alertmanager to PagerDuty to on-call

    Interaction diagram of a Sev-1 page from Prometheus through Alertmanager and PagerDuty to primary, secondary and manager escalation levels with ack timers, status-page update and resolution, for the engineer who owns the escalation policy.

    Sequence & interaction
  • Emergency change — ECAB approval and back-out

    ITIL emergency change flow across requester, change manager, ECAB, release engineer and service desk, including the reclassification exit, the freeze-window override record, the burn-rate verification gate and the back-out path.

    Swimlane process
  • Order-to-cash with credit check and dunning

    End-to-end O2C collaboration: a purchase order from the customer is validated, credit-checked (with a credit-hold review), confirmed, picked, shipped and invoiced, then cash is applied — or a 30/60/90-day dunning cycle escalates to collections. Three lanes, seven message flows to the customer. Illustrative payment terms.

    BPMN 2.0
  • Procure-to-pay with three-way match

    P2P collaboration from purchase requisition to supplier payment: budget-holder approval, PO issue, goods receipt and invoice receipt in parallel, a three-way match (PO, goods receipt, invoice) with a variance-resolution loop, then payment and remittance. Four lanes and five message flows to the supplier. Illustrative tolerances.

    BPMN 2.0
  • Employee onboarding through probation

    From signed offer to confirmed employment: HRIS record and welcome pack, then right-to-work checks, the manager's 30-60-90 plan, IT accounts and equipment and a desk and badge prepared in parallel, a day-one induction, timer-driven 30-day check-in and an end-of-probation decision. Four lanes and four message flows with the new hire. Illustrative probation length.

    BPMN 2.0
  • ITIL incident management with major-incident path

    ITIL 4 incident management: log and categorise, prioritise by impact × urgency, first-line resolution from the knowledge base, functional escalation to a resolver group with a timer on the resolution target, a separate major-incident path (bridge, stakeholder updates, problem record), and auto-closure if the user does not reply. Illustrative service levels.

    BPMN 2.0
  • Customer support escalation (Tier 1 → Tier 2 → engineering)

    Tiered support with SLA-driven escalation: triage and SLA assignment, Tier 1 troubleshooting with a 2-hour timer that escalates to Tier 2, defect hand-off to engineering for a hotfix, and an event-based wait for the customer to confirm, report that the problem persists (re-opens to Tier 2) or go silent for 5 days. Illustrative SLAs.

    BPMN 2.0
  • Invoice approval with timer escalation

    Accounts-payable invoice approval: capture, duplicate check, GL coding, approver routing from an authority matrix, budget-holder approval guarded by a 3-day interrupting timer boundary event that escalates to the finance manager, rejection back to the supplier, and payment with remittance. Illustrative escalation period.

    BPMN 2.0
  • Hiring collaboration with candidate and screening provider

    Recruitment as a BPMN collaboration: the employer's pool (recruiter, hiring manager, interview panel) exchanges ten message flows with a Candidate pool and a background-screening provider — application, interview invitation, regret and feedback emails, offer and acceptance with a 7-day timer, screening request and report, contract or offer withdrawal. Illustrative offer deadline.

    BPMN 2.0
  • Emergency department patient intake and triage (ESI)

    Clinical intake in an emergency department: arrival registration, nurse triage with vital signs, Emergency Severity Index (ESI) assignment, immediate care for ESI 1–2, full registration and waiting-room monitoring with a timer-driven re-triage loop for ESI 3–5, then clinician assessment and an admit-or-discharge disposition. Illustrative re-triage interval.

    BPMN 2.0
  • Software release with parallel quality gates and canary rollout

    Release pipeline modelled in BPMN: build and sign artefacts, then four quality gates in parallel (integration tests, SAST and dependency scan, regression testing, release notes), a fix-and-rebuild loop, change approval, a canary deployment with a 30-minute bake timer, SLO comparison, and promotion to full traffic or automatic rollback. Illustrative canary settings.

    BPMN 2.0
  • ITIL change enablement (standard, normal and emergency)

    Change enablement per ITIL 4: a request for change is classified as standard (pre-authorised, straight to implementation), normal (impact assessment and CAB authorisation) or emergency (ECAB), then scheduled, implemented with a backout path, and reviewed and closed. A rejection by either board goes back to the requester.

    BPMN 2.0
  • Idempotent checkout and payment recovery

    Models duplicate submissions and uncertain payment outcomes without treating a timeout as a decline. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Provenance-checked artifact promotion

    Keeps the tested artifact digest stable across staging and production promotion. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Incident escalation and stable recovery

    Requires stable observation after recovery and allows regression back to containment. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Inventory reservation, expiry and reconciliation

    Covers reservation timeout and inspection before returned stock becomes available. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Asset hierarchy, work orders and parts

    Connects hierarchical assets with task staffing, consumed parts and independent inspection evidence. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Circular material recovery and quality assurance

    Includes conditional reuse, retesting and residual disposal instead of assuming all recovered materials are reusable. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Graphviz (DOT)
  • Service recovery with severity and entitlement checks

    Combines incident escalation, ordinary support and a user-confirmed recovery loop. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Supplier disruption response and substitution

    Balances stock coverage, qualified substitution, demand allocation and incoming inspection. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.

    Mermaid
  • Tender panel: independent scoring and conflict review

    Combine independently recorded technical scores, commercial review and conflict declarations before award. Preserve reasons and panel evidence. Editable collaboration with role lanes, decisions and independent parallel checks. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Supplier qualification with three independent clearances

    Qualify a supplier only after capacity, financial resilience and integrity checks are complete. A failed clearance initiates documented remediation. Editable collaboration with role lanes, decisions and independent parallel checks. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Relief allocation with needs, stock and safeguarding checks

    Reconcile independently assessed needs, physical stock and safeguarding conditions before approving a distribution plan. Editable collaboration with role lanes, decisions and independent parallel checks. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Accessibility defect resolution with retest loop

    Keep an accessibility issue open until a reproducible workflow passes retest; support a recorded scope decision if correction is not currently viable. Editable collaboration with role lanes, decisions and a correction and resubmission loop. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Invoice dispute with evidence correction and re-review

    Assess disputed invoice lines against delivery and contract evidence, allowing corrected evidence or a recorded unresolved dispute. Editable collaboration with role lanes, decisions and a correction and resubmission loop. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Supplier corrective action under a response deadline

    Receive a supplier corrective-action response under a bounded deadline, then validate effectiveness or move to controlled escalation. Editable collaboration with role lanes, decisions and an interrupting response timer. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Personal data correction request with escalation clock

    Receive requested supporting information within an illustrative internal service clock, then verify correction scope or escalate for a recorded determination. Editable collaboration with role lanes, decisions and an interrupting response timer. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Backorder reservation with customer response or expiry

    Race a customer acceptance message against a reservation expiry so stock is not retained after a missed response. Editable collaboration with role lanes, decisions and a response-versus-expiry event race. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Interview scheduling invitation with response window

    Model an invitation response and timer as competing events, then validate the selected time or release capacity. Editable collaboration with role lanes, decisions and a response-versus-expiry event race. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Service appointment offer with capacity release

    Race a customer's selected appointment against expiry, preserving capacity and confirming accessibility needs before booking. Editable collaboration with role lanes, decisions and a response-versus-expiry event race. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Equipment loan with pickup confirmation expiry

    Hold shared equipment pending borrower confirmation and induction checks; release the hold if no response arrives. Editable collaboration with role lanes, decisions and a response-versus-expiry event race. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0
  • Order reservation with explicit release on payment failure

    Reserve inventory and authorize payment as distinct steps; commit only when both succeed, otherwise reverse reservations and preserve an audit trail. Editable collaboration with role lanes, decisions and explicit rollback activities. Illustrative policy and timing; adapt to local requirements.

    BPMN 2.0