Effortless Automation for Everyone
What do you like best about the product?
Makes automatization easy, fast and simple for anyone that uses it
What do you dislike about the product?
Sometimes the system is a bit slow to respond
What problems is the product solving and how is that benefiting you?
Financial reports, security copies and data transfer
Effortless to Use with Outstanding Observability
What do you like best about the product?
Ease of use and observability make the product very user friendly.
What do you dislike about the product?
The upgrades from version 9.0.20.x has been a difficult task.
What problems is the product solving and how is that benefiting you?
SLA management is always a concern. Control-M helps us track deviations from normal runs of workflows.
Effortless Scheduling and Versatile Job Management
What do you like best about the product?
Ease of use. Multiple ways of scheduling and connecting jobs.
What do you dislike about the product?
The differences between the client and the web. They changed terminology in the web, but not in the client, so as we try to move from one to the other, there is some difficulty in finding things. The scheduling in the web is different and harder to use. Maybe because there are more options. We have not had time to look into these changes and how to use it.
What problems is the product solving and how is that benefiting you?
The integration with different services, so we can move away from using scripts. Looking forward to implementing MFT and getting rid of all of our current FTP scripts.
Best views for complex data
What do you like best about the product?
The reporting and forecasting abilities.
What do you dislike about the product?
The loss of what services a specific job belongs to from a historical view.
What problems is the product solving and how is that benefiting you?
Accurate predictions of end times for critical services.
Centralized Automation with Room for UI Improvement
What do you like best about the product?
I love how Control-M centralizes and automates complex batch processes, significantly reducing manual effort and minimizing the risk of human error. The centralized dashboard is particularly impressive as it allows me to see every job, dependency, and workflow in real-time. This feature lets me immediately view job statuses, dependencies, and potential bottlenecks without the need to dig through multiple screens, making it extremely efficient and user-friendly. Additionally, the tool integrates seamlessly with monitoring tools like Splunk and CloudWatch for tracking logs and alerts, and with ticketing systems such as ServiceNow or Jira for incident management and workflow tracking, ensuring a smooth operational workflow. The initial setup was straightforward, and the visual tools made defining workflows easier once the core setup was established. The comprehensive documentation is also a big help for getting started, although there is a learning curve. Overall, based on my experience, I confidently give Control-M a recommendation score of 10 out of 10.
What do you dislike about the product?
Some areas of the Control-M interface still feel outdated and could benefit from a more modern, streamlined design. The visual layout can become crowded, especially when navigating large workflow maps. This makes improved zooming, grouping, or filtering options a desirable enhancement. Additionally, while the installation process was straightforward, configuring the environment, agents, security settings, and integrations required planning and technical knowledge. The documentation was helpful, but there remains a learning curve for new users.
What problems is the product solving and how is that benefiting you?
I find Control-M helps by centralizing and automating complex batch processes, reducing manual effort and human error. The dashboard offers real-time overview, making it easy to track job statuses and workflows.
Effortless Workflow Automation and Seamless CI/CD Integration
What do you like best about the product?
Control-M lets us design workflows as code and keep everything in Git. It fits well with CI/CD, so job changes can be tested and deployed just like application updates. This makes our automations more consistent and easier to maintain.
What do you dislike about the product?
Some advanced options take a while to learn, and creating new integrations often requires coordination with other teams. When multiple groups add jobs without a structure, the workspace can feel cluttered and harder to search through.
What problems is the product solving and how is that benefiting you?
It gives us one place to create and manage automations, keeps tasks running in the right order, and reduces manual fixes. This makes our processes more stable and easier to maintain.
Effective Job Scheduling with Debugging Ease, But Slow Performance
What do you like best about the product?
I find Control-M incredibly helpful for job scheduling as it simplifies the process of scheduling tasks. The feature I appreciate the most is the ability to track failures and access debug logs, which are essential for troubleshooting. Whenever a job fails, I can quickly check the debug logs to instantly identify and solve problems, making the troubleshooting process much more efficient. This capability of Control-M adds significant value by ensuring that any issues can be resolved swiftly without prolonged disruptions.
What do you dislike about the product?
I find Control-M to be slow at times, which can be frustrating and potentially impact my productivity. Additionally, the software feels like it's based on legacy systems, which might suggest that it lacks some modern features or user-friendly interfaces that newer software options could offer.
What problems is the product solving and how is that benefiting you?
I use Control-M for easy job scheduling, tracking failures, and debugging logs, which simplifies troubleshooting processes.
Streamlines Automation, Needs UI Modernization
What do you like best about the product?
I really appreciate the user interface of Control-M, as it is both simple and effective. It features a design that is basic and decluttered, yet it resembles a control room dashboard, offering both simplicity and depth. This combination is refreshing and provides a lot of functional detail while remaining highly customizable. Control-M maintains a user-friendly approach that keeps things straightforward without sacrificing complexity for those who need to dive deeper. Additionally, the ability to visually arrange workflows through drag-and-drop is incredibly useful, allowing for easy adjustments and amendments as needed. The inclusion of analytics graphics, like pie charts, is also a significant advantage, making it easy to comprehend data at a glance. This is particularly beneficial for management, providing well-presented, good data that can be extracted seamlessly.
What do you dislike about the product?
I find the visual design of Control-M to be very dated due to the inability to change the color scheme easily. The current colors appear somewhat childish and reminiscent of an old-fashioned PowerPoint presentation. It would be beneficial if the software allowed for customization in alignment with our core branding to avoid having to modify the graphics through another tool post-generation.
What problems is the product solving and how is that benefiting you?
I use Control-M to automate database processes, ensuring consistency and freeing up my team to focus on other tasks. It standardizes operations, reduces manual oversight, and simplifies complex workflows, allowing us to maintain operational efficiency without variation.
Centralized Task Management with Proactive Alerts
What do you like best about the product?
Control-M shows all the tasks that feed into our applications in one clear place. I can quickly check if a data load, report, or system update ran the way it should. The alerts also help us catch issues early.
What do you dislike about the product?
Some menus take a few clicks to reach, and new users need time to learn where everything is. The design could be simpler, especially when you have many jobs linked together.
What problems is the product solving and how is that benefiting you?
Control-M helps us see job status fast, fix issues before users notice, and understand how different systems connect. It reduces guesswork and speeds up daily support work.
Saves significant weekly effort by automating job scheduling and ensures immediate task transitions
What is our primary use case?
Control-M is used to run Oracle scripts with scheduled jobs including monthly, weekly, and yearly schedules. Around 50 or more jobs are run every week. Control-M connects to the database, triggers all procedures, performs the operation, and generates the final report. The log is sent to mailboxes detailing how the process went, any issues, or any errors. If there are issues, the mailbox is checked; otherwise, a message indicating successful completion is received along with statistics such as how much time the process took and which processes were run. Jobs are scheduled once, Control-M jobs are created, timing is set up, and the jobs fire automatically at the particular time.
Control-M is used to connect to Oracle products, and through Control-M, a Tableau dashboard is maintained. Most of the scheduling jobs use Control-M to schedule. Control-M helps all products, making it a utility that can be used wherever scheduling features are needed. It is not just for DevOps, databases, or front-end applications; it can be used anywhere without manual intervention to perform particular activities. Wherever there is an opportunity for scheduling jobs, Control-M is the first option.
For migration, Control-M is considered very good. Once all the source and target details are configured in Control-M, it can automatically migrate data. It requires proper configuration and specifying the necessary changes for target technology along with the source system scripts. If properly configured, the complete migration can be triggered end to end. Data migrations and reporting, along with all scheduling activities, can be efficiently managed.
What is most valuable?
The best features in Control-M include sending emails to mailboxes after the process is completed and providing proper acknowledgement reports. The timing is impressive; it connects very fast and performs activities efficiently. The UI is very friendly, making it easy to configure jobs in Control-M. If core technology scripts are available, creating Control-M jobs is a five-minute task. The GUI is very friendly, which simplifies task assignment, scheduling, canceling, and all these operations, making it easily navigable.
Every week, 50 jobs are run using Control-M. If those 50 jobs were being run manually, it would take more than a week. Through Control-M, the jobs are able to be scheduled within two days, saving around five days of effort.
Before Control-M, jobs would be run on Friday evening so that the process would end by Sunday night, allowing the business to start on Monday. Without Control-M, everything would have to be run manually throughout the week. Thanks to Control-M, around five days are being saved. Otherwise, old data would be received for the current week's business, but now the latest data is received.
What needs improvement?
Control-M has room for improvement in displaying dashboard-like graphical reports once processes are completed. For example, after scheduling 50 jobs, if a dashboard showing the completed scripts, status, and time taken is displayed within Control-M itself, it would be very helpful. Currently, mailboxes are checked for reports; if it were in Control-M, anyone could check it. Only those configured with specific mail IDs receive emails, so if a few members are not set up, they will not see the reports. If it were available in Control-M, those users could directly check the dashboard.
For how long have I used the solution?
Control-M has been used for the last two years from the beginning of the project level. Earlier, it was already there in Control-M that the client was using.
What do I think about the stability of the solution?
The same score for stability is a nine out of ten.
What do I think about the scalability of the solution?
Control-M is capable of handling a large volume of processing if the necessary memory space is provided to the server.
How are customer service and support?
Great support is received, with a rating of nine out of ten.
How would you rate customer service and support?
What other advice do I have?
Control-M would definitely be recommended because it saves a lot of time. If everything were being done manually, it would take a lot of time to run and validate scripts. If everything is configured in Control-M, even non-experts like front-end staff can trigger jobs, making it simple. It is a one-time configuration, and anyone can trigger it. That is the best part; significant time is saved, and there is no waiting time; the next process starts immediately once the current one is completed. If dependencies are set in Control-M, it starts the next task automatically. That is why Control-M is highly recommended for scheduling.
The client is a big enterprise client.
Control-M requires occasional maintenance, maybe yearly or once every six months for upgrades. A Control-M team manages activities such as maintenance every six months or once a year, including cleaning up scripts or memory.
Around 15 members are using Control-M.
The overall review rating for Control-M is ten out of ten.
