Net Supply Ratio Dashboard¶

Monitoring dashboard — instantiates Sustainment-Reach Alignment

Shows, live, what fraction of dispatched support actually reaches the front once the line's own costs are paid — and where along the line it is leaking.

A gross view of logistics flatters everyone: dispatch a hundred units, report a hundred units sent. Net Supply Ratio Dashboard ignores what leaves the base and reports what arrives — the ratio of support that lands usefully at the front to the support committed, after the line has taken its own cut for transport, guarding, coordination, spoilage, and rework. Its defining move is to make that subtraction continuous and visible: a single live figure (net delivered ÷ committed) broken out segment by segment, so a ratio quietly sliding toward zero is caught while it is still a trend rather than a collapse. It measures; it does not decide — the number it publishes is what the gates, ladders, and reviews around it act on.

Example¶

A relief agency is trucking supplies to towns cut off by a regional flood. On paper the pipeline looks healthy — warehouses dispatch roughly 500 pallets a day. The Net Supply Ratio Dashboard tells a different story: of every pallet committed, only about 60% is reaching the forward distribution points. Crucially, it localizes the loss instead of just flagging it — a washed-out bridge is forcing a ≈200 km detour that burns fuel and hours (transport tax), a transfer depot is spoiling perishables held too long (spoilage), and one corridor needs armed escort that ties up two trucks per convoy (guarding tax). Each segment shows its own ratio, so the leak is attributable, not mysterious.

When the escorted corridor's ratio drifts under ≈0.4, the dashboard's trend line makes the crossover visible days before that corridor would be consuming more than it delivers — early enough for the surrounding decisions to reroute or throttle rather than pour more trucks into a line that is eating them.

How it works¶

Meter both ends. Instrument dispatch at the base and useful receipt at the front, and treat the ratio between them — not the dispatch figure — as the headline number.
Decompose the loss. Attribute the gap to named line taxes (transport, guarding, coordination, spoilage, rework) per segment, so the ratio is diagnosable rather than just alarming.
Trend, don't snapshot. Plot the ratio over time against the crossover line (where net delivery reaches zero), so a slide shows up as slope, not just level.

It is the net and the per-segment attribution that separate this from a plain throughput monitor: a throughput monitor says how much moved; this says how much survived the line, and where it died.

Tuning parameters¶

Denominator choice (dispatched vs. committed vs. capacity) — whether the base is what left the base, what was promised, or what could be sent. Widening it makes the ratio harsher but more honest about idle capacity.
"Useful receipt" bar — how strictly arrival counts: in the door, in usable condition, or actually consumed at the front. A stricter bar catches spoilage and rework the loose bar hides.
Segment granularity — one end-to-end ratio versus a ratio per leg. Finer granularity localizes leaks but needs more instrumentation.
Refresh latency — real-time telemetry versus daily rollup. Faster refresh catches fast leaks but adds noise and cost.
Alert band — the ratio (and slope) at which it escalates. Set near the crossover to catch culmination early; set too tight and it cries wolf.

When it helps, and when it misleads¶

Its strength is that it kills the gross-dispatch illusion and turns "the line feels strained" into an attributable, trending number everything downstream can hang a decision on — the closest thing reach has to a fuel gauge. Its military cousin is the tooth-to-tail ratio, the balance between fighting strength at the front and the support tail behind it.^[1]

A dashboard measures only what is instrumented, so un-metered taxes — a corridor's political cost, a partner's goodwill burning down — read as zero and flatter the ratio. The classic misuse is to tune the metric until it looks green: loosening the "useful receipt" bar or the denominator to report a comfortable number, which is running the instrument backwards to justify continued advance. The discipline is to fix the definitions before the numbers get political, and to treat an un-attributable loss as a measurement gap to close, not a rounding error.

How it implements the components¶

Net Supply Ratio Dashboard realizes the measurement side of the archetype — the components an instrument can fill:

net_delivery_metric — its headline output: support that lands usefully at the front over support committed, after line taxes.
line_health_monitor — the per-segment decomposition is a continuous read on where along the line delivery is degrading.

It does not set the stop-line at the crossover (crossover_threshold, front_pace_gate) — that is Reach Limit Gate; nor does it project how fast reach is consuming sustainment over time (reach_cost_model, reach_review_cadence) — that is Support Burn-Rate Review. It supplies the live readings those act on.

Instantiates: Sustainment-Reach Alignment — the dashboard is its primary sensor.
Consumes: the line topology from Relay Hub Network and Line-of-Support Capacity Model, to attribute losses to the right segment.
Sibling mechanisms: Reach Limit Gate · Support Burn-Rate Review · Priority Supply Ladder · Relay Hub Network · Support Line Postmortem · Advance Pause & Consolidation Window · Forward Staging Cache · Front Rescope Playbook · Lead-Time Stress Simulation · Line-of-Support Capacity Model · Local Sourcing & Repair Protocol

Notes¶

The dashboard is a sensor, not a controller: a green ratio does not mean "advance," it means "the line is currently paying its way." Acting on it belongs to the gate, ladder, and review. Watch too for step effects — a single bridge going out can flip a whole segment's ratio overnight, so a healthy level is not the same as a robust one.

References¶

[1] Tooth-to-tail ratio — the balance between a force's combat ("tooth") strength at the front and the logistics and support ("tail") behind it; a standing measure of how much of a force's mass is consumed sustaining its own reach. ↩