LeanIX

So what SAP is evolving with is, is the, uh, knowledge graph, uh, which is baked in into the Joule Studio.

And, uh, obviously how we are architecting the whole solution is like you have the tribal knowledge of your, um, enterprise architecture in preferably LeanIX, uh, um, a modern EA tool.

You have your process context and process engineering into your, uh, tools like Signavio, and these are baked into, in your, uh, en-enterprise semantics, which is the standard semantics provided by SAP, by the standard knowledge graph, which basically gives the context of your processes and enterprise architecture knowledge.

And the agent can fit in the data, the raw data that is coming from your S/4HANA context or Ariba SuccessFactors context, but plugs it into a business context process, business context or business process context or a capability context.

So the dispute cycle come, m-might come down or a procurement variance might come down, the order to cash reduce... m-maybe the order to cash number of days might have reduced, uh, the touchless rate might have gone up.

But that's why, uh, the operating model, what we are talking about, uses, uh, three tools for three jobs.

We have SAP LeanIX, which is the registry of intent, which is where every agent is on record with the business capability and the outcome it was deployed, so that to... you can move, so that nothing runs as a orphan agent.

It's always tied.

It is a brilliant defense-in-depth strategy.

We also saw SAP confirm that their AI agent hub in LeanIX provides a central inventory of all SAP agents.

And they proudly announced that their governance architecture is independently ISO IEC 42001 certified.

That means they have rigorous third-party validation of their AI management systems, which is becoming a hard requirement for enterprise procurement.

It is a brilliant defense in depth strategy.

We also saw SAP confirm that their AI agent hub in LeanIX provides a central inventory of all SAP agents.

And they proudly announced that their governance architecture is independently ISO IEC 42001 certified.

That means they have rigorous third-party validation of their AI management systems, which is becoming a hard requirement for enterprise procurement.

What if we're just burning tokens? Is it too expensive? That's been a concern, and certainly the more recent soap opera about, you know, let's have a big AI slowdown, uh, which I think is kind of silly.

What SAP's doing now with the autonomous enterprise and a lot of these new agents is they are using Signavio and LeanIX to be able to help people make the best decision, be able to map out exactly, you know, what processes to map, how to map those, what KPIs to put together with it.

So they feel like this is going to be, with the autonomous enterprise, not just the technology, but, uh, some very, very strong guidance, best practices that customers will be able to use to put together full end-to-end solutions.

And the other part that I think is particularly exciting is also van Rossum said that industry AI begins to move now into the mainstream here with this latest, uh, updates to the autonomous enterprise they'll be showing at Connect.

It is very important, you know, so as to how one can, uh, get access to discover an MCP server, how, uh, one can, you know, so invoke an MCP server at runtime, uh, with the right access privileges, how one can get insights into agent accesses of, uh, MCP servers, uh, right? So, and last but not least, very important, uh, that you really run a validated MCP servers, uh, in your company.

So, uh, Integration Suite provides these capabilities or mechanisms to govern and, uh, manage these access privileges via Integration Suite Developer Hub, and also the Integration Suite Developer Hub's integration with LeanIX AI Agent Hub.

Thanks, Vishnu, for putting it that way.

Dhaval, does the MCPs gateway also handle things like rate limiting, payload protection, and observability once the agent starts calling these tools on scale?