Automation Analytics & Intelligence v26

What AAI v26 Means for Your Automation Bill

Product update · Broadcom AAI v26

Five glossy white tiles on glass pedestals, each with a glowing amber ring floating above it

At a Glance:

  • AAI v26 ties cost to job runs, so chargeback and showback can rest on actual usage
  • A new chat interface lets anyone ask workload questions in plain English
  • Practitioners get an 18-month SLA trend view, Airflow proxy support, and simpler CA 7 dependency tracking
  • Broadcom’s 19-minute on-demand session with product manager Jennifer Chisik walks through all of it

What did your automation cost last month? Not the license. The runs.

If that took a minute to answer, you’re in good company. At Broadcom’s Automation Virtual Summit in September, Jon Hiett, Global Solution Architect at Broadcom, cited a survey figure: 53% of organizations don’t provide showback or chargeback for automation. Broadcom puts the problem plainly. For too long, workload automation has been a fixed IT cost that the business couldn’t fully trust and IT couldn’t fully explain.

Broadcom’s answer is Automation Analytics & Intelligence (AAI) v26, now generally available. Here’s what stood out to me, and what it means if you run AutoSys, Automic, or both.

Showback gap

53%

Of organizations don’t provide showback or chargeback, per research Jon Hiett cited

One pipeline

$12,000

One month of one department’s ad hoc pipeline, in Jon’s example

SLA history

18 months

Of SLA trend history in AAI v26

Put a Price on Every Run

The headline feature is cost attribution. In AAI v26, administrators set cost variables such as software, infrastructure, and labor, then map job runs to the cost centers that use them. That gives you the true total cost of ownership of your automation instead of a guess.

It also changes the questions you can ask. Jon’s example at the summit: a department’s ad hoc pipeline triggered 50,000 job executions in a month, at a cost of $12,000. Is that report worth $12,000 a month? Maybe. But nobody can ask until the number exists. The same view also surfaces what Jon calls ghost workloads, which are redundant pipelines that keep running but serve no purpose.

My own take: showback first, chargeback later. Let each business unit see its number for a quarter before anyone sends a bill.

Ask Your Workload a Question

AAI v26 adds a chat interface in plain English. Users of any technical skill level can ask about workload and job performance and get an answer, without writing a database query. Broadcom says generative AI only builds the query. The data itself comes back through direct, deterministic access, so the numbers come straight from your data.

Think about who asks your team “why was my report late?” every month. With this, the application owner can look it up. Your scheduler experts get an afternoon back, and the business gets its answer before the meeting instead of after it.

18 Months of SLA History

One bad week tells you very little. A year and a half tells you whether month-end is quietly getting slower. AAI v26 extends the SLA trend view to 18 months and adds unified visibility by business area.

That matters given the industry research Broadcom shared at the summit. In a Broadcom-sponsored Dimensional Research survey of 500 people at enterprises worldwide, 84% said they were fairly confident they’d meet their SLAs, yet 57% said they miss orchestration deadlines monthly or more. Long-range trends are how you spot the gap between those two numbers before an auditor does. Our recap, The Orchestration Accountability Gap: Inside the SLA Illusion, has the short version.

Built for Shops With More Than One Scheduler

Citing recent research, Jon said 97% of companies use more than one orchestration tool. AAI fits that reality. Broadcom lists support for Automic Automation, AutoSys, CA 7, ESP, Apache Airflow, Google Cloud Composer, and other schedulers, so leadership can get one view while each team keeps the tools it knows.

v26 adds secure Airflow proxy support and streamlines CA 7 dependency tracking, two of the most requested practitioner enhancements. If your critical path runs from the mainframe through a Python pipeline and ends in Automic, those handoffs are where blind spots like to hide. Jon’s session on that theme is covered in The Illusion of Green: Automation Observability Beyond the Return Code.

Easier to Stand Up, Tougher to Break

Two changes for whoever has to run AAI itself:

  • OpenShift container images. Broadcom now offers official images with an auto-configured, single-instance setup. That means less manual installation, and you keep your existing external database. The traditional install and upgrade paths are still supported.
  • AI-assisted security scanning. In its v26 announcement, Broadcom says this is the first AAI release to use frontier AI models to scan source code for vulnerabilities and fix them before general availability, on top of its existing security testing.

Where to Start

If you already run AAI, put the v26 upgrade on your plan and pick one business unit for a showback pilot. If you don’t, start with the question you can’t answer today. What does month-end actually cost? Which job chain misses its window most often? Those answers tell you whether AAI belongs on your roadmap.

Either way, the fastest way to see it is Jennifer Chisik’s session. Jennifer is Broadcom’s Automation Analytics & Intelligence product manager, and the session runs 19 minutes, which is shorter than most status meetings: Powering Proactive Automation: What’s New in Broadcom AAI v26.

Want a second opinion on your own numbers? Bring your SLA headaches and your cost questions to a free 30-minute call with our team. Just a straight conversation about where you stand. Book a Free Call.

Not Sure What Your Automation Costs?

RMT helps AutoSys and Automic teams see where AAI fits, starting with a look at the numbers you have today.