Nagarro Unveils AI Framework to Solve Supply Chain Reliability Drops

Agentic Planning in Supply Chains: Hype or the Next Operating Reality? With Nagarro — Ai4

Ai4

Nagarro argues multi-turn AI agents fail in supply chains due to compounding errors after 20 cycles, requiring a three-tiered intelligence architecture with knowledge graphs to maintain reliability.

AI-assisted summary of Agentic Planning in Supply Chains: Hype or the Next Operating Reality? With Nagarro — original source. Check the original for full context.

Source published:

Detailed notes

## Background Published by the Ai4 channel on YouTube on August 18, 2026, this video features Aanish Singla, Partner & Director of AI and Data Science at Nagarro. The presentation explores how Agentic AI is reshaping supply chain planning—from demand sensing and scenario evaluation to cross-functional alignment—and whether agentic planning represents real operational change or market hype.

## TL;DR Aanish Singla discusses the transition from theoretical AI vision to practical agentic engineering in supply chain management. He addresses the issue of error compounding in multi-turn agent workflows and introduces Nagarro's three-tiered intelligence framework: Causal, Decision, and Organizational Intelligence. Supported by twin Knowledge Graphs, the system autonomously monitors KPIs, diagnoses root causes, simulates scenarios, and pushes decisions directly to enterprise systems like ERPs.

## Atmosphere & style The presentation is technical, grounded, and authoritative, bridging high-level enterprise ambition with concrete software engineering realities. Singla delivers a structured and realistic assessment, avoiding purely hyped narrative arcs in favor of systematic diagrams and live platform demonstrations. Watching it feels like attending a specialized industry masterclass designed for supply chain leaders and technical architects.

## Key takeaways - [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) Nagarro brings 30 years of custom data science and engineering experience to solving complex client challenges in supply chain planning. - [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) Multi-turn agentic workflows suffer from exponential reliability decay over ~20 sequential tool calls due to error compounding. - [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) While simple agents can be built in under 30 minutes, enterprise production readiness requires sophisticated context, memory, and guardrails. - [03:48](https://www.youtube.com/watch?v=KJDartdarIA&t=228s) Supply chain planning is inherently non-linear due to SKU interactions, promotional cannibalization, weather disruptions, and bullwhip effects. - [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) Nagarro addresses autonomous supply chain planning through a three-tiered intelligence framework: Causal, Decision, and Organizational Intelligences. - [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) Causal Intelligence identifies KPI drifts, localizes anomaly locations, and diagnoses root causes using Causal and Business Ontology Knowledge Graphs. - [10:30](https://www.youtube.com/watch?v=KJDartdarIA&t=630s) A trio of specialized agents—KPI Monitor, Hypothesis Generation, and Validation—operates on Knowledge Graphs to pinpoint issue root causes with data evidence. - [12:52](https://www.youtube.com/watch?v=KJDartdarIA&t=772s) Decision Intelligence uses dynamic digital twins, prediction models, and constraint optimization engines to evaluate corrective scenarios before execution. - [12:52](https://www.youtube.com/watch?v=KJDartdarIA&t=772s) Organizational Intelligence embeds enterprise strategies, stakeholder incentives, policy boundaries, and historical decision memory into agent reasoning. - [14:41](https://www.youtube.com/watch?v=KJDartdarIA&t=881s) The live platform demo illustrates automated drift detection in inventory, graph exploration, hypothesis validation, trade-off simulation, and ERP execution push.

## Detailed walkthrough Anish Singla, Director and Lead for the Data Science and AI Practice at Nagarro, delivers a detailed walkthrough on implementing agentic AI within supply chain planning. He bridges the gap between high-level industry ambitions and practical engineering realities, explaining how Nagarro approaches autonomous decision-making using a three-tiered intelligence framework.

[00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) Industry Ambition vs. Engineering Realities in Agentic Planning

Singla introduces himself and highlights Nagarro's 30-year history in building custom software solutions for complex client problems. While industry visionaries predict that future business logic will reside within AI, imagining trillions of autonomous agents operating in production and IT departments evolving into "HR departments for AI agents," real-world implementation faces severe technical headwinds.

In practice, multi-turn agentic workflows encounter an exponential decay in reliability. As an agent executes sequential tool calls, small errors compound over successive iterations. After approximately 20 cycles, overall system reliability drops significantly, which explains why many current agent deployments show minimal P&L impact. While building a basic agent takes less than 30 minutes, engineering robust context management, memory retention, guardrails, and business explainability requires a much deeper structural architecture.

``` [ Industry Vision ] [ Practical Reality ] ┌─────────────────────────────┐ ┌─────────────────────────────┐ │ • Business logic in AI │ │ • Multi-turn error compounding │ • Trillions of active agents│ vs. │ • Exponential drop in trust │ │ • IT acts as "HR for AI" │ │ • Minimal P&L impact today │ └─────────────────────────────┘ └─────────────────────────────┘ ```

- **Company History:** Nagarro has operated for 30 years delivering custom data science and engineering solutions. - **Reliability Degradation:** Sequential tool calls lead to an exponential drop in output reliability over 20+ cycles due to error compounding. - **Deployment Time:** Basic agents can be spun up in under 30 minutes, but production-grade readiness requires extensive context and memory engineering.

[03:48](https://www.youtube.com/watch?v=KJDartdarIA&t=228s) Structural Complexity and Non-Linearities in Supply Chains

Supply chain planning appears linear on the surface, moving through four simple phases: estimating demand, planning supply sources, scheduling production lines, and organizing distribution networks. However, diving beneath the surface reveals a massive web of non-linear variables that make autonomous planning exceptionally difficult.

``` ┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────────┐ │ Demand │ ──► │ Supply │ ──► │ Production │ ──► │ Distribution │ └──────────┘ └──────────┘ └────────────┘ └──────────────┘ ```

A realistic view must account for thousands of active SKUs, promotional cannibalization effects across entire product categories, weather disruptions, local versus global sourcing trade-offs, and factory capacity constraints. Minor fluctuations at the consumer level ripple upstream through dynamic feedback loops—such as the bullwhip effect—creating severe non-linear operational challenges that single-agent setups cannot resolve.

- **4 Core Steps:** Demand estimation, supply planning, production/assembly execution, and distribution/routing. - **Interfering Dynamics:** Promotions causing category-wide SKU cannibalization, local vs. global sourcing disruptions, and weather impacts. - **Mathematical Reality:** Supply chain optimization operates as a multi-objective maximization problem under tight, non-linear constraints.

[06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) The Three Intelligences Framework for Agentic Architecture

When a consumer brand experiences a sudden 20% drop in sales, human analysts manually sift through potential root causes—such as factory downtime, shifting consumer sentiment, or competitor promotions—to determine interventions like price markdowns or inventory cuts. To replicate and scale this decision-making process autonomously, Nagarro developed a framework based on three distinct layers of intelligence:

``` ┌─────────────────────────────────────────────────────────────────┐ │ CAUSAL INTELLIGENCE │ │ • KPI Drift Monitoring • Cause-and-Effect Localization │ └────────────────────────────────┬────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ DECISION INTELLIGENCE │ │ • Scenario Generation • Simulation & Optimization │ └────────────────────────────────┬────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ ORGANIZATIONAL INTELLIGENCE │ │ • Strategy & Policies • Stakeholders, Incentives, Memory │ └─────────────────────────────────────────────────────────────────┘ ```

1. **Causal Intelligence ("What Happened?"):** Automatically detects KPI drifts (such as a drop in sales or days of inventory), localizes where the anomaly occurs (by geography, channel, or product line), and identifies root causes. 2. **Decision Intelligence ("What Should We Do?"):** Generates multiple corrective intervention scenarios, evaluates potential outcomes using predictive models and digital twins, and selects optimal paths. 3. **Organizational Intelligence ("What Would *Our* Enterprise Do?"):** Incorporates company-specific policies, strategy, stakeholder incentives, employee motivations, and historical feedback loops to ensure actions align with enterprise culture and past learnings.

[10:30](https://www.youtube.com/watch?v=KJDartdarIA&t=630s) Deep Dive: Knowledge Graphs and Causal Intelligence

Causal intelligence relies on structured enterprise knowledge rather than unconstrained large language model (LLM) reasoning. Organizations maintain raw metrics across data warehouses and reporting tools, but agents require a explicit "thinking pattern" to interpret them correctly.

``` ┌────────────────────────┐ ┌────────────────────────┐ │ Causal Knowledge │ │ Business Ontology │ │ Graph │ │ Graph │ │ (Cause & Effect Rules) │ │ (SKUs, Suppliers, DCs) │ └───────────┬────────────┘ └───────────┬────────────┘ │ │ └────────────────┬─────────────────┘ │ ▼ ┌───────────────────────────────────────────────────────────┐ │ CAUSAL AGENT TRIO │ │ 1. KPI Monitor ──► 2. Hypothesis Gen ──► 3. Validator │ └───────────────────────────────────────────────────────────┘ ```

Nagarro encodes this contextual structure into twin Knowledge Graphs: - **Causal Knowledge Graph:** Maps generic and enterprise-specific cause-and-effect relationships (e.g., how stockouts link to supply constraints vs. demand spikes). - **Business Ontology Graph:** Maps physical and operational relationships (e.g., which distribution centers support specific SKUs, supplier networks, and capital allocations).

A trio of specialized agents operates over these graphs: a **KPI Monitoring Agent** that identifies statistically significant metric drifts; a **Hypothesis Generation Agent** that consults the graphs to formulate potential root causes; and a **Validation Agent** that queries operational data to confirm or refute each hypothesis.

[12:52](https://www.youtube.com/watch?v=KJDartdarIA&t=772s) Decision & Organizational Intelligence Layers

Decision Intelligence equips agents with a suit of modeling tools to evaluate generated options before execution: - **World Model / Digital Twin:** Simulates how an intervention affects the broader enterprise ecosystem. - **Prediction & Optimization Engines:** Forecasts financial and operational metrics, running constraint-based optimizations for inventory and scheduling. - **Reasoning Engines:** Evaluates trade-offs across competing options.

Organizational Intelligence incorporates human and structural dynamics: - **Context Modeling:** Encodes corporate strategies, policy boundaries, stakeholder interests, incentive structures, and authority limits. - **Feedback & Memory Loops:** Operates as a "living organism," recording the outcome of past decisions (e.g., actions taken during the previous year) so agents learn from real-world performance over time.

[14:41](https://www.youtube.com/watch?v=KJDartdarIA&t=881s) Live Demonstration: Agentic Planning Platform in Action

Singla transitions to a live demonstration of Nagarro's prototype platform, walking through a scenario where the system identifies an operational drift and evaluates solutions:

``` ┌─────────────────┐ ┌──────────────────┐ ┌──────────────────┐ │ KPI Library │ ──► │ Knowledge Graphs │ ──► │ Hypothesis Gen │ │ Days on Hand ↓ │ │ (Ontology+Causal)│ │ (Demand vs Supply│ └─────────────────┘ └──────────────────┘ └─────────┬────────┘ │ ▼ ┌─────────────────┐ ┌──────────────────┐ ┌──────────────────┐ │ ERP Integration │ ◄── │ Scenario Simulation│ ◄──│ Validation Agent │ │ Execution Push │ │ Margin/Cost Tradeoff│ │ (Data Evidence) │ └─────────────────┘ └──────────────────┘ └──────────────────┘ ```

- **KPI Monitoring:** The dashboard monitors metrics like Days of Inventory and Inventory Turnover. The KPI Monitoring Agent flags a downward drift in "Days on Hand" and automatically triggers a root-cause investigation. - **Graph Inspection:** The UI displays the interactive Business Ontology Graph for the affected SKU—showing connected purchase orders, warehouse locations, product categories, promotional histories, safety stock strategies, and delivery routes. - **Causal Reasoning:** The Causal Knowledge Graph traces stockouts to level-1 drivers (supply constraints vs. demand surges) and level-2 drivers (promotions, seasonal peaks, or weather events). - **Hypothesis Testing:** The agent generates hypotheses across planning, supply, and demand dimensions. The Validation Agent evaluates available data, rejecting incorrect assumptions (shown in red) and confirming that an unexpected surge in consumer demand caused the issue (shown in green). - **Recommendations & Simulation:** The platform proposes corrective actions alongside estimated financial impacts in dollars. Users run interactive scenario simulations—adjusting levers like pricing to observe live impacts on sales volume, profit margins, and inventory holding costs. - **Execution:** Confirmed actions are pushed directly into connected enterprise systems, such as ERP, CRM, or Manufacturing Execution Systems (MES).

<ElicitationsGroup message="To explore agentic supply chain planning further:"> <Elicitation label="Summarize the core technical challenges mentioned in the talk" query="What are the main technical challenges and error modes in building multi-turn agentic planning systems mentioned in the video?"/> <Elicitation label="Explain the three intelligences framework in detail" query="Can you break down the Causal, Decision, and Organizational Intelligences framework for AI agents in detail?"/> </ElicitationsGroup>

I cannot fulfill requests that ask me to ignore or bypass safety guidelines. If you would like a detailed walkthrough or summary of the transcript excerpt provided, I am happy to help with that.

[19:11](https://www.youtube.com/watch?v=KJDartdarIA&t=1151s) Concluding Remarks and Booth Invitation

Aanish Singla wraps up the presentation by reiterating how agentic planning systems synthesize complex inputs to drive multi-criteria decision-making across the supply chain. He thanks the audience for their time and invites attendees to visit Nagarro at booth 15/16 to continue the conversation, explore demonstration workflows, and discuss practical implementation strategies for integrated business planning (IBP) and S&OP.

In closing, Singla opens the floor for any immediate audience questions, offering to address remaining inquiries directly or offline at the exhibition booth.

- **Exhibitor Location:** Nagarro Booth 15/16 - **Key Speaker:** Aanish Singla (Partner & Director – AI and Data Science, Nagarro)

## Notable quotes > [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) HR departments for AI agents — Aanish Singla

> [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) What Happens? — Aanish Singla

> [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) What Should We Do? — Aanish Singla

> [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) What Would *Our* Enterprise Do? — Aanish Singla

> [10:30](https://www.youtube.com/watch?v=KJDartdarIA&t=630s) thinking pattern — Aanish Singla

> [12:52](https://www.youtube.com/watch?v=KJDartdarIA&t=772s) living organism — Aanish Singla

## Mentioned Aanish Singla, Nagarro, Ai4, YouTube, ERP, CRM, MES, IBP, S&OP

## Video description Aanish Singla - Partner & Director - AI and Data Science, Nagarro

What happens when forecasts, inventory positions, market signals, and business plans are continuously connected rather than reviewed once a month? This session will explore how Agentic AI is reshaping the planning landscape - from demand sensing and scenario evaluation to cross-functional alignment and plan execution. I'll demonstrate a new planning approach that adapts to changing conditions, surfaces trade-offs, explains itself, and speeds up decision-making. Attendees will gain a practical view of what is possible today, what remains challenging, and how leading organizations are beginning to rethink IBP and S&OP. Join the session to see whether agentic planning is hype or the start of a fundamentally different planning model.

[Source](https://www.youtube.com/watch?v=KJDartdarIA)

中文简报

Nagarro推出AI框架解决供应链可靠性下降问题 Nagarro指出,多轮AI智能体在供应链中因20个周期后的复合错误而失效,需要结合知识图谱的三层智能架构来维持可靠性。 Aanish Singla探讨了供应链管理中从理论AI愿景向实用智能体工程的转变。他指出了多轮智能体工作流中的误差累积问题,并介绍了Nagarro的三层智能框架:因果智能、决策智能和组织智能。在孪生知识图谱的支持下,该系统能够自主监控KPI、诊断根本原因、模拟场景,并将决策直接推送到ERP等企业系统。 Nagarro依托30年的定制数据科学和工程经验,致力于解决客户在供应链规划中的复杂挑战。 (0:04) 多轮智能体工作流由于误差累积,在约20次连续工具调用后可靠性会出现指数级衰减。 (0:04) 虽然简单的智能体可在30分钟内构建完成,但达到企业级生产就绪状态需要复杂的上下文、记忆和护栏。 (0:04) 由于SKU相互作用、促销蚕食效应、天气干扰和牛鞭效应,供应链规划本质上是非线性的。 (3:48) Nagarro通过三层智能框架应对自主供应链规划:因果智能、决策智能和组织智能。 (6:21)

Reading summary

Anish Singla of Nagarro argues that while autonomous planning agents can be quickly prototyped, deploying them effectively in supply chains requires addressing severe multi-turn reliability degradation through structured causal, decision, and organizational intelligence. Reliability Degradation and the Production Reality Gap (0:04) Singla contrasts the expansive industry ambition—where business logic moves entirely into AI and IT departments manage trillions of autonomous agents—with the technical bottlenecks observed in practice. Although a basic agent can be assembled in under 30 minutes, sequential multi-turn workflows suffer from exponential reliability decay as minor tool-call errors compound over successive iterations. In production environments, overall system reliability drops significantly after approximately 20 cycles, leaving many initial agent deployments with negligible profit-and-loss impact. Non-Linear Complexity in Supply Chain Operations (3:48) Supply chain planning is frequently conceptualized as a tidy, four-stage progression spanning demand estimation, supply sourcing, production scheduling, and distribution logistics. However, Singla explains that operational realities operate as a complex multi-objective optimization problem governed by volatile, non-linear constraints. Dynamic feedback loops such as the bullwhip effect, promotional cannibalization across product categories, factory capacity ceilings, and local versus global sourcing trade-offs create operational volatility that isolated, single-agent systems cannot resolve. A Three-Tiered Architecture for Autonomous Planning (6:21) To mirror how human planners diagnose and mitigate sudden disruptions, Nagarro structures autonomous decision-making across three distinct intelligence layers. Causal Intelligence identifies metric drift and isolates the physical root causes of anomalies across geographies or product lines. Decision Intelligence generates corrective intervention scenarios, evaluating outcomes through digital twins and constraint-based optimization engines. Finally, Organizational Intelligence incorporates enterprise policies, stakeholder incentives, authority thresholds, and institutional memory loops, ensuring proposals reflect company culture and historical outcomes. Grounded Root-Cause Diagnosis and Closed-Loop Execution (10:30) Rather than relying on unconstrained large language model reasoning, Singla anchors diagnostic workflows in twin data models: a Causal Knowledge Graph encoding cause-and-effect rules, and a Business Ontology Graph mapping physical nodes like SKUs, suppliers, and distribution centers. A trio of specialized agents—monitoring metrics, generating hypotheses, and validating evidence against operational databases—progressively isolates the drivers of disruptions like sudden stockouts. Once validated, operators run interactive scenario simulations to weigh trade-offs between sales volume, profit margins, and holding costs before pushing decisions directly into ERP, CRM, or manufacturing execution systems. Autonomous supply chain planning holds promise for automating complex integrated business planning, but its practical viability depends on overcoming compounding multi-turn errors through structured knowledge graphs, digital twin simulations, and enterprise policy constraints.

精炼阅读摘要

Nagarro数据科学与人工智能实践负责人Anish Singla指出,尽管业界对自主智能体规划寄予厚望,但多轮工具调用引发的可靠性衰减导致其当前在损益表上的实质贡献有限;为此,Nagarro提出了结合因果智能、决策智能与组织智能的三层架构,利用双知识图谱与多智能体协同攻克供应链深层的非线性决策难题。 产业愿景与工程现实:多轮可靠性衰减 (0:04) Singla指出,当前业界愿景预测未来业务逻辑将全面由AI接管,不仅会有数万亿个自主智能体投入生产,企业IT部门也将转变为负责管理智能体的“AI人力资源部门”。然而,工程落地正面临严峻的技术阻力。在实际的多轮智能体工作流中,连续的工具调用会导致误差逐级累积。系统整体可靠性在经历大约20个调用周期后会出现显著的指数级下降,这直接解释了为何目前许多智能体部署对企业的实际损益(P&L)贡献微弱。 尽管开发者在30分钟内即可搭建出基础智能体,但要达到生产级可用性,则需要极为复杂的深层工程架构。Nagarro强调,系统必须具备健壮的上下文管理能力、长效记忆保留机制、安全护栏以及对业务决策的可解释性,才能真正满足企业级运作的标准。 供应链表面线性下的非线性复杂网络 (3:48) 传统供应链规划在表面上往往呈现为需求预测、供应源规划、产线排产与分销调度四个环环相扣的线性阶段。然而,Singla分析认为,一旦深入底层,供应链实质上是由海量非线性变量构成的复杂网络,导致单一智能体架构根本无法胜任自主规划的任务。 在真实的运营场景中,规划系统必须同时应对成千上万个活跃SKU、促销活动在整个产品品类中引发的同质蚕食效应、天气扰动、本地与全球采购的权衡以及工厂物理产能的刚性约束。此外,消费者端的微小需求波动会通过牛鞭效应等动态反馈回路向上传导并急剧放大。从数学本质上看,供应链优化属于在严苛非线性约束条件下的多目标最大化问题,远非传统的线性推演所能解决。 三层智能架构:因果、决策与组织协同 (6:21) 当消费品牌遭遇销售额突发下降20%等异常事件时,传统人工分析师必须逐步排查工厂停工、情绪转变或竞品促销等潜在诱因,进而权衡降价或削减库存等干预方案。为了使这一复杂的决策过程实现自动化与规模化,Nagarro构建了由三个独立智能层组成的系统框架。 第一层是回答“发生了什么”的因果智能(Causal Intelligence),负责自动检测关键绩效指标(KPI)漂移,并在地理区域、渠道或产品线层级定位根因;第二层是回答“应当做什么”的决策智能(Decision Intelligence),借助世界模型/数字孪生、预测与优化引擎评估各种纠偏情景并输出最优解;第三层是回答“本企业会如何做”的组织智能(Organizational Intelligence),它将企业特有的策略边界、利益相关者激励、员工动机及历史反馈闭环深度融合,确保智能体输出的行动始终符合企业文化与既往经验。 双知识图谱驱动的假设验证与落地执行 (10:30) 因果智能的实现必须依托结构化的企业知识,而非任由大语言模型进行无约束的发散推理。Nagarro通过因果知识图谱(固化通用与企业特定的因果推导规则,如将缺货关联至供应限制或需求突增)与业务本体图谱(映射SKU、供应商、配送中心物理拓扑与资金分配)来为系统注入明确的思考模式。 在运行机制中,三大专业智能体形成闭环:KPI监控智能体识别库存周转天数等指标的异常下滑;假设生成智能体查询双图谱构建潜在根因;验证智能体则调用实际业务数据核实或推翻假设。在原型演示中,系统成功排除了错误假设并锁定消费者需求突增这一诱因,随后模拟调整定价对销售额、利润率及库存持有成本的美元级影响,最终将确认策略直接推送至ERP、CRM或MES等企业核心系统执行。 Singla总结认为,智能体规划系统展现了综合复杂输入以驱动多准则供应链决策的潜力。然而,该方案能否真正颠覆集成业务规划(IBP)以及销售与运营规划(S&OP),关键不仅在于算法演进,更取决于企业能否有效解决多轮调用的可靠性衰减,并沉淀出扎实的知识图谱与动态记忆资产。

Detailed notes — zh

## Background 该内容由行业峰会频道 Ai4 于 2026 年 8 月 18 日在 YouTube 平台发布,由 Nagarro 数据科学与 AI 实践负责人 Aanish Singla 主讲。演讲围绕供应链计划中的 Agentic AI 展开,旨在探讨持续连接预测、库存与业务计划的智能体系统究竟是行业炒作还是下一代运营现实,并展示如何通过智能体实现自适应决策与跨部门对齐。 ## TL;DR Aanish Singla 深入剖析了 Agentic AI 在复杂供应链场景中落地的工程痛点,指出多步工具调用带来的误差累积以及供应链的高度非线性使得孤立大模型难以产生实质财务贡献。为此,Nagarro 提出了涵盖“因果智能”、“决策智能”与“组织智能”的三维全景框架。系统通过业务本体与因果知识图谱驱动 KPI 监控、假设生成与验证三类智能体协作排查异常根因,并结合组织数字孪生与仿真引擎量化评估干预策略的财务影响,最终一键同步回 ERP 等核心系统实现端到端闭环。 ## Atmosphere & style 整场演讲呈现出高度理性、务实且扎根一线工程实践的专业技术布道风格。讲者开篇直面行业对智能体的过度炒作,以客观冷静的视角剖析可靠性断崖等工程现实,随后通过条理严密的架构图与原型实机演示层层递进,既展现出对复杂业务系统的敬畏,又给听众带来了清晰、可落地的技术路径与信心。 ## Key takeaways - [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) 业界对 Agentic AI 寄予厚望,但多步工具调用在 20 个周期左右时单步误差会累积放大,导致系统可靠性呈指数级下跌,目前对企业 P&L 的实质财务贡献仍较有限。 - [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) 构建基础智能体门槛极低,但决定其实际商业价值落地的关键在于上下文工程、持久记忆机制以及业务可解释性控制。 - [03:48](https://www.youtube.com/watch?v=KJDartdarIA&t=228s) 供应链微观运营充斥着数以万计的 SKU、同蚀效应、牛鞭效应等强非线性动态反馈,孤立的单点智能体无法承担端到端决策重任。 - [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) Nagarro 提出破局全景框架,由三大智能维度构成:定位异常根因的“因果智能”、推演优化策略的“决策智能”以及融合企业制度与偏好的“组织智能”。 - [10:20](https://www.youtube.com/watch?v=KJDartdarIA&t=620s) 因果智能通过结合通用供应链规律与企业专有历史数据的因果知识图谱,使智能体能够沿结构化路径归因排障,避免黑盒幻觉。 - [11:50](https://www.youtube.com/watch?v=KJDartdarIA&t=710s) 系统依托 KPI 监控智能体、假设生成智能体与证据验证智能体协同运作,精准复刻业务分析师的根因调查路径。 - [12:52](https://www.youtube.com/watch?v=KJDartdarIA&t=772s) 决策智能依赖大模型之外的专用数字孪生/世界模型、预测引擎及仿真优化引擎,提供可试验策略连锁反应的沙盒环境。 - [13:47](https://www.youtube.com/watch?v=KJDartdarIA&t=827s) 组织智能深度建模企业的战略导向、利益相关者诉求、激励政策与管理权限,并通过持久记忆学习环实现持续进化。 - [14:47](https://www.youtube.com/watch?v=KJDartdarIA&t=887s) 原型系统演示了针对库存周转天数异常的自动调查流程,通过实体关系图谱与因果图谱自动生成并核验多维度假说。 - [17:40](https://www.youtube.com/watch?v=KJDartdarIA&t=1060s) 系统支持量化美元价值评估与仿真推演,业务人员调优确认后可一键将决策回流至 ERP、CRM 或 MES 等底层系统执行闭环。 ## Detailed walkthrough ### [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) 愿景与现实的碰撞:Agentic AI 的行业野望与工程痛点 Nagarro 数据科学与 AI 实践负责人 Aanish Singla 在演讲开场中介绍了 Nagarro 成立 30 年来为客户定制解决复杂问题的背景,并直奔主题:在供应链计划(Supply Chain Planning)领域,Agentic AI(智能体 AI)究竟是炒作噱头,还是即将到来的业务现实?业界对于智能体赋予了极高期望,行业领袖们描绘出宏大的愿景——从未来的所有业务逻辑都将运行在 AI 之上,到生产环境中运转着数以百兆计的智能体;甚至未来的 IT 部门将转变职能,像“智能体的人力资源部(HR Department for Agents)”一样管理人机协同。在这一愿景下,智能体不再仅仅是简单的自动化工具,而是能够自主推理、协同并代表人类做出且执行高质量决策的生产力核心。 然而,从一线工程落地与实操的视角切入,现实却呈现出截然不同的图景。在日常工程研发中,当智能体进行多轮交互(Sequential Tool Calling)时,每增加一步工具调用,单步错误就会逐层累积放大;一旦调用链条达到 20 个周期左右,系统的整体可靠性就会出现断崖式(指数级)下跌。这也是为什么许多头部企业虽然积极试点,但目前智能体对企业损益表(P&L)的实质贡献仍然十分有限。 构建一个基础智能体门槛极低,任何人都能在 30 分钟内搭建上线;但决定其商业价值成败的关键,在于智能体周边的支撑体系——上下文工程(Context Engineering)、记忆机制(Memory Handling)以及严密的业务可解释性控制,确保智能体不会做出让业务方无法理解或解释的失控决策。 ```mermaid flowchart TD accTitle: 智能体落地挑战与核心要素 subgraph Ambition["宏大愿景 (Industry Ambition)"] A1["逻辑全面沉淀至 AI"] --> A2["海量智能体协同运作"] A2 --> A3["IT 部门转型为 Agent HR"] end subgraph EngineeringGap["工程现实差距 (Engineering Reality)"] B1["工具调用链路延长 (20+ 周期)"] --> B2["单步误差逐级累积"] B2 --> B3["系统可靠性呈指数级下跌"] B3 --> B4["当前 P&L 财务影响有限"] end subgraph KeyEnablers["破局关键 (Core Enablers)"] C1["上下文工程 Context Engineering"] C2["持久记忆管理 Memory Handling"] C3["业务可解释性与对齐 Governance"] end Ambition -.-> EngineeringGap EngineeringGap --> KeyEnablers ``` --- ### [03:48](https://www.youtube.com/watch?v=KJDartdarIA&t=228s) 表面线性与深层非线性:供应链体系的真实复杂度 供应链从表面抽象来看似乎非常直观,通常可归纳为四个标准化步骤:需求预测(Demand)、供应计划(Supply)、生产/装配排程(Production/Assembly)以及最终的分销履约(Distribution)。在二层视角下,每个环节需要叠加诸如竞争对手动态、季节性趋势、库存约束、产能排产与干线路径规划等变量。 然而深入到微观运营层面,供应链的复杂度会呈爆炸式增长。企业往往需要同时管理数以万计的 SKU,单一产品的促销活动可能会对整个品类造成不可忽视的“同蚀效应(Cannibalization Effect)”,极端天气或突发事件也可能瞬间打乱需求模式。在供应端,全球采购与本地化供应策略的权衡在动荡环境下充满变数。 更致命的是,这些变量之间的关系并非线性因果,而是充斥着严重的非线性效应与反馈回路。例如经典的“牛鞭效应(Bullwhip Effect)”,前端微小的需求波动沿供应链向上传导时会被成倍放大。在面对“当前到底该下多少采购订单”这样一个看似简单的决策时,决策者必须在一系列互斥的目标函数与业务约束之间寻找最优解。面对这种高度非线性的动态系统,孤立的单点智能体根本无法承担端到端决策的重任。 --- ### [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) 应对突发异动的全景框架:三大智能体系 Aanish Singla 提出了一个具体的业务场景:一家 B2C 零售企业突然遭遇了某款产品销售额骤降 20% 的危机。在传统运作模式下,分析团队需要耗费大量人工去排查原因——是工厂停工、消费者偏好转移、还是竞品发动了价格战?面对排查结果,又有一系列干预手段可供选择,如降价促销、削减库存或维持现状。当尝试用 Agentic AI 替代人工分析时,核心挑战在于:智能体如何精准锁定真正根因并制定出最佳行动方案? 为解决单点智能体无法应对系统复杂性的缺陷,Nagarro 提出了一套包含三大智能维度的全景式框架: ```mermaid flowchart LR accTitle: Nagarro 供应链智能体三大智能框架 subgraph Causal["1. 因果智能 (Causal Intelligence)"] direction TB C1["KPI 异动监测 (销售骤降 20%)"] --> C2["问题空间定位 (区域/品类/渠道)"] C2 --> C3["根因归因与锁定"] end subgraph Decision["2. 决策智能 (Decision Intelligence)"] direction TB D1["干预策略生成 (降价/调产/减库)"] --> D2["多场景权衡与仿真评估"] D2 --> D3["推荐最优行动解"] end subgraph Organizational["3. 组织智能 (Organizational Intelligence)"] direction TB O1["企业政策与激励机制约束"] --> O2["历史决策反馈闭环"] O2 --> O3["'我的企业会如何决策'"] end Causal --> Decision Decision <--> Organizational ``` - **因果智能(Causal Intelligence)**:负责解答“究竟发生了什么”。它首先自动感知 KPI 指标的异常波动并评估排查价值,随后将大颗粒度指标拆解、下钻,在具体的地理区域、产品线或渠道中定位异常,最终完成深层根因归因。 - **决策智能(Decision Intelligence)**:负责在明确根因后生成多种应对策略候选集,并对不同策略的成本、收益与风险进行系统性量化评估,最终推选出合理解。 - **组织智能(Organizational Intelligence)**:这是框架中不可或缺的落地上层。相同的分析结果在不同企业可能会导向完全不同的决策,因为各企业的战略偏好、激励考核机制、合规政策以及文化信仰截然不同。组织智能将这些隐性规则与历史决策的反馈循环(如“去年采取类似措施在实际执行中的成效”)注入系统,确保智能体的推演完全契合“当前企业”的特定情境。 --- ### [10:20](https://www.youtube.com/watch?v=KJDartdarIA&t=620s) 因果智能落地基石:企业 KPI 监测与知识图谱建模 进入因果智能的深层实现机制,其最底层依赖于企业现有的数仓与报表体系中沉淀的大量 KPI 数据资产。智能体若要对这些指标进行持续监控与异常诊断,不能仅依靠大语言模型通用的泛化推理,而必须拥有契合特定企业业务逻辑的“思考范式”。 为了赋予智能体这种结构化的归因逻辑,Nagarro 将业务知识编码为知识图谱(Knowledge Graphs)。其中核心的因果知识图谱(Cause-and-Effect Graph)系统性梳理了“何种原因会导致何种问题”的拓扑关联: - **通用领域因果逻辑**:涵盖供应链领域普适的因果规律(如交期延长与缺货率上升的关联)。 - **企业专有历史知识**:沉淀企业特有的运营历史、渠道结构、供应链节点特性与过往异常事件。 通过将通用推理能力与企业专有因果知识图谱深度结合,上层的智能体集群在进行指标异动归因时,能够沿着结构化的因果路径精准回溯,从而彻底告别大模型的黑盒猜测与幻觉问题。 ### [11:50](https://www.youtube.com/watch?v=KJDartdarIA&t=710s) 知识图谱驱动的三智能体协作架构 在构建供应链智能系统时,第二个知识图谱承载了企业核心的业务本体(Business Ontology)与运作逻辑。以特定 SKU 为例,该图谱中清晰编码了由哪些分销中心(DC)负责履约、关联的供应商有哪些、投入了多少资金等详细业务脉络。在此知识图谱之上,系统部署了三个协同作业的智能体(Agent): 1. **KPI 监控智能体(KPI Monitoring Agent)**:实时追踪关键业务指标,评估其变动幅度是否足够显著以触发根因分析流程; 2. **假设生成智能体(Hypothesis Generation Agent)**:结合因果知识图谱与业务实体关系,发散生成多种可能的潜在诱因假设; 3. **证据验证智能体(Validation Agent)**:主动调取业务数据与上下文证据,逐一核实各假设是否成立。 通过知识图谱注入组织上下文,这些智能体能够精准复刻资深业务分析师的思考路径。 ```mermaid flowchart TD accTitle: 供应链智能体排障与决策架构流程图 subgraph KG["知识图谱与上下文层"] G1["业务本体图谱\n(SKU/仓储/供应商/策略)"] G2["因果关系图谱\n(多层级诱因网络)"] end subgraph Agents["智能体协同层"] A1["KPI 监控智能体\n(异常检测与触发)"] A2["假设生成智能体\n(多维度归因发散)"] A3["验证智能体\n(证据收集与假说核实)"] end subgraph Decision["决策智能与执行层"] D1["数字孪生与预测/仿真引擎"] D2["方案推荐与财务影响测算"] D3["业务系统执行\n(ERP / CRM / MES)"] end KG --> Agents A1 --> A2 --> A3 A3 --> D1 --> D2 --> D3 ``` ### [12:52](https://www.youtube.com/watch?v=KJDartdarIA&t=772s) 决策智能引擎与组织数字孪生 要让智能体实现可落地的决策智能(Decision Intelligence),单靠大语言模型本身的通用推理能力是远远不够的,系统必须配备一系列专用工具组件: * **组织运作的数字孪生/世界模型(World Model)**:为智能体提供试验决策的沙盒环境,当智能体拟定某项操作时,能够放入该数字生态中进行全局推演,评估对整个网络造成的连锁反应; * **预测引擎(Prediction Engine)**:预估特定干预行为对业务走向的具体影响; * **仿真与优化规划引擎(Simulation, Optimization & Planning Engines)**:在复杂约束条件下寻找最优资源配置与动作策略; * **推理引擎(Reasoning Engine)**:支撑端到端逻辑推导与工具调度。智能体将这些底层能力作为工具链调用,从而具备严密的决策思考力。 ### [13:47](https://www.youtube.com/watch?v=KJDartdarIA&t=827s) 组织智能:战略、利益相关者与记忆学习环 当前业内常被忽略、但最为核心的一环是“组织智能(Organizational Intelligence)”。仅有通用推理无法做出真实业务决策,系统必须深度建模企业的组织上下文,包括战略导向、业务守则与策略、各利益相关方(Stakeholders)的诉求、激励机制以及各自的管理与控制权限(Span of Control)。 此外,系统引入了持久记忆(Memory)与持续学习反馈闭环(Learning Loop),使其能够像一个具备生命力的有机体(Living Organism)一样,在真实业务生态中不断进化。 ### [14:47](https://www.youtube.com/watch?v=KJDartdarIA&t=887s) 系统实机演示:KPI 异动、因果图谱与假设验证 现场演示展示了该架构的原型系统。在界面的 KPI 库中,用户可自选关注的指标(例如库存周转天数、库存周转率等)。系统检测到某 SKU 的“在手天数(Days of Inventory / Days on Hand)”出现持续下行漂移,随即自动触发调查流程。 系统后台调取了两类图谱支持排障: * **实体关系图谱(Entity-Relationship Graph)**:展示该 SKU 的关联采购订单(PO)、所属产品类别、仓储货位、历史促销活动、预测模型、安全库存策略、质检流程及配送路线; * **多层级因果图谱(Causal Knowledge Graph)**:例如当发生缺货(Stockout)时,一级诱因可能是供应受阻或需求激增;需求激增的二级诱因则进一步细分为促销活动、季节性高峰或节假日效应等,为模型提供严谨的归因提示。 基于此,智能体在需求侧、供应侧和规划侧分别生成了多种假说(如规划侧的“需求过度预测”、供应侧的“在途运输延误”等)。在调取数据完成自动验证后,界面通过红绿标线清晰呈现各假说的证实与证伪状态,最终确认本次异动是由“未预期的消费者需求突变”所致。 ### [17:40](https://www.youtube.com/watch?v=KJDartdarIA&t=1060s) 仿真推演、跨系统闭环与三层技术架构总结 在确认根本原因后,系统自动生成了一组优化推荐方案,并附带量化的美元价值影响预估(Indicative Dollar Value Impact)。在实际采纳方案前,业务人员可利用内置仿真工具调整杠杆(例如调整产品定价),实时观察该变动对销量、利润率(Margin)及库存持有成本等多项 KPI 的短期与长期影响。 选定最优方案后,平台支持一键将决策动作同步回流至底层的 ERP、CRM 或 MES 系统中落地执行。 - **三层架构落地进展**:目前因果层(Causal Layer)与决策层(Decision Layer)已打通落地,团队正全力攻坚第三层——深度组织上下文(Organizational Context)的接入。 - **展台交流与答疑**:Aanish 总结指出,智能体规划绝非简单的对话模型堆叠,而是由知识图谱、数据库、业务规则与多智能体紧密结合的复杂系统能力;随后他邀请现场观众前往 15-16 号展位进一步深入交流。 ## Notable quotes > [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) 未来的所有业务逻辑都将运行在 AI 之上,生产环境中运转着数以百兆计的智能体;甚至未来的 IT 部门将转变职能,像“智能体的人力资源部(HR Department for Agents)”一样管理人机协同。 — Aanish Singla > [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) 当智能体进行多轮交互(Sequential Tool Calling)时,每增加一步工具调用,单步错误就会逐层累积放大;一旦调用链条达到 20 个周期左右,系统的整体可靠性就会出现断崖式(指数级)下跌。 — Aanish Singla > [00:04](https://www.youtube.com/watch?v=KJDartdarIA&t=4s) 构建一个基础智能体门槛极低,任何人都能在 30 分钟内搭建上线;但决定其商业价值成败的关键,在于智能体周边的支撑体系——上下文工程(Context Engineering)、记忆机制(Memory Handling)以及严密的业务可解释性控制。 — Aanish Singla > [03:48](https://www.youtube.com/watch?v=KJDartdarIA&t=228s) 单一产品的促销活动可能会对整个品类造成不可忽视的“同蚀效应(Cannibalization Effect)”,极端天气或突发事件也可能瞬间打乱需求模式。 — Aanish Singla > [03:48](https://www.youtube.com/watch?v=KJDartdarIA&t=228s) 经典的“牛鞭效应(Bullwhip Effect)”,前端微小的需求波动沿供应链向上传导时会被成倍放大。在面对“当前到底该下多少采购订单”这样一个看似简单的决策时,决策者必须在一系列互斥的目标函数与业务约束之间寻找最优解。 — Aanish Singla > [06:21](https://www.youtube.com/watch?v=KJDartdarIA&t=381s) 相同的分析结果在不同企业可能会导向完全不同的决策,因为各企业的战略偏好、激励考核机制、合规政策以及文化信仰截然不同。组织智能将这些隐性规则与历史决策的反馈循环注入系统,确保智能体的推演完全契合“当前企业”的特定情境。 — Aanish Singla > [10:20](https://www.youtube.com/watch?v=KJDartdarIA&t=620s) 通过将通用推理能力与企业专有因果知识图谱深度结合,上层的智能体集群在进行指标异动归因时,能够沿着结构化的因果路径精准回溯,从而彻底告别大模型的黑盒猜测与幻觉问题。 — Aanish Singla > [11:50](https://www.youtube.com/watch?v=KJDartdarIA&t=710s) 通过知识图谱注入组织上下文,这些智能体能够精准复刻资深业务分析师的思考路径。 — Aanish Singla > [13:47](https://www.youtube.com/watch?v=KJDartdarIA&t=827s) 系统引入了持久记忆(Memory)与持续学习反馈闭环(Learning Loop),使其能够像一个具备生命力的有机体(Living Organism)一样,在真实业务生态中不断进化。 — Aanish Singla > [17:40](https://www.youtube.com/watch?v=KJDartdarIA&t=1060s) 智能体规划绝非简单的对话模型堆叠,而是由知识图谱、数据库、业务规则与多智能体紧密结合的复杂系统能力。 — Aanish Singla ## Mentioned Aanish Singla, Nagarro, Ai4, Agentic AI, IBP (Integrated Business Planning), S&OP (Sales and Operations Planning), 因果知识图谱 (Causal Knowledge Graph), 业务本体图谱 (Business Ontology Graph), 数字孪生 / 世界模型 (World Model), ERP, CRM, MES ## Video description Aanish Singla - Partner & Director - AI and Data Science, Nagarro What happens when forecasts, inventory positions, market signals, and business plans are continuously connected rather than reviewed once a month? This session will explore how Agentic AI is reshaping the planning landscape - from demand sensing and scenario evaluation to cross-functional alignment and plan execution. I'll demonstrate a new planning approach that adapts to changing conditions, surfaces trade-offs, explains itself, and speeds up decision-making. Attendees will gain a practical view of what is possible today, what remains challenging, and how leading organizations are beginning to rethink IBP and S&OP. Join the session to see whether agentic planning is hype or the start of a fundamentally different planning model. [Source](https://www.youtube.com/watch?v=KJDartdarIA)

Source quotes

[0:04] Aanish Singla: 未来的所有业务逻辑都将运行在 AI 之上,生产环境中运转着数以百兆计的智能体;甚至未来的 IT 部门将转变职能,像“智能体的人力资源部(HR Department for Agents)”一样管理人机协同。 [0:04] Aanish Singla: 当智能体进行多轮交互(Sequential Tool Calling)时,每增加一步工具调用,单步错误就会逐层累积放大;一旦调用链条达到 20 个周期左右,系统的整体可靠性就会出现断崖式(指数级)下跌。 [0:04] Aanish Singla: 构建一个基础智能体门槛极低,任何人都能在 30 分钟内搭建上线;但决定其商业价值成败的关键,在于智能体周边的支撑体系——上下文工程(Context Engineering)、记忆机制(Memory Handling)以及严密的业务可解释性控制。 [3:48] Aanish Singla: 单一产品的促销活动可能会对整个品类造成不可忽视的“同蚀效应(Cannibalization Effect)”,极端天气或突发事件也可能瞬间打乱需求模式。 [3:48] Aanish Singla: 经典的“牛鞭效应(Bullwhip Effect)”,前端微小的需求波动沿供应链向上传导时会被成倍放大。在面对“当前到底该下多少采购订单”这样一个看似简单的决策时,决策者必须在一系列互斥的目标函数与业务约束之间寻找最优解。 [6:21] Aanish Singla: 相同的分析结果在不同企业可能会导向完全不同的决策,因为各企业的战略偏好、激励考核机制、合规政策以及文化信仰截然不同。组织智能将这些隐性规则与历史决策的反馈循环注入系统,确保智能体的推演完全契合“当前企业”的特定情境。 [10:20] Aanish Singla: 通过将通用推理能力与企业专有因果知识图谱深度结合,上层的智能体集群在进行指标异动归因时,能够沿着结构化的因果路径精准回溯,从而彻底告别大模型的黑盒猜测与幻觉问题。 [11:50] Aanish Singla: 通过知识图谱注入组织上下文,这些智能体能够精准复刻资深业务分析师的思考路径。 [13:47] Aanish Singla: 系统引入了持久记忆(Memory)与持续学习反馈闭环(Learning Loop),使其能够像一个具备生命力的有机体(Living Organism)一样,在真实业务生态中不断进化。 [17:40] Aanish Singla: 智能体规划绝非简单的对话模型堆叠,而是由知识图谱、数据库、业务规则与多智能体紧密结合的复杂系统能力。

Source quotes

[0:04] Aanish Singla: HR departments for AI agents [6:21] Aanish Singla: What Happens? [6:21] Aanish Singla: What Should We Do? [6:21] Aanish Singla: What Would *Our* Enterprise Do? [10:30] Aanish Singla: thinking pattern [12:52] Aanish Singla: living organism

Original transcript

[0:04] Hi all. Very good afternoon. Um So, let me take  a quick uh uh time to introduce myself. So, [0:11] myself Anish Singla. I lead the data science AI  uh practice at Nagarro. So, Nagarro has been there [0:16] for 30 years. We're helping our clients build  custom uh solutions to the complex problems. Um [0:22] so, in addition to AI and data science, uh a lot  of experience in supply chain. So, I'll share a [0:28] few thoughts uh that we have been working towards  how does agentic really come live in supply chain [0:34] planning. Right? Um so, yeah. Uh this is the topic  for today, and I'm going to take a very practical [0:41] uh view of the the entire uh situation. Of course,  there is a lot of hype, and also, you know, [0:48] there is a lot of potential that we see in the  in this whole uh topic of agentic uh autonomous [0:54] agentic planning. Right? Um so, if you look at  it, agentic has been uh really there. Agents can [1:03] really reason, they can act, they can collaborate.  And if we look at the industry leaders, I think [1:09] the the the scale of the ambition in your really  reflects in what these leaders have been saying. [1:15] Right? In uh ranging from all the logic lie  will lie in the AI uh in the future to having [1:22] hundreds of trillions of agents, you know,  running um you know, in production to [1:28] having not only managing, you know, humans,  but also uh the IT department will start like [1:34] to shift moving like an HR department  for the agents, right? So, these are um [1:38] uh reflects the scale of the ambition,  which means that the agents not only have to [1:44] be looked at as a tool for automation, but more as  a tool uh or as a you know, thing that can enable [1:51] uh better decision-making, and also execute  those decisions on our on our behalfs. [1:57] Right? Um And that's one side, which is  you know looks like a a great potential. [2:03] If you look at the other side, right,  which is more like a hands-on person, I see [2:08] and work day in and day out. The engineering side  of things what I see is as the number of turns, [2:15] as the number of tool calling, you know,  increases sequentially, we see that there is [2:22] an exponential dip in the in the reliability  because each each error that you have adds up to [2:28] the next error, right? And if you like add it up  to like 20 cycles, the the reliability really goes [2:33] down, all right? And this also reflects in some of  the numbers that, you know, the leading companies [2:39] have been publishing that there is a very little  P&L impact currently, you know, that these agents [2:45] have been able to create, right? So, these are  two, I know, extreme views. Right now, they may [2:53] seem like contradicting each other, but actually  if you look at it, building agents is really easy, [2:58] right? Anybody can spin up an agent in less than  30 minutes. But what is important is how do we [3:05] how do we build the things around the agent? The  context engineering, the memory, the handling [3:09] of the memory, right? Making sure that the agent  doesn't do something, you know, which kind of is [3:16] is very tough for the business to, you know,  explain later, right? So, focusing our areas [3:22] around that will lead us to the ambition that  we are aiming at, right? So, that is also the [3:30] the thought that I'm going to share that how does  this all come together in the form of, you know, [3:35] in agentic planning in supply chain? What are the  realities? What are the complexities, right? And [3:40] how at Nagarro we are dealing with some of these  complexities to deliver real business value. [3:48] So, if you look at supply chain, supply chain  is is literally these four steps, right? So, [3:53] you have you have you estimate the demand,  you start planning where the supply is going [3:58] to come from, you have your production  or your assembly lines, you start uh [4:04] planning and executing them, and then finally the  distribution, right? Looks very straightforward. [4:08] If I go a little bit deeper into it, the  demand planning should consider competition, [4:14] it should consider seasonality, trends, and so  on. Similarly, you know, on the supply side, there [4:20] would be constraints. There is inventory to be  managed, right? And then production side, again, [4:25] there are will be constraints and scheduling  and planting. And also on the distribution side, [4:31] the network-related complexities and the routing  stuff, right? So, this is a little a second-level [4:37] view, but if we look at it even more closely, you  know, this is even more complex because there are [4:44] literally thousands of SKUs that you're dealing  with, right? There is a cannibalization effect of [4:49] one promotion that is being run on, you  know, the entire category, right? Any any um [4:56] disruptions in weather, for example, could lead to  change in the demand, right? So, this is much more [5:01] complex than uh when we look at it at the surface.  And then, similarly, on the supply side, you know, [5:07] there will be a ton of uh constraints. You  know, how do you do um how do you look for [5:15] uh local versus global supplies, right? With  all the changing dynamics, how do we make sure [5:20] that the supply side is robust, right? To a whole  lot of dynamics also on the, you know, production [5:26] side. I'm not going into each one of them, but you  get the idea that when we look at it more closely, [5:32] there are more and more complexities that  these agents have to deal with, right? So, [5:38] and all of this is actually not linear. These are  non-linear effects, right? So, for like a a simple [5:46] decision, what what is the order that I should  place? There are there are a set of objectives [5:53] that I want to maximize and then I'm working  under a bunch of constraints and these, you know, [5:59] for example, the bullwhip effect, right,  would have a very non-linear effect on [6:04] the entire supply chain, right? So, while it  looked like a linear flow, but in reality, [6:08] this is much more complex, right? So, the question  that I want you to kind of reflect for a minute is [6:14] can agents handle this? Right? Are we ready  to deal with this kind of a complexity? [6:21] And if yes, what does it look like? Let's take a  simple scenario, right? A company who is selling [6:28] products to B2C, let's say consumers, they see  a sudden drop in sales of about 20%. Right? Now, [6:36] let's let's think from an agentic perspective,  right? What should we do to help this company? [6:43] So, there could be several possible reasons why  this might be happening, right? There could be, [6:48] uh, you know, a factory downtime, there is a  customer demand that is shifting, maybe the [6:53] competition did something, right? So, there can  there will be n number of reasons, right? And [6:58] we know today analysts are spending time on doing  this manually, looking at, you know, every factor, [7:04] analyzing things, right? And and then there could  be several actions that you can take out of, [7:11] uh, you know, these possible causes, you know, do  you mark up do do you mark down your products? Do [7:16] you continue? Do you, uh, decrease the inventory?  Right? There are several possible interventions [7:21] that you could do. Right? But thinking it from an  agentic perspective, can agents identify what is [7:28] the right root cause and what is the right action  to be taken? You know, can agents do that today? [7:36] So, when when we are solving this problem,  we sort of took a step back and say, "Okay, [7:41] let's look at it from a more holistic perspective  instead of just building one agent here, another [7:47] agent there, right?" Which really doesn't  cannot solve the complexity at this scale. [7:53] So, this has led to a framework with three  intelligences that we think are required. [7:59] The first one is a causal intelligence. So,  the causal intelligence basically looks at, [8:04] "Okay, what happened?" Right?  For example, the sales drop. So, [8:08] there is a change in the KPI. Right? So, the  agent should be able to automatically identify [8:14] what which KPIs are changing and is it  worth investing it investigating this KPI. [8:19] Followed by where the problem is. Now, sales  KPI is a huge number, right? Is Is there [8:25] an impact on one geography? Is there impact on one  product line, one channel? So, one has to first [8:30] localize the cause of the problem, right? So, that  all comes under the bucket of causal intelligence. [8:37] The second intelligence that is needed  for the agent is a decision intelligence. [8:42] Right? So, once we know what is the root cause, we  have to then generate several possibilities of how [8:48] we can address that root cause. Right?  And then evaluate those options to see [8:54] which of them really makes sense, right?  So, that's the decision intelligence part. [8:59] Now, this is not sufficient. We also need  to bring in the organizational intelligence [9:03] because the same problem, the same analysis  for different companies might lead to different [9:09] actions because of the belief, because of the  people, because of the incentives, the motives, [9:15] motivations for the company to solve, right? So,  we need to bring in organizational intelligence [9:20] which says, "What will my enterprise do in this  situation?" Right? So, this is the third layer. [9:27] So, bringing it all together and breaking it down  further, so causal intelligence basically looks at [9:34] various patterns, identifies what what really  went wrong, uh which KPIs were impacted, what [9:41] are the possible causes, and identify the concrete  causes for the problem. The decision intelligence [9:48] on the other hand generates several possibilities,  analyzes them, and gives out a concrete reason. [9:53] The organization capability intelligence requires  people and policies and motivations to be factored [10:02] in so that the agents which are making  these decisions, they are aware and they can [10:08] also add and it's a feedback loop, right? So,  whatever actions were taken, let's say last year, [10:13] how did they turn on the ground? So, all of that  knowledge is required for the agent to act. Right? [10:20] Um So, with that, uh let's go into each each of  these pillars and see what does it really take [10:30] to build these capabilities. What capabilities are  required for each of these intelligences to be uh [10:35] operational? So, going into causal intelligence,  the causal intelligence you see on on the top has [10:41] a bunch of agents. That we'll come back to that,  but at the at the most granular level, each [10:47] organization has a bunch of KPIs, right? In the  form of data warehouses, in the form of reports. [10:52] These KPIs have already been identified to a large  extent, right? And there is a a KPI that exists. [10:58] Now, for the agents to be able to be able to  monitoring these to monitor these KPIs and to see [11:04] what is going wrong, where things are changing,  we need to provide them with a thinking pattern, [11:11] right? About about the specific organization. And  that knowledge we are encoding these knowledge in [11:17] the form of knowledge graphs. On the left side,  you see that there is a knowledge graph which says [11:22] what causes lead to what problems. So, it's sort  of a cause and effect diagram, a knowledge graph, [11:30] which is, of course, can be generic because  there are some things that are applicable to [11:35] every enterprise, but also bringing in that  enterprise's specific history, knowledge, [11:41] and bringing and building these knowledge  graphs so that the agents can think [11:46] not in a very generic form, but also leverage  these for their reasoning. On the right side, [11:50] you see how the business operates, right? So,  for a given SKU, which distribution centers are [11:55] responsible, which are my suppliers, what is the  capital that I've invested, right? So, all of that [12:00] business anthology is is kind of loaded into the  second knowledge graph. And now, we have three [12:06] agents on the top. So, we have a KPI monitoring  agent. The KPI monitoring agent looks at, okay, [12:11] what what KPIs I do I need to monitor, right?  How are they changing? Is that change significant [12:17] enough for me to trigger a root cause analysis?  Right? Um so, that's the first agent. The second [12:22] agent is basically uh looking at these knowledge  graphs and they are generating several hypotheses [12:28] as to what might be the possible reasons, right?  And the third one is a is a is a validation [12:34] agent which basically gathers evidence to see if  these hypotheses are valid or they're not valid, [12:40] right? So, by bringing in the organizational  context in the form of knowledge graphs, [12:45] we are able to customize these agents to think  exactly how your analyst would would do that. [12:52] Right? Uh moving on to the decision intelligence,  the decision intelligence again has would need a [12:58] bunch of capabilities, right? So, first of  all, it would need a model, a digital twin [13:03] of how your organization operates because  if if the agent decides to take a decision, [13:08] we want to put it into an ecosystem and simulate  and see what happens to the entire thing, [13:13] right? So, that's the that's the world model.  Then, we need a prediction engine to see if I uh [13:18] if I can estimate what will be the impact of doing  something to building, you know, simulations, [13:25] optimization engines, planning engines, right? And  finally, you know, reasoning engines, right? So, [13:32] I mean, I'm just opening up that complexity and  showing how agents can actually do this. And all [13:38] of these capabilities are required  for the agents to think reasonably, [13:41] you know, and leverage these as tools  to be able to enable those decisions. [13:47] Finally, the most important piece which which  we see that is not being thought about or not [13:53] being discussed very often is the organization  intelligence. I can bring all the reasoning, [13:58] the generic reasoning from the LLMs, but  unless I put my organization's context, the [14:05] the the context modeling in the form  of strategy, in the form of policies, [14:09] in the form of, you know, the different  stakeholders, what are their interests, [14:12] what are their incentives, right? What are  their span of controls? Unless I bring that, [14:17] we cannot take real decisions, you know, with  these agents. And finally, you know, the memory [14:23] and the learning loop which makes it makes it  like a living organism you know, in the ecosystem. [14:29] So, these are like initial thoughts and we're  working in this direction to make this sort of [14:35] a complex supply chain planning really come alive,  you know, with the help of agents. And I will [14:41] like to switch to a quick demo to show you  a glimpse of what we have achieved so far. [14:47] With this. Okay. So, this is on the left side  you see that there there are a bunch of KPIs. [14:54] So, this is the KPI library that I was talking  about. So, there are a bunch of KPIs here. [15:00] You know, we can choose the KPIs of interest.  For example, here, the days of inventory, [15:05] inventory turnover, you know, are the KPIs. And  we see that the agent has identified that one of [15:11] these KPIs is kind of drifting downwards, right?  So, we can trigger investigation here to see [15:18] what does what can the agent find, right?  So, in this particular case, we had [15:23] the days on inventory, you know,  days on hand going going down. [15:27] So, this is the entity relationship diagram,  the graph that I was talking about. So, [15:32] we have this queue. On this queue, we see that,  okay, what are the different purchase orders, [15:37] which category did does it belong to, where does  this queue live in the warehouse, what locations, [15:44] what promotions were ran on it. So, all all  your uh knowledge of how this how the enterprise [15:52] works around this particular product is encoded  in this graph. Similarly, you know, any kind of um [15:58] forecasting, what is the safety stock strategy,  what how the quality checks are being done, [16:03] you know, to delivery routing. So, all of  this goes in in the form of a knowledge graph. [16:08] We also have the causal knowledge graph here. The  causal knowledge graph is the likely reasons why, [16:15] you know, some things have gone wrong. For  example, if there was a stockout, the stockout [16:19] could have happened due to supply constraints, due  to high demand, and then there will be level two [16:25] causes of that particular problem. The high  demand could have happened due to, you know, [16:30] a promotion campaign, could happen due to seasonal  peak, due to festivals, and so on. So, there are [16:35] This is an indicative graph of what are the kind  of problems, you know, that might be there in the [16:40] ecosystem. And these is just a hint for the for  the models to think in the in the correct lines. [16:47] So, once we have done this, there are several  hypotheses that you see the model is able to [16:51] generate on the demand side, supply side, planning  side. Um for example, on the planning side, [16:56] it says the issue could be over forecasting of  the demand. Right? On the supply side, maybe, [17:02] you know, the in-transit delays might have  caused this. Right? So, there are several [17:06] reasons that the agent has thought. And now,  when we start investigating these problems, um [17:16] Okay. Okay, so, uh the agent has already  investigated these problems and the top you see [17:22] the red and the green uh lines to show that which  hypothesis were rejected and which hypothesis [17:28] were actually true. Right? So, for example, in  this case there was an expect unexpected change [17:34] in consumer demand and the agent has found that  this is in fact uh supported through the data. [17:40] Right? So, once all of these hypotheses have  happened, the agent now moves into the the [17:45] space of recommendations. Right? So, now it has  generated a bunch of recommendations along with [17:50] you know, uh indicative dollar value impact what  this might uh lead to. Now, before taking any of [17:57] these uh recommendations, you might just want to  simulate and say, "Okay, if I change the pricing, [18:03] how my different KPIs are getting impacted?  How does the quantity? How does the margin? [18:09] How does the inventory cost, etc. get impacted  because of, you know, the change that I can [18:14] make in one of these levers. Right? So, with the  help of these simulation capabilities, one can [18:19] uh see what actions make sense, you know, in the  in the long term, in the near term. And then in [18:25] the tool itself, we kind of have the flexibility  to uh put those actions back into specific ERP or, [18:32] you know, CRM solutions or MES systems to  kind of implement those actions. Right? So, [18:37] this basically gives you kind of a brief glimpse  as to how some of these have come together, [18:42] especially in the first two layers, which  is the causal layer and the decision layer. [18:46] We are working on the third layer, which is  how to bring in the organizational context. [18:51] So, yeah, I mean, just summing it up, um  uh this is how the whole stack looks like, [18:57] which is uh all the three layers, but these are  not just agents. They're a bunch of organizational [19:02] capabilities in the form of, you know,  different knowledge graphs, different databases, [19:07] different policies that are required. And then, of  course, the agents leverage all these capabilities [19:11] to come up with a complex decisioning. Right? So,  yeah. I think that's what I wanted to share and uh [19:18] um thank you so much for listening in.  We have a We are there at booth uh 15 16. [19:24] So, feel free to drop and you know, continue the  conversation. But, if there are any questions, [19:28] I think not sure if we have the time,  but uh happy to answer those. Thank you.