We performed a comparison between IBM Workload Automation and Stonebranch 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."The initial setup is easy."
"Technical support from IBM is very good."
"The support from Cisco is very good. I was with them as a company for 40 years"
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"The whole product is valuable because it is a tool for batch automation."
"Jobs can be triggered in multiple nodes."
"The technical support is great, the product is easy-to-use, and it is stable."
"I have supported this product in literally 100s of different environments and its unmatched in its ability to scale to any size."
"The Universal Agent is the most valuable feature. Being agent-based and being able to go across multiple technology stacks, which is what our workflows do, Stonebranch gives us the ability to bridge those disparate technologies. It enables us to remove the dependency-gap with the agent so we know the status of the workflow at each step."
"The interface is very user-friendly and easy to navigate."
"I like the dashboard and the various workflows."
"Stonebranch performs well, and the graphical representation is excellent. Overall, it requires more technical effort from our teams, but the solution is intuitive, so anybody can use it."
"We like that it has GUI and is not just a command line."
"The support is good from Stonebranch Universal Automation Center."
"The features are upgraded, and every six months they're releasing patches."
"The most valuable feature is the reliability of the agents, because we need them accessible and we need to run stuff. The agent technology and compatibility are top-notch."
"The performance of the previous versions could be better."
"Scalability-wise, it can be a little bit challenging."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"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."
"The configuration of IBM Workload Automation has some challenges. We have a difficult time customizing it, but it is similar to other solutions."
"It should support other schedulers that aren't IBM products."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"Occasionally, we have an agent that doesn't come back up after patching. That doesn't happen very often... It's really just a restart of the agent and it comes back up. But that might be one thing that could be improved."
"It would be ideal if they had the exact same features as the CA Workload Automation DE series. It would be helpful to have calendaring options."
"It can't handle negative written codes."
"I have a request regarding our agent on the mainframe. It may time out when communicating to the Universal Controller, when the mainframe is extremely busy. That can cause a task which is running at that time to not see the results of the job that ran on the mainframe. It happens sporadically during times of really busy CPU usage. We're expecting that enhancement from them in the fourth quarter."
"There is room for improvement with its connectivity with the Microsoft SRS system. It is very weak. They keep telling us it works with it, and technically it does, but it does not provide a lot of visibility. We have lost a lot of visibility migrating to Stonebranch, compared with just running tasks on the SRS server. That's really about the only thing that is a sore point for us."
"It's not available on the cloud, so they should take that due to safety, security, and scalability."
"There is a component called the OMS, which is the message broker. We rely on infrastructure, resiliency, and availability for that piece. If that could change to be highly available just as a software component, so that we don't have to provide the high-available storage, etc. for it, that would be a plus. It would just be cheaper to run."
"It can be hard to manage the task monitor."
IBM Workload Automation is ranked 13th in Workload Automation with 28 reviews while Stonebranch is ranked 16th in Workload Automation with 26 reviews. IBM Workload Automation is rated 8.2, while Stonebranch is rated 8.8. The top reviewer of IBM Workload Automation writes "With an easy setup phase in place, agent-based installation can be done in minutes". On the other hand, the top reviewer of Stonebranch writes "Allowed us to develop workflows without having to train and develop very specialized skillsets". IBM Workload Automation is most compared with Control-M, AutoSys Workload Automation, HCL Workload Automation, Red Hat Ansible Automation Platform and OpCon, whereas Stonebranch is most compared with AutoSys Workload Automation, Control-M, Redwood RunMyJobs, ESP Workload Automation Intelligence and VisualCron. See our IBM Workload Automation vs. Stonebranch 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.