Simulate delivery flow digital twin

What it's for

Models delivery as a queue network with finite WIP, rework and stochastic service — which is what a delivery pipeline is, and what a burndown chart cannot represent.

Upgrades What-If from scalar multipliers to a delivery-system digital twin that identifies bottlenecks and compares operating policies.

What you give it

Inputs split into evidence read from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.

{
  "arrival_rate_per_day": 1,
  "backlog_cost_per_item_day": 3,
  "horizon_days": 60,
  "policies": [
    {
      "id": "add_reviewer",
      "stage_overrides": [
        {
          "additional_daily_cost": 18,
          "servers": 2,
          "stage_id": "review"
        }
      ]
    }
  ],
  "seed": 9,
  "simulations": 50,
  "sla_days": 8,
  "stages": [
    {
      "id": "build",
      "server_cost_per_day": 15,
      "servers": 2,
      "service_median_days": 0.4,
      "service_sigma": 0.25
    },
    {
      "id": "review",
      "rework_probability": 0.08,
      "rework_to": "build",
      "server_cost_per_day": 20,
      "servers": 1,
      "service_median_days": 1.2,
      "service_sigma": 0.35
    },
    {
      "id": "deploy",
      "server_cost_per_day": 10,
      "servers": 1,
      "service_median_days": 0.2,
      "service_sigma": 0.2
    }
  ],

What you get back

This is the actual output of running the example above — computed by the same function the platform calls, not an illustration.

{
  "assumptions": [
    "Arrival and service distributions must be calibrated from comparable work; policy results are conditional on those inputs.",
    "A WIP limit holds excess demand in an intake backlog, so cycle time and backlog must be interpreted together.",
    "The simulator models aggregate delivery capacity, not individual productivity."
  ],
  "method": "delivery_flow_discrete_event_twin_v1",
  "model": {
    "arrival_process": "poisson",
    "horizon_days": 60,
    "paired_random_numbers": true,
    "service_time_family": "lognormal",
    "simulations_per_policy": 50,
    "warmup_days": 15
  },
  "policies": [
    {
      "average_intake_backlog": {
        "mean": 0,
        "p05": 0,
        "p50": 0,
        "p95": 0
      },
      "average_wip": {
        "mean": 2.65,
        "p05": 1.69,
        "p50": 2.45,
        "p95": 4.39
      },
      "bottleneck_stage": "review",
      "cycle_time_days": {
        "p50": 2.364,
        "p75": 3.201,
        "p90": 4.311
      },
      "ending_intake_backlog": {
        "mean": 0,
        "p05": 0,
        "p50": 0,
        "p95": 0
      },
      "ending_wip": {
        "mean": 2.3,
        "p05": 0,

How it works

Network & dependency analysis — Trace how load, failure and knowledge propagate through a graph of teams, services or components.

1. 1 Simulate delivery as a network of finite queues with stochastic arrivals, lognormal service, rework, WIP limits, and policy economics.
2. 2 Evaluate the method-specific diagnostics and gates returned by the function, then abstain unless the declared decision clears them under locally governed thresholds.

Before you trust it

Every tool in the catalog ships with the conditions under which its answer is meaningful — and the conditions under which it should abstain instead of guessing.

Calibrating it to your org

Calibration workflow

1. 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
2. 2 Build a tenant-scoped historical cohort using only information available before each prediction or decision; preserve zero periods, censoring, assignment probabilities, and unresolved outcomes when the method requires them.
3. 3 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
4. 4 Validate on later time windows or held-out aggregate units at the deployment grain, against a simple baseline and the function-specific validation strategy.
5. 5 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
6. 6 Monitor realized outcomes, data drift, coverage, and decision regret; recalibrate at a governed cadence or after a detected regime/definition change, never merely because a stakeholder dislikes the result.

Call it from your AI

You don't wire up 388 tools in your MCP client. The GitRevio MCP server exposes 18 tools, three of which let an agent search the catalog, read a tool's schema, and run it — so the assistant finds this one on its own.

gitrevio_capabilities_search
  { "q": "simulate delivery as a network of" }
  → finds "simulate_delivery_flow_digital_twin"

gitrevio_capability_describe
  { "capability_id": "simulate_delivery_flow_digital_twin" }
  → returns the input schema and agent guidance shown on this page

gitrevio_capability_run
  { "capability_id": "simulate_delivery_flow_digital_twin", "arguments": { ... } }
  → returns the result shown above

Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.

Related tools

See every tool in Capacity, staffing & flow →