Twelve roles, two layers

Twelve roles. Two layers. Internal stakeholders govern and operate VYAN — they set policy, review decisions, consume outputs, own the integration. External stakeholders collaborate with VYAN through bidirectional workflows — they contribute data, receive better signals, and benefit from the predictability VYAN's policy discipline creates.

The external layer matters as much as the internal one. VYAN's planning quality is bounded by the quality of its inputs, and the highest-value inputs come from outside the buyer's four walls — customer forward demand with confidence intervals, supplier request-commit signals before POs are placed, 3PL lane-level capacity and rate intelligence, contract manufacturer schedule visibility. Treating external partners as data sources alone is the old planning paradigm. Treating them as collaboration partners — participating intelligences in the planning loop — is what VYAN enables.

Each role gets its own node. A reader who's a CSCO can skip to 7.1; someone leading organizational change management for a deployment reads all twelve. Each node is self-contained, with the before/after framing for that specific role's work, the new rhythm of their week, and their relationships across the stakeholder map. The chapter's deliberately written so the prose a planner shares with their CFO does the work of cross-role translation on its own.