What advice do you have for others considering BMC Control-M for Managed File Transfer?

Control-M does require some maintenance on your end, as with any software. There are fix packs released or patches, and you need to be aware of that. BMC is very good about notifying you when they post out new patches or fix packs. It usually requires a downtime, but it's a very short downtime. It takes longer to take the product down than to apply the patch for Control-M. You have all the processes to shut down, apply the patch, and bring them all back up, and the up and down takes longer than the actual patch application sometimes. I would rate this review a nine out of ten.

Control-M does not sell any perpetual licenses right now. I have to constantly renew my contract as a software subscription license. I think the pricing is a little high, but the solution is very robust and stable. I mean, I am paying for a Mercedes, and I am getting a Mercedes. My overall rating for Control-M out of ten for the solution overall is a seven. It is pricey, but it is stable. On the other hand, I have to work a lot to adapt my software to run with Control-M.

I will absolutely recommend Control-M. I rate Control-M as nine out of ten from a product perspective, and I give this review an overall rating of nine.

The biggest lesson I learned from using this solution is that Control-M is my favorite. The biggest lesson is that workflow orchestration is much more than scheduling jobs. It is about managing dependencies, handling failures gracefully, ensuring SLA compliance, and providing end-to-end visibility into business processes. As environments become more distributed across cloud and on-premises systems, centralized orchestration becomes increasingly important. Control-M is very helpful for building, scheduling, managing, and monitoring our workflows. It is a very mature, highly reliable platform that performs particularly well in large enterprise environments with complex and business-critical operations. For managing workflows, it offers centralized administration, role-based access, workload prioritization, audit trails, and lifecycle management. This helps standardize operations across multiple teams, environments, and geographic locations. It reduces our manual efforts and operational errors by 30 to 35 percent. It provides a unique and centralized dashboard for better visibility into workflow execution, which again helps us reduce our manual efforts by 25 percent. It provides faster incident detection and recovery and manages our incident responses by 25 percent. It improves compliance and auditability by 12 percent and enables easier management of hybrid cloud and on-premises workloads, resulting in improvements of about 15 to 20 percent. Integrating Control-M with technologies for our DataOps and DevOps processes is moderate. I would rate it seven out of 10. Control-M provides a broad set of out-of-the-box integrations and APIs for enterprise technologies. In our environment, we have integrated Control-M with technologies such as SQL databases, cloud services deployed in AWS and Azure, REST APIs, Kubernetes, and enterprise data platforms. These integrations enable us to orchestrate end-to-end workflows from data ingestion through processing and reporting while improving our overall visibility and reducing manual intervention. Our technology landscape involves containerized applications, cloud-native workloads, CI/CD applications, pipelines, and API-driven services. We ultimately reduce our reliance on legacy batch scripts and manual scheduling tools by consolidating all workloads into Control-M. This centralized approach improves governance, standardizes scheduling, simplifies monitoring, and strengthens SLA management. For building, scheduling, managing, and monitoring production workflows, I would rate Control-M nine out of 10 because it helps us in all these areas. It is one of the most natural enterprise workflow automation platforms, particularly for organizations running complex business-critical processes across hybrid environments. Workflow orchestration is extremely important to both DataOps and DevOps initiatives because it ensures that the data pipeline executes in the correct sequence, and data is available on time for downstream analytics and reporting to remain reliable. The biggest business value is reliability because instead of managing hundreds or thousands of independent jobs, organizations gain end-to-end visibility, automated failure handling, SLA tracking, and governance, which ultimately reduces operational risk, improves productivity, and helps ensure critical business processes are completed on time. I would highly recommend this solution to prospective buyers. I have given this review an overall rating of 10 out of 10.

Currently, we do not use Control-M to orchestrate workloads across multiple environments; all usage is on-premises. I have not used the Control-M Python client or API because no API was within our scope, so I cannot comment with any correct feedback.

Control-M, which is the BMC workload automation tool, is mainly used for scheduling. When we integrate Control-M into a SAP basis, we can automatically fetch records. We have to schedule and run jobs at a particular time, going through phases such as initial phase, build phase, and delivery phase. In that process, we handle job scheduling, workload management, creating OS and file transfer of database jobs, and reporting and configuration management involving automation capabilities. Currently, our client is using BMC's Control-M software, so we must go as per the client's requirements. We are not in a position to decide whether we can proceed with it or not because the client uses Control-M for batch scheduling. I definitely recommend BMC; Control-M is excellent for handling very large batch scheduling jobs. We have many jobs to complete in our daily activities, and this is one of the best tools. I would also recommend it to my partners for different clients who need batch scheduling; Control-M is a very good tool or application. Primarily for email and SNMP, as well as monitoring tools, we use Control-M compared to other solutions or vendors. I would rate this product an overall eight out of ten.

Control-M is utilized at a large scale. Control-M is very useful and is used by many businesses. I am a customer. My company bought this project. They are getting the project to onboard it to Control-M. We are supporting that onboarding, agent installation, agent upgradation, and all the things we are managing on the back end. Deployment of Control-M is both. We have both. Control-M in our environment is on-premises. Control-M is utilized in an MNC, enterprise-level. My last company was Wipro. Control-M was also being used there. It is also being used at this company. My relationship with Control-M is work-related, not transactional. My relationship with BMC is information-based. With Control-M, we configure it when they come with what they are doing manually. What they are currently doing is manual, or they are doing manual things by putting a manual person on it. We are analyzing those. We are thinking that if that can be onboarded to Control-M to automate. If we find that this can be done by Control-M, we get those things onboarded on Control-M in their environment. If it is a vendor or partner, we get one server from them, we configure all the things on their environment, and we run from our side. If they ask, I will be a reference for the vendor. Our company is a merger of five companies, including Guy Carpenter, Oliver Wyman, Mercer, and Marsh. These all companies are together. They all work on their business. If Mercer has the solution of Control-M and Guy Carpenter needs that, that business comes to us for onboarding their environment. It works this way. I would give Control-M an overall rating of eight out of ten.

I think the forecast is a feature to consider. I assess Control-M for building, scheduling, managing, and monitoring production workflows primarily through the Control-M GUI. The accuracy and reliability of Control-M's AI output are ninety percent accurate and reliable. My advice to others looking into using Control-M is to have it in their organization. I find this interview good and do not think any changes are needed for the future. I would rate Control-M a ten out of ten.

Approximately 2,000 to 3,000 people use Control-M, including users from Axis Bank where all employees are using Control-M. Control-M is recommended to other users by providing them a demo and showing them the uses, which helps them understand the benefits and features that Control-M provides that cannot be obtained from other tools. This allows them to rely on Control-M for their day-to-day tasks. One point is deducted from the overall rating because Control-M carries some vulnerability points. The overall rating for Control-M is nine out of ten.

The impacts that Control-M has caused for my organization have very visibly increased operational reliability. Before Control-M, most jobs were script-based, such as cron jobs, and there was a lot of dependency on manual monitoring. Until the jobs were reported as failed by the business teams, we would not have had visibility over them. Now with Control-M, we have an end-to-end workflow which is centrally managed. If a node has failed, it sends notifications, and there is a lot of error handling built in. There are multiple automatic retries, reducing human intervention. In terms of issue detection and resolution itself, we have dashboards configured that enable us to get alerted even before the businesses are impacted or the businesses report the impact, allowing us to solve issues proactively. This has also increased productivity improvement. When one of our reporting downstreams processes data and uploads it to our systems, it used to take an hour for the data to actually reflect. Businesses would notice missing data in the systems when they consumed the data. Now, within the duration when the job runs, it counts the number of rows we have, which means if the job fails, it is notified immediately within that 15-minute duration, helping us rerun the job. This means issues that were reported in an hour's time now get reported within the duration of the job running, which is within 15 minutes, leading to a significant improvement in how we see that the reports are being run. There is a huge user base in our organization, with about 3,000 users using Control-M. The levels of usage vary; some have read access and just view the jobs, while others perform deployments in terms of job scheduling and other tasks. We extensively use Control-M to schedule multiple banking-related jobs in varied fields, not just the contact center. We definitely intend to increase the usage. The biggest lesson I have learned from using Control-M is that it is a best-in-class workload automation platform, effective in building, scheduling, managing, and monitoring complex workflows, especially for critical applications such as DataOps and enterprise DevOps environments where reliability and SLAs play a major role. The cross-system orchestration matters significantly more than speed alone, as it ensures jobs run accurately and efficiently. My advice for others looking into using Control-M is that no matter how many systems you have, Control-M is the most competent and enterprise-scalable tool available. With various requirements, it is extremely reliable in monitoring and scheduling, making it an excellent choice. I would rate Control-M an 8 out of 10 overall.

Control-M does require maintenance on our end. There are two different windows of maintenance. One is when the core technology, in our case SAP, is getting under maintenance window, so we have to pause our jobs and resume it later on. This is a critical window that prevents our jobs from being pushed into SAP. We have to pause it and resume it depending on the schedules and make sure that we resume it and do not miss any jobs. The other window is when our agent maintenance or agent infrastructure maintenance occurs, when switching from a primary to a secondary agent, routing it, and making sure nothing is lost in the transit. Those are the two maintenance activities we perform. We have a team of seven today, with two of us as admins. We have three schedulers and two monitoring agents. Our engagement is with BMC. I have been involved with getting the contract rolled in for my current client and getting into the core of the technicalities in achieving the job requirements. It has been both. We achieved the project in a month's time with Control-M. We had a project of converting and migrating our jobs from SAP workload onto the Control-M scheduler. End to end, we took less than a month to get the agents installed on the SAP infrastructure and get these jobs migrated from the SAP workload. Overall, I give this product a review rating of ten.

With job scheduling and workflow automation, this automation has increased the scheduling time by fifty percent. The monitoring task has been reduced by twenty to thirty percent. Instead of going on multiple tabs, we can view it at once. Workflow management through the technologies is a bit of a complex task. As we have used this, we can implement it. For new users, it might be a bit complex. Currently, we have been using this for the past six months. We are seeing good, positive results. The automation workflow is also good, and the batch scheduling jobs are definitely good. We will still want to try it on different platforms and then decide on any further usage or increase in usage of Control-M. In production, this workflow is mainly through the monitoring and reporting features in Control-M. We check the job status to make sure the scheduled process completes successfully within the expected time window. If the job fails or is delayed, we review the logs again, analyze the dependency chain, and rerun or troubleshoot the job if needed. This helps ensure that the overall production workflow continues without impacting downstream processes. One piece of advice I would give is to spend time planning the job dependencies and workflows carefully during the initial stages. If the workflow is well-structured, Control-M can automate processes very efficiently and reduce manual intervention repeatedly. Overall, Control-M has been a reliable solution for managing automated workflows and scheduled jobs. It provides good visibility into job execution and helps teams maintain operational stability. I gave Control-M a rating of eight because it is a very reliable solution for scheduling jobs and automating workflows, and it helps me manage complex job dependencies and provides good monitoring capabilities, which makes it easier to track and troubleshoot batch processing. The reason I did not rate it higher is that the interface can feel complex for new users, and the initial setup and learning curve could be improved. With some improvements to the user interface and onboarding experience for new users, it could become even more effective.

The biggest lesson I have learned from using Control-M is that automation is very convenient, with workload automation and job scheduling being easy and maintaining jobs in Control-M being very manageable. My advice for others considering Control-M is that it is definitely a reliable option since it is convenient, flexible, and stable. Control-M is extensively used as we have deployed it for many asset teams, and we plan to increase its usage as we are in discussions with different teams to migrate their manual activities into Control-M. I would rate this review as a nine out of ten.

Deployment is on a Windows platform in a high availability environment. I would recommend Control-M to others looking to implement it, but it is essential to ensure it fits your environment, so doing a proof of concept is always beneficial.

Nearly 100 users are using Control-M in our organization. We previously used BMC Eclipse, which is a Software as a Service solution, for three years. Control-M has enabled us to transition from mainframe to the cloud environment with Azure. We are using this on a video conference basis. My overall rating for Control-M is 8 out of 10.

My advice to others looking into using Control-M is that it is easy to use, flexible, and stable. The features in Control-M are good, and the GUI of Control-M is actually very fantastic. Currently, 500 users are using Control-M in my organization, where the majority of them are from the application team and a few are admin and schedulers. Control-M is currently used extensively, and while we do not have plans to increase its usage, we are using Control-M in different domains. The biggest lesson I have learned from using Control-M is that it makes automation easy. It is easy to integrate Control-M with technologies for my data ops and DevOps processes as things change. I have automated activities on the Linux server while integrating with Control-M. I would rate this product a 10.

I would advise others looking into using Control-M that it is a good tool if you want workload automation to be done and if you want to save time. I have given this review a rating of seven out of ten.

For those considering using Control-M, I would advise it is an excellent choice for managing workflows and orchestrating jobs as per project demands. I have been using Control-M in various roles over the past 10 plus years, and I recommend it, provided you understand processes and setups. I give this review a rating of 9.

BMC Control-M Managed File Transfer is my favorite product, so while I would typically rate it around 9.7 or 9.8, I would ultimately assign it a rating of 10.

On a scale of one to ten, I rate this solution a ten.

Regarding workflow orchestration, I haven't quite used that part of BMC Control-M Managed File Transfer yet. I am totally satisfied with the functionality of the BMC Control-M Managed File Transfer product. I would definitely recommend BMC Control-M Managed File Transfer solution to other users. Overall, I would rate BMC Control-M Managed File Transfer an eight out of ten.

Since I'm not the vendor, I'm not going to disclose that information. The product has enough options to disable features that could expose proprietary information. One feature is that I can look at the output of a job, however, that can be disabled with security. It integrates LDAP and Active Directory authentication processes, making it secure and compliant. Overall, I would rate it a nine out of ten. We are just customers and not partners or resellers.

I would definitely recommend Control-M because it is a reliable tool expected to remain relevant for the next twenty to thirty years. I rate it ten out of ten.

I would rate BMC Control-M a nine out of ten. Build self service portals using the existing API endpoints to make provisioning easier.

Control-M is not just for file transfer; it integrates with all file-related jobs in downstream systems, including file generation, file transfer, and file usage. These processes run smoothly together, allowing us to meet KPH, PAs, and VNSLS SLAs. If you use a different tool for MFT, without proper control, there could be time delays. This might require adding buffer time between the file generation, file transfer, and file usage jobs, causing delays. With Control-M, there won't be any delays, as all three jobs run together seamlessly, ensuring no time lapse. Compared to script-based or other file transfer methods, Control-M offers a more streamlined process that doesn’t require extra support for file transfer tasks. Those managing the Control-M tool can handle file transfers and perform necessary checks. The integration includes a web or self-service portal, allowing customers to track file transfers and check their status, even from a web view. Unlike other tools where only the production support or technical team can monitor file transfers, Control-M allows users with appropriate credentials to verify whether a file transfer was successful. This is especially beneficial for reporting tool users like PowerBI, Cognos, or BusinessOptics, where data files are transferred from the source system to the reporting tool. Report users who refresh data manually can check if the file transfer was successful and, if necessary, rerun the job, ensuring their reports are updated on time without needing support from the technical team. Control-M offers excellent file management. In my current customer environment, more than 90% of file transfers are handled by Control-M, with only 5% to 10% done using internal mechanisms within AWS or Azure for cloud-specific transfers. For transfers within AWS, between applications, a small portion of the files is transferred outside Control-M. However, most file transfers go through Control-M, and the customer is satisfied because they don't need to pay extra for the product or support team. Control-M also handles email service and business view integration, allowing users to monitor and resolve file size, space, network, protocol, certification, and public key problems on-premises without additional support. Overall, I rate the solution an eight out of ten.

I recommend the solution to those who plan to use it. I rate the overall product an eight out of ten.

I rate the solution as a seven.

I definitely recommend the solution for automating manual workloads. You get good visibility for jobs and a dashboard to maintain things. There are no challenges and all of our customers are happy with the solution. I rate the solution a ten out of ten.

I'd advise looking at the roles and responsibilities of your team and your IT topology and assessing whether or not this product would fit into your basic production environment and/or some type of standalone system. There are multitudes of products out there, and some people even use homegrown products. It's based on your business needs and how you want to meet the needs of the end users and the consumers of the file transfers. I'd rate it a nine out of ten. We haven't had any issues with it.

I rate the solution a nine out of ten. The solution is good, but its current functionalities can be upgraded. I recommend the solution to users considering it.

I would recommend others follow the instructions given by the documentation and use it. That way, it is very simple to use. I rate BMC Control-M Managed File Transfer a ten out of ten.

We are mediators between the vendor and customers. We are using around version nine. I'm not sure of the exact version number. I'd rate the solution seven out of ten. I do need more time with the product. However, I haven't seen the product causing many issues. It's been sustainable, and we've liked having all operations in one single cluster.

If you are starting from scratch, I would strongly recommend the Control-M Matrix, which is BMC's current SaaS solution. It is my understanding that it is a lot less expensive. I haven't used it myself, but based on the prices, it's likely to be nearly half the price of what we currently pay. That simplifies your life because any upgrades to the Control-M server are handled by BMC. You go to the cloud, and they give you control and a server, and you don't have to worry about upgrades and such. The disadvantage is that BMC now has your data, and they do not currently have a SaaS solution available in Switzerland. I believe it is only in the United States that things can become complicated, and BMC would then have complete control over your licensing. They'd be able to see exactly how much you're using because we currently report how much we use. I believe it would work well for BMC because they would see a genuine reflection on usage and could then say, "You should be paying a lot more for what you are doing with the product." The SaaS solution is called Matrix Control-M. If I were starting from scratch today, that's what I'd look at first, but some people might want to keep it on-premises. Control-M obviously has agents that will work in the Amazon and whatever cloud, the Google Cloud, but that's a different story. Where you can have it on-premises but have your agents somewhere in the cloud. That's not a solution I've considered, but I suppose it's becoming more popular. I would rate BMC Control-M Managed File Transfer a nine out of ten.

I would rate this solution a nine out of ten.

I rate Control-M an eight out of ten, so there's some scope for input. To those considering implementation, I would advise you to have a good plan of what you need to set up—what does your environment really look like? Because to change your environment or database midway into something is a hefty task. So before starting it, I would advise you to check what your company's database looks like. Some use Oracle, some use Microsoft SQL, but BMC comes with a default one as well. It's better to plan that out because changing it midway is a task in and of itself.

I rate BMC Control-M a nine out of ten, because of the stability and the customer support. The only reason I wouldn't rate it a ten out of ten is because their licensing is a bit expensive. Otherwise, BMC Control-M is the best tool I have ever worked on. I would absolutely recommend this solution to new clients. Lots of new clients are converting to this Control-M tool because of the stability and the support model. So I wouldn't only recommend it externally, but, internally, we also recommend it to our clients. If they can compromise on cost a little, then this is the best tool to go with.

I think it's important to have knowledge about the infrastructure required, and the right data needs to be provided to the implementation partner. Once that's done, the solution is quite flexible to accommodate all requirements. I rate the solution nine out of 10.

I would rate BMC Control-M Managed File Transfer a nine out of ten. Our clients are happy with this solution.

This product is not feature-rich but it is a solid file-transfer solution. I would say that the features they have now are very good, although the product is not complete because you cannot send files. I would recommend it but at the same time, I think that everybody needs to test it and see if it meets their needs. The supported features are very good but obviously, if there is a protocol or something else that you need that isn't supported then it will not be suitable. I would rate this solution a seven out of ten.

The work is really on the configuration side. Installation is not a problem these days. Push it out as much as possible, to have a dedicated team and to decide that you're going to investigate enterprise completely and figure out where the automation will pay the quickest dividends because the return on investment is very quick on these kinds of products. Once you start to use them and you realize how useful they are, then you really make a big difference to the company and it can save a lot of money for many large organizations. Obviously there will be some situations where it doesn't make sense to use it because you're happy with your setup. But there are numerous elements of the business that would benefit that you might just have to get out to your users and ask how you can help improve the way day-to-day work is dealt with. I would rate this product a nine out of 10.