AutoSys Workload Automation Review

The WCC shows the status of job flows and job failures. Duration is not displayed in the GUI.

What is most valuable?

The flexibility of being able to schedule the timing and frequency of different automation scripts makes it easier for us to meet our customers’ business requirements.

We use the WCC, which is an interface that sits on top of the application. That is pretty user friendly in terms of being able to see the status of job flows, job failures; and in the ability to manually intervene and fix issues. Essentially, the code you're running sends a return code, which you can configure to be read as a success or failure.

How has it helped my organization?

We're in healthcare. We need a way to automate loading the members and processing claims. Without a tool, we wouldn't be able to do that efficiently. It increased efficiency.

What needs improvement?

The most important thing is that duration is not displayed in the actual WCC GUI. I know they have some different add-on tools where you can get that information; but it would be nice to be able to see how long jobs ran, and the history for more than ten days. As is, the scheduler already starts to have performance issues when you keep the ten day history. So there are efficiency issues related to being able to keep more logs.

There are always issues with software. They have some improvements they can make. The way they're heading, I think they're on the right track.

What do I think about the stability of the solution?

Stability has been good since we took release 11.36. Before that, we had release 11.35. That was somewhat stable. We had growing pains because we switched over from a different scheduling tool.

What do I think about the scalability of the solution?

It has been easily scalable. CA helped us build the Workload Automation infrastructure that we knew we were going to grow into. It was really a partnership between the two of us to make sure we were scaled correctly. We do about 10,000 jobs a week, a couple hundred thousand a month.

How are customer service and technical support?

Early in my career, I was more on the technical side. Now that I've transitioned to management, I step in at times to help with it, but not as much.

The few times that I get involved, it's usually bad because it's an escalated incident of some sort. I think primarily my team's happy with the support they get from the resources that have been engaged; and works with them through the issues.

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

We were using Tidal Enterprise Scheduler. We switched over, and then had some growing pains during the transition.

How was the initial setup?

My team owns setting it up, configuring it, supporting it, and all of those things.
The first time we set it up, it was a little overwhelming because it's something different and new. I had a newer resource on it, and there was a time constraint for getting it installed. We had somebody from CA handhold us through the process.

Which other solutions did I evaluate?

A couple of our customers use Control M, so we considered that as well, from what I understand.

What other advice do I have?

Do your homework, and be ready for a challenge. Anytime you switch tools, it's going to be a challenge.

Which version of this solution are you currently using?

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More AutoSys Workload Automation reviews from users
Find out what your peers are saying about Broadcom, BMC, IBM and others in Workload Automation. Updated: June 2021.
511,307 professionals have used our research since 2012.
Add a Comment
ITCS user