Control-M reviewed by Senior Data Engineer in daily life.
Overall Satisfaction with Control-M
I have used Control-M for more than 3 years as a scheduler in data warehousing projects; it is feature-rich and stable. Business needs an all-rounder scheduling tool for most job orchestration, and thus has chosen Control-M. We are using it to schedule Informatica, Unix Shell script, Database, and other script jobs.
Pros
- The good thing is that there are so many connectors available. Control-M provides lots of features, and we are using almost 60 to 70% of them. Control-M is providing us with so much capability to use during our daily problem-solving.
- Most of the job creation is very simple and quick and worked as per expectations.
- Testing and debugging are also very easy, and you can test multiple scenarios using temporary changes during job runs.
- Log and output presentations are also very good, short and detailed.
- To monitor specific job net, we can create viewpoint, which can be use on daily basis.
Cons
- When I joined this project and was very new to Control-M, there was one problem that even the seniors sometimes faced. Suppose you are using Informatica; there are many Informatica developers in the market, or other tools that are well-known to everyone. Even though Control-M is used by many people, the documentation at the beginning was very hard to find on Google. This is why we had to reach out to experienced people, and it was a tough job for us because a few functionalities were not properly documented.
- Sometimes when we change over, there are multiple domains in Control-M, such as Planning, Monitoring, History, and Forecast Tools. When we hop from one domain to another, sometimes we open a job, and the detail dialog box or detail window fails to open.
- Some hidden features are not properly documented in Control-M itself, or are documented but not properly presented with examples. This is a problem. Sometimes we are forced to connect with senior developers who have used it for 5 to 6 years or more to learn about it.
- Control-M reduces the number of developers needed for orchestration. We have chosen this tool because it is easy to use, compact, and supports multi-platform integration.
- The Dev Team and the OPS Team are so happy with this tool. It saves time, and time saves money. Around a 30% increase in productivity.
45 - The DEV team, operations, business users, and the testing team are our primary users on a daily basis. It has increased productivity by around 25%. Control-M processes about 10,000 jobs every day in our production environment, and monitoring each job's current status is also super easy. We have a monitoring alert configured that sends emails for warnings or failures.
Control-M is generally considered superior to AutoSys for organizations requiring a centralized, cloud-forward, and developer-friendly orchestration platform. While AutoSys remains a robust choice for on-premises batch processing, Control-M excels in hybrid multicloud environments and modern DevOps integration.
Do you think Control-M delivers good value for the price?
Yes
Are you happy with Control-M's feature set?
Yes
Did Control-M live up to sales and marketing promises?
Yes
Did implementation of Control-M go as expected?
Yes
Would you buy Control-M again?
Yes


Comments
Please log in to join the conversation