Control-M Reviews

We use Control-M to provide business services to our customers. The use cases involve Hadoop, a lot of file transfers, and SQL scripts. In our business, automation is used for many things and we use a lot of the Control-M modules. For example, we connect to SAP, with databases, Hadoop, MFT, Informatica, and other technologies.

What we do relates to many different business services in a retail environment.

We have hybrid deployment; over the past two years, we have had a mix of on-premises and cloud-based implementations. Ultimately, we are moving to the cloud. We are using AWS, GCP, and Azure.

The main benefit is that Control-M can work with almost all of the applications that are on the market right now. We work with technologies including Hadoop, Informatica, all kinds of databases, and file transfer with MFT tools. The real potential with Control-M is that it can be used for everything you want.

It is really important that our clients can manage their own application workflow with full autonomy. Our customers are using this capability a lot and it helps because we don't need to be present when they want to perform a simple task. It's better for them because they don't need to wait to ask or to have something changed. They can just do it themselves. Also, it's better for us because we have more time to do other things.

The expanded capabilities in version 2020 for planning and monitoring have had a positive effect on our clients' operations, as well as our own. It saves a lot of time when it comes to developing and implementing things. As a result of saving time, both us and our clients are saving money.

Control-M has definitely helped us to achieve faster issue resolution, although it is difficult for me to estimate how much by. We don't have metrics that are suitable for tracking this kind of thing.

The best part about this product is that it has a lot of features. Control-M doesn't limit us and we can use it for a lot of things.

Control-M is easy to install, use, and maintain. It is easier to work with than other products.

The web interface hosts a lot of videos and webinars and I really appreciate this because I find them very helpful. They have tutorials that explain how to approach the new technologies and explain how things can be done using Control-M. This is something that I use a lot.

The Application Integrator is helpful because not all applications have a module available in Control-M, and we can use this feature to create them.

When it comes to supporting cloud services, Control-M is a bit slow. We are not advancing with the technology because we don't have the modules that can interact or use the new application services provided by the cloud technologies. BMC has been telling me that they are working hard to be more aligned with these new technologies, but they are a bit slow. Consequently, we are having a few issues when it comes to implementing Control-M. Some services that are being offered, such as Databricks, have been a problem.

The documentation is something that needs to be improved. Years ago, the documentation was very good, and I don't understand why but the documentation is no longer as good as it should be. For example, if I need to install or upgrade Control-M Enterprise Manager or Control-M server, the only information that I have in the documentation are things like "Execute this and follow the instructions on the screen".  What it doesn't tell you is what will be needed for the process. For example, you may need to enter a password or select a source, but you won't know what these parameters are in advance.

Also, it is different to find what you are looking for in terms of documentation. For instance, if you visit the Control-M download page, you see several tabs. There is a tab where you can download software and another tab where you can download patches. This is perfect. However, there is another tab for the documentation but there is never anything there.

With any Control-M product, it is hard to find the documentation. The reason for this is that they are moving all of the documentation online, in an HTML format. The problem is that it is hard to download documentation in this format. In particular, if it is a specific part that you need or a certain module, then it would be much easier to have a PDF version like they used to have. Consequently, it is more difficult for us to pass the documentation to our internal teams.

For example, if we are trying to configure a module for Informatica or SAP, it's hard because we don't have PDF documentation. We need to go online but it is difficult because it is very hard to find what you are looking for.

Another area of improvement for Control-M is the version release lifecycle. Prior to 2018, we had the same, main version of Control-M for two or three years. Since 2018, they have been releasing a new version every year. There was a 2018, 2019, and 2020 version. It seems that these new versions are being released in an unfinished state because we are seeing a lot of bugs. Historically, it has been very stable, but from a point between two and three years ago, it has not been so much so. It seems that the problem is that the versions are changing too quickly.

I have been using Control-M for nine years.

There are some limits to scalability in terms of cloud integration. There is some integration with cloud services but it is very simple. It is called the Application Integrator Module. This is a very good feature but the problem is that if we have to interact with cloud services, we need to create all of these modules on our own. We are paying a lot of money for a product where we have to create our own modules, which is not perfect.

It is very good that we have the Application Integrator available but for services that are being used by a lot of companies, we need official support from BMC.

I would rate the technical support an eight out of ten.

We have been dealing with BMC for several years and when you consider the support from a few years ago, the response that we received was more technical and more accurate regarding the problem that we were having.

As it is now, more and more we are seeing that the customer support has to rely on the product development team to resolve the issue. This is because there are a lot of bugs in the product and customer support cannot provide a solution for these. Instead, the problem has to be fixed by development, and then a patch is released to solve the problem.

For this reason, I am rating the support an eight instead of ten.

We have had cases where our clients migrated to Control-M from a competing solution. In fact, we did a migration last year from TWS, the Tivoli Workload Scheduler from IBM, to Control-M using the conversion tool. The tool was very important because it reduced a lot of work.

The problem is that the conversion was not as good as it should be. I estimate that we had to modify 90% of the jobs because the conversion was not good enough. It was still important because it would have taken a lot longer to create all of the jobs from scratch. That said, it was not perfect, at least that was our experience with migrating from TWS.

We were using TWS and another one that is called Visual TOM. It is another product that is similar to Control-M. These are both scheduling products, but Control-M has tons of features that the other ones don't have. They don't have the modules, the plug-ins, or the Automation API. They are stable and they are good, but we can't use them like you use Control-M because Control-M permits us to perform many more things. Unfortunately, with the many more things that you can do, it does introduce more opportunities for failure. However, this is true of any feature-rich solution. The more complex it is, the more prone to error it is.

Control-M is easy to install and maintain. There are not a lot of steps required to upgrade or downgrade from one version to another. With other products that I've been using, it is difficult and complicated to upgrade because there are a lot of confusing steps. But with control-M, you need only follow the onscreen instructions.

The length of time required to deploy depends on the customer. The scope and complexity of the client's requirements dictate the amount of time it will take to complete. For example, we can deploy for a smaller customer in one week. However, for a large retail customer, it could take a month to complete.

We have one client right now, where we are upgrading from Control-M 2018 to 2019, and it is going to take us almost three months to complete. Part of the reason it takes this long is that when you try to upgrade a production environment, it's really difficult to get a window to perform the upgrade or the installation or the modification. That said, it's still easier than many other products.

Pricing varies depending on which components and modules you are using.

My advice for anybody who is considering Control-M is that I recommend it. Although it's not perfect, it is relatively easy to use and maintain.

I would rate this solution an eight out of ten.

We use this solution for automating workloads across traditional data centers, the cloud, SaaS offerings, and various other Enterprise software packages.

It is allowing developers and product owners to create complex workflows that may encompass several different products or technologies and have it all visible, monitored, and managed from one place.

The Single pane of glass view has helped us to see the big picture.

The auditing and archiving capabilities have helped us maintain compliance and provide for a single place to look for errors, check historical runs, etc.

We have increased efficiency by reducing the number of people needed to watch and react to processing.

The simplified integrations and scheduling across various products was a big win to reduce silos.

The Automation API has opened up a world of possibilities for us, including the ability to create workflows on-demand using traditional DevOps tools.

The most valuable feature is the Automation API - Jobs as Code. This is the future of workload automation. It brings Control-M into the DevOps sphere, and they are focusing a lot of effort with monthly releases of this product.

The Web interface is coming along but still has some missing pieces. Today, you must still rely on the full GUI client to do everything you need. The next major release needs to focus on the lightweight web client.

I'd also like to see more out of the box support for Docker, etc.

We have been using this solution for more than sixteen years.

This solution is highly stable with a good customer support team.

This solution is highly scalable.  We can run one job or a million jobs, with ease. We've never had an issue.

Technical support for this solution is top-notch. Many of the folks that I email have been there for years! That says a lot.

Prior to using this product, we used homemade solutions and we outgrew them.

The initial setup of this solution is straightforward, but for new users, I would recommend engaging a third party to help you set up and learn the ropes.

We used a vendor team to assist with the deployment.

Over the years we've saved countless man YEARS. We have also avoided having to buy additional products for scheduling and integration. The list really does go on and on.

Pricing can be steep, but you get what you pay for. If you are just concerned about cost, you are going to miss the big picture because Control-M has features that are light years ahead of the competition. Don't save a nickel to spend $20.

Before choosing this product we looked at Computer Associates (CA Technologies) and Tivoli.

Control-M is light years ahead of any competitor we have looked at.

You can try it without buying it. I would suggest checking out the workbench at: https://jobsascode.io

This is a free version of the Control-M package that is perfect to take for a spin.

We use this solution for enterprise workload automation in the financial industry. We schedule and monitor hundreds of business-critical processes.

We also leverage the Managed File Transfer capabilities of Control-M to handle our file transfers securely & efficiently. Most of our tasks also deal with databases, and Control-M's purpose-built module for the databases comes in very handy when handling database components. It adds value with its capability to execute tasks natively and bring more information to the output.

The BIM feature is used to monitor the important set of jobs as a service and to proactively alert operations when it sees that some jobs in the critical path are failed or delayed. This helps a lot in maintaining our SLAs efficiently.

Control-M, with its huge integration capabilities, brought most of our scheduling activities under one roof. This adds to ease of use and support. To top that, the visibility it adds to the otherwise hidden information is very useful. In fact, invaluable.

Although we do not use tens of additional plugins available, we can see how they can be valuable to other companies.

BMC has now started concentrating more on APIs, which is a welcome move. This enables us to develop 'job as code'. This supports our efforts to adapt to a Continuous Integration/Continuous Delivery model. We hope that they make it one hundred percent compatible as early as possible.

Integration capabilities, plugins, support communities, visibility, MFT, Reports, APIs. As mentioned earlier, all these features mean that we don't need to use multiple solutions to do the task. It also makes things a lot easier that way.

MFT changed the way we manage our file transfers. On top of that, all of it is directly visible in the same GUI. All the statistics can be viewed at the click of a button. Although a bit flaky sometimes, it is very helpful.

Experts in the communities need a special mention here. There's a huge number of people who spend their valuable time helping each other, solving others problems. Although the actual BMC support can be slow in response sometimes, the expertise & the helpful nature of people in the BMC Community for Control-M more than make up for it.

MFT needs some more polishing. We ran into problems a few times & struggled to get them sorted in time. But, BMC gave their full support to us at such times.

APIs are not there one hundred percent yet, but BMC just adopted a monthly release mechanism for APIs. I can see that they are on it full time.

Inbuilt integration with Connect Direct could be helpful. A developer sandbox could be very helpful to try out new features or experience them.

Application Integrator can be helpful, although I don't see many templates being built by BMC experts. The hub that is available is mostly user-dependent.

It's stable ninety-nine percent of the time. Even the other one percent could be because of the funky underlying infrastructure/network setup.

Our job footprint is very low, so we never faced any scalability issues. From the documentation, it is my understanding that virtually, there is no limit to its scalability.

It can be slow at times, but you eventually come to an understanding that as long as you provide all of the information they 'might' need as early as possible, there are better chances that you get your answers 'sooner'.

I had used Cron scheduler for a short time, but it can be considered almost zero experience. My understanding is that BMC Control-M is years ahead in terms of usability & visibility.

The initial setup of this solution is very straight forward. BMCs AMIGO program is there to walk you through the process.

It gets a bit technical when you need to setup MFTs, but at the same time, it's not rocket science either.

We performed the deployment in-house with help from BMCs AMIGO program.

Pricing is a tricky area that I don't have much experience in. I can see it getting even trickier with more companies moving to a cloud-based infrastructure.

We did not evaluate other options before choosing this solution.

I like this solution, and my advice is to go for it :)

We do scheduling of tasks and jobs in Control-M.

The company has had the product for over 25 years.

The opportunity to automate work so you have an audit trail, especially with governmental requirements in a regulated industry, such as the airline industry. It's really important that we have that audit trail.

Because it's a tool which allows us to do scheduled work, it allows for notifications when jobs aren't running within that scheduled time frame. This improves the opportunity to meet SLAs.

We have all sorts of things which run through it, both on distributed and mainframe platforms. They all seem to run quite successfully. We're looking to add some additional work off of distributed platforms that will run with Oracle types of processing. But, we have a lot of work to come to the tool that we're not using it for yet.

It creates an audit trail for jobs that we run off of it.

With opportunity to run things through a repository, such as a scheduler, you have a better opportunity to ensure the information is where it needs to be when it needs to be there.

The company has been working with BMC on the MFT. There are still some things about MFT which don't work the way that we want with our needs. So, we would like to see that improved.

While the solution has affected the collaboration between our development and operations within our company, there is a need and opportunity to further that relationship with the use of this tool, so the enterprise uses it on all platforms. We will get there, but we are just not there yet.

For our shop, the tool is 99.9 percent reliable. We have very few instances of disruption with the tool.

We don't have any complaints about the usability. We like what it does. There are no issues with usability of the tool.

As we increase the number of tasks or jobs on the system, there are concerns about cost.

We previously used CA products.

We have seen ROI. Our in-house developed tool has been able to use the Control-M platform, making it easier for us to manage and monitor our file delivery processes.

Control-M saves us time.

Because we have been so pleased with this product, I would encourage others to look into this product with a view on what are their needs. Ask the right questions of either their sales rep or technical person from BMC to understand how this tool would work successfully for them, because it's been so successful for us.

Because we've had it for so long, and it's been such a stable product, some of our folks on the distributed side of things need to learn how to use Control-M effectively in regards to output when tasks or jobs fail. They need to give us smarter outputs, so we can resolve things more quickly.

Promotions between environments, as well as local, mass update, versioning, and self-service.

It is much easier to move and copy schedules. Versioning allows for quick restoration when an error is found.

It can definitely expand promotions, so that a single job can be moved. Currently you can only promote a job by promoting the entire table. In our environment we have very similar jobs in a flow but some are different so if i want to move just one of those jobs to all the other Control-M servers i would not be able to because it would overlay the entire folder. I want to be able to copy/move just a single job to prevent the overlay.

I have been using Control-M for 18 years.

I have not had any issues with deployment in any of the versions.

I can honestly say, I only had a stability issue once. Other than that one time, Control-M has been a very stable application.

No scalability issues at all. When we grew, we upgraded the server and it was back to business as usual.

I would give customer service a rating of 8/10.

I would give technical support a rating of 8/10.

We used another solution. Our company was looking to standardize across the enterprise.

The setup was straightforward.

We had a single contractor and our in-house team. She was very knowledgeable of the product.

We have used Control-M mostly as a file transfer and in conjunction with Hadoop.

We have many feeds coming in from different companies which are used by the business for various reasons and we must collectively have a central point to gather the files and feeds. We also use Control-M for encryption, decryption, and sending data across to different business users that begin at a point of time and making sure that we are not missing unnecessarily. It's a real help what we are getting. The example for us is we have a lot of business which depends on feeds which, if not properly processed, affect the stock exchange. So Control-M acts as a mediator in between that and provides it in a very efficient way. This has reduced a lot of manual intervention required as a business.

The feature we use most in Control-M is related to the file transfer module. It is quite advanced compared to other tools like Automate, etc. The new version which has come of same MFT has a lot of advanced features which makes it very easy to work with. There is less need for written programs and more GUI-based stuff.

One feature I would like to include is in the middle of the monitoring domain. In the monitoring domain, if I have to update a number of jobs, the only way to do it is by manually clicking on each job. I would like a feature that allows me to do a mass update in the jobs, which I feel is still lacking.

This version has done an amazing change, compared to version 7 and the versions after that. I'm not sure what they should change at this stage. One recent feature they have come up with is if we can upgrade Control-M agents from a central location. I would still prefer a solution where I can do an installation of the controller module from a remote distance. That's something they don't have. I know why it has still not come up, but it could be a great feature if we could include that somehow. To push out these sort of installation setup files onto another machine and get it in installed. It is not there for now, though.

I would rate this solution as eight out of ten. The reason for this rating is because of the scope of implementation. It will have an ultimately upper hand to the other tools in the market. They can show what most other controls don't have. Nevertheless, these features would really help as well. I would like to see more of them.

It is a very stable solution and BMC, the parent company, really comes up with tech packs and upgrades, which add new features and also resolve issues. Also, their knowledge base is quite full, which helps a lot to find the solution easily from the website.

I rate them nine out of ten for scalability.

On average, the control team consists of around fifteen people. This ranges from the elements of both which is the monitoring team and the L2 support which is for the scheduling team. Then there is also L3, who is the administrator. Apart from that, we have certain business users that will use the help service module often.

If we are looking at a 24 path sell and support, we would need close to seven members on a daily basis. That's the same for L1, L2, and L3 teams to each do daily support. L1 would be for monitoring, L2 for scheduling, and L3 is administrative.

We do have certain programs to increase usage down the line, which we're considering. I would say close to 60 to 65 percent of the company is using Control-M right now.

The technical support is great and I would give it a ten.

My main experience is with this as the central unit, but I have used other tools. The main reason I chose Control-M was firstly that it is user-friendly. Secondly, the market is wide open for Control-M, and a lot of other organizations use it. So it gives Control-M the upper hand in the market to work on something like this.

It was quite simple since Control-M has a very user-friendly GUI. That made it fairly easy to relate with the business and convert it into something which looks familiar.

We kind of started from scratch, so I think it took two to three months for us to set everything up at the initial stage. The strategy was to tackle one business at a time so that we don't complicate stuff because not everything is automated. We started to target one business/application at a time and converted them each into something which Control-M can work with.

We did the deployment on our own based on our experience. We had previously deployed it for certain clients basically so we were primarily the consultant for that.

I may not be able to convert it into a value in this way, but it does more in terms of reducing manual intervention. This, in turn, means less human resources are being used. For instance, if there are three people in a team and controlling certain work, they could probably put more on one resource. So that reduces the cost of resources in the whole organization.

We have account based licensing. There are two or three types of licensing. One of them is based on the number of jobs, so we a license close to 4,000 jobs per day.

The cost is based on the different modules, which we buy from them. If we a buy a hardware module, which we are presently using and integrating, that is an additional cost, but I'm not sure of the amount. Each module comes with a different cost.

I have experience with alternates like IBM Tivoli and another software called JAMS. These are the ones that I have worked on and the features and user-friendliness of both of them is fine. It's such a different level compared to this, so that's the reason I'm sticking to Control-M.

For those who want to implement, there are a few cons. Cost-wise it is not very simple for every business to implement it. So they should really plan if they are going to use it extensively. If not, they should think twice about it. 

If they are thinking of implementing, though, they should analyze the business and check which controller modules will really help them enhance their work and ultimately transform their work into an automated solution, which in turn will reduce their cost. 

I would really suggest someone who is planning to use Control-M or wants to deploy is first to check which modules are really required and also what kind of licensing makes sense for their business. If its a very large enterprise then it would be great to use a premium based license. If not, it's better to use a job count based license. So that is a point which they should check before implementing.

Product is intuitive, you can start working with it and figure out the basics pretty quickly. The built in modules (examples: File Transfer, Database, File Watcher etc.) help eliminate custom built scripts which accomplish the same thing.

One big example I can think of is the availability of the Self Service plug-in. The non scheduling IT users or business users will actually be able to have insight into their automated job flows which is a feature that we never had before.

Quicker adoption of the newest versions of the product by all would help work out the bugs sooner.

4 and a half years.

I have not encountered any stability issues.

Mostly on our end, as we grow learning how to properly increase resources of the distributed servers and spread out the workload.

I've been happy not only with the customer service overall but also the speed with which I am contacted after submitting a case.

The level of technical support for Control-M continues to meet my needs.

CA Workload Scheduler, archaic, not intuitive, lack of features.

In house.

Price is based on how many jobs come into the scheduler each day (not executions) across all your different environments.

This evaluation was done a year or two before I started working with the product.

We install, configure, and deploy Control-M for customers and make it run on-premises from them. After that, the customers take over.

BMC uses partners. They don't sell directly in the Middle East. So, they don't directly install the product and sell it. Instead, they go through partners, like my company.

We, as a company, don't use Control-M, but we sell Control-M to customers. We go onto a customer site, install the product, and configure it per their requirements. Then, we get their feedback and support related project stuff.

From a services perspective, we actively use BIM, which is the affiliate manager. We use the history to see the forecast. When the customer gets Control-M, the affiliate manager comes along with it. 

It is 100% on-prem, primarily because the Helix part of Control-M is not hosted in the Middle East yet. For many customers, there are regulations since the primary customers are banking, insurance, etc., which all require their data to remain within the country.

My customers are primarily banking customers, so they have their end of day processes that happen at night after the bank closes. These processes would involve AML, banking, and end of month payroll-related stuff across multiple organizations.

We do maintenance, project management, and support. Once a project is done, the customer has a support contract through BMC. That is through us. Customers cannot directly get in touch with BMC to open cases. It has to go through a partner. Therefore, we offer first and second line support to the customer.

There is definitely room for improvement. Version 9.0.20 actually comes with a web-based interface, but there are still a lot of things unavailable with it. There will eventually be more inclusions added into the web interface, but there is still a long way to go. 

There is also the automation API, which is a way to interact with Control-M, but it also needs a lot of improvement for other people to understand how to use it.

The documentation isn't really straightforward for the initial setup. It says, "Follow the on-screen instructions." The reason why people read the documentation is to have a heads up of what to expect and what is coming up. However, when you say, "Follow the on-screen instructions," I believe that is inappropriate.

I have been using it for two or three years.

It is very stable. We hardly get calls in respect to issues on Control-M, particularly on version 9.0.19. 9.0.20 is still pretty new in terms of deployments. However, with version 9.0.18. I have had a couple of problems from customers.

You barely need one person for customer maintenance because the system is pretty stable. Of course, if it is version 9.0.18, the number of support cases that come in are more compared to version 9.0.19. We also get information requests from the customer where they might have audit requests or want to enable certain protocols because of security compliance within their organization. In these cases, they reach out to us. 

It is not that we are always involved with the customer. It is not an onsite model. If there is an issue with the product, the person calls. We have 20 customers whom we manage at the moment for BMC. That is just done with three people: an onsite resource and two employees, including myself. The onsite employee is with a telecom vendor within the UAE. His job is monitoring and maintaining the system as well as assisting the customer. He does everything in respect to Control-M at the customer site, e.g., defining jobs, monitoring jobs, executing jobs, and making sure that they are done properly. Another of my colleagues and myself deal with all the other customers from a project and support perspective. It is primarily support because once a project is done, then a customer has support with us. We manage those cases, involving ourselves in those cases. We understand what is required. If we have the information already and know how to do it, we will give them the procedure, etc. If we cannot do it, we get in touch with BMC to get the relevant answers.

I have not had an issue with scalability per se. If there is any kind of resource crunch, the customer just needs to add resources. If it is a memory usage, then add memory to the virtual machine and you are good to go. 

You can have jobs at multiple customer sites. For that, there is a different level of scalability altogether from an infrastructure perspective.

BMC support is good. I would give them eight or nine out of 10, most of the time. They reply quickly, even before the actual SLA time. However, in certain worst case scenarios, I would give them a seven out of 10.

Most of the time, the integrated guide immediately opens up the relevant page. You can get the necessary information from that. The videos are really basic. For example, with version 9.0.20, there are videos that come up by default in many places as part of the help page, which is ideal for beginners. Whereas, at my level of implementation, we are looking for more detailed explicit knowledge for a specific scenario. For beginners, the web help is more than enough, if a person is patient enough to go through it.

Personally, I have worked previously with a competitive product: Automic One Automation Platform. I was working with Broadcom earlier, doing a similar profile, where my portfolio was dealing with retail support and projects. So, I was deploying Atomic solutions. After that solution, I made a change and moved to BMC, as a partner. I have been working with Control-M ever since. Therefore, I have exposure with other automation products.

The initial setup is straightforward.

If all the prerequisites are ready, a full-fledged setup for a single system would take 15 to 20 minutes to deploy.

Normally, we deploy with high availability so it has an uninterrupted service, even if a server goes down.

Once the PO is all done for a project, we have a pre-kickoff with our company and the customer. We basically run them through the prerequisites and understand their priorities. For example, some customers are more inclined towards Windows and others are more inclined towards Linux. Most of them would like to have the DR environment in the setup, meaning it would be the primary site with two servers for high availability and a DR site with two servers. All these technicalities for the infrastructure and environment would be run by the customer along with the prerequisites. 

From a project perspective, we ideally implement the process flow. So, we understand their documentation. Then, we have an actual analysis and design phase, where we sit down with the customer stakeholders and get their requirements in terms of the actual process flows early on. Until then, we just know at a high level that these are the number of database jobs that will run on Control-M. We don't have explicit details at the analysis and design phase. We literally sit with them and go through their documentation, understand what they want to implement on Control-M, and how we can make it better or include notifications. After this, we start off with the installation. Based on the outcome of the analysis and design, we implement the process flows.

The annual licensing within BMC Control-M is on a per task basis. Three- and five-year contracts are also offered. The customer usually buys a bundle of tasks, e.g., 5,000 tasks, then my team configures Control-M for their usage. 

It is a good, stable solution. It does depend on what exactly you are implementing, because automation solutions are primarily back-end solutions, e.g., back-end processes and batch processes, which can be executed on Control-M. However, sometimes customers get back-end solutions confused with RPA, which is front-end automation. When customers decide that they want to use some kind of an automation tool, they should really understand what their process flows actually need. There is a handshake that can be given between the front-end and back-end, but there are some customers who come to us wanting to buy Control-M, but they are actually looking for an RPA solution because their operations are front-end.

I would rate Control-M as eight or nine out of 10 in terms of stability and features.