We performed a comparison between AutoSys Workload Automation and Red Hat Ansible Automation Platform based on real PeerSpot user reviews.
Find out what your peers are saying about BMC, Tidal Software by Redwood, Redwood Software and others in Workload Automation."It has improved my organization by automating IT applications."
"The ability to create calendars, calendering for batch jobs to run on a scheduled frequency."
"Automation of patch process."
"It scales very well. We can add jobs and remove jobs. We do not have problems maintaining the product across multiple environments and multiple servers."
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"I find that it provides better agility in regards to job execution features."
"The most valuable features of AutoSys Workload Automation are the file transfer protocol and file watcher. The solution has a user-friendly user interface. It is very simple to use. You have a scope of all your jobs, jobs are what you call tasks that you will automate in the solution. It lets you monitor everything in these jobs."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"The most valuable feature of the solution is that we don’t need an agent for it to work."
"The automation is the most valuable feature."
"It enabled me to take the old build manifest and automated everything. So when it came time to spin everything up, it was quick and simple. I could spin it up and test it out. And then, when it came time to roll production, it was a done deal. When we expanded to multiple data centers, it was same thing: Change a few IP addresses, change some names, and off we went."
"I like the fact that Ansible is agentless."
"The most valuable feature of Ansible is repeatability because when you're working at the DoD, you want things to be cookie-cutter and replicable."
"It was easy to read and learn. It is a YAML-based syntax, which makes it easily understand and pick up."
"RBAC is great around Organizations and I can use that backend as our lab. Ingesting stuff into the JSON logs, into any sort of logging collector; it works with Splunk and there are other collectors as well. It supports Sumo and that helps, I can go create reports in Sumo Logic. Workflows are an interesting feature. I can collect a lot of templates and create a workflow out of them."
"It is agentless. I don't have to think about which client system my unit has understanding in or not, because I can execute from my system. It will go and configure it, and any module that it is looking for will be shipped out."
"They could do better supporting it. They have too many of the same type of products, so sometimes it doesn't get as much attention as it should."
"Reduce the number of operational files. This would make the job of a system programmer supporting ESP easier."
"The visibility and control features are somewhat limited."
"CA installation processes are never anything but complex."
"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"A better graphical user interface, because we have a lot of people using the client utility, and we want to get them away from that."
"The solution does not have a friendly subscription model because it forces users to take a five-year subscription simultaneously, charging millions of dollars."
"The solution requires some Linux knowledge."
"What I would like to see is a refined Dashboard to see, when I log in: Here are all my jobs, here are how many times they've executed; some kind graphical stitching-together of the workflows and jobs, and how they're connected. Also, those "failed hosts," what does that mean? We have a problem, a failed host can be anything. Is SSH the reason it failed? Is the job template why it failed? It doesn't really distinguish that."
"The communication on it is not probably where it could be. We could use some real life examples where we could point customers to them and say, "This is what you are trying to do. If you follow these steps, it would at least get you started a bit quicker.""
"There are some options not available in the community edition of the solution."
"The support could be better."
"Because Ansible is establishing SSH sessions to perform tasks, there is a limit on scalability."
"The governance features could be improved."
"The solution is slightly expensive, and its pricing could be improved."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
AutoSys Workload Automation is ranked 6th in Workload Automation with 79 reviews while Red Hat Ansible Automation Platform is ranked 1st in Configuration Management with 62 reviews. AutoSys Workload Automation is rated 8.4, while Red Hat Ansible Automation Platform is rated 8.6. The top reviewer of AutoSys Workload Automation writes "Helps us manage complex workloads, reduce our workload failure rates, and save us time". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Its agentless, making the deployment fast and easy". AutoSys Workload Automation is most compared with Control-M, IBM Workload Automation, Automic Workload Automation, Stonebranch and CA 7 Workload Automation Intelligence, whereas Red Hat Ansible Automation Platform is most compared with Red Hat Satellite, Microsoft Configuration Manager, VMware Aria Automation, Microsoft Azure DevOps and Cisco DNA Center.
We monitor all Workload Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.