CA Technologies today announced the general availability of CA Workload Automation 11.3, which provides the ability to initiate, monitor and manage workloads in private, public and hybrid clouds for increased agility and better business outcomes.
Supporting an expanded breadth of applications and events, this new version of CA Workload Automation also enables workload cloud bursting and dynamic workload placement that was first demonstrated at VMworld Europe last October.
“Organizations understand that it’s cost-prohibitive to maintain dedicated infrastructure to support peak demands in workload processing. As a result, many of the world’s largest enterprises use CA Workload Automation to process millions of business transactions daily to more cost-effectively run their businesses,” said Roger Pilc, general manager, Virtualization and Automation, CA Technologies. “The new capabilities in this version provide the increased agility customers need to keep up with their ever-growing business demands, and to process more workloads reliably and cost-effectively on all platforms and in all types of environments.”
Key capabilities in CA Workload Automation 11.3 include:
• Support for new applications: CA Workload Automation’s deep integration into the application stack allow for the detection of business events that trigger workloads. Specific enhancements have been added that extend support for managing workloads for web services, J2EE, relational databases, and other components. This deeper integration reduces the need for customers to use costly scripts and other custom integration methods.
• Dynamic workload placement: CA Workload Automation enables customers to quickly move and process workloads in different cloud environments when demand for processing spikes. This makes it possible through dynamic workload placement, enabling customers to quickly provision and process workloads from a physical infrastructure to a virtualized private cloud or to a public cloud such as Amazon EC2.
• Self-service for workload management: CA Workload Automation extends its self-service interface and gives end-users the ability to request and execute workload processing controlled by workload policy and governance processes. End-users no longer need to depend on administrators to make changes as they are now empowered to manage their own workload processing. This helps provide higher levels of efficiency and control, while giving the business more control over their own services.
• Release management for workload automation: CA Workload Automation now automates the process of moving workloads from test and development environments into production. This is done using a policy-driven approach that includes automatic migration of complex configurations from development to production. A large financial institution was able to reduce this process from two weeks to just 20 minutes using the new version of the product.
CA Workload Automation 11.3 reinforces CA Technologies broad application management capabilities, which include configuration management, capacity management, discovery and dependency mapping, performance management, and self-service and administrator provisioning. This growing set of solutions helps customers optimally match dynamic applications and their workloads to increasingly dynamic and virtualized IT infrastructure in a ‘just-in-time’ manner.
“This release of CA Workload Automation adds important new capabilities for customers looking to process a broader set of workloads, and to do so in the cloud,” said Tim Grieser, program vice president, Enterprise System Management Software, IDC. “Dynamic workload management will help customers utilize public, private and hybrid cloud resources to optimize service delivery.”
The Latest
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.
The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...