Alerts and impact

Your priorities ranked, the impact already modelled.

Ori, the planner’s assistant, hands your planners only the decisions that matter, ranked by impact, explains each one and follows up with the people who know. Accept a decision and Horizon carries it through: the plan updated and written back to the ERP, with owner and reasoning logged.

TodayThis weekLog
Ori
Example · today’s decisions for Lena, key planner
1
Move the Retailer North launch75,000 units to weeks 12–13Why: CRM · delivery moved to week 12
AcceptAccepted
2
Plan first fills for 12 new stores11,520 units, weeks 21–22Why: Email · Retailer East opens 12 stores
Accept
3
Add the heatwave uplift+18% ice cream, weeks 27–28Why: Weather · heatwave, Spain and Italy
Accept
Supply plan updatedWritten back to the ERPOwner and reasoning logged
Ranked

by impact, so the key decisions come first, each with its reason

ImpactReasonSource
3steps

carried through after one accept

PlanERPLog
Every

decision logged with its owner and reasoning

OwnerReasoningDate
1Language models readCRM updates and customer emailsSales chats and tendersPOS, weather and market data2Engines decide the numbersHZN-1: the baselineScenario engine: the impactOptimisers: the optimal plan3People own the large callsOri ranks the decisions by impactPlanners accept, change or rejectOwner and reasoning loggedWithin agreed boundaries, Horizon acts on its own and carries the plan through
Whodoes what
Language models readCRM, emails, sales chats, POS, weather and market data
Engines decide the numbersHZN-1, the Scenario engine and the optimisers
People own the large callsRanked by Ori, with owner and reasoning logged
Agreed boundariesWithin them, Horizon acts on its own

What you can do

Fewer alerts, better decisions.

Ranked priorities

The decisions that matter, ranked by impact

  • Ori, the planner’s assistant, hands your planners only the decisions that matter, ranked by impact.
  • Each decision comes with the impact already modelled and the signal behind it.
  • Everything else is already in the baseline, so nobody has to work through a list of alerts.
Priorities · today
Example
RANKED BY IMPACT, UNITS1 · Move the Retailer North launch75,000CRM2 · Heatwave uplift, ice cream+18%Weather3 · First fills, 12 new stores11,520EmailALREADY IN THE BASELINE40 more signals read today, no decision needed

Explained

Every number, with a reason

  • Start from the baseline forecast, adjust it with each live input, weighed by its track record, then anchor the result back toward the plan.
  • Every step from the baseline to the final number is visible.
  • Ori explains each priority and follows up with the people who know.
From plan to final number
Illustrative example
SKU-4471 · DC_01 TO RETAILER_NORTHBaseline forecast6.2KOrder book+380POS signal+240Store sell-out−150Customer update+310Sales update+270Pure signal read7.3KAnchor back toward plan−90Final forecast7.2KOri asked Sales North to confirm the customer updateConfirmed

Carried through

Accept once, Horizon carries it through

  • Your planners make the key decisions; Horizon does the rest, and carries it through.
  • The plan updated and written back to the ERP, with owner and reasoning logged.
  • Within agreed boundaries, Horizon acts on its own; people own the large calls.
Decision log · today
Example
Accepted by LenaMove the Retailer North launch09:14Demand plan updated75,000 units to weeks 12–1309:14Supply plan updatedProduction and transfers rebalanced09:15Written back to the ERPPlanned orders updated09:16Owner and reasoning loggedLena · CRM: delivery moved to week 1209:16WITHIN AGREED BOUNDARIESSmall changes carried through on their own, each one logged

FAQ

Alerts and impact, answered.

What does Ori do?

Ori is the planner’s assistant. It ranks the priorities, explains them, and follows up with the people who know, so your planners only make the key decisions.

How are alerts ranked?

By impact. Each decision comes with the impact already modelled and the signal behind it, and only the decisions that change the plan reach your planners; the rest is already in the baseline.

Can I see why a number changed?

Yes. Every number comes with a reason: from the baseline forecast, each live input moves the forecast by what it is worth, weighed by its track record, and the result is anchored back toward the plan. Every step is visible.

What happens when I accept a decision?

Horizon carries it through: the plan is updated and written back to the ERP, with owner and reasoning logged.

Does Horizon change the plan on its own?

Within agreed boundaries, yes. Language models read, engines decide the numbers, and people own the large calls.

How fast can we start?

Start with Horizon Instant: your ERP connected and real demand planning on your own data, up and running in less than 24 hours. Add Deep Sensing and Ori when you’re ready.

See your priorities ranked on your own data.

Horizon Instant: up and running in less than 24 hours.