We performed a comparison between AutoSys Workload Automation and VisualCron based on real PeerSpot user reviews.
Find out in this report how the two Workload Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"It seems like it would scale well."
"The most valuable feature is the automation in general."
"Thus far we have only had a few minor problems, all of which the vendor addressed quickly. We have not encountered any major problems. The product is very stable and reliable."
"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 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."
"Last year, we added a second environment and the OpCon Deploy product. This has allowed us to build a testing environment. This has been a great addition for us as we can work through our workflows without disrupting our production environment."
"With a simple click of a button in self-service, the department or the user can complete his/her job."
"To me, what's most valuable in AutoSys Workload Automation is its robustness and quickness. The tool can trigger jobs within a few milliseconds, and it can handle large volumes of jobs."
"AutoSys Workload Automation is a stable solution."
"The solution has been stable."
"The initial setup is easy."
"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 scalable."
"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."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good."
"What I like about VisualCron is that like its name, it's a very visual tool. In my previous company, there were a lot of scripts for all kinds of services, and through VisualCron, you get to group all flows and get a nice visual overview. VisualCron also has an alerting feature, so you receive alerts from it. VisualCron makes everything clearer and easier to maintain. Every other solution that I was looking for almost always needed a programmer, but with VisualCron, you can do what you need to do without programming skills, so this is another valuable feature of the tool."
"What I found most beneficial from VisualCron is that you can directly connect it with different databases, user accounts, and credentials. You can run queries from one machine to another using the credentials, unlike PowerShell, that's run by the machine itself. With VisualCron, you can directly ask other machines and run requests through user credentials. Suppose you have an AWS or Azure environment. In that case, you can maintain the connection between on-premises and cloud-based machines, which is the type of setup in the organization I'm working for. You can directly call some of the services via VisualCron on your local on-premises machine, and I found that an excellent feature of the tool."
"We don't have to do any coding. We just plug and play and it works."
"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."
"Upgrading to newer versions remains complex."
"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."
"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."
"The logs are a little daunting to look at the first few times, however, as you begin to understand what you're looking at, it becomes easier."
"I would like to see OpCon being accessible using a mobile app."
"Enterprise Manager is a little clunky which I know they're addressing in the solution's manager."
"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."
"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."
"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."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"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."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"The reporting system, currently, could be better."
"The solution could improve by having support for container environments."
"The only problem I face when I use the tool is that it doesn't contain much documentation or it doesn't have many video tutorials on its features."
"I want to improve the UI in VisualCron, as it's not as user-friendly, particularly when setting up the task scheduler. If you're familiar with the tool, then no problem, but if not, you'll have a problem typing text because sometimes, the cursor points to other places, so there's an issue with text box alignment in VisualCron. That was painful for me when I was just a VisualCron novice, but when you become used to it, there won't be a problem."
"An area for improvement in VisualCron is its cluttered interface. It isn't always easy to find all functionalities, so what VisualCron needs is a user interface expert who can improve the interface. There's a learning curve in terms of finding what you need from the interface of VisualCron. The technical support for VisualCron also needs improvement in terms of response time. Currently, there's no live support or hotline you can call to get quick answers, so this is what I'd like to see in the next version of VisualCron. A less cluttered and more streamlined interface, where you don't need to hunt for some of the features, is also what I'd like to see in the next VisualCron update."
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 4th in Workload Automation with 10 reviews while VisualCron is ranked 12th in Workload Automation with 3 reviews. AutoSys Workload Automation is rated 8.0, while VisualCron is rated 8.0. The top reviewer of AutoSys Workload Automation writes "Robust, quick, and can trigger jobs within a few milliseconds, but lacks advanced workflow-related features found in its competitors". On the other hand, the top reviewer of VisualCron writes "Has many features and plugins but it's not easy to set up". AutoSys Workload Automation is most compared with Control-M, IBM Workload Automation, Red Hat Ansible Automation Platform, CA Workload Automation ESP and CA Workload Automation CA 7, whereas VisualCron is most compared with Microsoft Power Automate, Control-M, UiPath, WinAutomation by Softomotive and JAMS. See our AutoSys Workload Automation vs. VisualCron report.
See our list of best Workload Automation vendors.
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.
