AutoSys Workload Automation Reviews

I work as an engineer in an enterprise company. We have used AutoSys Workload Automation for a long time for batch processing and other automation things.

AutoSys Workload Automation has saved us a lot of time for batch processing and bad jobs. Earlier, if someone had an issue with the application, they would open a ticket, and we would take the ticket and work on the issue. AutoSys Workload Automation can pick up a ticket raised by someone, resolve the issue, and close the ticket. So, it saves a lot of human intervention.

The most valuable feature of AutoSys Workload Automation is batch processing.

There is a recently made change in AutoSys Workload Automation's subscription model. The solution does not have a friendly subscription model because it forces users to take a five-year subscription simultaneously, charging millions of dollars. Hence, our managers are looking for alternatives to AutoSys Workload Automation.

I have been using AutoSys Workload Automation for five years.

I rate AutoSys Workload Automation ten out of ten for stability.

I rate AutoSys Workload Automation ten out of ten for scalability.

Overall, I rate AutoSys Workload Automation ten out of ten.

We use AutoSys to run our scheduled jobs. In terms of the version, I am probably using version 14.

This type of tool is essential for a data group in terms of how we pick up data from different things and vendors, and how we set up the workflows to do all the jobs. Without it, we can't imagine how we would run all the jobs. If we need something to run on a daily basis, we can use AutoSys to fully automate it. We don't need to have a dedicated resource to look at a job and ensure that it is completed. AutoSys simplifies our life.

It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task.

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.

I've been using this solution for more than 10 years.

It is quite mature. It is pretty good.

We are using AutoSys for very large-scale deployment, and it is very scalable. It is capable of handling 10,000 jobs on a daily basis. It is very good.

We have more than a hundred users, and it is being used at the corporate level. We are trying to use something like this in the cloud. I don't think we are going to expand the usage of AutoSys because we are thinking of moving to the cloud. We are trying to see which solutions provide similar functionality but support the cloud environment.

Their support is very standardized. The application has been out there for quite a long time, and the skillset is generally available in the market.

It is a very mature product, and we require very little support. I don't remember ever contacting their customer support or client support team for any major issues or downtimes.

I have been using this solution from day one in this organization.

It depends on the experience. For me, it is very straightforward. In a simple setup, you set up a server, a database, and an agent, and you are ready to go. In a complicated setup, you have to set up high availability, virtual machines clusters, etc.

We have a dedicated group to handle all top-level applications. This is relatively straightforward for them. From planning to implementation and getting it into the production environment, it takes a month or two.

We did it ourselves. To get it rolling and to maintain it, we have a very small team with less than five people. They are just regular developers.

This product has been bought by Broadcom, and Broadcom does not have enough dedicated resources to further develop this product. I don't see any major features, versions, or functions being added to this product in the future. I don't think the vendors would be willing to spend resources on top of it.

I would rate it a nine out of 10. We really like the product and its functions. It works, and we like its stability, scalability, and robustness. It is a very reliable product, but it lacks future enhancements. We haven't heard of any cloud initiative for this product.

In our organization we have more than 30,000 automations we are running in this product. From an admin perspective, we have around seven to eight people working with the solution, managing it and dealing with the volume. We are a customer of AutoSys and I'm a company manager. 

I think one of the valuable features of AutoSys is the easy configuration and integration of this tool with SAP. It's a critical part of managing the solution. In terms of the basic functionality, I found this to be a really excellent tool to work with. There are minimal issues and minimal maintenance.

Support definitely needs improvement. It's possible they're in some kind of transition so I'd like to give them the benefit of the doubt but it's an issue. The pricing is definitely something they should look at, it's quite expensive. Finally, the latest features like the quick searching or better reporting and analysis of the jobs which are running in, needs to be improved. It's a great product but with the latest feature set there is a large scope for improvement.

From a manageability point of view, the easy upgrade should be included and the frequent feature update too. Reporting and notifications need to be improved too, these are important things.

We've been using this product since 2008, so close to 12 years. 

Stability of the product is excellent, I'd give a very high score to that. 

I'll have to reserve judgment on scalability for now. 

The technical support could be improved. 

The initial setup is complex, it's not really easy to install this tool from scratch. We have improved in that area over the period of time we've been using the solution. Not all features were available from day one but over time, as new progressive things have come up in the later versions, we started implementing them. From the implementation point of view, it's a little difficult. Even the upgrades of AutoSys are not really simple. It needs to be planned and requires significant down time if you have a large set up. An upgrade can be done within seven to eight hours, but from a planning perspective, you have to work for at least four to five months.

AutoSys is out of line with the latest trends of the IT industry, like the quick searching and things like that. It requires special skills which you have to develop in your team in order to manage it. That said, it's an excellent product and will give you the functionalities that you need. 

I would rate this solution a six out of 10. 

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 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.

In an upcoming release, AutoSys Workload Automation could include more integrations capabilities. I have seen other tools that have native integrations with other tools, such as Docker and other services in the cloud. They are not taking this into account in AutoSys Workload Automation.

I have been using AutoSys Workload Automation for approximately two years.

We have approximately 15 administrations who use this solution, but the tool is made to work for all the infrastructure of the organization, we could have more users.

The technical support is great, they have helped us a lot.

The initial configuration of AutoSys Workload Automation was simple. When you need to make a migration from previous versions or from other tools, it's easy. There are some complexities, but it is not something that is impossible, it can be very simple.

I rate AutoSys Workload Automation an eight out of ten.

In our case, it's just managing the day and night jobs of banks because we are supporting several banks in Europe.

The company I'm working for is an outsourcing company who provides solutions for customers. We host their complete environment.

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.

If you do not need the latest features like cloud and compare, I would really advise using AutoSys. For future technologies, I cannot answer the question yet.

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.

I have been using AutoSys Workload Automation for nine years.

We are not using the latest version. We are planning a migration towards the latest version or a migration to another tool. Most likely, because of the lifetime of the environment that has to be supported, we will probably migrate to the latest version because it's often easier if you stay with the same product.

We have several customers at this moment and AutoSys is used by one bank. In fact, it's not like real end-users are touching the tool. It is doing its job during the night and it is only for one application including the bank application, so it's not connected to its final end users, so you scale all the toolings which are available in the bank environment. We only focus on the core banking.

The technical support is very good. If you open a case, the support is really sufficient.

AutoSys Workload Automation is really easy to install. You can install the server and an agent in about 10 minutes. It takes the agent on five clicks. Even if you have many agents to install during installation, you can pick that very easily and you also can deploy it fairly easily. In terms of the deployment, it's a nice solution.

Normally you can do it by yourself unless you're running into situations where the newest version is working slightly differently than the previous version. Sometimes you need to adopt some parameters, but they provide you sufficient support for that. The deployment can be done by one guy. One system engineer can handle the job.

AutoSys Workload Automation has a yearly subscription.

On a scale of one to ten, for the part that we are currently using, I can give AutoSys Workload Automation an eight.

I would recommend this product for other users who want to start using it depending on their needs. I'm still investigating what the new version provides in the future, based on technology, so it is difficult to answer that question.

We are a system integrator and this is one of the products that we implement for our customers. AutoSys is primarily used for scheduling CP jobs, file transfer, and other miscellaneous jobs.

The graphical interface can be improved.

I have been working with AutoSys Workload Automation for the past five years, but not on a regular basis.

AutoSys Workload Automation is a stable solution.

This is a scalable product and we have about 50 users. We are planning to increase our usage in the future.

Since Broadcom acquired this product, the technical support has not been as good. They should really be faster and more knowledgeable.

The agent package and the other package should be more user-friendly to install.

I provide support on this product for our customers.

I would rate this solution a seven out of ten.

My clients mainly use this solution for server workloads — work process flows around the deployment of servers, etc

This solution has made my clients' workplaces a lot less labor-intensive.

I have been using this solution for the past few months.

It is pretty stable from my understanding. I haven't heard any complaints about a run maintain.

AutoSys Workload Automation is very scalable. My clients were mainly large organizations and they never had any complaints about the scalability.

I never had to contact technical support so I cannot comment on that.

The initial setup is quite straightforward.

The pricing needs to be improved. Some of my client's complained that it was too expensive.

My advice would be to negotiate thoroughly on the price.

On a scale from one to ten, I would give this solution a rating of eight.

A strong aspect of our current use case is to provide integration with the Zeke mainframe scheduler and enable cross platform job dependencies between the two worlds.

Self-Service can enable the support team to move from being a bottleneck to being the go-to team for expertise and advice and to focus on maintaining the infrastructure.

Granular Security enables self-service role-based access. JIL language is always a big accelerator for creating/editing job flows efficiently.

Great at handling timezones and daylight savings adjustments.

Despite the commitment of the development team to improve the UI since version 11.3, the WCC module still lacks true quality. There are still too many screens and the use cases need to be handled in a more "compact" way. I have not seen the v12 product yet.

Note that this product is now a legacy product with a dwindling user base and support.

Do not consider for a green site implementation

We've been using v11.3.6 for years, and the tool in general since 2006.

We've had no issues with the stability.

We've had no trouble scaling it for our needs.

Customer Service:

The user conference used to be a great way to catch the attention of the development and product management team. Sadly, these are a thing of the past.

Technical Support:

Technical support has noticeably gone down since the Broadcom takeover of CA. A lot of the knowledge base is now on line and the expectation is that users self-support with that. The level of depth that the support organisation provides is not as deep as previously. We have not experienced any emergency situations though, so can't comment on that.

The initial setup was not hugely complicated, but do set aside four to six man-months if you are not using specialist services. The product does require some careful thinking around the High Availability and security sides. Thorough qualifications testing is recommended for a scheduler, too.

If you don't buy competence, you will need to build it internally which takes time. The recent versions of the product are a lot more complex than the relatively simple 4.0.

Legacy product with dwindling user base and support.

Get some specialist help if you don't have internal knowledge.

This product is now legacy.