Session

Beyond Simple Q&A: Building an Agent Orchestrator for Enterprise Analytics

Overview

ExperienceIn Person
TrackArtificial Intelligence & Agents
IndustryFinancial Services
TechnologiesDatabricks Agents, Genie
Skill LevelIntermediate
DOWNLOAD SESSION SLIDES

What does it take to go from multiple separate Genie spaces to a single agent that can coordinate across them all? How do you ensure they reference context from your unstructured data, pull up relevant BI reports, and loop in downstream reporting agents? In this breakout session, we’ll share how the World Bank built a multi-agent system that coordinates Genie spaces, document retrieval, and downstream reporting behind a single interface.

 

What we'll cover:

 

  • Orchestrator architecture: Designing a LangGraph-based orchestrator that routes natural-language questions to the right domain Genie, decomposes multi-step queries, and synthesizes unified answers.
  • Consistency through the metrics layer: Introducing metrics-grounded Genie spaces to reduce answer variability.
  • Bridging structured and unstructured data: Combining Genie's structured query capabilities with a RAG-powered agent for document retrieval and an auto-visualization agent that can show users plots and surface relevant BI reports.

Session Speakers

Max Marcussen

/AI Engineer, AI FDE
Databricks

Speaker placeholderIMAGE COMING SOON

Suresh Kaudi

/Data Leader & AI
World Bank

Full Summary

How the World Bank built a multi‑agent orchestration layer for enterprise analytics

The World Bank Group manages massive structured datasets, millions of documents, and hundreds of dashboards tied to global development work. The goal was a trustworthy conversational interface that answers cross‑domain questions without forcing users to hunt through systems. The solution, built on the Databricks Platform, combines certified Genie agents anchored to deterministic metric views with a supervisor that orchestrates across domains.

FAQ


Metric views provided governed, deterministic definitions for concepts like budgets and commitments. Early Genie experiments on the gold layer produced inconsistent figures, so metric views, plus naming standards, data contracts, quality thresholds, and a shared glossary in Unity Catalog, established repeatable answers.

Genie One supports cross‑domain questions, but a custom supervisor adds fine‑grained control over routing logic and domain taxonomy. It also enables orchestration across data that may live outside the Lakehouse, which many enterprises still require.

Each Genie agent and sub‑agent runs on behalf of the end user and inherits Unity Catalog permissions. The supervisor never executes queries outside the user's access, so existing row‑level security and governance are consistently enforced.

Begin with context enrichment and a domain ontology. Build and certify one Genie agent per domain on metric views, then add knowledge retrieval and BI discovery agents. Move to cross‑domain orchestration only after single‑domain agents are reliable and well evaluated.

The team treats evaluation as an ongoing loop. SMEs review feedback and traces, LLM judges score correctness, relevance, routing, and "no fabricated numbers," and verified Q&A pairs and instruction tuning prevent repeat errors while expanding coverage.