Control-M Reviews & Product Details

Control-m provides the centralized automated scheduling and orchestration of work flows in across different platforms and applications . Mostly I like how it simplify complex jobs dependencies and ensuring SLA must meets and integrate with cross cloud platforms making operation more efficient and reliable . Review collected by and hosted on G2.com.

Below are some lists which i dislike in control-m .

1. Licensing cost relatively high comparing to other competitor of control-m .

2.GUI is looks outdated that can be upgraded .

3.Control-m is bit complex to configure for new users . Review collected by and hosted on G2.com.

Control-M makes complex job scheduling simple. I love it's intuitive interface, strong automation capabilities, and the way it integrates seamlessly with multiple platforms. It saves time and reduces manual effort. Review collected by and hosted on G2.com.

The initial setup and configuration process can be somewhat complicated for new users. Additionally, the licensing costs are significantly higher compared to other tools. What I find most frustrating is the column width and sizing in the self-service section. While many features have been carried over from CCM to the web version, the configuration windows remain quite small, making them difficult and frustrating to use. Review collected by and hosted on G2.com.

As an Automation Engineer, I use Control-M to manage processes that run for hours and span multiple systems. It handles complex timing, retries, and dependencies better than simple schedulers. I especially value the ability to pause, restart, or rerun only specific steps without breaking the full flow. The job history and execution details help validate changes after automation updates and make troubleshooting much more controlled. Review collected by and hosted on G2.com.

Automation design requires discipline. If standards are not followed, workflows can become hard to read over time. Some advanced configuration options are not obvious, so engineers need hands-on experience before building more complex logic. Review collected by and hosted on G2.com.

I like how Control-M gives early visibility into what is running, what is delayed, and what might fail next. Instead of waiting for user complaints, we can proactively watch critical background jobs and data movements. The dependency view is especially helpful because it shows how one delay can affect multiple systems. Review collected by and hosted on G2.com.

The platform needs ongoing attention. If alerts and views are not tuned properly, they can become noisy. Some routine admin tasks also take more steps than expected, so experience matters to use it efficiently. Review collected by and hosted on G2.com.

Managing tasks across various systems without switching between tools is made simple with Control-M. The timeline view makes it easier to keep track of what's pending, what's running, and potential delays. Additionally, it provides unambiguous alerts, making it simple to respond before a problem impacts workflow. Review collected by and hosted on G2.com.

When establishing new workflows, some configuration steps seem a little onerous. In some places, the interface might use some updating. Because the platform is so feature-rich, it also takes time for new users to comprehend all of the options. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I like that Control-M helps me understand how different systems depend on each other. I can see when jobs start, finish, or wait for inputs from other applications. This makes it easier to analyze system behavior and explain delays or failures to both technical and nontechnical teams. Review collected by and hosted on G2.com.

The tool has many options, which can feel overwhelming at first. Finding specific jobs or flows takes time if the environment is not well organized. Some views could be simpler for analysis work. Review collected by and hosted on G2.com.

I like below things of control-m

1.Centralized Orchestration

2.Dependency Management

3. Audit and Compliance

4. Visibility and Alert Mechanism Review collected by and hosted on G2.com.

I dislike below number of things of control-m .

1.Licenscing cost

2.Complex Setup

3.High Resource utilization .

4.Upgrade and Patch Management Review collected by and hosted on G2.com.

Control-M fits into environments where both legacy systems and modern tools exist. It helps coordinate background jobs that still matter to the business while allowing automation to be triggered through APIs. This makes it easier to keep deployments stable and avoid breaking downstream processes. Review collected by and hosted on G2.com.

It’s not a lightweight tool. Some configurations feel more operations-focused than DevOps-focused, and setting things up the “right way” takes planning. Without clear ownership, workflows can grow faster than documentation. Review collected by and hosted on G2.com.

I find Control-M to be a versatile and highly flexible product. It allows for groups of jobs to be configured to match business rules and requirements for diverse teams without forcing all teams to operate in the same way. I also appreciate the job flow self-documentation by the flow design, which makes it easy to reference and explain upstream and downstream processing steps, especially to less technical parties. The enterprise single-pane-of-glass visibility and dependency relationship flow are incredibly useful, and documentation linkage within the job to further details with just a click simplifies the process. Recommendation “7” due to the compexity of the product, and it being a heavyweight product. This is not a bad thing, however it is not for everyone in my opinion. Look for the time and resource required for a 1+ year integration effort. Review collected by and hosted on G2.com.

The product has been around a while and it should be flawless, but that's not the case. It's well known for its quirks and inconsistencies, and there are items that work differently between patch releases. It feels like QA is too light prior to launch. Review collected by and hosted on G2.com.