Automic Automation Reviews

During the closing of business processes, it does provide the interface you require to interact with, including various systems, operating systems, databases, customer services, and so forth. It is very, very good. I'm quite pleased with it. I stay in very close contact with bank operators since they have to close the business on a daily basis.

The USB port is okay. 

The product in general, is okay. I do appreciate it from an architecture point of view. 

The most important and critical process business in the bank, including COB, close of business, which has to run on a daily basis, is automated. This is the most critical and the most important business process in the bank. 

The electronic work order combinations have the ability to scale and handle large volumes of data. So far, it's fine, as of right now. We don't have huge amounts of data. The amount of backups involved is quite limited, and for the amount of data exchange, it's actually pretty low. 

It is easy to manage complex workloads using automatic workflow automation. I would rate it above average. It's far from perfect. However, it's above average.

It's good for managing processes that span multiple operating platforms. We have very good integrations between everything. We have multiple agents surrounding only Nutanix. I'm happy with that.

Automic Automation helped improve our compliance processes. For example, we have to prove that we do a backup or daily backup, and so forth. It is very easy to extract the backup report and the enterprise report. Whenever we have a compliance audit, I can simply send those outputs and everything is fine.

The only thing I'm actually not satisfied with is, during the COB, the use of processes makes time estimation for the flow completion harder. Most of the time, it is not accurate, and it's actually very frustrating for the operators since they have to run the COB. They have to connect many people each and every day to run the closed business for the core banking system for the production environment and also for the testing environment. Since they have to work in shifts, the first thing they are looking at is whenever they are going to complete the task. I'm not sure what data they use to make time estimates. However, most of the time it is not accurate. It's either way too long or way too short.

I've used the solution for a while. I've used it for more than three years - almost four, in fact. 

I consider the solution stable. 

We have 20 to 30 people using the solution right now. 

I'd rate the solution eight out of ten. 

To some extent, I provide support myself. Whenever I need additional support, I can go to our business partner, a local company, and they can help. They've been very nice and helpful. 

I'm also familiar with Control M. I prefer Automic as it has multiple interfaces and capabilities to interact with various types of systems - even old, legacy databases. 

I handled the initial setup, including handling the requirements and infrastructure.

When we installed the solution two years ago, we installed the latest versions - whatever was available at that time. 

The implementation wasn't easy. However, I had local partners from a local company to assist with the setup. It would be difficult for inexperienced people to install it alone. They have to understand the concept. They have to understand the architecture and be able to manage the credentials required to authenticate. I had these problems, for example, when I set up the UC port.

I handled the implementation by myself.

I worked with local partners during implementation. They had a very good background.

I can't speak to the exact pricing. I don't manage that. 

While I did not evaluate other options, it's my understanding that my managers did. I don't have any details, however.

We are Broadcom customers. 

We are not actually using them as cloud capabilities. We are only running on-premises.

We have yet to use any AI functionality. However, we are interested in the possibilities. 

I'd rate the solution nine out of ten. 

We use Automic to coordinate batch processes for Oracle Utilities products like customer care and billing, and work and asset management. It helps us load customer data, meter reads, and process billing. We also use it to make calls to Solar processes and for file transfers across servers.

I like the GUI interface of Automic. We use it to coordinate batch processes and it's beneficial for orchestrating various processes, especially in the context of Oracle Utilities products.

Automic's database structure is not intuitive. When upgrading, the system breaks down frequently and we require a lot of support. More visual aids in the documentation would be helpful.

Probably four or five years, but I started focusing on it more in the last two or three years.

It's pretty stable once you fix the initial issues after deployment.

Scalability is good.

They are good and helpful, but many issues require support tickets due to inadequate documentation.

Positive

The pricing has been increasing significantly over the years, raising operational costs instead of reducing them.

We've been looking into other possible replacements because the pricing with Broadcom has increased significantly.

I would rate Automic a six due to its high price and other issues. For new users, I'd advise taking training courses and learning to read log files effectively.

We don't use it in my company. We implement for our customers. They primarily use the solution for workflow automation and work close with oracle. 

This is an easy-to-use, user-friendly product. The user interface is very simple and straightforward. 

It scales well. We can increase or reduce the number of nodes as needed. 

It is easy to set up. 

The solution is stable. 

The support could be better in the future.

They should work to reduce pricing. 

I've been using the solution for around two to three years.

It is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. I'd rate the stability nine out of ten. 

The solution is very easy to scale up and down by increasing or reducing nodes. 

I'd rate the scalability ten out of ten. 

Our clients are quite sizable, at least in Thailand. They are all enterprise-level organizations. 

The solution was recently acquired by another company, and since then, support has suffered. They need to work to bring better support services back to the product. 

Neutral

I am also well-versed in Stonebranch Universal Automation Center.

The setup is pretty straightforward. I'd rate it eight out of ten in terms of ease of implementation. 

Deploying the solution only takes about one day. You simply have to install and configure, and you are ready to go. The process is fast. 

We have a team of five that can handle deployment and maintenance tasks. 

This is quite expensive. It's one of the most expensive on the market. That said, I can't speak much about the exact pricing. I would rate it six out of ten in terms of affordability.

We are partners. 

I'd invite anyone to try the solution as it is user-friendly and has an easy user interface. It's functional and scalable. Overall, the product is quite good. 

I'd rate the product nine out of ten. I'm very happy with it in general. 

We used Automic for a multinational pharmaceutical client.

In the latest version, we can access the solution through a web browser as well. 

The web-based edition is missing a lot of the most important features available in Automic, we have absence. For example, when I'm scheduling a job, there is normally a flag that you can toggle to activate and deactivate the task, but that doesn't work properly in the web version. It's missing a lot of the calendar and scheduling features. 

My organization used the tool for almost 10 years, but we were dissatisfied when we upgraded to web-based edition because it doesn't provide all the options. It's challenging to create a new job or edit and reconfigure an existing. The web version has to be improved on various levels. 

Previously, we were using Solaris with Automic, but now I think it's Unix and Windows. I don't know what version you are going to provide for the cloud. The cloud always supports Unix and Windows, so it means the tool is cloud compatible.

In the web version, everything is moving from the on-premise server to the cloud. So in this scenario, the Automic tool has to be more cloud-oriented. We are not sure how it will work in the cloud. Since 2011 or 2012, we have been using Automic on-prem only. It would be nice to have more documentation about using the cloud version of Automic. The tool could be more user-friendly as well. Most people consider Automic to be a difficult tool to understand and use.

I've been using Automic for six years, but we just switched to another tool called AutoSys six months ago.

Automic is 99 percent stable. We've never had a problem with stability.

The scalability could be improved because we have three kinds of tools on our hardware itself, and we don't know whether Automic will accommodate the other two jobs as well. We have 200 direct users and probably 1,000 who benefit from the tool indirectly.

It depends on the terms of the support contract, but sometimes it will take two or three days to fix an issue. The impact is high because this type of job scheduling solution is used mostly for finance. For example, let's say there are 3,000 jobs scheduled, and four jobs fail. That could mean millions of dollars lost.

It should be fine If they provide support within eight to 16 hours, but they typically take three days to get a response. That won't work because on the impact side. On the other hand, it's highly stable, so we are generally okay, but we still face some bugs every six months or so. When that happens, we expect a speedy response.

The initial setup was straightforward, but it gets complex when you start using it. It will only be complex if you're a new user. The total deployment time for the original and web version was about three months. That includes installation and testing. During the testing, we found missing features, so it took three months to set the solution up, configure it correctly, and test it. 

The personnel needed to manage and maintain the solution depends on staffing and scheduling. For example, If you are providing 24-hour support 365 days a year, you need six at the most. We need one person per shift, and we have three eight-hour shifts. Including backups, that's three to six people. 

I don't have any numbers about the return handy. We didn't renew the license, and we've already onboarded the other solution and started using it. It's costly and our companies are cutting costs. They consider this an extra cost, so we didn't renew for this year.

The license for Automic is around $7,000 per year, which is somewhat costly, but it includes enterprise support. 

I rate Automic Workload Automation eight out of 10.

Right now, we are working with version 10 of the product, it is very good. We are very happy with it. However, we have to upgrade to a different version and there are a lot of things that are different, and we are not completely convinced how it will work. 

Our normal functions, what we had in version 10, are lost or not there. So, we will have to see how it will work in the future. As a company and as a product, though, we are ready to upgrade.

It is a batch application. We have a daily batch that we have to start. This application controls the batching. So, this application is essential to our company.

We have a lot of places in Germany. For example, if there was someone in Munich who wants to send data to someone in Hamburg, it is very easy to do a production application safely and quickly, because we have everything in one system. We just do a file transfer. 

It depends for me as an administrator. There are a lot of features which help us get a stable application. It is easy to have a stable production line, because this app supports us very well.

I hope in the next release that they will solve all the bugs which they have found in development. 

I hope going forward they will make some changes to the documentation. I hope they will write into the documentation what has changed and what the new names are. For example, some features have a new name. I hope they will make a translation the names in the old version to the names in the newer version. This would be a very important thing.

Version 10 is very stable. We have no problems with the product. 

Some problems could happen in the future because the current version does not seem to be stable. There are a lot of things which could bring danger into the stability of our work process, because things have been changed, and it is not possible to work the product in the same way. We have to accept the changes, and we are not sure if our employees will be able to accept the changes in such a short time frame and perform them the way they should.

There are so many possibilities to be used from this product, and every company is using it in their own very special way. Though, I don't think every company is using it 100 percent for all of its possibilities. There are a lot of areas that you can go with it.

When I came to the company, they were already using Automic. They had been using it for a long time.

The complexity of the initial setup depends on the person who is performing it. It was okay for me, but I have some colleagues who have had some problems with it.

We have increased efficiency with this application.

I prefer this product.

We use it to schedule our production workload.

We scheduled our database maintenance jobs through ASP and when we did this, we scheduled them in a certain defined way that we expected them to run. And when that was initially set up, there was no consideration for a database not being available so if the jobs tried to run when a database wasn't available, obviously they wouldn't work and an operator would have to intervene.

The plan was that people would open requests to have jobs held at that time. When there were only one or two databases, that wasn't hard to maintain and people did it. When we grew to many, it became harder to do that. Then with the change in how we're doing stuff, everything happens more, servers get booted more, more changes.

We use features of the product that allow us to determine if the database is available and to only allow the jobs to run when the database is available. So that saves a lot of manpower in the one group that was opening requests to hold jobs, and in the other group which had to implement the request to hold the jobs. It eliminated all that and provided a more dynamic environment for when these jobs can run, without operator intervention. 

That is something we started about two years ago. We fully implemented it last year and we've noticed a big savings in manpower.

It's easy to use. When you schedule jobs, if you can speak English you can schedule them easily and correctly.

There's a lot of flexibility because the product allows you to do many tasks, in multiple ways, so you can choose the way that works best for your environment.

How they handle cross datacenter failover, because they have a really good High Availability solution that works well within a single sysplex, but in our environment, since we have two main datacenter locations, we have two separate sysplex. And, while when everything is working ASP can control jobs both here and in the other location, the current product does not support High Availability across datacenters. That is something we would like to see the product have.

Currently, what we have is we have a homegrown solution, because we're required to have that kind of resiliency, because it's our enterprise job scheduler.

When everything's working, we're invisible. When it's not working: "Why aren't you working?"

Stability is a 10 out of 10.

Scalability is a 10 out of 10.

Tech support is a 10 out of 10.

When I started, we were already on this product, but I do know that they were using a competing product before and they felt that this product had more of what they wanted. So they converted from the competing product to this product.

When the company chose this product, it was actually pre-CA, and then CA acquired the product. But for the most part, they've kept it what it was. While it has a new owner, it's still the same product.

I believe it's pretty straightforward. It's a complex thing by nature so it's not going to be super simple, but it's not like you can't do it either.

I believe experience helps. And in our case, we had a lot of help from the vendor, so while we, per se, didn't have the experience, there were people helping to get us going that did have the experience. So maybe I'm underestimating how much that was important, because it was available, even though it wasn't coming from me or one of my team members, but somebody else was providing it.

I'm really the technical guy. Pricing is not something that I deal with so I can't answer that question.

That would have been 20 years ago, so the market is a little different than it was back then. There are solutions today that did not exist back then. Pretty much all of the big players still exist today. But we're definitely in a different place today than we were back then.

No advice other than the normal stuff that you would do when looking at any product: Does it fit what you need? 

I would recommend doing a proof of concept before signing any contract. Everybody's stuff sounds good on paper and everybody's stuff can do everything, but what happens when you bring it in your environment? Does it do what you need it to do? Those are the most important things. The other stuff, while it's nice stuff, if you can't do what the product is required to do, then there's no value to the product.

For us, it gives us what we need so it's a good value. Forget about the price, because if the product doesn't do what you want, it doesn't matter what the price is.

I would rate the product a 10 out of 10. We use the product everyday and it works and, for the most part, every time we have a problem, it seems it's never my product's problem. It's: I have a problem because there's a problem on the system, so guess what? We're not going to be working. I need a stable system to run. 

Or if it is our problem, maybe we didn't do something we were supposed when we found out that we were supposed to do this, and we reconfigure something and then we move forward and we don't have that problem any more. Or we re-architect how we do stuff, because we've had to make tweaks of stuff as we've gone along. We would do stuff and it would work and then we would do something a little differently, and what we did, it didn't work and we'd have to figure out what the problem is and fix it.

Again, the flexibility of the product allows us to do things multiple ways. We might have started doing it one way and that worked for a while and then either something changed -whether we had more volume or we did something a little differently or we had different issues - and then we would address them with different tweaks, solutions.

We are an insurance company, so we are using Automic Workload Automation to control all of the night processes, the batch processes, and also the EDW. It is for controlling the other databases that we are using. We take all the data from the S400 and move it to other databases in order to do queries and gather other information. We also use it to control between a lot of other systems because we do a lot of workflow between other computers, so we can control the time and flow and other things.

The feature that I have found most valuable is that we can control between a lot of operating systems and other products because we have a lot of old and new products in our environment. It helps us to control all of them together.

In terms of what can be improved, we are in Israel, so we work in Hebrew. Now they are starting to move it also from English to Hebrew and to support the language, but for us it has been very difficult because the Hebrew looks like gibberish. So there are language issues.

The price could always be improved.

Now we are starting to check the AI, which is a new product there which can give us more information like Iosoft and other things. I hope it can help us because right now we cannot know when we can improve or not because we only see part of the data. I hope that if we can collect all the data we can improve and maybe use less CPUs in S400, but at least we can improve by knowing what happened in our batch processes. Meaning, how much time and how much CPU it takes not only for one month but to see all the information for one year. This can improve our flow.

I have been using Automic Workload Automation for more than 15 years. Now I'm using the latest version.

It is not stable all the time. Just now, we upgraded and we found out that it does not support the requirement that is an important computer in our environment, so the new version is not stable right now. I spoke with them and I hope they understand that they have to fix this.

Automic Workload Automation is scalable.

I not remember the number using it because we are always adding more and more. We add a lot of servers to this because we took the daytime process and brought it to our other system. In the Automic, I think we have about 50 users or something like that and a thousand processors.

We only have four people for maintenance of the solution here, and that's all. It is not complicated.

We are using this product extensively and I think we have plans to increase the usage.

We added the new features and we are looking to make our environment do things automatically, less manually.

Our license is for three years, or something like that.

My advice to anyone considering Automic is to know how they will use it, because they changed the license type. Previously, we used to pay for each computer. Now we pay for all the environment, no matter how much we use.

We change the license for the processors, but it depends on the environment that you want to automate, so I cannot give any advice. It depends on what you want. If you only have a few computers that you want to use, you can use it by computer, by your agents. If you have a lot of processors, don't pay for the processors. It depends on the type of environment you use it in. Sometimes you prefer to do it with the scheduling if you have a lot of workflows.

On a scale of one to ten, I would give Automic Workload Automation an eight. This is because of the language and stability issues.

One key point for our selling is our business's dashboarding. It was something very important and we used it at the beginning very much. 

It is an easy product to use, and we can use it for end-to-end process automation. We also have the capabilities to do dashboarding, therefore we have an analytics product that can provide other things and value for us.

We would like to see more dashboarding into the product, maybe an embedded Java API which we would be able to load on our own objects into the system. We were writing them on our own, but we would like this standardized.

The system is a stable product overall. We did something maybe a little bit wrong at the beginning, so we had a little bit of an unstable product. Since we have merged to version 12, it has become a stable system.

It is a very scalable product, not only for Workload Automation, but also for the other products provided by Automic or CA Automic. You can use the baseline, the automation engine, and scale up what you need.

Technical support is excellent from our past experiences with Automic. At the moment, we are facing a few issues with the merge of CA and Automic. We hope these will be resolved soon.

Our old solution was not able to deliver a real end-to-end automation. It was embedded in SAP. An excellent product for SAP so far, but it is not able to be scalable for the end-to-end. 

This was the reason why we did research at our company to do an end-to-end product assessment. In the end, the decision was to made to go with Automic.

During our PoC, I was the guy who was implementing and installing the product. I thought with the help of a consultant that it was an easy installation. 

On the shortlist, when we purchased the product, we had CA, Stonebranch, BMC Control-M, Automic, and our current vendor in mind. A few of them were kicked out during the first session because they were not able to deliver everything. In the end, we had BMC and Automic.

I would like to rate it as an eight out of 10, because there is room for improvement, and I would like to see this from Automic. They should continue to work on the product to improve the product.

If my peers are looking for a real end-to-end solution, not only some siloed solution, they should go for Automic because it is an easy product to use. It is easy to install. I can recommend this product to other customers.

Most important criteria when selecting a vendor: The partnership between a vendor and customer is very important. You should have a good account manager in place who is dealing with the customer. This is something very important for us. Customer service and support are also important.