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
186 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Centralized Orchestration and Visibility Make Control-M Stand Out
What do you like best about the product?
I like below things of control-m
1.Centralized Orchestration
2.Dependency Management
3. Audit and Compliance
4. Visibility and Alert Mechanism
1.Centralized Orchestration
2.Dependency Management
3. Audit and Compliance
4. Visibility and Alert Mechanism
What do you dislike about the product?
I dislike below number of things of control-m .
1.Licenscing cost
2.Complex Setup
3.High Resource utilization .
4.Upgrade and Patch Management
1.Licenscing cost
2.Complex Setup
3.High Resource utilization .
4.Upgrade and Patch Management
What problems is the product solving and how is that benefiting you?
1. I would said the main problem that control-m solving for me is that as administrator we need to maintain the kpi of sox report and controlm's audit and annotation mechanism help us to provide the audit details .
2. Its cross platform support things multiple hosts jobs can be run and managed in one workflow
3.SLA Management keep us alerting if a job delay is there .
2. Its cross platform support things multiple hosts jobs can be run and managed in one workflow
3.SLA Management keep us alerting if a job delay is there .
Centralized Workflow Management with Seamless Multi-Cloud Integration
What do you like best about the product?
Integration with multi cloud platform and a number of different applications which gives a centralized view of entire workflows.
What do you dislike about the product?
- Their inability to support scheduling Legacy app servers.
- Pricing is on a higher side.
- Pricing is on a higher side.
What problems is the product solving and how is that benefiting you?
- Helps maintain SLA for workflows.
- Helps identify the issues more quickly.
- Proactive alerts for Critical batch chains.
- Helps identify the issues more quickly.
- Proactive alerts for Critical batch chains.
Streamlined Automation with Control-M, Needs UI Enhancements
What do you like best about the product?
I really like the Control-M API because it minimizes manual intervention for activities in Control-M. The Control-M BIM, SAAS portal, and Reporting feature are very helpful in my daily activities. The Simplified Control-M App view for jobs, SLA, and automation is also something I appreciate. It was easy to search for any job, get notified about job failure and delay.
What do you dislike about the product?
The execution of jobs based on loops needs improvement, and there's a need to check both the application and Control-M UI for root cause analysis. Managing cloud-related jobs alongside on-prem jobs is a bit cumbersome. The UI could be more user-friendly by providing more convenient options, like searching for agentless hosts connected via an agent and finding specific agents linked to agentless hosts. Additionally, the centralized connection profile lacks sufficient information in the initial view, requiring further exploration to find details about the host where MFT/DB is installed.
What problems is the product solving and how is that benefiting you?
Control-M avoids manual intervention during activities and automation, provides quick information on critical chain failures and delays, and simplifies job searching while notifying failures and delays. The Control-M API minimizes manual tasks, and its BIM, SaaS portal, and reporting features aid daily activities.
Centralized Batch Scheduling with Robust Features
What do you like best about the product?
I like Control-M's ability for Hybrid Multicloud orchestration, which helps in managing a mix of old mainframes and modern cloud infrastructure within our bank. The Job As Code feature is beneficial as well. The Centralized Visibility and Auditing capabilities are also valuable, providing a centralized place to connect our systems, audit, monitor, and execute tasks effectively.
What do you dislike about the product?
It's quite complex at the learning stage, especially for beginners. Also, the cost is high. If I have a chance to improve it, my focus would be first on the native reporting tool, which definitely needs some enhancements.
What problems is the product solving and how is that benefiting you?
I use Control-M to reduce manual effort, system overload, downtime, and high operational cost. It centralizes job scheduling, provides hybrid multicloud orchestration, and offers centralized visibility and auditing, connecting our old and new IT infrastructures efficiently.
Comprehensive Orchestration with Room for Improvement
What do you like best about the product?
I like the user interfaces of Control-M, both the FAT Client and the Web UI. I appreciate that Control-M provides a lot of integrations by BMC, and I also like having the ability to create my own integrations using the Application Integrator.
What do you dislike about the product?
Sometimes it would be nice to have an integration provided by BMC. Or the integrations that are provided should have more functionalities. The Workload Archiver of Control-M could be improved by including more log information and keeping the logs revision-compliant. The MFT/E part of Control-M is missing a high-availability solution and a lot of modern MFT-functions. There could be improvements in regards to system requirements.
What problems is the product solving and how is that benefiting you?
Control-M solves gaps between different applications, databases, and file transfers.
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?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Robust Workflow Management with Control-M
What do you like best about the product?
I can say Control-M has a very good product support, and it effectively takes care of the vulnerability security part.
What do you dislike about the product?
I guess the interface needs improvement. They provide a web interface, but it doesn't contain all the features. Going more and more web-based would make it easier for all end users. Also, making it better for new users would be more efficient.
What problems is the product solving and how is that benefiting you?
Control-M provides a robust solution for managing workflows dependent on different processes, like file generation, and handles such scenarios superbly. It offers a user-friendly interface for end users whose applications depend on Control-M.
Powerful DevOps Automation with Robust Monitoring and Security
What do you like best about the product?
Below are some points I like in Control-M :-
1, Jobs as a code for Devops
2.Robust Monitoring and SLA Management .
3.Security and Compliances .
4.Cros Platform Support
1, Jobs as a code for Devops
2.Robust Monitoring and SLA Management .
3.Security and Compliances .
4.Cros Platform Support
What do you dislike about the product?
Below are some points I dislike in Control-M :-
1.High Licensing Cost .
2.Complexity on Setup .
3.Outdated GUI .
4.Advance File Transfer Limitation .
1.High Licensing Cost .
2.Complexity on Setup .
3.Outdated GUI .
4.Advance File Transfer Limitation .
What problems is the product solving and how is that benefiting you?
1. Complex Workflows Orchestration Acros Hybrid Environment .
2.SLA Compliance and Risk Business Disruption .
3.Devops Integration Challenges .
4.Opeartional Inefficiency and Resource Waste .
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
What do you like best about the product?
Below are some points what I like about control_m .
1.Centralized Job Scheduling Capabilities
2.Hybrid Platform Integration .
3.Secure File Transfer and Compliance
4.Centralised connection Profile
1.Centralized Job Scheduling Capabilities
2.Hybrid Platform Integration .
3.Secure File Transfer and Compliance
4.Centralised connection Profile
What do you dislike about the product?
Below are some points what I dislike about Control-M .
1.Cve Managing
2. Complex Maintenance
3.Upgrading and Challanging Configuration
1.Cve Managing
2. Complex Maintenance
3.Upgrading and Challanging Configuration
What problems is the product solving and how is that benefiting you?
1. Solving Complex workflow Orchestration .
2.CI/CD Implementation .
3.Opeartinal Overhead from Log and File Cleanup .
2.CI/CD Implementation .
3.Opeartinal Overhead from Log and File Cleanup .
Robust, Enterprise-Scale Solution for Complex Workflows
What do you like best about the product?
It’s robust, centralized and enterprise-scale which can handle complex dependencies and strict SLAs.
What do you dislike about the product?
High-cost, complexity and learning-curve.
What problems is the product solving and how is that benefiting you?
Solves the problem of reliably running complex, business critical workloads. Also brings very concrete benefits.
showing 21 - 30