What is our primary use case?
Control-M runs all of our payments, batch, and managed file transfers.
Approximately 250 people use Control-M on a daily basis. Their main roles include schedulers who create batch jobs, testers, and administrators and operators.
Control-M enables us to better support our DataOps and DevOps initiatives because we have a release system every month, which allows us to work more effectively and we're automating that system with Control-M.
Control-M orchestrates workloads across several environments. Currently, we use it across five environments.
Control-M handles complex data pipelines and analytics processes by allowing us to integrate with different services. For instance, we use it with our Power BI for our reporting tools, and for pipelines for release functions as well.
We only use on-premise for the creation and automation of data pipelines with Control-M. We don't have the cloud yet.
What is most valuable?
The main features of Control-M that we appreciate the most are the scheduling and the automation capabilities. When it works, it really works very well for us. Another feature that we appreciate is the file watching service because we interact with many different sections who drop files in various locations. It's great to have that feature to kick off batch when a file becomes available.
Control-M's performance in building, scheduling, managing, and monitoring workflows is amazing. I love Control-M and enjoy working on it. I appreciate how it has automated our workflow because before we had Control-M, it was a manual workflow that was open to user error and took much longer to complete because of the manual checks we had to do before we moved on to our next piece of batch. We've been able to automate it and this has enabled us to triple our workflow.
What needs improvement?
Having more options with regards to scheduling in Control-M would improve it. There are certain scheduling features that aren't available currently in Control-M, which would be nice to be added.
For how long have I used the solution?
I've been using Control-M for six years.
What do I think about the stability of the solution?
I assess the stability and reliability of Control-M as very reliable because we very rarely have any downtime. The only time we would ever have any downtime is during our reboots, which we need to do failovers for, and those are very brief. When we are actually doing our batch, I don't remember a time we've had any downtime on our production side.
What do I think about the scalability of the solution?
Control-M scales with the growing needs of my company brilliantly. It's been really good for us. We've added so much to it over the last two or three years. We've added more users, more jobs, and all different types of jobs including OS jobs, MFTs, and file watch, and it's been absolutely no problem for us to add. We've probably doubled our amount of jobs in the last two years, so we've had absolutely no problem with it. It's scaling perfectly.
How are customer service and support?
My experience with customer service and technical support has been positive. Anytime we've had a problem, which is very rarely, or we've had a question, it's always been answered very swiftly or I've looked through the community myself. The community is actually really good, and I really appreciate that side of it because I even contribute on that side. I've never had a problem.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We were using an in-house product for running our batch before integrating with Control-M. Control-M enabled us to automate that batch, but it also enabled us to bring in many more things that weren't currently being done by us.
What was our ROI?
The biggest return on investment for me when using Control-M is the reduced errors, quicker runtimes for our batch, and making the job easier.
Which other solutions did I evaluate?
I have not considered other solutions while using Control-M.
What other advice do I have?
Control-M's performance has improved our timing and the speed of the releases. It's halved our release speed basically in the last two years.
The measurable benefits and improvements my company has achieved with Control-M include reduced errors, which is the first big one. Before we used the previous in-house software, we would have a lot of manual errors that would have to be changed manually if there was a change in a variable or anything else. Now it's all automated, and the system runs for itself. We've tripled our workflow and we are doing more in less time than we used to previously.
Control-M has enabled new capabilities and business processes that weren't possible before. Our integration with external partners has become easier due to the MFT capability that we weren't doing before. Now we're able to connect through them. These were manual processes done through moving files manually from one server to another, through different partners, but now we're able to integrate it all as one.
Regarding licensing, we handle licensing through endpoints. We've had to increase our endpoints because we're increasing the amount of workflow we have and the amount of jobs that we have. We've had to increase the number of endpoints we've needed. It's very easy to handle the growth and it's easily done.
I haven't used the Control-M Python client, but I've used a small amount of API.
I have not been using Control-M since I've been in my company because I've been in my company since 2009, and we started using it in 2019.
The impact of the migration to Control-M on our business-critical operations has led to fewer errors and fewer failures. Our biggest success story has been the lack of errors. Even when we do have errors, having the outputs available to us allows us to clearly see what the problem is.
I would rate this review ten out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.