AutoSys Workload Automation Reviews

I find the UI to be a really nice feature. It's great and pretty user friendly. Also, there are many agent integrations available that support various platforms.

It provides us with automated management of a high volume of workloads across our enterprise.

I'd like to see more agents for integrations with other platforms. Also, I think the interface could be unified in a better way. Additionally, we could benefit for more data analytics.

We've had no issues with deploying it.

It is very stable and we haven't had any problems.

They are enhancing the product for new limits, so we should be able to scale without a problem.

They have great support when we work together.

The initial setup was very straightforward. It's a great benefit that you can install and configure it very quickly.

I would recommend the product, but you have to have a good team to work with it. The solution is good, but you need a prepared team.

Our challenge is having a centralized schedule on a single pain with 180,000 jobs each day. We are looking to move to iDASH with predictive analytics. We don’t have many SLA’s. We're looking to do better with predictive analytics and we want to further integrate.

We were using a lot of homegrown stuff. This solution provides us with more details on jobs failing. It also gives us restorability. For the last 10 years, it's become more complex, but it's also bridged our platforms and gave us the ability to recover.

I'd like to see automation pushed even further, giving us greater looks into other systems. I'd like more enhanced process automation and have it manage a few more platforms without relying on another orchestration platform.

We've used it for 10 years.

We've had no issues with deploying it.

It's stable. It’s so busy finding maintenance windows, and we are currently going through exercises.

We can leverage multiple servers with ease.

Technical support is knowledgeable and I don’t have a whole lot of complaints. We don’t get the run around.

We had already had some other CA technologies, so it was a good fit and we knew what we were dealing with.

Initial setup and upgrades were straightforward.

Understand your needs, don’t complicate it, and understand what you are looking for. You don’t want to create an automated mess.

In our current environment, we have a large community of users. So Workload Automation helps us with our complex job scheduling with automating placements.

I believe it's a mission-critical application that is required within the company because everything requires to be scheduled. Everything needs to move. In today's economy, everything is 365-24/7.

In all aspects of the company, whether you're in the actual trading or in the wholesale or retail space, you're our internal client and we treat you like a customer. Ultimately, we're in operations.

It needs more complex scheduling capabilities on the end points. For that to happen, you really need the next version of AutoSys that has the ability to do that. We used it as an opportunity to test out what that next version going to look like, so when we deployed enterprise-wide, we had a little bit of understanding of how it's going to work.

Also, it shouldn't take longer than six months to do a deployment. I heard good things about being portable, meaning CA is able to introduce a lot of agents as packages on top of your existing environment that you're going to add. That's some of the good things that I'm hearing and I'm looking forward to seeing those because our business requirements always expand.

I'd also like to see iDASH integration with monitoring, which I think is up and coming.

I've used it for almost 3 years.

I've had no issues deploying it.

We've had stability issues, but CA's pretty prompt about fixing things for us. We've had commonly-known bugs that are fixed after an upgrade.

It's been scalable. Architecture-wise, it's pretty robust, and we've been able to work it out with CA. We run over 10,000 jobs a day.

Technical support is relatively on the upper hand of some of the companies that we deal with because we do have dealings with our account management team. When we have a major deployment, the support team is made fully aware of that. If, for example, if we're doing a deployment on the weekend, we have a 1-800 number that we can call. It's been great.

For the original implementation, I wasn't involved, but we are moving to a newer release. We have built an environment where I was involved. Complexity-wise, it's more or less a specific business requirement that we needed.

At this moment, we've been pretty long-term customer with CA. I don't think there's any product out there that we're going to be willing to switch out at the moment, given what their customer base is, what the capabilities of the product and how it fits into our model.

We are using AutoSys Workload Automation for parent jobs and can create scripts for automation.

The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it.

It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications.

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

The solution is stable. 

We are able to view reports at any point in time

AutoSys Workload Automation is scalable.

We plan to increase our usage of the solution.

I have used the support from the vendor.

I have used other solutions similar to AutoSys Workload Automation. 

We can do the process with a script and it does not take more than 10 minutes. The environment can play a role in how long it will take and what type of script we need to use.

We paid to use the solution monthly.

When comparing this tool to others it is far better.

I recommend this solution to others. 

I rate AutoSys Workload Automation an eight out of ten.