Automic Workload Automation Review

The connection to ServiceNow is good feature that we use. Unfortunately, it is not stable yet.


What is our primary use case?

We use it to automate our business processes. It is just for automation and scheduling.

How has it helped my organization?

We have worked about 20 years with this product. We have migrated for 20 years from CA to Automic. It is very interesting. Now, we are back to CA, because they have taken over the Automic company. The benefits also include the automation of our processes. We have worked mostly with SAP software, and we have other things in our plans. We want to automate the distribution of servers, so clients can make a request from ServiceNow. That way, companies can order servers on the internet that we normally we would build during the process for internal use. Because developers sometimes need a very fast machine for testing, you can click in ServiceNow to request a machine after two hours, then you can have a machine to plug into. At the moment, we have tried to make this a digitalized process, although we have a problem with ServiceNow.

It is easy to integrate different systems in one platform, then to automate it. You have a job, then one part of the job is going to the SAP system, and the other one is going to ServiceNow or to another system. Then, they all combine into one process.

What is most valuable?

The very special feature that we use is the connection to ServiceNow.

What needs improvement?

It does not have the same functions as the old version, which makes our developers angry because because they must work with this tool. We going forward it may not be possible.

CA has missed the product's focus. We have a lot of developers in our company, and we are experiencing the same problem. However, the CA company has not seen that developers and clients are having a problem, which is not good for the product that we do. CA took over the Automic company last year, and we do not think this was a good direction for the product.

I would like to see the rich client with the product for the developers.

It is more important for us to have a longer, stabler releases. We do not need so many features. This is a problem of bigger companies where the management wants new features, but the product has no stability after that.

It would be good to have a mobile app, where you can monitor your process, just to see if it is running or if it is blocked. The user interface on the web is not good for the developers. Features are missing, and for the client, it is too complex. At the moment, we build our own UI. We have programmers in Java API, and we have a Client which works on the mobile phone. It can start jobs, make the schedules stop and start, and see the statistics on a smartphone.

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

We have had issues with the performance. We have a job now in production, but the product is not very stable. ServiceNow creates problems with the Automic entry of the connector, so the stability could be a little bit better with this product.

What do I think about the scalability of the solution?

Sometimes, we have some performance problems. I am not sure it is because of the software. It might be because we have a huge amount of objects in our system. In this case, it can happen that we often have performance problems. I am not sure if it is because of the product, it is more because of the objects in our system.

Because the product is based on the SQL Database, we have too many activations. The scalability is limited by the SQL in the background, and that is a problem. If you want to take jobs to other systems, you must build the developer our way. At the moment, we are building a new system. We have it for every country and have separated it for machines. It is mostly getting better, but the scalability to build it on new systems or to split it is not so easy.

How is customer service and technical support?

We have technical support. We also have a connection in Austria with the support colleagues there. 

The first step: You must describe the problem. At the most, filling in a checklist.

Then: It helps to take the telephone, and talk to a technical engineer directly. 

That is why their technical support is very good.

Mostly, we contact support because our problems are very complex. Normally, we find problems that they have never knew about before. We have new technology and build actions on the automation system, then we find objects which can work with those actions, because we have technical limitations. 

We have a contact within the support, and also with a freelance in Austria. We have worked together with several people to find a solution for this new philosophy. Automic states you should build everything with actions and take multiple actions with business processes. However, not all objects are usable for actions that we see.

What was our ROI?

If you would have to start all your jobs manually, it would cost you a lot of time and money.

You do not need any humans to start jobs, so you can save a lot of money.

Which other solutions did I evaluate?

From the bad products, the Automic is the best. All products in the market are not good since they are simple workload scheduling. There are some things are missing in the Automic product, which our management does not see.

What other advice do I have?

I would recommend using Automic.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Add a Comment
Guest
Sign Up with Email