Skip to content

Travel-Time Matrix

Artifact — instantiates Central Reserve Redeployment

Tabulates the full response time from each candidate reserve location to each front under normal, degraded, and surge conditions, turning 'centrally positioned' from a claim on a map into a checkable number.

The whole premise of a central reserve is that it sits on interior lines — shorter effective paths to several fronts than those fronts have to each other or to outside help. Travel-Time Matrix is the artifact that tests whether that premise is actually true. It lays candidate reserve locations down one axis and fronts along the other, and fills each cell with the full time to respond — not straight-line distance, but dispatch, turnout, travel, and arrival — computed separately for normal, degraded, and surge conditions. Its defining move is to measure time, not geometry: a location that looks central on a map can be slow in practice, so the matrix is what converts "we're well placed" into "from here we reach five of six fronts faster than their next-best support, except when the river bridge is down." It supplies the reach numbers; it does not itself decide where anything goes.

Example

A regional ambulance service holds two surge units as its mobile reserve and must choose which station to base them at. The obvious pick is the geographically central station downtown. Before committing, the planners build a Travel-Time Matrix: candidate stations down the side, the six catchment districts across the top, each cell the call-to-arrival time — and each computed three ways, for a quiet Tuesday, for weekday rush hour, and for a mass-casualty surge that clogs the arterials. The downtown station wins on the quiet-Tuesday numbers, as expected. But under rush-hour and surge conditions its times to three districts blow out, because every route funnels across one choke-point bridge. A slightly off-center depot near a ring road reaches four of the six districts faster across all three regimes. The matrix makes the decision on evidence: central on the map was not central in time, and the depot is where the reserve should live.

How it works

What distinguishes this artifact from a generic distance table is three commitments:

  • Full response time, not travel time. Each cell includes the fixed overheads — notification, turnout, loading, and access at the far end — because those often dominate and they are exactly what a straight-line map omits.
  • Multiple condition regimes. The same origin–destination pair is timed under normal, degraded (weather, closures, congestion), and surge conditions, so the matrix shows not just reach but the fragility of that reach.[1]
  • The viability test. With the grid filled, the central-position question becomes answerable: is there a location whose interior-line times to the front set genuinely beat each front's next-best alternative — and does that advantage survive the degraded regime, or only exist on a calm day?

Tuning parameters

  • Condition regimes modeled — how many scenarios and how adverse. More regimes expose the fragility that decides real reach, but each costs data and modeling effort.
  • Time definition — travel-only versus full door-to-door. Travel-only is cheap but systematically flatters central sites; full response time is honest and usually less flattering.
  • Candidate granularity — a handful of real sites versus a fine location grid. Finer search can find a materially better position but multiplies the matrix and invites false precision.
  • Cross-front aggregation — score a candidate by its worst front, its average, or a priority-weighted blend. Worst-case scoring buys resilience; weighted scoring optimizes expected performance and can hide a weak front.
  • Refresh trigger — computed once versus recomputed when roads, demand, or hub locations change. The matrix is perishable, and a stale one quietly lies.

When it helps, and when it misleads

Its strength is that it kills the "looks central" illusion and makes the interior-lines claim — the load-bearing assumption of the whole archetype — something you can check rather than assert. By carrying degraded and surge regimes it surfaces the fragile-reach problem (a position that works only in calm conditions) before it is discovered mid-crisis.

Its limits are those of any estimate. The matrix is only as good as its travel model, and a tidy grid of numbers can lend false confidence to times that were themselves guessed. A single averaged cell can mask the one regime in which the position collapses. And it is easily run backwards — computed under only the flattering normal-condition regime to ratify a location already chosen. The discipline is to always carry the worst credible regime through, treat the matrix as perishable and re-run it when the network changes, and remember that it estimates reach on paper: only a live rehearsal proves the reserve can truly concentrate under real handoffs.

How it implements the components

Travel-Time Matrix fills the path-estimation subset — the reach numbers the rest of the machinery reasons over:

  • interior_path_time_model — the matrix is this model: full response times from each candidate reserve position to each front, across conditions.
  • central_position_viability_criterion — the filled grid answers the criterion directly: whether some position's interior-line times genuinely beat each front's alternatives, and whether that edge survives degradation.

It does not display live front or route state (Multi-Front Dispatch Board), turn these times into allocation decisions (Capacity-Aware Dispatch Optimizer), or prove viability under real handoffs — the Sequential Concentration Drill validates live what this only estimates on paper.

Notes

The matrix and the Sequential Concentration Drill answer the same question at two levels of proof: the matrix estimates interior-line reach from a model, cheaply and for many candidate positions; the drill demonstrates it once, expensively, under real setup and handoff friction. Estimate first to choose the position; rehearse to confirm the estimate was not optimistic.

References

[1] An origin–destination (travel-time) matrix is a standard transport-planning artifact tabulating the time or cost to move between each origin and destination. Computing it under several network conditions rather than one is what lets it speak to the resilience of a position, not just its average convenience. ↩