We just raised a $30M Series A: Read our story

Schedule a 30-minute demo or reference call with a real user from the PeerSpot community. Available only to members that are in a buying process for this product and have contributed a review that's then published.

IBM Workload Automation OverviewUNIXBusinessApplication

IBM Workload Automation is #9 ranked solution in top Workload Automation tools. IT Central Station users give IBM Workload Automation an average rating of 8 out of 10. IBM Workload Automation is most commonly compared to Control-M:IBM Workload Automation vs Control-M. The top industry researching this solution are professionals from a computer software company, accounting for 30% of all views.
What is IBM Workload Automation?
IBM Workload Automation is a complete solution for batch and real-time workload management, available for distributed mainframe or hosted in the cloud. Use it to drive business and IT workloads on hosted servers, with virtually no cost of ownership for your central server. Increase your productivity with powerful plan- and event-driven scheduling, and run and monitor your workloads wherever you are. This includes interfaces dedicated to application developers and operators, providing them both autonomy and precise governance.

IBM Workload Automation was previously known as IBM Tivoli Workload Scheduler, IBM TWS.

Buyer's Guide

Download the Workload Automation Buyer's Guide including reviews and more. Updated: November 2021

IBM Workload Automation Customers
Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
IBM Workload Automation Video

Pricing Advice

What users are saying about IBM Workload Automation pricing:
  • "The contract is with the customer with whom we are working, so IBM is not directly involved in this."
  • "It is about one-third of the cost of a controller."

IBM Workload Automation Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Salvador Reyna
IT Manager at a manufacturing company with 10,001+ employees
Real User
Top 20
Workload automation that helps track productivity and progress across platforms

Pros and Cons

  • "The technical support is great, the product is easy-to-use, and it is stable."
  • "It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."

What is our primary use case?

The tool is managed from offshore by another company. The primary use for it in our company providing support to our main client who is a large beverage company that needs the product to manage operations. I just act as the support interface between the client and the offshore team starting at the time I took this position as a global manager for workload scaling. I found out about this product someplace and how we could put it to use. We have been running it ourselves and with our client for a long time. It is also a part of our company's application or solution set.  

The use cases for my workload purposes have to do with my applications. It works fine for scaling jobs and can interface with other systems. So it does what I need it to do.  

What is most valuable?

The interface for the applications team is really the most valuable part of the product in my opinion.  

What needs improvement?

The interface for the operator is not so good. I do not think it is as complete as something like Control-M by BMC Software (named for former Shell executives Scott Boulette, John J. Moores, and Dan Cloer). A few other things could be better like the scheduler and linking between jobs and dependencies.  

For how long have I used the solution?

I have been working for the last five years between the client the provider and my company. 

What do I think about the stability of the solution?

This product is quite stable. There are no issues within the application or with the tool itself becoming unstable.  

What do I think about the scalability of the solution?

The scalability is actually quite fine. I think that right now we have around 100 to 150 users that have jobs running on it.  

The offshore team is made up of about five guys that mainly take care of the maintenance tasks. At this moment, we do not actually have any plans to scale our usage. Maybe in the coming two years, we might have to. We are planning to upgrade or migrate to another tool depending on what is best for our situation at that time.  

How are customer service and technical support?

I think the technical support is great. They have been helpful when we needed something resolved.  

Which solution did I use previously and why did I switch?

Before working with IBM Tivoli Workload Automation I worked with Control-M from BMC. 

The main differences and advantages of Control-M are mostly to do with the operator interface. The console that the operator is using is quite a bit better in Control-M rather than Tivoli, and so is the way to schedule and make the relationships between jobs.  

How was the initial setup?

I think the product is generally easy-to-use and that includes my experience with the setup.  

What other advice do I have?

The advice I would give to others considering using Workload Automation depends on the necessity and the reality of their requirements. It depends on the complexity of the jobs. Depending on that it may be interesting to use Tivoli because it is a good tool. It is a good application to use to run workload tracking.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this product between and eight and ten depending on who is using it and for what reason. I think it is quite good so I think it deserves a nine.  

Additional features I would like to see included in the next release to improve and make it a ten would just be the two things I mentioned that Control-M does somewhat better for now. The interface for the operator should be improved, and the way to create relationships and dependency between the jobs can be better.  

Disclosure: I am a real user, and this review is based on my own experience and opinions.
GR
Manager- Projects at a computer software company with 10,001+ employees
Real User
Top 5Leaderboard
A stable solution

Pros and Cons

  • "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 performance of the previous versions could be better."

What is our primary use case?

The solution comes with a scheduler. It contains a file for receiving things from external sources. We trigger the file, on which basis the subsequent business practices are kicked off, one after the next. This means that there is dependency on the file dependency. The subsequent steps in the business practices kick off, automatically, once the file is loaded. 

What needs improvement?

The performance of the previous versions could be better. We encountered certain issues with the lower version of it, the 9.2. Things have greatly stabilized since then. However, as with any IBM tool, things are a bit tricky. I would give a rating of four or five out of ten, as we encountered certain issues with the domain controller with the lower versions. 

It would be nice if we could get support for earlier versions. Generally speaking, IBM insists that we move on to their latest one. 

In respect of the dependency diagrams, the job dependencies across the business process should be improved. 

For how long have I used the solution?

I have been using IBM Workload Automation for three or four years. 

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

We do not have plans to increase the number of users of the solution.

How are customer service and support?

We regularly reach out to technical support when dealing with issues that are beyond our control. 

Which solution did I use previously and why did I switch?

We did not use a different solution prior to IBM Workload Automation. 

How was the initial setup?

While the installation is fine, it requires the involvement of an IBM engineer. The solution is easier to install for those who are well versed in the IBM world, but this is a bit difficult for someone who has a background in application development. The process is easier for someone who has experience working with IBM tools. 

What about the implementation team?

One can handle the installation on his own. 

Including management, fewer than seven people are needed for the deployment and maintenance. This will always involve an administrator. There will also be a program manager involved, the rest of the team consisting of developers. 

What's my experience with pricing, setup cost, and licensing?

The contract is with the customer with whom we are working, so IBM is not directly involved in this. 

What other advice do I have?

There are approximately 50-plus users making use of the solution in our organization. 

My advice is that the implementation be handled by someone with the requisite knowledge. This will be difficult for someone who is not properly acquainted with IBM products. It should be done by someone who knows the IBM environment, who would find the process much easier to handle. 

I rate IBM Workload Automation as an eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Find out what your peers are saying about IBM, BMC, Broadcom and others in Workload Automation. Updated: November 2021.
554,873 professionals have used our research since 2012.
BS
Enterprise Architect at kosakya
Real User
Collects the resources within the IT system that reports the use of different resources, file system resources, storage resources, and so on

What is our primary use case?

We use it at the Bank for the portfolio management system. In 2001 and 2003 I created all these jobs for the portfolio management system for collecting data from the backend system. From 2015 I use it as the tool that collects the resources within the IT system that reports the use of different resources, file system resources, storage resources, and so on.

What is most valuable?

The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions. 

What needs improvement?

Other solutions like Control-M are better than this solution. IBM should have better integration with the cloud.  It should support other schedulers that aren't IBM products. 

For how long have I used

What is our primary use case?

We use it at the Bank for the portfolio management system. In 2001 and 2003 I created all these jobs for the portfolio management system for collecting data from the backend system.

From 2015 I use it as the tool that collects the resources within the IT system that reports the use of different resources, file system resources, storage resources, and so on.

What is most valuable?

The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions. 

What needs improvement?

Other solutions like Control-M are better than this solution. IBM should have better integration with the cloud. 

It should support other schedulers that aren't IBM products. 

For how long have I used the solution?

We have been using IBM Workload Automation since 2015. 

What do I think about the stability of the solution?

It's very, very stable. The support is quite good. I was totally astonished about the life cycle of this IBM product because a lot of colleagues told me that Control-M is the best scheduler but I have found that it's not true. IBM does a really good job with its product.

How are customer service and technical support?

It's better than the solution that Control-M offers. Within Deutsche bank they are using Control-M for the investment banking and they are using different timezones, for every console you need a separate installation with Control-M. With IBM, it's not necessary. 

IBM uses also has different plan options, from monthly plans to weekly plans. This is a problem with Control-M. It makes maintenance very, very costly because you have to configure different environments for different timezones.

How was the initial setup?

The scheduler is a little bit complex. They have different concepts, they use event mechanisms for their workforce. 

With Control-M you have a lot of server components. In the meantime, you can install them with Kubernetes as well which is a big improvement.

What other advice do I have?

I would definitely recommend this product. It's an interesting option in terms of schedulers. 

I would rate it an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
FA
Manager Production Applicative at a financial services firm with 10,001+ employees
Real User
A stable solution with good technical support

What is most valuable?

The most valuable feature is the job scheduler.

What needs improvement?

I would like to be able to access the return value or result from one job, in the following job. This is a feature that other solutions have and is very helpful. I had to create my own workaround for it because the capability is important for me. It would be helpful to have a mobile app that could be used to follow the job schedule. Most IT applications now have mobile app support.

For how long have I used the solution?

I worked on IBM Workload Automation for close to 10 years, although I have recently changed companies and no longer use it.

What do I think about the stability of the solution?

The stability is good. 

What do I think about the scalability of the solution?

We did…

What is most valuable?

The most valuable feature is the job scheduler.

What needs improvement?

I would like to be able to access the return value or result from one job, in the following job. This is a feature that other solutions have and is very helpful. I had to create my own workaround for it because the capability is important for me.

It would be helpful to have a mobile app that could be used to follow the job schedule. Most IT applications now have mobile app support.

For how long have I used the solution?

I worked on IBM Workload Automation for close to 10 years, although I have recently changed companies and no longer use it.

What do I think about the stability of the solution?

The stability is good. 

What do I think about the scalability of the solution?

We did not need to scale this solution. We had close to ten people who used it.

How are customer service and technical support?

Technical support from IBM is very good. I have worked with different vendors and I know that it is sometimes difficult to get a good level of support, but there were people supporting this solution who were very good and always helped.

What about the implementation team?

The implementation was done by external consultants.

What other advice do I have?

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Anthony Heilbronn
IT Specialist TWS at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Extremely scalable, very stable, and good for batch automation, but needs custom Java API documentation and more training

What is most valuable?

The whole product is valuable because it is a tool for batch automation.

What needs improvement?

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. 

For how long have I used the solution?

I have been using this solution for 15 years.

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

It is extremely scalable. We run more than 80,000 jobs a day across multiple platforms.

How are customer service and technical support?

Their technical…

What is most valuable?

The whole product is valuable because it is a tool for batch automation.

What needs improvement?

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. 

For how long have I used the solution?

I have been using this solution for 15 years.

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

It is extremely scalable. We run more than 80,000 jobs a day across multiple platforms.

How are customer service and technical support?

Their technical support is fine. We have a contract with them to assist us.

How was the initial setup?

It is simple to install.

What's my experience with pricing, setup cost, and licensing?

It is about one-third of the cost of a controller.

What other advice do I have?

I would rate IBM Workload Automation a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Product Categories
Workload Automation
Buyer's Guide
Download our free Workload Automation Report and find out what your peers are saying about IBM, BMC, Broadcom, and more!