Analyses
Dataleo Insight · 2026-08-26· Supply Chain AI

o9, Kinaxis, OMP and Anaplan: Four Different Visions for AI-Driven Supply Chain Planning

Why the next APS battle may be less about AI agents than the decision architecture beneath them.

Supply chain planning vendors have reached an unusual point of apparent agreement. o9 has APEX. Kinaxis has Maestro Agents and a broader operational orchestration architecture. OMP has UnisonIQ and Decision-Centric Planning. Anaplan is building toward an Agentic Enterprise.

Read the announcements quickly and the strategies can look similar. They are not. A plausible answer is not necessarily a feasible plan.

The more useful lens is decision architecture: the layer that defines the context, constraints, objectives, authority and execution rules around a decision. Gartner's 2026 Critical Capabilities framework reinforces this distinction by assessing AI Planning/Decision Automation alongside Constraint-Based Supply Planning, Workflow Orchestration, Scenario Management & Financial Impact and Decision-Centric Planning. AI does not replace planning architecture; it has to operate through it.

The market map in one minute

o9 → operating model + enterprise knowledge
Kinaxis → concurrency + composable operational orchestration
OMP → decision situations + governance + optimization
Anaplan → deterministic cross-functional decision infrastructure, progressively extended with agents

Four vendors, four architectural bets

o9: enterprise knowledge as the operating model

o9's APEX model—Agile, Adaptive, Autonomous Planning & Execution—connects decisions across functions and planning horizons through the Digital Brain. Its Enterprise Knowledge Graph provides a machine-readable representation of relationships, rules and institutional knowledge, while its neuro-symbolic direction combines language and statistical AI with symbolic enterprise representations.

The architectural bet is clear: make enterprise knowledge machine-readable, then give agents access to it.

APEX's autonomy should not be read as removing human judgment. o9 describes progressive autonomy: AI can automate routine planning and execution-horizon decisions within defined governance guardrails, while humans retain strategy, intent, policy, oversight and higher-stakes judgment. Post-Game Analytics adds a learning loop by evaluating outcomes against plans and assumptions.

Dataleo question: Who maintains the decision knowledge when policies, constraints or decision rights change?

The failure mode is a sophisticated agent reasoning over an outdated operating model. Decision knowledge becomes a new category of master data.

Kinaxis: composable orchestration grounded in concurrency

Kinaxis retains a distinctive foundation: concurrency. Maestro continuously synchronizes signals, plans and decisions across demand, inventory, capacity, production and other constraints, giving AI a live model for understanding end-to-end consequences.

But the current strategy is broader than “the agent inside the live planning model.” Kinaxis is expanding toward operational orchestration: a composable architecture spanning data, semantic intelligence, decisioning, AI runtime, workflows, orchestration, governance and learning. These building blocks can enhance planning within Maestro but are also intended to coordinate actions across enterprise systems, workflows, teams and functions.

Maestro Agent Studio, reusable agent skills and orchestration therefore sit on top of concurrency rather than replacing it. The ambition is to connect the decision to what happens next—even when execution crosses the conventional APS boundary.

Dataleo question: Can Kinaxis preserve the constraint-awareness and synchronized context that make concurrency powerful when orchestration extends across systems Maestro does not own?

OMP: governed decision situations and optimization

OMP begins with the decision. Decision-Centric Planning aims to continuously identify decision situations, prepare scenarios and trigger action rather than waiting for a periodic planning cycle. UnisonIQ connects agents and generative AI with established optimization engines.

Its architecture formalizes a path from strategy → preparation → execution. Strategy defines priorities and decision logic; preparation continuously simulates scenarios and pre-evaluates options; execution is triggered when events cross defined thresholds. Routine decisions can automate while exceptions escalate with context.

Governance is therefore not an approval button added after an AI recommendation. Priorities, thresholds, escalation logic and who decides what and when become part of the operating design.

OMP's implied division of labor
LLMs interpret and orchestrate → agents monitor and coordinate → optimization engines solve → scenario models expose trade-offs → humans validate consequential decisions.

Dataleo question: Can agentic planning reduce the number of decisions humans need to make, rather than produce better analysis for more decisions?

Anaplan: building toward deterministic agentic infrastructure

Anaplan's stated vision extends beyond Supply Chain. The Agentic Enterprise is presented as decision infrastructure connecting finance, Supply Chain, HR and sales through a shared computational and data foundation that combines deterministic calculations, probabilistic AI, connected data and workflows.

But this is a roadmap and architectural direction, not four equally mature agentic suites already in production. Anaplan's June 2026 announcement puts the first skills-based agents around the office of the CFO later in 2026. The Supply Chain, HR and Sales vision matters strategically, but should not be confused with uniform current availability.

The architectural proposition remains interesting: probabilistic intelligence can detect or estimate a change, while deterministic models preserve business relationships and financial identities when evaluating consequences. This could matter as agents cross operational and financial planning boundaries.

Dataleo question: Where does connected enterprise planning stop and detailed Supply Chain constraint logic begin—and will future agents have enough operational context to cross that boundary safely?

The real battleground: how each platform represents context

All four vendors agree that a useful Supply Chain agent needs context. They disagree on what that context fundamentally is.

  • o9: Enterprise Knowledge Graph + Digital Brain.
  • Kinaxis: synchronized concurrent planning model extended through semantic intelligence and operational orchestration.
  • OMP: decision situation + scenarios + priorities + thresholds + specialized optimization.
  • Anaplan: connected deterministic enterprise model enriched by probabilistic AI and workflows.

This may become one of the defining architecture choices in next-generation APS. Agents will become easier to build. Foundation models will improve. Natural-language interfaces will commoditize. What remains difficult is encoding the physics of the decision: dependencies, constraints, objectives, trade-offs, policies, financial consequences and organizational authority.

Mature planning vendors have an advantage here: they already possess years—sometimes decades—of Supply Chain decision logic. The race is not simply to put AI into APS. It is to decide whether APS logic becomes the substrate for agents, one tool used by agents, or is reorganized around a new agentic operating model.

The autonomy trap

Enterprise enthusiasm is running ahead of readiness. McKinsey's 2025 Supply Chain survey found that 75% of respondents are planning, blueprinting or piloting AI use cases, but only 19% report deployment at scale. Demand forecasting, inventory optimization and supply planning are among the leading generative-AI use cases.

The hard step is not moving from chatbot to agent. It is moving from recommendation to delegated decision rights.

An agent that summarizes an exception is low risk.
An agent that reallocates supply is not.
An agent that commits inventory, changes production priorities or triggers procurement has crossed into delegated operational authority.

At that point architecture must answer: What objective is being optimized? Which constraints are hard? Whose policy wins when service, working capital and margin conflict? What confidence permits autonomous action? When must the agent escalate? Who owns the outcome? Can the decision be reconstructed later?

These are not generic AI-governance questions. They are planning-system design questions.

The Dataleo 6-question test for agentic planning

  1. What gives the agent its world model?
    A knowledge graph, concurrent planning model, optimization model and multidimensional enterprise model are not interchangeable.

  2. Can the agent distinguish plausible from feasible?
    Native access to constraints and optimization becomes critical once recommendations affect real supply, capacity or inventory.

  3. Does the agent interrogate the plan or change the decision workflow?
    The larger opportunity is eliminating unnecessary analysis and coordination, not making dashboards conversational.

  4. What learns?
    Distinguish improvement of an ML model from learning across forecast error, overrides, scenario choices and realized outcomes.

  5. Where is authority encoded?
    Human-in-the-loop cannot mean an approval button after every recommendation. Mature autonomy requires explicit rules for what agents may decide, execute and escalate.

  6. Can decisions cross functional boundaries?
    High-value Supply Chain decisions are often simultaneously commercial, operational and financial.

Dataleo perspective: AI will commoditize intelligence before decision architecture

The important development is not that APS vendors now have agents. It is that agents are forcing vendors to expose what their platforms really believe a decision is.

o9 emphasizes enterprise knowledge and a learning operating model. Kinaxis combines concurrency with composable operational orchestration. OMP emphasizes governed decision situations, scenarios and specialized optimization. Anaplan is building toward deterministic cross-functional decision infrastructure augmented by probabilistic intelligence and role-based agents.

None is intrinsically the universal winner. But they expose a useful rule for buyers:

Do not evaluate the intelligence of the agent before evaluating the decision architecture underneath it.

The generative layer will improve rapidly and become increasingly interchangeable. The hard problem remains the layer that knows whether a recommendation is feasible, valuable, authorized and consistent with the rest of the enterprise.

The future of Supply Chain AI may therefore look less like replacing APS with agents and more like turning the APS into an executable decision model that agents can safely operate.

When the agent is wrong, what part of the architecture knows it?

Sources and further reading

Related Dataleo Radar: o9 Solutions · Kinaxis · OMP · Anaplan · agentic AI