Control-M Reviews

We are using it for job scheduling, shift scheduling, etc. It is pretty much orchestrating all the job shifts for the IT team or core team.

We specialize in security, which means 24/7 your system or team needs to be ready for anything or anybody in the world, independent of even time differences. If you are managing your client's services from Europe, or anywhere else in the world, Control-M makes it easier to do scheduling, saving people time.

Since we have different satellite offices in Toronto and Ottawa, we use different role accessibility in different locations. That is why we are using it on-premise. However, in the next six months or so, we are planning to go to a hybrid cloud environment on Control-M since we are adding two or more satellite offices. We think that it will be more manageable if we implement it in a hybrid cloud environment.

The solution is innovative. Specifically for the overseas and time differences, you can feel the efficiency of Batch Impact Manager on jobs, batch processing, and impact management. It works the best on these kinds of issues. It saves us time and money, which is important. We save a lot using Control-M.

The most important thing is it is easy to manage conversions and stuff. It is easy to convert different systems, like AWS, which saves time.

We are working with vendors, partners, and clients to manage GDPR and data privacy. This solution is good with data privacy because BMC is GDPR compliant. That is very important, especially for overseas clients and businesses.

Overall, Control-M is quite critical for our business. I would rate this as nine out of 10.

• The monitoring
• Workflows
• Production
• Scheduling the shifts
• Timeframes for specific roles and management

Time differences are important because we have some overseas clients. That is why we are using Batch Impact Manager for the Control-M, which is very helpful for us. It detects potential blocks in advance, delays, and errors. That helps us to optimize the scheduling, then the batch workload processing as well. 

It is pretty easy to create, integrate, and automate data pipelines. It is user-friendly, not rocket science. That is what I like about the Control-M, and specifically Batch Impact Manager. You will need some orientation and need to know what you are doing if you are integrating your system, and this solution makes it easier.

We use Control-M Python Client and cloud data service integrations with GCP, which is pretty hassle-free. There aren't any problems or compliance issues. It is pretty easy to retrieve the data, do conversions, etc. They are on-time, and there is not much of a delay. 

The engineers on our team say that it is pretty easy to build, test and promote data workflows with the data coding language integrated into Control-M through the Control-M automation API. The ease of integration is eight out of 10. Python is the main language that our database managers and data engineers are using along with some other languages. 

The Control-M interface is user-friendly and easy to use. Orientation-wise, it is easy for data engineers to adapt.

Ingesting and processing data from different platforms can be a challenge. Control-M does allow integration for this with other systems to make this easier. For example, we integrate Control-M with an in-house system to do this.

I am unsure if Control-M is compliant with Microsoft Azure environment integrations. We have some clients in Azure environments. Specifically, in Canada, government agencies and nonprofits mostly use Microsoft Azure.

I have been using it for almost a year and a half.

The stability is very good. My impressions of the stability are very positive.

I would rate the scalability as nine out of 10.

The technical support is near perfect. I would rate them as nine and a half out of 10.

Positive

We were previously using an in-house solution, but we weren't improving it much, which is why we switched to Control-M.

Control-M creates cost-efficiencies, saves time on scheduling and data efficiency, and provides better data management. We use the managed services as well because we partner with some clients at MSPs and MSSPs. This solution is also good for their environment because it is easy to access, retrieve, and work with actionable data as well as all the procedures and processes. It is good and works. I would rate it as eight out of 10. 

The total cost of ownership is impacted by the Control-M pricing as well as the overall cost of the procedures and daily batch processing. We can easily see that at the end of the year, in terms of big time and money savings.

The pricing and licensing could be better. However, when I compare Control-M pricing with JAMS, Control-M is still better priced than JAMS enterprise.

We also evaluated JAMS Scheduler, which is also a workload automation solution. The pricing for Control-M was better and has good predictive maintenance that is better than JAMS. Control-M is also more integrated with Google for different solutions.

Control-M is better for the cloud. Specifically, the hybrid cloud is the best. On-premise is still okay, but it depends. Its hybrid cloud environment works better and is optimized in a better way to save money and time. Its implementation is easy from the cloud GCP and AWS. Microsoft Azure is not there yet, but otherwise, it is perfect.

I would rate the solution as nine out of 10.

We needed to automate our batch application workloads. We looked for a solution that perfectly matched our requirements. 

We use it as an orchestrator for our database, applications, data transfers, all data-related activities, and full automation of all processes.

We are able to automate all of our batch processes very efficiently with Control-M. Control-M from BMC is highly recommended. It fulfills our needs.

Control-M can handle a large volume of data. You can automate them as batch processes. You can create your own data pipelines and automate them according to your scheduled timelines. It can also fulfill all your workflow needs. You can monitor or have an overview of the job schedules and workflows with a single click. You can analyze through the logs and through the reports if any job has failed.

Control-M is very easy. Our DevOps team can efficiently perform their work by using Control-M. They can produce a timely report for the senior management if any job fails. They can easily automate and customize based on the user requirements by using Control-M.

Control-M consumes less memory and CPU. It consumes less infrastructure resources as compared to the other alternatives such as Broadcom. That is one reason why we are using Control-M.

Control-M saved us costs. We no longer need to deploy the workforce to manually schedule the job and batch processes. After implementing Control-M, all processes were automated. This automation saves time, effort, and money. It saves 25% to 30% of the cost. Previously, we had deployed 12 to 15 people.

Previously, many users used to call the help desk or the DevOps team directly to monitor their processes or get information about their jobs. Since implementing Control-M, we have given dashboard access to every user. They can get the details from their own dashboard. It is helpful that they have access to their own dashboard and they do not have to reach out to DevOps or other team members for small tasks or information. Control-M provides flexibility to our internal as well as external team members to get the information they need and when they need it.

It is very easy to create a pipeline within Control-M. You can easily create, design, develop, and test a pipeline on your own. You can monitor whenever you need to. There is also a notification feature where you get the alerts directly in your email and on the app so that you can take action.

After we have tested our workflows in the staging or testing servers, we can deploy our workflows or pipelines to production. Control-M helps us there too. Before moving to production, we can check any flagged areas or issues by using the Control-M dashboard and log management. We can easily migrate those pipelines to production. It helps in two ways. We do not need a lot of downtime of the application and the users also have visibility. It does not affect their businesses.

Control-M is very fast. It can transfer large data files at once. It can monitor workflows and has a notification feature in case of errors.

Control-M integrates with different third-party applications and tools. All the job-related flows or workflows are extremely useful. Anyone with some technical background can operate Control-M effortlessly.

Sometimes jobs fail without clear reasons. That needs to be improved.

Licensing costs could be improved, especially for small and mid-sized businesses.

After applying patch releases or version updates, some bugs appear that affect our daily activities. Testing should be more thorough before a release. When they have any release or update, we find issues in some modules and they do not work as expected. I advise them to test their releases well.

Their customer support can also be better. There can be improvements in the response time.

We have been using Control-M for more than three years.

Control-M is a highly stable product. It is considered a mature solution in the market.

Control-M is scalable. It can be scaled according to your requirements. It adapts well to organizational needs.

We have 100 to 120 internal and external users of this solution.

I would rate their customer support an eight out of ten. There are times when our team finds that they do not respond promptly. That could possibly be because the customer support is not well versed in the issues and the requirements of the customer.

Positive

Before using Control-M, we had engaged an external workforce to automate our processes. They manually ran jobs, wrote scripts, and scheduled the pipelines. They manually monitored the jobs and batch processes. Since implementing Control-M, we have seen drastic improvements. It saves time, human effort, and overall organizational cost.

It is deployed on the cloud. We are using it on AWS.

Its deployment is straightforward. It does not require a high level of technical expertise. Their solution architect and technical team can help you with the deployment.

After completing and finalizing our requirements, it took us around two weeks.

It does not require any maintenance because it is a fully managed service.

We took the help of BMC. They have their own team of solution architects, so we did not have to look for a third-party implementer.

We had our own migration strategy and a roadmap. They helped us in achieving the milestones in our roadmap. The BMC team has supported us in fulfilling the requirements.

Control-M has provided a positive return on investment by automating processes and allowing human resources to focus on other tasks.

We experienced a 12% return on investment last financial year and 8% the year before that. It has reduced the total cost of ownership by 15% to 20%.

While it is quite flexible, the licensing cost could be more affordable, especially for small and mid-sized enterprises.

We evaluated Apache Airflow, AWS Batch, and Azure Batch. We also evaluated Broadcom Automic Automation. We found Control-M to be the best fit for our requirements. It offered more functionality and features, along with better integration.

I would rate this solution higher in terms of value, functionality, and reliability. With Azure Batch, there were some instances where third-party applications were not fully optimized for Azure, so we had difficulty with that. Control-M is much more useful.

I would highly recommend Control-M to prospective users due to its comprehensive feature set and stability. BMC is known for providing world-class software support and services, making it a reliable choice.

Such a solution is quite essential for any organization. Any organization in need of transforming its businesses can benefit from Control-M. I would recommend Control-M to modernize your legacy system. I believe Control-M Helix has advanced features such as AI and machine learning. We are also evaluating that.

Our relationship with BMC is more transformative. BMC is a trusted partner as well as a trusted adviser for us.

I would rate Control-M a nine out of ten. There is always room for improvement.

I manage the team responsible for the tool itself, the administration of the system. We have a separate team internally that does all the operations and scheduling facets of the tool.

Our primary use case includes supply chain, payroll, accounting, information technology, pricing validations, etc. Most of the areas of the business have some facet into Control-M.

We have automated critical processes with Control-M. It is critical in a lot of different processes. We use it for all of our server patchings every month, we schedule that so that it kicks off the job every month, then goes and updates all of our Linux servers, for example, or our Windows servers. It does deployments and things that are critical to IT business.

Automating this critical process has taken the human aspect out of that process. So, that user no longer has to be up in the middle of the night to do server patching. That's all hands-free, completely zero downtime, knowing back to the customers. It's been beneficial in that regard.

Control-M helped improve data transfers. Specifically things like processing sales information. So we have all the data from our various retail locations, our individual stores that get processed every day automatically using Control-M. And we have our daily pricing information that we send to the stores to update all the pricing for all the different locations. Those would be some of the bigger areas of business automation.

It has helped to improve data transfers. Specifically things like processing sales information. So, we have all the data from our various retail locations, our individual stores that get processed every day automatically using Control-M. And we have our daily pricing information that we send to the stores to update all the pricing for all the different locations.

The most valuable features are the scheduling aspects of the tool and to have everything scheduled and automated to be able to run on a set timeframe.

It's important to our work because we can set it and forget it. We don't have to worry about logging in and pulling that data every day or manipulating the data. It can be run on a schedule and then the proper timing after dependencies are run.

Control-M provides us with a unified view where we can easily define, orchestrate, and monitor all of our application workflows and data pipelines. It's not super important in my particular line, but it is important for the operations and scheduling team that use the tool.

We use mobile interfaces. They allow the development teams to be able to go in and set up the jobs that they need to schedule them accordingly. There's still quite a bit of a gap between the two tools. So, a lot of our users still prefer to use the desktop client.

We use Control-M to integrate our file transfers within our application workflows. But we do not use the BMC MFT program. We use a different third-party file transfer tool.

The ability to integrate file transfers has been instrumental in allowing us to accomplish the things we need with Control-M. In our industry, we take a lot of data and either push it down to the stores or retail grocery stores. We take files and push them down to the stores or pull files and information from the stores and bring it back to corporate. So, it's two-way communication with file transfers. One of the bigger things that we do with Control-M is scheduling data moves and moving data from one location to another.

We also use Control-M to streamline our data and analytics projects. It's not doing any automation now. That would be done with the tools that it feeds, like Cognos or other reporting tools. It just collects data for us.

The integrated guides and how-to videos in the solution's web interface are okay for some of the basic user questions that we get for how to use the tool and do some of the basics, but from an admin standpoint, which is what I'm responsible for with my team, they're not very helpful. We still go back to BMC Docs, open tickets when we need to, and things of that nature to get the information.

The MFT applications should have more functionality and flexibility within that tool. Having more flexibility with that tool for handling the one to many or many to one concept. Like being able to take data from one source and push it to many locations or pull data from many locations and bring it back into a single source. That's why we still use our TPS program for the file transfers just because we don't have some of those capabilities available to us within MFT.

It is still a little difficult to get support on Control-M. It seems to be its own very specific BMC product unlike Remedy and some of the other BMC tools we have. It's quite a bit more difficult to get support for Control-M.

I would rate their support a five out of ten. They're just average to adequate. 

You don't have the option to have a dedicated support resource and engineer. Someone that works with you individually to understand your environment, to help you grow and adapt to new things, and to roadmap your maturity within the tool as you do with some of the other BMC tools.

We use Premier Support for other BMC tools, just not this one.

I have been using Control-M for two and a half years. The company started using the product in 2014.

It's very stable. We have no complaints in this area. The application is very well built and it is reliable. We were also very focused on the idea of availability when we built our environment.  We are setup with both high availability and a fail-over environments. If we were to have problems with a particular server, we have the secondary to fail over to.  Or, worst case, another environment to use in our secondary datacenter.

Scalability is excellent. It's easy enough to spin up another server and add it to the server group.

Pretty much every application that we have in this company has some kind of Control-M piece to it. That's everything from accounting and payroll for our stores and customer interfaces. We're pushing and pulling data and doing different job-related things for almost all applications.

We'll continually use Control-M. Our IT business has 3,400 people. Control-M is mostly used by some of our development teams, traditional application development groups that develop our in-house applications. We have our system administrators, our infrastructure teams, IT security, operations, and those types of groups.

We require only one staff member for day-to-day administration. She was responsible for all the day-to-day administration of the tool like adding users, provisioning users, making sure hotfixes are applied to system upgrades.  

We recently did overall system health initiatives. It was also a point of contact for our operations scheduling group. If they have questions on the tool if there are any issues, or things of that nature.

Technical support through BMC Support can be challenging at times.  If any issues need to be escalated to R&D then you have to work with directly with the team in Israel.  This can cause problems coordinating between time zones.  

We previously used ESP. There were a few reasons the company decided to move from ESP to BMC Control-M.   

1. The need for a product that was distributed based vs. mainframe based.  The company was working to retire the mainframe so there wasn't as much of a need for a product that was heavily mainframe focused. 

2. We were told that BMC Remedy and BMC Control-M were integrated so job failure ticket automation would be simple.

3. There was a desire to have the same vendor for our automation, orchestration, monitoring, CMDB, and ITSM tools.  BMC was able to meet this requirement.

For the initial conversion, we used BMC. Through the last couple of upgrades, we used other BMC preferred partners.

We have used both CFS and Cetan Corporation to assist us with upgrading the application.  Both companies were knowledgeable and we were able to perform the upgrades without problems.

Recently, we have been able to upgrade the environments without assistance from a third party.

The licensing and pricing are bundled together with our other BMC products. I don't know the specific cost of Control-M by itself. For us, it is based on how many jobs we run annually.  We run roughly 9,000 jobs a year.

If I had to guess, I would say it's in the neighborhood of about $250,000.

Since it is based on a per-job run, if we increase the number of jobs that we run annually, the cost will increase accordingly.

There are also additional operational costs, hardware for servers, databases, BMC maintenance, etc.

Yes, other vendors were evaluated at that time.  Control-M was selected primarily because of the integration between it and other BMC tools.

Make sure that you spend enough time to design and build your environment, both high availability and failover are critical to overall success.  Because we rely on Control-M so heavily, it needs to always be available. Control-M is critical to the success of our business, we cannot accept downtime. We do everything we can to keep the system running 24/7, 365. For example, we have invested additional time and resources to fully automate our monthly server patching. Now we can patch our environment with zero impact to jobs. 

Another piece of advice, use BMC as a partner for professional services, especially when doing your initial implementation.  It is a big endeavor and BMC can help you be successful.  Lastly, spend time training your staff on how to use and administer the product.  Control-M is a powerful but complex application.  It requires skilled and knowledgeable operators and admins to keep the system working well.

Control-M supports a lot of business processes. It supports some of the HR functions. I don't know if payroll is directly supported, but we do run jobs through PeopleSoft, which obviously impacts HR. Recently, we've started using the SAP module. So, we're making a transition from PeopleSoft to SAP, and I also see some payroll functions happening there.

We use Control-M to orchestrate a diverse landscape of vendor products such as Pega, MuleSoft, etc. File transfers and data feeds fetching are quite important for us. So, a lot of data processing happens through Control-M.

Control-M provides us with a unified view where we can easily define, orchestrate, and monitor all of our application workflows and data pipelines. Of course, such a diverse landscape requires you to make the effort to utilize Control-M to tie everything together or to act as the glue. Once you do that, everything is clearly defined, and you can view these disparate systems using one unified pane. If you don't define it correctly, then obviously Control-M won't have that insight, and so you'll have to go to multiple locations to go look at your job statuses.

We use its web interface. It is primarily for the application support teams to go monitor their own jobs. The jobs defined within Control-M are tightly controlled by a specific group of people. There are also people who need access to view that the jobs were completed successfully or why the jobs may have failed. These people are given access through Control-M web to view and monitor the jobs that they support or the applications they support. They're usually able to log on without having to install any client on their personal workstations. So, it's quite convenient. We have not implemented its mobile interface.

The integrated file transfers with our application workflows have certainly sped up our business service delivery by 80%. It has allowed the business to integrate file transfers more readily. Prior to utilizing the Control-M module, people had to write their own file transfer scripts in a scripting language of their choice to vary degrees of effectiveness. With the integrated File Transfer solution within Control-M, there is a standardized way of performing file transfers along with the capability of file watching and grabbing the file names that were transferred, making it much more versatile.

Control-M can immediately report when a job fails. If you have proper monitoring in place, you're notified immediately when your business flows are impacted. In the past, when you run jobs using Cron or just wrote shell scripts, you're really left in the dark because they don't necessarily report even from within Control-M. Implementing Control-M has made the business realize how critical and important it is to have proper error coding within the scripts that they schedule. If the scripts don't necessarily report any errors or redirect the system output into log files, when a job fails, there is no way to detect that.

We've automated many time-consuming business reports and other things that were very manual and took a tremendous amount of manhours. We've also automated a lot of maintenance using Control-M. We've integrated with Ansible Tower. So, we now are able to run Ansible playbooks and Ansible job templates. With the scheduling capability and the multitude of integrations that Control-M offers, it really acts as the unifying glue and as a communicator and orchestrator across the enterprise. With Ansible Tower, you can run a number of playbooks through it to perform patching and reboots and whatever maintenance that the infrastructure teams require, but you can't really do it when the business is still operating, or you can't do it when that business is operating, but you could do it for another business that's not operating at the moment. It is very hard to coordinate that without knowing which lines of business have jobs running or things like that. With Control-M, you can see that and you can actually enact workload policies to put jobs on hold prior to running Ansible playbooks. Once your Ansible playbook is complete, you can release the jobs again by deactivating the workload policies. So, it makes those processes very streamlined.

We do use the Role-Based Administration feature. We have been allowing other groups to gain more control over their agents so that they can define connection profiles, and they can do a little bit more on their side without inundating the main team with a lot of tasks. Everybody is happier. They can get things done faster, and they have immediate feedback and response because they're in control. The main Control-M team is not inundated with a lot of different requests from various teams to do a number of mechanical tasks. They don't get asked to create the connection profile for a database. People have all the information there, and they can do it themselves. They can define it in a way so that only they have access to it.

It has helped us to achieve faster issue resolution. Control-M reports on the error. It is easier to view the system output of that job. Whether it is an Informatica job, a scripted job, or a database job, it is easier to go in and view the issue and then troubleshoot from there. Most of the time, you can be running from the point of failure if the jobs aren't defined correctly. In a properly defined job, I would estimate that there is a 70% to 90% reduction in the meantime to resolution.

It has helped us by improving our service-level operations performance. We've built integration between Control-M and our ITSM, which is ServiceNow, and that has certainly allowed us to gain more visibility within our community through ServiceNow. Every time a production job fails, an incident ticket is cut, and that's highly visible. That needs to be escalated too, and there is a much more defined process to be able to resolve that issue. In the past, obviously, when you didn't have that level of visibility or that integration, there was always time lost in identifying what the issue is.

The File Transfer component is quite valuable. The integration with products such as Informatica and SAP is very valuable to us as well. Rather than having to build our own interface into those products, we can use the ones that come out of the box. The integration with databases is valuable as well. We use database jobs quite a bit. The file watcher component is also indispensable when integrating with other applications that generate files, instead of triggering a workflow based on time.

We have been experimenting with centralized connection profiles. There are some bugs to be worked out. So, we don't feel 100% comfortable with only using centralized connection profiles. We do have a mix of control on agents out there, which leads to some complications because earlier agents do not support centralized connection profiles.

A lot of the areas of improvement revolve around Automation API because that area is constantly evolving. It is constantly changing, and it is constantly being updated. There are some bugs that are introduced from one version to the next. So, the regression testing doesn't seem to capture some of the bugs that have been fixed in prior versions, and those bugs are then reintroduced in later versions. One particular example is that we were trying to use the Automation API to fetch a number of run ads users from the environment. The username had special characters and backspace characters because it was a Windows User ID. In the documentation, there is a documented workaround for that. However, that relied on two particular settings in the Tomcat web server. I later found out that these settings work out-of-the-box for version 9.0.19, but those two options were not included in the config file for 9.0.20. So, it led to a little bit of confusion and a lot of time trying to diagnose, both with support and the BMC community, what is the issue. Ultimately, we did resolve that, but that is time spent that really shouldn't have been spent. It had obviously been working in 9.0.19, and I don't know why that was missed in 9.0.20, but that's a primary example of an improvement that can happen.

We've also noticed that the Control-M agents themselves now run Java components. Over time, they tend to destabilize. It could be because garbage collection isn't happening, or something is not happening. We then realize that the agent is consuming quite a large amount of memory resources on the servers themselves. After recycling the agents and releasing that memory, things go back to normal, but there are times when the agent becomes unresponsive. The jobs get submitted, and nothing executes, but we don't know about it until somebody says, "Hey, but my job isn't running." When we look at it, it says Executing within the GUI, but there is no actual process running on the server. So, there is some disconnect there. There is no alerting function or the agent there that says, "Hey, I'm not responding." It is not showing up in the x alerts or anything like that.

The integrated guides have not been that helpful to us. I do find a lot of the how-to videos on the knowledge portal to be useful. However, there are some videos where the directions don't always match with some of the implementations. There are some typos here and there, but overall, those have been more helpful for us.

Its pricing and licensing could be a little bit better.  The regular Managed File Transfer piece, is a little overpriced, especially for folks who already have licensed Advanced File Transfer.

What I'm also noticing when I'm trying to recruit for Control-M positions is that the talent pool is quite small. There's not a whole lot of companies that utilize Control-M, and if they do, most people don't want to let their Control-M resources go if they're good. There is a high barrier of entry for most people to learn Control-M. There are Workbench, Automation API, and so forth mainly for developers to learn, but there are not a whole lot of resources out there for people to get more familiar with administering Control-M or things like that in terms of the technology or even awareness. So, it becomes very challenging to acquire new resources for that. A lot of the newer people coming out of college don't even know what is Control-M. If they do, they think of it as a batch scheduler, which is certainly not true in its current transformation.

Control-M is a very powerful enterprise tool, but the overall perception has not changed in the past five to six years that I've been working with Control-M. There's not much incentive for people to dive into that world. It is a very small community, and overall, the value of Control-M is not being showcased adequately, maybe at the C-level for corporations. I've had multiple conversations with other people and other companies who have already exit using Control-M. About 70% of the companies out there do not take full advantage of the capabilities in Control-M. So, that type of utilization really hampers and hinders the reputation of Control-M. That's because people then acquire this untrue concept that Control-M can only do X, Y, and Z, rather than the fact that Control-M can do so much more. I don't know if it needs a grassroots marketing movement or a top-down marketing movement, but this is what the perception is because that's what I'm hearing and that's what I'm seeing. For some of the challenges that I face working in Control-M, when I go back to my management and say, "Hey, I want to spend more money in this space," they're like, "Why? Can you justify it? This is what we see Control-M as it is. It's not going to bring us value in this area or that area." I have to go back and develop a new business case to say, "Hey, we need to upgrade to MFT enterprise or something like that." So, it definitely requires a lot more work convincing management in order to get all these components. In the past, we had to justify acquiring a workload change manager. We had to justify acquiring the workload archive. All of these bring benefits not only to our audit environment but also to the development environment, but the fact that we had to fight so hard to acquire these is challenging.

I've been using Control-M for about eight years.

Version 9 was very stable. Once they started adding a lot of the newer Java components, the stability suffered. It seems to have gotten better in version 9.0.20, but that's could be my basic perception. 

We run a lot of database client jobs. There are some things that we've implemented that I understand can contribute to the agent instability. We sometimes extract a lot of database output and massage that output using other scripts. I've noticed there are certain things that you cannot do with it, or there are some things that contribute to the instability. For example, in the output scanning functionality, there certainly is a size limit. You probably don't want to scan anything too large because that's going to put a lot of resources on the environment.

In addition, there are times when the agent becomes unresponsive. The jobs get submitted, but nothing executes. There is no alerting function. These are the examples of instability that I've noticed. Overall, the main application itself, the EM, and the scheduler have been pretty stable.

It is very scalable in terms of job execution. I haven't really explored scaling Control-M and the EM environment to a point where we have hundreds of users accessing it at a given time. That's because I don't have a hundred users who want to access that at a given time, but I do understand that you can distribute the web server more, and then have a load balancer to balance the load. I would think Control-M is a fairly scalable application.

In terms of its users, we have a lot of application support folks. We do have some developers who access Control-M mostly for the non-prod environments to execute and monitor their own jobs. There are some software engineers and operational engineers who are part of the application support teams that access Control-M. As for size or concurrent users, we have about 50 concurrent users at the max.

I would probably give them a nine out of 10. For the most part, they're very helpful, but there's always an initial standard dialogue. For an issue, you have to collect from EM logs, agent logs, and so forth, and you submit that. Sometimes, we have done all the advanced work and submitted it, but they still come back and say, "Hey, we need the logs." It seems like that's a canned response without looking at the tickets.

Positive

We've been with Control-M for quite a long time. We have not been using anything else in my history with this organization. 

I have not looked at anything recently. I am aware there are other application orchestration solutions out there, but I have not felt the need to go explore those options at the time.

If you're deploying using out-of-the-box options, the process is fairly straightforward. If there is some customization that needs to happen, then the process can be complex, and the documentation does not cover some of those complexities.

For the most part, we are standard out of the box. We have run into some performance issues where we had to, later on, go in and maybe make some modifications. For example, we had to stand up different gateways for various purposes just because one singular gateway was not enough to take the load in particular because we had installed a workload archive, and that was just taking up a lot of resources. Other human users were not able to perform their actions because the archive user was consuming so much of the server's resources. So, there was a lot of tweaking there, and we had to basically break out and distribute some of the components.

In terms of implementation strategy or deployment plan for Control-M, the environment always had Control-M, and we just had to upgrade the Control-M environment. We've had Control-M in our environment for quite a long time, probably when it was still version 6. So, as we progressed through different versions, we obviously had to expand the environment and the platforms. We initially started off with Control-M on AIX, and we later moved to Control-M on Linux. As you go to Linux, obviously, there is planning for high availability and production environments, disaster recovery environments, and so forth. So, you have to plan for marrying a lot of the BMC Control-M components and identifying where a load balancer may be required, or DNS ALIAS is required so that you can quickly flip over in the event something happens. Then, of course, there is sizing for the environment in terms of how many jobs are running, how many executions are happening, and so forth. This is how we plan.

We've used the AMIGO program, and then we've performed the upgrades ourselves.

For its day-to-day administration, we have a team of five people. They're administrators and schedulers.

Its return on investment is quite high, and that's mostly because we use so many of Control-M's capabilities. We also extend those capabilities. We write our own scripts to be able to integrate Control-M with so many other applications such as Automation Anywhere, Alteryx. We have also done vice versa. We have helped other teams develop their capabilities in integrating with the REST API and Control-M. So, the ROI is quite high for our use case, but based on the conversation with some of the community partners out there, their ROI is probably quite low because they're not making use of all these new features. I don't know if it is because they don't have the skillset to make use of these new features, or their management structure or process structure is hampering them from going out there. A lot of large companies I know like to maintain the status quo, and that's why they're slow to adapt and slow to move, which is going to hurt them in the long run, but in the meantime, it can hurt the adoption of Control-M as well.

Its pricing and licensing could be a little bit better. Based on my experience and discussions with other existing customers, everybody feels that the regular Managed File Transfer piece, not the enterprise one, is a little overpriced, especially for folks who already have licensed Advanced File Transfer. We understand that Advanced File Transfer is going away and is going to be the end of life, and there is some additional functionality built into MFT, but the additional functionality does not really correlate with the huge price increase over what we're paying for AFT already. This has actually driven a lot of people to look for alternative solutions.

I know they are now moving more towards endpoint licensing or task-based licensing. In my eyes, the value of Control-M is the ability to break down jobs from monolithic scripts. You don't want to have to wrap everything up in one monolithic script and say, "Hey, I'm executing one task because I want to save money." That defeats the purpose of controlling, and that defeats the value of Control-M. By being able to take that monolithic script and break it down into the 10 most basic components, you can monitor each step. It is self-documenting because, within Control-M, you can see how the flow will work, and you can recover from any one of those 10 steps rather than having to rerun the monolithic script should something fail. That being said, the endpoint licensing does make more sense, but maybe pricing or things like that can be more forgiving.

N/A

It is worth the time and money investment to learn more about Control-M. You should learn all the features of Control-M and really explore and test out the capabilities of Control-M. That's the only way people get comfortable with what Control-M can implement. A lot of people aren't aware of just how flexible a platform Control-M is, especially with all the new features that are being added via the Automation API. These features are helping to drive Control-M and things developed in Control-M more towards a microservices model.

We are just beginning to explore using Control-M as part of our DevOps automation toolchains and leverage its “as-code” interfaces for developers. Obviously, there is a little bit of a learning curve for developers as well in order to see the value of developing Jobs-as-Code. Currently, we're walking developers through it, and we're holding their hands a little bit in terms of developing Jobs-as-Code, but we are heading in that direction because it does provide artifacts that you can version control and change quickly and easily. You can redeploy much quicker than just having the jobs defined in the graphical user interface. Previously, when you had to modify it, you either did it via the GUI, or you exported it via XML and then modified those components. Once you get the developers closer to their job flows, then you can theoretically speed up the delivery of applications along with scheduled jobs.

I don't have a whole lot of experience with other scheduling orchestration environments, but from everything that I've heard while speaking with other colleagues, I would say Control-M ranks fairly high. I would rate it a nine out of 10. Control-M usually is the platform that people are moving to, not moving away from.

We use it for our workload automation. We use it as a single pane of automation for our enterprise.

We are currently using three different environments for three different productions. We have production data tasks, and we have multiple different levels spread out. 

We are currently using its most recent version. In terms of deployment models, they have both models. They have an on-prem solution, and they also have a SaaS solution. It just depends on what your company needs. They can take care of you.

Over the past so many years, I have learned that one of the most important features is giving everybody one tool that can do many different types of automation and workflows. That's been invaluable. Instead of having multiple tools for different teams and different platforms, Control-M has become the one-stop-shop for a lot of these automations.

It is very easy to create, integrate, and automate data pipelines with Control-M. It allows us to ingest and process data from different platforms. It could take us anywhere from a day to a week to get a new integration in place. We've taken it upon ourselves to try to introduce that to all of our internal customers as well.

It can orchestrate all our workflows, including file transfers, applications, data sources, data pipelines, and infrastructure with a rich library of plug-ins, which is very important for us. We try to utilize all new plugins that come out. If our company uses it, we try to use that plugin at least somewhere in our infrastructure.

In terms of creating, monitoring, and ensuring delivery of files as part of our data pipeline, it is a recent project, and it is something I've been learning about recently. However, having the ability to set up a job, set up a connection, deploy that job, and automatically have the feedback on where your files are when they've been moved has made life five times easier.

It has had an effect on our organization when creating actionable data. It has decreased the time to resolve dramatically. Everywhere I've worked, having Control-M orchestrate those alerts has been invaluable.

Our internal customers and management really appreciate the ability to be proactive before things really devolve into a problem or a high-severity incident. We're trying to incorporate analytics and proactive notifications as much as possible to decrease our downtime dramatically.

It impacts our business service delivery speed. Within the past few years, we have taken projects that normally would have taken multiple months, but the duration came down to a couple of weeks. So, we've increased our productivity tenfold.

Its impact on the speed of our audit preparation process has been great. With some of the built-in tools and some of the built-in reporting, being able to pull that data at any given moment has aided audit and probably increased our personal response time tenfold. We're able to get reports and audit out to the requesters within a week, if not sooner. Without Control-M, it would typically take us at least a month or so to get that out.

It has dramatically improved our execution times. We're able to get solutions out the door much quicker. A lot of our automations have been built around that, and we're able to get valuable output relatively quickly. When developing a new solution, without having Control-M, we would spin our wheels trying to come up with something that could only do a fraction of what Control-M can do at this point. Especially for a new solution or a new execution, we would be looking at a couple of weeks if not a couple of a month or two to come up with something deliverable. With Control-M, we're able to get that down to a week or two.

Our ability to integrate with many different solutions has been invaluable. The new approach of the automation API and jobs-as-code is also valuable.

The biggest improvement they could have is better QA testing before releases come out the door.

I have been using this solution for about 10 years.

I love it. It is rock solid. It is very stable.

There are no limits. You can easily scale up depending on your workload or whatever you need in a very short time. You can pretty much automate it at that point.

It is being used extensively in the organization. We do have multiple locations, but because we're using a web client, it is hard to say exactly how many end users are using it at this point. It is a company-wide solution. So, we probably have a couple of hundred users at this point.

They're very responsive. I'd rate them a 10 out of 10.

Positive

I personally have always used Control-M as my primary. I do know that other companies have experimented in the past, but I've always come back to Control-M.

I wasn't involved in the deployment. I always came on a little afterward.

In terms of maintenance, it is relatively maintenance-free besides the patches that come out. They come out pretty and frequently, but when they do, they're pretty comprehensive. Other than that, maintenance is pretty minimal. Because it is low maintenance, our engineering team does the maintenance when required.

We have absolutely seen an ROI. Over the last five years, I've heard we've done price analysis, especially with other tools. We always come out on top with Control-M. It always has the best price-to-performance ratio.

It is critical to our business. I don't know the facts and figures, but from anecdotes and talking to other management and up levels, I can say that it is considered a priceless solution in our environment.

If we no longer had Control-M, a lot of our most important pipelines would fall apart. Workflows would go unnoticed. The automation is so deeply integrated at this point that there's no telling what would break at this point. There may be things that we're not even thinking of.

For the tooling that you get, the licensing is acceptable. It has competitive pricing, especially with all the value that you get out of it.

There are additional costs with some of the additional modules, but they are all electives. Out of the box, you get the standard Control-M experience and the standard license. They're not forcing some of the modules on you. If you decide that you do need them, you can always purchase those separately.

I would advise working with the engineers, reading the documentation, and going into it expecting to set up high availability.

Control-M has been around a while. They're very quick to market, and they're very quick to adapt. At this point, they do have offerings, either on the way or recently released, that can support multiple cloud environments.

We are currently not using the Python Client, but that is on our board, and I do intend on investigating. We are utilizing some parts of the AWS integration.

I would rate it a 10 out of 10.

The business services that Control-M supports for our organization include everything from finances, marketing, data analysis, big data, data lakes—pretty much everything.

We have it on-prem and we also use it in the cloud. We still have most of our components in the data center right now.

When it comes to data analytics, Control-M helps make sure that as we're ingesting data and running it, that the workflows are kicking off in the correct order, and that we're actually getting the data. It's also making sure we return data to the appropriate business units or partners. It definitely streamlines our data analytics. It has sped things up because we don't have to wait on humans anymore to kick things off.

Our line-of-business personnel use Control-M's web interfaces and it gives them a view, a red-light/green-light dashboard. They can see if things are behind or ahead. It helps them keep track of the stuff that's important to them without having to call other people or put in tickets.

In addition, the use of Control-M as part of our DevOps automation toolchains and leveraging of its “as-code” interfaces for developers has considerably sped up our ability to roll out new applications and application updates. It's also allowed our developers, even when they have one-off projects, to easily use the automation API and Jobs-as-Code to kick those off without having to write that kind of function by hand or find another tool. It has been a big part of our DevOps process.

We have also automated critical processes with Control-M. The top-three are 

1. a number of financial processes
2. data ingestion
3. and what we call partner management. 

Those automations mean we get things done consistently and on time. It also lets us know if we're not going to meet our deadlines and enables us to be proactive instead of reactive.

By using Control-M 20’s Role-Based Administration feature, we have been able to decentralize teams to manage their own application workflow orchestration environments. That's important because it frees up resources. People can get things done more quickly without having to stop what they're doing. And it allows them to focus, instead of constantly being pulled in a thousand directions or having to call in different people for help. It helps eliminate tickets or requests to a Control-M administrator, and that frees up our operations personnel to focus on what's more important for the business. Instead of watching for and answering tickets, they're actually able to be proactive and look for potential bottlenecks or to help people enhance their processes.

Another benefit comes from using Control-M 20's Centralized Connection Profiles. Being able to store all connection profiles in a central database helps with efficiencies, with DevOps initiatives, and it helps with ownership.

The extended capabilities of version 20, especially the web interface, help because we don't have to deploy clients or maintain the clients. It lets pretty much anybody who wants to use it just fire up a web browser and use it. That's the biggest capability of version 20, for us.

Overall, Control-M lets us spot problems more quickly. And in terms of Service Level Operations performance, it helps because we now can be proactive instead of reactive. If we know that we're not going to meet an SLA, we can meet ahead of time instead of having to wait and see.

Among the most valuable features are

• the measuring and monitoring of the SLAs, the service level agreements—they code in recovery actions for when things go wrong
• the single pane of glass enables us to see everything, all the processes, in one place
• the ability to integrate with all sorts of different platforms and services.

It provides a unified view where you can orchestrate and monitor all your application workloads and data pipelines. That's very important because with cloud, software as a service, edge computing, traditional data center, and legacy apps, there are all these environments. If you don't have that single pane of glass or that one place to look at, you're going to invest a lot of time and resources into tracking things down when they go wrong. You really need that single pane of glass to show you what's going on across all your disparate systems, in one location.

We also have Control-M for internal and external file transfers. It's really just a part of our normal, everyday procedures. It makes sure that they happen. It makes sure that we got the files. It makes sure that data has flowed back to the appropriate departments.

They really need to work on improving the web interface, as there are still a lot of bugs. 

Also, the new Helix Control-M version doesn't seem quite ready for prime time for many of us. 

In general, they need to do a lot of work on shoring up their testing and quality assurance. A lot of bugs seem to make it into the product.

I've been using Control-M for about 21 years.

It's a highly stable product. It has to be—it runs your business. It's very mature in that arena.

It's highly scalable, so as your enterprise grows it's very easy to continue adding in agents or to expand out your management platform, with little or no downtime.

We use Control-M for financial applications across the spectrum, including marketing, data analytics, data analysis, and partner management. We continue to grow and as new things come online we're adding them in.

They do a really good job in terms of how they expand the product and keep up with the times. It's very cloud-centric, but at the same time, it can also handle legacy-type stuff. Overall, they've done a very good job on that.

What we had previously were all home-grown solutions. We switched to Control-M to get a grip on our environment, to have the single pane of glass to enable us to monitor and manage everything from one location. And the big thing that Control-M allows us to do now that we could not do previously is to orchestrate workflows across all types of disparate systems.

The initial setup was straightforward. It was easy to get going, easy to install, easy to create workflows consistently. There wasn't a huge learning curve. We learned as we went, but it was pretty easy to learn the product.

Our deployment took about a month.

The integrated guides and how-to videos in the solution’s web interface, for helping get to full productivity with the solution, are very helpful. People watch them. They need to be a little more in-depth and they need more of them, but what they have is a good start.

We have about 120 people in our company who are actively using Control-M. They range from developers to operations personnel, financial analysts, marketing analysts, and data scientists. We have a team of three for day-to-day administration of Control-M but they do more than just Control-M.

We worked with a partner to deploy Control-M. Our experience with them was very good.

We have definitely seen return on our investment in Control-M, many times over.

It's an expensive product, there's no doubt about it. It's one of those solutions where you're paying upfront to reap the benefits down the road. You're going to spend a lot of money upfront, but the benefits you're going to get out of it are going to quickly pay for it. That's something people don't understand sometimes.

We looked at a few others including IBM's Tivoli and Computer Associates.

The biggest difference is that Control-M is a more mature and growing product. The other ones were very stale. They just didn't seem to be keeping up with the times. Also, Control-M requires a lot less administration than the other products did, and Control-M was a lot easier to learn than the others. The others had a very high learning curve.

Look at Control-M from a high level, not only down to the details. See how it can benefit your company. Most companies have data centers, they use cloud, they use software as a service—they use a mixture. But even if you're 100 percent cloud, Control-M can still benefit you because it is going to give you that vision that you've never had before of what is going on in the company. And it's going to present it to you in a way that business owners and business management can understand. It's also going to allow you to do some amazing things with automation around the automation API and Jobs-as-Code. So instead of having all these siloed systems, it is really going to help you get many things under that one roof.

My biggest advice to anybody looking into this product, or any product like this is, is to do your due diligence and get your training. It's very important to have some sort of education on this going into it. That training could be formal training or it could be help from a Control-M partner for your implementation. You can get the easy stuff out of the product on day one, but to get to the things that are really going to save money and make you say, "Wow," that takes some knowledge.

The biggest thing I have learned from using Control-M is that you never know what you can automate until you try.

I work for the second largest chain of supermarkets in the UK. We are running about 90% of our jobs through Control-M. This applies for jobs and scripts on-premises and in the cloud.

When we used Control-M version 7, we were just doing scheduling. When we moved to Control-M version 9 six months ago, we started using the cloud plugins, like AWS.

Control-M is business-critical for our operations. It does all our monitoring and tracking.

Our command center people watch the Control-M job status and alerts. Since the pandemic started, and we are working from home, we have been providing them with Self Service. We started this two or three months back. Now, they can watch the jobs and alerts through their mobile and iPads instead of logging into their laptops.

We set up a file transfer mechanism because this will be easier for Control-M to track end-to-end.

We use Control-M as part of our DevOps automation toolchains. We have a four-person team for Control-M. We help the DevOps team create new jobs. We assign a dedicated resource to understand their requirements and how they can be integrated with other jobs. Because Control-M works end-to-end, it is critical for our DevOps daily jobs.

We use Control-M to streamline our data and analytics projects. Control-M has helped improve our data transfers. If there are no security concerns, the data can directly link to downstream systems. We use Control-M to watch all the transfers of files to their targets.

All our Control-M alerts go to our internal automation.

It has two-way integration. We now have a ServiceNow integration. 

Control-M reporting isn't that good. It is very limited. We would like the ability to create our own reports as well as the ability to publish dashboards in the cloud, which would help us. Improved reporting will help us determine statuses and get the answers that we need. However, I personally think BMC is not focusing on the reporting. I have even visited the BMC office in India, and asked, "Why haven't you improved the reporting?"

There are some latency issues with jobs between on-premises and the cloud. BMC is helping a lot to check the imports and exports from version 7 to version 9, including the EM server and the mainframe.

Control-M could improve agentless connectivity a little more. We are using it almost 100% with agents, but when we start using agentless, Sainsbury's Bank has different security mechanisms and we cannot install Control-M. For example, the agentless connection fluctuates a lot, which triggers alerts.

I have worked with Control-M for almost 10 years, since 2010.

The stability is very good. 

The scalability of the latest version is a drastic improvement compared to version 7.

We are getting good help from them. When I use Support Central, I can also see tickets that have been created by my colleagues.

We currently have IBM TWS as a job scheduler, but they don't automate their ticketing. Whereas, Control-M has automatic ticketing. 

We are using TWS for mainframe data. We are looking to start moving all our TWS jobs to Control-M now that Control-M is in the cloud. We are looking at moving these jobs around September or October, then we will have 200,000 jobs daily in Control-M.

We are trying to import from Control-M version 7 to Control-M version 9, but have experienced a major problem with its new features (database-related stuff). We are slowly fixing this as we go, with the help of BMC. Right now, we are doing this process step-by-step, but we can't upgrade everything to the latest version. We can only move everything to Control-M version 9.5.

Initially, we were first-timers doing the cloud. We had so many trials and errors. For importing, we created virtual machines in AWS and set up a lot of automation. However, we needed a static IP address for Control-M. So, we had to start from scratch to create new virtual machines with static IP addresses.

We are currently importing step-by-step. We still have two mainframe servers that we need to do and should be done by the end of August.

We have 70,000 jobs running daily. Control-M has reduced the number of jobs that we are running daily. We used to have more than 500,000 jobs running daily. This is very important to us.

Control-M has helped us resolve issues 70% to 80% faster. It provides us with alerts instead of having someone go to that particular server and check the logs to determine where the issue is. We can simply click on the alert information, then everything is in front of us. This provides us with time savings, human effort savings, and process savings.

You can't compare other tools to Control-M, because Control-M is further ahead of any other tool.

Once a year, as part of our disaster recovery, we restart Control-M and see what happens. Next, we will run those jobs through Control-M. Then, we will show management, "This is what happens if you use Control-M and if you don't use Control-M."

There are some areas of our business where we don't have Control-M. When we start doing those areas through Control-M, it will be an end-to-end solution.

We don't use Control-M for file transfers. We have proposed using Control-M for file transfer with version 9, which is in the cloud.

In the future, we will give control to the DevOps team through BMC AMI Change Manager. They will create the jobs, then send them to our BMC Control-M team for review, testing, and promotion to production. However, adopting this will take some time.

I would rate Control-M as a nine out of 10.

Control-M is a scheduler tool, and we have multiple batch jobs that are currently running in our organization. 

We are currently one version behind the latest one. The latest version is 9.0.19.200, which also has Control-M Python Client, and we are planning to go for the latest version.

We currently have it on-premises on the Windows platform. We are planning to migrate to AWS.

We have multiple technologies, and we have different types of jobs, such as Informatica jobs, SAP jobs, database jobs, web service jobs, etc. In such an environment, from the support perspective, usually, we need to log in to multiple technologies and check if a job is executed or not and if there is any error, which is not easy. Control-M acts as a one-stop shop to check the status of all jobs. The maintenance or support team members can easily log into Control-M and verify the job status.

It has been helpful in reducing the burden on our resources during the weekend. It has also been helpful in reducing delays and data mismatches.

It is easy to create, integrate, and automate data pipelines with Control-M. You can drop and drag whatever you want and then provide a time for the scheduler. There are many inbuilt plug-ins, such as the Informatica plug-in and the SAP plug-in. We are using these plugins. It is pretty easy and simple.

It allows us to ingest and process data from different platforms. For example, you can have a flow that starts with a REST call. Once that is processed, the records are picked from the database and sent to SAP. You can easily design a pipeline workflow and schedule jobs. You can also specify the dependencies. For example, you can specify to execute Job B when Job A is completed or execute Job C when Job A and B are completed. There are multiple options in Control-M to ingest and not miss data from any platform.

Testing is easy. You can have multiple environments, such as development environment, testing environment, staging environment, and production environments. You can easily test your workflows, and you can easily promote from one environment to another environment. You can promote from the development environment to the staging and production environment. There is an option called Promote, and you can use that option to promote to whichever environment you want.

We are an enterprise, and when the data moves from one technology to another technology, multiple teams get involved, which requires multiple communication exchanges between the teams. Sometimes, there might also be delays in getting the data from one team. With Control-M, we can create a workflow where we can specify to proceed for job B after job A. There is no need for a team to send emails to another team. There is no delay. Team A doesn't have to inform team B to run a job because otherwise, there will be a delay. Control-M eliminates such issues. It has improved our business service delivery speed.

It has good reporting capabilities. You can get a report of the status of all your jobs. You can see how many jobs are pending and how many are processed. You can also share these reports with the management. There is also a URL that you can give to your management or customers. They can check the job status, and they will have knowledge about the status and any abnormalities.

Automation of Control-M has improved the speed of process execution. No manual intervention is required using Control-M. You don't need to have a resource waiting to do a job at a certain time. You can automatically schedule a job, even over the weekend. It results in faster speed and better utilization of resources. You can also integrate it with other solutions. For example, if a job fails, a ticket can automatically be created in ServiceNow or BMC Remedy and assigned to a specific group so that they can look into it.

I find Control-M for SAP and Control-M for Informatica good. You can connect to the Linux or Windows servers, and you can run multiple jobs. 

Control-M Managed File Transfer is also a very nice feature for transferring multiple files.

It meets our requirements, and it is simple and easy to use. 

They can give more predefined plug-ins so that we don't have to create them. 

The security layer for Control-M MFT can be better. 

We have been using Control-M for the past six years.

Its stability is good.

Its scalability is good. We would like to increase its usage, but its price is a challenge.

Their technical support is very good. They also have a community portal. I would rate them a nine out of ten.

Positive

We didn't use any other solution previously.

I am responsible for installing and managing Control-M. Its initial setup was straightforward. It took about nine hours to get it installed and up and running. The number of people required for deployment and management of jobs depends on the scope of your operations. If you have 50,000 jobs a day, two people are enough.

Its maintenance is handled by the server team. We have it on-premises, and they take care of the patches and upgrades. If it was on the cloud, the upgrades would be done automatically.

Its pricing is a little bit high. They could provide an enterprise-level license for an unlimited number of jobs. Currently, it is based on the number of jobs, and if you exceed the number of jobs, there are charges. For example, if your license is for 3,000 jobs per day, but you run 3,050 jobs, you will have to pay for the extra 50 jobs. They charge $120 per job. So, it is too costly.

To someone who is looking for a process automation solution but is concerned that Control-M isn’t modern enough to work with multiple cloud-based data sources and tools, I would say that Control-M is the best option even when working with cloud-based data sources. 

I would rate it a nine out of ten. Control-M is the best solution to replace any enterprise solution if its price suits you.