Automic Workload Automation OverviewUNIXBusinessApplication

Automic Workload Automation is the #5 ranked solution in top Workload Automation tools. PeerSpot users give Automic Workload Automation an average rating of 8.2 out of 10. Automic Workload Automation is most commonly compared to Control-M: Automic Workload Automation vs Control-M. Automic Workload Automation is popular among the large enterprise segment, accounting for 74% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a financial services firm, accounting for 20% of all views.
Automic Workload Automation Buyer's Guide

Download the Automic Workload Automation Buyer's Guide including reviews and more. Updated: November 2022

What is Automic Workload Automation?

Deliver the fully agile enterprise using CA Automic Workload Automation 

The modern enterprise needs to orchestrate a complex, diverse landscape of applications, platforms and technologies. Workload automation can prove a critical differentiator, but only if it provides intelligent automation driven by data analytics.

The IT landscape is currently more complex than ever: Islands of automation are a barrier to scaling and standardizing your workload activities. Processing errors are common because of manual handoffs. And the lack of an end-to-end view of the business process make inefficiencies and problems difficult to resolve. In addition to this, you are operating 24x7 and cannot find maintenance windows to upgrade your infrastructure in order to innovate. 

CA Automic Workload Automation gives you the agility, speed, visibility and scalability needed to respond to the constantly changing technology landscape. It centrally manages and automates the execution of business processes end-to-end; across mainframe, cloud and hybrid environments in a way that never stops—even when doing an upgrade to the next version.

Automic Workload Automation was previously known as Automic Dollar Universe.

Automic Workload Automation Customers

ING, Adidas, 84.51, ESB

Automic Workload Automation Video

Automic Workload Automation Pricing Advice

What users are saying about Automic Workload Automation pricing:
  • "There are different licensing fees for cases where high availability is important."
  • "I'm not sure about licensing costs, but I know the base price is about $3,000, and you can get some kind of discount per node."
  • "Its price is way up there with BMC. It is a little bit on the expensive side."
  • "The pricing is based on the number of servers and agents."
  • "They have changed the pricing on their licensing, and it's cheaper than before."
  • Automic Workload Automation Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Application Developer Senior Analyst at a tech vendor with 10,001+ employees
    Real User
    Top 20
    It's a stable solution for scheduling finance-related tasks
    Pros and Cons
    • "Automic is 99 percent stable. We've never had a problem with stability."
    • "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."

    What is our primary use case?

    We used Automic for a multinational pharmaceutical client.

    What is most valuable?

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

    What needs improvement?

    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.

    For how long have I used the solution?

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

    Buyer's Guide
    Automic Workload Automation
    November 2022
    Learn what your peers think about Automic Workload Automation. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    655,113 professionals have used our research since 2012.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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.

    How was the initial setup?

    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. 

    What was our ROI?

    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.

    What's my experience with pricing, setup cost, and licensing?

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

    What other advice do I have?

    I rate Automic Workload Automation eight out of 10.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Department Manager at a insurance company with 1,001-5,000 employees
    Real User
    Top 10
    Provides good control between different systems and processes.
    Pros and Cons
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

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

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Buyer's Guide
    Automic Workload Automation
    November 2022
    Learn what your peers think about Automic Workload Automation. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    655,113 professionals have used our research since 2012.
    Marcos L. Domingos - PeerSpot reviewer
    Support Analyst, Lead at Sonda IT
    Real User
    Top 5Leaderboard
    Good integration, responsive support, and a short learning curve
    Pros and Cons
    • "The monitoring and troubleshooting features are rich and with the dashboards and other features, automation work is made easier."
    • "In most of the packages available, it took time to study and gain knowledge of the features and resources due to poor documentation."

    What is our primary use case?

    We have several corporate solutions that need to be integrated with our ITSM products.

    Automic facilitates integration to ensure the correct execution of ITIL process workflows. The first was to create service offerings for provisioning virtual machines in both private and public cloud environments.

    The creation of virtual machines would have to contemplate the current process of changes, releases, and configurations. Our service catalog should make service offerings available; these involved diverse operating systems, different hardware configurations, and some functioning web services.

    An approval process would also be contemplated, where the main steps would be the registration and closing of the change tickets, as well as the registration and deactivation of the generated configuration items.

    How has it helped my organization?

    We have several solutions, but we opted for Automic following the natural evolution of CA Process Automation. The fact that it has native integration with ITSM solutions was also an important factor in the decision. Due to the various possible integrations, all of them need to be in accordance with the ITIL process. This would facilitate the actions that would come in order to implement a DevOps culture in the organization.

    The service support is acceptable and response times are fast, whether from the manufacturer itself or from partners.

    What is most valuable?

    Due to the fact that we have several solutions to be integrated into the ITSM processes, the possibility of having multiple client areas is important because it favors organizing integrations and automations.

    We have other products from Broadcom (CA Technologies) in operation, and integration with these products was very smooth. It integrates easily with CA Service Desk Manager, CA Service Catalog and CA Process Automation, and more.

    Adding that to the various packages and plugins available at Marketplace, the learning curve to make automation work was very fast.

    What needs improvement?

    We found that some Actions Packs and plugins do not have documentation, are incomplete, or are of poor quality. In most of the packages available, it took time to study and gain knowledge of the features and resources due to poor documentation. This time could be reduced if the documentation was more complete.

    If the documentation is not well built, there will always be extra time for testing and some of these generate doubts that turn a simple job into something complex. With the project's schedules in progress, it is difficult to set deadlines, even if they are adjusted for more.

    For how long have I used the solution?

    I have been using Automic Workload Automation for two years.

    What do I think about the stability of the solution?

    The product demonstrates excellent stability, regardless of whether the installation has high availability or not. We have not seen any problems in this regard.

    What do I think about the scalability of the solution?

    It is a product that scales easily, but with a short aggregate in its version with high availability.

    How are customer service and technical support?

    The most experienced support team is international. Some professionals at the time of implantation are no longer available. The service responds quickly to doubts and so far we have had no difficulties in this regard.

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

    We have also used CA Process Automation, MS System Center Orchestrator, and Control-M.

    How was the initial setup?

    Complexity only exists when installing high availability. Support from the manufacturer was required.

    What about the implementation team?

    It was through a Broadcom partner. The team was very experienced in the product, including with use cases in a company in the same area in which our organization operates.

    What was our ROI?

    We don't have enough time to calculate ROI yet, but we are optimistic.

    What's my experience with pricing, setup cost, and licensing?

    There are different licensing fees for cases where high availability is important. There is also a certain complexity in this type of installation.

    Which other solutions did I evaluate?

    We only evaluated Broadcom (CA Technologies) products.

    What other advice do I have?

    Overall, the user experience is extremely good. The monitoring and troubleshooting features are rich and with the dashboards and other features, automation work is made easier.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Kuntal Sadhu - PeerSpot reviewer
    Architect at Wipro Limited
    Real User
    Top 10
    A workload automation platform with many useful features, but file transfers could be better
    Pros and Cons
    • "I like that Automic Workload Automation has many features compared to other products. There are a lot of good features, and architecture-wise there is a valuable client concept. The architecture and the multi-tenancy is a multi-client concept. That is also useful."
    • "The manage file transfer area could be better. The file transfer area needs improvement. Other products like Control-M have some good features in this area."

    What is our primary use case?

    I use Automic Workload Automation for SAP-related use cases. They are primarily functional and nonfunctional job executions for SAP Windows Unique. So, mainly for a business process or business functions, job execution, and creating dependencies related to retail like Oracle and SAP jobs execution.

    What is most valuable?

    I like that Automic Workload Automation has many features compared to other products. There are a lot of good features, and architecture-wise there is a valuable client concept. The architecture and the multi-tenancy is a multi-client concept. That is also useful.

    What needs improvement?

    The manage file transfer area could be better. The file transfer area needs improvement. Other products like Control-M have some good features in this area.

    For how long have I used the solution?

    I have been working with Automic Workload Automation for the last ten years.

    What do I think about the stability of the solution?

    Automic Workload Automation is a stable solution. It's good because, architecture-wise, it has high reliability. So, we recommend it to our customers and ask them to use two or three-node architecture. If one goes down, the other should be up. So, two or three-node architecture is stable.

    What do I think about the scalability of the solution?

    Automic Workload Automation is a scalable solution. Scalability depends on the architecture. We are currently running 10,000 jobs or 20,000 jobs with two-node architecture. If we want to add one node or if we're going to add more resources, you can do it online. You do not need any downtime. You can run thousands of pages and millions of jobs.

    How are customer service and support?

    Technical support is good. I worked with a particular dedicated client, and we had to reach out to Broadcom once or twice a month for help. Whenever we raised a ticket, they responded within a day or the next day. Most of the time, it wasn't even an urgent issue.

    Nowadays, they have very helpful knowledge articles. If I have an error and they share some knowledge articles, I get the solution through those articles. They are helpful.

    How was the initial setup?

    The initial setup is straightforward. It hardly takes half an hour or one hour, but small components like agents must be installed later. The initial fresh installation will take about one hour.

    What's my experience with pricing, setup cost, and licensing?

    I'm not sure about licensing costs, but I know the base price is about $3,000, and you can get some kind of discount per node.

    What other advice do I have?

    I would tell potential customers that they must use third-party software like Control-M, Stonebranch, AutoSys, or Tidal to migrate to Automic Workload Automation. 

    If we compare it to any market-leading software, like Control-M BMC, Automic has the same capability, but Automic provides everything as a bundled product. Others like BMC sell their products in different modules. So, you have to buy the license, and on top of that, you have to buy the separate modules. 

    I would also tell potential users that with competing products, they need a job-based license if they plan to scale up and avoid penalization. But as Automic is node-based, there will be no penalty if you are running 5,000 jobs today and 6,000 jobs tomorrow. It'll be the same.

    On a scale from one to ten, I would give Automic Workload Automation a seven.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Sr Systems Analyst at a retailer with 10,001+ employees
    Real User
    Top 20
    It was a natural transition for us from ESP, but there are glitches where things don't always work the way they should
    Pros and Cons
    • "The reason we went with Automic is very simple. We were using ESP, which was a Broadcom product. So, Automic happened to be a natural fit. It was a much easier transition from ESP to Automic. We had familiarity with the vendor and the product."
    • "There are pain points, like anything else. Sometimes, things they say work, and sometimes, they don't work. You need to find out why they don't work and then go back and have them fixed."

    What is our primary use case?

    It is basically for workload automation. Automic has also got other features, but we are not using them. We are just sticking to workload automation. We basically do batch processing through automation. We mostly have nightly batches and cyclical batches during the daytime.

    What is most valuable?

    The reason we went with Automic is very simple. We were using ESP, which was a Broadcom product. So, Automic happened to be a natural fit. It was a much easier transition from ESP to Automic. We had familiarity with the vendor and the product.

    What needs improvement?

    There are pain points, like anything else. Sometimes, things they say work, and sometimes, they don't work. You need to find out why they don't work and then go back and have them fixed. 

    For how long have I used the solution?

    We have been using it for close to a year.

    What do I think about the stability of the solution?

    Like any product, there are glitches. We had used ESP for almost 30 years. So, we were very familiar with the tool, and it was pretty stable. This is an agent-based solution. So, sometimes, the agents don't respond and triggers don't work. Those kinds of issues are still there.

    What do I think about the scalability of the solution?

    Workload automation is not heavy stuff. When things have to happen, they just wake up and do the work. It is not like an E-commerce solution where your workload is going to increase by X factor and then you add X servers. It is not that way. So, from a scalability point of view, it is scalable.

    How are customer service and support?

    They're pretty okay. We worked with CA before Broadcom bought them. So, we've got a long working relationship with them for over 20 years, and their support is pretty okay.

    How was the initial setup?

    They work with a partner to help you with implementation and migration. The partner had tools for migration from ESP to Automic, which was helpful.

    What's my experience with pricing, setup cost, and licensing?

    Its price is way up there with BMC. It is a little bit on the expensive side.

    What other advice do I have?

    We only use it for workload automation. We haven't explored the tool as such. It claims to have a lot of features, but we have just touched the surface of it.

    From a workload automation point of view, there are multiple tools. You've got BMC. You've got Automic, and you've got Stonebranch. Stonebranch is the smaller of the lot, and from a solution perspective, their agent can work with any other automation tool. Cost-wise also, it is much cheaper than the others. If you are a small enterprise and don't have an existing tool, Stonebranch wouldn't be a bad option.

    I would rate Automic Workload Automation a seven out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    SandeepKumar10 - PeerSpot reviewer
    System Administrator at MIRAKI TECHNOLOGIES
    Real User
    Top 5
    Scripted automations are easy to convert for specific requirements
    Pros and Cons
    • "The solution includes many features and is scalable and stable."
    • "The pricing has the potential to be high."

    What is our primary use case?

    Our company uses the solution to run scripts for customers. For each use case, we create a description and use it with the agent to schedule run times. 

    Our team size ranges from 40 to 50 people and varies across clients or use cases. 

    What is most valuable?

    The solution includes many features and is scalable and stable. 

    The automation tool provides scripting that is easy to convert for specific requirements. 

    What needs improvement?

    The pricing has the potential to be high because it is based on the number of servers and agents. 

    For how long have I used the solution?

    I have been using the solution for five years. 

    What do I think about the stability of the solution?

    The solution's stability is better than other products. We do not see the solution fail much at all. 

    We had issues with other products where servers would go down or items needed to be fixed and that caused struggles. 

    What do I think about the scalability of the solution?

    The solution is scalable. 

    How are customer service and support?

    I worked closely with technical support for overall assistance during my first installation and they were dedicated and helpful. 

    I have not needed support for issues but am currently working with them to complete another installation. 

    Sometimes support leaves out details, but they do help a lot with tools. 

    I rate technical support an eight out of ten. 

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    The ease of setup depends on the person who handles it. The setup is a bit different because it includes four or five components that require separate installations. There are various steps and processes to follow. If you have knowledge of the solution, then setup is easy. 

    Typical setups take 14 to 16 hours for server and data installations. 

    What about the implementation team?

    We implement the solution for customers. 

    What's my experience with pricing, setup cost, and licensing?

    The pricing is based on the number of servers and agents. 

    Which other solutions did I evaluate?

    Our developers chose the solution because of its scalability, stability, and features. Technical support is also much better than what competitors offer.

    The solution allows us to do everything we want. We can use it for smaller items or large-scale projects with no problems. 

    What other advice do I have?

    It is important to understand workload automation and how the solution functions. Work with your customer to determine the infrastructure and number of agents or servers. Create an infrastructure table and then starting installing to those specifications. 

    I rate the solution a nine out of ten. 

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: My company has a business relationship with this vendor other than being a customer: customer/partner
    Flag as inappropriate
    PeerSpot user
    Senior Technical Consultant at a tech services company with 51-200 employees
    Real User
    Top 5Leaderboard
    Robust, highly scalable, and easy to implement
    Pros and Cons
    • "The most valuable features are its robustness, it's highly scalable, and it's easy to implement."
    • "This solution's out-of-box automation sets could be improved. They could be industry standardized out-of-box, or even runbook automation processes could be useful—just some plug-and-play automation processes out-of-box. It has many integration capabilities, from APIs to databases, but if the customer sees some out-of-box automation processes in it, it could be useful."

    What is our primary use case?

    This solution has many use cases because it's automation, so the sky is the limit. It can be useful for any workloads—DD operation, disaster recovery, data center automation—required by the customer. 

    This solution is deployed on-prem. 

    What is most valuable?

    The most valuable features are its robustness, it's highly scalable, and it's easy to implement. 

    What needs improvement?

    This solution's out-of-box automation sets could be improved. They could be industry standardized out-of-box, or even runbook automation processes could be useful—just some plug-and-play automation processes out-of-box. It has many integration capabilities, from APIs to databases, but if the customer sees some out-of-box automation processes in it, it could be useful. 

    As for additional features, a best practices library could be good. Also, maybe more technology connectors, in order to connect and run the automation, so more out-of-box integration points. 

    For how long have I used the solution?

    We have been dealing with Automic for around three years. 

    What do I think about the scalability of the solution?

    This solution is highly scalable. In our country, we have more than 30 customers using this solution. 

    How are customer service and support?

    I would rate support an eight out of ten. From a customization point of view, it requires some technical knowledge. 

    How was the initial setup?

    The installation is very straightforward. The time it will take depends on the implementation and the size of the project—it can range from one day to five days. A team of one to three people could be enough for deployment. 

    What about the implementation team?

    We implement this solution for clients. 

    What's my experience with pricing, setup cost, and licensing?

    They have changed the pricing on their licensing, and it's cheaper than before. 

    What other advice do I have?

    I rate Automic Workload Automation a nine out of ten. I recommend this solution to others. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    PeerSpot user
    Managing Consultant at ICT
    Consultant
    An enterprise scheduling solution for the automation of IT processes
    Pros and Cons
    • "Both the stability and the scalability of Automic Workload Automation are great."
    • "There are some monitoring features that could be added."

    What is our primary use case?

    We have many clients in financial services. We install, implement, and configure this solution for them. They use this solution to automate financial processes.

    We have roughly 100 users, using this solution. We expect to increase the number of users of this solution.

    What needs improvement?

    There are some monitoring features that could be added. For example, when we have some external dependencies from processes that were run the day before or one week before, these dependencies are always complicated to configure.

    Workload Automation should also have better RPA features, too. I think that would definitely improve this solution. Instead of having to have a separate solution for RPA, it would be nice if Workload Automation could handle it, too.

    For how long have I used the solution?

    I have been using Automic Workload Automation for more than 10 years.

    What do I think about the stability of the solution?

    Both the stability and the scalability of Automic Workload Automation are great.

    How are customer service and technical support?

    Usually, we only contact support when we have issues with bugs, etc. I think some users have support for installation and configuration.

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

    I have used plenty of automation solutions. 

    I made the move over to Automic Workload Automation as many other solutions weren't compatible with REST APIs. For me, it was a matter of evolution. The new solutions come with more features, more updated technologies that I can use. 

    How was the initial setup?

    The initial setup, installation, and configuration are very straightforward.

    What other advice do I have?

    Overall, on a scale from one to ten, I would give this solution a rating of eight. If they added some additional features for monitoring, I would give it a higher rating.

    If you're in need of RPA capabilities, this may not be the solution for you. RPA can be applied for some processes, but not for everything. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Buyer's Guide
    Download our free Automic Workload Automation Report and get advice and tips from experienced pros sharing their opinions.
    Updated: November 2022
    Product Categories
    Workload Automation
    Buyer's Guide
    Download our free Automic Workload Automation Report and get advice and tips from experienced pros sharing their opinions.