I use Automic Workload Automation for SAP-related use cases. They are primarily functional and nonfunctional job executions for SAP Windows Unique. So, mainly for a business process or business functions, job execution, and creating dependencies related to retail like Oracle and SAP jobs execution.
I like that Automic Workload Automation has many features compared to other products. There are a lot of good features, and architecture-wise there is a valuable client concept. The architecture and the multi-tenancy is a multi-client concept. That is also useful.
The manage file transfer area could be better. The file transfer area needs improvement. Other products like Control-M have some good features in this area.
I have been working with Automic Workload Automation for the last ten years.
Automic Workload Automation is a stable solution. It's good because, architecture-wise, it has high reliability. So, we recommend it to our customers and ask them to use two or three-node architecture. If one goes down, the other should be up. So, two or three-node architecture is stable.
Automic Workload Automation is a scalable solution. Scalability depends on the architecture. We are currently running 10,000 jobs or 20,000 jobs with two-node architecture. If we want to add one node or if we're going to add more resources, you can do it online. You do not need any downtime. You can run thousands of pages and millions of jobs.
Technical support is good. I worked with a particular dedicated client, and we had to reach out to Broadcom once or twice a month for help. Whenever we raised a ticket, they responded within a day or the next day. Most of the time, it wasn't even an urgent issue.
Nowadays, they have very helpful knowledge articles. If I have an error and they share some knowledge articles, I get the solution through those articles. They are helpful.
The initial setup is straightforward. It hardly takes half an hour or one hour, but small components like agents must be installed later. The initial fresh installation will take about one hour.
I'm not sure about licensing costs, but I know the base price is about $3,000, and you can get some kind of discount per node.
I would tell potential customers that they must use third-party software like Control-M, Stonebranch, AutoSys, or Tidal to migrate to Automic Workload Automation.
If we compare it to any market-leading software, like Control-M BMC, Automic has the same capability, but Automic provides everything as a bundled product. Others like BMC sell their products in different modules. So, you have to buy the license, and on top of that, you have to buy the separate modules.
I would also tell potential users that with competing products, they need a job-based license if they plan to scale up and avoid penalization. But as Automic is node-based, there will be no penalty if you are running 5,000 jobs today and 6,000 jobs tomorrow. It'll be the same.
On a scale from one to ten, I would give Automic Workload Automation a seven.