Book contents · 9 chapters
Chapter 3 · How VYAN is shaped

Composability — VYAN runs any solver

VYAN owns the stochastic envelope. Any deterministic solver — ours, yours, your incumbent's — runs inside it.

VYAN owns the stochastic envelope. The solver in the middle is pluggable. That sentence is the architectural move that turns VYAN from a planning vendor into a System of Intelligence above every planning vendor.

Concretely: VYAN's workspace constructs an iteration set — a fan of deterministic scenarios sampled from the joint distribution of past variabilities and future risks. Each iteration is a coherent future ("Brent at P85 AND FX at the corresponding copula draw AND demand at P75 AND the Taiwan supplier risk firing at Week 5"). VYAN hands each iteration to a solver as an ordinary deterministic planning problem. The solver returns a deterministic plan. VYAN catches the answer, repeats across the iteration set, and reconstructs the probability histograms from the deterministic results.

The solver never sees uncertainty. It does what every deterministic planner already knows how to do — solve one scenario — and hands back one plan. That means any deterministic solver becomes a stochastic solver when VYAN orchestrates it. SAP MRP doesn't know what a distribution is — doesn't need to. VYAN sends MRP one deterministic scenario at a time, MRP runs its batch, VYAN reads the result, repeats. SAP MRP, a 1990s-architecture batch planner, suddenly produces P10/P50/P90 ranges. The solver stays dumb about uncertainty; VYAN supplies the intelligence.

This is real today, not roadmap. VYAN already runs two solvers internally behind one interface — the heuristics engine and the optimizer engine. Both implement the same "scenario in, plan out" contract. Third-party solvers extend a proven internal pattern; they're not a new concept. PVA already arbitrates between the internal heuristics and optimizer engines today on the same iteration set.

The proprietary IP sits on both sides of the solver — iteration construction (modeling past variabilities, modeling future risks, building the joint sample) is VYAN, and histogram assembly plus PVA computation is VYAN. The solver in the middle never sees the stochastic intelligence, only the deterministic problem. Composability is safe to advertise precisely because the solver runs inside two layers of VYAN IP it never sees.

VYAN's answer

VYAN owns the envelope on both sides. The solver runs inside it, knowing nothing about uncertainty. Any solution provider with a good deterministic solver can advertise their solver through VYAN.

Not 100% clear on a term?Glossary →