Reference Implementation — Supply Chain Disruption Graph

Reference Implementation — Supply Chain Disruption Graph

Impact propagation from supplier outages to SKUs, orders, and regions with bounded path semantics.

Why it matters

Spreadsheet lineage breaks under multi-tier dependencies. Graph traversal is the shortest path to operational impact clarity.

Going deeper

Minimum viable disruption graph:

Supplier -> Component -> Assembly -> SKU -> Order/Region. Add lead-time and risk properties to relationships, then evaluate weighted paths for realistic impact scoring.

A supply-chain graph is tracing which dominoes fall when one supplier tips over. A spreadsheet lists the dominoes; only a graph walks the chain — supplier → component → assembly → SKU → order/region — to tell you, in bounded hops, exactly which customers feel a single factory fire.

• Table-native lineage. Multi-tier impact needs recursive joins that explode. Fix: typed, bounded traversals.
• Unbounded impact traversal. Walks the whole graph. Fix: bound hops and relationship types to real dependency depth.
• No lead-time/risk weights. Impact is unranked. Fix: weight edges and evaluate weighted paths.