Dependency Concentration Stress Test¶
Simulation method — instantiates Dependency Concentration Control
Simulates the sudden loss, withdrawal, or price shock of the dominant provider or cluster and traces the blast radius — checking whether the substitutes and reserves that look adequate on paper actually absorb it.
A concentration map tells you where reliance is heavy; it doesn't tell you what happens when the heavy node fails. Dependency Concentration Stress Test answers that by removing the dominant provider — or the correlated cluster — in a modelled scenario and following the consequences: how much demand suddenly has nowhere to go, whether the nominal substitutes can actually take that load in the time available, and whether the standby capacity everyone assumed exists is real and reachable. Its defining move is going from static exposure to dynamic consequence: it doesn't measure how concentrated you are, it plays the failure forward and measures how much of it lands where. Where an audit asks "do these alternatives share a root?", the stress test asks "if the biggest one is gone tomorrow, does the fallback hold — and by how much does it fall short?"
Example¶
A regional electric utility relies on one gas supplier for roughly 65% of its generation fuel. On the dependency map that is a known heavy node; the question is what its loss actually costs. The team runs a Dependency Concentration Stress Test: model a mid-winter supply interruption from that supplier and trace it forward. The substitution-feasibility side asks whether the two backup suppliers can physically deliver the shortfall — and the pipeline capacity into the region caps replacement at ≈40% of the gap within the first week, not the 100% the contracts imply. The shadow-capacity side asks whether on-site fuel reserves and demand-response bridge the rest — they cover perhaps three days, not the ten the scenario needs.
The output isn't a colour or an index; it's a sized shortfall with a clock on it: "a one-week loss of the dominant supplier leaves ~35% of critical-season load uncovered after day three." That converts a vague "we're too reliant on them" into a specific gap the rebalancing plan must close — reserves to hold ten days, or a second pipeline path. The exercise is the concentration-risk analogue of the grid's N-1 contingency criterion, which requires a system to survive the loss of any single element.[n1]
How it works¶
- Pick the failure to inject. Choose the shock — outage, withdrawal, price spike, or degradation — and apply it to the dominant provider or to a common-mode cluster that fails together.
- Trace the redistributed load. Follow the demand the failed node was carrying and test where it actually goes, honouring real substitution limits (capacity, lead time, qualification) rather than assuming instantaneous failover.
- Test the reserves against the residual. Check whether standby capacity and buffers cover whatever the substitutes cannot, over the scenario's duration — not just at the first instant.
- Report the sized, time-boxed shortfall. Express the result as the gap that remains and how fast it opens, so remediation attaches to the binding constraint.
Its distinguishing trait is that it exposes optimistic redundancy — substitutes and reserves that pass inspection statically but cannot actually absorb the dominant node's load in the time the failure allows.
Tuning parameters¶
- Shock severity and duration — how large and how long the modelled loss runs. A brief blip flatters reserves; a sustained outage is where concentration actually bites, and short scenarios are the usual way a stress test is quietly rigged to pass.
- Substitution realism — whether substitutes fail over instantly or under real capacity, lead-time, and qualification limits. Realistic limits are the whole point; frictionless failover assumptions hide the shortfall.
- Cluster vs. single — whether you fail one provider or the whole correlated group at once. Testing the cluster reveals the common-mode blast radius a single-node test misses.
- Coverage horizon — how many days of reserve the scenario demands before it counts as survived.
When it helps, and when it misleads¶
Its strength is that it prices the concentration in consequences rather than in exposure: it turns "65% with one supplier" into "35% of load uncovered after three days," which is the number that actually justifies the cost of a second source or a bigger reserve. It also catches the failover that looks fine until the day it has to carry full load.
Its failure modes come from its assumptions. A test is only as honest as its scenario, and the classic misuse is running a mild, short shock you already know the system survives, then citing the pass as proof of resilience. Frictionless substitution assumptions and single-node (rather than cluster) failures both flatter the result. And a stress test values only what it thought to model — an unmodelled correlated shock stays invisible. The discipline that keeps it useful is to size the scenario to a genuinely severe-but-plausible loss, model substitution under real constraints, fail the cluster and not just the name, and revisit as the portfolio changes.
How it implements the components¶
Dependency Concentration Stress Test fills the dynamic-validation side of the archetype — it exercises the fallbacks, it does not inventory, measure, or govern them:
substitution_feasibility_map— it establishes, under load and against real constraints, which substitutes can actually take the dominant node's demand and how much they fall short.shadow_capacity_reserve— it tests whether standby capacity and buffers cover the residual the substitutes cannot, over the scenario's duration.
It does not statically trace which providers share an upstream root (that's Common-Mode Dependency Audit), rehearse the live operational cutover to a backup (that's Substitution Drill), or quantify standing concentration (that's Effective Independent Provider Count); the stress test consumes those and plays the failure forward.
Related¶
- Instantiates: Dependency Concentration Control — the stress test converts standing concentration into a sized, time-boxed shortfall the remediation must close.
- Consumes: Common-Mode Dependency Audit identifies the correlated cluster the test fails as a unit.
- Sibling mechanisms: Common-Mode Dependency Audit · Substitution Drill · Effective Independent Provider Count · Provider Load Split Table · Concentration Cap Policy
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Dependency Concentration Stress Test operates as a bounded trial, probe, simulation, or rehearsal that generates evidence from performance because it simulates the sudden loss, withdrawal, or price shock of the dominant provider or cluster and traces the blast radius — checking whether the substitutes and reserves that look adequate on paper actually absorb it.
Independent corroboration: The frozen evidence defines Dependency Concentration Stress Test as 'Simulates the sudden loss, withdrawal, or price shock of the dominant provider or cluster and traces the blast radius — checking whether the substitutes and reserves that look adequate on paper actually absorb it', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Reliability engineering cohered contingency tests such as N-1 analysis that remove a dominant element and test whether substitutes absorb the load.
Related originating lineages:
- Economics & Finance — Financial stress testing independently modeled dominant-counterparty and correlated-cluster failure.
- Logistics & Supply Chain Management — Supplier-risk practice developed loss-of-source and substitution-capacity scenarios.
Review resolution: Reliability engineering cohered contingency tests such as N-1 analysis that remove a dominant element and test whether substitutes absorb the load. Engineering N-1 testing, financial stress testing, and supply-chain disruption exercises are convergent; the generalized dependency test is an encyclopedia synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The N-1 contingency criterion in power-system reliability requires a network to keep serving load after the loss of any single element — a line, transformer, or generator. Applying the same "survive the loss of one" discipline to a concentrated dependency portfolio, and in the stronger case to a whole correlated cluster, is what this stress test does. ↩