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.

Control-M is used for file transfer and batch job scheduling.

Control-M provides a unified view where we can easily define, orchestrate, and monitor all application workflows and data pipelines. This is important because while running a robust environment, and managing and scheduling on individual servers are quite tedious. It has a centralized mechanism where it can schedule jobs on individual components within the environment. In this way, it helps with the ease of administration and achieving business requirements.

Control-M is used to integrate file transfers within the application workflows. Generally speaking, it has helped the business service delivery. For all applications, it has helped to notice bottlenecks, using its dashboard monitoring and alert mechanism. Therefore, immediate action can be taken in the case of failures. When compared to the traditional module or way of operating and scheduling, where the centralized monitoring alert mechanism is not available, Control-M helps in achieve having the application workflow run smoothly.

Control-M is useful to automate all critical and non-critical processes. Using Control-M, we can automate application workflows as well as file transfers involved in application workflows. We can also use it to run batches related to applications. Automating these processes reduces the RTO and RPO, which helps in the case of failures. It also helps to identify bottlenecks and take corrective measures.

1. File transfer.
2. It has an easy configuration. 
3. You don't need to create individual scripts for individual file transfer jobs. This reduces the load on the individual servers, when compared to a local task scheduler running on any OS.
4. The frequency at which it runs; it can be scheduled to run every minute. It is quite fast and quickly completes the job.
5. The online dashboard and job status. 
6. It has an alert mechanism for any failures.

These items are more useful when compared to the traditional way of doing or scheduling things.

It is on the web. This provides ease of administration, where we can manage the service from a central location. Also, can check or view all the jobs on a single dashboard, where we can manage and monitor them. 

In these three areas, I would like to see improvements in Control-M:

1. It is not giving us diagnostic logs during job runs. 
2. I would like them to beautify the dashboards, in terms of the number of jobs processed which have failed or are in progress. 
3. Control-M doesn't have any dynamic reporting facilities or features. 

I have been using it for about 1 year

If you implement Control-M, and configure it properly, it is quite stable. In the last year, BMC has been releasing a number of patches or updates to make it more stable. 

Initially, stability was not good. When BMC released quite a number of updates to fix some bugs, it became stable.

For any environment with about 80,000 of the jobs running per day, at least we require 10 people to monitor it and three people to administer it.

It is feasible to scale. We have not found any hiccups.

For an environment with about 80,000 jobs running per day, it requires at least 10 people to monitor it and three people to administer it.

Centralized monitoring and administration can be achieved

BMC support will be good level with more number or expertise available

BMC support is clueless on the new issues that arise. It seems like 90% of them are escalated to the R&D department, where they research and come back with a solution.

The guides or materials available are quite useful when exploring all the features.

No solution was used Previously, most of them use the traditional way of going through scripts.

Initially, the setup was a bit complex when trying to understand what all the features and settings do. However, when we explored it more, then we understood it and became comfortable with it.

Initial deployment took a couple of weeks. But once explored more the more convenient

The implementation is always with Control-M. Look at how to utilize all the features in Control-M, work out how to use them in subsequent reports, or while designing subsequent dataflows.

Work with BMC support for upgrades and for any issues encountered.

Looking at the rate of the usage, I can definitely see there is a gain. It is definitely profitable for any organization.

Control-M will help improve data transfers by approximately 80%. As an example, if you run any file transfer schedule in the local OS schedulers, compared to Control-M file transfer, Control-M will be better than the traditional schedulers. This is because of the number of features Control-M has and the frequency at which it runs. You can also choose the type of transaction data during a file transfer, which can be helpful for scheduling and troubleshooting.

Depends on business requirement

No other options available

I definitely recommend Control-M. It is quite stable, scalable, and the ease of administration is good as well.

Useful to automate batch scheduling. integrate within applications

Can be streamlined in data analytics applicaitons with Control-M.

I would rate Control-M as an eight out of 10.

Self Service, BIM features are most valuable. As no need to login to EM client and check the job status. From any where we can login to self service poral and validate the process status. Different Control modules.

5 years back, our organisation runs Control-M 6.2. After upgrading to ver 7, application team benefited with the new features and very to easy manage their application jobs. Productivity has increased, introduced Job naming standards, stream line the application based on the priority.. etc...,

All is well in Control-M tool . Thank you for new enhancements of tool . But for some issues, BMC will suggest to upgrade to new version which will not be feasible to standards of the organisation. Hence some work around should be shown to run the business until new version was upgraded.

I am working on Control-M tool from past 10 years in different organisations.

No, its very pretty simple to deployment and configure all the components.

No issues with stability. Its easy to switch PROD to DR and vise versa, if there are any issues.

No

10 out of 9.

10 out of 0

N/A

It's straightforward to use Control-M compare to other tools. Easy to migrate from other tools to Control-M.

Up-gradation from ver 6.2 to ver 7 was done in-house.

As technical personal. I am not able to answer this question.

Compare to other tools Pricing and licensing was more. It should be decrease.

In my previous organisation, I have refer Control-M for batch process. But due to pricing client has not agrees and then client has decided to go with Active Batch tool.

No.. Happy to work on Control-M and looking to upgrade current version Control-M ver 7 to 9. One suggestion after a stable version released there should be gap of 2 year of support.

Our organization works with the cloud and databases. Our primary use case for Control-M is automating orchestration and scheduling jobs across the cloud and on-prem. We use it to monitor and report on jobs. We also use the index to integrate with the cloud service. It leverages our ability to manage workloads across various cloud platforms like AWS and GCP. 

Implementing Control-M saved us time by reducing our manual intervention. We can divert more resources to meaningful work. It reduced the amount of manual intervention needed by 30 to 35 percent. 

In addition to improving efficiency, workflow orchestration enhances our integration with other tools. We can orchestrate across on-prem and cloud environments and reliably create and integrate data pipelines. Workflow orchestration is critical to our DevOps. Control-M is constantly surveying the network.

The most valuable features of Control-M are automation and orchestration. It allows a different schedule, and we can manage thousands of jobs. It ensures we can complete them on time accurately. This automation reduces our manual intervention, significantly reducing error.

Control-M should receive more notice when it releases new features. The user interface is also a bit complex, and the navigation should be streamlined. 

I have used Control-M for a year and a half. 

I rate Control-M eight out of 10 for stability. 

I rate Control-M nine out of 10 for scalability. 

I rate Control-M support eight out of 10. 

Positive

We used Broadcom before switching to Control-M. The migration was a little complex.

Deploying Control-M is somewhat complex. It's easier to convert to the other tool. We spent more than two weeks on the deployment and received some support from the Control-M side. We had almost five teams of people working on it. First, we set up the environment. Then, we ran the installation and reconfigured the database. After that, we did functional and integration testing. 

Switching to Control-M reduced our total ownership cost.

Control-M isn't cheap, but this is an enterprise model. 

I rate Control-M nine out of 10. I will recommend it. It's easy to integrate and has the flexibility we need. 

We use this solution to automate batch processing, create automated workflows to support various applications, and integrate various endpoints in the workflow to support business processes.

File transfer between our company and partner is critical for us. MFT has provided this solution and we are now using MFT for internal and external file transfers.

With version 9.0.18, which included new features, it has increased the usage of Control-M.

Introduction of Control-M-managed file transfer has increased usage in our organization. BIM is a good tool to monitor SLAs, and being a financial organization, this is a very good feature for us.

The most valuable feature is the Autoedit variable resolution in planning. This feature allows developers to better understand the schedule, and allow them to correct any potential issues in advance.

The MFT dashboard is also a useful tool to track all file transfers. It provides detailed information about both source and destination.

Control-M MFT and Control-M API both need improvement.

The Control-M MFT has to support checksums for FTP transfer between our own Control-M agents.

The Control-M API does not support SQL database-type jobs, where a job has been configured to use the SQL catalog to locate SSIS.

BIM needs further improvement to include any dynamic-type jobs with the workflow.

The support and bug fix timeline need improvement.

Technical support for this solution needs to be improved.

We did not use another solution prior to this one.

We did not evaluate other options before choosing this solution.

• The ability to view a history of jobs\tasks that have run: This makes troubleshooting a breeze.
• The ability to proactively forecast the runtime of a workflow: Managing SLA expectations and proactively generate alerts when the SLA won’t be met.
• Having a flow diagram of all workflows and the relationship between jobs\tasks: This is a visual representation of the entire workflow estate, which is updated in real time.
• Control modules: These are add-ons that further integrate Control-M with other third-party products, eliminating the need to write any custom code. E.g., Control-M For File Transfers makes it effortless to SFTP files externally or within the organization.
• Mass update: This feature allows for multiple fields of job definitions to be updated based on certain search criteria, with a very user-friendly interface.

It has given the organization visibility into how various applications relate to and depend on one another. It has reduced scripting and coding time down to almost zero with the out-of-the-box plugins.

There are many areas that have room for improvement in V7:

• Specific to Control-M for Files Transfer: Have a broader list or custom pre & post commands when running a file transfer.
• Customizable HTML shout emails, for a better user experience.
• Out-of-the-box New Day Process per table\application (This can be done with a custom user daily but requires a job to run at the specified “New Day Time”).
• Include some sort of label object (similar to a job, but only performs shouts and doesn’t have a cost), so you can categorize work flows.

Control-M V9 improves on most, if not all, of the pain points in V7.

In my professional career, I’ve been using Control-M for 12 years.

No issues experienced with stability at all.

I have not encountered any scalability issues. The way the product is tiered makes it easily scalable.

I find the level of technical support (Blue Turtle Technologies) to be exceptional. Whether it is a small query or a large problem, you will always get a timeous response and often one of the support staff members will be present on-site.

Control-M was here when I started at this organization, so I’m not sure if a different solution was previously used.

The initial setup was fairly simple. Once all the servers and DBs were set up, the installation of Control-M Enterprise Manager, Control-M Servers and Control-M Agents was painless.

Task-based licensing (number of active jobs) can get very expensive. Bundle multiple functions within a batch\script file.

I’ve tried and POCed many other workload automation\batch scheduling tools out there; none of them come close to functionality and ease-of-use as Control-M.

Decide on bulletproof naming standards\site standards. This will make implementation and promotion of workflows incredibly easy.

There are many valuable features, including its ability to interface with so many applications and allowing complex scheduling to be done easily.

BMC provides control modules that interface with third-party applications such as SAP, DB, VMware, FileWatcher, AFT and many more. These are valuable features that allow jobs with those applications to be easily scheduled.

We are able to automate a lot of scheduling, and integrate the scheduler with many applications to automate business cycles.

Cost

Provide a little customisation based on needs; the capability for development at the user level should be available. The reporting facility is a GUI with some standard queries. I think the portal needs to allow us to do reports that reflect many possibilities, like selecting fields present in the DB schema and building our own reports using the reporting GUI, rather than using any of the standard templates it offers.

Also, I’d like to be able to build a custom module for some applications that cannot be interfaced, provided we give some standard variables to connect with the application. For example, we are currently using the Axway product for file transfer on a very, very large scale. We are not happy with Axway, and would want to see if BMC can provide us a remedy for it. Or, if we were able to do some customization on the AFT module to incorporate this requirement.

I have used it for 10 years, starting with version 6.1.

I have not encountered any stability issues.

I have not encountered any scalability issues.

I rate technical support 10/10.

I did not previously use a different solution.

Initial setup was complex. We have integrated Control-M with many applications using some complex scripts for meeting our business needs.

Pricing and license cost is high.

Before choosing this product, we evaluated Redwood, Autosys, and $U (Dollar Universe).

If you are willing to pay for it, the product is excellent.

We use the product as our primary application tool for workload automation. It helps monitor and manage client domains in terms of configuration daily.

The product has enhanced the interface with a clear visual display of data and process batches, showing the completion status of workflows. It makes it easier to understand our organization's progress at a glance.

The platform integrates with Jenkins, Ansible, Docker, and Kubernetes. It can schedule and manage container workflows.

Integrating new solutions into the DevOps toolchain with the right approach and resources is straightforward. However, sometimes it can be complex.

It offers excellent visibility and management capabilities. It provides a centralized platform for monitoring and managing workflows and job scheduling. It supports various scheduling options, including time-based, event-based, and condition-based scheduling, allowing users to automate complex workflows efficiently.

It has simplified the process by streamlining the data workflow. It facilitates data extraction from sources, transforms it as needed, and loads it into the destination database. This comprehensive support for data extraction, transformation, and loading (ETL).

It is highly effective for building, scheduling, managing, and monitoring production workflows. For instance, it allows us to set up ETL processes to run at specific times, such as daily at midnight or in the morning. This precise scheduling ensures that all dependencies are met and tasks are executed in the correct sequence. For example, the transformation job is scheduled to start after the extraction job has been completed.

Operational efficiency is crucial as it reduces processing time. Faster data flow means job workflows are completed more quickly, reducing processing time. It is essential for meeting tight deadlines and maintaining smooth operations.

While numerous scheduling solutions are available, BMC's Control-M is highly effective for managing and orchestrating workflows across an enterprise.

The platform's best features are the monitoring capabilities. It is essential for tracking activities and ensuring jobs run smoothly. Additionally, the scheduling capability excels in building, scheduling, managing, and monitoring production workflows. These features are critical to our organization's operations and efficiency.

They could enhance the product's data flow, job processing speed, and efficiency.

Additionally, improvements are needed in real-time monitoring and alerts. Developing more robust real-time analytics capabilities to monitor and report the performance status of DevOps workflows would be beneficial.

I have been using Control-M for one and a half years.

It is a stable product. I rate the stability a nine.

Our organization has a team of 50 executives who use the product.

It is scalable. I rate the scalability a nine.

BMC's service team significantly supported the development of our migration plan for the Standard AutoCorrelation Controller (SGP). Their assistance involved several key steps. First, they helped us identify and map out the different requirements and dependencies, including how SGP jobs interact with one another and their integration within Control-M. The migration plan included phases for testing, fallback strategies, and execution. Post-migration validation was crucial to ensure that all SGP jobs were successfully migrated and were functioning correctly in the new environment.

Positive

The initial setup is easy. The deployment takes two months and involves a team of 50 executives.

The platform has helped us save 30% of operations time.

The product price is reasonable. I rate the pricing an eight.

I rate the product a nine out of ten.