AutoSys Workload Automation Reviews

We're able to monitor a complex workload, easily see where we're at in our batch flows, and take care of problems before they become bigger issues.

We had a stuck file-watcher we weren't aware of, and then because of alerting, instead of missing an SLA, we were able to reach out and get the file in time to still make our batch commitments.

I think just having visibility into it; our managers can see what's going on too. It's not just a single technician that's a bottleneck trying to find out where we are. 

So the visibility into the workflow, and ease of use to be able to schedule.

The main push is the web UI, to be able to give it to our business users. They don't want to have to log in to a mainframe to use the product.

If we can get iDASH into ESP that would help. I know this request is the fourth... We're "in the hole," we're not even on deck. So it's going to come out to DEs, then it will come to us. That would be a big improvement, an option that we'd like to see.

No issues at all. In fact, that's actually one of the, I would say, competitive advantages of this product, the scalability and its ability to do the throughput we would need without having any delays.

We've scaled with it as far as we can grow. I've been talking to other companies that are much larger. I'm confident it could scale. If we had a tenfold growth, we'd still be okay.

I have not used tech support. Other people in my area have. They seem easy to work with. You get the documentation to them; they get back to you in a couple days with what they've found.

Yes, CA Scheduler, at that time. I think they were dropping support for CA Scheduler.

At that time I wasn't high enough up. By the time it rolled out I was happy with how I was able to get up to speed in the product, and support what I needed to support. But I was not involved in evaluating other products.

When choosing to work with a vendor, the most important criteria I look for are

• a long-term relationship
• a partnership
• willing to grow
• willing to listen to feedback
• support
• that they'll help us do our job.

I've worked with CA Workload Automation so I'm happy. I would say they're a nine out of 10 because I don't know anyone else. It's all relative. They could be a 10. I'm happy with them. I don't have any complaints. They're responsive.

Make sure you partner with them. Get buy-in from your business units before implementing. I think that's one of the biggest keys to success. If you don't feel comfortable let them explain their product. Get the buy-in first, then move forward so you don't have the resentment of, "Hey, you're forcing this product on us."

It's been great.

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.

We have used batch job scheduling and ad-hoc jobs in DEV, QA, UAT, PREPROD, and production for tier-one sensitive applications.

It helped us to avoid manual error. It helped us to reduce the manual efforts also. Helped us by giving alerts for long running jobs.

Virtual machine usage: It helped us to schedule the job to run on multiple servers based on the workload. It is automatically taking care of workload balance based on configuration settings.

Calendar usage is also very useful. It allows us to use our own calendar.

• It needs improvement in the high-availability side.
• It needs improvement in WCC console and EEM console to make it user-friendly.

SME for Cross Platform Agent installation and configuration. We have taken over ownership from the Unix Ops Team for installing, configuring, and administering the Systems Agents. I have also installed and stood up the Web Client. Currently, rolling it out to the general population of our company.

Scheduling workload across multiple platforms from a single point of contact and integration with ERP/ETL type platforms and products, such as Oracle and SEQUEL.

• Flexible agent configurations
• Integration with multiple services and applications across the enterprise.

Sunset CA-7 and stop leading people on with it. 

ESP, Dseries, and now Automic are CA's strategic vision. Not much engineering being done with CA-7 any longer. As a "batch scheduler", it is and always has been a workhorse. As we all know, batch scheduling is antiquated. Workload Automation is the future and changing the product name to CA Workload Automation, CA-7 Edition does not make it a modern WLA Platform.

Batch operations. Running our insurance systems.

It is wonderful. It's been everything we expected it to be.

• It gives us higher accuracy rates and faster performance of our batch processes.
• Higher reliability of our business processes. 

Reliability is a big one. When I go home at night I sleep well because I trust that the product will perform its design.

It has allowed us to automate many of the functions of our operations staff. 

For instance, we had production control staff spending two hours a day entering date parms into our daily business processes. And now, CA Workload Automation does it for us.

I am looking forward to more of their dashboard features. I think it would be very valuable for us to have dashboard features that could be delivered to our customers in the form of a URL, and they could refresh that URL whenever they wanted to get up to date performance metrics out of our systems. 

There have been a couple hiccups along the way, but then I call support and we always iron out any stability issues. It is a 24 x 7 operation product and it's highly stable.

We're currently crossing over into another insurance underwriting software product, and I see no problems with it being able to scale into this new product area.

I love those guys at tech support. In fact, I recently had a call where someone was concerned that I was upset, so they even had someone else call me to discuss with me how I felt about my call. I was not upset, but I appreciated their follow-through.

They are highly knowledgeable. They seem to be product experts.

Our old solution was losing its ability to scale. As our organization was changing, we needed a product that could change with us, and CA Workload Automation seems to be the right tool.

We chose this product for its scalability and its reliability, and the fact that it can run our business solutions on multiple platforms, in concert with one another. It can run an object on our Windows systems or our Unix systems, and then send messages to the other system when they are complete.

It was complex, but we also hired Automic business support staff to come and assist, and they helped us get through all the complexities, very easily.

We evaluated other products, but it was several years ago.

When selecting a vendor it really centers around the product reliability for us, and we saw that in this product.

I actually sat by several people today, here at the CA World conference, that were saying they were here just to evaluate this product. I mostly told them some of my personal success stories and shared with them, that it has been a wonderful tool for automating our business needs, and that they should really consider this product.

Cross-platform functionality.

Inherit Dependencies. Reduces scheduling errors for holiday processing.

Documentation and cross-application externals.

No issues.

No issues.

Excellent.

Jobtrac. We switched because of a contractual dispute.

Changing scheduling tools will never be a simple process, but the conversion tools and specialist assigned to us made it a smoother transition.

Pricing model for distributed should have an Enterprise option.

Yes.  IBM TWS/OPC, BMC Control-M and ASG-Zeke.

I recommend using the conversion services provided by CA.

We schedule overnight and daily jobs, mainly on a Cc&B system. We do file transfers from outside agencies, things like financial pledges and meter readings.

It performs very well. As far as the product is concerned, all of our issues are really with the system that we call rather than with the AE product itself. 

We were able to eliminate an overnight operator job, for one thing. He just left, but we did not replace him.  We get better reports than we use to have. Basically it runs jobs on a schedule, but we already had the jobs. It also eliminates manual job starting.

Its scheduling and its notification to us. We need to know when things are taking too long and when it fails, but we really need to schedule jobs to run. We need to have things run in a very sequential order, so it is very useful that we can schedule the work flows.

There is a difference between a web interface and the thick client interface. We particularly like a thick client interface, and it has gone away. I am finding that is disappointing to me. Now, it looks like the web interface is where all the development is going, which means it will become more full-featured than any thick clients that might be compatible with the new version. I would hate to see the thick client be left behind. I would really like to see that thick client come along.

I would really like to see a feature where if you have a variable object and you reference it anywhere, in any object or script, that you could somehow click on it and resolve the value and display it.

This is one thing I would really like to see in a new release of it. I have no idea if that has already been implemented or not, because we do not have the latest version, but I would really like to see something like that.

As far as I can tell, it is stable. We are just transferring to the AE version, but we were using Automation Manager for two years before that. 

I can't recall the actual product failing in any way. 

The tool can probably handle way bigger stuff than what we are doing. 

We are a gas distribution company, but we also own other companies. We are only using this at one of our locations where there are several million customers. We are firing off jobs that are billing those customers, managing meter readings, and various other billing-related financials and lettering processes. We are not at a Netflix or American Airlines level. I am pretty sure we have way more capacity in the product then what we are using. 

I do not think that I called technical support, though I think we have reported a software bug. There is one bug that we noticed, which is kind of annoying. So, aside from that, I do not think we used technical support at all.

I have looked up stuff on the CA Community. I might have gone into some of the Community pages to look for a solution. Nothing really memorable though.

Since we are still using the AE product and we are just transferring into it, we are still talking to the consultants, the people who actually came in and sold it to us, installed it, and trained us. So, we still have those as resources at this time. We have not really needed the Community.

As I recall, there is a transfer application from our AM to our AE. That went very well. Any problems that we had with that we probably caused ourselves, because we wanted to rename a lot of stuff, which was probably a bad idea, but I could not control that. 

I think it was relatively smooth. It could have been smoother. I do not think it was a fault of the program. I think it was more our fault. 

I would recommend it. Actually I do not even know another automation product. I would not know what else to recommend.

I appreciate training and support from a vendor. They should come in, train us on the product, and be around for a while, or at least available, to help us with anything we should have learned or did not. Or, things we discover we need. Training and early on support are really important and we really would like to see, like the same person providing it. 

I would like to be able to contact him and say, "Hey, how do I do such and such? How do I attach this report to this thing? How do I filter this?" And he would reply with, "Here are some codes you might find useful." I know these would be available out in the community, but I should not have to look it up because I am still in training. That is just one thing I would like.

CA Workload Automation AutoSys Edition is one of the most powerful schedulers that you have on the open systems, or going between Window servers; to be able to schedule and take advantage of the different powers that the automation has with it.

I've taken advantage of not only the normal command jobs and stuff like that, but I've turned them into using the proper plugins, the job types. One of the things that I have found out is that I'm the one that's using most of the job types, because I've taken away the need for writing or scripting processes. When somebody knows the database and knows how to write SQL code, or they know how to write a stored procedure, they don't need to know how to write scripting in order to run their scripts.

It's a little bit of a cost savings thing by using a plugin and using the different job types that AutoSys has. It goes the same thing when you're running a web service and you want to update stuff.

Taking care of the customers is the number one thing for any client; the client that I'm with, it's the same thing. They want to make sure that the customers are happy.

The benefit of using this product is the fact that your return on investment is major. When you don't have to teach people how to script or how to write different codes because of the way they connect to stuff, you're saving money, because you're able to put stuff into a production environment in a much faster solution.

We're also able to update our customers and let them know via apps to be able to see from using a web service to run and they log in to see what their activity is or what the status is on their stuff. It's updated immediately.

Cost benefits are amazing because somebody doesn't have to call a customer service person and sit on the phone for 30 minutes to find out the same thing they can find out in two seconds on the internet.

To make it a lot more user-friendly, in order to make it so other people can use it without having to do much training with it; the more user-friendly it is, the easier it is to work with.

The product has been out since 2.0 which is when I started working with this Workload Automation and, have seen it grow to a more powerful system that has been able to resolve all types of different automation appliances.

Customer Service is as always a high quality and, have had great success with getting any issues resolved.

Great working with the Tech team.

I think it's one of the most powerful workload automation processes that are out there. It is able to reach across platforms. It's able to reach across appliances. It's able to update.

It's a matter of your return on investment. It goes right back to that. How much do you want to spend, but how much are you going to save?