"Having the jobs laid out while attaching dependencies is a nice addition to the program."
"We're also starting to use its Self Service and Solution Manager. My team in the data center and some of the development team use the Self Service. Developers are using the Self Service for upon-request jobs for their testing. They used to have to go through us to schedule testing and now they can just go on and kick it off all they want. They have also really appreciated that they have access to view and/or submit jobs."
"For us, the most valuable feature of the solution is the file transfer piece and being able to automate the moving of files around between our various vendors. It reduces the time involved versus somebody having to individually move the files around."
"The biggest example in which OpCon has improved my organization is that we have to download and process files from the federal reserve several times a day. If we don't do it in a certain timeframe, we can be penalized. It's the fact that we can download these files, process them, get our accounting teams the information they need to work the exceptions that is one of the most important roles."
"It makes everything simpler. Once OpCon is in, it just repeats itself day after day. We don't have to worry about whether a process will be missed. It will run every single time. We are not dropping jobs or missing stuff. When you have multiple institutions, it's very easy to miss jobs. You get on a roll, start doing things, and then forget somebody. With OpCon, everything is done."
"The end code response allows us to evaluate how a process finished, set the termination/end code appropriately, and then trigger further processing based on how it ended."
"File Watcher can run jobs when files are made available in a folder."
"There are a lot of valuable features. The version that we're currently casting, Self Service, is going to be the most valuable to us. It is going to allow us to open up the doors, broaden our automation capability and help other business units to be able to automate a lot of the little things that they do from day to day. I'm really looking forward to being able to help other areas with their automation needs. Self Service is really key."
"The features that I have found most valuable with AutoSys are that it is scalable, easy to use, fast, and always available. That's very important because if it's not steady then it's a real problem. So, at this point, we are satisfied with it."
"AutoSys Workload Automation is a stable solution."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good."
"It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task."
"This solution has made my clients' workplaces a lot less labor-intensive."
"The most valuable feature of this solution is the functions are easy to use."
"Easy configuration and integration with SAP."
"Ansible is agentless. So, we don't need to set up any agent into the computer we are interacting with. The only prerequisite is that the host with which we are going to interact must have the Python interpreter installed on it. We can connect to a host and do our configuration by using Ansible."
"Being a game-changer in configuration management software is what has made Ansible so popular and widespread. Much of IT is based on SSH direct connectivity with a need for running infrastructure in an agentless way, and that has been a big plus. SSH has become a great security standard for managing servers. The whole thing has really become an out-of-the-box solution for managing a Unix estate."
"Ansible provides great reliability when coupled with a versioning system (git). It helps providing predictability to the network by knowing exactly what's being pushed after validating it in production."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"The FICS integration is a little bit clunky. We've had some tickets with their support team, and sometimes they couldn't figure it out, but that probably has more to do with FICS than with OpCon."
"It would be great if you could create physically separate "clients," as I call them. I wish I could have a production client and a testing client and that they would be separate."
"There is room for improvement needed around setting up the calendars and frequencies. I would like more flexibility in what jobs run. Sometimes, with frequencies, I can't find what I want to without putting a little more labor into it."
"A way to select multiple jobs in the UI for a quick change or to hold, release, et cetera, would be nice."
"We are still in the early stages of our implementation, so at this point, I cannot see any needed improvements or features."
"More functionality within self-service would be greatly appreciated."
"Licensing would be the first part I would overhaul. Each time a new licensing paradigm comes out, more features are removed and costs are added. They "add" features that are rarely used and increase charges for the number of jobs run. I'm sure someone in finance got a raise for their brilliance but the end-users won't thank them one bit. Expect price hikes and threats when you hold them to account at every opportunity."
"We would like a display of the created date, created by, and last modified date, as well as modified by."
"I am not sure whether it is our limitation or a tool limitation because we haven't yet explored it, but whenever we look for different types of reporting, we have some limitations in getting those. It could be because of the way we have set it up internally in our enterprise, but it would be helpful if we can customize the reporting features and some of the alerts that can go out. When we connect enterprise systems, each one looks for a different use case, and if we can get different types of reporting, it will be helpful."
"The solution could improve by having support for container environments."
"Quick search feature and job analysis could be improved."
"We are trying to see if we can use this from a cloud perspective with AWS, Azure, and other clouds, but it seems that there is no cloud integration in this product. We would like to see cloud integration. We are very pleased with this solution, but we are moving our application to the cloud, and we found out that it doesn't support any cloud features. So, we are trying to find a replacement."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"The graphical interface can be improved."
"The area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules."
"When you set up Playbooks, I may have one version of the Playbook, but another member of the team may have a different vision, and we will not know which version is correct. We want to have one central repository for managing the different versions of Playbooks, so we can have better collaboration among team members. This is our use case for using Git version control."
"Some of the modules in Ansible could be a bit more mature. There is still a little room for further development. Some performance aspects could be improved, perhaps in the form of parallelism within Ansible."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Automate repetitive tasks so you can focus on projects that drive your business forward. Find out how OpCon workload automation enables you to create repeatable, reliable workflows - all managed from a single platform.
AutoSys Workload Automation is ranked 5th in Workload Automation with 8 reviews while Red Hat Ansible Automation Platform is ranked 2nd in Configuration Management with 5 reviews. AutoSys Workload Automation is rated 7.2, while Red Hat Ansible Automation Platform is rated 8.4. The top reviewer of AutoSys Workload Automation writes "Mature, reliable, scalable, and helpful for orchestrating jobs". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Enables us to efficiently manage an almost unlimited number of nodes". AutoSys Workload Automation is most compared with Control-M, Automic Workload Automation, CA Workload Automation ESP, IBM Workload Automation and Stonebranch Universal Automation Center, whereas Red Hat Ansible Automation Platform is most compared with Microsoft Endpoint Configuration Manager, Red Hat Satellite, VMware vRealize Automation (vRA), BigFix 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.
