We performed a comparison between ActiveBatch Workload Automation and Control-M based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: ActiveBatch Workload Automation is highly praised for its versatility and ease of use. Users appreciate the prebuilt jobs, scheduling, monitoring, and alerting mechanism provided by the software. It is also commended for its scalability and intelligent automation features. Control-M stands out in areas such as Managed File Transfer, credentials vault, integration capabilities, Role-Based Administration, collaboration, and forecasting. Users find the software to be particularly useful for these functionalities.
ActiveBatch improvements include managed file transfer, subscription model transition, cloud aspect, interface, crashes, triggers, monitoring dashboard, price, documentation, help center, setup process, email alerts, lag/stability issues, customization options, and customer support. Control-M needs enhancements in microservices, API integration, web interface, testing/quality assurance, reporting, customization, upgrade process, distributed architecture, third-party tool integration, FTP job logs visibility, and QA testing.
Service and Support: ActiveBatch Workload Automation has been praised for its customer service, with users appreciating the helpful, reliable, and responsive support team. Control-M has received mixed feedback. Some customers have praised the prompt and knowledgeable support team, while others have faced slow response times and a lack of proactive assistance.
Ease of Deployment: The setup process for ActiveBatch Workload Automation was smooth and uncomplicated. Nevertheless, there is a minor requirement for additional instructional material when importing files. Control-M had a direct setup procedure, although a few users mentioned a learning curve and the necessity to manually convert jobs and scripts.
Pricing: ActiveBatch Workload Automation is highly regarded for its flexible and reasonably priced setup cost. Users appreciate the ease and speed of the process. Control-M's pricing and licensing elicit varied opinions, with some users considering it costly and perplexing.
ROI: ActiveBatch Workload Automation has proven to be highly effective, leading to substantial financial gains for users. It has resulted in a significant boost in net revenue. Control-M offers a more cost-effective solution, improving overall efficiency and providing advanced automation features.
Comparison Results: ActiveBatch Workload Automation is the preferred product over Control-M according to user reviews. It is praised for its simplicity and ease of use during setup. ActiveBatch offers more versatility and ease of configuration, with prebuilt jobs and a user-friendly interface. Its pricing is considered reasonable and competitive, especially for smaller companies.
"The automation feature is a very valuable feature as the associates do not have to worry about performing repetitive tasks (i.e. endpoint security scans on a daily basis) that would take several hours to complete on a daily basis."
"From a scheduling point of view, it is pretty good."
"It is very useful in sending confidential files through FPP servers."
"The user interface is really incredible."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"Error Handling is one of the best standout features of ActiveBatch."
"By implementing a sophisticated scheduling mechanism, the system allows for the precise triggering of jobs at user-selected frequencies, enabling a seamless and automated execution of tasks according to specified time intervals."
"One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable"
"Speeds up processes and automated tasks."
"Automation of the batch jobs is the most valuable feature."
"Control-M provides us with a unified view, where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. It also provides the ability to filter. So, if I don't want to see everything, I can also narrow it down or open ViewPoint. This is very important since we have thousands of jobs to monitor. If we did not have this ability, it would be very difficult to see what is going on."
"The ability to integrate file transfers has been instrumental in allowing us to accomplish the things we need with Control-M. In our industry, we take a lot of data and either push it down to the stores or retail grocery stores. We take files and push them down to the stores or pull files and information from the stores and bring it back to corporate. So, it's two-way communication with file transfers. One of the bigger things that we do with Control-M is scheduling data moves and moving data from one location to another."
"It is simple to create, integrate, and automate data pipelines and to ingest data from different platforms. It integrates well between platforms."
"The best part about this product is that it has a lot of features. Control-M doesn't limit us and we can use it for a lot of things."
"As soon as you have an issue, a ticket is created and the tech support is quite responsive."
"If they have ad hoc requirements, then they can theoretically schedule their own file transfers with the Self Service. We are trying to push as much work back to the customers or developers that have that requirement, because they prefer to help themselves, if possible. We try empowering them and enabling them through Control-M, especially for file transfers, because it is a much broader base of the business then just with batch scheduling. Typically, with SAP batch scheduling, it would work with dedicated teams. With file transfers, the entire business is involved. There are business users, end users, etc. It definitely needs to be as simple as possible and as managed as well as possible. They need to manage it themselves, if possible, because our team is not growing but the number of customers, applications, and jobs are growing. We need to hand back some of the responsibility to the customer for them to resolve and action it."
"They should offer pricing that is more affordable."
"I can't get the cleaning up of logs to work consistently. Right now, we are not setup correctly, and maybe it is something that I have not effectively communicated to them."
"The thing I've noticed the most is the Help function. It's very difficult, at times, to find examples of how to do something. The Help function will explain what the tool does, but we're not a Windows shop at the data warehouse. Our data warehouse jobs actually run on Linux servers. Finding things for Linux-based solutions is not as easy as it is for Windows-based solutions. I would like to see more examples, and more non-Windows examples as well, in the Help."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"The documentation is very limited, and it can be improved."
"As more organizations are moving towards a cloud-based infrastructure, ActiveBatch could incorporate more capabilities that support popular cloud platforms, such as AWS, Azure, and Google Cloud."
"Whenever there is an overload, we are seeing crashes happening."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"The infrastructure could be improved."
"An issue we have run into in our lower environments is that Control-M can log you out frequently."
"They can improve their interface."
"With earlier versions, the support was not accurate or delivered in a timely manner. What would happen is that I would be in production mode and I would have an issue and would want to get someone on a call to see what was happening. But they would always say, “Hey, provide the log first and then we'll review and we'll get back to you." I feel that when a customer asks about a production issue, they should jump onto the call to see what is going on, and then collect the logs."
"We develop software. More frequently, we are working with microservices and APIs, using our integration tool, MuleSoft. While Control-M is really a good tool to integrate with other tools, it is important for them to continue improving their microservices and API."
"I would like to see them adopt more cloud. Most companies don't have a single cloud, meaning we have data sources that come from different cloud providers. That may have been solved already, but supporting Azure would be an improvement because companies tend not to have only AWS and GCP."
"But for some issues, BMC will suggest to upgrade to new version which will not be feasible to standards of the organisation. Hence some work around should be shown to run the business until new version was upgraded."
"Control-M reporting isn't that good. It is very limited. We would like the ability to create our own reports as well as the ability to publish dashboards in the cloud, which would help us. Improved reporting will help us determine statuses and get the answers that we need. However, I personally think BMC is not focusing on the reporting. I have even visited the BMC office in India, and asked, "Why haven't you improved the reporting?""
ActiveBatch by Redwood is ranked 6th in Process Automation with 35 reviews while Control-M is ranked 4th in Process Automation with 110 reviews. ActiveBatch by Redwood is rated 9.2, while Control-M is rated 8.8. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, the top reviewer of Control-M writes "We have seen quicker file transfers with more visibility and stability". ActiveBatch by Redwood is most compared with AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs, VisualCron and IBM Workload Automation, whereas Control-M is most compared with AutoSys Workload Automation, IBM Workload Automation, Rocket Zena, ESP Workload Automation Intelligence and Automic Workload Automation. See our ActiveBatch by Redwood vs. Control-M report.
See our list of best Process Automation vendors, best Managed File Transfer (MFT) vendors, and best Workload Automation vendors.
We monitor all Process 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.