Automic Automation Reviews

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.

On-premises

We use Automic to schedule and automate our financial jobs. It is primarily used for our financial processes, such as closing the books at the end of the quarter or year. When closing the books, we need to load the data from one system to the other. The jobs involved in loading the data are automated through Automic. We have more than a thousand critical jobs automated through Automic that vary in complexity from simple to highly complicated. 

Some benefits of Automic were immediate. For example, we instantly increased productivity in managing our data workload. It became effortless. While those benefits were immediate, others were long-term benefits. 

It enabled us to build more complex workflows and manage all the data loads end to end in Automic, which was not possible before we implemented it. Those kinds of benefits took a bit more time. We began to realize those benefits in around a year because it took time to understand the tool, its features, and what was possible with it.

We can use Automic to manage workloads across multiple operating systems. Our systems are hosted on Windows, Linux, and the cloud. Automic's good log-capturing methodologies help us reduce workload failure rates. Those logs help us do a detailed root cause analysis, preventing those failures in the future. Some of our systems are on AWS, and some are on Azure. Our Automic installation is on Azure, so we operate across multiple cloud environments.

Automic Automation helps free up the bandwidth of our contractors and employees to focus on more important things. Our systems are financial, so they have to abide by SOC compliance, and Automic's controls and logging enable us to maintain SOC compliance. 

We have achieved productivity benefits and avoided costs. We could repurpose some of our costs in other areas that we would not have prioritized otherwise. 

Our financial processes have stringent requirements, especially during the quarter close and one-time close periods. Any deviation from our SLAs gets escalated, so we must be on top of all our workloads running through Automic. Real-time monitoring is helpful because as soon as the issue occurs, it sends an alert, and we don't waste time not knowing what the issue is. We know what the issue is and take action on it. We can reduce any impact due to the issue.

I like the connectors Automic has provided or the agents that give me the flexibility to connect to various source and target systems. It's pretty easy to manage complex workloads using Automic. Its user interface makes it easier for us to manage.

We can monitor job progress in real time, and the IT teams' visibility into the progress is excellent. In the event of any issues, the error messages that Automic sends help us to debug the problem.

From a features perspective, we still need some agents to connect to specific systems that Automic doesn't have. Expanding their available agents would make the tool more compatible with various systems that other customers may have.

I have used Automic for about eight years.

We've never had a crash or any stability issues. There have been some infrastructure-related issues that caused the server to go down, but Automic has been stable.

I rate Automic nine out of 10 for stability. We have not encountered any use case that we could not automate with Automic. From that perspective, the scalability is good for us. It has been able to meet all our needs. 

I rate Automic support nine out of 10. They are responsive and bring a lot of expertise to the table. We have been assigned an account executive, who provides fantastic support.

Positive

Deploying Automic was somewhere in the middle. It wasn't too complicated, but it wasn't a cakewalk. We are on the cloud. We started on-prem, but then as a company strategy, we moved all our applications to the cloud. Automic is also on the cloud. 

When we started implementing Atomic, we set a scope to implement Automic over many years, and that scope has gradually increased. In the beginning, it was a four-month project that included all our financial jobs and a solid chunk of jobs that we were trying to accommodate in our topic. After deployment, it's fairly easy to maintain Automic. You just need to do regular patching and updates.

We generally work with IT vendor partners and service companies. The Automic team also collaborated closely with us to ensure they provided their product expertise during our migration to our scheduling tool. Four from my company were on the deployment team. 

Before I joined this company, Automic had a contract with its parent company, and their pricing was very competitive. However, when we split into multiple businesses, the contract increased significantly, becoming an expensive tool. 

Make sure you understand your licensing requirements and the model that Automic offers. You have to count the nodes and the agents. As a product owner, you should know what your licensing requirement will be based on how Automic does the licensing counts. 

I rate Automic Automation nine out of 10. Before deploying Automic, you should ensure your team has developed some technical expertise so that the systems or scope that you identify for Automic automations are feasible with the tools. You should also ensure that the agents are available and that they work with the types of systems you're trying to connect.  

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.

Private Cloud

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.

On-premises

I am a systems administrator and primarily responsible for maintaining the physical servers, databases, upgrades, managing vulnerabilities, and granting permissions to our customers who use it. Although I do not use the software personally, it serves housekeeping purposes.

Automic Automation allows us to serve the service without interruptions. It supports high availability by operating multiple servers concurrently, which means users do not experience outages or the need to log in again, even if some servers are updated. This seamless operation is crucial for us as administrators.

The support and knowledge of incident management could be enhanced. There have been unresolved issues persisting for years, affecting customer satisfaction. Improvement is needed in both the response time and the depth of problem resolution provided by support.

I have been working with the solution for two years now.

It's easy because it was installed several years ago, and we only conduct upgrades now. The upgrade process is straightforward with internal scripts to update data in specific folders. The main challenge is performing the upgrades multiple times across test, development, QA, and production environments.

The stability is high, rated as nine. There is minimal downtime, and overall, it functions reliably.

I hold scalability in high regard, giving it a perfect score of ten. The solution effectively supports our existing user base and is equipped to scale further.

The quality of customer service is lacking. Previously, support was more proactive and involved live sessions to resolve issues. Recently, support tends to delay resolving problems, asking repetitive questions without providing solutions.

Negative

I have worked with Control-M from BMC Software previously. While I prefer Control-M's visual interface, Automic Automation offers its own unique set of job scheduling elements. Over time, I have acclimated to Automic Automation’s approach and can manage and troubleshoot within its environment.

The initial setup was done years before I joined, and I do not have information about it.

As a rough estimate, Automic Automation has helped reduce workload failure rates by fifty percent. However, the reduction largely depends on the business unit in question.

Overall, I would rate Automic Automation as an eight. I would recommend it because it is stable, scalable, and supported by one of the major companies in IT services. However, having two schedulers can be beneficial to ensure license negotiations are feasible. I rate the overall solution as an eight.

On-premises

We use it for scheduling cloud jobs and on-premises jobs.

The scheduling feature is very user-friendly.

They could improve by providing more control features for schedules. For example, we can hold a job, and then it could stop the job in the actual end application. They could improve such capabilities.

Automic Automation was probably implemented back in 2017.

Sometimes, I see performance issues when there are a lot of jobs running. Otherwise, it is pretty good. It is very stable compared to others. We rarely see issues.

Scalability is good. We started using it more often, so scalability is good.

Customer service is good. They are pretty quick. A couple of times I faced issues, but maybe the other person who was working was not there. Most of the time, they are good and on time.

Positive

Other teams used Appworx which was an old product. Appworx was bought by Broadcom. Because we have been using other products by Broadcom, we bought this.

I am only exposed to Automic Automation. I have not used other products.

I was not involved in the initial setup. I took over sometime in 2021. I did one upgrade with their support and development team's help, and it was smooth when they were there. I managed it myself for production because they provided the steps and did a recording, so I was able to understand the process.

It does not require much maintenance from our end. We renew the maintenance contract every year, but we have not used that much. The product is efficient.

The pricing was client-wise, but they are changing it to execution-wise pricing. So, we are in negotiation.

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

It is an automation tool. We build the workflows and Linux and Windows servers with it, particularly for running client jobs and databases. We use it with a lot of big data ecosystem tools, such as Hadoop or HDFS.

We have automated regular ETL processes such as data transformation. They are loading data into databases and the HDFS file system.

We use it for data transfer jobs between servers. It is being used for SFTP-type jobs, and we run a lot of Python-based things with Automic.

It deals with business-critical processes. It is an important tool for us. For a lot of backend work, we use Automic Automation to run all kinds of jobs. We have some very complex jobs, but we also use it for some basic jobs. It is being used for very critical or high-priority jobs and complicated workflows with hundreds of jobs.

It has been easy for us to manage complex workloads using Automic Automation. The user interface allows us to zoom into a particular section of a complicated workflow. If we have 30 different jobs and scripts tied together in a workflow, we can use the graphical interface to work on one section of the job on our screen. We can also embed one workflow into another. If there is a complicated workflow, we can bunch it all into one workflow and embed that one into a different workflow. This way, we can manage more complicated workflows.

It is easy to use. We previously had a thick client which was Java-based, and now, we have the web-based one. Both have been easy to use. Building jobs and doing the admin side of things, such as monitoring jobs, checking reports of the jobs, and checking job statistics has been easy. It is one of the easy-to-use tools.

We could see its benefits immediately after deploying it. We were replacing a legacy tool with Automic. It was a new solution, and we could see all the new features in it.

We have a lot of alerting features and notification features. It even has a feature to notify us when a job takes longer than usual. If our workflow usually takes two hours to run, but it is taking longer, Automic Automation can notify us. It helps to reduce the error or failure rates.

Automic Automation has freed up staff to do other things more. By automating routine things with Automic, they can move on to doing other things. It surely frees up people's time. It is saving time for our staff.

Automic Automation helped reduce our operational costs. We used to get called often with our old tool because of more failure rates, agents going down, etc. In that sense, it is saving time for staff. If more tickets are generated, we would have to hire more people offshore. With fewer tickers and fewer job failures, we need fewer people.

Automic Automation has helped improve our ability to meet SLAs by being more reliable and more stable. It is a stable tool. Our jobs are not failing because technology is failing or agents are going down or not responding.

Since we bought it, we have not had any big issues. We are satisfied with it. We are able to run multiple jobs. We can build and run complicated jobs. There are no issues. The user interface and other things are easy to use, and people are generally happy with the tool.

We use Automic for both legacy and modern systems. We have automated Linux workflows, shell scripts, database jobs, and big data jobs such as HDFS jobs and Spark jobs.

Integration with the cloud is an area for improvement. They have to make it somehow fit or usable for cloud use cases. Right now, it works great for our on-prem data center, but they have to come up with a very good reason why people should be using it in the cloud. 

We got the tool in 2015, so it has been nine years.

It is stable. We have not had any issues related to stability.

It is scalable. We only have a two-server cluster. We never had a need for more than that. We have the licenses to add more servers in case we need more throughput from Automic.

I have interacted with them a lot of times. They can be better, but overall, they are okay. If we have a severe or high-priority issue where we need help immediately, we get very experienced engineers, but if it is a routine issue, there are a lot of emails back and forth. So, for low-priority issues, there can be some improvement.

Neutral

We used to use a tool called Redwood Cronacle previously. We got separated from our parent company, and our managers had more autonomy to select the tech stack and switch to a different technology.

So, we had an old tool before, and we wanted to replace it. Back in 2015 or 2016, when Atomic was selected as a vendor, we were looking at all the features, the integrations with HDFS, and the agent architecture they have. We were also looking for the stability of the tool. With the previous tool, we had a lot of stability issues, such as agents going off, so we were looking for a more stable tool. We also wanted to have a more modern tool.

Given the number of jobs we had, it took us a long time to move to it, but we expected that. We were able to do it within the allotted time. In that sense, we did not have any unforeseen issues when we moved to Automic Automation.

Given that we had hundreds or thousands of jobs, it took us about six months to complete the move. We totally deprecated our old tool and moved 100% of our jobs to Automic Automation.

It does not require anything big in terms of maintenance. It just requires upgrades. Other than that, there is nothing. The platform is stable.

They have increased the license price a little bit. It is more than what we expected about two years ago. So, there could be some surprises when it comes to pricing.

It is an easy-to-use tool. You do not have to spend too much time learning the interface and other things. It is a stable tool. It is reliable.

We have not used the predictive modeling provided by the AAI capability. We tried it for a while, but we did not have any advanced use cases where we had to dig deep into the system. We have some basic reports, and people seem to be happy with that.

We predominantly use it for on-prem jobs. We never tested it on the cloud. It seems complicated. It needs a lot of setup such as opening the network and the network's firewalls and other things. It seems difficult. We may also need a different type of licensing to run from the agents in the cloud, so we did not try it. In the future, we may use Automic Automation with the cloud.

I would rate Automic Automation a nine out of ten.

We have many different use cases. One use case is to back up all our servers. This is a big usage. The next one is to schedule things on SAP systems. We have SAP reports. We have processes where different SAP systems are involved and we can build up dependencies. We create business process flows. This is a big use case.

We use Automic Automation for managing databases, such as SQL databases, Oracle databases, and SAP databases. We have customers who use UC4 for general monitoring, system jobs, and other things. These are the main use cases.

We have some business-critical processes. For example, if a file is there, then the file has to be loaded to SAP. The customers can then, for example, print the papers to transport the goods. If our UC4 process does not happen, the papers cannot be printed and the goods cannot be shipped to a customer.

Some departments use it to handle the databases. If the process is stuck, then perhaps for Oracle databases, the archive files will not be moved to another folder, and the folder will grow and grow. There would be no space on the file system, and the application that is using the database cannot work anymore. We have some very critical processes and also many processes that are not so critical.

The biggest benefit is that we have one point of view on the processes. We can build dependencies, and we can have access to different platforms. We can integrate different platforms. This is the biggest benefit of Automic Automation.

Our systems are very big. At times, we have more than 11 million jobs per day or executions per day, and we have struggled with this amount in the past, but Broadcom has improved the application so that we can avoid such struggles. We have a big environment. When new functionality is implemented in the system, very often, we are the first ones to struggle with something, and then Broadcom has to improve it. Normally, it is a very stable product for us.

We have some very big workflows, which include more than a thousand objects, so it can be very hard for us to have a good overview of it all. That is why we build our processes in small steps. This way, it is much easier to handle them as one very big workflow. This is our experience, and we try to go in this direction.

We have the agent, or we can use the REST API. It is easy to implement in the end. The big challenge is that if you have many components in your systems, you have to update the components from time to time, and this, of course, is a big effort.

Automic Automation has saved time and helped free up staff for other projects or tasks. We automate many things with Automic Automation. If we had to do these things every day manually, we would lose a lot of time. It helps us save time for other projects.

Automic Automation has helped us reduce our operational costs. I am from the admin team, and we have to roll out the new version of our agent. We have more than 30,000 agents in our system. To update each agent manually, we would have to log onto the server, move the binaries to the target system, stop the agent, and start the agent. It would take a very long time to do this manually for 30,000 agents. With Automic Automation, we have the possibility to just say that we want to update this agent. The binaries will be moved to the platform, and the agent will be stopped and started automatically. We do not have to log in to the servers. It will be done in the background. Therefore, it is a big help for us in saving time.

It has so many possibilities, and many functions are important for us. We use it very often, so it is difficult to say which is the best one. In general, the complete functionality that Broadcom offers is very good. It is very flexible in terms of using the functionalities and build processes. The biggest benefit perhaps is that we have so many possibilities in UC4 or Automic Automation to reach the target. We can more or less build each requirement from our customers.

The visibility and control that Automic Automation provides are good, but it could be improved. In case we run into performance issues, it is sometimes hard to find out what is the real cause for it.

At the moment, the REST interface does not include everything. It was improved a little bit, but some functionality is still open. This is something that can be improved. There is nothing critical that is missing for that we cannot use Automic Automation.

I have been using this solution for more than 25 years.

I would rate it an eight out of ten for stability.

It is easy to scale, but the database should support that scalability. We can scale processes, and it is easy, but in the end, the database must be able to handle that. We sometimes struggle a little bit there. 

In our experience, when we want to scale, we do, but we then see some negative side effects, and we have to go down again. We have to contact the support. In most cases, we need a patch.

Some errors are checked directly if you create an object, and for some errors, it is always best if Broadcom checks whether it fits or not, but, of course, not all of them can be done in this way. If we run into an error that we cannot solve immediately at our end, we have the possibility to create a support ticket. We have the possibility to specify the priority one, two, three, or four. If it is priority one, we normally get very fast support on the phone, and they help. If it is a normal error, a ticket is created, but it takes time to get a solution, which is okay.

I have good experience with technical support. We also have a TSE partner. If we have some problems, we can contact this colleague directly. That makes life very easy.

Positive

In the mainframe environment, we had our own solution, but it was a long time ago. It is not comparable with Automic Automation.

We are not using cloud environments at the moment. We work only with on-premises environments. We have databases. At the moment, we are focusing on on-prem because most of the automations are still on-prem. I guess it will change in the future, but I do not see the change to the cloud environment happening in the next two years.

I have not practiced the deployment process, but I know that we could support some of our customers. They really benefited because of this.

In terms of maintenance, maintaining the processes is easy, but before we roll out a new version, we have to test all the things. This is a big effort for us every time. We struggle every time a new functionality is implemented because in most cases, the product is tested in a smaller environment, and it works. However, we usually reach the limit and then we have to adapt the product. We have to get in touch with Broadcom for that. Before we can roll out a new version, we have to test it properly. This is a big challenge on our end. If you are a customer with a small environment, it is easier to install the application because you have not adapted many things. You can more or less use it as you installed it, but in a bigger environment, you have many adaptations.

We have our TSE as the contact person.

We do an evaluation from time to time. We check out the market from time to time to see if there is perhaps a better product, but at the moment, we are concentrating on this solution.

I could recommend Automic Automation, but it is a bit challenging if you want to implement it in a very big environment. If it is a small environment, it can easily handle that.

I would rate Automic Automation a nine out of ten.