Control-M is used for scheduling, specifically scheduling application jobs. We have always been using Control-M, as we inherited it. We work with all technologies within the business using Control-M, including WebMethods, Axway, and IBM MQ. In the managed file transfer space, using Control-M, I find that it is not as user-friendly as other products available for MFT.
Control-M SaaS
BMC SoftwareExternal reviews
External reviews are not included in the AWS star rating for the product.
Comprehensive Orchestration with Room for Improvement
Workflow orchestration has reduced manual effort and now supports complex hybrid integrations
What is our primary use case?
What is most valuable?
The best features in Control-M are its ease of use and robustness; it is very feature-rich, which is what we use it for—scheduling. It is easy to integrate Control-M with technologies for our DataOps and DevOps processes as things change. The integration aspects of Control-M are out of the box, so they are straightforward to use. From using Control-M, I have seen improvements as they grow with the versions; with the newer versions come enhanced functionalities, such as the latest version allowing access through a web GUI instead of the client GUI that you have to install, which is quite helpful because you can access it from anywhere.
What needs improvement?
We are not on the latest version of Control-M; we currently have version 20 and 21.
For how long have I used the solution?
I have been using Control-M for 10 years.
What do I think about the stability of the solution?
Regarding stability with Control-M, I would rate it nine out of ten for downtime, bugs, and glitches.
What do I think about the scalability of the solution?
Control-M is very scalable, and I would rate it a nine.
How are customer service and support?
I would rate the vendor's technical support for Control-M as a nine.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have tried to look at other products, but there is no other product out there that does what it needs to do as Control-M does, which is why it is still around—it simply does what it needs to do.
How was the initial setup?
The deployment of Control-M was quite complex to get in, but once it is in, it does what it needs to do. It took weeks to get Control-M deployed.
What about the implementation team?
Control-M requires maintenance from our end, as we have to perform patching whenever needed, but that does not happen very often—probably once a quarter. Patching for Control-M is easy.
What was our ROI?
I have definitely seen a return on investment with Control-M in terms of time and resources, but I cannot speak to the financial aspect—I do not know. I would estimate that I have saved perhaps 20% to 30% on time and resources using Control-M.
What's my experience with pricing, setup cost, and licensing?
From what I know about pricing, I would probably put Control-M in the expensive category, but you do pay for what you get; you are paying for a premium product.
Which other solutions did I evaluate?
We looked at AWS products for scheduling with Control-M; I cannot remember the actual name of the scheduling tool at AWS, but it is nowhere near as advanced as what we need.
What other advice do I have?
Approximately 100 users work with Control-M. They are not all Australia-based; some users are from India, so we have offshore resources as well. My relationship with BMC is both transformative and transactional. Regarding the transformative aspect, I have impressions of BMC as both because we partner with them; we might not be strategic partners, but we value their advice all the time—not just product advice, but sales as well. We consider ourselves a partner with the vendor, but I do not know if we are officially a signed partner; we are a partner at the base level. When I refer to our relationship with the vendor, we are considered an entry level partner; we are not a reseller, so we cannot resell their products, but we are partners and we consult while using their products internally and with customers to support their customer base. Our clients are generally enterprise businesses. I would recommend Control-M to other users; I know they are going all web-based, which they believe is the best way to go, but I can tell you that everybody I have spoken to has said the contrary—they actually prefer the client GUI that you can install, which is easier to use and more feature-rich, while the web GUI is very hard and difficult to navigate through. I have rated this review a nine out of ten overall.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Robust Workflow Management with Control-M
Powerful DevOps Automation with Robust Monitoring and Security
1, Jobs as a code for Devops
2.Robust Monitoring and SLA Management .
3.Security and Compliances .
4.Cros Platform Support
1.High Licensing Cost .
2.Complexity on Setup .
3.Outdated GUI .
4.Advance File Transfer Limitation .
2.SLA Compliance and Risk Business Disruption .
3.Devops Integration Challenges .
4.Opeartional Inefficiency and Resource Waste .
Centralized Scheduling and Seamless Integration Make Control-M Stand Out
1.Centralized Job Scheduling Capabilities
2.Hybrid Platform Integration .
3.Secure File Transfer and Compliance
4.Centralised connection Profile
1.Cve Managing
2. Complex Maintenance
3.Upgrading and Challanging Configuration
2.CI/CD Implementation .
3.Opeartinal Overhead from Log and File Cleanup .
Robust, Enterprise-Scale Solution for Complex Workflows
Effortless Job Scheduling and Seamless Integration
User-Friendly GUI with Seamless Batch Scheduling
Centralized Workflow Automation That Simplifies Complex Operations
1. Licensing cost relatively high comparing to other competitor of control-m .
2.GUI is looks outdated that can be upgraded .
3.Control-m is bit complex to configure for new users .
1.Early alerts of SLA breaches which helps us to be ready for the disaster .
2.Different team's can view there jobs in one workflow
3.ON-prem and cloud jobs can be managed by admin team in one url also .
4.even if password expire of os or db the infra teams are able to take the backup of their db and os in control-m .