An Insider's Look at SAP's 'Autonomous Enterprise'
SAP's Autonomous Enterprise pairs agentic AI with per-employee budgets and model routers to make consumption predictable
- 01At TechEd Berlin, SAP Chief AI Officer Jonathan von Rüden outlined a three-layer cost-governance model for Joule Work and the SAP Autonomous Suite: usage limits per employee or department, default-model selection (supporting 70 LLMs), and optional process analytics to verify realized value.
- 02Auto-routing across models is in internal testing before limited customer release.
- 03The framework shifts AI cost control from IT procurement to continuous operational governance—a meaningful change for CFOs embedding agentic workflows in SAP environments.
SAP's Autonomous Enterprise pairs agentic AI with per-employee budgets and model routers to make consumption predictable
At TechEd Berlin, SAP Chief AI Officer Jonathan von Rüden outlined a three-layer cost-governance model for Joule Work and the SAP Autonomous Suite: usage limits per employee or department, default-model selection (supporting 70 LLMs), and optional process analytics to verify realized value. Auto-routing across models is in internal testing before limited customer release. The framework shifts AI cost control from IT procurement to continuous operational governance—a meaningful change for CFOs embedding agentic workflows in SAP environments.
Watch: Whether SAP's model-router rollout enables finance and ops teams to automate tier selection without sacrificing auditability—a differentiator for SAP-centric managed-services providers pricing outcome-based contracts.
At the TechEd developer conference in Berlin, SAP presented additional details of its “ Autonomous Enterprise ” concept, which includes AI capabilities via Joule Work and SAP Autonomous Suite, built on the SAP Business AI Platform. The company’s focus is not just AI, but AI agents capable of acting automatically within the SAP system by performing analyses and answering queries. This raises questions, such as: How can the costs of AI agents be controlled? Who is allowed to develop the agents, and how can companies maintain oversight?
Read the full article at cio.comShow the full text · 11 min readHide the full text
At the TechEd developer conference in Berlin, SAP presented additional details of its “ Autonomous Enterprise ” concept, which includes AI capabilities via Joule Work and SAP Autonomous Suite, built on the SAP Business AI Platform. The company’s focus is not just AI, but AI agents capable of acting automatically within the SAP system by performing analyses and answering queries. This raises questions, such as: How can the costs of AI agents be controlled? Who is allowed to develop the agents, and how can companies maintain oversight? Jonathan von Rüden, chief AI officer of SAP, explains in an interview with Computerwoche how the software provider is addressing these questions — and where work still needs to be done. Computerwoche: Companies are increasingly using AI and developing more and more AI agents. But it is often difficult to predict how costs in this area will develop over time. How is SAP addressing this? Jonathan von Rüden: We generally proceed in three steps. First, we clarify together with the customer or in product management which use cases are relevant and what should be achieved with them. We distinguish between different areas of focus. First, there’s general productivity: transcriptions, summaries, presentations, or information research. This now extends far beyond classic office tasks. For example, information from the internet can be combined with SAP data and used for financial analysis. However, this area is difficult to define precisely because it encompasses so many tasks in everyday work. In addition, there are dedicated AI agents that are centrally deployed and managed by IT. These can be standard agents from SAP or customer-specific agents from Joule Studio. Finally, there are use cases where companies can differentiate themselves significantly. Here, they should consider whether they can develop their own solution. Based on this information, we estimate consumption. To do this, we consider factors such as the number of employees, how frequently a process is carried out, and how many documents are processed. We also incorporate empirical data from comparable customers and industries. Ultimately, a large part depends on usage. However, budgets and limits can be set to control costs. How do these limits prevent costs from spiraling out of control? In Joule Work, for example, a daily usage limit can be set for each employee. The user can see how much of this limit has already been used via a percentage indicator. Companies can assign different budgets, for example, for individual departments or countries. If the budget is exhausted, employees can request an additional allocation if, for example, a task absolutely needs to be completed. This allows usage-based billing to be combined with centralized cost control. The subsequent success measurement is an optional step. Agent and process analysis can be used to verify whether the desired effects have actually materialized. Many users, as a precaution, opt for the most powerful model — even if it’s the most expensive. How can this be controlled? The default setting alone has a significant impact. We see this in our own use within SAP: Most people don’t change the default model. If I set a default model that balances costs and performance well, this can already reduce costs considerably. Companies can therefore consider: Do these employees really always need the most powerful model for their tasks, or is a cheaper one sufficient for everyday use? Budgets also create an incentive to engage with the issue. If I know that my budget is limited, I’m more likely to consider whether I really need the most expensive model for a particular task. Couldn’t this selection be made automatically? We’re working on that with model routers. However, auto-routing is more complex in our use cases than in scenarios where, for example, it’s just about summarizing documents. When a system has to search through and link various transactional business objects, the question of the appropriate model becomes significantly more challenging. We are currently testing automatic routing internally and plan to make it available to our first customers in the future. SAP supports 70 LLMs in Joule Work. How much influence do customers generally have on the model selection? That depends on what they’re building or using. Anyone developing their own agent can choose the model from the available options. In Joule Work, the selection is made via modes like Standard, Extended, or Light; in addition, there’s automatic routing, which we’re currently working on. We can replace the LLMs behind these modes if a different model is better suited for the respective task. The user then doesn’t have to constantly deal with individual model versions. For our assistants, the developers decide which models best perform the tasks. They conduct extensive evaluations to determine this. When a new model is released, they check whether it actually improves the assistant. Only then is a replacement worthwhile. Additionally, we take geographical requirements into account, for example, if customers want to use exclusively European models. In doing so, we must consider regional regulations while simultaneously ensuring that the models offered are suitable for the respective tasks. What about local models? For a purely web-based agent, a local model generally plays no role. However, in the desktop application, the models for natural language processing, for example, already run locally. We are working on supporting additional local models. This is also interesting for users because it allows them to save tokens. For example, they could say: “My token budget is used up, so I’ll continue working with local models.” However, the hardware must be suitable for this. Furthermore, IT departments are often more restrictive when it comes to what can be installed. On development machines, this is usually not a problem. However, rolling out such solutions on a large scale at a customer’s site is significantly more challenging. We are working on that as well. Joule Studio makes it relatively easy for non-developers to build agents. How do companies prevent uncontrolled agent proliferation? First of all, not every user automatically has permission to use Joule Studio. This role is assigned by IT. That’s the first level of control. At SAP, we’re also initially rolling out Joule Studio to only a few thousand employees outside of IT and development, but not to everyone. We’re starting with those who are already familiar with it and have completed the necessary training. Each company decides on the specific access rules for itself. Furthermore, not every personal customization needs to result in a company-wide agent. Individual skills can be a first step. This allows you to define, for example, the style in which an agent should deliver results. In this way, I can adapt it to my own workflow. If something emerges that is also useful for others, I can discuss the next steps with IT: Will I be given permission to develop and share an agent myself? Or should I hand the idea over to a Center of Excellence that will further develop it? Is there a specific approval process? In Joule Studio, I can initially share an agent with specific colleagues who can test and work with it. Further access can be controlled via roles and the identity provider. Version control and the ability to later distribute agents to larger user groups are also included. In the SAP AI Agent Hub, I can see the inventory and the respective status: Which agents need to be reviewed, which have already been reviewed, and which have been rejected. The lifecycle can also include company-specific approvals. For example, SAP requires approval from the works council before a central agent is rolled out. Similarly, it’s possible to plan when an agent will be decommissioned. The associated IT components are also visible in this process. How do companies determine whether an agent works reliably and provi
Don't miss tomorrow's
The Daily Pulse in your inbox each morning — sourced and linked.