Automic Automation Reviews

We are a Broadcom partner. We use it internally for some smaller tasks, and we also help customers implement the product and run their projects.

It is primarily used for automating business processes. Customers use it to automate a variety of processes. Customers mainly automate their financial processes. Some of the customers are using Atomic Automation to automate, for example, the production of cars or automobiles.

Customers want to move away from manual monitoring and checking processes. Automating these processes helps in time-saving and reduces human error. When you automate business processes, it reduces mistakes. It eliminates the risk of manual errors such as typos. There is a 20% to 30% reduction in human error.

It fulfills all the needs when it comes to visibility and control across various operating platforms. 

It is the perfect product for managing processes that span multiple operating platforms. Automic Automation has the widest platform support compared to other products, such as Control-M, Tivoli from IBM, or Stonebranch.

It definitely helps with compliance processes. We have had a lot of customers for two years with a focus on compliance, and it works. They were successful.

Due to the fact that our customers can automate a lot of things, it reduces operating costs. It is hard to give a number because the savings are different for each customer. If a customer never had any automation, there could be about 80% savings after implementing Automic Automation, whereas for a customer who already has automated tasks, the difference will be less by adding Automic Automation. They might see 5% to 10% more savings.

Automic Automation helps improve our ability to meet SLAs. In the recent versions, SLA management has been integrated, which previously was an external component. Because a lot of customers used it and asked Broadcom to implement SLA management into the workload engine, Broadcom included it. We see more and more customers running their SLA management via the Automic Automation product.

The best feature is its wide platform support and the user interface. It offers a consistent user experience regardless of whether you are implementing a job on a mainframe, SAP platform, or other machines.

Recent changes in Broadcom's licensing model are making some customers reduce tasks or replace Automic Automation. This is something Broadcom should consider.

There is room for improvement in their support.

My first contact was around the years 1986 or 1987. I started using it when Broadcom was not its owner. It was called UC4 and then was renamed a couple of years later to Atomic Workload Automation. Then CA took over or acquired the company, and after that, Broadcom acquired CA.

I would rate the stability of the solution at eight out of ten.

I would rate its scalability a ten out of ten. It has a very wide platform support and is highly scalable.

In our organization, we have about 25 people working with Automic Automation. Our clients are small, medium, and large organizations. We have small clients running a thousand tasks per day and big enterprises running one million or two million tasks per day.

Customer service has improved over the years. I would rate their support an eight out of ten. It mainly depends on the person who picks up the ticket and solves the issue.

Positive

I do not have much experience with other products, but I know how they look and how to operate and navigate them to implement things. What makes Automic Automation unique is the wide platform support and easy-to-use, web-based user interface.

The initial setup should not require as much time. The solution is straightforward to set up.

The implementation can take a couple of hours. If different interfaces to different third parties are involved, it might take a week or two weeks.

We have seen both on-prem and cloud deployments. Some customers are thinking about moving or migrating the on-prem installation to the cloud because they are also moving their other applications, such as SAP and databases, from on-prem to the cloud.

On average, moving the engine to the cloud takes a few days to a week. This does not include the time required for the communication between us and Broadcom.

It does require maintenance. You have to maintain the database. This means deleting old information from the Automic database. Your database grows and grows and grows. You can spend money to buy bigger storage and bigger databases, but in the end, you will have a maximum limit. You have the maintenance aspect of the database. There is also the user management aspect, but this is not a daily business. You do not add new Atomic Automation users to the system on a daily basis.

Once every six months or once a year, we have to upgrade the system to a new version, apply service packs, apply hotfixes, etc.

Broadcom has recently changed its licensing model. I do not deal with pricing, but from what I heard from customers is that due to the increased pricing, some of them are thinking of reducing tasks in Automic to have fewer executions. Others are thinking of replacing Automic Automation.

If you are evaluating this solution, talk to reference customers. Ask about their experiences with Automic. Reference customer contacts are available through Broadcom and partners. Personal experience and advice from current users are invaluable. You do not only have to read the documentation.

Once you have attended the training, which we always recommend, it is easier to use. Starting from scratch and only reading the documentation will not work. It will take you much longer to implement a business process. If you attend training, it is not very complicated because you learn all the tips and tricks. You learn how to implement things. You might get some examples from existing ones which makes work easier.

In Europe, we do not have a lot of implementations using Automic Workload Automation’s predictive modeling provided by the AAI capability. From what I have seen in presentations from Broadcom, it can serve in very complex scenarios and help simplify your schedules because it analyzes cross-dependency.

Overall, I would rate Automic Automation an eight out of ten.

The primary use case for the solution is to automate various manual tasks for clients in SAP or other solutions or make backups. The purpose is either to automate tasks or migrate from another tool to Automic Automation.

In the beginning, it is used to schedule some basic tasks, and as soon as the clients understand how the product works, they increase the scope by having more critical jobs. In the end, it is the core of the business making sure that all jobs are running properly.

Automic Automation enhances visibility for customers who previously had no clear insight into their scheduling tasks, allowing them to quickly see and address issues. With other schedulers, such as AutoSys, most customers do not have the visibility to know and see exactly what is going on. The advantage of having a front end is that the customer has more visibility to see exactly where is the problem and how to solve it. They have more visibility today than in the past.

The advantage of using Automic Automation is that we can adapt to different business requirements. We have some customers who use Atomic Automation only for mainframe, and we have some only for Windows. Most of the time, we can modify or adapt the way of working based on business requirements. Some of them start by doing some basic jobs, and after that, they increase the scope by including SAP or some other application.

With Automic Automation, we can do a lot of things. One very interesting feature is being able to work with scripting, which is not possible with some other schedulers. We can cover all business needs with this product. For sure, as soon as they come out with a new feature, we investigate to see if we can apply this feature to the customer and help them use it. Automic Automation is very powerful and can satisfy all needs.

As a consultant company, we only help clients get started and train them in best practices. Afterward, they build the workflows themselves. Based on the feedback I have received, our customers would like to have some additional features, but they are mostly satisfied. For example, they would like to be able to print a workflow to have visibility. Sometimes, a workflow is quite complex, and they do not have the full picture of the workflow themselves. This is one feature, for example, that could be interesting for the customer. Other than that, Automic Automation is quite powerful, and we are able to satisfy many customers with this solution.

Their pricing model, which has changed now, seems costly to some clients. Pricing is a major issue for some clients due to changes in Broadcom's pricing model, causing some to seek alternative solutions. Most of the time, customers are not satisfied with its price. They sometimes decide to check if another solution is less expensive. It depends on the size of the company, but small or medium companies prefer to use a tool that costs less. We know that some customers are trying to see an alternative for Broadcom. This is not because the product is not good enough. This is mainly because of the price.

I have been working with Automic Automation for five years.

We are a partner of Broadcom. We install the Automic Automation software for many different companies in Europe. I have been working in this company as a contractor for more than five years.

The solution is stable. I would rate it an eight out of ten for stability.

Automic Automation is quite scalable, and we are able to increase or decrease the scale based on the job or automation needs of a company. This scalability meets most customer requirements.

Most of the time, we try to evaluate how many jobs or how many automation parts should be there in the company. We also have a contact in Broadcom to tell us about the best size for a company. We know what we can provide to the customer without any issues.

Our clients are usually small and medium companies. In our organization, we have seven or fewer people working with Automic Automation. Some of them are dedicated to one customer, and some of them are dedicated to three or four customers.

After the company was bought, the support was not satisfactory because most of the people left the company, but it has since improved and is now somewhat better.

Neutral

In the past, everything used to be on-prem, but now the trend is to go to the cloud. Some of the clients put applications like SAP in Google Cloud, whereas some of them are in Azure. We just use the normal image of Automic Automation and put them in the cloud. We have the same way of installing and working with it irrespective of whether it is on the cloud or not.

The initial setup is quite easy. There are certain requirements such as the database has to be up and running, which is done by the DBA who is internal to the company. The entire installation takes around two to three days.

In terms of maintenance, we try to follow the lifecycle of the product. It is mostly stable. If there is any issue, we have enough experience to cover the need.

We are a consulting company that assists with the start-up and training of clients. We do not maintain control after the initial setup as clients manage their systems.

Automic Automation has saved about 30% time of clients.

Pricing is a big issue for some of them because Broadcom changed the way of calculating the price. People have been their customers for the last five or ten years, but Broadcom decided to change the way of licensing by moving to the number of jobs runs and then they say that clients have to pay three million because they run one million jobs per day. The clients are quite surprised to see that the contract is not the same as before, and then they are afraid of paying more.

I would recommend Automic Automation to others. We know it quite well and know that we can satisfy our client's requirements. Because we have a lot of experience, we can cover exactly what they need.

It is user-friendly. If the clients want to start building jobs with the tool, it is not a big deal. It is quite easy to start with and they can go a little bit deeper with scripting and other things.

It is crucial to ensure clients receive the right support to implement best practices in automation. In the beginning, we help customers to make the workload as simple as possible. If they have some specific needs, we help them build some more complex workloads or schedules to satisfy their business needs.

I would rate Automic Automation a seven out of ten.

We primarily use Automic Automation for ETL and batch processes.

It automates pretty much any application for internal users, including file transfers, payroll, shipping, and billing. Some of them are business-critical and complex.

Automic Automation has helped the organization by freeing up people for other projects and tasks. The time spent on running business tasks has been decreasing consistently.

It does exceptionally well when it comes to managing processes that span multiple operating platforms, even though our use cases with it are limited.

In terms of the reduction in our job/workload failure rates, we only use our internal cloud, but because of being able to easily build self-remediation, even if the volume of failures does not decrease, the remediation time is so low, and the impact is minimal.

As for compliance, it is tightly integrated with some of our processes, allowing for task history to be shown and comments to be added for internal compliance, which is critical.

With the simplification of business tasks, Automic Automation has helped us reduce our operational costs, but I am uncertain if there is a direct monetary gain. While it reduces operational workloads and costs in terms of resource use, it may be a wash in a dollar-for-dollar comparison.

Automic Automation has been ingrained in our organization far longer than I have been, but it seems we were able to see its benefits very rapidly, within six months.

We majorly have flavors of Linux or Unix. We also have some Windows, VMs, bare metal, or Kubernetes. Automic Automation can be used with cloud and on-premises environments. This was very important, especially during transition periods, as we moved things into our cloud. If it was not able to interact with both, that would have caused major problems in migration efforts. We are currently using it in our internal cloud environment, but we may move a few things and look at GCP.

We have consistency in throughput when it comes to SLAs and we are able to have more self-remediation or to have remediation that requires minimal interaction to complete. Even if there is an issue, setting up the monitoring and doing remediation is quick.

The most valuable feature is the flexibility of the tool. With a little bit of time and understanding, it is capable of completing any business use case we have encountered. There are many ways to achieve desired results without much issue.

Anything related to the enhancement process is poor at best and should be more transparent. They should consider an open-source model where users can more easily see requests.

They need more long-term consistency in pricing and should consider support-based costs. They should find a model that has more long-term price consistency to not lose larger customers. They can even consider a perpetuity model and move towards support-based costs.

Finding better real-time solutions is hard because it is not designed for that. It does not work as well for activities that require real-time input/output, but it works very well for batch, ETL, or similar cases.

I have been using Atomic Automation for approximately 13 years.

If you increase the load without knowledge of maintaining database performance, you may see lag. However, in a well-tuned environment, it runs very smoothly. We have periods throughout the day where we get massive loads put on it. We see a small amount of slowness, but it is always a manageable slowness that self-corrects, so no issue.

The scalability is excellent. It does not perform real-time scalability in our environment, but because of the way we have built it, it can scale well past any thresholds with no issues.

Any problems that I have seen working with Broadcom do not include support. Support tends to be responsive. They are highly knowledgeable in their product area and very easy to work with.

Positive

I have been exposed to and had minor interactions with alternatives but not nearly as much as Automic Automation.

Any new deployments, upgrades, and environment rollouts have been easy and straightforward.

If you make a capable engineer with no experience in the product do it without a discussion with support, he or she might hit some hurdles because of the nature of the product. The documentation definitely serves you well if you know what you are looking for, but if somebody is coming in fresh, I could see them having problems. A discussion of steps with support can help any experienced IT technician manage an initial rollout.

We do all of our maintenance. Mostly we do it from within the tool itself, aside from things like OS patching or DB maintenance.

The number of people required for deployment depends on the environment. The biggest piece that is going to affect that is related to the database. In most environments, you would require a DBA because the level of access and monitoring you need in the database is usually outside of the scope of the systems admin. If you have access to the database and you have a DBA and the systems admin, one person can do it.

Initially, the pricing was competitive but consistently, year over year, its pricing has become more erratic. It increases to the point where even with the positives, it starts to become a longer-term question about how it will fit into the environment.

Be comfortable using the Broadcom community and support. Both these resources will keep you from reinventing the wheel. When planning for more than a small blueprint, plan for scalability and reproducibility across environments. Make sure your framework is reproducible, and you have that consistency, especially across environments. Be comfortable integrating into your larger environment through not just the product directly but through its APIs.

Overall, I would rate Automic Automation an eight out of ten.

The primary use case for Automic is as an IT process automation product. We use it for file transfers across multiple operating systems, like Linux to Windows or vice versa. 

It is also used to automate SAP jobs, Informatica jobs, and database jobs. Additionally, it integrates with various cloud services like AWS, GCP, and Azure, as well as Airflow for data pipeline orchestration.

What I like the most about Automic is its user interface. I have worked with many workload automation products over the past ten years, and Automic's UI is user-friendly and less cluttered. It provides a comprehensive overview of what users need to do. 

Designing workflows is made easier by the graphical user interface, simplifying complex tasks. The preconditions and postconditions are clear and straightforward, making Automic stand out.

There are certain areas in Automic that need improvement, such as the complexity of workflow dependencies. When you have workflows within workflows, it can become complicated. 

The existing options to search for use are available, but a feature that provides a dependency chart or tree diagram would be very helpful. This would alleviate dependency on database queries, which can sometimes be challenging to access.

I have been using Automic for about ten years.

So far, I have not encountered any issues related to instability such as lagging, crashing, or downtime. While there might be occasional bugs, they are addressed promptly by the support team.

Automic makes it easy to manage jobs across multiple platforms. The logical partitioning and multitenancy features allow for the creation of multiple clients to efficiently manage complex workloads.

The technical support for Automic is better now than it was in previous times. The customer service team is responsive and tries to resolve issues, often in collaboration with the development team.

Positive

I have used multiple alternatives, including Autosys, Redwood Chronicle, and Control M.

The initial setup of Automic is straightforward, especially if you use the typical installation route. It configures PostgreSQL automatically and guides you through the necessary steps clearly. Custom installations require some planning and additional steps.

The pricing model for Automic has changed from a host-based licensing model to one based on successful execution. I still prefer the earlier licensing model, but I understand that it was likely changed for business reasons.

I have evaluated other solutions such as Autosys, Redwood Chronicle, and Control M.

I would rate the overall solution as an eight out of ten. Despite some room for improvement, it has been a reliable and valuable tool in managing IT process automations effectively.

The product is used primarily for automating IT processes. Our customer is a big telecom company called COSMOTE. They use Automic for various processes, including Sibel Automation, Oracle applications, billing, data warehousing, and core business workflows. It handles complex workflows with numerous jobs, making it ideal for large-scale operations.

The product is extremely user friendly for both operators and developers. Operators can easily monitor workflows and customize interfaces. Developers find it easy to build workflows in minutes. A standout feature is the comprehensive versioning, allowing easy rollback to previous states. The platform is also very stable, fast, and robust.

There are issues with compatibility when installing agents on legacy operating systems. This presents a problem for users with older systems. Additionally, the lack of support for these systems can complicate deployment. Despite these challenges, the technical support team is knowledgeable and capable.

I have been working with this platform for one year as a vendor, but as a customer for about ten years.

The stability of the solution is excellent. We have had minimal disruptions over the past twelve years, and any issues were related to network problems, not the product itself.

Scalability is one of the strengths of the product. It's straightforward to scale horizontally by adding more application servers or agents. These processes can be done quickly and efficiently.

Customer service and technical support are exceptional. On a scale of one to ten, I would rate them a ten.

Positive

Prior to adopting Automic Workload Automation, we evaluated various vendors. At the time, our team compared several offerings and chose this product based on its capabilities.

The initial setup of Automic on premises was straightforward, taking about an hour with appropriate scripts. While a wizard option was available on Windows, manual configuration was also easy.

Pricing has been reasonable historically, but I am currently unsure of the exact costs under Broadcom's licensing scheme.

During the evaluation phase, we considered numerous solutions from various vendors before deciding on Automic Workload Automation. There was a competing solution called Dollar Universe that we evaluated at the time.

I would certainly recommend Automic Workload Automation to others. It is a robust and user-friendly solution for automation, provided it remains cost-effective. Overall, I would rate the product a ten.

I have been dealing with Automic Automation for probably around ten years. I have been both a partner with Automic, with Broadcom and with Autosys.

Automic Automation is a good tool that offers many advantages.

The greatest advantages of Automic Automation over its competitors include scripting capabilities.

The best features of Automic Automation are that we are able to support many endpoints.

Automic Automation's integration with cloud platforms for enhancing operational efficiency is positive, as it has many supported endpoints for cloud applications out of the box.

Intelligent monitoring with Automic Automation has helped in proactive decision making by providing an AI component.

Automic Automation's detailed logging and reporting has assisted with compliance by supporting major authentication systems and security systems.

Automic Automation has some disadvantages; it is more simplified, and sometimes it can be complicated.

The technical support by Automic, provided by Broadcom, is good with the same blocking support.

I have been working at my current company for thirty years.

Automic Automation does not have any major bugs after upgrading; these are pretty common for most software.

I would rate their technical support as an eight. The only thing I would improve is the upgrade process, which could be simplified.

Positive

My name and company name will not be mentioned. The overall rating for Automic Automation is 8 out of 10.

We use Automic Automation for our enterprise scheduling software. 

It automates a lot of our financial and CIS processes. It is used for file transfer processes and various business processes. Our CIS and financial processes are very deep.

It is not at all difficult to manage complex workloads using Automic Workload Automation. Once it is set up and running, it is usually a matter of monitoring. The individual developer group manages our own clients, and they are usually pretty self-sufficient and have monitors in place that will send them emails or something to keep them alerted of things that are not working. It is pretty seamless and does not require a lot of heavy lifting to keep it going.

It is very well suited for managing processes that span multiple operating platforms. We do that for several of our clients.

I am sure it has freed up staff for other projects or tasks, but I do not work with each individual team, so I do not know those details.

It has improved the compliance processes. The clients that fall in the compliance realm are always checked at least once a year to make sure their processes are not abandoned. If they are abandoned, they are being taken care of. The reporting structure within Automic Automation helps them to get results to support their findings.

We use Automic Workload Automation to automate and orchestrate processes across legacy and modern systems. We have automated CIS financials, PeopleSoft financials, and all kinds of legacy or homegrown application processes.

Automic Automation can be used with cloud and on-premises environments. This was very important when we were migrating from on-premise to the cloud. We have now migrated almost everything in our environment to Azure, but at the time, it was very important that Automic Automation was able to cross between the cloud and on-premise.

The ease of use is valuable. It is very intuitive. Usually, anyone who starts with it is up and running within a few minutes without requiring much assistance afterward. 

There is room for improvement in reporting. There is a lack of reporting capabilities.

I have been using Automic Automation since 2011, so it has been about 13 years.

There is no instability. It has uptime, and any downtime occurs only during maintenance.

It is also very scalable and capable of handling large volumes of data well.

If you put the tickets in for which you need help right away, they get back to you right away. If you tell them you do not need immediate assistance, they will keep in touch with you. If it is a medium severity, there is usually a two to three-day turnaround on answers, and that is what I expect.

Positive

We migrated from TWS to Automic, and it addressed our needs effectively. 

It took us a little bit of time to see its benefits after we deployed it. When we first deployed it, there was a lot of trial and error because we migrated from TWS. There was a lot of tinkering around to get it to work in Automic Automation, but for the most part, it transferred over from TWS pretty well.

I worked on the iSeries before, and we used a couple of different tools there. They were not ones that would run on Windows or Linux systems. They were just on iSeries. Automic does better on the Windows and Unix platforms. They have a connector for the iSeries, but they do not run on the iSeries.

We have it within our environment. It is in the cloud, but it is in our environment. It is not SaaS.

The initial setup was not difficult due to Automic Automation itself, but migrating from TWS had challenges. Putting up an Atomic Automation system would not be as difficult as migrating from another scheduling software package.

It is pretty much a one-person job. I manage the entire system and receive assistance from database administrators when it comes to the database. Other than that, it is all me.

I also do all the maintenance work, which includes doing upgrades and things like that once or twice a year. I try to keep up to date on patches and releases.

It is a comprehensive project. Be prepared to invest time in learning and understanding how an object-based system like this works. 

I would rate Automic Automation a ten out of ten.

The vast majority of our clients basically execute batch and PowerShell commands. We have a few clients that execute stored procedures on databases. However, the primary use is for executing batch and PowerShell tasks.

The solution is usually pretty easy for non-technical people to pick it up as long as they have basic experience with scripting. It has been easier onboarding new clients to Automic Automation versus Dollar Universe since it's relatively easy for anyone to grasp basic workloads or workflows. Compared to Dollar Universe, which had weird terminology and was complicated, Automic is by far easier.

I find that documentation is either very good or borderline useless depending on where you go. There are opportunities where things could be documented a little bit better. Additionally, during the version 21 to version 24 migration, a lot of manual steps were required, which was somewhat inconvenient.

I have been using Automic Automation since 2018.

Broadcom has generally been responsive and supportive. Recently, for non-urgent issues, response times have been slower, however they react quickly when it is urgent. They have been good about getting us back on track when needed.

Positive

The only other solution I ever worked with was Dollar Universe, which was extremely complicated to use, especially when trying to teach non-technical users. Compared to that, Automic Automation is much easier.

For me, the initial setup was straightforward due to previous experience setting up similar systems. However, I do think there could be improvements, such as automating some tasks currently done manually. The initial setup could include more wizard-based steps to reduce configuration file work.

At the time of deployment, we had an entire team involved because we managed two production environments each with their infrastructure. Now, the environment has been consolidated, making management possible with two people.

Pricing is above my pay grade, however, the team lead mentioned that we have a good deal compared to other solutions out there.

I would rate Automic Automation as eight out of ten. I would advise staying current with updates and possibly considering improvements to documentation.

Currently, we support one of the bank's environments, which is highly complex and relies heavily on Automic Automation. This environment is massive, processing billions of batches daily across four environments, each with millions of jobs. We utilize Automic for various tasks, from simple scripting and file transfers to sending data to external parties like Bloomberg and Nets. Given the scale and scope of our operations, we primarily use Automic for most of our business processes.

We struggled with the manual process of loading data into our SQL database. By implementing Automic Automation, we've successfully automated many time-consuming tasks, significantly reducing the potential for human error.

Automic has significantly improved our IT operations by reducing costs and saving time. For example, manually triggering a script at 10 AM required logging into the server and clicking at the exact time, which took at least 15 minutes. Automic automates this, allowing us to schedule scripts without manual intervention. This benefit is magnified when handling thousands of scripts with dependencies, such as script A triggering B, C, D, E, and so on while managing upstream data and multiple file transfers.

Workload automation capabilities are crucial to our operations. While we depend on databases, Windows, and network infrastructure, Automic is a business-critical application supporting our core banking batches. Its importance cannot be overstated; it's essentially the backbone of our bank. As such, any issues with Automic must be prioritized and resolved promptly.

The file transfer feature is the most valuable for process automation, as many organizations rely heavily on data transfer. Consequently, file transfer functionalities are the most frequently utilized within Automic Automation.

Automic Automation struggles with managing external dependencies, limiting its effectiveness. Built as a self-contained system, it relies on internal workflows composed of basic tasks. When external workflows and dependencies are involved, Automic's limitations become apparent. Manual scripting has been necessary to address this, but integrating this functionality directly into Automic would significantly improve its capabilities. For instance, scheduling a job to run after a delay and only if previous batches are complete is currently challenging in Automic. A built-in feature for such dependencies would greatly simplify the process.

We occasionally encounter bugs when applying new agent versions, patches, or updates to Automic. This is problematic because Broadcom, the vendor, should thoroughly test their components before release. Unfortunately, we've experienced instances where bugs have been discovered after deployment, highlighting the need for improved testing practices from Broadcom before making products available to the market.

I have been using Automic Automation for four years.

The new version experienced significant stability issues. While the vendor may share responsibility, our outdated infrastructure, particularly the ten-year-old data, also contributed to the problem. Queries on such old data were time-consuming and impacted tool performance. We identified and addressed our infrastructure shortcomings with the vendor's assistance. Although there were initial challenges, the system is now stable. We continue to work closely with the vendor to maintain optimal performance.

Automic Automation is highly scalable, with thousands of agents deployed as part of our baseline build. Consequently, every server in our large environment hosts a UC4 agent.

We can connect with technical support by submitting a ticket through the portal, and support is prioritized based on the impact on our business. However, in many cases, we have found that the vendor does not provide a thorough root cause analysis. Instead, we often receive generic recommendations to upgrade our systems or infrastructure.

Neutral

I previously used IBM Workload Automation. Both IBM Workload Automation and Automic Automation have their advantages and disadvantages. IBM Workload Automation was capable of handling all external dependency requirements. We have integrated similar capabilities using other methods, but not within Automic. While Automic might be more expensive, the cost depends on the chosen purchase and licensing model, including options like premium support.

I was involved in upgrading Automic Automation from version 12 to 21. This complex process is highly dependent on the environment and requires extensive planning. Before the upgrade, we must reboot all potentially impacted systems, release specific certificates, and upgrade the agent to ensure compatibility with the latest version. Automic release notes, accessible in their documentation, provide crucial information about potential issues and compatibility requirements. While these compatibility metrics should be carefully reviewed, the complexity of the process varies significantly based on the specific environment, ranging from simple to highly intricate.

Four people were involved in the upgrade process, which took 18 hours due to the necessary migration of our large database.

Automic Automation is costly.

I would rate Automic Automation eight out of ten.

We have a team of 31 people who work with Automic Automation.

Our expert team makes maintenance of Automic Automation easy.

I recommend Automic Automation as a powerful tool with solid functionality. It offers numerous options for completing various tasks in multiple ways.

Everything hinges on a solid foundation. Therefore, a dedicated server for Automic Automation is crucial. Sharing a machine with other applications can introduce latency issues. To avoid this, establish a separate machine with its own VLAN and database exclusively for Automic. A dedicated environment ensures optimal performance. However, installing Automic on shared infrastructure is likely to cause problems.

Negative