D-12
Network & Resilience Review
A three-view network review pattern over authored scenario versions, route flows, resource assumptions, dependency evidence, qualified alternatives, and owned mitigations, with no optimizer or probability inference.
There is a reference build of this pattern: the Network & Resilience Review dashboard in the showcase renders it over frozen, simulated data — not a live client system.
See the working synthetic reference build. Its route flows are authored modeled cases, not optimizer output.
What it answers
Which supplied scenario serves more of the same demand, whether its routes fit authored supply and capacity, and which dependency records carry explicit qualification or mitigation evidence.
It does not choose a network, predict a disruption, or infer sole-source status, recovery probability, or mitigation effectiveness.
The wireframe
Network review with scenario control, five measures, route comparison, capacity register, and dependency evidence
Layout basis
- L-04 Tabbed Views — separates baseline assumptions, like-for-like scenario comparison, and dependency evidence while preserving scenario context
- L-03 Master-Detail / Drill-Down — keeps routes and resources attached to the assumptions and evidence that govern them
- Scenario context — one immutable version and baseline govern every comparison.
- Headline row — served demand stays distinct from leg workload, capacity, and cost.
- Route register — ordered legs preserve continuity and material conservation.
- Dependency register — qualification and action states remain evidence, never a composite score.
The scenario model
The route fact carries one authored end-to-end flow. Ordered legs join to directed arcs for workload, cost, and transit without multiplying served demand. Scenario versions pin the baseline and horizon.
Grain scenario version x product x authored route
Stored components
- flow_quantity
- quantity_uom
- source_node_id
- market_node_id
- scenario_id
- scenario_version
Foreign keys
- → dim_network_node
- → dim_network_arc
- → dim_product
- → dim_dependency_evidence
- scenario_id
- version
- kind
- baseline_ref
- horizon_start
- horizon_end
- authored_at
Alternatives pin an immutable baseline so later edits cannot rewrite the comparison.
- arc_id
- from_node_id
- to_node_id
- mode
Directed arcs join through ordered route legs; path continuity is validated.
- dependency_id
- evidence_kind
- effective_from
- effective_to
- provenance
Dependency, qualification, and mitigation claims retain status, coverage dates, and provenance.
- node_id
- label
- kind
- handling_capacity_ref
Source, hub, and market roles are explicit; handling coverage is never assumed.
- product_id
- quantity_uom
- workload_factor_ref
Quantity and workload conversion versions prevent cross-unit arithmetic.
Measures and states
| Measure | Formula | Additivity | Note |
|---|---|---|---|
| Served demand | sum end-to-end route flow once at each destination | Additive | Never multiply by route-leg count. |
| Unmet demand | max(authored demand - served demand, 0) | Additive | Zero is evidenced; missing demand is unavailable. |
| Leg workload | sum route flow x ordered leg count after exact workload conversion | Additive | A transport workload measure, not served demand. |
| Resource utilization components | modeled workload and authored capacity in the same workload UOM | Non-additive | Publish components and feasibility status; an absent capacity leaves feasibility unknown. |
| Modeled cost | sum variable workload cost + fixed cost once per used arc | Additive | One currency per total; no inferred exchange rate. |
| Modeled transit | sum authored duration across ordered route legs | Additive | A modeled duration, never a probability or observed recovery outcome. |
An evidenced zero is shown as zero. Missing capacity, cost, transit, qualification, or status evidence remains unavailable and cannot produce a feasible or covered claim.
Implementation notes
- Validate ordered route continuity, source supply, market demand, resource capacity, and intermediate material conservation.
- Use workload conversions only when product, input unit, output unit, and factor version match exactly.
- Compare served-demand deltas only over identical horizons and demand populations.
- Keep currencies separate and fixed cost applied once per used arc.
Source and renderer mapping
Supply canonical product, node, arc, supply, demand and route identities; retain the versioned capacity, cost, transit and dependency evidence behind each scenario. A customer source adapter must document its extraction path, units, history and reconciliation. A BI adapter must reproduce the same populations, withheld states and scenario controls. Neither adapter is established by this synthetic reference build.