"MAS is by far the best feature, although not a feature of the software specifically. MAS has more knowledge than our employees, so we have been able to develop schedules that are far beyond our own skillset."
"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."
"Reliability is always important, and the reliability of the system is outstanding."
"File Watcher can run jobs when files are made available in a folder."
"With a simple click of a button in self-service, the department or the user can complete his/her job."
"Often times there are criteria that cannot be determined by the system, which allows a human to make the determination and use the Self-Service Solution Manager to trigger a job."
"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."
"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."
"The most valuable feature of this solution is the functions are easy to use."
"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."
"AutoSys Workload Automation is a stable solution."
"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."
"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."
"The initial setup is easy."
"This solution has made my clients' workplaces a lot less labor-intensive."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good."
"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."
"One of the most valuable features is automation. We are doing automation infrastructure, which allows us to automate regular tasks. This solution provides us with a service catalog, like building new services and automating daily tasks."
"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."
"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 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."
"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."
"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."
"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."
"The products are extremely powerful and capable. Anytime you have such capability, the programming/configuration that goes into making it work can be complicated."
"Stability is an area for improvement. There are FTP agents that run on the MCP and they are there so that we can transfer a file from the MCP to the Windows environment or vice versa. Sometimes, and nobody has been able to figure out why, it just goes down, and all of my jobs that need it are hanging or failing... It would be very helpful if they could figure out what in the world is happening with that FTP client that's on the MCP."
"There are some limitations in the actual jobs that are created and how you're able to rename files. Suppose you're bringing in, say, 10, 15, or 20 reports from a core system, and you're using an "asterisk character" to identify files. For example, if you're grabbing files that start with this, end with this, but the characters in between could be different, it has to retain that same name in the destination. It won't allow you to rename them with a date stamp or the like."
"We are still in the early stages of our implementation, so at this point, I cannot see any needed improvements or features."
"Enterprise Manager is a little clunky which I know they're addressing in the solution's manager."
"We would like a display of the created date, created by, and last modified date, as well as modified by."
"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."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"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 graphical interface can 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."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"The solution could improve by having support for container environments."
"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."
"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."
"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..."
"We would like support for the post-integration of this product before cloud frameworks because right now their approach is to avoid using on-premises activities and move everything to the cloud."
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 6th in Workload Automation with 9 reviews while Red Hat Ansible Automation Platform is ranked 2nd in Configuration Management with 6 reviews. AutoSys Workload Automation is rated 7.4, while Red Hat Ansible Automation Platform is rated 8.6. 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, IBM Workload Automation, CA Workload Automation ESP, Automic Workload Automation and BigFix, whereas Red Hat Ansible Automation Platform is most compared with Microsoft Endpoint Configuration Manager, Red Hat Satellite, VMware vRealize Automation (vRA), Microsoft Azure DevOps and Micro Focus Operations Orchestration.
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.
