Control-M's experience in Banking and Telcos
April 13, 2021

Control-M's experience in Banking and Telcos

Raciel Hernández Barroso | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Control-M

I work in a company that is a BMC Elite partner and we help other companies in the implementation, administration, support and mesh factory of the main companies in the Banking and Telecommunications of Chile. I have actively participated in more than 700 automation projects and I want to summarize here the common experiences of the operation and use of Control-M in that industry.
  • Control-M is centralized and used transversally throughout the organization. Some cases have several Control-M/Server in production to serve the operation of different countries, however, the Control-M/EM component is usually only one for that environment.
  • Different areas and IT management play different roles in the Control-M Jobs automation lifecycle.
  • The use of Control-M is related to the massive processing of data across different applications and backend services running on different servers and operating systems that could be orchestrated in a complex way.
  • File transfer jobs are common in banking.
  • It is becoming more and more common to design REST API type Jobs in the industry.
  • Control-M provides a single, centralized interface for monitoring and managing all batch processes in the organization. Nothing is hidden or left unattended in a timely manner.
  • The proper use of the BIM component has allowed the change of paradigm in the operation, adopting a proactive management instead of the typical reactive management in the event of production failures.
  • The use of Forecast and production simulations allows you to identify bottlenecks and focus first on managing those failures that have the greatest impact on production SLAs.
  • Control-M/Change Manager has arrived to shorten development cycles from requirements gathering to production testing. It has been a utility that monetizes the development of Jobs meshes.
  • The GUI is capable of efficiently handling more than 80,000 jobs per day. This is certainly a challenge in designing a good user experience. I don't know if there is a reasonable limit to this. One of my clients runs more than 80,000 Jobs daily and the GUI remains smooth all the time.
  • Job-As-Code is a DevOps accelerator that has just begun to be adopted. Its implementation will make workload management even more cost-effective.
  • Enabling secure mode on all Control-M is cumbersome and could be one reason why customers are reluctant to adopt it, despite the importance they place on the security of their IT assets.
  • While it is true that connection profiles are useful for hiding secrets, there is no possibility to make use of secrets in system variables in the Jobs design. Furthermore, secrets that are escaped in the output output should be able to be managed individually.
  • The use of translator tables for the promotion of Jobs between environments is limited and has not allowed their use in most of the clients I have worked with. The reason is that the rules of homologation between environments is more complex than usual.
  • Control-M has improved service delivery times, reliability and quality of batch processing.
  • It has simplified the management of the operation and the use of the alert system has made it possible to act in a coordinated and efficient manner to solve problems.
  • The implementation of policies has made it possible to make greater use of Control-M and thus reduce development costs that are generated unnecessarily when the potential of the system is not considered.
  • Simplicity and good user experience.
  • Ability to scale and process large amounts of jobs without affecting the user experience.
  • For the large number of Jobs palettes and the ease of designing new Job Types.
  • Simulation and critical path management options.
  • Resource automation and workload policy enforcement.
  • For the great variety of integrations.
  • Ease of running processes on agentless servers.

Do you think Control-M delivers good value for the price?


Are you happy with Control-M's feature set?


Did Control-M live up to sales and marketing promises?


Did implementation of Control-M go as expected?


Would you buy Control-M again?


The use of Control-M is recommended for the following circumstances:
  • Workload and batch processing automation.
  • Backend automation based processes
  • Silent execution of processes and no human intervention
  • Execution of workflows that are too complex for a human to handle
  • Massive operations on massive amounts of data
  • Invasive, with access to the data layer and business logic
  • Processes with focus on security, efficiency and reliability
  • When you want to predict the duration of each job and of the complete flow
  • In critical path management
  • For proactive alerting of deviations and possible job failures.
  • For workload simulation
  • Capability for resource automation

Control-M Feature Ratings

Multi-platform scheduling
Central monitoring
Alerts and notifications
Analysis and visualization
Application integration