Core idea · 6 min read
Your systems record what happened and say what the plan is. Something still has to decide.
At midnight the ERP knows exactly what sits in every warehouse. The S&OP plan says what the business agreed to aim for. Neither answers the question the COO gets at 8 a.m.: a key customer wants a fifth of next quarter's volume a month early. Do we say yes, and what does it cost if the supplier is late?
Three layers, three jobs
Each layer answers a different question.
▤
System of record: what is true
ERP, ledgers, warehouse and order systems. Exact, audited and backward-looking: it can tell you inventory at midnight, not what to do about it.
ERPLedgersOrders
▦
System of planning: what the plan says
Demand, supply and financial planning, coordinated through S&OP or IBP. Forward-looking and essential, built around an agreed forecast and each function's plan.
DemandSupplyFinance
◆
Decision layer: what to commit
Reads from both, keeps uncertainty as ranges, judges choices against one enterprise objective, and hands decisions back to the systems that execute them.
CommitmentsProtectionTiming
The gap
Between what happened and what was planned sits a question neither answers.
Given everything that could happen next, which commitments should we make now, which should stay open, and how much protection is worth buying?
The planning layer answers inside one agreed future, largely one function at a time. The decision layer exists for the questions that cut across functions and futures.
Side by side
Three layers, compared.
System of record
System of planning
Decision layer
Question it answers
What is true right now?
What do we intend to do?
What should we commit, protect and leave open?
Time it looks at
The past and the present
One agreed future
The range of plausible futures
Uncertainty
Records what happened
Collapses it into a forecast
Keeps it as ranges and prices it
Whose objective
Accounting accuracy
Each function's plan
One enterprise objective
What it keeps
Every transaction
The approved plan
Each decision and the run behind it
Why above, not inside
A decision that helps one function and hurts another is not a good decision.
Planning is organized by function, each with its own objective. Judging a commitment across service, profit, cash and risk needs a vantage point above all of them.
Nothing is ripped out. Your record stays your record and your planning tools stay your planning tools. The decision layer connects to them through APIs and file exchange, decides, and hands the decision back.
What the decision layer carries
Four ideas make it more than another planning module.
⊕
Integrated
Reads across the functional plans and judges every choice against economic profit (EVA), not each function's target.
Explore integrated →≈
Resilient
Keeps demand, yields, lead times and costs as ranges, and chooses the plan and its protection together.
Explore resilient →◎
Autonomous within bounds
Lets the plan continue when a change is inside its bounds, and reopens only the affected decisions when it is not.
Explore autonomous within bounds →∑
Compounding
Keeps a record of decisions, not just transactions, so the next call starts from what the last one taught.
Explore compounding →Common questions
What the decision layer changes, and what it leaves alone.
Do we have to replace our planning system?
No. S&OP and IBP stay the system of planning. The decision layer adds the executive questions above them: what to commit, what to protect and when to reopen a decision.
How is this different from adding agents to our planning?
Automation of a single-number plan produce faster answers on the same assumptions. The decision layer changes the assumptions: ranges instead of one forecast, one enterprise objective instead of functional targets, and bounds that say when to act.
Who owns it?
Leadership. The Decision Policy sets the objective, how protective to be and who approves, and leadership’s rules set the limits. Planners and partners work inside both.
What does it need from our systems?
Transaction history, open orders and the current plans. VYAN connects through APIs and file exchange and learns from that history how each driver has actually behaved.
Next
See where your next big commitment would sit.
Bring one decision that cuts across functions and work through it with us.