What is our primary use case?
The primary use case of this solution is workload automation in a batch environment, in clients' environments. This tool extends support to a number of applications and can be integrated with plugins like PeopleSoft and Informatica. It's a centralized monitoring system, so from the controlling client, you can monitor the entire batch environment of your client. It can also be used for disaster recovery.
This solution is deployed both on-prem and on the cloud. We are using the latest version.
What is most valuable?
This solution has a vast amount of features and with every new release, there are lots of new features introduced. The application has high availability—we have multiple customers and it's highly available. On an application level, if something goes down with the primary, then the application goes over to the secondary, so it's very, very easy to do disaster recovery.
From an application integration point of view, it has a lot of APIs, rich APIs. Every month, they are releasing new APIs and new updates, like Java, but more than that. Now they are introducing a couple more APIs, which you can use to integrate your controlling environment with any applications you want.
What needs improvement?
The only improvement I would suggest is the license pricing should be a little reduced. Apart from that, I don't see anything else as a major concern with the tool right now.
For how long have I used the solution?
I have been using this solution for more than 11 years now.
What do I think about the stability of the solution?
This is a stable product.
What do I think about the scalability of the solution?
This solution is scalable. We have more than 200 clients using Control-M.
How are customer service and support?
I've been working in the production environment for more than 11 years, but we created a high priority ticket for BMC when we first introduced it. They went all the way to resolve it and help us find a solution. Not only that, but they also helped us identify and analyze the root cause. In terms of customer support, BMC is at the top, in my rating.
I have raised seven tickets and, within 15 minutes, we would get a call from their technical support. They never leave us in the middle of an issue, they go all the way to help us resolve it. Their support is the best.
How was the initial setup?
The installation is pretty straightforward. Anybody who has just two or three years of experience in this tool can do the installation. Their documentation is really nice. If you have a little experience in these tools and installation, then you can easily install Control-M. The installation took 10-15 minutes, maximum, and you can do it yourself.
What about the implementation team?
I implemented this solution myself.
What's my experience with pricing, setup cost, and licensing?
The licensing is a bit more expensive than other tools, so if a client is focused on the cost, that would be something to consider. The licensing should be cheaper.
Which other solutions did I evaluate?
I don't have experience in AutoSys, but my team also operates in AutoSys.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.