Michelle LestrangeData Center Manager at a insurance company
Anonymous UserAutomation Manager at a financial services firm
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"Auto-scheduling is the most valuable feature. We have the ability to schedule [batch jobs on our Unisys mainframes] seven days in advance, so we know exactly how we're running every night."
"The most valuable feature is the self-service because it has made it possible to provide simple and quick solutions in the handling of certain tasks."
"There's also a self-service solution manager... that allows us to enable staff to run complex automation tasks by clicking a button and entering some information. They don't have to have access to the OpCon environment to kick off those kinds of events."
"Previously, we would receive a file from a vendor, then we would have to go through and make changes to individual accounts in our core system. There are probably between 10 to 20 accounts any given week. It probably took around five minutes for it to run through the report and make all the changes, and that was if there was nothing complicated with all very straightforward changes. Now, that is done in 30 seconds."
"There are three features which are valuable: the automated calendar functions; the notification process for failed jobs or unscheduled events occurring, via email and text messaging; and the ability for the scheduling package to communicate across multiple platforms."
"It has also helped to streamline our operations. We contract out our collection department so they are no longer housed on our system. They're housed on another platform. OpCon is able to not only pull in our data, but it also, on a daily basis, updates that third-party."
"Manual processing has been automated 99 percent by OpCon. With new processes, we give it at least two weeks manual so we can write down the details of how to do the steps, then we automate it. Within a month, it has been automated, then it's no longer a manual process."
"One of the advantages of OpCon is the ability to use the API and web services. We couldn't do that with our previous solution. We have been able to change our procedure for ticketing. When a job is down, we can immediately create a ticket from OpCon in our ticketing solution, which is ServiceNow, using the web services."
"Technical support from IBM is very good."
"The technical support is great, the product is easy-to-use, and it is stable."
"The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions."
"The whole product is valuable because it is a tool for batch automation."
"For us, the calendaring system is very robust. Some of the teams have very specific requests for when they need jobs to run. That's been really valuable, because a lot of times, when people run scripts, if they run on a holiday, they're going to fail... A couple of times a month it probably saves us work and the necessity of logging in from home and checking to make sure everything's okay."
"Especially in the newer versions of Tidal, the segmentation of user permissions enables us to give people operator permissions for their jobs, to rerun jobs, but view-only for other groups' jobs. We're able to keep people from hurting themselves or other groups accidentally. The permissioning is really good."
"We use the solution for cross-platform, cross-application workloads. The solution’s ability to manage and monitor these workloads is very easy and accurate. We have file dependencies for running jobs. The job does not start until a file exists on a completely different server, then where the job will run. So, it is cross systems."
"It saves times due to automation. With some files, we do hundreds a day for a particular vendor. This would be hard to do manually. Also, the speed at which we can do this is excellent."
"We wouldn't be able to do many of the complex scheduling that we do today without it. For us, it is a mission-critical app. Because if it doesn't work or has a problem, then SAP doesn't function. It is that critical. So, it's an essential tool for us to manage and run SAP jobs."
"The first, big thing that we got out of using Tidal Workload Automation was having a centralized view of the status of all of our batch processes across all these systems... We can look into the schedule at any given time and see if things are running on track or if they are falling behind. We can also see if something failed."
"With the varied features in the varied adapters provided, we use Tidal Enterprise Scheduler because we want everything to be scheduled in one place. Tidal provides that for us with its tools and varying platforms in our organization. Tidal provides all the connectors to the platforms. This is very useful because we don't want to look for another scheduler for scheduling certain jobs. We don't want to look at those schedules manually between platforms."
"Tidal helps administrators and users to see the information that is relevant to them in that single pane of glass. They can see jobs running, they can see job history, and they can see job progression. If you look at alternatives like Airflow and clouds, you'd have to design your own UI to monitor the progress of the different jobs that you've created in Airflow. So Tidal is huge for us."
"Do your first install, your first upgrade, with SMA. It's simple, it's as per the manual, as per the training, but you need that little bit of confidence."
"The ability to retrieve information from logs in variables to display relevant information would be helpful."
"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."
"What can get complicated is if you're doing anything more than just the built-in jobs. If you're using the more advanced features, troubleshooting becomes extremely complicated."
"The calendar interface and the frequency interface is a very powerful, yet complex, section of OpCon in which all our staff have made mistakes. They have implemented what they believed was logically correct and then afterward discovered that their logic was flawed because OpCon did it a different way. That part, which is incredibly useful, is also incredibly dangerous. The interface or the ability to directly do more functions within the frequency definitely has room for expansion. As good as it is, it can be a lot better."
"Usage is a little complex. It's not like you can bring somebody in and they can just use it. They have to be trained... As far as complexity goes, it's right up there."
"There is some difficulty with the ease of use when I don't have some of the templates that were already created. More templates would be great. Non-core featured templates are my biggest struggle."
"I would like to see them improve the Solution Manager for the web application. It's the future for us. Our customers need a lot of functionality, but there isn't that functionality within Solution Manager. So they have to develop and improve it."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"It should support other schedulers that aren't IBM products."
"There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools."
"I don't know if Tidal wants to get into the business of monitoring long-running jobs, but that could be a feature for the future: a job launching and monitoring tool. Using Tidal for monitoring doesn't seem like a good fit, but if they could offer something that did that as an add-on or include it, it might be helpful."
"I know they are working on it, but there needs to be better reporting. Currently, there are only three or four reports that we can get off of the system. That needs to be improved. They already have a solution to this in the new version. I.e., a schedule of all the jobs running for one day, specifically calling out what dependencies that job relies on. It would be like a flow chart of how the day's jobs would run."
"I would like more involvement with the cloud."
"One of the weaknesses of the product is, when something happens, it's difficult to find out the root cause. There are a lot of logs you can take a look at in Tidal. Sometimes, they are useful, but other times, they're not. That is mostly relegated to the administrative team. Users for the most part don't see that and don't know anything about that. They just know they have a problem, then it's up to the administrative team to see what happened and figure out the problem."
"Their software installation and update process could use some improvements. I'm pretty sure they're working on that, but that's definitely an area where it could be streamlined a lot. There's still a lot of manual work that you have to do with the schedule when you deploy masters or do the agents."
"With the client, we have had certain issues. The user interface for Tidal is a little slow. A lot of people would love this tool if they had a faster user interface. The drill-down functionality should be much quicker than what it is pulling out now. If I fill out some data, then it takes awhile to get that data back onto the screen. It's not as fast as we were expecting."
"One area for improvement is the command-line interface and the API to bulk-load jobs. It's a little bit kludgy, but we still manage without it. They're working on it and it's getting better all the time. In addition, the documentation for their API for creating jobs needs to be updated. It's a bit of a learning curve."
"It takes a lot of time to learn the product. I have admins and developers who are working on the products for the last three to four years and still don't know all the functionalities. Tidal has really great things about it, but people are focused on their day-to-day job and the solution is not intuitive."
"This solution is certainly not the cheapest, but we win in time."
"OpCon cost us $80,000 in 2017 money, and that included everything: support, installation, onsite assistance during the conversion, etc. It's been a worthwhile investment by far."
"Yearly, it's around $30,000."
"Our licensing is on a yearly basis."
"Our license is for 1000 jobs. Including support, the license and upgrades are 2000 euros a month."
"Yearly, we're paying about $62,000. OpCon has an all-inclusive feature and module license, but you pay per task."
"Our annual maintenance costs are $45,000. The initial cost is separate."
"On a yearly basis our cost is between $25,000 and $30,000."
"It is about one-third of the cost of a controller."
"The new prices that we've received seem reasonable and comparable to the marketplace."
"We pay maintenance annually through Blue House of about $9,000. That's for our two environments: production and test."
"The pricing is pretty reasonable. That seems to help a lot versus other companies. There are no other fees aside from the standard licensing fees. There are other products out there where you pay based on how many jobs you run and so on, and I know that's very frustrating for users."
"The solution’s licensing model in terms of its flexibility and transparency regarding costs is pretty good. A person can buy the license, and if you decide to stop support, you can do that but still have the product. So, it's not like you're paying constantly to keep that license alive. Certainly, you want to keep support going too. Once you buy it, you own it. It's not like I have to keep paying somebody to keep using it."
"If you are willing to shop around to other vendors, you can possibly get a good price on your support license."
"Our annual maintenance cost is competitive for what we have and what they do."
"There are project, system, and server costs. Some of the things that they are doing is introducing new products. They are introducing what they call their Repository, which is a way for you to move a job. That doesn't cost anything to us, because it is reusing a tool called Transporter. The repository is the successor to Transporter, so we already own it and are sort of grandfathered in. But that new product requires a server and database, so now we have to go out and get a server and database. So, there is a cost there."
"...it is a pretty affordable scheduler tool that lets us do a lot. You get a lot of bang for the buck... The licensing model is hugely flexible."
OpCon is a robust and flexible platform capable of scaling up to meet the needs of clients running 140,000+ daily jobs across multiple environments and operating systems. Our proven migration framework helps clients painlessly transition from outdated or cost inefficient platforms thanks to our deep organizational expertise, REST API, and extensive library of legacy connectors. We have a variety of consulting options available for clients and offer no-cost training for the life of the contract.
Tidal Software is a leading provider of enterprise workload automation solutions that orchestrate the execution of complex workflows across systems, applications and IT environments. With a comprehensive portfolio of products and services, Tidal optimizes mission-critical business processes, increases IT cost efficiencies and satisfies legal and regulatory compliance requirements. Hundreds of customers around the world count on Tidal for modernizing their workload automation and driving their digital transformation. Tidal Software is headquartered in Chicago with offices in Houston, London, Minsk, Belarus and Chennai, India. For more information, visit tidalsoftware.com.
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.
IBM Workload Automation is ranked 9th in Workload Automation with 4 reviews while Tidal Automation is ranked 4th in Workload Automation with 15 reviews. IBM Workload Automation is rated 8.0, while Tidal Automation is rated 8.4. The top reviewer of IBM Workload Automation writes "Workload automation that helps track productivity and progress across platforms". On the other hand, the top reviewer of Tidal Automation writes "Gives us the ability to see everything across our scheduling universe, without having to access multiple systems". IBM Workload Automation is most compared with Control-M, AutoSys Workload Automation, Ansible, HCL Workload Automation and ASG-Zena, whereas Tidal Automation is most compared with Control-M, AutoSys Workload Automation, Automic Workload Automation, ActiveBatch Workload Automation and ASG-Zeke. See our IBM Workload Automation vs. Tidal Automation 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.