Supply Chain Disruption Simulations

This dataset provides detailed synthetic scenarios of supply chain disruptions, including impacts on logistics network nodes, delivery times, inventory levels, rerouting events, and financial consequences. It enables robust analysis and modeling of supply chain resilience strategies for risk mitigation and operational planning.

  • last updated 20 Aug 2025
  • by GoMask
The brief that made it

Supply chain resilience modeling and risk assessment

Sample rows

preview · 8 of 200 rows · all 18 columns
scenario_idstringdisruption_typestringinventory_level_afterfloatrerouting_event_occurredbooleannetwork_node_typestringscenario_namestringdisruption_start_datedatedisruption_end_datedateaffected_regionstringnetwork_node_idstringinventory_level_beforefloataverage_delivery_time_beforefloataverage_delivery_time_afterfloatfinancial_impactfloatresilience_scorefloatcreated_atdatetimescenario_descriptionstringrerouting_strategystring
SCN001natural_disaster7921truesupplierFlooding at Supplier Hub2023-03-142023-03-28Mississippi DeltaSUP-MSD-0012743221.281.720845000.222023-03-01T10:31:12Severe flooding impacted the main supplier hub, halting inbound shipments and disrupting regional supply chains.Alternate supplier sourcing from Tennessee region
SCN002equipment_failure14890falsewarehouseEquipment Malfunction Warehouse East2022-10-052022-10-07Newark, NJWARE-NWK-0021532013.617.8370000.982022-09-28T15:22:17Unexpected conveyor belt failure at the eastern warehouse caused minor delays in outbound shipments.blank
SCN003labor_strike272230trueportPort Labor Strike - Los Angeles2023-07-112023-07-21Los Angeles, CAPORT-LA-00328654032.564.310800000.432023-07-01T08:05:32A labor strike at the Los Angeles port led to long delays and rerouting of maritime shipments.Temporary rerouting to Seattle port with expedited handling
SCN004cyber_attack6542trueretailerCyber Attack on Retail Node2023-11-022023-11-09Houston, TXRTL-HOU-00498118.241.321400000.112023-10-27T18:44:09Retail operations were disrupted by ransomware, severely impacting order fulfillment and inventory management.Manual processing and use of expedited third-party shippers
SCN005transport_delay563850falsedistribution_centerRoad Closure Delays Distribution Center2022-08-162022-08-19Chicago, ILDC-CHI-00558120018.925.6780000.852022-08-11T09:22:33Major highway closure led to delays at the Chicago distribution center, impacting regional deliveries.blank
SCN006natural_disaster12045truesupplierSupplier Region Tornado2023-04-042023-04-20Little Rock, ARSUP-LRK-0063180025.398.131250000.182023-03-28T14:13:45A tornado swept through the Arkansas supplier region, halting production and causing severe shortages.Emergency sourcing from Oklahoma facilities
SCN007equipment_failure473680falsedistribution_centerDistribution Center Power Outage2022-12-012022-12-02Denver, CODC-DEN-00748093019.425.1145000.992022-11-25T11:35:01Power outage at Denver DC temporarily delayed outbound shipments to retailers.blank
SCN008cyber_attack6045trueretailerRetailer Payment System Breach2023-08-152023-08-22Brooklyn, NYRTL-BKN-008100416.765.247000000.072023-08-10T14:39:20Cyber breach at a New York retailer delayed order processing and required manual intervention.Manual fulfillment and delivery via alternate carriers

What the 200 rows show

from the 200-row sample

Labor_strike (disruption type) stands out: mean inventory_level_after is 244,441, against 53,304 for the rest.

  • 62%rerouting_event_occurred = true
  • 13,415median inventory_level_after
  • 30,832median inventory_level_before
  • 16.8median average_delivery_time_before
  • 35.3median average_delivery_time_after
  • 520,000median financial_impact
Mean inventory_level_after by disruption_type200 rows
0200k400k25,107natur…55 rows244.4klabor…24 rows80,217equip…36 rows21,769cyber…25 rows114.1ktrans…28 rows42,917other32 rows
inventory_level_after200 rows, in bands of 100k
07515014135152610300k600kinventory_level_after →

Median 13,415, from 0.0 to 563,850.

network_node_type200 rows · 5 values
  1. supplier54
  2. distribution_center49
  3. port38
  4. warehouse30
  5. retailer29
18 columns by typefrom the column list below
  • string 8
  • float 6
  • date 2
  • datetime 1
  • boolean 1

Columns

18 columns in four groups
blueprint · 18 columns
columntypedescriptionexample
Text 8 columns
scenario_idstringUnique identifier for each disruption simulation scenariouniqueSCN001
scenario_namestringDescriptive name of the disruption scenarioFlooding at Supplier Hub
scenario_descriptionstringDetailed description of the disruption scenario, including context and objectivesoptionalSevere flooding impacted …
disruption_typestringType of disruption (e.g., natural disaster, labor strike, equipment failure)6 valuesnatural_disaster
affected_regionstringGeographic region or location impacted by the disruptionMississippi Delta
network_node_idstringIdentifier for the affected logistics network node (e.g., warehouse, port, distribution center)SUP-MSD-001
network_node_typestringType of logistics network node (e.g., warehouse, port, distribution_center, supplier)6 valuessupplier
rerouting_strategystringDescription of rerouting strategy used (e.g., alternate route, expedited shipping, supplier change)optionalAlternate supplier sourci…
Numbers 6 columns
inventory_level_beforefloatInventory level at the network node before the disruption (in units)0 or more27432
inventory_level_afterfloatInventory level at the network node after the disruption (in units)0 or more7921
average_delivery_time_beforefloatAverage delivery time to customers before the disruption (in hours)0 or more21.2
average_delivery_time_afterfloatAverage delivery time to customers after the disruption (in hours)0 or more81.7
financial_impactfloatEstimated financial impact of the disruption (in USD)0 or more · optional2084500
resilience_scorefloatCalculated resilience score for the scenario (0-1 scale, higher is better)0 to 1 · optional0.22
Dates and times 3 columns
disruption_start_datedateDate when the disruption begins2023-03-14
disruption_end_datedateDate when the disruption endsoptional2023-03-28
created_atdatetimeTimestamp when the simulation scenario was created2023-03-01T10:31:12
True or false 1 column
rerouting_event_occurredbooleanIndicates if rerouting was required due to the disruptiontrue

Use it for

  • rerouting even…62%123 of 200 rowsmean inventory level …25.1knatu…244.4klabo…80.2kequi…21.8kcybe…

    A logistics dashboard

    The rerouting_event_occurred rate, inventory_level_after by disruption_type and a breakdown of network_node_type. Excel, Power BI or Tableau.

  • Why do the 24 labor_strike rows have a mean inventory_level_after of 244,441?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable scenarios with scenario_name, scenario_description and disruption_type to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 18 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset200 rows18 columns
Yours1,000 rows18 columnsaffected_region: UK only

blueprint · supply-chain-disruption-simulations

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 18 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Region, route, and carrier specified
  • Disruption type and duration detailed
  • Inventory delays calculated
  • Reroute events and affected shipments logged
  • Seasonal spikes incorporated
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
supply-chain-disruption-simulations

What should your data show?

Preview 20 rows free
No signup. No card.